'The computer has rebooted from a bugcheck' - how to determine cause of system shutdown?

[8385895939]

Hi all, my computer turns off several times a day currently, typically always under load eg games, YouTube, voip calls.

I checked my event logger and I don't see any event (if I'm supposed to) before the PC turns off, but when it turns back on I see an event detailing:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000010, 0xffffb70462a7c028, 0xffffb70419739b2c, 0xffffb704198f21a0). A dump was saved in: C:\WINDOWS\Minidump\050724-12562-01.dmp. Report Id: 5eab68d1-cc53-4b3a-9977-778ea0b03b6b.

I've got the dmp file attached here but I can't seem to find or run windbg on my computer (again, not sure if that's what I am supposed to do) to read the dmp file and know for sure what it is causing it.

How can I analyse this file to determine what is causing my system to turn off? PS - no blue screen or error, just straight powers off always under the same circumstances.

 

Attached is the dmp and the event logger file that occured when the PC last turned off today.

 

Thanks in advance

050724-12562-01.dmp test.evtx

[Murasaki]

Seems to be caused by GenuineIntel.sys (which sounds like CPU related?) but also has a stack trace to stornvme.sys

My guess is something is happening between the cpu and your nvme SSD communicating. I suggest you check your NVME SSD's S.M.A.R.T. info with software like CrystalDiskInfo.

Spoiler

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

Debugging Details:
------------------
CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffef09`6e2520e8 fffff805`8060ef7b     : 00000000`00000124 00000000`00000010 ffffb704`62a7c028 ffffb704`19739b2c : nt!KeBugCheckEx
ffffef09`6e2520f0 fffff805`8060faa3     : ffffb704`2e47b890 ffffb704`2e47b890 ffffb704`19739b00 fffff805`8024a81d : nt!WheaReportHwError+0x37b
ffffef09`6e2521c0 fffff805`8060fbc5     : 00000000`00000000 00000000`000000ba ffffb704`2e47b890 fffff805`802c6064 : nt!WheaHwErrorReportSubmitDeviceDriver+0xf3
ffffef09`6e2521f0 fffff805`821801c8     : ffffef09`6e252430 ffffef09`6e252430 ffffb704`198f2050 ffffb704`140102c0 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffef09`6e252250 fffff805`821798b3     : 00000000`00000000 00000000`00000000 ffffb704`198f21a0 00000000`00000000 : storport!StorpWheaReportError+0xb8
ffffef09`6e2522e0 fffff805`8215c36e     : ffffb704`37d8b900 ffffb704`197db010 00000000`00000000 fffff805`82459a4c : storport!StorpMarkDeviceFailed+0x3ff
ffffef09`6e252590 fffff805`8245d04c     : ffffb704`197db010 ffffb704`197db010 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x1f1ce
ffffef09`6e252660 fffff805`8245d9c1     : ffffb704`197db010 ffffb704`197db010 00000000`00000000 00000000`00000000 : stornvme!NVMeControllerInitPart2+0x2a8
ffffef09`6e252760 fffff805`8245bf6f     : 00000000`00000000 ffffb704`197db010 00000000`00000000 ffffb704`13cc6cd0 : stornvme!NVMeControllerReset+0x145
ffffef09`6e252870 fffff805`82143326     : ffffb704`336173c0 ffffb704`198f2050 ffffb704`00000000 00000000`00000000 : stornvme!NVMeControllerAsyncResetWorker+0x1f
ffffef09`6e2528a0 fffff805`8025bbe0     : ffffb704`37d8b950 ffffb704`2ad92630 00000000`00000000 ffffb704`31fe7040 : storport!StorPortWorkItemRoutine+0x46
ffffef09`6e2528d0 fffff805`802d6fd5     : ffffb704`13cc6cd0 ffffb704`19724080 ffffef09`6e252a40 00000000`00000000 : nt!IopProcessWorkItem+0x100
ffffef09`6e252940 fffff805`8036db37     : ffffb704`19724080 00000000`000001d8 ffffb704`19724080 fffff805`802d6e80 : nt!ExpWorkerThread+0x155
ffffef09`6e252b30 fffff805`8041d554     : ffffcb80`97691180 ffffb704`19724080 fffff805`8036dae0 00000000`00000000 : nt!PspSystemThreadStartup+0x57
ffffef09`6e252b80 00000000`00000000     : ffffef09`6e253000 ffffef09`6e24c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

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

Edited May 7 by Murasaki
made post make more sense

[8385895939]

2 hours ago, Murasaki said:

Seems to be caused by GenuineIntel.sys (which sounds like CPU related?) but also has a stack trace to stornvme.sys

My guess is something is happening between the cpu and your nvme SSD communicating. I suggest you check your NVME SSD's S.M.A.R.T. info with software like CrystalDiskInfo.

  Hide contents

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

Debugging Details:
------------------
CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffef09`6e2520e8 fffff805`8060ef7b     : 00000000`00000124 00000000`00000010 ffffb704`62a7c028 ffffb704`19739b2c : nt!KeBugCheckEx
ffffef09`6e2520f0 fffff805`8060faa3     : ffffb704`2e47b890 ffffb704`2e47b890 ffffb704`19739b00 fffff805`8024a81d : nt!WheaReportHwError+0x37b
ffffef09`6e2521c0 fffff805`8060fbc5     : 00000000`00000000 00000000`000000ba ffffb704`2e47b890 fffff805`802c6064 : nt!WheaHwErrorReportSubmitDeviceDriver+0xf3
ffffef09`6e2521f0 fffff805`821801c8     : ffffef09`6e252430 ffffef09`6e252430 ffffb704`198f2050 ffffb704`140102c0 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffef09`6e252250 fffff805`821798b3     : 00000000`00000000 00000000`00000000 ffffb704`198f21a0 00000000`00000000 : storport!StorpWheaReportError+0xb8
ffffef09`6e2522e0 fffff805`8215c36e     : ffffb704`37d8b900 ffffb704`197db010 00000000`00000000 fffff805`82459a4c : storport!StorpMarkDeviceFailed+0x3ff
ffffef09`6e252590 fffff805`8245d04c     : ffffb704`197db010 ffffb704`197db010 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x1f1ce
ffffef09`6e252660 fffff805`8245d9c1     : ffffb704`197db010 ffffb704`197db010 00000000`00000000 00000000`00000000 : stornvme!NVMeControllerInitPart2+0x2a8
ffffef09`6e252760 fffff805`8245bf6f     : 00000000`00000000 ffffb704`197db010 00000000`00000000 ffffb704`13cc6cd0 : stornvme!NVMeControllerReset+0x145
ffffef09`6e252870 fffff805`82143326     : ffffb704`336173c0 ffffb704`198f2050 ffffb704`00000000 00000000`00000000 : stornvme!NVMeControllerAsyncResetWorker+0x1f
ffffef09`6e2528a0 fffff805`8025bbe0     : ffffb704`37d8b950 ffffb704`2ad92630 00000000`00000000 ffffb704`31fe7040 : storport!StorPortWorkItemRoutine+0x46
ffffef09`6e2528d0 fffff805`802d6fd5     : ffffb704`13cc6cd0 ffffb704`19724080 ffffef09`6e252a40 00000000`00000000 : nt!IopProcessWorkItem+0x100
ffffef09`6e252940 fffff805`8036db37     : ffffb704`19724080 00000000`000001d8 ffffb704`19724080 fffff805`802d6e80 : nt!ExpWorkerThread+0x155
ffffef09`6e252b30 fffff805`8041d554     : ffffcb80`97691180 ffffb704`19724080 fffff805`8036dae0 00000000`00000000 : nt!PspSystemThreadStartup+0x57
ffffef09`6e252b80 00000000`00000000     : ffffef09`6e253000 ffffef09`6e24c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

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

 

Really helpful and perhaps related to the following:

• I have two 980 Pro 1TBs but one gets corrupted frequently no matter what I do with it so I think it's defective.
• I downloaded the software you mentioned and I am not sure if there's anything glaring here, my C drive is my 'good' SSD and my D drive is the one that seems to corrupt when downloading files. Is there anything here you'd see that doesn't look right?

Two other questions I have:

• Are the warnings in my log (hundreds of records every few seconds) also pointing to the NVME drive? It shows some warning with PCI Express Port (A corrected hardware error has occurred, Primary Device Name:PCI\VEN_8086&DEV_A74D&SUBSYS_86941043&REV_01)
• is there anything in the logs that would point to which drive my computer has an issue or is the stornvme.sys error not in direct relation to a drive?

Thanks for this! Going to take out that second NVME and see if this stops the power offs / errors in event logger.

[Murasaki]

1 hour ago, 8385895939 said:

~stuff~

SMART values look alright in general minus the last value for the D drive NVME. I've observed this on my only NVME drive I've ever had which also had thousands of log entries. It ended up suddenly dying on me eventually (doesnt mean it will happen to you ofcourse). Since you mentioned it gets corrupted frequently then there really might be an issue with this specific SSD so removing it temporarily is a good idea to troubleshoot this issue. If the drive is still in warranty you could look into getting it replaced.

 

1 hour ago, 8385895939 said:

Two other questions I have:

• Are the warnings in my log (hundreds of records every few seconds) also pointing to the NVME drive? It shows some warning with PCI Express Port (A corrected hardware error has occurred, Primary Device Name:PCI\VEN_8086&DEV_A74D&SUBSYS_86941043&REV_01)
• is there anything in the logs that would point to which drive my computer has an issue or is the stornvme.sys error not in direct relation to a drive?

 

Ah sorry I didn't look at the eventviewer log. I've managed to track down VEN_8086&DEV_A74D and that points to "Raptor Lake PCIe 4.0 Graphics Port" but I'm not sure if thats accurate or related to PCI lanes on M.2 ports. The stornvme.sys trace only helped figure out it was something to do with an NVME device. I haven't managed to get any information from the dump/logs pointing to a specific drive.

 

Good luck.

[8385895939]

On 5/7/2024 at 3:50 PM, Murasaki said:

SMART values look alright in general minus the last value for the D drive NVME. I've observed this on my only NVME drive I've ever had which also had thousands of log entries. It ended up suddenly dying on me eventually (doesnt mean it will happen to you ofcourse). Since you mentioned it gets corrupted frequently then there really might be an issue with this specific SSD so removing it temporarily is a good idea to troubleshoot this issue. If the drive is still in warranty you could look into getting it replaced.

 

Ah sorry I didn't look at the eventviewer log. I've managed to track down VEN_8086&DEV_A74D and that points to "Raptor Lake PCIe 4.0 Graphics Port" but I'm not sure if thats accurate or related to PCI lanes on M.2 ports. The stornvme.sys trace only helped figure out it was something to do with an NVME device. I haven't managed to get any information from the dump/logs pointing to a specific drive.

 

Good luck.

@murasaki and anyone reading this thread in the future - found the fix! Yes I did have a bad SSD but the power offs still kept happening. The error pointing to VEN_8086&DEV_A74D is due to a terrible setting / management of power to the PCI root controller in ASUS mobos. I found several posts when I searched the device name and my mobos name. This issue completely stopped when I turned off PCI express native power management in ASUS bios. Its enabled by default.

i still marked your answer as the solution because when I removed the drive it did stop instability but the true root cause was indeed this setting on top of the corrupted drive. Thanks for helping to narrow down my thinking, you are awesome!

[Murasaki]

27 minutes ago, 8385895939 said:

@murasaki and anyone reading this thread in the future - found the fix! Yes I did have a bad SSD but the power offs still kept happening. The error pointing to VEN_8086&DEV_A74D is due to a terrible setting / management of power to the PCI root controller in ASUS mobos. I found several posts when I searched the device name and my mobos name. This issue completely stopped when I turned off PCI express native power management in ASUS bios. Its enabled by default.

i still marked your answer as the solution because when I removed the drive it did stop instability but the true root cause was indeed this setting on top of the corrupted drive. Thanks for helping to narrow down my thinking, you are awesome!

Glad its solved~ Thanks for sharing! Have a good one and don't look at the title under my name.