Mar 7, 2024
1
0
10
I got windbg installed and opened my most recent minidump, which was actually only on 2/20, and i've had crashes since then that i guess didn't produce a minidump?. When i click !analyze -v it says i have a DPC_WATCHDOG_VIOLATION (133). Here's the FULL copy paste, including me clicking "!analyze -v" and then "lmvm stornvme" when i clicked on "stornvme". I'm working on finding a way to upload my minidump files to dropbox or something but it's not working very well, so i'll just stick with copy/paste.


this is causing blue screen crashes. I had thought it was my Razer Synapse software, but I need it for my peripherals. It happens when my computer is sleeping and come back to the PC and wiggle the mouse to wake up, and the peripherals lights don't turn on.

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

EnableRedirectToV8JsProvider : false

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

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

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

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

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


Loading Dump File [C:\Windows\Minidump\022024-10125-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff806`4d200000 PsLoadedModuleList = 0xfffff806`4de2a770
Debug session time: Tue Feb 20 16:59:16.994 2024 (UTC - 8:00)
System Uptime: 2 days 7:22:23.406
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols

Loading unloaded module list
.....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`4d5fd5b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb381`4313dc90=0000000000000133
2: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff8064defb320, 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: 3530

Key : Analysis.Elapsed.mSec
Value: 4715

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x133

Key : Bugcheck.Code.TargetModel
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: fffff8064defb320

FILE_IN_CAB: 022024-10125-01.dmp

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: ffff840a34e3ee40 -- (.trap 0xffff840a34e3ee40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000008e1653cd rbx=0000000000000000 rcx=0000000000000002
rdx=00000000000185e3 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8064d565523 rsp=ffff840a34e3efd8 rbp=000000000036ee83
r8=00000000000003e8 r9=ffffa00f1a563020 r10=fffff8064d565520
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!HalpTscQueryCounterOrdered+0x3:
fffff806`4d565523 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:
ffffb381`4313dc88 fffff806`4d637812 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffb381`4313dc90 fffff806`4d45945d : 000185e3`8e167135 ffffb381`43124180 00000000`00000246 00000000`00c2abda : nt!KeAccumulateTicks+0x1e15d2
ffffb381`4313dcf0 fffff806`4d4519b1 : 00000000`00000000 00000000`0074087b ffffb381`43124180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffb381`4313dd40 fffff806`4d453873 : ffffb381`43124180 00000000`00000000 fffff806`4de31880 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffb381`4313de80 fffff806`4d450a82 : ffff840a`34e3ee40 ffff840a`34e3eec0 ffff840a`34e3ee00 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffffb381`4313df30 fffff806`4d500825 : 000001d0`227d9897 ffffa00f`19503200 ffffa00f`195032b0 ffffa2be`d6a62724 : nt!HalpTimerClockInterrupt+0xe2
ffffb381`4313df60 fffff806`4d5ff59a : ffff840a`34e3eec0 ffffa00f`19503200 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffb381`4313dfb0 fffff806`4d5ffda7 : 00000000`000003d3 fffff806`4d5ffdb4 00000000`00000000 fffff806`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff840a`34e3ee40 fffff806`4d565523 : fffff806`4d450db0 ffff846e`008f44de 00000000`ffffffff ffff6f3d`dd6017f1 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff840a`34e3efd8 fffff806`4d450db0 : ffff846e`008f44de 00000000`ffffffff ffff6f3d`dd6017f1 00000000`00000000 : nt!HalpTscQueryCounterOrdered+0x3
ffff840a`34e3efe0 fffff806`4f1f8478 : 00000000`00000000 ffff840a`34e3f109 ffff840a`34e3f180 00000000`c1000002 : nt!KeStallExecutionProcessor+0x120
ffff840a`34e3f060 fffff806`4f1d0db6 : 00000000`00000000 fffff806`4f1cf2b6 ffffa00f`1a574000 00000000`00000000 : storport!StorDelayExecution+0xdc
ffff840a`34e3f0a0 fffff806`4f29ccf0 : ffffa00f`1a563020 ffffa00f`1a563020 00000000`000003e8 ffffa00f`1a563020 : storport!StorPortExtendedFunction+0x1716
ffff840a`34e3f170 fffff806`4f29c245 : ffffa00f`1a563300 ffffa00f`1a563370 00000000`00000000 00000000`00989680 : stornvme!WaitForCommandCompleteWithCustomTimeout+0xd4
ffff840a`34e3f290 fffff806`4f28e19d : 00000002`a6efd000 ffffa00f`29afb000 00000001`c00fb000 01da6461`2bcad138 : stornvme!NVMeSyncHostTime+0x179
ffff840a`34e3f2d0 fffff806`4f28e3fa : ffffa00f`1a563020 00000000`00000000 00000000`00000000 ffff840a`34e3f569 : stornvme!NVMeControllerInitPart3+0x189
ffff840a`34e3f370 fffff806`4f2861b4 : ffff840a`34e3f3b8 ffffa00f`1a563020 ffff840a`34e3f410 ffff840a`34e3f430 : stornvme!NVMeControllerPowerUp+0x62
ffff840a`34e3f3a0 fffff806`4f1d3dc9 : 000001d0`169112c0 00000000`c00000bb ffffa00f`1a56c9b0 00000000`00000000 : stornvme!NVMeHwAdapterControl+0x134
ffff840a`34e3f430 fffff806`4f1fec37 : 00000000`c00000bb 00000000`00000000 ffffa00f`00000002 ffff840a`34e3f480 : storport!RaCallMiniportAdapterControl+0x25
ffff840a`34e3f460 fffff806`4f1e8b7d : ffffa00f`1a56c9b0 ffffa00f`1a51d050 ffffa00f`1a56c9b0 ffffa00f`1a49e060 : storport!RaidAdapterSendPowerToMiniport+0x6b
ffff840a`34e3f4b0 fffff806`4d45d2a5 : ffffa00f`1a56cb5b ffffa00f`1a56c9b0 ffffa00f`1a51d050 00000000`80080000 : storport!RaidAdapterPowerUpDeviceCompletion+0x140dd
ffff840a`34e3f4f0 fffff806`4d45d0e7 : ffffa00f`1a56c9b0 ffff840a`34e3f600 00000000`00000000 ffffa00f`1a49e1b0 : nt!IopfCompleteRequest+0x1a5
ffff840a`34e3f5d0 fffff806`4eef22e0 : ffffa00f`1a49e718 00000000`00000000 0000019b`0000000b fffff806`4ef24000 : nt!IofCompleteRequest+0x17
ffff840a`34e3f600 fffff806`4d4af389 : ffffa00f`1a438ea0 fffff806`4eef1e10 fffff806`4eef1e10 ffff840a`34e3fa70 : pci!PciPowerUpDeviceTimerCallback+0x4d0
ffff840a`34e3f700 fffff806`4d4c3a15 : ffffa00f`1a4389e8 00000000`00000001 ffff840a`34e3fa10 ffffa00f`1a4389e8 : nt!KiExpireTimer2+0x429
ffff840a`34e3f810 fffff806`4d4c0fd4 : 00000000`00000000 00000000`00000000 00000000`00000008 00000000`00740598 : nt!KiTimer2Expiration+0x165
ffff840a`34e3f8d0 fffff806`4d601fae : 00000000`00000000 ffffb381`43124180 ffffb381`4312f240 ffffa00f`253c6080 : nt!KiRetireDpcList+0x874
ffff840a`34e3fb60 00000000`00000000 : ffff840a`34e40000 ffff840a`34e39000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: stornvme!WaitForCommandCompleteWithCustomTimeout+d4

MODULE_NAME: stornvme

IMAGE_NAME: stornvme.sys

IMAGE_VERSION: 10.0.19041.4106

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

2: kd> lmvm stornvme
Browse full module list
start end module name
fffff806`4f280000 fffff806`4f2af000 stornvme # (pdb symbols) C:\ProgramData\Dbg\sym\stornvme.pdb\A275F902010A2DC03125B0E31B04C61D1\stornvme.pdb
Loaded symbol image file: stornvme.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\stornvme.sys\10A5D7AB2f000\stornvme.sys
Image path: \SystemRoot\System32\drivers\stornvme.sys
Image name: stornvme.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 10A5D7AB (This is a reproducible build file hash, not a timestamp)
CheckSum: 0003757F
ImageSize: 0002F000
File version: 10.0.19041.4106
Product version: 10.0.19041.4106
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: stornvme.sys
OriginalFilename: stornvme.sys
ProductVersion: 10.0.19041.4106
FileVersion: 10.0.19041.4106 (WinBuild.160101.0800)
FileDescription: Microsoft NVM Express Storport Miniport Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
 
Last edited by a moderator:
That looks as though it's a problem with an NVMe storage drive. M.2 drives do cause niggly issues sometimes if they're not seated properly. Try removing all NVMe drives and reseat them fully. See whether that helps.

If it still BSODs after that then look for the drive vendor's diagnostic tool and run a full diagnostic on the NVMe drive(s).

It's always important to upload the dump file itself to the cloud with a link to it here. Also upload all the dumps you have.