Bugcheck 124

[speeddemon89]

I'm looking for someone to give me a diagnostic of why my computer keeps crashing at very inopportune times.

The bugcheck was: 0x00000124 (0x00000000, 0x862574dc, 0x00000000, 0x00000000).

I have several dump files so I'm gonna attach several of them.

If you have any other questions just let me know.

 

[Jonathan_King]

Welcome!

Please read this article on bugcheck 124: http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

 

[speeddemon89]

Thank you very much for the swift reply. I have tried a fan to the motherboard, i have tried to individually remove the ram one by one and retesting, I have ran memtest all day and night with no errors and I have also reinstalled windows. The only thing that I have not done is checked on the overclocking. I have never messed with any of that and am not really sure where to begin. If there is a simple way of checking that would be great. Also I am going to run a check on my hard drive to see if there is any bad sectors there.

 

[speeddemon89]

Alrighty, well I have run the diagnostic programs that I could find for my memory (memtest) and my hard drive (SeaTools) and everything came back fine. Now I did go through and found that the network driver on my motherboard was out of date and went ahead and updated it. I thought that had fixed it but after 3 hours of gameplay and listening to music, it crashed again. Now I was wondering if there was any way that a detailed crash report could be compiled to find the exact culprit to these annoying crashes. If anyone could help me that would be great.

Here is the most recent crash minidump file.

The bugcheck was: 0x00000124 (0x00000000, 0x86236024, 0x00000000, 0x00000000).

Oh and i checked on the overclocking of my cpu and it was running at the set standard so no problem there.

 

[zigzag3143]

Alrighty, well I have run the diagnostic programs that I could find for my memory (memtest) and my hard drive (SeaTools) and everything came back fine. Now I did go through and found that the network driver on my motherboard was out of date and went ahead and updated it. I thought that had fixed it but after 3 hours of gameplay and listening to music, it crashed again. Now I was wondering if there was any way that a detailed crash report could be compiled to find the exact culprit to these annoying crashes. If anyone could help me that would be great.

Here is the most recent crash minidump file.

The bugcheck was: 0x00000124 (0x00000000, 0x86236024, 0x00000000, 0x00000000).

Oh and i checked on the overclocking of my cpu and it was running at the set standard so no problem there.

Well this one still points to hardware.
Did you do all 9 points in the instructions "what it means and what to try"??


If we cannot find the offending driver we can always use driver verifier to help

These are the instructions for it. Let us know before you start

Ken

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Ken