BSOD 0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

[zhouwenhai]

hello,

I am having some BSOD and upon analyzing the dmp files this is what I have found. Seems to be related to the Processor. Any ideas on what I can do here?

PROCESS_NAME: System

Minidump:

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

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

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

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

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

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


Loading Dump File [C:\Users\ZWH\Desktop\021524-44218-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff807`37000000 PsLoadedModuleList = 0xfffff807`37c2a2b0
Debug session time: Thu Feb 15 16:14:13.920 2024 (UTC + 8:00)
System Uptime: 0 days 0:03:25.699
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....
Loading User Symbols

Loading unloaded module list
....................
For analysis of this file, run !analyze -vnt!KeBugCheckEx:
fffff807`373f7dd0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffbd84`0cb20390=0000000000000124
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: 0000000000000010, Device Driver Error
Arg2: ffffd604ccb3d028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffd604b7720b5c
Arg4: ffffd604b782b1a0

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3046

    Key  : Analysis.Elapsed.mSec
    Value: 19024

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x124

    Key  : Failure.Bucket
    Value: 0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

    Key  : Failure.Hash
    Value: {37af9407-4a3e-0b08-acdd-dadffdc34c3c}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  124

BUGCHECK_P1: 10

BUGCHECK_P2: ffffd604ccb3d028

BUGCHECK_P3: ffffd604b7720b5c

BUGCHECK_P4: ffffd604b782b1a0

FILE_IN_CAB:  021524-44218-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffbd84`0cb20388 fffff807`375b668c     : 00000000`00000124 00000000`00000010 ffffd604`ccb3d028 ffffd604`b7720b5c : nt!KeBugCheckEx
ffffbd84`0cb20390 fffff807`375b71e9     : ffffd604`ca943690 ffffd604`ca943690 ffffd604`b7720b30 ffffd604`ccb1e128 : nt!WheaReportHwError+0x3ec
ffffbd84`0cb20470 fffff807`375b7305     : 00000000`00000000 00000000`00000062 ffffd604`ca943690 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffbd84`0cb204a0 fffff807`3b8b3311     : 00000000`00000000 ffffbd84`0cb206c0 ffffd604`b782b1a0 ffffd604`b78300ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffbd84`0cb20500 fffff807`3b8ac6f0     : 00000000`00000000 ffffd604`b782b1a0 ffffd604`b77851a0 00000000`00000000 : storport!StorpWheaReportError+0x9d
ffffbd84`0cb20590 fffff807`3b894994     : fffff807`3b8d9000 00000000`00000062 00000000`00000000 ffffbd84`0cb20930 : storport!StorpMarkDeviceFailed+0x358
ffffbd84`0cb20820 fffff807`3b84b3bd     : 00000000`00000100 ffffd604`b7830020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x17174
ffffbd84`0cb208f0 fffff807`3b84e5b2     : ffffd604`c1000002 00000000`00000000 ffffd604`b7830020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffffbd84`0cb20970 fffff807`3b84d52f     : ffffd604`b7830020 ffffd604`b782b050 ffffd604`c8bb25d0 80000000`00002000 : stornvme!NVMeControllerReset+0x10a
ffffbd84`0cb209a0 fffff807`3b8a9de6     : ffffd604`c8bb25d0 ffffd604`b782b050 ffffd604`b7778080 ffffd604`b5288ca0 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffbd84`0cb209d0 fffff807`372f3265     : ffffd604`c3dbac10 ffffd604`c3dbac10 ffffd604`b782b050 fffff807`3d145440 : storport!StorPortWorkItemRoutine+0x46
ffffbd84`0cb20a00 fffff807`372bfae5     : ffffd604`b7813080 ffffd604`b7813080 fffff807`372f3130 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffffbd84`0cb20a70 fffff807`372eea75     : ffffd604`b7813080 00000000`00000080 ffffd604`b5269040 000fa4ef`bd9bbfff : nt!ExpWorkerThread+0x105
ffffbd84`0cb20b10 fffff807`373ff428     : fffff807`34705180 ffffd604`b7813080 fffff807`372eea20 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffbd84`0cb20b60 00000000`00000000     : ffffbd84`0cb21000 ffffbd84`0cb1a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {37af9407-4a3e-0b08-acdd-dadffdc34c3c}

Followup:     MachineOwner
---------