DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Code:
Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\032319-34562-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Invalid directory table base value 0x0
************* Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff801`a4ca6000 PsLoadedModuleList = 0xfffff801`a5054150
Debug session time: Sat Mar 23 19:35:52.662 2019 (UTC + 1:00)
System Uptime: 0 days 10:18:11.469
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
.Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {1, 1e00, fffff801a50f3378, 0}
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: 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: 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: fffff801a50f3378, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
KEY_VALUES_STRING: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
DUMP_TYPE: 2
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff801a50f3378
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
CPU_COUNT: 8
CPU_MHZ: af8
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x133
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: MICHAL
ANALYSIS_SESSION_TIME: 03-23-2019 23:39:09.0970
ANALYSIS_VERSION: 10.0.17763.132 amd64fre
LAST_CONTROL_TRANSFER: from fffff801a4e7b187 to fffff801a4e500a0
STACK_TEXT:
fffff801`a7542b78 fffff801`a4e7b187 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`a50f3378 : 0xfffff801`a4e500a0
fffff801`a7542b80 00000000`00000133 : 00000000`00000001 00000000`00001e00 fffff801`a50f3378 00000000`00000000 : 0xfffff801`a4e7b187
fffff801`a7542b88 00000000`00000001 : 00000000`00001e00 fffff801`a50f3378 00000000`00000000 00000000`00000001 : 0x133
fffff801`a7542b90 00000000`00001e00 : fffff801`a50f3378 00000000`00000000 00000000`00000001 00000000`00000014 : 0x1
fffff801`a7542b98 fffff801`a50f3378 : 00000000`00000000 00000000`00000001 00000000`00000014 00000000`00000001 : 0x1e00
fffff801`a7542ba0 00000000`00000000 : 00000000`00000001 00000000`00000014 00000000`00000001 00000000`000005c0 : 0xfffff801`a50f3378
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID: CORRUPT_MODULELIST_0x133
DEFAULT_BUCKET_ID: CORRUPT_MODULELIST_0x133
PRIMARY_PROBLEM_CLASS: CORRUPT_MODULELIST_0x133
FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x133
TARGET_TIME: 2019-03-23T18:35:52.000Z
OSBUILD: 17134
OSSERVICEPACK: 0
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: unknown_date
ANALYSIS_SESSION_ELAPSED_TIME: 4b
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:corrupt_modulelist_0x133
FAILURE_ID_HASH: {13e3c9ef-8526-da41-b41d-06d8277b0319}
Followup: MachineOwner
---------
Unfortunately this dump has been corrupted so i can't analyze
Code:
Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\032319-37234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff801`708a5000 PsLoadedModuleList = 0xfffff801`70c53150
Debug session time: Sat Mar 23 20:27:34.505 2019 (UTC + 1:00)
System Uptime: 0 days 0:41:00.313
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {1, 1e00, fffff80170cf2378, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded 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 ***
*** ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+e1f93 )
Followup: MachineOwner
---------
0: 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: 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: fffff80170cf2378, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
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
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804
SYSTEM_MANUFACTURER: Notebook
SYSTEM_PRODUCT_NAME: N85_N87,HJ,HJ1,HK1
SYSTEM_SKU: Not Applicable
SYSTEM_VERSION: Not Applicable
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 1.05.01
BIOS_DATE: 12/13/2016
BASEBOARD_MANUFACTURER: Notebook
BASEBOARD_PRODUCT: N85_N87,HJ,HJ1,HK1
BASEBOARD_VERSION: Not Applicable
DUMP_TYPE: 2
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff80170cf2378
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
CPU_COUNT: 8
CPU_MHZ: af8
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: firefox.exe
CURRENT_IRQL: d
ANALYSIS_SESSION_HOST: MICHAL
ANALYSIS_SESSION_TIME: 03-23-2019 23:45:27.0978
ANALYSIS_VERSION: 10.0.17763.132 amd64fre
LAST_CONTROL_TRANSFER: from fffff80170a7a187 to fffff80170a4f0a0
STACK_TEXT:
fffff801`73142b78 fffff801`70a7a187 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`70cf2378 : nt!KeBugCheckEx
fffff801`73142b80 fffff801`708e61ed : 00000659`fca8433f fffff801`6ecf6180 00000000`00000246 00000000`00026714 : nt!KeAccumulateTicks+0x190487
fffff801`73142be0 fffff801`708e72d3 : fffff780`00000340 fffff801`6ecf6180 00000000`00026714 00000000`00000000 : nt!KiUpdateRunTime+0x5d
fffff801`73142c30 fffff801`7081a883 : 00000659`fca7db34 00000000`00000000 00000000`00000000 fffff801`7313aaa0 : nt!KeClockInterruptNotify+0x8f3
fffff801`73142f40 fffff801`709aca65 : fffff801`7087bcb0 fffff801`7313b120 fffff801`7313b500 ffffc804`b9ad9920 : hal!HalpTimerClockInterrupt+0x63
fffff801`73142f70 fffff801`70a5095a : fffff801`7313ab20 fffff801`7087bcb0 00000000`00000001 00000000`00000001 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`73142fb0 fffff801`70a50e47 : 00000000`000000fe 00000000`00000000 00000000`00140001 00000000`000000fe : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff801`7313aaa0 fffff801`708c2552 : 00000000`00000002 00000000`00000001 ffff8faf`485645c6 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`7313ac30 fffff801`708c24dd : fffff801`6ecf6180 00000000`00000000 fffff801`6ecf6180 00000000`00000000 : nt!KiIpiWaitForRequestBarrier+0x32
fffff801`7313ac60 fffff801`708c23ce : fffff801`6ecf6180 00000000`00000002 00000000`00000000 00000000`00000000 : nt!KiIpiSendRequestEx+0x69
fffff801`7313aca0 fffff801`70924762 : 00000000`00000000 00000000`00000001 00000000`00091b00 00000000`00000001 : nt!KxFlushNonGlobalTb+0x9a
fffff801`7313adb0 fffff801`7094bfd7 : 00000000`00000001 fffff801`7313af90 00000000`00000000 ffffc804`c2eeef00 : nt!KeFlushTb+0xc2
fffff801`7313ae00 fffff801`70909f35 : 00000000`00000000 00000000`00000001 00000000`00091b24 00000000`00091b24 : nt!MiFlushTbList+0x417
fffff801`7313af50 fffff801`709af2ad : ffffdde4`02617000 00000000`000000ef 8a000000`00000863 ffffddee`f20130b8 : nt!MiFlushTbAsNeeded+0x285
fffff801`7313b0a0 fffff801`70909573 : fffff801`70c72c10 ffffdde4`02617000 fffff801`7313b1f0 0a000000`402bc863 : nt!MiAssignNonPagedPoolPtes+0x7d
fffff801`7313b0f0 fffff801`709098d0 : fffff801`7313b318 fffff801`00000000 0000004c`00001000 00000000`00001000 : nt!MiCommitPoolMemory+0x773
fffff801`7313b230 fffff801`708bd393 : fffff801`7313b331 00000000`00100000 fffff801`70c888c0 00000000`00000100 : nt!MmAllocatePoolMemory+0x80
fffff801`7313b290 fffff801`70b8fd37 : 00000000`00000000 00000000`4d52564e ffffc804`bf2f0000 00000000`4d52564e : nt!ExpAllocateBigPool+0x713
fffff801`7313b390 fffff807`43491f93 : 00000000`00000000 fffff807`435ba9ac fff00000`4d52564e ffffc804`bb699000 : nt!ExAllocatePoolWithTag+0x927
fffff801`7313b480 00000000`00000000 : fffff807`435ba9ac fff00000`4d52564e ffffc804`bb699000 ffffc804`bbd8ea80 : nvlddmkm+0xe1f93
THREAD_SHA1_HASH_MOD_FUNC: a67a342d2c106c26d19d78d0ba11656777922e98
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 5fb21c9ed309e11fbba8e14f03281c3e0c417b8f
THREAD_SHA1_HASH_MOD: a6139c745ffb4f96bf11d14926bcc2b223454d09
FOLLOWUP_IP:
nvlddmkm+e1f93
fffff807`43491f93 488bf0 mov rsi,rax
FAULT_INSTR_CODE: 48f08b48
SYMBOL_STACK_INDEX: 13
SYMBOL_NAME: nvlddmkm+e1f93
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5c78e109
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: e1f93
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-03-23T19:27:34.000Z
OSBUILD: 17134
OSSERVICEPACK: 648
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: 2019-03-06 09:32:15
BUILDDATESTAMP_STR: 180410-1804
BUILDLAB_STR: rs4_release
BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804
ANALYSIS_SESSION_ELAPSED_TIME: 3929
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x133_isr_nvlddmkm!unknown_function
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
---------
0: kd> !pcr
KPCR for Processor 0 at fffff8016ecf6000:
Major 1 Minor 1
NtTib.ExceptionList: fffff80173129fb0
NtTib.StackBase: fffff80173128000
NtTib.StackLimit: 0000000000000000
NtTib.SubSystemTib: fffff8016ecf6000
NtTib.Version: 000000006ecf6180
NtTib.UserPointer: fffff8016ecf6870
NtTib.SelfTib: 0000004c30737000
SelfPcr: 0000000000000000
Prcb: fffff8016ecf6180
Irql: 0000000000000000
IRR: 0000000000000000
IDR: 0000000000000000
InterruptMode: 0000000000000000
IDT: 0000000000000000
GDT: 0000000000000000
TSS: 0000000000000000
CurrentThread: ffffc804bf2fe340
NextThread: ffffc804bcfb9080
IdleThread: fffff80170d0f400
DpcQueue: Unable to read nt!_KDPC_DATA.DpcListHead.Flink @ fffff8016ecf8f80
0: kd> !dpcs
CPU Type KDPC Function
Failed to read DPC at 0xfffff80170c4e840
The DRIVER_POWER_STATE_FAILURE bug check has a value of 0x0000009F. This bug check indicates that the driver is in an inconsistent or invalid power state.
Code:
Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\032319-35187-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff801`c220a000 PsLoadedModuleList = 0xfffff801`c25b8150
Debug session time: Sat Mar 23 20:41:52.464 2019 (UTC + 1:00)
System Uptime: 0 days 0:12:43.271
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffae0b1b3ac060, ffff8a8912c7f7d0, ffffae0b218702a0}
Implicit thread is now ffffae0b`2506c700
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1f9681 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffae0b1b3ac060, Physical Device Object of the stack
Arg3: ffff8a8912c7f7d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffae0b218702a0, The blocked IRP
Debugging Details:
------------------
Implicit thread is now ffffae0b`2506c700
KEY_VALUES_STRING: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804
SYSTEM_MANUFACTURER: Notebook
SYSTEM_PRODUCT_NAME: N85_N87,HJ,HJ1,HK1
SYSTEM_SKU: Not Applicable
SYSTEM_VERSION: Not Applicable
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 1.05.01
BIOS_DATE: 12/13/2016
BASEBOARD_MANUFACTURER: Notebook
BASEBOARD_PRODUCT: N85_N87,HJ,HJ1,HK1
BASEBOARD_VERSION: Not Applicable
DUMP_TYPE: 2
BUGCHECK_P1: 3
BUGCHECK_P2: ffffae0b1b3ac060
BUGCHECK_P3: ffff8a8912c7f7d0
BUGCHECK_P4: ffffae0b218702a0
DRVPOWERSTATE_SUBCODE: 3
FAULTING_THREAD: 2506c700
CPU_COUNT: 8
CPU_MHZ: af8
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: MICHAL
ANALYSIS_SESSION_TIME: 03-23-2019 23:41:43.0434
ANALYSIS_VERSION: 10.0.17763.132 amd64fre
LAST_CONTROL_TRANSFER: from fffff801c22a13a6 to fffff801c23bad46
STACK_TEXT:
ffff8a89`13c56a20 fffff801`c22a13a6 : ffff767b`00000000 ffffae0b`2506c700 00000000`00000000 00000000`ffffffff : nt!KiSwapContext+0x76
ffff8a89`13c56b60 fffff801`c22a0b9b : 00000000`00000005 00000000`00000007 ffff8a89`13c56d40 fffff801`c2b5fdf5 : nt!KiSwapThread+0x2c6
ffff8a89`13c56c30 fffff801`c22a02bf : fffff800`041b40b0 ffff8a89`00000000 00000000`00000000 ffffae0b`2506c840 : nt!KiCommitThreadWait+0x13b
ffff8a89`13c56cd0 fffff800`039e9681 : ffffae0b`1cbfe970 fffff800`00000000 00000000`00000000 ffff35b1`c5e34e00 : nt!KeWaitForSingleObject+0x1ff
ffff8a89`13c56db0 ffffae0b`1cbfe970 : fffff800`00000000 00000000`00000000 ffff35b1`c5e34e00 00000000`00000000 : nvlddmkm+0x1f9681
ffff8a89`13c56db8 fffff800`00000000 : 00000000`00000000 ffff35b1`c5e34e00 00000000`00000000 ffffae0b`22d051c0 : 0xffffae0b`1cbfe970
ffff8a89`13c56dc0 00000000`00000000 : ffff35b1`c5e34e00 00000000`00000000 ffffae0b`22d051c0 00000000`00000130 : 0xfffff800`00000000
STACK_COMMAND: .thread 0xffffae0b2506c700 ; kb
THREAD_SHA1_HASH_MOD_FUNC: 91c09f95649eaff6bfa06c2196d3e0ff4295c271
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 637873d2fdea86339311d5ef676853ce5d5fade2
THREAD_SHA1_HASH_MOD: 4e96c4bcc4ec8f85ee49d7124864474789fdce87
FOLLOWUP_IP:
nvlddmkm+1f9681
fffff800`039e9681 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nvlddmkm+1f9681
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5c78e109
BUCKET_ID_FUNC_OFFSET: 1f9681
FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm!unknown_function
BUCKET_ID: 0x9F_3_nvlddmkm!unknown_function
PRIMARY_PROBLEM_CLASS: 0x9F_3_nvlddmkm!unknown_function
TARGET_TIME: 2019-03-23T19:41:52.000Z
OSBUILD: 17134
OSSERVICEPACK: 648
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: 2019-03-06 09:32:15
BUILDDATESTAMP_STR: 180410-1804
BUILDLAB_STR: rs4_release
BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804
ANALYSIS_SESSION_ELAPSED_TIME: c5e
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_nvlddmkm!unknown_function
FAILURE_ID_HASH: {8b257f08-e34e-7c26-3880-084b82f90c48}
Followup: MachineOwner
---------
6: kd> !irp ffffae0b218702a0
Irp is active with 6 stacks 5 is current (= 0xffffae0b21870490)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned
cmd flg cl Device File Completion-Context
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
0 0 ffffae0b1b3ac060 00000000 fffff80000bca720-ffff8a8913c57790
\Driver\pci dxgkrnl!DpiFdoPowerCompletionRoutine
Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffffae0b1efd4030 00000000 fffff801c236fa90-ffffae0b23172e88 Success Error Cancel pending
\Driver\nvlddmkm nt!PopRequestCompletion
Args: 00000000 00000001 00000001 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-ffffae0b23172e88
Args: 00000000 00000000 00000000 00000000
6: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff800`037f0000 fffff800`04c19000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nvcvi.inf_amd64_3c5b42cdad4fff4f\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Thu Feb 28 23:36:41 2019 (5C78E109)
CheckSum: 013CB133
ImageSize: 01429000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
6: kd> !devstack ffffae0b1b3ac060
!DevObj !DrvObj !DevExt ObjectName
ffffae0b1efd4030 \Driver\nvlddmkm ffffae0b1efd4180 InfoMask field not found for _OBJECT_HEADER at ffffae0b1efd4000
ffffae0b1b288290 \Driver\ACPI ffffae0b19d00010 InfoMask field not found for _OBJECT_HEADER at ffffae0b1b288260
> ffffae0b1b3ac060 \Driver\pci ffffae0b1b3ac1b0 Cannot read info offset from nt!ObpInfoMaskToOffset
!DevNode ffffae0b1b3aeb20 :
DeviceInst is "PCI\VEN_10DE&DEV_1C8C&SUBSYS_850A1558&REV_A1\4&23726a3e&0&0008"
ServiceName is "nvlddmkm"
6: kd> !devobj ffffae0b1efd4030
Device object (ffffae0b1efd4030) is for:
InfoMask field not found for _OBJECT_HEADER at ffffae0b1efd4000
\Driver\nvlddmkm DriverObject ffffae0b1ddffe60
Current Irp 00000000 RefCount 0 Type 00000023 Flags 00002004
SecurityDescriptor ffffc00bd3f49c20 DevExt ffffae0b1efd4180 DevObjExt ffffae0b1efd5930
ExtensionFlags (0000000000)
Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) ffffae0b1b288290 \Driver\ACPI
Device queue is not busy.
6: kd> !drvobj ffffae0b1ddffe60
fffff801c25b6e48: Unable to get value of ObpRootDirectoryObject
fffff801c25b6e48: Unable to get value of ObpRootDirectoryObject
Driver object (ffffae0b1ddffe60) is for:
\Driver\nvlddmkm
Driver Extension List: (id , addr)
Device Object list:
ffffae0b230a4640: Could not read device object
Because this is the minidump not all information is available
WARNING! Below is a corrupted dumps
Code:
Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\032319-37640-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Invalid directory table base value 0x0
************* Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image Unknown_Module_003f03bc`e04f6f03, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_003f03bc`e04f6f03
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_003f03bc`e04f6f03
Debugger can not determine kernel base address
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`aba9c000 PsLoadedModuleList = 0xfffff803`abe4a150
Debug session time: Sat Mar 23 20:46:17.198 2019 (UTC + 1:00)
System Uptime: 0 days 0:03:40.005
Unable to load image Unknown_Module_003f03bc`e04f6f03, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_003f03bc`e04f6f03
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_003f03bc`e04f6f03
Debugger can not determine kernel base address
Loading Kernel Symbols
.
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffac8e49d84060, ffff9188c6a7f7d0, ffffac8e502a8b40}
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffac8e49d84060, Physical Device Object of the stack
Arg3: ffff9188c6a7f7d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffac8e502a8b40, The blocked IRP
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
KEY_VALUES_STRING: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
DUMP_TYPE: 2
BUGCHECK_P1: 3
BUGCHECK_P2: ffffac8e49d84060
BUGCHECK_P3: ffff9188c6a7f7d0
BUGCHECK_P4: ffffac8e502a8b40
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: ffffac8e502a8b40
DEVICE_OBJECT: ffffac8e49d84060
CPU_COUNT: 8
CPU_MHZ: af8
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CORRUPT_MODULELIST_0x9F
BUGCHECK_STR: 0x9F
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: MICHAL
ANALYSIS_SESSION_TIME: 03-23-2019 23:47:32.0682
ANALYSIS_VERSION: 10.0.17763.132 amd64fre
LAST_CONTROL_TRANSFER: from fffff803abd0ce89 to fffff803abc460a0
STACK_TEXT:
ffff9188`c6a7f798 fffff803`abd0ce89 : 00000000`0000009f 00000000`00000003 ffffac8e`49d84060 ffff9188`c6a7f7d0 : 0xfffff803`abc460a0
ffff9188`c6a7f7a0 00000000`0000009f : 00000000`00000003 ffffac8e`49d84060 ffff9188`c6a7f7d0 ffffac8e`502a8b40 : 0xfffff803`abd0ce89
ffff9188`c6a7f7a8 00000000`00000003 : ffffac8e`49d84060 ffff9188`c6a7f7d0 ffffac8e`502a8b40 ffffac8e`00000000 : 0x9f
ffff9188`c6a7f7b0 ffffac8e`49d84060 : ffff9188`c6a7f7d0 ffffac8e`502a8b40 ffffac8e`00000000 00000000`00028000 : 0x3
ffff9188`c6a7f7b8 ffff9188`c6a7f7d0 : ffffac8e`502a8b40 ffffac8e`00000000 00000000`00028000 fffff803`abe47790 : 0xffffac8e`49d84060
ffff9188`c6a7f7c0 ffffac8e`502a8b40 : ffffac8e`00000000 00000000`00028000 fffff803`abe47790 fffff803`abe45270 : 0xffff9188`c6a7f7d0
ffff9188`c6a7f7c8 ffffac8e`00000000 : 00000000`00028000 fffff803`abe47790 fffff803`abe45270 ffffac8e`486c2bf0 : 0xffffac8e`502a8b40
ffff9188`c6a7f7d0 00000000`00028000 : fffff803`abe47790 fffff803`abe45270 ffffac8e`486c2bf0 ffffac8e`486f9d20 : 0xffffac8e`00000000
ffff9188`c6a7f7d8 fffff803`abe47790 : fffff803`abe45270 ffffac8e`486c2bf0 ffffac8e`486f9d20 fffff780`00000008 : 0x28000
ffff9188`c6a7f7e0 fffff803`abe45270 : ffffac8e`486c2bf0 ffffac8e`486f9d20 fffff780`00000008 00000000`00000001 : 0xfffff803`abe47790
ffff9188`c6a7f7e8 ffffac8e`486c2bf0 : ffffac8e`486f9d20 fffff780`00000008 00000000`00000001 fffff803`abd0cd92 : 0xfffff803`abe45270
ffff9188`c6a7f7f0 ffffac8e`486f9d20 : fffff780`00000008 00000000`00000001 fffff803`abd0cd92 ffffac8e`51c75e88 : 0xffffac8e`486c2bf0
ffff9188`c6a7f7f8 fffff780`00000008 : 00000000`00000001 fffff803`abd0cd92 ffffac8e`51c75e88 ffff9188`c6a7f910 : 0xffffac8e`486f9d20
ffff9188`c6a7f800 00000000`00000001 : fffff803`abd0cd92 ffffac8e`51c75e88 ffff9188`c6a7f910 00000000`000000e0 : 0xfffff780`00000008
ffff9188`c6a7f808 fffff803`abd0cd92 : ffffac8e`51c75e88 ffff9188`c6a7f910 00000000`000000e0 ffff8000`e0339180 : 0x1
ffff9188`c6a7f810 ffffac8e`51c75e88 : ffff9188`c6a7f910 00000000`000000e0 ffff8000`e0339180 00000000`00000000 : 0xfffff803`abd0cd92
ffff9188`c6a7f818 ffff9188`c6a7f910 : 00000000`000000e0 ffff8000`e0339180 00000000`00000000 fffff803`abe477a0 : 0xffffac8e`51c75e88
ffff9188`c6a7f820 00000000`000000e0 : ffff8000`e0339180 00000000`00000000 fffff803`abe477a0 00000000`00000002 : 0xffff9188`c6a7f910
ffff9188`c6a7f828 ffff8000`e0339180 : 00000000`00000000 fffff803`abe477a0 00000000`00000002 00000000`83221f00 : 0xe0
ffff9188`c6a7f830 00000000`00000000 : fffff803`abe477a0 00000000`00000002 00000000`83221f00 00000000`00000002 : 0xffff8000`e0339180
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID: CORRUPT_MODULELIST_0x9F
PRIMARY_PROBLEM_CLASS: CORRUPT_MODULELIST_0x9F
FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x9F
TARGET_TIME: 2019-03-23T19:46:17.000Z
OSBUILD: 17134
OSSERVICEPACK: 0
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: unknown_date
ANALYSIS_SESSION_ELAPSED_TIME: 51
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:corrupt_modulelist_0x9f
FAILURE_ID_HASH: {ddd0b2e3-6b2f-3277-50b2-bd39c69844ec}
Followup: MachineOwner
---------
Code:
Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\032319-42500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Mini Kernel Dump does not have process information
************* Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image Unknown_Module_4c8d480b`75ff8548, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_4c8d480b`75ff8548
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_4c8d480b`75ff8548
Debugger can not determine kernel base address
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff802`99403000 PsLoadedModuleList = 0xfffff802`997b1150
Debug session time: Sat Mar 23 19:45:49.316 2019 (UTC + 1:00)
System Uptime: 0 days 0:09:14.123
Unable to load image Unknown_Module_4c8d480b`75ff8548, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_4c8d480b`75ff8548
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_4c8d480b`75ff8548
Debugger can not determine kernel base address
Loading Kernel Symbols
.
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {1, 1e00, fffff80299850378, 0}
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: 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: 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: fffff80299850378, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
KEY_VALUES_STRING: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
DUMP_TYPE: 2
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff80299850378
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
CPU_COUNT: 8
CPU_MHZ: af8
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x133
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: MICHAL
ANALYSIS_SESSION_TIME: 03-23-2019 23:49:06.0418
ANALYSIS_VERSION: 10.0.17763.132 amd64fre
LAST_CONTROL_TRANSFER: from fffff802995d8187 to fffff802995ad0a0
STACK_TEXT:
fffff802`9bd42b78 fffff802`995d8187 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`99850378 : 0xfffff802`995ad0a0
fffff802`9bd42b80 00000000`00000133 : 00000000`00000001 00000000`00001e00 fffff802`99850378 00000000`00000000 : 0xfffff802`995d8187
fffff802`9bd42b88 00000000`00000001 : 00000000`00001e00 fffff802`99850378 00000000`00000000 00000000`00000001 : 0x133
fffff802`9bd42b90 00000000`00001e00 : fffff802`99850378 00000000`00000000 00000000`00000001 00000000`00000014 : 0x1
fffff802`9bd42b98 fffff802`99850378 : 00000000`00000000 00000000`00000001 00000000`00000014 00000000`00000001 : 0x1e00
fffff802`9bd42ba0 00000000`00000000 : 00000000`00000001 00000000`00000014 00000000`00000001 00007fff`ffff0000 : 0xfffff802`99850378
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID: CORRUPT_MODULELIST_0x133
DEFAULT_BUCKET_ID: CORRUPT_MODULELIST_0x133
PRIMARY_PROBLEM_CLASS: CORRUPT_MODULELIST_0x133
FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x133
TARGET_TIME: 2019-03-23T18:45:49.000Z
OSBUILD: 17134
OSSERVICEPACK: 0
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: unknown_date
ANALYSIS_SESSION_ELAPSED_TIME: 54
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:corrupt_modulelist_0x133
FAILURE_ID_HASH: {13e3c9ef-8526-da41-b41d-06d8277b0319}
Followup: MachineOwner
---------
At this point, the suspect is the NVIDIA graphics driver. If the driver change does not give anything, send me a full memory dump. Have you checked RAM with memtest86+?
Quote