Processors
Intel® Processors, Tools, and Utilities
15863 Discussions

13900-K causing fatal hardware crash?

Guywhoneedshelp3452
58 Views

Hello,

 

My system has run flawlessly for two years. Out of nowhere yesterday, while I was doing nothing other than typing a URL into Brave Browser, the entire device froze--everything on my desktop froze, mouse and keyboard were unresponsive (clicking Num Lock wouldn't turn the corresponding light on the keyboard on), and even the lights on my CPU cooler and RAM sticks stopped their usual changing RGB colors and had their colors frozen in a static state. I had to click the reset button on my PC, after which the PC turned off and turned itself back on and booted normally.

WHEA Logger logged an "Event ID: 1": "A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event." This is the only time that event has appeared in Event Viewer.

I have the details from the dump file below, which suggests that something related to my 13900-K is the problem, but first here are my system specs:

OS: Windows 10 Version 10.0.19045 Build 19045

Processor: 13th Gen Intel(R) Core(TM) i9-13900K, 3000 Mhz, 24 Core(s), 32 Logical Processor(s)

Motherboard: PRO Z690-A WIFI (MS-7D25)

RAM: 64GB 5600MHz DDR5

GPU: Palit RTX 4090

 

Here is the dump file:

*******************************************************************************
*                                                                             *
*                        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: ffffcc049d926150, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

Mini Kernel Dump does not contain unloaded driver list
Mini Kernel Dump does not contain unloaded driver list
Mini Kernel Dump does not contain unloaded driver list

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 765

    Key  : Analysis.Elapsed.mSec
    Value: 3601

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x124

    Key  : Bugcheck.Code.TargetModel
    Value: 0x124

    Key  : Dump.Attributes.AsUlong
    Value: 18

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: LKD_0x124_7_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

    Key  : Failure.Hash
    Value: {5ea80f6a-69bf-5d6f-8fd2-cd87deb91a03}


BUGCHECK_CODE:  124

BUGCHECK_P1: 7

BUGCHECK_P2: ffffcc049d926150

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  WHEA-20241122-1525.dmp

DUMP_FILE_ATTRIBUTES: 0x18
  Kernel Generated Triage Dump
  Live Generated Dump

FAULTING_THREAD:  ffffcc04a9859080

PROCESS_NAME:  smss.exe

STACK_TEXT:  
fffff080`edb3a0d0 fffff805`81b621cf     : ffffcc04`9d926130 00000000`00000000 ffffcc04`9d926150 00000000`00000022 : nt!LkmdTelCreateReport+0x139
fffff080`edb3a610 fffff805`81b620c6     : ffffcc04`9d926130 fffff805`00000000 00000085`00000000 00000085`491ff490 : nt!WheapReportLiveDump+0x7b
fffff080`edb3a650 fffff805`819d7941     : 00000000`00000001 fffff080`edb3aac0 00000085`491ff490 00000000`00000300 : nt!WheapReportDeferredLiveDumps+0x7a
fffff080`edb3a680 fffff805`817dd8f7     : 00000000`00000000 ffffcc04`a7f91030 00000000`00000103 00000000`00000000 : nt!WheaCrashDumpInitializationComplete+0x59
fffff080`edb3a6b0 fffff805`81612505     : ffffcc04`a9850000 ffffcc04`a98576b0 fffff080`edb3aac0 ffffcc04`00000000 : nt!NtSetSystemInformation+0x1f7
fffff080`edb3aa40 00007ffa`8add0a64     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000085`491ff438 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`8add0a64


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .process /r /p 0xffffcc04a901f0c0; .thread 0xffffcc04a9859080 ; 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
---------

There doesn't appear to be anything wrong with the computer apart from the fact that this happened. I ran some CPU benchmarks a few times--3DMark CPU Profile and Time Spy Extreme--and everything seemed normal.

In hopes of avoiding the crash in future, I uninstalled iCUE software as I read this can create problems like this. I also disabled the 13900-K's integrated graphics in Device Manager, as the 4090 video card is the only thing that should be handling video processing anyway. Does anything in the dump file suggest it could be the integrated graphics driver or component that caused this?

0 Kudos
0 Replies
Reply