View Single Post
26 Sep 2012  
Vir Gnarus

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

Looks good now. Each one reports an issue with a USB HID (Human Interface Device; e.g. keyboard, mouse, touchpad). It's being held up somehow when attempting to do a remove device, which is kinda unusual normal activity. There's a good possibility that we're dealing with an internal issue with one of the input devices on your laptop, such as a connection problem or a motherboard malfunction, which would cause it to lose connection to the input device and have it meet an unexpected demise. I do know that the reason it was held up was because the request given to it was not supported, so it doesn't quite understand this device remove request given to it.

I recommend you go to the Dell website and find updates for your drivers involving your Touchpad and any other input device present. If you are using an external device like a mouse with its own drivers get updates (and firmware if available) for that too. BIOS updates may also help in this regard. Otherwise, you may have a hardware failure here.

This is just a rudimentary analysis. I cannot delve further into it without a MEMORY.DMP file from your Windows directory.

Analysts:

Code:
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 887dc030, Physical Device Object of the stack
Arg3: 82f7bae0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: 9e5cd340, The blocked IRP

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: USBHUB!_DEVICE_EXTENSION_PDO                  ***
***                                                                   ***
*************************************************************************
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: 887fb3d8

IMAGE_NAME:  usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c04da

MODULE_NAME: usbhub

FAULTING_MODULE: 8afb8000 usbhub

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
82f7ba94 82f1aecf 0000009f 00000003 887dc030 nt!KeBugCheckEx+0x1e
82f7bb00 82f1af48 82f7bba0 00000000 82f88380 nt!PopCheckIrpWatchdog+0x1f5
82f7bb38 82ece019 82f966e0 00000000 73379a5e nt!PopCheckForIdleness+0x73
82f7bb7c 82ecdfbd 82f7ed20 82f7bca8 00000001 nt!KiProcessTimerDpcTable+0x50
82f7bc68 82ecde7a 82f7ed20 82f7bca8 00000000 nt!KiProcessExpiredTimerList+0x101
82f7bcdc 82ecc00e 0000abff 8acca7f8 82f88380 nt!KiTimerExpiration+0x25c
82f7bd20 82ecbe38 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82f7bd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_3_IMAGE_usbhub.sys

BUCKET_ID:  0x9F_3_IMAGE_usbhub.sys

Followup: MachineOwner
---------
0: kd> !irp 9e5cd340 1
Irp is active with 9 stacks 6 is current (= 0x9e5cd464)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = 9e5cd350
ThreadListEntry.Blink = 9e5cd350
IoStatus.Status = c00000bb
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = 9e5cd380
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = 82f96178
Tail.Overlay.ListEntry.Blink = 82f96178
Tail.Overlay.CurrentStackLocation = 9e5cd464
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     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
>[ 16, 2]   0 e1 887dc030 00000000 9b9905b4-00000000 Success Error Cancel pending
           \Driver\usbhub    hidusb!HumPowerCompletion
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e0 8a9efb78 00000000 9b9a0464-8a9efc30 Success Error Cancel 
           \Driver\HidUsb    HIDCLASS!HidpFdoPowerCompletion
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 8a9efb78 00000000 00000000-00000000    pending
           \Driver\HidUsb (IopUnloadSafeCompletion)
            Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-9e561e38    

            Args: 00000000 00000000 00000000 00000000
0: kd> !error c00000bb
Error code: (NTSTATUS) 0xc00000bb (3221225659) - The request is not supported.
I can't go much further with the minidumps. I tried looking at the device nodes to see what types of states they support, but I can only view the parent node (the usbhub itself) and not the child (the actual usb device), which is what I need. However, I have seen this before in other PCs and often it's because of some internal hardware issue with the laptop.
My System SpecsSystem Spec