Solved BSOD playing SW:ToR, error 0x00000124

[PhrozenFear]

Crash playing SW:ToR, error 124 (no longer BSOD)

Windows 7 Pro x64
- Intel 1st gen Core i7 860 @ 2.8 (normally overlocked to 4.0, but reset to stock to test)
- 2x 1TB Seagate HD's (have had this problem on both of them, as well as my other two disabled Seagate 500GB HD's)
- eVGA GeForce GTX280 graphics - latest 2.96 graphics driver installed at windows reinstall
- 8GB Corsair Viper RAM

Some information about this:
- Fresh reinstall of Windows as of three days ago
- Fresh run of all windows updates as of three days ago (Minus Bing Bar and Security Essentials)
- Fresh install of game from online

While loading the game, I have it start to load, then graphics go all wonky on me (video showing this at SWToR Crash - YouTube, approx. 30 seconds into it), causing system crash, or else I get BSOD with error 124.

Also, I get random Error 124 crashes, from doing completely random things - browsing the web (googling information, youtube, facecrack), doing windows Updates, re-installing software (like Thunderbird, Chrome, Trillian, etc). It happens completely randomly, and is kind of driving me nuts.

Any assistance would be great, since I can't afford any money to drop on a new system any time soon.


EDIT MAY 14:
Sorry, I didn't upload the attached files, and I've got them now. System Health Report is in the folder with the dump files and everything else. Sorry about that. They are now attached.

 

[PhrozenFear]

So, to further add to some of what diagnostics / tests / checks I have done on this system:

- Hiren's Boot CD using Seagate Tools on it, to do a full level test of both of the 1TB HD's (both of the 500s are disconnected)
- Reseated the RAM
- Reseated the SATA cables to the DVD-ROM Drive, and the HDD's.
- Tried changing the cables of the HDD's
- Reseated them in different ports (instead of 0 (DVD) 1 (HDD) and 2 (HDD), tried 3 (HDD), 4 (HDD), and 5 (DVD)
- Reseated the power connections on the motherboard for power
- Changed the power plugs to the various devices (HDD and DVD)
- Fresh firmware reinstall of the Motherboard (A74, dating Aug 8, 2011)
- Factory reset of motherboard settings back to stock

- testing now with Prime95 to do a memory test
- Have done a memtest using an ubuntu boot disk
- Done an full system MRI by a buddy who works for Geek Squad

This is the fourth reinstall of Windows (on a fourth drive configuration) in the last two weeks. Hopefully I don't have to do it many more times - Microsoft is getting cranky at me for all the activations I keep calling in for.

 

[zigzag3143]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
Please attach the DMP files to your next post not to post one.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

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

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[PhrozenFear]

Thanks for that, mate. The file has since been uploaded.

A few things:
- The system was overclocked, but the crashes still happened randomly even when I reset the processor to stock. So I put the overclock back on, thinking that wasn't the issue.
- The system runs with an open side panel, on the concrete floor of a basement. Exhaust fans are tuned right, and there is no airflow issues.
- MemTest86+ was run twice yesterday, with no anomalies found. MDSCHED was run with no anomalies the day before I posted in here. Same with CHKDSK.
- All drivers are as up-to-date as Windows will allow. The only non-Windows-updated driver I have is the graphics card.
- BIOS is as up-to-date as it can be.
- I did a complete system blowout and reseated all connections a couple months before this all started to happen, and nothing new has been added since - no drivers updated, no new hardware. Just minor software updates - games, new versions of certain programs, etc.
- I have tried with a vanilla reinstall, and had the same randomness happen. Sometimes it'll be during the downloading of windows updates, so I stopped doing them in bulk and did them one at a time. I've also had the crash happen during Windows setup - before it even gave me the chance to log in for the first time, it had crashed (on a previous reinstall, different HD). So I know it's not the Windows install itself that's causing the issue - at least, I hope not. I don't have any spare copies of Win 7 Pro x64 to test with.

Thanks again, I eagerly await any further assistance you can provide, or anything further I can try.


EDIT: Attached to this post are JUST the dump files. I have them in a separate zip file now, and the first post has the whole jcgriff2 folder.

 

[zigzag3143]

If you ran memtest for the required 6-8 passes and it passed I would start running stress tests so see if we cant trigger the crashes.

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

CPU Stress Tests:
- http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=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

 

[PhrozenFear]

Yes, it ran the full MemTest86+ series of tests, no errors at all, and I ran it twice just to be sure. RAM seems stable.

In reading other threads with similar problems, I heard about Prime95, so I tried running it for about six hours, and nothing at all happens. Then I dropped the overclock again and ran another twelve hours, still nothing, and everything seems to be a little more stable, so I'm leaving the overclock off.

However, while running FurMark 1.10.1, I click Settings, check Burn-In (Dynamic Background was already checked, whereas Dynamic Camera, Xtreme burn-in and Post-FX were unchecked), set GPU Alarm to 92, and to Log GPU Data, hit OK. Went and clicked Burn-in test, and the first five seconds, everything's okay. After that, both of my monitors go to a solid colour (different for each one), and the system locks up completely. I let it sit for 15 minutes, nothing at all. Have to do a hard power-off to get anything to happen.

If, however, I run just the Benchmark (User Settings), I get it to complete no problem. GPU Temp starts at about 80, stabilizes at about 90ºC, and goes through the whole thing without causing a crash of any sort. Even if I run it five times in a row, it still stays at those levels and runs completely.


I also have changed my drivers since I started this thread - apparently, I had the 3.10 beta instead of the 2.96 stable graphics drivers. I still crash randomly, usually without a BSOD, but now I'm running the proper stable drivers again, and back again to stock processor speeds.

 

[writhziden]

I assume Burn-In on FurMark also crashes the system on the stable drivers? If so, you should start swapping out hardware to determine which is causing the issue starting with the most likely: graphics card, PSU, motherboard (the motherboard you probably cannot swap and should RMA if a different graphics card and a different PSU do not resolve the problem). Swap one at a time, and try to get a graphics card and a PSU that are similar to your current hardware if possible.

As you add and remove hardware, follow these steps for ESD safety:

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.

Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[PhrozenFear]

Yes, the FurMark causes the crash on both beta and stable graphics drivers. I haven't tried from Safe Mode (but I will as soon as I hit submit).

Since posting my last post, somehow something changed, and the BSOD's have stopped. Now I still have the funky graphics crash when playing my games (which is shown by example in the youtube video first post), but they don't lead to BSOD's any more. Something happened as well to stop the crashes for a little bit... until I rebooted my PC. The only changes I made between when they stopped and the last reboot that started again was installing Acrobat (which never caused a problem before), and my printer (same). I have tried uninstalling them both, and no change.

I also took my PC out and blew it out again, reseated the graphics card (which I don't have a spare of any kind of), blew the crap out of it, and reseated everything else except the CPU. Went through three tanks of air doing it, too. Upon reboot, graphics are screwed up in anything except safe mode, so I'm gonna try my temporary fix of uninstalling the 296.10 stable graphics drivers and re-downloading the driver through Windows Update. See if I can at least get back into Windows. I also have tried while using a separate PSU, no change.

 

[writhziden]

This is sounding more and more like a failing graphics card... Let us know what happens when you switch drivers.

You say everything is screwed up outside Safe Mode; does that include on the POST screen as well? Power-on self-test - Wikipedia, the free encyclopedia

 

[PhrozenFear]

Yes, it is starting to sound like it. I have a friend who's willing to loan me his graphics card to test it - it is a lower-end card, but still PCI-E, so I can test to make sure it isn't the mobo.

And no, I don't mean the POST. POST works fine, graphics and internet work okay if I boot into Safe Mode (I only have my one monitor rather than both, but I can still operate). It's just something else. I'm going to try rolling back to the previous driver before the 296.10, and see if that might help fix things. Since the beta drivers don't work, or the current stable, time for a rollback. Then, when I get my buddy's graphics card, I'll start with the older drivers, then work my way to the new ones until the problem occurs again (if at all).

 

[writhziden]

Sounds like good steps. Let us know the results.

 

[PhrozenFear]

So, tried going back to 285 version of drivers, things seemed to work for a bit - was able to do most Windows-related things no problem. Gamed for a little bit before it crashed, but wasn't too big of a deal. Kind of expected it.

Updated to the 295 version, and it won't even load me into Windows. On load, screen colour goes all wonky like in the YouTube vid, and system locks up. On reboot, I get an Error 117 (which google leads me to believe is a graphics timeout error, something that generally happens when your graphics card is hooped).

The only thing I've noticed seems to be the issue is I removed the PhysX driver from the last install, went back to the 285, and stability seemed to ensue (at least for a bit). On upgrading to the 295, it installed a newer PhysX driver, and crashes happened.

So, my plan is to Sys Restore back to 285, uninstall PhysX, and try installing 295 without it. Barring that, trying the 296 without PhysX might be worth a shot, too. At least until I can scrounge up the extra three hundred I need to buy a new card.

 

[writhziden]

Alright, sounds good. Not sure why PhysX would cause issues like that, though...

 

[PhrozenFear]

I'm not sure either, but it was the common thread between crashing and not crashing. Or so I thought.

Today I went out and got a GTX560 TI and all problems went away. I haven't had a crash yet, and I've gamed for half the day on ultra settings, so I can confidently say it was the graphics card that caused the problems. We can close this thread. Thank you muchly, everyone, for your assistance.

 

[writhziden]

Glad the new card resolved the issue. When you are sure the problem is solved, you may mark the thread solved.