WHEA_UNCORRECTABLE_ERROR (124) BSOD

[RoboX]

Intel Xeon on P55 Motherboard (no server), Bios setting at default, and with ram tested ok with memtest. Random freezes in idle, after 1 minute from the boot, in windows and in the recovery section of the dvd windows, without HD, so I think is not a software problem).
So I disable all cpu setting like c1e, eist, green power, control phase etc... and I not have freeze, but when I do a linx test I have this BSOD:

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe0007f425028, fa000000, 400405}

Probably caused by : GenuineIntel

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

1: 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: ffffe0007f425028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.



DUMP_TYPE:  1

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe0007f425028

BUGCHECK_P3: fa000000

BUGCHECK_P4: 400405

BUGCHECK_STR:  0x124_GenuineIntel

CPU_COUNT: 4

CPU_MHZ: 966

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 1e

CPU_STEPPING: 5

CPU_MICROCODE: 6,1e,5,0 (F,M,S,R)  SIG: 5'00000000 (cache) 5'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  linpack_xeon64

CURRENT_IRQL:  f

ANALYSIS_SESSION_HOST:  HM

ANALYSIS_SESSION_TIME:  02-15-2016 01:43:11.0463

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT: 
ffffd000`d5517cf8 fffff803`de1e1213 : 00000000`00000124 00000000`00000000 ffffe000`7f425028 00000000`fa000000 : nt!KeBugCheckEx
ffffd000`d5517d00 fffff803`ddbdae4d : 00000000`00000001 ffffe000`7b5e9160 ffffe000`7b5e9160 ffffe000`7f425028 : hal!HalBugCheckSystem+0xcf
ffffd000`d5517d40 fffff803`de1e16a0 : 00000000`00000728 00000000`00000001 ffffd000`d5518130 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd000`d5517da0 fffff803`de1e1a0d : ffffe000`00000010 ffffe000`7b5e9160 ffffd000`d5517f48 ffffe000`7b5e9160 : hal!HalpMcaReportError+0x50
ffffd000`d5517ef0 fffff803`de1e18f8 : ffffe000`7b5e8bb0 00000000`00000001 00000000`00000001 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd000`d5517f40 fffff803`de1e1b42 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd000`d5517f80 fffff803`de1e1ccf : ffffe000`7b5e8bb0 ffffd000`d55181b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd000`d5517fb0 fffff803`ddb75dbb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd000`d5517fe0 fffff803`ddb75b71 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd000`d5518120 00000001`402cc511 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
00000000`0263efe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`402cc511


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  a46f769f9bb88b377fa260529f59dcef5f50e990

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  29312a4267facee58b38f6e4355aa4f81a0aa678

THREAD_SHA1_HASH_MOD:  dcad533a74a3db89beeba48522fb4c242f2efae0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION: 

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE

PRIMARY_PROBLEM_CLASS:  0x124_GenuineIntel_PROCESSOR_MAE

TARGET_TIME:  2016-02-15T00:08:42.000Z

OSBUILD:  9600

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

OSEDITION:  Windows 8.1 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-12-30 15:49:56

BUILDDATESTAMP_STR:  151230-0600

BUILDLAB_STR:  winblue_ltsb

BUILDOSVER_STR:  6.3.9600.18185.amd64fre.winblue_ltsb.151230-0600

ANALYSIS_SESSION_ELAPSED_TIME: 184a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_mae

FAILURE_ID_HASH:  {7c95de0c-286c-8226-45c2-422b4de101d6}

Followup:     MachineOwner

 

[P4-630]

Any overclocking?
If so reset the BIOS to default.

 

[RoboX]

no OC, bios at default, also clear cmos

 

[Caring1]

What model CPU and make and model number of Motherboard.
Sounds like a CPU error.
Is it on the compatibility list?

 

[stevorob]

Xeon's should go into p55 boards without a problem, so shouldn't be compatibility... but in any case, which P55 board are you using, and what model Xeon?

LinX stress tests, right? If so, how's the temps when you run LinX? Could be overheating and causing the stability issues, causing your bsod.

 

[RoboX]

X3480....is it possible that is a problem of the mainboard? (Asus Maximus III extreme)

 

[dorsetknob]

Not on the Official CPU supported list
https://www.asus.com/Motherboards/MAXIMUS_III_EXTREME/HelpDesk_CPU/

It may work or not
have you actualy had this CPU running in this Motherboard or is this a "upgrade" CPU Attempt ?

 

[brandonwh64]

BSOD 124 (When OCing) usually means needs more VCORE.

 

[stevorob]

X3480....is it possible that is a problem of the mainboard? (Asus Maximus III extreme)

Xeon's aren't typically listed on a vendor's "officially supported CPUs" list, however, they will still work in alot of boards. It's a very 'do at your own risk' sort of deal. I have a Xeon X3440 running in an Asus p7p55d pro, but it's not listed on their supported list, but still runs well and I haven't seen any issues.

It's likely that if you're overclocking, temps might be an issue, or as @brandonwh64 said above, you just don't have enough voltage for your OC, and you'll need more vcore on your CPU.

 

[dorsetknob]

Op might look at a microcode injection for the bios to ensure CPU compatability
Thats what people used to do to get Xeon 771 to 775 motherboard compatibility