Solved BSOD playing Battlefield 3, Star Trek Online after adding bluray burne

[ahcirandombsod]

Hi guys. This windows install has been running flawlessly until Tuesday. I purchased a Pioneer BDR-206 BDK internal 5.25" optical drive and installed it. It wasn't running perfectly so I changed my SATA type in BIOS to AHCI. That nerfed my Windows install and I had to fix it with my Windows 7 flash drive's repair utility. That fixed it, but I got reboots when ripping a CD (in the process of ripping/converting to flac my brother's giant CD collection) and playing Star Trek Online and Battlefield 3. So, I'm only random rebooting/BSODing (I changed the registry entry to 0 so I can take a picture of the actual BSOD error) under heavy load. Yesterday it happened while just playing Star Trek Online, as I quit trying to rip while playing games.

I built this machine in April of 2009. Since then it has received a new HDD, GPU, and the addition of the aforementioned optical drive. I have attached the .zip specified in the sticky in this forum and followed that OP's instructions to the best of my ability.

This Windows install is from December of 2011 and it is Windows 7 Ultimate x64 full student retail. This is the machine's third Windows 7 install, and the first one on this HDD. The first install was the public beta. I am overclocked and custom water cooled and I tried changing all X58 chipset-specific OCing parameters back to stock for X58 and an i7 920 with no change in behavior so please don't tell me "oh lulz it's broken because you're overclocking." Also, the motherboard was replaced in December alongside the new GPU and HDD so that's where the third Windows install came from.

I'd really like to save this Windows installation if at all possible. I have everything backed up with Backblaze but that's hundreds of GB's and my monthly Internet allowance is merely 250GB.


Edit; I have two SATA controllers on my board. I have 6 SATA 3Gb/s from Intel ICH10R and a crappy Marvell 6Gb/s that I don't use (2 ports). BIOS is configured for AHCI, was on IDE originally. Ran Startup Repair from Windows Install medium.

 

[Vir Gnarus]

All 4 crashdumps are WHEA errors reported by your CPU. Two of them state a data write error in your L2 cache of your CPU, while the other two state an issue with the internal timer of your CPU. You had the Intel Linpack benchmark running for three of them at the time, so I assume this was during stress testing while you were checking out your OCing.

There's a couple things I've seen that would cause what appears to be CPU failure displayed by these WHEA error records. First off, if you're using any utilities or software that came with your motherboard, please uninstall them. All OCing should be done straight from the motherboard. Software-based OCing is not preferred, and often the software that runs them is riddled with bugs that actually make WHEA think that the CPU is failing. The other motherboard software I've seen do the same thing in order to perform some gimmick. It's recommended to remove em all. If you wish to OC, you should resort only to doing so with the BIOS.

If none of that seems to resolve the issue, than run MemtestCL for a few passes. I've actually seen graphics cards cause these WHEA errors before (rare, but it happens). You may also run Prime95 on Torture Test at Large FFTs overnight if you wish to test your CPU specifically.

In addition, you'll want to provide us some voltage/temp logs with HwInfo. When it starts, check Sensors only, then record two logs: one during idle and one during high load. For idle have it run 30 minutes. For high load, it'd be preferable if you have it run until the system crashes. Otherwise, have it run for 45 minutes to an hour. Send both logs to us.

Lastly, I'd like to add that it is possible that the CPU has been stressed to the point of no return with your OCing, causing these errors to now start manifesting themselves even when you reset things to factory defaults. Of course, our endeavor is to test and make sure that's not the case rather than fruitlessly spend money and/or time getting a replacement CPU, but there is always the chance that it's simply dead now. It is possible to OC a CPU and keep it stable during high loads, but it's also well capable that OCing would reduce the lifespan of your CPU in the meantime.

 

[ePeen]

ALL attached dumps are x124 hardware bugchecks, so something is going on here regarding your hardware most likely, especially since you've gone ahead reformatted multiple times.

General troubleshooting for this bugcheck, thanks to H2S04.

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

With this being said, I'd recommend first and foremost testing your memory, I don't see any mention of doing so in the OP, so:

Read the following to test your memory for errors.

Drivers that need to be updated:

SaiH0460.sys - Mon Nov 24 05:14:27 2008 (not listed in the carona drivers list, most likely related to Saitek as other drivers minus the "H" in SaiH are labeled Saitek. Possibly a driver for the hub on the keyboard if there is one?" Update here.

For now... and please, read before typing and jumping to conclusions. Bring every component on your system that is overclocked to stop temporarily for diagnostic purposes. With all do respect, I don't care if you believe your Overclock is stable, I don't care if ran Prime95 for 400 hours and got no crashes, an overclock can & will do unthinkable thinks to a system when unstable. So, with that being said, for testing purposes allowing us to help you better, please just bring everything to stock for NOW. When your issue is solved, you're MORE THAN WELCOME to put everything back to what it once was

All 4 crashdumps are WHEA errors reported by your CPU. Two of them state a data write error in your L2 cache of your CPU, while the other two state an issue with the internal timer of your CPU. You had the Intel Linpack benchmark running for three of them at the time, so I assume this was during stress testing while you were checking out your OCing.

There's a couple things I've seen that would cause what appears to be CPU failure displayed by these WHEA error records. First off, if you're using any utilities or software that came with your motherboard, please uninstall them. All OCing should be done straight from the motherboard. Software-based OCing is not preferred, and often the software that runs them is riddled with bugs that actually make WHEA think that the CPU is failing. The other motherboard software I've seen do the same thing in order to perform some gimmick. It's recommended to remove em all. If you wish to OC, you should resort only to doing so with the BIOS.

Very good call, my friend! After checking OP's drivers list, he does in fact have the Asus PCProbe Utility installed.


Dump for reference:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\Windows_NT6_BSOD_jcgriff2\020612-19656-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0301e000 PsLoadedModuleList = 0xfffff800`03263670
Debug session time: Mon Feb  6 03:43:17.944 2012 (UTC - 4:00)
System Uptime: 0 days 0:18:30.866
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007349028, be000000, 800400}

Probably caused by : hardware

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa8007349028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`04590a98 fffff800`03619a3b : 00000000`00000124 00000000`00000000 fffffa80`07349028 00000000`be000000 : nt!KeBugCheckEx
fffff800`04590aa0 fffff800`031ab513 : 00000000`00000001 fffffa80`0734ca10 00000000`00000000 fffffa80`0734ca60 : hal!HalBugCheckSystem+0x1e3
fffff800`04590ae0 fffff800`03619700 : 00000000`00000728 fffffa80`0734ca10 fffff800`04590e70 fffff800`04590e00 : nt!WheaReportHwError+0x263
fffff800`04590b40 fffff800`03619052 : fffffa80`0734ca10 fffff800`04590e70 fffffa80`0734ca10 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`04590c90 fffff800`03618f0d : 00000000`00000008 00000000`00000001 fffff800`04590ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`04590cd0 fffff800`0360ce88 : fffffa80`05642700 fffffa80`056878c0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`04590d00 fffff800`0309952c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`04590d30 fffff800`03099393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`04590e70 fffff800`030a0dd5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`04584560 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeferredReadyThread+0x115


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------

 

[ahcirandombsod]

OK, I don't overclock from Windows. I do BCLK ocing in BIOS. I've been overclocking since 1997. I don't think you understand. I didn't BSOD outside of trying lower voltages while OCing months ago until I added this Bluray burner and changed SATA config from IDE to AHCI. That nerfed the install and I had to repair the startup with my Windows XP install flash drive. The ASUS OCprobe installed with the drivers for the board and will not uninstall. I do not run it.

I already tried lowering clock speeds to stock, as well as voltages. I did a complete reset of the CMOS to accomplish this. It didn't stop the BSODs. This is an RMA'd processor, new motherboard, and RMA'd RAM.

The old driver is for an ancient joystick.

 

[ePeen]

Please, cooperate with us or you will never receive the proper advice.

I understand, you take pride in your overclocking and you believe it is stable, and you know what? It probably is. However, it's so much easier for us to help you diagnose a BSOD, NO LESS a HARDWARE BUGCHECK BSOD, by returning whatever overclocks you have to stock. It really just makes our and your life much easier in this situation, as we can completely and 100% rule out something that can cause so many different things to malfunction.

Also, as I said earlier, when your issue is gone and you're able to use your system as you should be, go right ahead and overclock again.. have a blast, get some extra performance! Just right now, I recommend cooperation so we can help you get up & running.

You also have to understand that the Asus OCprobe utility monitors voltages and other readings in the OS itself. When you're overclocked, this utility and specific piece of software has been sometimes reported to causes extreme misreadings (temperatures, voltages, etc), and even BSODs. I can even attest, and I am sure many other members of the BSOD Team on this forum that we've seen tons of Asus software related BSODs after a member has enabled verifier and of course, Asus was the culprit.

I also believe in general this utility has been reported to cause a boatload of issue regardless of the system being overclocked or not.

We're not telling you this for the good of your health, or telling you this because we're trying to waste your time. We're telling you this because we're trying to help you, and not taking diagnostic steps will unfortunately get your nowhere.

So, with that being said, my suggestion to you is to follow the suggestions given to you, that way you can get your problem solved and use your system as intended

 

[ahcirandombsod]

I'm at 2.66 Ghz with everything at bone stock and memory at XMP settings right now. Everything went along swimmingly until Tuesday when I installed a Pioneer bluray burner and changed to AHCI SATA configuration and repaired the windows startup with the flash drive I use to install windows. The ASUS utility has had every part of it removed except for the EPU part, whatever that is. That component is still there because whenever I try to remove it, my system hardlocks, requiring a forced restart. I cannot remove it. I haven't had a random reboot since yesterday so I'll go play Star Trek Online until I get another one and then make another crashdump to upload. I promise you guys that the crash logs you're looking at stem from months ago when I was trying a vcore less than 1.2875 volts.

Please, cooperate with us or you will never receive the proper advice.

I understand, you take pride in your overclocking and you believe it is stable, and you know what? It probably is. However, it's so much easier for us to help you diagnose a BSOD, NO LESS a HARDWARE BUGCHECK BSOD, by returning whatever overclocks you have to stock. It really just makes our and your life much easier in this situation, as we can completely and 100% rule out something that can cause so many different things to malfunction.

Also, as I said earlier, when your issue is gone and you're able to use your system as you should be, go right ahead and overclock again.. have a blast, get some extra performance! Just right now, I recommend cooperation so we can help you get up & running.

You also have to understand that the Asus OCprobe utility monitors voltages and other readings in the OS itself. When you're overclocked, this utility and specific piece of software has been sometimes reported to causes extreme misreadings (temperatures, voltages, etc), and even BSODs. I can even attest, and I am sure many other members of the BSOD Team on this forum that we've seen tons of Asus software related BSODs after a member has enabled verifier and of course, Asus was the culprit.

I also believe in general this utility has been reported to cause a boatload of issue regardless of the system being overclocked or not.

We're not telling you this for the good of your health, or telling you this because we're trying to waste your time. We're telling you this because we're trying to help you, and not taking diagnostic steps will unfortunately get your nowhere.

So, with that being said, my suggestion to you is to follow the suggestions given to you, that way you can get your problem solved and use your system as intended

 

[ahcirandombsod]

In particular, Debug session time: Mon Feb 6 03:43:17.944 2012 (UTC - 4:00)

Those crashdumps are not applicable to the issue at hand.

ALL attached dumps are x124 hardware bugchecks, so something is going on here regarding your hardware most likely, especially since you've gone ahead reformatted multiple times.

General troubleshooting for this bugcheck, thanks to H2S04.

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

With this being said, I'd recommend first and foremost testing your memory, I don't see any mention of doing so in the OP, so:

Read the following to test your memory for errors.

Drivers that need to be updated:

SaiH0460.sys - Mon Nov 24 05:14:27 2008 (not listed in the carona drivers list, most likely related to Saitek as other drivers minus the "H" in SaiH are labeled Saitek. Possibly a driver for the hub on the keyboard if there is one?" Update here.

For now... and please, read before typing and jumping to conclusions. Bring every component on your system that is overclocked to stop temporarily for diagnostic purposes. With all do respect, I don't care if you believe your Overclock is stable, I don't care if ran Prime95 for 400 hours and got no crashes, an overclock can & will do unthinkable thinks to a system when unstable. So, with that being said, for testing purposes allowing us to help you better, please just bring everything to stock for NOW. When your issue is solved, you're MORE THAN WELCOME to put everything back to what it once was

All 4 crashdumps are WHEA errors reported by your CPU. Two of them state a data write error in your L2 cache of your CPU, while the other two state an issue with the internal timer of your CPU. You had the Intel Linpack benchmark running for three of them at the time, so I assume this was during stress testing while you were checking out your OCing.

There's a couple things I've seen that would cause what appears to be CPU failure displayed by these WHEA error records. First off, if you're using any utilities or software that came with your motherboard, please uninstall them. All OCing should be done straight from the motherboard. Software-based OCing is not preferred, and often the software that runs them is riddled with bugs that actually make WHEA think that the CPU is failing. The other motherboard software I've seen do the same thing in order to perform some gimmick. It's recommended to remove em all. If you wish to OC, you should resort only to doing so with the BIOS.

Very good call, my friend! After checking OP's drivers list, he does in fact have the Asus PCProbe Utility installed.


Dump for reference:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\Windows_NT6_BSOD_jcgriff2\020612-19656-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0301e000 PsLoadedModuleList = 0xfffff800`03263670
Debug session time: Mon Feb  6 03:43:17.944 2012 (UTC - 4:00)
System Uptime: 0 days 0:18:30.866
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007349028, be000000, 800400}

Probably caused by : hardware

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa8007349028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`04590a98 fffff800`03619a3b : 00000000`00000124 00000000`00000000 fffffa80`07349028 00000000`be000000 : nt!KeBugCheckEx
fffff800`04590aa0 fffff800`031ab513 : 00000000`00000001 fffffa80`0734ca10 00000000`00000000 fffffa80`0734ca60 : hal!HalBugCheckSystem+0x1e3
fffff800`04590ae0 fffff800`03619700 : 00000000`00000728 fffffa80`0734ca10 fffff800`04590e70 fffff800`04590e00 : nt!WheaReportHwError+0x263
fffff800`04590b40 fffff800`03619052 : fffffa80`0734ca10 fffff800`04590e70 fffffa80`0734ca10 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`04590c90 fffff800`03618f0d : 00000000`00000008 00000000`00000001 fffff800`04590ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`04590cd0 fffff800`0360ce88 : fffffa80`05642700 fffffa80`056878c0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`04590d00 fffff800`0309952c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`04590d30 fffff800`03099393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`04590e70 fffff800`030a0dd5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`04584560 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeferredReadyThread+0x115


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------

 

[ePeen]

Have you tried safe mode when it comes to removing the EPU part of probe?

And as far as the crash dumps go, that's fine my friend, those were just the only ones you had / had attached, so that's what we're telling you

I will further wait any more dumps.

 

[ahcirandombsod]

Well, I figured out there was a service running that was preventing the successful uninstall. I used Revouninstaller Pro after stopping that service and removed every last vestige of that ASUS crap. I had another crash playing STO a few minutes ago but it just rebooted, no BSOD. Here are my pertinent registry entries for that. Did I do something wrong?

It just crashed again. In the pictured registry entries, what do the values need to be to get a bluescreen error I can take a picture of?

 

[ePeen]

No, a BSOD not being written can be a wide variety of things. See if it crashes again and doesn't write a dump.

 

[ahcirandombsod]

here's the jcgriff output zip

 

[ahcirandombsod]

Ah ha! I finally got a BSOD and it did dump memory! Please help me! I tried to reinstall windows but it kept saying "CD/DVD driver required" or something, even with my bluray burner disconnected from power and sata... The AHCI driver from Asus for X58/ICH10R didn't work and neither did the Marvell 92xx driver. I'd still like to save the present installation if at all possible. Here's the new report. Again, please disregard the BSODs from February; they are a result of stress testing before I figured out that 1.2875 volts is my happy place. The applicable one is the one on 3/23/11 @ ~11:45ish GMT-6. You guys are freakin' awesome and I hope this forum and it's BSOD analyzers live on forever.

 

[ePeen]

Hey buddy

I've taken a look at the latest dump you've attached. The culprit is labeled dxgkrnl.sys, which is the DirectX Graphics Kernel. This is a core Windows file, so I doubt this was actually the cause of the crash, but regardless I'd recommend repairing DirectX. Video card drivers may also be a cause of this, so if you'd like you can go ahead and uninstall / reinstall video card drivers for safe measure. I noticed yours are dated from 2012, so they're recent and most likely up to date, but just for good measure and diagnostic purposes it'd probably be a good idea.

Another thing I would really recommend is enabling Driver Verifier. I have a feeling your issue is related to software if the overclock you're so graciously upholding is not unstable, and the system even crashed at stock.. so it may be hardware as well, but I have a feeling it's a driver.

You can read on how to enable & disable Driver Verifier here:

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

If Driver Verifier finds a fault, it will force a BSOD and generate a detailed dump with the specific driver that caused the crash. Before enabling this though, I would recommend creating a restore point or a back up. 9/10 times the driver that Driver Verifier identifies as the faulting driver is on start up, so that will cause Windows to freeze / crash / BSOD as intended sometimes before actually getting into Windows. In rare cases, this will cause data corruption / loss, just as any other crash / BSOD would.. so for safe measure

Dump file for reference:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\Windows_NT6_BSOD_jcgriff2\032312-22198-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0305b000 PsLoadedModuleList = 0xfffff800`0329f650
Debug session time: Sat Mar 24 00:43:15.319 2012 (UTC - 4:00)
System Uptime: 0 days 1:07:56.583
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 109b, 44051f02, fffff8a008afbcb1}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGSHAREDRESOURCE::`scalar deleting destructor'+87 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 0000000044051f02, Memory contents of the pool block
Arg4: fffff8a008afbcb1, Address of the block of pool being deallocated

Debugging Details:
------------------


BUGCHECK_STR:  0xc2_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003204be9 to fffff800030d7d40

STACK_TEXT:  
fffff880`02d342e8 fffff800`03204be9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`44051f02 : nt!KeBugCheckEx
fffff880`02d342f0 fffff880`05a1b873 : fffff8a0`03c1d110 00000000`00000000 fffff8a0`4b677844 00000000`00000799 : nt!ExDeferredFreePool+0x1201
fffff880`02d343a0 fffff880`05a51230 : fffff8a0`0881aca0 00000000`00000000 fffff8a0`00ef2000 00000000`00000799 : dxgkrnl!DXGSHAREDRESOURCE::`scalar deleting destructor'+0x87
fffff880`02d343d0 fffff880`05a513ac : 00000000`00000001 00000000`00000000 fffff8a0`00000001 fffff8a0`00ef2000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x7ac
fffff880`02d344c0 fffff880`05a50a59 : fffffa80`00000000 fffff8a0`00ef2000 fffff8a0`0263a730 fffff8a0`0881aca0 : dxgkrnl!DXGDEVICE::DestroyResource+0x84
fffff880`02d344f0 fffff880`05a543e7 : fffff900`c00fc79c fffff8a0`0263a730 fffffa80`09d0b918 fffffa80`09d0bf11 : dxgkrnl!DXGDEVICE::TerminateAllocations+0x231
fffff880`02d34540 fffff880`05a5b8c6 : fffff8a0`00ef2000 fffff880`02d34870 00000000`00000000 0000057f`f62f5270 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x93
fffff880`02d345d0 fffff960`0070682d : fffff900`c00fc020 00000000`00000001 fffff880`02d34cd0 00000000`00000001 : dxgkrnl!DxgkCddEnable+0x7ea
fffff880`02d34920 fffff960`00705ce1 : ffffffff`00000004 ffffffff`fffd74f6 00000000`00000002 00000000`00000000 : cdd!CreateAndEnableDevice+0x1e1
fffff880`02d349b0 fffff800`03371f7a : 00000000`01e9bd21 fffffa80`09edc740 00000000`00000080 fffffa80`09d60a90 : cdd!PresentWorkerThread+0x975
fffff880`02d34d40 fffff800`030c89c6 : fffff880`033d5180 fffffa80`09edc740 fffff880`033dffc0 fffff880`01643cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`02d34d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DXGSHAREDRESOURCE::`scalar deleting destructor'+87
fffff880`05a1b873 488b7350        mov     rsi,qword ptr [rbx+50h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgkrnl!DXGSHAREDRESOURCE::`scalar deleting destructor'+87

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa

FAILURE_BUCKET_ID:  X64_0xc2_7_dxgkrnl!DXGSHAREDRESOURCE::_scalar_deleting_destructor_+87

BUCKET_ID:  X64_0xc2_7_dxgkrnl!DXGSHAREDRESOURCE::_scalar_deleting_destructor_+87

Followup: MachineOwner
---------

 

[ahcirandombsod]

I nuked and am reinstalling windows. The dump came at stock speeds and voltages. Hopefully this goes away. I updated the driver to 295.xx whql from 295.xx beta and that's when I got a bsod instead of just a reboot with no dump.

edit

I went out and got a 2TB seagate 5900 RPM/64MB cache drive and used it to backup all my steam stuff, music, movies, and crap before reformatting and reinstalling Windows. I got a BSOD while copying 200GB of steam information to C:/Program Files x86/Steam and installing .net 4 via windows update. It did a successful BSOD and dump, here are the results. My perfmon report is strange. I have drivers installed for everything that I use and it says my CPU is a weakling. Granted, it's stock right now but it's still a D0 i7 920...

Now I'm going to try Driver Verifier, thanks for that tip ePeen. If it BSODs during that I'm going to try reverting my GPU driver back to a known good driver from January.

 

[ahcirandombsod]

I accidentally edited the new debug info into the above post, please help me ePeen. I'll totally paypal you some money if you can help me get this figured out.

 

[ePeen]

Hi my friend. In the attached dump file above, that's not verifier enabled, it's the same dump we've been through earlier (the dxgkrnl one).

Once you get a new verifier enabled dump, please attach it and I'll take a look

 

[ahcirandombsod]

I'm quite certain that the issue stems from the last two nvidia WHQL drivers. I used Revo Uninstaller Pro to remove the latest one completely and then I installed the last beta before the WHQLs. I haven't had a BSOD since. Star Trek Online crashed, but Battlefield 3 doesn't and Windows as a whole stays up. I will keep a close eye on it. Thank you very much for your assistance.

 

[ePeen]

My pleasure, keep me updated.

 

[ahcirandombsod]

Hey ePeen, I am getting crashes in Star Trek Online but it isn't taking Windows with it so that's progress. I finally got around to running Memtest86+ v 4.20 and my RAM failed on 2 out of three sticks so that's awesome because my Corsair warranty expires in exactly 29 days!

 

[ePeen]

Very cool! Replace that RAM!