Blue Screen crash during Video Games

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

sniperfx20

Thread Starter
Joined
May 15, 2012
Messages
3
Hello,

I randomly have issues of game's crashing into "BlueScreen" errors. Well the screen isn't really a bluescreen but rather the image of the game becomes 'corrupted'. Sometimes you can still hear the audio while the screen is frozen in place and it sometimes auto restarts the computer on it's own. I am either playing World of Warcraft or Starcraft II.

***************************************************************
***************************************************************
These are my solutions:
1. Though the error occurs in both games, I have re-installed them both games multiple times.

2. I have installed the latest drivers, including my graphic card: NVIDIA GeForce 9800 GT. Problem Persists

3. I initially had Windows Vista 64 Bit running, but I had just did a clean and fresh install of Windows 7 Ultimate 64 Bit. Problem persists.

4. I have 'cleaned' out my desktop computer from dust and took out the graphic card and placed it back in.


***************************************************************
***************************************************************
This is the "error" Windows 7 caught:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8008C583D8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\051512-33181-01.dmp
C:\Users\Joe\AppData\Local\Temp\WER-66440-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

***************************************************************
***************************************************************

My computer specs:
HP Intel 2 Quad Core Q6600 @ 2.40 Ghz
8 GB RAM
NVIDIA GeForce 9800 GT
BIOS Date: 09/05/08 Ver 5.30
Direct X 11

***************************************************************
***************************************************************

If anyone can provide any constructive suggestions, that would be greatly appreciated! Thanks
 

fairnooks

Banned
Joined
Oct 1, 2007
Messages
5,251
To me it sounds like the graphics card is either overheating and seizing up or just has some other hardware glitch that only becomes apparent when its more stressed.
 

Tanis

Shane
Joined
May 29, 2006
Messages
3,969
I agree with fairnooks, it does sound like a problem with the GPU under stress. This could be due to its age, overheating, power issue or other factors.

Having said that, I would suggest you update Windows as it would appear you are currently about 17 months out of date as you don't appear to have Windows 7 SP1 installed which was released in Jan 2011. This also means you are probably missing a number of other stability and security patches and updates. I appreciate, as you said in your post, this is a fairly new clean install but you need to get it fully patched and up to date to diagnose properly.

What is the exact make and model of your PC, how old is it and have you ever upgraded / changed / added any hardware since you bought it? That is assuming its a 'big name' machine like HP, Dell, Acer etc.

If it is a self / custom build, what is the exact make and model of the motherboard, RAM, power supply etc?

The more info you can give us the better.
 

sniperfx20

Thread Starter
Joined
May 15, 2012
Messages
3
Thanks for the help!
I will start patching it to the latest windows 7 update.
It's a HP FQ550AA-ABA m9426f (thats what it says under dxdiag.exe).
I bought it around 2008, since then I replaced the graphic card and power supply.

I will also open the computer and allow additional air for the graphic card fan. I truly believe it's the graphic card causing issues.
 
Joined
May 31, 2009
Messages
274
Stop 0x124 is a hardware error. I can tell you more if you upload the DMPS.

If you are overclocking try resetting your processor to standard settings and see if that helps.

If you continue to get BSOD here are some more things you may want to consider.

This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).



Stop 0x124 - what it means and what to try
Synopsis:

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.


Generic "Stop 0x124" Troubleshooting Strategy:

1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.


2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.


3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.


4) Update the motherboard BIOS according to the manufacturer's instructions.
Their website should provide detailed instructions as to the brand and model-specific procedure.


5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.

6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing.
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the harware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent harware troubleshooting steps may, in some cases, void your warranty:

8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Staff online

Top