Mobile and Desktop Processors
Intel® Core™ processors, Intel Atom® processors, tools, and utilities
16760 Discussions

A fatal hardware error has occurred. A record describing the condition is contained in the data sect

halfspringchicken
1,208 Views

Hi, ive been getting this error after my pc freezes.

A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.

from the WHEA dump:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.016 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

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


Loading Dump File [C:\Windows\LiveKernelReports\WHEA\WHEA-20250108-2250.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 26100 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff800`dd600000 PsLoadedModuleList = 0xfffff800`de4f4850
Debug session time: Wed Jan  8 22:50:46.727 2025 (UTC + 8:00)
System Uptime: 0 days 0:00:03.403
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000005c`fde9b018).  Type ".hh dbgerr001" for details
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -vnt!LkmdTelCreateReport+0x1c8:
fffff800`dde145f4 488b03          mov     rax,qword ptr [rbx] ds:002b:ffffe10a`602f7d60=????????????????
6: 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: ffffe10a660ed020, 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: 1359

    Key  : Analysis.Elapsed.mSec
    Value: 8769

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

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

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

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

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

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

    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: ffffe10a660ed020

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  WHEA-20250108-2250.dmp

DUMP_FILE_ATTRIBUTES: 0x18
  Kernel Generated Triage Dump
  Live Generated Dump

FAULTING_THREAD:  ffffe10a661f5080

PROCESS_NAME:  smss.exe

STACK_TEXT:  
fffff302`9ecaee40 fffff800`ddda732e     : ffffe10a`660ed000 00000000`00000000 ffffe10a`660ed020 0000005c`fe17f4e8 : nt!LkmdTelCreateReport+0x1c8
fffff302`9ecaf380 fffff800`ddda722a     : ffffe10a`660ed000 00000000`00000001 ffffe10a`660ed000 00000000`00000000 : nt!WheapReportLiveDump+0x76
fffff302`9ecaf3c0 fffff800`ddda7197     : 00000000`00000001 fffff302`9ecafaa0 00000000`00000000 0000005c`fe17f4e8 : nt!WheapReportDeferredLiveDumps+0x7a
fffff302`9ecaf3f0 fffff800`de057581     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!WheaCrashDumpInitializationComplete+0x4b
fffff302`9ecaf420 fffff800`ddc8d355     : ffffe10a`661f5000 00000000`00000000 ffffe10a`661f5080 00000000`00000000 : nt!NtSetSystemInformation+0x641
fffff302`9ecafa20 00007ffd`e6702e94     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000005c`fe17f488 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`e6702e94


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

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



ive also attached the logs from the intel system support utility. im at my wits end.

0 Kudos
3 Replies
Earl_Intel
Moderator
1,115 Views

Hi halfspringchicken,


Thank you for posting in the communities!


I'm sorry to hear that your system is giving you trouble. Please supply the information requested here so that we can better assist you and identify the best course of action:

  • May I know if the processor is working fine before?
  • How did the issue start?
  • Are there any changes on the system before you encounter this issue?
  • Have you already tried to troubleshoot the issue? if yes, what are the troubleshooting steps you have tried?
  • Have you already tried the new Microcode 0x129 or Microcode 0x12B update on your BIOS?
  • Did you overclock the processor (Please note that if the system was overclocked, including voltage/frequency beyond the processor supported specifications, your processor voids warranty)?


We will be able to move forward with the following step and try to address the problem you are having once we receive this information.


Best regards,

Earl E.

Intel Customer Support Technician


0 Kudos
Earl_Intel
Moderator
1,094 Views

Hi halfspringchicken,


I wanted to check if you had the chance to review the questions I posted. Please let me know at your earliest convenience so that we can determine the best course of action to resolve this matter.


Best regards,

Earl E.

Intel Customer Support Technician


0 Kudos
Earl_Intel
Moderator
1,073 Views

Hi halfspringchicken,


I have not heard back from you so I will close this inquiry now. If you need further assistance, please submit a new question as this thread will no longer be monitored.


Best regards,

Earl E.

Intel Customer Support Technician


0 Kudos
Reply