*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8046d173358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202
SYSTEM_MANUFACTURER: LENOVO
SYSTEM_PRODUCT_NAME: 20217
SYSTEM_SKU: LENOVO_BI_IDEAPAD
SYSTEM_VERSION: Lenovo IdeaPad Y510P
BIOS_VENDOR: LENOVO
BIOS_VERSION: 74CN44WW(V3.05)
BIOS_DATE: 09/18/2013
BASEBOARD_MANUFACTURER: LENOVO
BASEBOARD_PRODUCT: VIQY0Y1
BASEBOARD_VERSION: 31900004STD
DUMP_TYPE: 2
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8046d173358
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
CPU_COUNT: 8
CPU_MHZ: 95a
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3c
CPU_STEPPING: 3
CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 25'00000000 (cache) 25'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
ANALYSIS_SESSION_HOST: DESKTOP-18V31A3
ANALYSIS_SESSION_TIME: 12-11-2019 17:33:10.0634
ANALYSIS_VERSION: 10.0.18362.1 x86fre
LAST_CONTROL_TRANSFER: from fffff8046cdeeac1 to fffff8046cdc14e0
STACK_TEXT:
fffff804`70e18b08 fffff804`6cdeeac1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff804`6d173358 : nt!KeBugCheckEx
fffff804`70e18b10 fffff804`6cc1f897 : 00000793`5090fca4 fffff804`68226180 00000000`00000286 fffff804`70e11640 : nt!KeAccumulateTicks+0x1cc061
fffff804`70e18b70 fffff804`6cb601e1 : ffff890f`0f4b7010 fffff804`6cbcbfe0 fffff804`70e116c0 fffff804`6cbcc090 : nt!KeClockInterruptNotify+0xc07
fffff804`70e18f30 fffff804`6cc02a25 : fffff804`6cbcbfe0 00000000`0000000c ffff5aae`b6630685 00000000`00002140 : hal!HalpTimerClockIpiRoutine+0x21
fffff804`70e18f60 fffff804`6cdc2f7a : fffff804`70e116c0 fffff804`6cbcbfe0 fffff804`70e11b00 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff804`70e18fb0 fffff804`6cdc34e7 : ffff890f`0f48a000 fffff804`84f82eb5 ffff890f`084298a0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff804`70e11640 fffff804`84f57151 : fffff804`84f7a1e4 ffff890f`0f48a000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff804`70e117d8 fffff804`84f7a1e4 : ffff890f`0f48a000 00000000`00000000 00000000`00000000 fffff804`70e11b00 : nvlddmkm+0x1e7151
fffff804`70e117e0 ffff890f`0f48a000 : 00000000`00000000 00000000`00000000 fffff804`70e11b00 ffff890f`00000020 : nvlddmkm+0x20a1e4
fffff804`70e117e8 00000000`00000000 : 00000000`00000000 fffff804`70e11b00 ffff890f`00000020 fffff804`70e11820 : 0xffff890f`0f48a000
THREAD_SHA1_HASH_MOD_FUNC: 588f764390cf3a7f40526e2ad7327176945e52e0
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 102c2a1e7a8d7f144ed481f27c5a8639f15ceb25
THREAD_SHA1_HASH_MOD: b65638c546229c8b9c3693c2a82ed471ad9bee32
FOLLOWUP_IP:
nvlddmkm+1e7151
fffff804`84f57151 c3 ret
FAULT_INSTR_CODE: 8accccc3
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: nvlddmkm+1e7151
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5bee0308
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1e7151
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
PRIMARY_PROBLEM_CLASS: 0x133_ISR_nvlddmkm!unknown_function
TARGET_TIME: 2019-12-09T17:23:05.000Z
OSBUILD: 18362
OSSERVICEPACK: 476
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2011-12-30 02:28:41
BUILDDATESTAMP_STR: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: 16a51
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x133_isr_nvlddmkm!unknown_function
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
---------
