Windows 10: Random BSOD: WHEA_UNCORRECTABLE_ERROR 124 arg1: 0

Keep randomly crashing while doing nothing as well as while playing games. No overclocks. All drivers up to date. Opening the dump file with windbg gives me errors that it can't find the symbols for ntoskrnl even though I have my path set to: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols


The bugcheck is as follows when I run !analyze -v :

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


However I am super new to looking at these dumps so I don't know if I might be missing something because of the missing symbols:



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


Loading Dump File [C:\Windows\Minidump\061819-4515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Error: Empty Path.
WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

Executable search path is:
WARNING: Whitespace at end of path element
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE_TRANSITION ***
*** ***
*************************************************************************
Windows 10 Kernel Version 17763 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff802`2f016000 PsLoadedModuleList = 0xfffff802`2f431670
Debug session time: Tue Jun 18 22:35:31.624 2019 (UTC - 4:00)
System Uptime: 0 days 0:05:40.416
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE_TRANSITION ***
*** ***
*************************************************************************
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
......

************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
For analysis of this file, run !analyze -v

:)

 

WHEA_UNCORRECTABLE_ERROR (124) BSOD

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

 

WHEA_UNCORRECTABLE_ERROR 124 but no bsod


Same like this:
WHEA_UNCORRECTABLE_ERROR 124 but no bsod - Windows 10 Forums

Code:

Code:

0x00000124:    [SPECIAL] WHEA_UNCORRECTABLE_ERROR (2018-02-19 14:36:04) [Windows 10]    CAUSED BY:     AuthenticAMD_PROCESSOR_BUS_PRV        WHEA Notify:   Machine Check Exception       Type:     BUS error       Error:    BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)    PROCESS:       System

"BUS OBS Error": Observing error. Usually caused by hardware components, Mainboard or chipset drivers.

 

WHEA_UNCORRECTABLE_ERROR (124) BSOD

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:

Code: 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[/quote]