Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
- Copyright (c) Microsoft Corporation. All rights reserved.
- Loading Dump File [C:\Windows\Minidump\120116-11029-01.dmp]
- Mini Kernel Dump File: Only registers and stack trace are available
- Symbol search path is: SRV*G:\Symbols*http://msdl.microsoft.com/download/symbols
- Executable search path is:
- Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
- Product: WinNt, suite: TerminalServer SingleUserTS Personal
- Built by: 7601.23569.amd64fre.win7sp1_ldr.161007-0600
- Machine Name:
- Kernel base = 0xfffff800`03a5c000 PsLoadedModuleList = 0xfffff800`03c9e730
- Debug session time: Thu Dec 1 01:02:14.606 2016 (GMT+1)
- System Uptime: 0 days 3:17:20.324
- Loading Kernel Symbols
- ...............................................................
- ................................................................
- ................................................................
- ................
- Loading User Symbols
- Loading unloaded module list
- ..........
- *******************************************************************************
- * *
- * Bugcheck Analysis *
- * *
- *******************************************************************************
- Use !analyze -v to get detailed debugging information.
- BugCheck 9F, {3, fffffa800e124060, fffff80000b9a3d8, fffffa8012eb19d0}
- *** 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
- Followup: MachineOwner
- ---------
- 0: kd> !analyze -v
- *******************************************************************************
- * *
- * Bugcheck Analysis *
- * *
- *******************************************************************************
- DRIVER_POWER_STATE_FAILURE (9f)
- A driver is causing an inconsistent power state.
- Arguments:
- Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
- Arg2: fffffa800e124060, Physical Device Object of the stack
- Arg3: fffff80000b9a3d8, Functional Device Object of the stack
- Arg4: fffffa8012eb19d0, The blocked IRP
- Debugging Details:
- ------------------
- DRVPOWERSTATE_SUBCODE: 3
- IRP_ADDRESS: fffffa8012eb19d0
- DEVICE_OBJECT: fffffa80111ce480
- DRIVER_OBJECT: fffffa80111a6470
- IMAGE_NAME: nvlddmkm.sys
- DEBUG_FLR_IMAGE_TIMESTAMP: 55259065
- MODULE_NAME: nvlddmkm
- FAULTING_MODULE: fffff88008e15000 nvlddmkm
- CUSTOMER_CRASH_COUNT: 1
- DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
- BUGCHECK_STR: 0x9F
- PROCESS_NAME: System
- CURRENT_IRQL: 2
- LAST_CONTROL_TRANSFER: from fffff80003b3e3c0 to fffff80003acc400
- STACK_TEXT:
- fffff800`00b9a388 fffff800`03b3e3c0 : 00000000`0000009f 00000000`00000003 fffffa80`0e124060 fffff800`00b9a3d8 : nt!KeBugCheckEx
- fffff800`00b9a390 fffff800`03ad75cc : fffff800`00b9a4c0 fffff800`00b9a4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x2e4a0
- fffff800`00b9a430 fffff800`03ad7466 : fffffa80`12e7bc58 fffffa80`12e7bc58 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
- fffff800`00b9a4a0 fffff800`03ad734e : 0000001b`916227b0 fffff800`00b9ab18 00000000`000b94ce fffff800`03c4ec48 : nt!KiProcessExpiredTimerList+0xc6
- fffff800`00b9aaf0 fffff800`03ad7137 : 0000000a`ca6968c2 0000000a`000b94ce 0000000a`ca6968ed 00000000`000000ce : nt!KiTimerExpiration+0x1be
- fffff800`00b9ab90 fffff800`03ac410a : fffff800`03c4ae80 fffff800`03c58cc0 00000000`00000000 fffff880`08f40430 : nt!KiRetireDpcList+0x277
- fffff800`00b9ac40 00000000`00000000 : fffff800`00b9b000 fffff800`00b95000 fffff800`00b9ac00 00000000`00000000 : nt!KiIdleLoop+0x5a
- STACK_COMMAND: kb
- FOLLOWUP_NAME: MachineOwner
- FAILURE_BUCKET_ID: X64_0x9F_IMAGE_nvlddmkm.sys
- BUCKET_ID: X64_0x9F_IMAGE_nvlddmkm.sys
- Followup: MachineOwner
- ---------
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement