Question DPC_WATCHDOG_VIOLATION BSOD after sleep mode or sometimes on restart ?

[bsodbob]

About 2 weeks I'm struggling with BSOD wherever I'm waking PC from sleep mode or sometimes after PC restart. I assume that it started after one of the windows updated in late august along with Gigabyte updates but I wasn't paying any attention and haven't restored it in time, so now I have more updates already installed and no snapshots to recover. Here are recents minidumps

I have already tried updating with Windows Update, Gigabyte Control Center and even manually downloading drivers from Gigabyte website but with no avail.
Also treid scf /scannow, scanning all SSDs chkdsk /f /r and DISM /Online /Cleanup-image /Restorehealth but still having troubles with BSOD.

Also to mention sometimes after BSOD one of the NVMe drives is disabled by windows as if it can not be seen but after another restart it can be located again.

And also there is weird thing in Gigabyte Control Center - it says that my 4090's BIOS can be updated to F2 version, but I already have it. After filling installation bar to 100% and re-opening GCC it again says that update can be installed.

Specs:
Mobo X670 AORUS ELITE AX
GPU gv-n4090wf3-24gd
CPU Ryzen 7950x

Spoiler: Dump 1

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8022acfb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2436

Key : Analysis.Elapsed.mSec
Value: 10463

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x133

Key : Failure.Bucket
Value: 0x133_DPC_stornvme!WaitForCommandCompleteWithCustomTimeout

Key : Failure.Hash
Value: {a5bb45e0-648c-41a5-ef61-87d76ff0d84e}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8022acfb320

FILE_IN_CAB: 091423-16937-01.dmp

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: ffffb60182bae8c0 -- (.trap 0xffffb60182bae8c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000084eb53bf rbx=0000000000000000 rcx=0000000000000019
rdx=0000000000007192 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8022a3654f3 rsp=ffffb60182baea58 rbp=0000000000448923
r8=00000000000003e8 r9=ffffa10408740020 r10=0000fffff8022a36
r11=ffff80fd9e600000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy
nt!HalpTscQueryCounterOrdered+0x3:
fffff802`2a3654f3 48c1e220 shl rdx,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9100`35e93c88 fffff802`2a430ee0 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9100`35e93c90 fffff802`2a248dbd : 00007192`84eb6fb2 ffff9100`35e40180 00000000`00000246 00000000`003a9b36 : nt!KeAccumulateTicks+0x1eb340
ffff9100`35e93cf0 fffff802`2a23fe41 : 00000000`003a9600 00000000`0022ee9c ffff9100`35e40180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffff9100`35e93d40 fffff802`2a2431d3 : ffff9100`35e40180 00000000`00000000 fffff802`2ac31558 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffff9100`35e93e80 fffff802`2a24aa62 : ffffb601`82bae8c0 ffffb601`82bae940 ffffb601`82bae900 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffff9100`35e93f30 fffff802`2a2a7765 : 0000008b`bc74fa12 ffffa104`05361ea0 ffffa104`05361f50 ffffc2c1`e282b964 : nt!HalpTimerClockInterrupt+0xe2
ffff9100`35e93f60 fffff802`2a3fedca : ffffb601`82bae940 ffffa104`05361ea0 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9100`35e93fb0 fffff802`2a3ff597 : 00000000`00006c98 fffff802`2a3ff5a4 00000000`00000000 fffff802`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffb601`82bae8c0 fffff802`2a3654f3 : fffff802`2a24ad90 ffff9877`cd1c8245 00000000`ffffffff ffff4d9e`40890895 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffb601`82baea58 fffff802`2a24ad90 : ffff9877`cd1c8245 00000000`ffffffff ffff4d9e`40890895 00000000`00000000 : nt!HalpTscQueryCounterOrdered+0x3
ffffb601`82baea60 fffff802`2f698468 : 00000000`00000000 ffffb601`82baeb89 ffffb601`82baec00 00000000`c1000002 : nt!KeStallExecutionProcessor+0x120
ffffb601`82baeae0 fffff802`2f670d86 : 00000000`00000000 fffff802`2f66f286 ffffa104`08777000 00000000`00000000 : storport!StorDelayExecution+0xdc
ffffb601`82baeb20 fffff802`2f73ccf0 : ffffa104`08740020 ffffa104`08740020 00000000`000003e8 ffffa104`08740020 : storport!StorPortExtendedFunction+0x1716
ffffb601`82baebf0 fffff802`2f73c245 : ffffa104`08740300 ffffa104`08740370 00000000`00000000 00000000`00989680 : stornvme!WaitForCommandCompleteWithCustomTimeout+0xd4
ffffb601`82baed10 fffff802`2f72e19d : 0000000f`f46f4000 ffffa104`18cfd000 00000002`676fd000 01d9e6cd`4a664d8b : stornvme!NVMeSyncHostTime+0x179
ffffb601`82baed50 fffff802`2f72e3fa : ffffa104`08740020 00000000`00000000 00000000`00000000 ffffb601`82baefe9 : stornvme!NVMeControllerInitPart3+0x189
ffffb601`82baedf0 fffff802`2f7261b4 : ffffb601`82baee38 ffffa104`08740020 ffffb601`82baee90 ffffb601`82baeeb0 : stornvme!NVMeControllerPowerUp+0x62
ffffb601`82baee20 fffff802`2f673d98 : 0000008b`b085eb54 00000000`c00000bb ffffa104`0876fab0 ffffa104`06cffa68 : stornvme!NVMeHwAdapterControl+0x134
ffffb601`82baeeb0 fffff802`2f69ec27 : 00000000`c00000bb 00000000`00000000 ffffa104`00000002 ffffb601`82baef00 : storport!RaCallMiniportAdapterControl+0x24
ffffb601`82baeee0 fffff802`2f688b23 : ffffa104`0876fab0 ffffa104`08766050 ffffa104`0876fab0 ffffa104`085ee120 : storport!RaidAdapterSendPowerToMiniport+0x6b
ffffb601`82baef30 fffff802`2a2546b5 : ffffa104`0876fc13 ffffa104`0876fab0 ffffa104`08766050 00000000`00000004 : storport!RaidAdapterPowerUpDeviceCompletion+0x14123
ffffb601`82baef70 fffff802`2a2544f7 : ffffa104`0876fab0 00000000`00000000 00000000`00000000 ffffa104`085ee270 : nt!IopfCompleteRequest+0x1a5
ffffb601`82baf050 fffff802`2f1c22e0 : ffffa104`085ee7d8 00000000`00000000 000001ad`0000001d 00000000`ffffff00 : nt!IofCompleteRequest+0x17
ffffb601`82baf080 fffff802`2a2fab29 : ffffa104`075f7870 fffff802`2f1c1e10 fffff802`2f1c1e10 ffffb601`82baf4b0 : pci!PciPowerUpDeviceTimerCallback+0x4d0
ffffb601`82baf180 fffff802`2a24f8a5 : ffffa104`3d6023b8 00000000`00000003 ffffb601`82baf490 ffffa104`3d6023b8 : nt!KiExpireTimer2+0x429
ffffb601`82baf290 fffff802`2a24ce64 : 00000000`00000000 fffff802`2a2f4275 00000000`00000008 00000000`0022ebb8 : nt!KiTimer2Expiration+0x165
ffffb601`82baf350 fffff802`2a40172e : ffffffff`00000000 ffff9100`35e40180 ffff9100`35e4b840 ffffa104`20a760c0 : nt!KiRetireDpcList+0x874
ffffb601`82baf5e0 00000000`00000000 : ffffb601`82bb0000 ffffb601`82ba9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: stornvme!WaitForCommandCompleteWithCustomTimeout+d4

MODULE_NAME: stornvme

IMAGE_NAME: stornvme.sys

IMAGE_VERSION: 10.0.19041.3205

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: d4

FAILURE_BUCKET_ID: 0x133_DPC_stornvme!WaitForCommandCompleteWithCustomTimeout

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a5bb45e0-648c-41a5-ef61-87d76ff0d84e}

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

Spoiler: Dump 2

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff805758fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2593

Key : Analysis.Elapsed.mSec
Value: 5859

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x133

Key : Failure.Bucket
Value: 0x133_DPC_stornvme!WaitForCommandCompleteWithCustomTimeout

Key : Failure.Hash
Value: {a5bb45e0-648c-41a5-ef61-87d76ff0d84e}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff805758fb320

FILE_IN_CAB: 091223-15265-01.dmp

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: ffffb90fd371e8c0 -- (.trap 0xffffb90fd371e8c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ec019fd4 rbx=0000000000000000 rcx=0000000000000010
rdx=000000000000b9b9 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80574f654f3 rsp=ffffb90fd371ea58 rbp=0000000000448925
r8=00000000000003e8 r9=ffffa88e135b9020 r10=0000fffff80574f6
r11=ffffbe7af3c00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy
nt!HalpTscQueryCounterOrdered+0x3:
fffff805`74f654f3 48c1e220 shl rdx,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffce80`0ae5ac88 fffff805`75030ee0 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffce80`0ae5ac90 fffff805`74e48dbd : 0000b9b9`ec01bb40 ffffce80`0ae40180 00000000`00000246 00000000`004a4eb4 : nt!KeAccumulateTicks+0x1eb340
ffffce80`0ae5acf0 fffff805`74e3fe41 : 00000000`004a4900 00000000`002c4a6a ffffce80`0ae40180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffce80`0ae5ad40 fffff805`74e431d3 : ffffce80`0ae40180 00000000`00000000 fffff805`75831528 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffce80`0ae5ae80 fffff805`74e4aa62 : ffffb90f`d371e8c0 ffffb90f`d371e940 ffffb90f`d371e900 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffffce80`0ae5af30 fffff805`74ea7765 : 000000b1`2c79e95a ffffa88e`10162f40 ffffa88e`10162ff0 ffff0eb8`f8b61e2f : nt!HalpTimerClockInterrupt+0xe2
ffffce80`0ae5af60 fffff805`74ffedca : ffffb90f`d371e940 ffffa88e`10162f40 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffce80`0ae5afb0 fffff805`74fff597 : 00000000`00005a6a fffff805`74fff5a4 00000000`00000000 fffff805`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffb90f`d371e8c0 fffff805`74f654f3 : fffff805`74e4ad90 ffffd078`f9e7e1c2 00000000`ffffffff ffff9187`16d44ef7 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffb90f`d371ea58 fffff805`74e4ad90 : ffffd078`f9e7e1c2 00000000`ffffffff ffff9187`16d44ef7 00000000`00000000 : nt!HalpTscQueryCounterOrdered+0x3
ffffb90f`d371ea60 fffff805`7a498468 : 00000000`00000000 ffffb90f`d371eb89 ffffb90f`d371ec00 00000000`c1000002 : nt!KeStallExecutionProcessor+0x120
ffffb90f`d371eae0 fffff805`7a470d86 : 00000000`00000000 fffff805`7a46f286 ffffa88e`13603000 00000000`00000000 : storport!StorDelayExecution+0xdc
ffffb90f`d371eb20 fffff805`7a53ccf0 : ffffa88e`135b9020 ffffa88e`135b9020 00000000`000003e8 ffffa88e`135b9020 : storport!StorPortExtendedFunction+0x1716
ffffb90f`d371ebf0 fffff805`7a53c245 : ffffa88e`135b9300 ffffa88e`135b9370 00000000`00000000 00000000`00989680 : stornvme!WaitForCommandCompleteWithCustomTimeout+0xd4
ffffb90f`d371ed10 fffff805`7a52e19d : 00000015`46cfe000 ffffa88e`5fe52000 00000008`a3a52000 01d9e544`a3b9dded : stornvme!NVMeSyncHostTime+0x179
ffffb90f`d371ed50 fffff805`7a52e3fa : ffffa88e`135b9020 00000000`00000000 00000000`00000000 ffffb90f`d371efe9 : stornvme!NVMeControllerInitPart3+0x189
ffffb90f`d371edf0 fffff805`7a5261b4 : ffffb90f`d371ee38 ffffa88e`135b9020 ffffb90f`d371ee90 ffffb90f`d371eeb0 : stornvme!NVMeControllerPowerUp+0x62
ffffb90f`d371ee20 fffff805`7a473d98 : 000000b1`208b0fb5 00000000`c00000bb ffffa88e`13406a20 ffffa88e`100504a8 : stornvme!NVMeHwAdapterControl+0x134
ffffb90f`d371eeb0 fffff805`7a49ec27 : 00000000`c00000bb 00000000`00000000 ffffa88e`00000002 ffffb90f`d371ef00 : storport!RaCallMiniportAdapterControl+0x24
ffffb90f`d371eee0 fffff805`7a488b23 : ffffa88e`13406a20 ffffa88e`135e6050 ffffa88e`13406a20 ffffa88e`134a7630 : storport!RaidAdapterSendPowerToMiniport+0x6b
ffffb90f`d371ef30 fffff805`74e546b5 : ffffa88e`13406b83 ffffa88e`13406a20 ffffa88e`135e6050 00000000`00000004 : storport!RaidAdapterPowerUpDeviceCompletion+0x14123
ffffb90f`d371ef70 fffff805`74e544f7 : ffffa88e`13406a20 00000000`00000000 00000000`00000000 ffffa88e`134a7780 : nt!IopfCompleteRequest+0x1a5
ffffb90f`d371f050 fffff805`79fc22e0 : ffffa88e`134a7ce8 00000000`00000000 000000f6`0000002e 00000000`00000000 : nt!IofCompleteRequest+0x17
ffffb90f`d371f080 fffff805`74efab29 : ffffa88e`125ff030 fffff805`79fc1e10 fffff805`79fc1e10 ffffb90f`d371f4d0 : pci!PciPowerUpDeviceTimerCallback+0x4d0
ffffb90f`d371f180 fffff805`74e4f8a5 : ffffb90f`d371f2c8 00000000`00000001 ffffb90f`d371f490 ffffa88e`125ff048 : nt!KiExpireTimer2+0x429
ffffb90f`d371f290 fffff805`74e4ce64 : 00000000`00000000 fffff805`74ef4275 00000000`00000029 00000000`002c4786 : nt!KiTimer2Expiration+0x165
ffffb90f`d371f350 fffff805`7500172e : ffffffff`00000000 ffffce80`0ae40180 ffffce80`0ae4b840 ffffa88e`3fec3080 : nt!KiRetireDpcList+0x874
ffffb90f`d371f5e0 00000000`00000000 : ffffb90f`d3720000 ffffb90f`d3719000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: stornvme!WaitForCommandCompleteWithCustomTimeout+d4

MODULE_NAME: stornvme

IMAGE_NAME: stornvme.sys

IMAGE_VERSION: 10.0.19041.3205

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: d4

FAILURE_BUCKET_ID: 0x133_DPC_stornvme!WaitForCommandCompleteWithCustomTimeout

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a5bb45e0-648c-41a5-ef61-87d76ff0d84e}

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

 

[Bob.B]

About 2 weeks I'm struggling with BSOD wherever I'm waking PC from sleep mode or sometimes after PC restart. I assume that it started after one of the windows updated in late august along with Gigabyte updates but I wasn't paying any attention and haven't restored it in time, so now I have more updates already installed and no snapshots to recover. Here are recents minidumps

I have already tried updating with Windows Update, Gigabyte Control Center and even manually downloading drivers from Gigabyte website but with no avail.
Also treid scf /scannow, scanning all SSDs chkdsk /f /r and DISM /Online /Cleanup-image /Restorehealth but still having troubles with BSOD.

Also to mention sometimes after BSOD one of the NVMe drives is disabled by windows as if it can not be seen but after another restart it can be located again.

And also there is weird thing in Gigabyte Control Center - it says that my 4090's BIOS can be updated to F2 version, but I already have it. After filling installation bar to 100% and re-opening GCC it again says that update can be installed.

Specs:
Mobo X670 AORUS ELITE AX
GPU gv-n4090wf3-24gd
CPU Ryzen 7950x

Spoiler: Dump 1

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8022acfb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2436

Key : Analysis.Elapsed.mSec
Value: 10463

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x133

Key : Failure.Bucket
Value: 0x133_DPC_stornvme!WaitForCommandCompleteWithCustomTimeout

Key : Failure.Hash
Value: {a5bb45e0-648c-41a5-ef61-87d76ff0d84e}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8022acfb320

FILE_IN_CAB: 091423-16937-01.dmp

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: ffffb60182bae8c0 -- (.trap 0xffffb60182bae8c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000084eb53bf rbx=0000000000000000 rcx=0000000000000019
rdx=0000000000007192 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8022a3654f3 rsp=ffffb60182baea58 rbp=0000000000448923
r8=00000000000003e8 r9=ffffa10408740020 r10=0000fffff8022a36
r11=ffff80fd9e600000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy
nt!HalpTscQueryCounterOrdered+0x3:
fffff802`2a3654f3 48c1e220 shl rdx,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff9100`35e93c88 fffff802`2a430ee0 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9100`35e93c90 fffff802`2a248dbd : 00007192`84eb6fb2 ffff9100`35e40180 00000000`00000246 00000000`003a9b36 : nt!KeAccumulateTicks+0x1eb340
ffff9100`35e93cf0 fffff802`2a23fe41 : 00000000`003a9600 00000000`0022ee9c ffff9100`35e40180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffff9100`35e93d40 fffff802`2a2431d3 : ffff9100`35e40180 00000000`00000000 fffff802`2ac31558 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffff9100`35e93e80 fffff802`2a24aa62 : ffffb601`82bae8c0 ffffb601`82bae940 ffffb601`82bae900 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffff9100`35e93f30 fffff802`2a2a7765 : 0000008b`bc74fa12 ffffa104`05361ea0 ffffa104`05361f50 ffffc2c1`e282b964 : nt!HalpTimerClockInterrupt+0xe2
ffff9100`35e93f60 fffff802`2a3fedca : ffffb601`82bae940 ffffa104`05361ea0 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9100`35e93fb0 fffff802`2a3ff597 : 00000000`00006c98 fffff802`2a3ff5a4 00000000`00000000 fffff802`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffb601`82bae8c0 fffff802`2a3654f3 : fffff802`2a24ad90 ffff9877`cd1c8245 00000000`ffffffff ffff4d9e`40890895 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffb601`82baea58 fffff802`2a24ad90 : ffff9877`cd1c8245 00000000`ffffffff ffff4d9e`40890895 00000000`00000000 : nt!HalpTscQueryCounterOrdered+0x3
ffffb601`82baea60 fffff802`2f698468 : 00000000`00000000 ffffb601`82baeb89 ffffb601`82baec00 00000000`c1000002 : nt!KeStallExecutionProcessor+0x120
ffffb601`82baeae0 fffff802`2f670d86 : 00000000`00000000 fffff802`2f66f286 ffffa104`08777000 00000000`00000000 : storport!StorDelayExecution+0xdc
ffffb601`82baeb20 fffff802`2f73ccf0 : ffffa104`08740020 ffffa104`08740020 00000000`000003e8 ffffa104`08740020 : storport!StorPortExtendedFunction+0x1716
ffffb601`82baebf0 fffff802`2f73c245 : ffffa104`08740300 ffffa104`08740370 00000000`00000000 00000000`00989680 : stornvme!WaitForCommandCompleteWithCustomTimeout+0xd4
ffffb601`82baed10 fffff802`2f72e19d : 0000000f`f46f4000 ffffa104`18cfd000 00000002`676fd000 01d9e6cd`4a664d8b : stornvme!NVMeSyncHostTime+0x179
ffffb601`82baed50 fffff802`2f72e3fa : ffffa104`08740020 00000000`00000000 00000000`00000000 ffffb601`82baefe9 : stornvme!NVMeControllerInitPart3+0x189
ffffb601`82baedf0 fffff802`2f7261b4 : ffffb601`82baee38 ffffa104`08740020 ffffb601`82baee90 ffffb601`82baeeb0 : stornvme!NVMeControllerPowerUp+0x62
ffffb601`82baee20 fffff802`2f673d98 : 0000008b`b085eb54 00000000`c00000bb ffffa104`0876fab0 ffffa104`06cffa68 : stornvme!NVMeHwAdapterControl+0x134
ffffb601`82baeeb0 fffff802`2f69ec27 : 00000000`c00000bb 00000000`00000000 ffffa104`00000002 ffffb601`82baef00 : storport!RaCallMiniportAdapterControl+0x24
ffffb601`82baeee0 fffff802`2f688b23 : ffffa104`0876fab0 ffffa104`08766050 ffffa104`0876fab0 ffffa104`085ee120 : storport!RaidAdapterSendPowerToMiniport+0x6b
ffffb601`82baef30 fffff802`2a2546b5 : ffffa104`0876fc13 ffffa104`0876fab0 ffffa104`08766050 00000000`00000004 : storport!RaidAdapterPowerUpDeviceCompletion+0x14123
ffffb601`82baef70 fffff802`2a2544f7 : ffffa104`0876fab0 00000000`00000000 00000000`00000000 ffffa104`085ee270 : nt!IopfCompleteRequest+0x1a5
ffffb601`82baf050 fffff802`2f1c22e0 : ffffa104`085ee7d8 00000000`00000000 000001ad`0000001d 00000000`ffffff00 : nt!IofCompleteRequest+0x17
ffffb601`82baf080 fffff802`2a2fab29 : ffffa104`075f7870 fffff802`2f1c1e10 fffff802`2f1c1e10 ffffb601`82baf4b0 : pci!PciPowerUpDeviceTimerCallback+0x4d0
ffffb601`82baf180 fffff802`2a24f8a5 : ffffa104`3d6023b8 00000000`00000003 ffffb601`82baf490 ffffa104`3d6023b8 : nt!KiExpireTimer2+0x429
ffffb601`82baf290 fffff802`2a24ce64 : 00000000`00000000 fffff802`2a2f4275 00000000`00000008 00000000`0022ebb8 : nt!KiTimer2Expiration+0x165
ffffb601`82baf350 fffff802`2a40172e : ffffffff`00000000 ffff9100`35e40180 ffff9100`35e4b840 ffffa104`20a760c0 : nt!KiRetireDpcList+0x874
ffffb601`82baf5e0 00000000`00000000 : ffffb601`82bb0000 ffffb601`82ba9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: stornvme!WaitForCommandCompleteWithCustomTimeout+d4

MODULE_NAME: stornvme

IMAGE_NAME: stornvme.sys

IMAGE_VERSION: 10.0.19041.3205

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: d4

FAILURE_BUCKET_ID: 0x133_DPC_stornvme!WaitForCommandCompleteWithCustomTimeout

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a5bb45e0-648c-41a5-ef61-87d76ff0d84e}

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

Spoiler: Dump 2

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff805758fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2593

Key : Analysis.Elapsed.mSec
Value: 5859

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x133

Key : Failure.Bucket
Value: 0x133_DPC_stornvme!WaitForCommandCompleteWithCustomTimeout

Key : Failure.Hash
Value: {a5bb45e0-648c-41a5-ef61-87d76ff0d84e}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff805758fb320

FILE_IN_CAB: 091223-15265-01.dmp

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: ffffb90fd371e8c0 -- (.trap 0xffffb90fd371e8c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ec019fd4 rbx=0000000000000000 rcx=0000000000000010
rdx=000000000000b9b9 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80574f654f3 rsp=ffffb90fd371ea58 rbp=0000000000448925
r8=00000000000003e8 r9=ffffa88e135b9020 r10=0000fffff80574f6
r11=ffffbe7af3c00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy
nt!HalpTscQueryCounterOrdered+0x3:
fffff805`74f654f3 48c1e220 shl rdx,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffce80`0ae5ac88 fffff805`75030ee0 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffce80`0ae5ac90 fffff805`74e48dbd : 0000b9b9`ec01bb40 ffffce80`0ae40180 00000000`00000246 00000000`004a4eb4 : nt!KeAccumulateTicks+0x1eb340
ffffce80`0ae5acf0 fffff805`74e3fe41 : 00000000`004a4900 00000000`002c4a6a ffffce80`0ae40180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffce80`0ae5ad40 fffff805`74e431d3 : ffffce80`0ae40180 00000000`00000000 fffff805`75831528 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffce80`0ae5ae80 fffff805`74e4aa62 : ffffb90f`d371e8c0 ffffb90f`d371e940 ffffb90f`d371e900 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffffce80`0ae5af30 fffff805`74ea7765 : 000000b1`2c79e95a ffffa88e`10162f40 ffffa88e`10162ff0 ffff0eb8`f8b61e2f : nt!HalpTimerClockInterrupt+0xe2
ffffce80`0ae5af60 fffff805`74ffedca : ffffb90f`d371e940 ffffa88e`10162f40 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffce80`0ae5afb0 fffff805`74fff597 : 00000000`00005a6a fffff805`74fff5a4 00000000`00000000 fffff805`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffb90f`d371e8c0 fffff805`74f654f3 : fffff805`74e4ad90 ffffd078`f9e7e1c2 00000000`ffffffff ffff9187`16d44ef7 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffb90f`d371ea58 fffff805`74e4ad90 : ffffd078`f9e7e1c2 00000000`ffffffff ffff9187`16d44ef7 00000000`00000000 : nt!HalpTscQueryCounterOrdered+0x3
ffffb90f`d371ea60 fffff805`7a498468 : 00000000`00000000 ffffb90f`d371eb89 ffffb90f`d371ec00 00000000`c1000002 : nt!KeStallExecutionProcessor+0x120
ffffb90f`d371eae0 fffff805`7a470d86 : 00000000`00000000 fffff805`7a46f286 ffffa88e`13603000 00000000`00000000 : storport!StorDelayExecution+0xdc
ffffb90f`d371eb20 fffff805`7a53ccf0 : ffffa88e`135b9020 ffffa88e`135b9020 00000000`000003e8 ffffa88e`135b9020 : storport!StorPortExtendedFunction+0x1716
ffffb90f`d371ebf0 fffff805`7a53c245 : ffffa88e`135b9300 ffffa88e`135b9370 00000000`00000000 00000000`00989680 : stornvme!WaitForCommandCompleteWithCustomTimeout+0xd4
ffffb90f`d371ed10 fffff805`7a52e19d : 00000015`46cfe000 ffffa88e`5fe52000 00000008`a3a52000 01d9e544`a3b9dded : stornvme!NVMeSyncHostTime+0x179
ffffb90f`d371ed50 fffff805`7a52e3fa : ffffa88e`135b9020 00000000`00000000 00000000`00000000 ffffb90f`d371efe9 : stornvme!NVMeControllerInitPart3+0x189
ffffb90f`d371edf0 fffff805`7a5261b4 : ffffb90f`d371ee38 ffffa88e`135b9020 ffffb90f`d371ee90 ffffb90f`d371eeb0 : stornvme!NVMeControllerPowerUp+0x62
ffffb90f`d371ee20 fffff805`7a473d98 : 000000b1`208b0fb5 00000000`c00000bb ffffa88e`13406a20 ffffa88e`100504a8 : stornvme!NVMeHwAdapterControl+0x134
ffffb90f`d371eeb0 fffff805`7a49ec27 : 00000000`c00000bb 00000000`00000000 ffffa88e`00000002 ffffb90f`d371ef00 : storport!RaCallMiniportAdapterControl+0x24
ffffb90f`d371eee0 fffff805`7a488b23 : ffffa88e`13406a20 ffffa88e`135e6050 ffffa88e`13406a20 ffffa88e`134a7630 : storport!RaidAdapterSendPowerToMiniport+0x6b
ffffb90f`d371ef30 fffff805`74e546b5 : ffffa88e`13406b83 ffffa88e`13406a20 ffffa88e`135e6050 00000000`00000004 : storport!RaidAdapterPowerUpDeviceCompletion+0x14123
ffffb90f`d371ef70 fffff805`74e544f7 : ffffa88e`13406a20 00000000`00000000 00000000`00000000 ffffa88e`134a7780 : nt!IopfCompleteRequest+0x1a5
ffffb90f`d371f050 fffff805`79fc22e0 : ffffa88e`134a7ce8 00000000`00000000 000000f6`0000002e 00000000`00000000 : nt!IofCompleteRequest+0x17
ffffb90f`d371f080 fffff805`74efab29 : ffffa88e`125ff030 fffff805`79fc1e10 fffff805`79fc1e10 ffffb90f`d371f4d0 : pci!PciPowerUpDeviceTimerCallback+0x4d0
ffffb90f`d371f180 fffff805`74e4f8a5 : ffffb90f`d371f2c8 00000000`00000001 ffffb90f`d371f490 ffffa88e`125ff048 : nt!KiExpireTimer2+0x429
ffffb90f`d371f290 fffff805`74e4ce64 : 00000000`00000000 fffff805`74ef4275 00000000`00000029 00000000`002c4786 : nt!KiTimer2Expiration+0x165
ffffb90f`d371f350 fffff805`7500172e : ffffffff`00000000 ffffce80`0ae40180 ffffce80`0ae4b840 ffffa88e`3fec3080 : nt!KiRetireDpcList+0x874
ffffb90f`d371f5e0 00000000`00000000 : ffffb90f`d3720000 ffffb90f`d3719000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: stornvme!WaitForCommandCompleteWithCustomTimeout+d4

MODULE_NAME: stornvme

IMAGE_NAME: stornvme.sys

IMAGE_VERSION: 10.0.19041.3205

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: d4

FAILURE_BUCKET_ID: 0x133_DPC_stornvme!WaitForCommandCompleteWithCustomTimeout

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a5bb45e0-648c-41a5-ef61-87d76ff0d84e}

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

What psu do you have ......make and model?

Boot up a copy of memtest86 and let it run no errors allowed.

 

[gardenman]

Also to mention sometimes after BSOD one of the NVMe drives is disabled by windows as if it can not be seen but after another restart it can be located again.

Both dumps mention stornvme.sys.

Key : Failure.Bucket
Value: 0x133_DPC_stornvme!WaitForCommandCompleteWithCustomTimeout

IMAGE_NAME: stornvme.sys

I would test your drives. If you have multiple drives and can remove some of them, I would do that temporarily for testing purposes to see if it helps.

Most times the drive maker will have tools for testing.

 

[ubuysa]

It's always better to upload the dump files to the cloud with a link to them here. There is way more to dump analysis than the analyze -v output.

That said, a DPC (a Deferred Procedure Call) is a work item that is typically used to run the back-end of device interrupts. The DPC code is part of the device driver (as is the ISR code that initially handles the interrupt). DPCs are run by a processor when it has no other work to do, but since a DPC effectively locks-out the processor, they are not allowed to run for too long (typically 100 microseconds). If a DPC runs for longer than this the DPC watchdog BSODs the system - because something unexpected is happening.

As above, you can see a call to the stornvme!WaitForCommandCompleteWithCustomTimeout function, this is a component of the Windows stornvme.sys driver, the NVMe storage driver. A little later (you read the stack from the bottom up) we see a call to the storport!StorDelayExecution function to 'delay execution [of this DPC]', (the storport.sys driver is the Windows high-level storage driver), followed by a call to the kernel function nt!KeStallExecutionProcessor - and that's what caused the DPC timeout.

This is also why the NVMe drive doesn't appear until you restart, because Windows has detected a problem with it. Whichever drive that is, that's the one with the problem. Do a web search for the manufacturer's SSD diagnostic tool from the drive manufacturers website.

 

[bsodbob]

Thank you guys for replies and suggestions

What psu do you have ......make and model?
Boot up a copy of memtest86 and let it run no errors allowed.

I have be quiet! DARK POWER PRO 12 1200W Titanium BN311
and here is the memtest86 report, all passed with 0 error

Spoiler: memtest report

MemTest86-Report-20230918-191900.html (47.43KB) - SendSpace.com

Send, Receive, Track & Share Your Big Files with SendSpace file sharing!

www.sendspace.com

Both dumps mention stornvme.sys.
I would test your drives. If you have multiple drives and can remove some of them, I would do that temporarily for testing purposes to see if it helps.
Most times the drive maker will have tools for testing.

I have downloaded tools for properly working Wester Digital drives and updated driver for m2 (however this is not the one which gets disconnected each time). Also downloaded same for Kingston, however it had no driver updates

Spoiler: images wih update

ssd-kf.png (72.63KB) - SendSpace.com

Send, Receive, Track & Share Your Big Files with SendSpace file sharing!

www.sendspace.com

https://www.sendspace.com/file/fmp106 both Kingston and WD

Updating that WD did not solve the problem completely. Now instead of BSOD my PC is stuck on black screen on waking up and never reaches windows or any other screen. No errors in windows logs or anything, as if that part of waking up was not logged. After forced reboot it starts with all programs and browser open as if it went to sleep. Weird.

I'll try removing m2 drives and update soon.

It's always better to upload the dump files to the cloud with a link to them here. There is way more to dump analysis than the analyze -v output.

That said, a DPC (a Deferred Procedure Call) is a work item that is typically used to run the back-end of device interrupts. The DPC code is part of the device driver (as is the ISR code that initially handles the interrupt). DPCs are run by a processor when it has no other work to do, but since a DPC effectively locks-out the processor, they are not allowed to run for too long (typically 100 microseconds). If a DPC runs for longer than this the DPC watchdog BSODs the system - because something unexpected is happening.

As above, you can see a call to the stornvme!WaitForCommandCompleteWithCustomTimeout function, this is a component of the Windows stornvme.sys driver, the NVMe storage driver. A little later (you read the stack from the bottom up) we see a call to the storport!StorDelayExecution function to 'delay execution [of this DPC]', (the storport.sys driver is the Windows high-level storage driver), followed by a call to the kernel function nt!KeStallExecutionProcessor - and that's what caused the DPC timeout.

This is also why the NVMe drive doesn't appear until you restart, because Windows has detected a problem with it. Whichever drive that is, that's the one with the problem. Do a web search for the manufacturer's SSD diagnostic tool from the drive manufacturers website.

Here is the link to the full dump file https://www.sendspace.com/file/3vrabl
As mentioned above diagnostic tool from Kingston hasn't discovered any problem not found any updates for it :<

Also tried downgrading drivers from Gigabyte Control Center, that did not help

 

[ubuysa]

The file.io site is telling me that the (kernel dump) file has been deleted by the owner.

 

[bsodbob]

The file.io site is telling me that the (kernel dump) file has been deleted by the owner.

indeed all files have been deleted :<
here is link for the dump mentioned before https://www.sendspace.com/file/3vrabl

updated all links in previous message

 

[bsodbob]

Update:
I all became much worse.

1. I've remove Kingston M2 then for a while there were no BSOD, shutdowns and restarts were working well.
2. Tried switchig Kingston and WD, in case if there is MB problem. BSOD appeared again on wake up/ reboot
3. Placed M2 ssds as they were and this time on start up there was DRIVER_IRQL_NOT_LESS_OR_EQUAL, here is dump https://www.sendspace.com/file/u1kfiq . Now my LAN does not work, always appears as disabled, updating drivers manually does not help, and also I dont have option to enable it in device management. 💩

In BIOS ran Controller and Namespace test - again test was passed, no problems with Kingston M2 found.

 

[gardenman]

Software tests are not always capable of finding hardware issues.

When moving things around in a PC, often other parts may become dislodged. Be sure everything is seated well.

 

[NinoPino]

After BSOD a drive is not working.... obviously try to disconnect the drive and wait to see if BSOD goes away. If it does then the drive probably is the problem.
Change the drive or try to update drive and/or motherboard firmware.

 

[bsodbob]

Software tests are not always capable of finding hardware issues.

When moving things around in a PC, often other parts may become dislodged. Be sure everything is seated well.

unfortunately LAN device is built into the motherboard by default, nothing external from my side

 

[bsodbob]

Will Windows reinstalling help here?

 

[bsodbob]

One more update.

Ethernet was recovered byt resetting CMOS.

During the tests I've removed GPU and suddenly no BSOD happened during multiple tries using sleeping mode. When all was okay I've plugged GPU and then again PC couln't boot after from sleeping. I also notited in log this error Dump file creation failed due to error during dump creation from volmgr EventID 161.

Changed NVIDIA driver from gaming to studio and now seems like no BSOD again.

So 1200W for 4090 is not enough?

 

[ubuysa]

That's interesting about the graphics card and driver. In the dump you uploaded (the first one you pasted the analyze -v output for), the nvlddmkm.sys driver is involved in the BSOD...

25: kd> !dpx
Start memory scan  : 0xffff910035e93c88 ($csp)
End memory scan    : 0xffff910035e94000 (ISR Stack Base)

0xffff910035e93cb0 : 0xfffff8022acfb320 : nt!KeDpcWatchdogProfileGlobalTriageBlock
0xffff910035e93ce8 : 0xfffff8022a248dbd : nt!KiUpdateRunTime+0x5d
0xffff910035e93d38 : 0xfffff8022a23fe41 : nt!KiUpdateTime+0x4a1
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_8c8de08a85de4474\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
0xffff910035e93e38 : 0xfffff8022a2a3667 : nt!KiSetClockIntervalToMinimumRequested+0x83
0xffff910035e93e48 : 0xfffff8022ac31500 : nt!KiClockTickTraces+0x20
0xffff910035e93e78 : 0xfffff8022a2431d3 : nt!KeClockInterruptNotify+0x2e3
0xffff910035e93e90 : 0xfffff8022ac31558 : nt!KiClockTickTraces+0x78
0xffff910035e93ea0 : 0xfffff8022a3654f0 : nt!HalpTscQueryCounterOrdered
0xffff910035e93ea8 : 0xfffff8022a2a3b0f : nt!KeQueryPerformanceCounter+0x5f
0xffff910035e93ed8 : 0xfffff8022a24abf7 : nt!RtlGetInterruptTimePrecise+0x57
0xffff910035e93f00 : 0xfffff8022f6c9000 : storport!WPP_GLOBAL_Control
0xffff910035e93f10 : 0xfffff8022ac48de8 : nt!HalpClockTickLog+0x108
0xffff910035e93f28 : 0xfffff8022a24aa62 : nt!HalpTimerClockInterrupt+0xe2
0xffff910035e93f58 : 0xfffff8022a2a7765 : nt!KiCallInterruptServiceRoutine+0xa5
0xffff910035e93fa8 : 0xfffff8022a3fedca : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
0xffff910035e93fd8 : 0xfffff8022a3ff597 : nt!KiInterruptDispatchNoLockNoEtw+0x37

This is the reason why dumps should always be uploaded, there is no indication of nvlddmkm.sys in the analyze -v triage output. You have to dig a bit deeper. If the studio driver is working for you then stick with it.