Bugcheck 124 - Hal.dll - Need a read on what is failing

[FuzzyDice]

I know this is a hardware failure based on a little research. This machine used to be stable but crashes about every 6 - 48 hours.

I have replaced a PSU (the fan seemed to be going anyway), updated the Bios, added a case fan and reset my bios so that over clocking is off (I think it got turned on during a previous bios flash).

I unfortuantely don't have the time to read up on reading bluescreen data - Thanks for the help.

I'm hoping something indicates a processor failure as my hunch is the now reset OC setting may have baked the stock fan thermal compound but I really don't want to waste time and money at it on a bad hunch,

 

[Arc]

[COLOR=Red]BugCheck 124[/COLOR], {[COLOR=Red][B]0[/B][/COLOR], fffffa800fdd1028, be000000, 800400}

Probably caused by : GenuineIntel

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

0x124 is WHEA_UNCORRECTABLE_ERROR. WHEA means Windows Hardware Error Architecture. It elaborates as ....

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.

So it is a hardware level failure. When the parameter 1 is zero, it means ....

Arg1: 0000000000000000, Machine Check Exception
​

It means that the Processor reported a hardware error. And the source of occurrence of the issue is un-traced. It may be anything and everything within the computer's environment.
And following the second parameter becomes meaningless here. It just gives a hint of the processor core where the error was traced. As in your case ....

===============================================================================
Common Platform Error Record @ fffffa800fdd1028
-------------------------------------------------------------------------------
Record Id     : 01d176258e7ce3c5
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/5/2016 6:37:20 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000006

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

Local APIC Id : 0x0000000000000006
CPU Id        : c3 06 03 00 00 08 10 06 - bf fb fa 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  @ fffffa800fdd1240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800fdd1138
Section       @ fffffa800fdd12c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
[COLOR=Red]Severity      : Fatal[/COLOR]

[COLOR=Red]Error         : Internal timer (Proc 6 Bank 4)[/COLOR]
  Status      : 0xbe00000000800400
  Address     : 0x0000000057785b4b
  Misc.       : 0x0000000057785b4b

It will look like the processor itself is causing the issue. But that will be a very misleading information. It is not a processor failure, it is a failure reported by the processor (which may be a processor failure, or any other hardware related issue as well.)

The best way to troubleshoot this issue is to follow http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696. It is lengthy and time consuming process, but it will narrow down the issue.