[SOLVED] BSOD "WHEA UNCORRECTABLE ERROR" when external display is connected to the laptop ?

[Altair21]

As the title says, I get a BSOD whenever I try to start my laptop with my external display connected to it. After removing the HDMI cable, It works fine after a few BSODs. I tried using WindDbg to find out what's happening and it's just nt kernel errors, but I am not able to figure out from the dumps and event viewer which driver is causing it, tho by the looks of it, it might be Intel's graphic driver but I did update it yesterday and still same problem.

Here's the MiniDump Link.

I tried to analyze the dumps and this is what the output was. I need some help finding which device exactly is causing the error.

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


Loading Dump File [C:\Users\shaleen\Desktop\Minidump\051622-25687-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`3be00000 PsLoadedModuleList = 0xfffff800`3ca2a2b0
Debug session time: Mon May 16 20:48:54.378 2022 (UTC + 5:30)
System Uptime: 0 days 0:00:24.060
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`3c1f7d60 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8807`35ac0390=0000000000000124
2: 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: ffff9d892d446028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffff9d89223500dc
Arg4: ffff9d89222e71a0

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7171

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 45320

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

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

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

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  051622-25687-01.dmp

BUGCHECK_CODE:  124

BUGCHECK_P1: 10

BUGCHECK_P2: ffff9d892d446028

BUGCHECK_P3: ffff9d89223500dc

BUGCHECK_P4: ffff9d89222e71a0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffff8807`35ac0388 fffff800`3c3b64dc     : 00000000`00000124 00000000`00000010 ffff9d89`2d446028 ffff9d89`223500dc : nt!KeBugCheckEx
ffff8807`35ac0390 fffff800`3c3b7039     : ffff9d89`2d72fa90 ffff9d89`2d72fa90 ffff9d89`223500b0 ffff9d89`2d34c128 : nt!WheaReportHwError+0x3ec
ffff8807`35ac0470 fffff800`3c3b7155     : 00000000`00000000 00000000`00000062 ffff9d89`2d72fa90 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffff8807`35ac04a0 fffff800`40d72671     : 00000000`00000000 ffff8807`35ac06c0 ffff9d89`222e71a0 ffff9d89`222ec0ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffff8807`35ac0500 fffff800`40d6ba50     : 00000000`00000000 ffff9d89`222e71a0 ffff9d89`223a81a0 00000000`00000000 : storport!StorpWheaReportError+0x9d
ffff8807`35ac0590 fffff800`40d53c94     : fffff800`40d98000 00000000`00000062 00000000`00000000 ffff8807`35ac0930 : storport!StorpMarkDeviceFailed+0x358
ffff8807`35ac0820 fffff800`40d0b3bd     : 00000000`00000100 ffff9d89`222ec020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x16474
ffff8807`35ac08f0 fffff800`40d0e5b2     : ffff9d89`c1000002 00000000`00000000 ffff9d89`222ec020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffff8807`35ac0970 fffff800`40d0d52f     : ffff9d89`222ec020 ffff9d89`222e7050 ffff9d89`2c7a1220 80000000`00002000 : stornvme!NVMeControllerReset+0x10a
ffff8807`35ac09a0 fffff800`40d69146     : ffff9d89`2c7a1220 ffff9d89`222e7050 ffff9d89`22374080 ffff9d89`1e2d6a20 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffff8807`35ac09d0 fffff800`3c0f3265     : ffff9d89`2d767980 ffff9d89`2d767980 ffff9d89`222e7050 fffff800`405ec5c0 : storport!StorPortWorkItemRoutine+0x46
ffff8807`35ac0a00 fffff800`3c0bfae5     : ffff9d89`22302080 ffff9d89`22302080 fffff800`3c0f3130 ffff9d89`00000000 : nt!IopProcessWorkItem+0x135
ffff8807`35ac0a70 fffff800`3c0eea75     : ffff9d89`22302080 00000000`00000080 ffff9d89`1e2bc040 000fa46f`b19bbfff : nt!ExpWorkerThread+0x105
ffff8807`35ac0b10 fffff800`3c1ff3b8     : ffffe400`33ec1180 ffff9d89`22302080 fffff800`3c0eea20 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8807`35ac0b60 00000000`00000000     : ffff8807`35ac1000 ffff8807`35aba000 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
---------

2: kd> !errrec ffff9d892d446028
===============================================================================
Common Platform Error Record @ ffff9d892d446028
-------------------------------------------------------------------------------
Record Id     : 01d869383370f7ba
Severity      : Fatal (1)
Length        : 298
Creator       : {57217c8d-5e66-44fb-8033-9b74cacedf5b}
Notify Type   : {0033f803-2e70-4e88-992c-6f26daf3db7a}
Timestamp     : 5/16/2022 15:18:54 (UTC)
Platform Id   : {83c1603c-1552-48a7-87d1-14d9467d7765}
Platform Id   : {00000000-0000-0000-0000-000000000000}
Flags         : 0x00000008

===============================================================================
Section 0     : {00000000-0000-0000-0000-000000000000}
-------------------------------------------------------------------------------
Descriptor    @ ffff9d892d4460a8
Section       @ ffff9d892d4460f0
Offset        : 200
Length        : 98
Flags         : 0x00000001 Primary
Severity      : Fatal
FRU Text      :

*** Unknown section format ***

2: kd> !whea
Error Source Table @ fffff8003cadaf58
0 Error Sources
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2202.7001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2202.7001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\ObjectiveC.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2202.7001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2202.7001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2202.7001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2202.7001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2202.7001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2202.7001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2202.7001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2202.7001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2202.7001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2202.7001.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis'

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


Loading Dump File [C:\Users\shaleen\Desktop\Minidump\051822-10625-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff805`39000000 PsLoadedModuleList = 0xfffff805`39c2a2b0
Debug session time: Wed May 18 09:09:20.289 2022 (UTC + 5:30)
System Uptime: 0 days 0:00:32.972
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
..............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`393f7d60 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffc01`e9ad0390=0000000000000124
2: 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: ffffd182d4add028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffd182c890392c
Arg4: ffffd182c89831a0

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 9092

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 32130

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

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

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


FILE_IN_CAB:  051822-10625-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  124

BUGCHECK_P1: 10

BUGCHECK_P2: ffffd182d4add028

BUGCHECK_P3: ffffd182c890392c

BUGCHECK_P4: ffffd182c89831a0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffffc01`e9ad0388 fffff805`395b64dc     : 00000000`00000124 00000000`00000010 ffffd182`d4add028 ffffd182`c890392c : nt!KeBugCheckEx
fffffc01`e9ad0390 fffff805`395b7039     : ffffd182`d3d40f10 ffffd182`d3d40f10 ffffd182`c8903900 ffffd182`d52e7128 : nt!WheaReportHwError+0x3ec
fffffc01`e9ad0470 fffff805`395b7155     : 00000000`00000000 00000000`00000062 ffffd182`d3d40f10 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
fffffc01`e9ad04a0 fffff805`3e972671     : 00000000`00000000 fffffc01`e9ad06c0 ffffd182`c89831a0 ffffd182`c89880ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
fffffc01`e9ad0500 fffff805`3e96ba50     : 00000000`00000000 ffffd182`c89831a0 ffffd182`c88d61a0 00000000`00000000 : storport!StorpWheaReportError+0x9d
fffffc01`e9ad0590 fffff805`3e953c94     : fffff805`3e998000 00000000`00000062 00000000`00000000 fffffc01`e9ad0930 : storport!StorpMarkDeviceFailed+0x358
fffffc01`e9ad0820 fffff805`3e90b3bd     : 00000000`00000000 ffffd182`c8988020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x16474
fffffc01`e9ad08f0 fffff805`3e90e5b2     : ffffd182`c1000002 00000000`00000000 ffffd182`c8988020 00000000`00000003 : stornvme!ControllerReset+0x1a1
fffffc01`e9ad0970 fffff805`3e90d52f     : ffffd182`c8988020 ffffd182`c8983050 ffffd182`d3ed8560 80000000`00002000 : stornvme!NVMeControllerReset+0x10a
fffffc01`e9ad09a0 fffff805`3e969146     : ffffd182`d3ed8560 ffffd182`c8983050 ffffd182`ce6aa040 ffffd182`c48b6c50 : stornvme!NVMeControllerAsyncResetWorker+0x3f
fffffc01`e9ad09d0 fffff805`392f3265     : ffffd182`d4c9c4a0 ffffd182`d4c9c4a0 ffffd182`c8983050 fffff805`3e1ec5c0 : storport!StorPortWorkItemRoutine+0x46
fffffc01`e9ad0a00 fffff805`392bfae5     : ffffd182`c8689440 ffffd182`c8689440 fffff805`392f3130 ffffd182`00000000 : nt!IopProcessWorkItem+0x135
fffffc01`e9ad0a70 fffff805`392eea75     : ffffd182`c8689440 00000000`00000080 ffffd182`c48bf040 000fa46f`b19bbfff : nt!ExpWorkerThread+0x105
fffffc01`e9ad0b10 fffff805`393ff3b8     : ffff9681`d7cc1180 ffffd182`c8689440 fffff805`392eea20 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffc01`e9ad0b60 00000000`00000000     : fffffc01`e9ad1000 fffffc01`e9aca000 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

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

2: kd> !errrec ffffd182d4add028
===============================================================================
Common Platform Error Record @ ffffd182d4add028
-------------------------------------------------------------------------------
Record Id     : 01d86a68c8730fa1
Severity      : Fatal (1)
Length        : 298
Creator       : {57217c8d-5e66-44fb-8033-9b74cacedf5b}
Notify Type   : {0033f803-2e70-4e88-992c-6f26daf3db7a}
Timestamp     : 5/18/2022 3:39:20 (UTC)
Platform Id   : {83c1603c-1552-48a7-87d1-14d9467d7765}
Platform Id   : {00000000-0000-0000-0000-000000000000}
Flags         : 0x00000008

===============================================================================
Section 0     : {00000000-0000-0000-0000-000000000000}
-------------------------------------------------------------------------------
Descriptor    @ ffffd182d4add0a8
Section       @ ffffd182d4add0f0
Offset        : 200
Length        : 98
Flags         : 0x00000001 Primary
Severity      : Fatal
FRU Text      :

*** Unknown section format ***

 

[johnbl]

the bugcheck was called by a driver
it looks like it is coming out of the storage driver
microsoft generic storport.sys asked stornvme.sys to reset and it not respond.
storport.sys returned a error that the device has failed which lead to the bugcheck.
(maybe it is overheating)
you might run crystaldiskinfo.exe and read the smart data from the drive, you might look at the firmware version and see if there is a update.

https://www.dell.com/support/home/en-us/product-support/product/inspiron-15-7577-laptop/drivers
for bios and driver updates
your bios info:
Vendor Dell Inc.
BIOS Version 1.9.3
BIOS Starting Address Segment f000
BIOS Release Date 12/20/2019

dell has a bios update released 27 Apr 2022
it might have an effect on the storage driver. (if it not a overheating issue)
=============

other issues:
I would disable these these drivers using autorun
then reboot and see if you still bugcheck.

WinRing0x64.sys Sat Jul 26 06:29:37 2008
(too old driver)
RTCore64.sys Thu Jun 18 04:55:42 2020
(overclock driver, just a bad idea while debugging)

ScrHIDDriver2.sys Mon Oct 22 07:07:44 2018
Related to Phone Input Device from Screenovate Tech
(just because it is the first time I have seen someone use this driver)

 

[Altair21]

the bugcheck was called by a driver
it looks like it is coming out of the storage driver
microsoft generic storport.sys asked stornvme.sys to reset and it not respond.
storport.sys returned a error that the device has failed which lead to the bugcheck.
(maybe it is overheating)
you might run crystaldiskinfo.exe and read the smart data from the drive, you might look at the firmware version and see if there is a update.

https://www.dell.com/support/home/en-us/product-support/product/inspiron-15-7577-laptop/drivers
for bios and driver updates
your bios info:
Vendor Dell Inc.
BIOS Version 1.9.3
BIOS Starting Address Segment f000
BIOS Release Date 12/20/2019

dell has a bios update released 27 Apr 2022
it might have an effect on the storage driver. (if it not a overheating issue)
=============

other issues:
I would disable these these drivers using autorun
then reboot and see if you still bugcheck.

WinRing0x64.sys Sat Jul 26 06:29:37 2008
(too old driver)
RTCore64.sys Thu Jun 18 04:55:42 2020
(overclock driver, just a bad idea while debugging)

ScrHIDDriver2.sys Mon Oct 22 07:07:44 2018
Related to Phone Input Device from Screenovate Tech
(just because it is the first time I have seen someone use this driver)

Thanks for the help! I did check my ssd health with crystal disk info and all seemed to be good even in the smart data. In the end I just nuked my windows installation and did a clean install. all seems to be working fine now. I did accidentally upgrade my bios and that seemed to exacerbate the issue but on the clean install, the new bios is working fine ( I did rollback the bios update tho for undervolting).

 

[Altair21]

the bugcheck was called by a driver
it looks like it is coming out of the storage driver
microsoft generic storport.sys asked stornvme.sys to reset and it not respond.
storport.sys returned a error that the device has failed which lead to the bugcheck.
(maybe it is overheating)
you might run crystaldiskinfo.exe and read the smart data from the drive, you might look at the firmware version and see if there is a update.

https://www.dell.com/support/home/en-us/product-support/product/inspiron-15-7577-laptop/drivers
for bios and driver updates
your bios info:
Vendor Dell Inc.
BIOS Version 1.9.3
BIOS Starting Address Segment f000
BIOS Release Date 12/20/2019

dell has a bios update released 27 Apr 2022
it might have an effect on the storage driver. (if it not a overheating issue)
=============

other issues:
I would disable these these drivers using autorun
then reboot and see if you still bugcheck.

WinRing0x64.sys Sat Jul 26 06:29:37 2008
(too old driver)
RTCore64.sys Thu Jun 18 04:55:42 2020
(overclock driver, just a bad idea while debugging)

ScrHIDDriver2.sys Mon Oct 22 07:07:44 2018
Related to Phone Input Device from Screenovate Tech
(just because it is the first time I have seen someone use this driver)

Hey I tried out what you suggested and it seemed fine for a while but now it's again started giving me BSOD, Here's the minidump analysis


***

• *
• 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: ffffb584ac120028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffffb5849b26b87c
Arg4: ffffb5849b2e31a0

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3842

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 31371

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

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

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


FILE_IN_CAB: 053022-9843-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 124

BUGCHECK_P1: 10

BUGCHECK_P2: ffffb584ac120028

BUGCHECK_P3: ffffb5849b26b87c

BUGCHECK_P4: ffffb5849b2e31a0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffc580c4aa7388 fffff8047b7b64dc : 0000000000000124 0000000000000010 ffffb584ac120028 ffffb5849b26b87c : nt!KeBugCheckEx
ffffc580c4aa7390 fffff8047b7b7039 : ffffb584ace05010 ffffb584ace05010 ffffb5849b26b850 ffffb584ac12a128 : nt!WheaReportHwError+0x3ec
ffffc580c4aa7470 fffff8047b7b7155 : 0000000000000000 0000000000000062 ffffb584ace05010 0000000000000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffc580c4aa74a0 fffff8047ff72671 : 0000000000000000 ffffc580c4aa76c0 ffffb5849b2e31a0 ffffb5849b2e80ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffc580c4aa7500 fffff8047ff6ba50 : 0000000000000000 ffffb5849b2e31a0 ffffb5849b2ea1a0 0000000000000000 : storport!StorpWheaReportError+0x9d
ffffc580c4aa7590 fffff8047ff53c94 : fffff8047ff98000 0000000000000062 0000000000000000 ffffc580c4aa7930 : storport!StorpMarkDeviceFailed+0x358
ffffc580c4aa7820 fffff8047ff0b3bd : 0000000000000300 ffffb5849b2e8020 0000000000000000 0000000000000000 : storport!StorPortNotification+0x16474
ffffc580c4aa78f0 fffff8047ff0e5b2 : ffffb584c1000002 0000000000000000 ffffb5849b2e8020 0000000000000003 : stornvme!ControllerReset+0x1a1
ffffc580c4aa7970 fffff8047ff0d52f : ffffb5849b2e8020 ffffb5849b2e3050 ffffb584a8f24cf0 8000000000002000 : stornvme!NVMeControllerReset+0x10a
ffffc580c4aa79a0 fffff8047ff69146 : ffffb584a8f24cf0 ffffb5849b2e3050 ffffb5849b3ab080 ffffb584982a0a20 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffc580c4aa79d0 fffff8047b4f3265 : ffffb584a9a3d280 ffffb584a9a3d280 ffffb5849b2e3050 fffff80495145440 : storport!StorPortWorkItemRoutine+0x46
ffffc580c4aa7a00 fffff8047b4bfae5 : ffffb584ac8cf040 ffffb584ac8cf040 fffff8047b4f3130 ffffb58400000000 : nt!IopProcessWorkItem+0x135
ffffc580c4aa7a70 fffff8047b4eea75 : ffffb584ac8cf040 0000000000000080 ffffb584982e2180 000fa46fb19bbfff : nt!ExpWorkerThread+0x105
ffffc580c4aa7b10 fffff8047b5ff3b8 : ffffe381958c1180 ffffb584ac8cf040 fffff8047b4eea20 0000000000000000 : nt!PspSystemThreadStartup+0x55
ffffc580c4aa7b60 0000000000000000 : ffffc580c4aa8000 ffffc580c4aa1000 0000000000000000 0000000000000000 : 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

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

As far as I can tell its an ssd error, do you think my ssd is failing?

 

[johnbl]

the driver for the drive failed to get a response from the drive, it then tried to reset the drive interface and did not get a response so it assumed the drive failed and called a bugcheck.

sometimes it happens if the device over heats. it can also happen under other conditions. you might boot windows, make sure there is plenty of free space on the drive. empty the recycle bin, delete programs you don't need. turn off virtual memory, reboot and turn it back on.
then boot into bios and leave the machine powered on for at least 30 minutes then reboot. (these drives run their own firmware that does cleanup independent of windows, sometimes it gets behind. The routines run 5 minutes after the drive goes idle but some systems sleep pretty fast now and the routines do not get to run)
now google for crystaldiskinfo.exe and download the tool and run it. it will read the smart info from the drive and give you an idea of its health. You can also look at the drives firmware version then look to see if there is a firmware update for the drive.

there are other causes for this error: fixes would be bios updates and matching chipset updates from the motherboard vendor. For some devices you also need a updated driver for the device itself.

if you can you should put the actual memory dump on a server. I generally look for overclocking drivers and for corrupted windows files since some malware targets and replaces sections of drivers. (such as storage drivers)
(deleting the virtual memory and turning it back on helps dump some of the hiding places for malware/corruption problems)

NOTE: when you look at the memory dump you should also note what the system up timer is (at the top of the debug output)
and see if it makes sense to you. Sometimes it might indicate a very small value like a few seconds and that could change what you should be looking for.

a 24 second up time could mean the system got hot, rebooted and the drive still has not cooled down enough to reconnect.
if the system has cooled down and it boots you could open the system up and take the drive out and just put it back in. just in the hopes you make a better connection.
but do use a tool like crystaldiskinfo.exe and check its health status.

 

[johnbl]

edit:
firmware bug in the drive could be a direct cause of the problem.
be sure to check to see if there is a update drive firmware.
---------
also run your system in high performance mode. you do not want something stupid like a usb device sleeping and not waking to be the cause of this failure.
=======
need to know what interface the external monitor is being connected to. docking station, usb -c, hdmi?
usb/thunderbolt can have their own firmware updates that need to be installed. these can also use the same interface as the drive and cause this type of issue.
-----
if this problem only happens when you connect a external display you are looking at a different problem than your drive failing. All these devices are going through the same high speed bus and they can mess each other up. when you connect the external display, power down and go into bios and reset it to defaults or change any setting and change it back and save and reboot and see if that has any effect.

you should also change the memory dump type to kernel and provide the kernel dump on the next bugcheck. This will provide debug info about your hardware, usb subsystem and windows plug and play as well as access to the internal error logs

notes:
the debugger can check for corrupt files with this command:
!for_each_module !chkimg @#ModuleName
you will get a error for each 3rd party driver that microsoft does not have symbols for on the symbol server)

 

[Altair21]

edit:
firmware bug in the drive could be a direct cause of the problem.
be sure to check to see if there is a update drive firmware.
---------
also run your system in high performance mode. you do not want something stupid like a usb device sleeping and not waking to be the cause of this failure.
=======
need to know what interface the external monitor is being connected to. docking station, usb -c, hdmi?
usb/thunderbolt can have their own firmware updates that need to be installed. these can also use the same interface as the drive and cause this type of issue.
-----
if this problem only happens when you connect a external display you are looking at a different problem than your drive failing. All these devices are going through the same high speed bus and they can mess each other up. when you connect the external display, power down and go into bios and reset it to defaults or change any setting and change it back and save and reboot and see if that has any effect.

you should also change the memory dump type to kernel and provide the kernel dump on the next bugcheck. This will provide debug info about your hardware, usb subsystem and windows plug and play as well as access to the internal error logs

notes:
the debugger can check for corrupt files with this command:
!for_each_module !chkimg @#ModuleName
you will get a error for each 3rd party driver that microsoft does not have symbols for on the symbol server)

1. I dont think its a overheating problem, the bsod mostly ocuurs on startup after the laptop has been pwered off for a while. also I keep track of temps in HWinfo, and its fine (just a single temp reading there that sometimes goes to 70c+)
2. The paging file is set to the HDD, but I have disabled it and enabled it again (let's see how it goes)
3. I'll do the bios thing after work today.
4. I have already run crystaldiskinfo and mark, both checked out with no issues.
5. I have an Adata SX8200 pro, their ssd toolbox is shiity but no firmware updates according to it.
6. I cant update the bios ( the newer ones disable undervolting - plundervolt vulnerability) but I have updated the chipset drivers,
7. I have set it to Kernel mode now, I'll upload the dump next time it fails.
8. I am using HDMI for my external monitor which is connected to the integrated gpu, no direct lane between hdmi to my discrete graphics,
9. Nah, external display is fine now. I think I started my laptop with it connected and it mostly always crashed on startup itself that's why I assumed it was the display but it crashes without it too.

P.S. I have 512gig ssd, outof which collectively 130 gigs are free. so space shouldnt really be a problem.

As for overclocking, I use throttlestop for undervolting as well as a bit of managing clock speeds, but the config has been stable for years and its only recently that its been a problem so I dont think thats the issue.

EDIT: I dont have any power savings plan etc for it. fast startup/hibernate is disabled.

 

[Dragos Manea]

Before any troubleshooting any undervolt/OC should be removed for easy troubleshooting

 

[Altair21]

Before any troubleshooting any undervolt/OC should be removed for easy troubleshooting

Yea, I have disabled it before I did my troubleshooting and it was still crashing with the same error and everything, even the mini dumps were identical

 

[Altair21]

UPDATE: My System crashed again and here's the kernel dump link if that helps ( I had to compress it because my net couldn't handle uploading the whole thing)
Link @johnbl

 

[johnbl]

i think what happened was your system went to a lower power state, then when some devices were to wake up they did not. a driver tried to reset the drive and it did not wake and a bugcheck was called.

you should update the bios and drivers from dell:
Support for Inspiron 15 Gaming 7577 | Drivers & Downloads | Dell US

then reboot and see what problems you still have

bios functions setup control for a lot of your hardware, the updates work with the new driver updates. if you can not get the old bios to work correctly with the new drivers then you will have to disable functions. like running in high power mode because of the changes to power management to save power.
you would also want to go into windows control panel, device manager. find all the hid and usb devices right click on them to bring up properties then find the power management tab and select it and disable letting windows control its power states to save power.
be sure to check your usb hubs and bluetooth devices.

---------------


i can see your usb 3 bus is waiting to wake,
your bluetooth is waiting to wake
your storage driver is just confused and in a unknown state.
-----------
2: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.0, DMIVersion 0, Size=6112]
BiosMajorRelease = 1
BiosMinorRelease = 9
BiosVendor = Dell Inc.
BiosVersion = 1.9.3
BiosReleaseDate = 12/20/2019
SystemManufacturer = Dell Inc.
SystemProductName = Inspiron 7577
SystemFamily = Inspiron
SystemSKU = 07FA
BaseBoardManufacturer = Dell Inc.
BaseBoardProduct = 0C5NXN
BaseBoardVersion = A03

your driver for your storage controller is old (2017)
you might want to go to dell and update your bios and various driver files and reboot and see if the problem just goes away.

I think your driver just does not understand some new low power states that windows is using. best to bios update and driver update from dell
device state history indicates a unknown state. from the debugger i can see it was in d3 power state (a low power state)

you might be able to prevent the bugcheck by running your system in high performance mode until you get the bios and driver updates installed.

2: kd> !DevNode ffffc5012a8e5ca0
DevNode 0xffffc5012a8e5ca0 for PDO 0xffffc5012a8d2360
Parent 0xffffc5012a98ead0 Sibling 0xffffc5012a87c520 Child 0xffffc5012a97ec30
InstancePath is "PCI\VEN_8086&DEV_A103&SUBSYS_07FA1028&REV_31\3&11583659&0&B8"
ServiceName is "iaStorAC"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[12] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[11] = DeviceNodeEnumeratePending (0x30c)
StateHistory[10] = DeviceNodeStarted (0x308)
StateHistory[09] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[08] = DeviceNodeEnumeratePending (0x30c)
StateHistory[07] = DeviceNodeStarted (0x308)
StateHistory[06] = DeviceNodeStartPostWork (0x307)
StateHistory[05] = DeviceNodeStartCompletion (0x306)
StateHistory[04] = DeviceNodeStartPending (0x305)
StateHistory[03] = DeviceNodeResourcesAssigned (0x304)
StateHistory[02] = DeviceNodeDriversAdded (0x303)
StateHistory[01] = DeviceNodeInitialized (0x302)
StateHistory[00] = DeviceNodeUninitialized (0x301)
StateHistory[19] = Unknown State (0x0)
StateHistory[18] = Unknown State (0x0)
StateHistory[17] = Unknown State (0x0)
StateHistory[16] = Unknown State (0x0)
StateHistory[15] = Unknown State (0x0)
StateHistory[14] = Unknown State (0x0)
StateHistory[13] = Unknown State (0x0)
Flags (0x6c0000f0) DNF_ENUMERATED, DNF_IDS_QUERIED,
DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED,
DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_LOWER_CLASS_FILTERS,
DNF_NO_UPPER_DEVICE_FILTERS, DNF_NO_UPPER_CLASS_FILTERS
UserFlags (0x00000008) DNUF_NOT_DISABLEABLE
CapabilityFlags (0x00400000)
Unknown flags 0x00400000
DisableableDepends = 2 (including self)

 

[Altair21]

@johnbl Is updating BIOS the only way it'll work? I really dont want to do it because without undervolting my laptop is unusable. Also I tried installing the Intel RST driver from dell, but it errors out saying system is not compatible

 

[johnbl]

@johnbl Is updating BIOS the only way it'll work? I really dont want to do it because without undervolting my laptop is unusable. Also I tried installing the Intel RST driver from dell, but it errors out saying system is not compatible

it will be tricky to not update the bios since vendors have been making updates for security fixes in their tools, bios and cpu.
-you could maybe run in high performance mode to avoid sleep problems but I am still seeing sleep problems with machines that are set to not sleep. Mostly with bluetooth headsets.

-You could update the bios but then go into the bios and disable any turbo functions or speedstep functions to prevent overheating issues so you would not need to underclock.

-The intel storage driver is not required.(assuming you are not running in a raid configuration) You can select the microsoft generic storage driver as a replacement. You will not get the intel special functions but you will not get all the little bugs either. you can google for instructions or look at something like this :Replacing Manufacturer AHCI Drivers With Standard Microsoft SATA Drivers | Crucial.com
The microsoft generic driver may just work with out issues with out changing the bios. The generic drivers are on a lot more machines, errors are automatically reported to microsoft and fixes pushed out by windows update. The generic version should not depend on specific bios fixes.

intel also has their own driver update tool, good for when vendors stop support of machines:
Intel® Driver & Support Assistant

here is the current bug list /fix list for the driver.
Crash Dump Report for Intel® Rapid Storage Technology (Intel® RST)... (this is a old buglist from early 2020)
most fixes on the list were sleep problems. waking up from sleep states (s3, and s4)

you may find the current intel driver may not install but one from 2020 might work for you. ( if you can find one)

 

[Altair21]

Thanks I

it will be tricky to not update the bios since vendors have been making updates for security fixes in their tools, bios and cpu.
-you could maybe run in high performance mode to avoid sleep problems but I am still seeing sleep problems with machines that are set to not sleep. Mostly with bluetooth headsets.

-You could update the bios but then go into the bios and disable any turbo functions or speedstep functions to prevent overheating issues so you would not need to underclock.

-The intel storage driver is not required.(assuming you are not running in a raid configuration) You can select the microsoft generic storage driver as a replacement. You will not get the intel special functions but you will not get all the little bugs either. you can google for instructions or look at something like this :Replacing Manufacturer AHCI Drivers With Standard Microsoft SATA Drivers | Crucial.com
The microsoft generic driver may just work with out issues with out changing the bios. The generic drivers are on a lot more machines, errors are automatically reported to microsoft and fixes pushed out by windows update. The generic version should not depend on specific bios fixes.

intel also has their own driver update tool, good for when vendors stop support of machines:
Intel® Driver & Support Assistant

here is the current bug list /fix list for the driver.
Crash Dump Report for Intel® Rapid Storage Technology (Intel® RST)... (this is a old buglist from early 2020)
most fixes on the list were sleep problems. waking up from sleep states (s3, and s4)

you may find the current intel driver may not install but one from 2020 might work for you. ( if you can find one)

Thanks I found an old version of rst from dell which was released right around my bios version. Hopefully this one will work fine