Windows 7 BSOD 0x124

[en1ma]

Is Windows 7 . . .
- x86 (32-bit) or x64 ?
64bit
- the original installed OS on the system?
Yes
- an OEM or full retail version?
Self Built

- What is the age of system (hardware)?
1 year
- What is the age of OS installation (have you re-installed the OS?)
8 months


-- happens extremely randomly. It seems to happen more when idling than gaming but I could be imagining that.

I have a hunch it's AMD drivers....

I'm wondering if anyone can look at dump files and see if there's signs that show that?

I'm running prime95 now and it's been fine for 2 hours so far. I'm running OC'd but I've been running overclocked for a year now. So I doubt it's the CPU faulting out of no where, especially with prime running fine.

It's a 2500k overclocked to 4.5GHz and I'm at 65C under load w/ prime 95.

I have 2x 6950's. Those are overclocked and HAVE been overclocked as well since the CPU- nothing new besides it possibly being the new cap drivers for AMD....

Thoughts from analyzing the dump files?

 

[JMH]

en1ma,

* I suggest you read through "Stop 0x124 - what it means and what to try"

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.

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

 

[en1ma]

I did read that... I don't know what to do after reading it. That's why I posted this debug information.

 

[JMH]

The information you were provided with contained clear & concise troubleshooting methods.

Did you actually read & try each of the 9 steps?
You provide no written indication that you have.

To reiterate...

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.

 

[en1ma]

Yes, I tried all of the steps. I tried updating all drivers. I tried stress testing each component. The removal of components will not tell me anything because I need every component to be able to boot. (Besides the memory which is fine on it's own).

The crash.zip which is in my first thread contains many dump files. I don't know why you're saying it doesn't contain dump files. It contains at least 15.

My issue is that I don't know how to read these files that may have a clue on to what hardware piece is failing if that, or what driver.

 

[JMH]

Please run these two tests...

1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+


2-Driver verifier

I'd suggest that you first backup your data 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/Windows 7 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.

Driver Verifier - Enable and Disable

NB.
In future we would prefer you upload the DMP files this way...

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.

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

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.


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 drop down box (the 256kb varies).
*Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
*OK.
Reboot if changes have been made.

 

[zigzag3143]

Yes, I tried all of the steps. I tried updating all drivers. I tried stress testing each component. The removal of components will not tell me anything because I need every component to be able to boot. (Besides the memory which is fine on it's own).

The crash.zip which is in my first thread contains many dump files. I don't know why you're saying it doesn't contain dump files. It contains at least 15.

My issue is that I don't know how to read these files that may have a clue on to what hardware piece is failing if that, or what driver.

Only after running JMH suggestions and having them pass you can run these additional tests to stress the hardware.


Try this free video stress test: 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).
- Click "Quit" to exit