*******************************************************************************
* *
* 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: fffff8071f171358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** 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: 10859
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-NFPVV9V
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 159619
Key : Analysis.Memory.CommitPeak.Mb
Value: 76
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: 19h1_release
Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z
Key : WER.OS.Version
Value: 10.0.18362.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff8071f171358
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff80721c71c10 -- (.trap 0xfffff80721c71c10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=ffffd5867c793502
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8071ec187fe rsp=fffff80721c71da0 rbp=0000000000000000
r8=ffffd5867d7d9e48 r9=0000000000000640 r10=fffff80725028168
r11=fffff80721c71d50 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KzLowerIrql+0x1e:
fffff807`1ec187fe 4883c420 add rsp,20h
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Launcher.exe
DPC_STACK_BASE: FFFFF80721C72FB0
STACK_TEXT:
fffff807`21c79b08 fffff807`1edfd11f : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff807`21c79b10 fffff807`1ec483dc : 000023b7`7f34fab3 fffff807`1a300180 00000000`002e0d3a 00000000`002e0d3a : nt!KeAccumulateTicks+0x1b18ff
fffff807`21c79b70 fffff807`1eb5d567 : 00000000`00000000 fffff807`21c71c10 fffff807`21c71c90 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
fffff807`21c79f30 fffff807`1ed377d5 : 0000006d`d002a210 fffff807`1ebcc100 fffff807`1ebcc1b0 fffff807`21c71cb0 : hal+0x1567
fffff807`21c79f60 fffff807`1edc441a : fffff807`21c71c90 fffff807`1ebcc100 00000000`00000000 00000000`0010a01c : nt!KiCallInterruptServiceRoutine+0xa5
fffff807`21c79fb0 fffff807`1edc4987 : ffffd586`7d49f000 00000000`00000000 ffffd586`7d7d9000 ffffd586`7d7d9000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`21c71c10 fffff807`1ec187fe : 00000000`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`21c71da0 fffff807`2507c340 : 00000000`00000000 fffff807`21c71ec8 00000000`00000000 fffff807`2504785a : nt!KzLowerIrql+0x1e
fffff807`21c71dd0 00000000`00000000 : fffff807`21c71ec8 00000000`00000000 fffff807`2504785a ffffd586`00000000 : nvlddmkm+0x29c340
SYMBOL_NAME: nvlddmkm+29c340
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 29c340
FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {15c3af0e-5564-7a80-2e26-65b5115ecc4d}
Followup: MachineOwner
---------
www.techpowerup.com
