BSOD on wake-up error 0x00000124, driver hal.dll, address ntoskrnl.exe

Generous experts,

I am getting somewhat random, though more often on "wake-up" BSOD. It seems that it may be related to the cpu, as the event view states:

A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor ID: 2

The details view of this entry contains further information.

I am moderately tech savvy, but this is beyond my skill level. I have searched this forum and web for a solution, and did not find any that were quite close enough - at least by my viewing.

Any suggestions would be very much appreciated

Thank you!

Code:

BugCheck 124, {0, fffffa80078c6028, bf800000, 124}

You are having 0x124 bugchecks which indicate a fatal hardware error has occurred.

Code:

2: kd> !errrec fffffa80078c6028
===============================================================================
Common Platform Error Record @ fffffa80078c6028
-------------------------------------------------------------------------------
Record Id     : 01cf84f0d193612a
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/10/2014 21:15:27 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80078c60a8
Section       @ fffffa80078c6180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80078c60f0
Section       @ fffffa80078c6240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : c3 06 03 00 00 08 10 02 - bf fb da 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa80078c6240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80078c6138
Section       @ fffffa80078c62c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL0_WR_ERR (Proc 2 Bank 1)
  Status      : 0xbf80000000000124
  Address     : 0x000000021b887200
  Misc.       : 0x0000000000000086

The Machine Check Exception indicates that the CPU has found a fault with the a piece of hardware and has bugchecked. We cannot really identify the cause without proper troubleshooting stress tests.

The 2nd parameter is the address that contains the WHEA (Windows Hardware Error Architecture) record.
Its a Level 0 cache write error.

There's only so much we can do until it comes down to a faulty processor, lets begin.

Stress test your CPU with Prime95

I recommend running Prime95 for around 2 hours

   Warning

As with most stress tests your component's temperature will rapidly increase.
It is advised that you download a temperature monitoring program like HWmonitor
Keep an eye on your temperatures and stop the tests if it starts to overheat

Stress test your graphics card with Furmark

I recommend running it for around 30 minutes

   Warning

Furmark will increase the temperature of your GPU rapidly so keep and eye on your temperatures

Memtest86 will test your RAM

   Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

Run a Disk Check to scan for errors

   Note

Afterwards go into an Elevated Command Prompt (Run as administrator) and type in sfc /scannow
If it finds errors reboot and run the scan two more times

Run SeaTools to see if your HDD or SSD is failing

Try removing the CMOS battery then putting it back in to clear the BIOS of any improper settings.
Make sure you keep an eye on the temperatures.

Remove these programs...

Code:

Start Menu\Programs\ASUS\AI Suite 3	Public:Start Menu\Programs\ASUS\AI Suite 3	Public
Start Menu\Programs\ASUS\ROG RAMDisk	Public:Start Menu\Programs\ASUS\ROG RAMDisk	Public
Start Menu\Programs\Avast	Public:Start Menu\Programs\Avast	Public
Start Menu\Programs\Microsoft Silverlight	Public:Start Menu\Programs\Microsoft Silverlight	Public
Start Menu\Programs\ASUS\PC Diagnostics	Homebuilt\David:Start Menu\Programs\ASUS\PC Diagnostics	Homebuilt\David

Especially the AI suite software which can cause 0x124 errors.

Use Avast's removal tool then replace it with MSE and Malwarebytes.

Microsoft Security Essentials - Microsoft Windows

Malwarebytes | Free Anti-Malware & Internet Security Software

   Tip

Make sure you don't enable the free trial of malwarebytes pro, deselect the option when prompted.

Post back the results.

I get the BSOD after only a minute or two of running furmark. Not sure where the furmark log is stored, so I don't know at what temp the graphics GPU fails, but it was not at its max. Other than reverting to a previous driver, or perhaps an new PSU, am not sure what else I can do. I have also uninstalled the 3 asus programs, but not silverlight or avast. Is it possible they are interacting with the GPU? BTW - the system was relatively stable for the last two months - the problem just started, even though I had not made any major changes.

Thank you for your help!

Do you have another GPU to test?
It looks promising that your GPU is failing which can happen at any time.

I replaced the gpu with an old nvidia 9500 i had around (after uninstalling the 660 and all its drivers). It made no difference - the systems crashed twice while installing the drivers for the 9500. Once that finally was going, I ran furmark (somewhat comical, as it would barely run) and the system crashed after ~2 minutes. BUT the good news is that when I re-installed the 660ti, I also, as instructed in your original post, removed and re installed the BIOS battery. That, so far, seems to have made things MUCH better. I ran, and passed, the 15 minute furmark benchmark AND was able to move, shrink, grow etc the furmark window as it was running. The latter always caused the system to crash. I will not claim victory yet, and will wait to see if the systems can wake up from sleep without crashing, but I have my fingers crossed. My current theory is that the AIsuite changed the BIOS to some unstable setting...

Thank you again for your help - I will check back in tomorrow.

Excellent news so far :)
Any more issues let me know.

Well, seems like it's fixed. I ran these tests:
1. Memory test (ran before posting): ran for 8 hours, no errors
2. Processor stress test: ran for 1.5 hours, no failure
3, Gpu stress test: Only ran for ~2 minutes, before BSOD
4. Removed Asus utilities: Still had BSOD

These are the changes I made to fix the problem (in order). I am not sure which one was the actual cure (removing ASUS utilities was not), though I suspect it was the BIOS reset:

1. Removed AIsuite III (not easy- it took three tries and an un-official removal tool), Asus ROG Ram disk and ASUS pc diagnostics
2. Uninstalled 660Ti GPu AND all drivers at device manager
3. Removed and re-installed BIOS battery (well, installed and then removed different graphics card first)
4. Installed 660Ti and let windows find driver (note - windows installed 335.23, Nvidia wants me to upgrade the driver to 337.88, which I have not done yet)

Thank you to this forum and Thedoctor44 for your considerable help!

No problem :)
Glad everything is fixed.