New
#1
Windows keeps freezing randomly - problem with usb dongle?
Hi,
Windows keeps randomly freezing, forcing a hard reboot and occasionally I get a BSOD too.
I think it might have something to do with the external devices i have connected to my laptop: an external monitor, and an external keyboard with trackpad and an external mouse. Both the keyboard and mouse are wireless and share the same single usb receiver dongle (logitech unifying receiver)
I think it might be the driver for the usb receiver dongle that's causing the problems based on the dump file i've pasted below. Anyone have any suggestions for remedying this short of getting rid of the mouse and keyboard? Both have the latest drivers.
Thanks. See dump file text below.
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8008825060, fffff800045b63d8, fffffa800866d550}
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
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 (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8008825060, Physical Device Object of the stack
Arg3: fffff800045b63d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800866d550, 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 ***
*** ***
*************************************************************************
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c15
MODULE_NAME: usbhub
FAULTING_MODULE: fffff88005241000 usbhub
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
TAG_NOT_DEFINED_c000000f: FFFFF800045BCFB0
STACK_TEXT:
fffff800`045b6388 fffff800`031416d2 : 00000000`0000009f 00000000`00000003 fffffa80`08825060 fffff800`045b63d8 : nt!KeBugCheckEx
fffff800`045b6390 fffff800`030e1c3c : fffff800`045b64c0 fffff800`045b64c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33ac0
fffff800`045b6430 fffff800`030e1ad6 : fffff800`0327ef20 00000000`0030ced8 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`045b64a0 fffff800`030e19be : 00000074`2e8f7655 fffff800`045b6b18 00000000`0030ced8 fffff800`0324dd88 : nt!KiProcessExpiredTimerList+0xc6
fffff800`045b6af0 fffff800`030e17a7 : 00000018`e79d50c1 00000018`0030ced8 00000018`e79d502b 00000000`000000d8 : nt!KiTimerExpiration+0x1be
fffff800`045b6b90 fffff800`030cecca : fffff800`03249e80 fffff800`03257cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`045b6c40 00000000`00000000 : fffff800`045b7000 fffff800`045b1000 fffff800`045b6c00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_btfilter_IMAGE_usbhub.sys
BUCKET_ID: X64_0x9F_3_btfilter_IMAGE_usbhub.sys
Followup: MachineOwner