*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8009c4ea10, fffff80000ba2748, fffffa80076c7760}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : pci.sys
Followup: MachineOwner
---------
0: 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: fffffa8009c4ea10, Physical Device Object of the stack
Arg3: fffff80000ba2748, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa80076c7760, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7928f
MODULE_NAME: pci
FAULTING_MODULE: fffff88000e00000 pci
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
DPC_STACK_BASE: FFFFF80000BA2FB0
STACK_TEXT:
fffff800`00ba26f8 fffff800`0353d8d2 : 00000000`0000009f 00000000`00000003 fffffa80`09c4ea10 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`034d885c : fffff800`00ba2848 fffff800`00ba2848 00000000`0000fff7 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00ba27a0 fffff800`034d86f6 : fffff880`00fa32b0 00000000`0000d4c4 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00ba2810 fffff800`034d85de : 00000001`fa79111e fffff800`00ba2e88 00000000`0000d4c4 fffff800`0364cb08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`034d83c7 : fffff800`03648ec3 fffffa80`0000d4c4 fffffa80`0a83b000 00000000`000000c4 : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`034d0d15 : 00000000`00000000 fffffa80`0b2f9b50 00000000`00000000 fffff880`05087588 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`034d0b2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`0b7c3560 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.1.7601.17514
FAILURE_BUCKET_ID: X64_0x9F_3_ACPI_IMAGE_pci.sys
BUCKET_ID: X64_0x9F_3_ACPI_IMAGE_pci.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x9f_3_acpi_image_pci.sys
FAILURE_ID_HASH: {f949ba98-ee69-8040-f9fe-7209de5e5499}
Followup: MachineOwner
---------