Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD when playing games (Diablo 3 + Starcraft II)

28 May 2012   #1
dabears

Windows 7 64-bit
 
 
BSOD when playing games (Diablo 3 + Starcraft II)

Hi, I have gotten a couple of BSODs when playing games. I am running Windows 7 Ultimate SP1 64-bit, OEM edition. I have attached the dump information as outlined in the sticky. Any help would be much appreciated, and thanks in advance!


My System SpecsSystem Spec
.
28 May 2012   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Stop 0x124 is a hardware error

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

If you continue to get BSODS, here are some 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).



Quote:
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.



Stop 0x124 - what it means and what to try
My System SpecsSystem Spec
29 May 2012   #3
dabears

Windows 7 64-bit
 
 

Thanks for the help. I am not OCing, and my drivers are up to date. Yesterday, I ran a bunch of tests on hardware. My HD passed Seatools short and long tests, memtest86+ completed 8 passes with 0 errors, and OCCT ran a couple of hours with no errors. Even though OCCT passsed, my gut tells me it is GFX card related because the BSOD only happens when I play games. Do you recommend any other stress testing software for the graphics card? I want to be absolutely sure the graphics card is fine before I attempt a clean install.
My System SpecsSystem Spec
.

29 May 2012   #4
zigzag3143

Win 8 Release candidate 8400
 
 

Quote:
FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90șC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
If the temperature gets above 105șC, quit the test - the video card is overheating.
- Click "Quit" to exit
Quote:
CPU Stress Tests:
- http://downloadcenter.intel.com/Deta...19182&lang=eng
- 7Byte : Hot CPU Tester Pro
- 7Byte : BurnIn64
- CPU Stress test - Overclock.net - Overclocking.net
- Fossil Free Online CPU Load or Stress Test.
- CPU Stability Test description, System Resources Tune-Up. Downloads List By All Time Popularity | PCWorld | PCWorld
- CPU Stress test - Overclock.net - Overclocking.net
- |MG| CPU Stability Test 6.0 Download
- LinX - A simple Linpack interface

Try these
My System SpecsSystem Spec
Reply

 BSOD when playing games (Diablo 3 + Starcraft II)




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD Playing Diablo 3 and Other Games 0x0124
I play Diablo 3 most of the time. It happens during other games too. I get about maybe 25 minutes, sometimes 2 hours when I'm lucky. It always comes up as a STOP 0x0124 error. BlueScreenView describes it as crashed by hal.dll and ntoskrnl.exe. I'm not sure whats causing it at this point. I'm asking...
BSOD Help and Support
BSOD while playing Starcraft II and Diablo 3
As the title suggests I've been getting the BSOD only when playing SC2 or D3. It seems to happen more often in multiplayer for SC2 but more often in D3. In both I've reduced the graphic settings to the lowest but to no avail. I have the latest drivers and am lost as to what to do next. I've...
BSOD Help and Support
BSOD playing Diablo 3 (maybe other games), error 0x0000007a
Hi, found your forum through google. I cant solve my problem Everytime I'm getting BSODs while playing Diablo 3 for 5-10mins but its happening after I reinstalled Windows 7. I dont have any other games right now to test maybe its caused by Diablo 3 but it worked perfect before the reinstallation....
BSOD Help and Support
BSOD playing games (Diablo 3), error 0xF4 Critical_Object_Termination
Running Windows 7 Ultimate x64, purchased for new build (not OEM). Computer was built in April: CPU: I7-2700K (Running @ stock), After-market cooler Motherboard: ASROCK|Z68 EXTREME3 GEN3 1155 R RAM: CORSAIR CMZ8GX3M2A1600C9 4GBx2 Video: EVGA GeForce GTX 560 Ti FPB 1024 MB GDDR5 SSD: 180...
BSOD Help and Support
[BSOD Help] Happens most frequently when playing games like diablo
I have attached pictures of my specs of my computer. What I have in it, my graphics card, my ram, my mother board, sound card. Everything is posted in the picture. This BSOD usually happens most when I am playing Diablo the game keeps slowing down and then out of no where BSOD. Any exaplanation...
BSOD Help and Support
BSOD Playing games Flight Sim X And Diablo 3
Hi there, In the last few days I have started getting BSOD's When playing games, The two mentioned in the title specifically. They will run OK for around 5/10 mins then BSOD. The only change I have made to the system in this time that i can think of is updating my ATI driver, But I did that...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 07:04.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App