Question Intel 12700k WHEA_UNCORRECTABLE Errors

Dec 13, 2022
1
0
10
Hello everyone,
I recently purchased a 12700k along with an ASUS TUF Gaming Z690 Plus D4 motherboard. BIOS has been updated to the latest version 2204, Windows 10 and all updates were freshly installed on a formatted SSD, and then standard chipset, audio, LAN drivers were installed from the ASUS website. I also have a TUF Gaming 6800XT and latest AMD drivers were installed for the GPU. All BIOS settings are set to default except ASUS MCE is off (Disabled, Enforce Power Limits). I also have a Corsair H100 Elite AIO cooler. My RAM kit is Corsair Vengeance 2x8gb 16-18-18-36 3200MHz, but running with XMP off for testing. PSU is an EVGA 1000w Gold.

I tested the system with OCCT and Cinebench R23 and had no issues at all! CPU temps were around 65-72 degrees during these tests. When gaming, CPU temps were similar and GPU temps were often in the mid 70s at highest utilization. I end up black screening, with a complete audio buzzing sound, and the system fans, GPU, etc keep running but cannot do anything on the PC. It needs to be shut down via the power button.
I am at a loss here especially because I am at stock bios settings with XMP off. Does anyone have any suggestions?

Event log reveals WHEA-Logger EVENT ID 1, and then a crash dump analysis reveals the following:


8: 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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000007, BOOT Error
Arg2: ffffe188f64ee150, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3374

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 6468

Key : Analysis.IO.Other.Mb
Value: 7

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 19

Key : Analysis.Init.CPU.mSec
Value: 968

Key : Analysis.Init.Elapsed.mSec
Value: 11487

Key : Analysis.Memory.CommitPeak.Mb
Value: 82

Key : Bugcheck.Code.DumpHeader
Value: 0x124

Key : Bugcheck.Code.Register
Value: 0x50c47120

Key : Dump.Attributes.AsUlong
Value: 18

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1


FILE_IN_CAB: WHEA-20221212-2103.dmp

DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

BUGCHECK_CODE: 124

BUGCHECK_P1: 7

BUGCHECK_P2: ffffe188f64ee150

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: smss.exe

STACK_TEXT:
fffff18250c470d0 fffff8015975e35f : ffffe188f64ee130 0000000000000000 ffffe188f64ee150 0000000000000022 : nt!LkmdTelCreateReport+0x139
fffff18250c47610 fffff8015975e256 : ffffe188f64ee130 fffff80100000000 000000dc00000000 000000dc1497f480 : nt!WheapReportLiveDump+0x7b
fffff18250c47650 fffff801595cacb1 : 0000000000000001 fffff18250c47ac0 000000dc1497f480 0000000000000280 : nt!WheapReportDeferredLiveDumps+0x7a
fffff18250c47680 fffff80159452827 : 0000000000000000 ffffe188f6078ce0 0000000000000103 0000000000000000 : nt!WheaCrashDumpInitializationComplete+0x59
fffff18250c476b0 fffff8015920caf5 : ffffe188f6500000 ffffe188f6a75d30 fffff18250c47ac0 ffffe18800000000 : nt!NtSetSystemInformation+0x1f7
fffff18250c47a40 00007ffa799b05f4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000dc1497f428 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa`799b05f4


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: LKD_0x124_7_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5ea80f6a-69bf-5d6f-8fd2-cd87deb91a03}

Followup: MachineOwner

8: kd> !errrec ffffe188f64ee150
===============================================================================
Common Platform Error Record @ ffffe188f64ee150
-------------------------------------------------------------------------------
Record Id : 01d90e9706503f2d
Severity : Fatal (1)
Length : 3552
Creator : Microsoft
Notify Type : BOOT Error Record
Timestamp : 12/13/2022 2:03:00 (UTC)
Flags : 0x00000002 PreviousError

===============================================================================
Section 0 : Firmware Error Record Reference
-------------------------------------------------------------------------------
Descriptor @ ffffe188f64ee1d0
Section @ ffffe188f64ee2a8
Offset : 344
Length : 2592
Flags : 0x00000000
Severity : Fatal


===============================================================================
Section 1 : Firmware Error Record Reference
-------------------------------------------------------------------------------
Descriptor @ ffffe188f64ee218
Section @ ffffe188f64eecc8
Offset : 2936
Length : 544
Flags : 0x00000000
Severity : Fatal


===============================================================================
Section 2 : Firmware Error Record Reference
-------------------------------------------------------------------------------
Descriptor @ ffffe188f64ee260
Section @ ffffe188f64eeee8
Offset : 3480
Length : 72
Flags : 0x00000000
Severity : Fatal

---------
 

Colif

Win 11 Master
Moderator
intel microcode

tried updating windows?

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .