Blue Screen - DEVICE_EXTENSION- usbhub.sys

original title: BSOD -  Bugcheck Analysis - usbhub.sys

 

Hello.

I was wondering if someone might be able to help. I recently purchased a new sports device (adidas micoach) which was working fine. Then I received the below error and system crash.

Now the computer won’t recognise or load the device advising that it might be damaged or faulty. However the same usb device loads correctly on other PCs. Also the same usb ports on my pc work fine with my usb mouse.

Does the below memory dump specify hardware failure of the device, or something else.

Many many thanks

Chris

 


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\memory.dmp]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0344f000 PsLoadedModuleList = 0xfffff800`0368ce50
Debug session time: Thu Feb 17 19:23:43.774 2011 (UTC + 0:00)
System Uptime: 0 days 0:09:05.444
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols

Loading unloaded module list
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {8, 6, 5, fffffa800b37cb20}

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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: usbport!_DEVICE_EXTENSION                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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_HUB                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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_HUB                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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_HUB                  ***
***                                                                   ***
*************************************************************************
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent
Arg4: fffffa800b37cb20, TimeoutContext - PortData

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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: usbport!_DEVICE_EXTENSION                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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_HUB                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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_HUB                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command 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_HUB                  ***
***                                                                   ***
*************************************************************************

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880061a79ec to fffff800034bf740

STACK_TEXT: 
fffff880`03369c18 fffff880`061a79ec : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
fffff880`03369c20 fffff800`037b9943 : fffffa80`0b372050 fffffa80`0b1290a0 ffffffff`dc3a58a0 fffff800`036645f8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`03369c80 fffff800`034cc961 : fffff800`03664500 fffff800`037b9920 fffffa80`06a36040 fffffa80`07a77b00 : nt!IopProcessWorkItem+0x23
fffff880`03369cb0 fffff800`037627c6 : 00000000`00000000 fffffa80`06a36040 00000000`00000080 fffffa80`069a7890 : nt!ExpWorkerThread+0x111
fffff880`03369d40 fffff800`0349dc26 : fffff880`03186180 fffffa80`06a36040 fffff880`031910c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03369d80 00000000`00000000 : fffff880`0336a000 fffff880`03364000 fffff880`03369970 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`061a79ec cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  usbhub!UsbhHubProcessChangeWorker+ec

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbhub

IMAGE_NAME:  usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc2d

FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

Followup: MachineOwner
---------

4: kd> lmvm usbhub
start             end                 module name
fffff880`06195000 fffff880`061ef000   usbhub     (pdb symbols)          c:\websymbols\usbhub.pdb\295DCA65F67B44BF8DD26C3B6D89A6F71\usbhub.pdb
    Loaded symbol image file: usbhub.sys
    Image path: \SystemRoot\system32\drivers\usbhub.sys
    Image name: usbhub.sys
    Timestamp:        Tue Jul 14 01:07:09 2009 (4A5BCC2D)
    CheckSum:         0005BB10
    ImageSize:        0005A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
4: kd> lmvm usbhub

 

 

 

Question Info


Last updated March 13, 2018 Views 3,094 Applies to:

Hi,

Be sure to check with the System maker's Support (or motherboard maker for custom systems)
and their forums (if any) for known issues. Check for updated BIOS and low level chipset
drivers.

Also check with that device maker's support for known issues and look for updated drivers if the
device uses its own specific drivers.

-------------------------------------------------

Check these KB Articles which "might" apply.

Stop 0xFE Resuming from Sleep or Hibernate with USB Streaming Device
http://support.microsoft.com/kb/974303

"Stop 0x9F" or "Stop 0xFE" error on a Windows 7-based or Windows Vista-based computer that
uses certain AMD USB EHCI host controllers
http://support.microsoft.com/kb/982091

"STOP 0x000000FE" error in Windows 7 or in Windows Server 2008 R2 when the computer enters
or resumes from sleep (S3) or from hibernation (S4)
http://support.microsoft.com/kb/974410

Those and 2 other KB Articles are available (as of the date of this reply)
http://support.microsoft.com/search/default.aspx?mode=a&query=0x000000FE&spid=14019&catalog=LCID%3D1033&res=10

============================================================

Although the Bug Check 0xFE: BUGCODE_USB_DRIVER does usually indicate hardware it could easily
be a USB device attached and not System USB hardware. And you can never really rule out drivers.

BCCode: FE    0x000000FE  <-- read this
http://www.faultwire.com/solutions-fatal_error/BUGCODE-USB-DRIVER-0x000000FE-*1251.html?order=date

--------------------------------------------------------------------------------------

Is this a Upgrade installation of Windows 7 or did Windows 7 come on the system from the factory?

A possible cause could be Windows Updates, especially drivers. Even drivers not usually thought of as
USB related, such as video/display, network (NIC & WiFI), and others, can be the cause.

Norton especially, McAfee, Kaspersky, SpyBot, Adaware and others could be causing or have a role
in this issue. Try uninstalling them to see if that helps. Use their maker's Removal Tools and/or
special instructions. (Antivirus/antispyware/security programs.)

----------------------

Remove ALL USB devices from the computer. Be sure to check for updated drivers for ALL USB
devices.

References to Vista also apply to Windows 7.

Do these to clear corruption and repair/replace damaged/missing system files.

Start - type in Search box -  COMMAND   find at top of list -  RIGHT CLICK  -  RUN AS ADMIN

sfc /scannow

How to Repair Windows 7 System Files with System File Checker
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Then run checkdisk (chkdsk).

How to Run Disk Check in Windows 7
http://www.sevenforums.com/tutorials/433-disk-check.html

-----------------------------------------------

Then lets refresh the USB Stack

Control Panel - Device Manager - click anywhere in the blank/white area - then VIEW - Show
Disabled Devices - look everywhere (except USB Controllers) for any hidden/disabled devices 
(may have none or more than one) and Right Click on it - UNINSTALL.

Control Panel - Device Manager - USB Serial Controllers - RIGHT CLICK on EVERYTHING and
UNINSTALL all except the category itself - REBOOT - this refreshes the driver and the USB stack

This KB shows the XP how to and the Vista and Windows 7 methods are identical
http://support.microsoft.com/kb/310575

Here is a utility to help but do the above 1st.

USBDeview is a small utility that lists all USB devices that currently connected to your computer,
as well as all USB devices that you previously used. Run it Options and check the 1st three
choices to see if any are there.

http://www.nirsoft.net/utils/usb_devices_view.html

You would remove all instances of the devices then reboot.

----------------------------------------------

If needed try both of these :

Tips for solving problems with USB devices - and a Mr Fixit
http://windowshelp.microsoft.com/Windows/en-US/Help/c39bd203-f729-47a4-8351-83291e13c8a81033.mspx#EGB

Hardware devices not detected or not working - Mr Fixit
http://support.microsoft.com/gp/hardware_device_problems

=======================================

After the above attach one USB device at a time to see if any cause the issue.

Hope this helps.


Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.
Rob Brown - Microsoft MVP - Windows and Devices for IT 2010 - current
Windows Insider MVP 2016 - current

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.