BSODs everyday! 0x00000124

Zoik said:

Ok, When I first built this PC not long ago I dont remember having any problems. Now all the sudden I seem to get them everyday. They happen in game or just in Windows while browsing or whatever.

So my most recent BSOD was just moments ago and I decided to check the event log in hopes that there is a decoding genius out there that could possibly assist me.

These are the codes. If you need more I'm sure I can get more info.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa8007fc9028, 0x00000000be200000, 0x000000000005110a). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 112911-17035-01.

If my memory serves me correctly they have all started with 0x00000124, not sure sure about the codes that follow.

Thank you. Any help would be greatly appreciated as I'm sure you know how frustrating these can be! Specially when you just buy an very expensive machine.

Sys Specs:
i7 2600k
Asus P8P67 Deluxe
8GB G.Skill 2133
GTX 570
WD Cav Black 1T x 3

To be more accurate we need you to upload the DMP files


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... Stop 0x124 - what it means and what to try

Is this the info you seek? Or do you need something else?

Bugcheck Analysis


WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007fc9028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

Also for now I will revert my overclocks. As for RAID my primary drive with Windows installed in the Intel controller is not in RAID, I do run a RAID set up in my Marvell controllers for my data drive for backup purposes which at the time of any Blue Screens I was not running any files of my data drive. that drive is just used for back up files such as movie, music, pictures etc.

As for the rest of the DMP read the report is here http://www.mediafire.com/?yk70barad57bz3p
If there is something else you or anyone needs let me know, Thanks.

Zoik said:

Is this the info you seek? Or do you need something else?

Bugcheck Analysis


WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007fc9028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

Also for now I will revert my overclocks. As for RAID my primary drive with Windows installed in the Intel controller is not in RAID, I do run a RAID set up in my Marvell controllers for my data drive for backup purposes which at the time of any Blue Screens I was not running any files of my data drive. that drive is just used for back up files such as movie, music, pictures etc.

As for the rest of the DMP read the report is here DMP.txt
If there is something else you or anyone needs let me know, Thanks.

No sorry.

We do need the actual 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.

It is almost impossible to spot trends from a single DMP file so if you have more than one please upload them. If you only have one please wait until the computer crashes again then upload both.

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.

Ok, I have attached the contents of the Minidump directory.

Zoik said:

Ok, I have attached the contents of the Minidump directory.

Virtually all of these were BCC 124 (hardware). I suspect RAM. Please run these two tests.

These crashes were caused by memory corruption. Please run these two tests to verify your memory and find which driver is causing the problem.


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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

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

Driver Verifier - Enable and Disable

Alrighty, I've created my boot CDs and I do have a laptop for backup contact. But before I go ahead with the Driver Verifier process I have a question. upon reading the link bellow your instructions it appears it will create a dump file with the info needed to determine which driver is causing the issue. So my next question you mentioned "if you know what causes the crash, do that repeatedly." What do I do repeatedly?
My apologies if this seems like a stupid question but I am a little lost with that one!

Zoik said:

Alrighty, I've created my boot CDs and I do have a laptop for backup contact. But before I go ahead with the Driver Verifier process I have a question. upon reading the link bellow your instructions it appears it will create a dump file with the info needed to determine which driver is causing the issue. So my next question you mentioned "if you know what causes the crash, do that repeatedly." What do I do repeatedly?
My apologies if this seems like a stupid question but I am a little lost with that one!

If you know that a certain action (ie a particular game, or when you boot your computer, or when coming out of sleep, etc) DO that action to try to cause a crash.

If verifier spots the offending driver it will write it to the pagefile and then the DMP. When you upload the DMP file we can examine its content.

There are no stupid questions, just stupid people who dont ask them. I am always happy to explain.

Well, I think I owe you an update since you've helped me out this far. and I appreciate all your help. I think I may have figured it out. After getting rid of what I thought was stable overclocks I was not getting any more BSODs. That pretty much told me what was going on. I have tried that before and thought I was still getting BSODs, but come to think of it it may have been restarts which is a problem I've been getting with some games. Reverting my Nvidia drivers seemed to fix some of those problems and a specific BSOD. With all this new technology trying to blend together there's just so many problems and incompatibilities going on its insane! I ran the memtest boot CD anyway to start and that passed. I then placed my 2600k back up to 4.5GHz @ 1.3v and ran Prime95.. BSODs right away first couple tries. Upped my voltage to 3.2v and ran prime95 for over an hour on the blend test and everything passed with no errors.
So for now everything seems ok. Only way to know for sure is to use my PC as normal for a week or so and see how everything pans out.
Thanks again and I'll let ya know in a week or so what happens.

Zoik said:

Well, I think I owe you an update since you've helped me out this far. and I appreciate all your help. I think I may have figured it out. After getting rid of what I thought was stable overclocks I was not getting any more BSODs. That pretty much told me what was going on. I have tried that before and thought I was still getting BSODs, but come to think of it it may have been restarts which is a problem I've been getting with some games. Reverting my Nvidia drivers seemed to fix some of those problems and a specific BSOD. With all this new technology trying to blend together there's just so many problems and incompatibilities going on its insane! I ran the memtest boot CD anyway to start and that passed. I then placed my 2600k back up to 4.5GHz @ 1.3v and ran Prime95.. BSODs right away first couple tries. Upped my voltage to 3.2v and ran prime95 for over an hour on the blend test and everything passed with no errors.
So for now everything seems ok. Only way to know for sure is to use my PC as normal for a week or so and see how everything pans out.
Thanks again and I'll let ya know in a week or so what happens.

Glad you figured it out and are working

Ken