JB
These were Related to
usbhub.sys Microsoft USB Standard Hub Driver/HID. First thing I would do is to run a system file check to verify the OS
Please run a system file check (SFC)
All instructions are in our
Wiki article below...
Should you have any questions please
ask us.
System file check (SFC) Scan and Repair System Files
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\020214-20984-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff801`d1c18000 PsLoadedModuleList = 0xfffff801`d1edc990
Debug session time: Sun Feb 2 12:04:01.055 2014 (UTC - 5:00)
System Uptime: 0 days 1:44:34.322
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffe000002f3060, fffff801d36417c0, ffffe00005589b80}
Probably caused by : usbhub.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: ffffe000002f3060, Physical Device Object of the stack
Arg3: fffff801d36417c0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe00005589b80, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
DRIVER_OBJECT: ffffe00004e57a20
IMAGE_NAME: usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5215f839
MODULE_NAME: usbhub
FAULTING_MODULE: fffff80002af5000 usbhub
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
DPC_STACK_BASE: FFFFF801D3649FB0
STACK_TEXT:
fffff801`d3641788 fffff801`d1e0f1a6 : 00000000`0000009f 00000000`00000003 ffffe000`002f3060 fffff801`d36417c0 : nt!KeBugCheckEx
fffff801`d3641790 fffff801`d1e0f0c6 : ffffe000`0558aac8 00000000`00000008 00000000`00000002 fffff801`d1c74a04 : nt!PopIrpWatchdogBugcheck+0xde
fffff801`d36417f0 fffff801`d1cc5f64 : ffffe000`0558ab00 fffff801`d36418b9 ffffe000`0558ab40 00000000`00000002 : nt!PopIrpWatchdog+0x32
fffff801`d3641840 fffff801`d1cc6478 : 00000000`00000001 ffffe000`04aee748 fffff801`d1f06180 fffff801`d1f09fe0 : nt!KiProcessExpiredTimerList+0x1d8
fffff801`d3641920 fffff801`d1d22478 : fffff801`d1f06180 00000000`002e5930 00000000`0003a473 00000000`0003a473 : nt!KiExpireTimerTable+0x218
fffff801`d36419c0 fffff801`d1c72abc : ffffe000`00000000 00001f80`00000001 0000000e`49d648a6 00000000`00000002 : nt!KiTimerExpiration+0x148
fffff801`d3641a70 fffff801`d1d697ea : fffff801`d1f06180 fffff801`d1f06180 00000000`001a3fc0 fffff801`d1f5ea80 : nt!KiRetireDpcList+0x19c
fffff801`d3641be0 00000000`00000000 : fffff801`d3642000 fffff801`d363b000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.3.9600.16384
FAILURE_BUCKET_ID: 0x9F_3_IMAGE_usbhub.sys
BUCKET_ID: 0x9F_3_IMAGE_usbhub.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_image_usbhub.sys
FAILURE_ID_HASH: {6e67f518-0887-9d66-a512-212f24e07d60}
Followup: MachineOwner
---------
Irp is active with 13 stacks 10 is current (= 0xffffe00005589ed8)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
cmd flg cl Device File Completion-Context
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
>[ 16, 2] 0 e1 ffffe000002f3060 00000000 fffff80002c01a50-00000000 Success Error Cancel pending
\Driver\usbhub hidusb!HumPowerCompletion
Args: 00000000 00000001 00000001 00000000
[ 16, 2] 0 e0 ffffe00005559060 00000000 fffff80002a06830-ffffe000055591b0 Success Error Cancel
\Driver\HidUsb HIDCLASS!HidpFdoPowerCompletion
Args: 00000000 00000001 00000001 00000000
[ 16, 2] 0 e1 ffffe00005559060 00000000 fffff801d1d2dd80-ffffe0000558aac8 Success Error Cancel pending
\Driver\HidUsb nt!PopRequestCompletion
Args: 00000000 00000001 00000001 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-ffffe0000558aac8
Args: 00000000 00000000 00000000 00000000