Processors
Processors (Intel® Core™, Intel® Xeon®, etc); processor utilities and programs (Intel® Processor Identification Utility, Intel® Extreme Tuning Utility, Intel® Easy Streaming Wizard, etc.)
12763 Discussions

12700k Plagued with WHEA Uncorrectable Errors

Refrax21
Beginner
206 Views

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 was 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:  
fffff182`50c470d0 fffff801`5975e35f     : ffffe188`f64ee130 00000000`00000000 ffffe188`f64ee150 00000000`00000022 : nt!LkmdTelCreateReport+0x139
fffff182`50c47610 fffff801`5975e256     : ffffe188`f64ee130 fffff801`00000000 000000dc`00000000 000000dc`1497f480 : nt!WheapReportLiveDump+0x7b
fffff182`50c47650 fffff801`595cacb1     : 00000000`00000001 fffff182`50c47ac0 000000dc`1497f480 00000000`00000280 : nt!WheapReportDeferredLiveDumps+0x7a
fffff182`50c47680 fffff801`59452827     : 00000000`00000000 ffffe188`f6078ce0 00000000`00000103 00000000`00000000 : nt!WheaCrashDumpInitializationComplete+0x59
fffff182`50c476b0 fffff801`5920caf5     : ffffe188`f6500000 ffffe188`f6a75d30 fffff182`50c47ac0 ffffe188`00000000 : nt!NtSetSystemInformation+0x1f7
fffff182`50c47a40 00007ffa`799b05f4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000dc`1497f428 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 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

 

0 Kudos
3 Replies
Jocelyn_Intel
Moderator
166 Views

Hello, @Refrax21

 

Thank you for posting on the Intel® communities.  

 

I am sorry to hear what is happening to your processor, I will gladly assist you to figure out a solution here. 

 

Please, answer these questions to have a better perspective on this issue and try the following steps: 

 

  1. Did you try setting the BIOS defaults in your motherboard? 
  2. Remove any hardware or drivers recently installed that might be causing this BSOD. 
  3. Try the Windows Safe mode. Check if there are any driver errors in the device manager and update device driver for the devices that are showing errors.  
  4. Make sure you have the latest Windows updates. Go to Settings → Update & security → Windows Update, and then select Check for updates. When done, reboot your system.  
  5. Try the minimal configuration (no Discrete Graphics card, motherboard, 1 RAM stick, SSD, power supply, less hardware components on your system). 
  6. Test your RAM with the Windows Memory Diagnostic to check for memory issues.  
  7. Did you check the power supply is working correctly? 
  8. If possible, try other hardware in your system to discard any hardware issue (a known working SSD, processor, motherboard, RAM, etc.). 
  9. Test the processor and attach the reports and screenshots, check on the notes: 

 

Intel® Processor Diagnostic Tool 

Note: As soon as you run it, it will start testing, please attach the complete Screenshot or click on "File", select the "View Results File" option, save and attach the report. 

 

Intel® Extreme Tuning Utility (Intel® XTU) 

Note: Click on "Stress Test" tab and "Start Testing" and then, attach a complete screenshot. 

 

Best regards,  

Jocelyn M.   

Intel Customer Support Technician.


Jocelyn_Intel
Moderator
133 Views

Hello, @Refrax21

 

We are checking this thread and we would like to know if you need further assistance. Please do not hesitate to contact us back. 

 

Best regards,  

Jocelyn M.   

Intel Customer Support Technician.


Jocelyn_Intel
Moderator
121 Views

Hello, @Refrax21

 

We have not heard back from you so we will proceed to close this thread now. If you need any additional information, please submit a new question as this thread will no longer be monitored.  

 

Best regards,  

Jocelyn M.   

Intel Customer Support Technician.


Reply