BCCode 0x124 WHEA_UNCORRECTABLE_ERROR

[Aikouka]

I built myself a new Haswell machine back in June, and by the end of the month, it had already BSOD'd with the stop code 124. Using Blue Screen Viewer, I saw that the issue was in hal.dll, and after some research on it, I was never able to come up with a conclusive path forward. I left it alone for a bit, and about a month later it BSOD'd again. Since then, it has become a bit more frequent, and it typically occurs when the machine is sitting idle. The BSOD is always the same: BCCode 0x124 WHEA_UNCORRECTABLE ERROR on hal.dll+2d965. I've run memory tests using MemTest86+ and CPU tests using Prime95 and the Intel Burn Test, but I've come up with no issues.

I've been rather curious if the problem might be power related. I have noticed that HWInfo reports my 3.3V and 5V values to be rather nominal, but my 12V numbers like to go a bit lower than I'm used to... around 11.5V. The ATX spec allows for a 5% drop (i.e. 11.4V), but it still seems undesirable. Although, I do know that software-based voltage reporting isn't always considered that reliable, so I really ought to get a multimeter out and try it.

Ultimately, I was wondering if anyone might have any ideas on a good path forward?

 

[Ketchup]

The last time I saw a 12v line go under 12 was probably the Windows 98/ME era, and I was overclocked at the time. Every 12v number I have seen since then is over 12. I don't know that I would be comfortable with that number, whether or not is was causing your issue.

Onto your error, have you seen this page yet?

http://answers.microsoft.com/en-us/...ll-error/bff7bb96-4b9d-4448-ac4b-6b21dcea8cd7

Also, what BIOS are your running on your motherboard?

 

[Aikouka]

Ah, I meant to post my hardware just in case someone wanted to see it:

CPU: i7-4700K
MBO: ASUS Maximus VI Formula
RAM: 16GB (2x8GB) G.Skill Trident X DDR3-2400 ( F3-2400C10D-16GTX )
GPU: 2x EVGA GeForce GTX 680 2GB (02G-P4-2680-KR)
PSU: Corsair AX860
SSD: Samsung 840 Pro 256GB
SSD: Crucial M4 256GB
HDD: 2x Hitachi 2TB (HDS723020BLA642)
ODD: Pioneer BD-RW (BDR-206)

The Crucial M4, Hitachi HDDs, Pioneer ODD, and one of the GPUs are all carry overs from my previous machine, which I don't think ever had a BSOD. I originally built this machine with a single GPU and an ASRock Z87 Extreme4 motherboard, and I still BSOD'd prior to adding the second GPU. I'd kind of like to stress that since I purchased it used and I didn't get to test it much. I've also had a BSOD with my memory at non-OC'd (i.e. XMP was not enabled) speeds.

The last time I saw a 12v line go under 12 was probably the Windows 98/ME era, and I was overclocked at the time. Every 12v number I have seen since then is over 12. I don't know that I would be comfortable with that number, whether or not is was causing your issue.

I want to be fair and make sure to stress that I was using software to check those voltages, and they may not have been reported correctly. I switched from HWiNFO64 (won't even show the voltages on my ASUS board) to CPUID HWMonitor, and the voltages look a lot better. I'm seeing the following: 5V = 5.04-5.08, 3.3V = 3.344-3.36, 12V = 12.096 (no variation reported).

Onto your error, have you seen this page yet?

http://answers.microsoft.com/en-us/...ll-error/bff7bb96-4b9d-4448-ac4b-6b21dcea8cd7

Yep, I've seen that page. Unfortunately, it's like a lot of the other pages in that it's some piece of hardware, but it's hard to definitively determine what. I believe that one guy with the same error actually had his CPU getting too hot or something like that. My PC will BSOD whether I'm sitting at it browsing the web or its just idling while I'm at work (temps are about 30C).

Also, what BIOS are your running on your motherboard?

I am currently running the latest: 0714.

 

[Ketchup]

Cool, glad the volts are OK. If you hadn't mentioned the other program I was going to select a volt meter, which will probably give you even more accurate numbers (at least they used to).

Is this the water cooled rig?
Does it ever crate a dump? That might make is easier to determine the issue.

Also, have you tried a fresh install since the problem started coming up? Any more I hate fresh installs, but after a length of time with something like that, I might be led to try one.

Is anything overclocked when you receive this error?

Honestly, I am tempted to suspect the RAM on this one. Do you have any other DDR3 you can test with? If not, you can run one stick at a time. Memtest can catch issues, but I have seen people in this forum have memory issues, but they still passed the test.

One other suspicion would be a program you use that runs in the background, but hasn't been updated in a while.

 

[denis280]

Honestly, I am tempted to suspect the RAM on this one. Do you have any other DDR3 you can test with? If not, you can run one stick at a time. Memtest can catch issues, but I have seen people in this forum have memory issues, but they still passed the test.

this is what i was thinking to.

 

[Ketchup]

this is what i was thinking to.

So we win or die together!!! lol.

 

[denis280]

So we win or die together!!! lol.

😱Lol.Just got one rig last week doing the same thing.double check the memory and all fine.took mine out.put them in and bingo.and then put the ram in my rig.and bsod😵but they pass all test.weird

 

[Ketchup]

😱Lol.Just got one rig last week doing the same thing.double check the memory and all fine.took mine out.put them in and bingo.and then put the ram in my rig.and bsod😵but they pass all test.weird

I still don't understand the difference there, but we have both seen it happen. What is Windows doing that something like Memtest wouldn't?

Aikouka, not trying to derail your thread. Let us know if you find anything on those memory sticks.

 

[Aikouka]

Cool, glad the volts are OK. If you hadn't mentioned the other program I was going to select a volt meter, which will probably give you even more accurate numbers (at least they used to).

I went and hooked a multimeter up, and the voltages look pretty good.

Is this the water cooled rig?

Yes.

Does it ever crate a dump? That might make is easier to determine the issue.

Yep. There's not too much to it though...

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Wed 8/21/2013 8:01:13  AM GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\082113-12984-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=hal.dll"]hal.dll[/URL][/COLOR][/SIZE][/FONT]  (hal+0x2D965) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA800E532028, 0xBE000000,  0x100110A)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+WHEA_UNCORRECTABLE_ERROR"]WHEA_UNCORRECTABLE_ERROR[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\hal.dll
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft® Windows® Operating System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: Hardware  Abstraction Layer DLL
Bug check description: This bug check indicates that a  fatal hardware error has occurred. This bug check uses the error data that is  provided by the Windows Hardware Error Architecture (WHEA). 
This is likely  to be caused by a hardware problem problem. This problem might be caused by a  thermal issue. 
The crash took place in a standard Microsoft module. Your  system configuration may be incorrect. Possibly this problem is caused by  another driver on your system that cannot be identified at this time. [/COLOR][/SIZE][/FONT]

Also, have you tried a fresh install since the problem started coming up? Any more I hate fresh installs, but after a length of time with something like that, I might be led to try one.

I thought about it, but I wasn't sure if I wanted to go that far... yet.

Is anything overclocked when you receive this error?

The memory has been in the past, but it wasn't when I got the last one.

Honestly, I am tempted to suspect the RAM on this one. Do you have any other DDR3 you can test with? If not, you can run one stick at a time. Memtest can catch issues, but I have seen people in this forum have memory issues, but they still passed the test.

I tossed in some of the RAM that I used with my old Sandy Bridge system. The only problem is that this is so random, that it may happen in three seconds or three weeks.

One other suspicion would be a program you use that runs in the background, but hasn't been updated in a while.

Does Windows 8 count as something that runs in the background? 😉 The only big differences in software in this build are Windows 8 and Office 2013 instead of Windows 7 and Office 2012.

 

[Ketchup]

Two last questions from me for the moment, then we may have to see how the memory from the "OLD" Sandy Bridge turns out. When these dumps occur, has the computer been running for a while? My thought is if so, the memory on the second stick may be getting more access, revealing a bad spot on the stick.

Also, do you plug in/turn on anything occasionally that has a driver?

 

[Aikouka]

When these dumps occur, has the computer been running for a while?

It's pretty random. The crash dates are... 6/30 @ 4:45AM, 7/24 @ 8:05 AM, 8/6 @ 6:22PM (only one that has occurred while I was on the machine), 8/9 @ 12:58AM, 8/21 @ 8:01AM. My PC was also turned off from 8/12 to 8/18 for a rebuild, so those latter two are a lot closer in regard to the actual run time between each.

Also, do you plug in/turn on anything occasionally that has a driver?

Hmm the only things that I can think of would be my phone, tablet and USB flash memory (USB 2 and USB 3).

 

[denis280]

I tossed in some of the RAM that I used with my old Sandy Bridge system. The only problem is that this is so random, that it may happen in three seconds or three weeks.

Lets see what go on with this.

USB flash memory (USB 2 and USB 3).

and i suspect this.

 

[Aikouka]

and i suspect this.

I've been using those memory sticks for quite awhile though... probably a few years for that USB 2 SanDisk Cruzer Micro. Also, I don't use them that often. It's only been over the past few days that I've been using them load up some tests to run on an ailing laptop that doesn't have an optical drive.

 

[Aikouka]

I crashed a little bit ago while playing a game with the same error. Here's the detailed info from WinDBG:

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009d0968 fffff803`9d844965 : 00000000`00000124 00000000`00000000 fffffa80`0d386028 00000000`be000000 : nt!KeBugCheckEx
fffff880`009d0970 fffff803`9d9e3ef9 : 00000000`00000001 fffffa80`0cb87400 00000000`00000000 fffffa80`0d386028 : hal!HalBugCheckSystem+0xf9
fffff880`009d09b0 fffff803`9d844703 : 00000000`00000728 00000000`00000001 fffff880`009d0b10 fffffa80`0cb87400 : nt!WheaReportHwError+0x249
fffff880`009d0a10 fffff803`9d844020 : 00000000`00000010 fffffa80`0cb87400 fffff880`009d0bc8 fffffa80`0cb87400 : hal!HalpMcaReportError+0x53
fffff880`009d0b70 fffff803`9d843f1b : fffffa80`0caeb6c0 00000000`00000001 00000000`00000001 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`009d0bc0 fffff803`9d843d78 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`009d0c00 fffff803`9d844f0f : fffffa80`0caeb6c0 fffff880`009d0e30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`009d0c30 fffff803`9d8db77b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009d0c60 fffff803`9d8db52e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`009d0da0 fffff803`9d8d74df : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
fffff880`0e5547c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchStMxCsr+0x90


STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME:  GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
Followup: MachineOwner

Here are a few older ones...

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: fffffa800e532028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  CINEBENCH Wind

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0154d968 fffff801`02e36965 : 00000000`00000124 00000000`00000000 fffffa80`0e532028 00000000`be000000 : nt!KeBugCheckEx
fffff880`0154d970 fffff801`02fd5ef9 : 00000000`00000001 fffffa80`0cb87850 00000000`00000000 fffffa80`0e532028 : hal!HalBugCheckSystem+0xf9
fffff880`0154d9b0 fffff801`02e36703 : 00000000`00000728 00000000`00000004 fffff880`0154db10 fffffa80`0cb87850 : nt!WheaReportHwError+0x249
fffff880`0154da10 fffff801`02e36020 : 00000000`00000010 fffffa80`0cb87850 fffff880`0154dbc8 fffffa80`0cb87850 : hal!HalpMcaReportError+0x53
fffff880`0154db70 fffff801`02e35f1b : fffffa80`0caece00 00000000`00000001 00000000`00000004 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`0154dbc0 fffff801`02e35d78 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`0154dc00 fffff801`02e36f0f : fffffa80`0caece00 fffff880`0154de30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`0154dc30 fffff801`02ecd77b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0154dc60 fffff801`02ecd52e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`0154dda0 00000001`4002cfa3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
00000000`0301b140 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`4002cfa3


STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME:  GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
Followup: MachineOwner

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: fffffa800e542028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f5968 fffff803`a6c42965 : 00000000`00000124 00000000`00000000 fffffa80`0e542028 00000000`be000000 : nt!KeBugCheckEx
fffff880`009f5970 fffff803`a6de1ef9 : 00000000`00000001 fffffa80`0cb88400 00000000`00000000 fffffa80`0e542028 : hal!HalBugCheckSystem+0xf9
fffff880`009f59b0 fffff803`a6c42703 : 00000000`00000728 00000000`00000001 fffff880`009f5b10 fffffa80`0cb88400 : nt!WheaReportHwError+0x249
fffff880`009f5a10 fffff803`a6c42020 : 00000000`00000010 fffffa80`0cb88400 fffff880`009f5bc8 fffffa80`0cb88400 : hal!HalpMcaReportError+0x53
fffff880`009f5b70 fffff803`a6c41f1b : fffffa80`0caecbf0 00000000`00000001 00000000`00000001 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`009f5bc0 fffff803`a6c41d78 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`009f5c00 fffff803`a6c42f0f : fffffa80`0caecbf0 fffff880`009f5e30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`009f5c30 fffff803`a6cd977b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f5c60 fffff803`a6cd952e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`009f5da0 00000000`696c3d70 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
00000000`002cb51c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x696c3d70

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME:  GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
Followup: MachineOwner

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: fffffa800d89a028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0126e968 fffff803`8fc2f965 : 00000000`00000124 00000000`00000000 fffffa80`0d89a028 00000000`be000000 : nt!KeBugCheckEx
fffff880`0126e970 fffff803`8fdceef9 : 00000000`00000001 fffffa80`0cb88570 00000000`00000000 fffffa80`0d89a028 : hal!HalBugCheckSystem+0xf9
fffff880`0126e9b0 fffff803`8fc2f703 : 00000000`00000728 00000000`00000002 fffff880`0126eb10 fffffa80`0cb88570 : nt!WheaReportHwError+0x249
fffff880`0126ea10 fffff803`8fc2f020 : 00000000`00000010 fffffa80`0cb88570 fffff880`0126ebc8 fffffa80`0cb88570 : hal!HalpMcaReportError+0x53
fffff880`0126eb70 fffff803`8fc2ef1b : fffffa80`0caecca0 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`0126ebc0 fffff803`8fc2ed78 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`0126ec00 fffff803`8fc2ff0f : fffffa80`0caecca0 fffff880`0126ee30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`0126ec30 fffff803`8fcc677b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0126ec60 fffff803`8fcc652e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`0126eda0 000007fc`260210b0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
000000ba`153df368 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fc`260210b0

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME:  GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
Followup: MachineOwner

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: fffffa800d555028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff802`e78b2a28 fffff802`e7a36965 : 00000000`00000124 00000000`00000000 fffffa80`0d555028 00000000`be000000 : nt!KeBugCheckEx
fffff802`e78b2a30 fffff802`e7bd5ef9 : 00000000`00000001 fffffa80`0cefeaa0 00000000`00000000 fffffa80`0d555028 : hal!HalBugCheckSystem+0xf9
fffff802`e78b2a70 fffff802`e7a36703 : 00000000`00000728 00000000`00000000 fffff802`e78b2bd0 fffffa80`0cefeaa0 : nt!WheaReportHwError+0x249
fffff802`e78b2ad0 fffff802`e7a36020 : 00000000`00000010 fffffa80`0cefeaa0 fffff802`e78b2c88 fffffa80`0cefeaa0 : hal!HalpMcaReportError+0x53
fffff802`e78b2c30 fffff802`e7a35f1b : fffffa80`0caf0b40 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff802`e78b2c80 fffff802`e7a35d78 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff802`e78b2cc0 fffff802`e7a36f0f : fffffa80`0caf0b40 fffff802`e78b2ef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff802`e78b2cf0 fffff802`e7acd77b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff802`e78b2d20 fffff802`e7acd52e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff802`e78b2e60 fffff880`04a043a2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
fffff802`e78a6888 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!C1Halt+0x2

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME:  GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
Followup: MachineOwner

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: fffffa800cf81028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  FlashPlayerPlu

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`014e1968 fffff800`64f95965 : 00000000`00000124 00000000`00000000 fffffa80`0cf81028 00000000`be000000 : nt!KeBugCheckEx
fffff880`014e1970 fffff800`6497cca9 : 00000000`00000001 fffffa80`0ca986e0 00000000`00000000 fffffa80`0cf81028 : hal!HalBugCheckSystem+0xf9
fffff880`014e19b0 fffff800`64f95703 : 00000000`00000728 00000000`00000003 fffff880`014e1b10 fffffa80`0ca986e0 : nt!WheaReportHwError+0x249
fffff880`014e1a10 fffff800`64f95020 : 00000000`00000010 fffffa80`0ca986e0 fffff880`014e1bc8 fffffa80`0ca986e0 : hal!HalpMcaReportError+0x53
fffff880`014e1b70 fffff800`64f94f1b : fffffa80`0c7e8d50 00000000`00000001 00000000`00000003 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`014e1bc0 fffff800`64f94d78 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`014e1c00 fffff800`64f95f0f : fffffa80`0c7e8d50 fffff880`014e1e30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`014e1c30 fffff800`6487477b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`014e1c60 fffff800`6487452e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`014e1da0 00000000`6542d24e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
00000000`009ce52c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6542d24e

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME:  GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
Followup: MachineOwner

I see the IntelPPM in the second to last one, and I recall seeing another user have this problem. He disabled the C1 state and some of the other low-power states to "fix" it. I'm not too terribly keen on this. I want it to work properly, not be stuck with some silly work-around.

 

[bueffel]

Hello, I registered here just because I encounterd a similar problem: A new system (i7 4770, ASUS H87M-Pro, Corsair 2x8GB DDR1600). No OC. Running great so far, but I once got a BSOD while browsing that irritates me.
The dump examination showed similar content as with Aikoukas postings : 0x0124 BSDO, L2_Cache_Error. (With Aikouka, its just Cache, not L2, but all cache memory L1-L2 on Haswell are in the CPU, right?).
A L2 Cache Error to me is a hint to a problem with the CPU...

Aikouka, can you give an update on the status of your problem ? Any solution?

bueffel

 

[Nec_V20]

HAL errors are indicative of either a hardware issue or a kernel driver issue.

The problem is that the only reporting which can be done is from the upper level process which was affected by the real underlying cause which does not report errors.

I cannot see any obvious issue with the hardware you have and biting the bullet with regard to a clean installation (after backing up the present one) would be indicated.

Sure we can go back and forward on possible causes such as RAM however a clean install will tell you one way or another whether you actually do have a hardware issue.

As with all Haswell boards, it goes without saying that you should have the latest BIOS for your motherboard installed.