Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\jdizzle921\Windows_NT6_BSOD_jcgriff2\032312-18813-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`045f2500?
Symbol search path is: SRV*C:\SymCache*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.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e59000 PsLoadedModuleList = 0xfffff800`0309d650
Debug session time: Fri Mar 23 18:24:34.534 2012 (UTC - 6:00)
System Uptime: 0 days 3:58:24.643
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8009d5c060, fffff800045f2518, fffffa800b547580}
Unable to load image \SystemRoot\system32\DRIVERS\AiCharger.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AiCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AiCharger.sys
Probably caused by : usbhub.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: fffffa8009d5c060, Physical Device Object of the stack
Arg3: fffff800045f2518, Functional Device Object of the stack
Arg4: fffffa800b547580, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c15
MODULE_NAME: usbhub
FAULTING_MODULE: fffff88005a79000 usbhub
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
fffff800`045f24c8 fffff800`02f43192 : 00000000`0000009f 00000000`00000003 fffffa80`09d5c060 fffff800`045f2518 : nt!KeBugCheckEx
fffff800`045f24d0 fffff800`02ee0a6c : fffff800`045f2600 fffff800`045f2600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34040
fffff800`045f2570 fffff800`02ee0906 : fffff800`0307ff00 00000000`000dfdde 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`045f25e0 fffff800`02ee07ee : 00000021`4e3b5666 fffff800`045f2c58 00000000`000dfdde fffff800`0304ee48 : nt!KiProcessExpiredTimerList+0xc6
fffff800`045f2c30 fffff800`02ee05d7 : 00000009`ff414ac1 00000009`000dfdde 00000009`ff414aef 00000000`000000de : nt!KiTimerExpiration+0x1be
fffff800`045f2cd0 fffff800`02ecda6a : fffff800`0304ae80 fffff800`03058cc0 00000000`00000000 fffff880`014b9a00 : nt!KiRetireDpcList+0x277
fffff800`045f2d80 00000000`00000000 : fffff800`045f3000 fffff800`045ed000 fffff800`045f2d40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_AiCharger_IMAGE_usbhub.sys
BUCKET_ID: X64_0x9F_3_AiCharger_IMAGE_usbhub.sys
Followup: MachineOwner
---------