Solved 0x00000124 While Playing MW3

[edgex]

So to start off I think this issue may have started when I jumped from amd 11.11 to 12.1 (now 12.1a) drivers. But I'd like some advice on the issue anyways. (Also, I always run Driver Sweeper every time I update my driver to make sure I have a clean slate)

Issue only happens in Modern Warfare 3, and pretty random. some days I can play through 10+ games. others ill crash in 1 or 2. It doesn't always happen while in game, sometimes just in the lobby.

Heat is not an issue, CPU never goes above 55c, top GPU never above 70c, bottom never above 65c. Have been running this rig about 9 months, had no issues with Black Ops, or Crysis 2, or Battlefield 3...

System:
Windows 7 Ultimate x64 SP1
i5 2500k @ 4.5GHz
ASRock P67 Fatal1ty Pro Mobo
8GB Gskill 1600MHz RAM
2x MSI 2GB 6950s in Crossfire (unlocked shaders and OCed to 900 - 1400)
Corsair Force GT 120GB + 1TB WD Black HDD
H60 HSF with two Cougar fans in Push/Pull
Corsair AX850W PSU

Was running Norton, just uninstalled and am going with MSE to see if that helps any.


I know you guys need the .dmp file, I don't know how to enable it and get it to you.

Thanks

 

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

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.

 

[edgex]

Updated with the correct files (I believe)

 

[JMH]

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

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

Some generic advice.

If you are overclocking STOP. return to the default settings at least for now.
If you are running a RAID update its driver.


You can read more on this error and what to try here... http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[zigzag3143]

Read and perform the suggested in JMH's post.

I do notice Symantec which is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows

If you are overclocking STOP

If you have made any changes to ram recently revert back

 

[edgex]

It does seem to be that Norton was the cause, and have gone through many games now without issue.

MSE it is.

/sovled