Solved Vista BSOD usbhub.sys on shutdown

[Tloram]

Hi guys,
I am almost completely happy with my new PC. I bought it with Vista 64 SP1 but am having troubles when shutting down the computer.

I have 3 different USB hubs that worked fine on my old XP Pro machine, I have tried each one of these in turn on my new Vista machine and for EVERY one, when I shutdown windows it BSODS and points at a usbhub.sys problem...

I have even just been out to the shops and purchased a brand new Vista certified Advent black 7 port powered USB2 hub and this exhibits exactly the same problem.

In all cases the hub works fine while the machine is on, but all cause a BSOD when attempting to shutdown.

Any ideas?

PS. My motherboard was a Asus P5E if that has any relevance...

 

[Dwarf]

Hi Tloram and welcome to the forums

What happens when you shutdown your PC WITHOUT a hub attached?
Dwarf

 

[Tloram]

It shutdowns correctly!

 

[Dwarf]

Hi Tloram,

Trying to narrow things down a bit. You said that without a hub, your PC shuts down correctly. What happens when you plug a hub in WITHOUT any peripherals attached to it and then shut down? If it then shuts down, repeat by adding a peripheral to the hub one at a time. If a certain peripheral seems to cause the BSOD, try plugging that peripheral directly in to your PC avoiding the hub. Of course, if you want to avoid hubs altogether you can check to see if all USB headers on your motherboard (m/b) are utilised. If not, you can obtain expansion slot brackets with USB sockets mounted on them that connect to the headers on your m/b. Ideally, you should avoid hubs altogether if at all possible. Most m/bs can accept a number of USB devices (typically 6 - 12), and it is unlikely that the average user is going to require more than that.
Dwarf

 

[Tloram]

Plugging in JUST the hub itself WITHOUT ANY devices will cause the BSOD everytime I shutdown. This is true for all 3 usb hubs I have now tried...

This is crazy. Any more ideas?

This is my hub >

http://www.pcworld.co.uk/martprd/st...=null&sm=null&tm=null&sku=226545&category_oid=

 

[Dwarf]

Hi Tloram,

What is the EXACT wording of the BSOD message?
Dwarf

 

[johngalt]

Better check those hubs carefully - they *say* USB 2.0 but they in fact may not be....I had very very similar issues on my older machine (MSI Neo2 Platinum Edition based P4 3.2 GHz machine) when I used a couple of different (different manufacturers) USB 2.0 Hubs - the ports were supposed to be USB 2.0 but they did not play well with all hubs I tried, only some.

 

[Tloram]

Hi Tloram,

What is the EXACT wording of the BSOD message?
Dwarf

Will the BSOD error be stored anywhere? It disappears to fast to read and write it all down

 

[sidney1st]

Hmmmm, minidump files should give the info.
If you do not know about minidump files, open the reliability monitor, the error code should be displayed.

EDIT: Have a look too in the events log.

 

[Tloram]

Hi guys, this is about as much info as I could dig up on the error:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 2057
Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFFA600313D709
BCP3: FFFFFA60087B5878
BCP4: FFFFFA60087B5250
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\Mini072808-01.dmp
C:\Users\Tim\AppData\Local\Temp\WER-31059-0.sysdata.xml
C:\Users\Tim\AppData\Local\Temp\WERAF8F.tmp.version.txt
Read our privacy statement:
Microsoft Online Crash Analysis


Attached is the corresponding minidump file but I am unable to read it. Any help?

 

[Tloram]

Anyone got any more ideas based on the above minidump?

 

[sidney1st]

Don't have the debug tool on this computer, have a look in the other files:
C:\Users\Tim\AppData\Local\Temp\WER-31059-0.sysdata.xml
C:\Users\Tim\AppData\Local\Temp\WERAF8F.tmp.version.txt

 

[AvatarOfTheShip]

Hi Tloram - you have tried the hub(s) with and without devices attached; have you tried the hub in different ports?

 

[Tloram]

Hi Tloram - you have tried the hub(s) with and without devices attached; have you tried the hub in different ports?

Yes and yes. No difference.

 

[Tloram]

Have managed to install WinDBG and got this info from it:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffffa6003135709, The address that the exception occurred at
Arg3: fffffa60005e4878, Exception Record Address
Arg4: fffffa60005e4250, Context Record Address
Debugging Details:
------------------
Unable to load image \SystemRoot\system32\drivers\libusb0.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
usbhub!UsbhFdoSetPowerDx_Action+4d
fffffa60`03135709 4c8b6e48 mov r13,qword ptr [rsi+48h]
EXCEPTION_RECORD: fffffa60005e4878 -- (.exr 0xfffffa60005e4878)
ExceptionAddress: fffffa6003135709 (usbhub!UsbhFdoSetPowerDx_Action+0x000000000000004d)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000048
Attempt to read from address 0000000000000048
CONTEXT: fffffa60005e4250 -- (.cxr 0xfffffa60005e4250)
rax=fffffa8007ba2910 rbx=fffffa800533f050 rcx=fffffa80053404c0
rdx=0000000000015047 rsi=0000000000000000 rdi=fffffa800533f050
rip=fffffa6003135709 rsp=fffffa60005e4ab0 rbp=fffffa8007ba2910
r8=0000000050734478 r9=0000000000000000 r10=fffffa800533f1a0
r11=fffffa800533f1a0 r12=0000000000000010 r13=0000000000000004
r14=0000000000000000 r15=fffffa800533f1a0
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
usbhub!UsbhFdoSetPowerDx_Action+0x4d:
fffffa60`03135709 4c8b6e48 mov r13,qword ptr [rsi+48h] ds:002b:00000000`00000048=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000207f080
0000000000000048
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffffa600313412b to fffffa6003135709
STACK_TEXT:
fffffa60`005e4ab0 fffffa60`0313412b : fffffa80`0533f050 00000000`00000004 fffffa80`0533f6f8 00000000`00000004 : usbhub!UsbhFdoSetPowerDx_Action+0x4d
fffffa60`005e4b10 fffffa60`03132fd8 : fffffa80`07ba2b48 fffffa80`0533f1a0 fffffa80`0533f050 fffffa80`07ba2910 : usbhub!UsbhFdoDevicePowerState+0x1db
fffffa60`005e4b60 fffffa60`03132347 : fffffa80`07ba2910 fffffa80`07ba2b90 fffffa80`0533f050 fffffa80`06e7fc10 : usbhub!UsbhFdoPower_SetPower+0x94
fffffa60`005e4ba0 fffffa60`0311bc03 : fffffa80`07ba2910 fffffa80`0536a1a0 fffffa60`01766cc0 00000000`00000000 : usbhub!UsbhFdoPower+0xaf
fffffa60`005e4be0 fffff800`01f651b2 : fffffa80`07ba2910 fffffa80`07ba2b90 fffffa80`0536a1a0 fffffa80`07ba2910 : usbhub!UsbhGenDispatch+0x93
fffffa60`005e4c20 fffffa60`0402992c : fffffa60`0402c0a0 00000000`00000003 00000000`00000000 fffffa80`07ba2910 : nt!IopPoHandleIrp+0x32
fffffa60`005e4c50 fffffa60`0402c0a0 : 00000000`00000003 00000000`00000000 fffffa80`07ba2910 00000000`00000000 : libusb0+0x392c
fffffa60`005e4c58 00000000`00000003 : 00000000`00000000 fffffa80`07ba2910 00000000`00000000 fffffa80`07ba2910 : libusb0+0x60a0
fffffa60`005e4c60 00000000`00000000 : fffffa80`07ba2910 00000000`00000000 fffffa80`07ba2910 fffffa80`0536a050 : 0x3
fffffa60`005e4c68 fffffa80`07ba2910 : 00000000`00000000 fffffa80`07ba2910 fffffa80`0536a050 00000000`00000000 : 0x0
fffffa60`005e4c70 00000000`00000000 : fffffa80`07ba2910 fffffa80`0536a050 00000000`00000000 00000000`00000001 : 0xfffffa80`07ba2910
fffffa60`005e4c78 fffffa80`07ba2910 : fffffa80`0536a050 00000000`00000000 00000000`00000001 fffff800`01f745aa : 0x0
fffffa60`005e4c80 fffffa80`0536a050 : 00000000`00000000 00000000`00000001 fffff800`01f745aa fffffa80`0536a1a0 : 0xfffffa80`07ba2910
fffffa60`005e4c88 00000000`00000000 : 00000000`00000001 fffff800`01f745aa fffffa80`0536a1a0 fffffa80`07ba2910 : 0xfffffa80`0536a050
fffffa60`005e4c90 00000000`00000001 : fffff800`01f745aa fffffa80`0536a1a0 fffffa80`07ba2910 fffffa80`06f2eb00 : 0x0
fffffa60`005e4c98 fffff800`01f745aa : fffffa80`0536a1a0 fffffa80`07ba2910 fffffa80`06f2eb00 fffffa80`06c5d400 : 0x1
fffffa60`005e4ca0 fffff800`020cef73 : 00010000`00003e95 fffffa80`03cad040 00000000`00000080 01c6fe4d`3afde901 : nt!PopIrpWorker+0x3ca
fffffa60`005e4d50 fffff800`01ee5526 : fffffa60`01763180 fffffa80`03cad040 fffffa60`0176cd40 00000000`00000000 : nt!PspSystemThreadStartup+0x57
fffffa60`005e4d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

FOLLOWUP_IP:
libusb0+392c
fffffa60`0402992c ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: libusb0+392c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: libusb0
IMAGE_NAME: libusb0.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45130544
STACK_COMMAND: .cxr 0xfffffa60005e4250 ; kb
FAILURE_BUCKET_ID: X64_0x7E_libusb0+392c
BUCKET_ID: X64_0x7E_libusb0+392c
Followup: MachineOwner
---------

Anyone able to read anything from this?

This is rediculous. Can somebody just recommend a good USB2 hub that WORKS (and they can personally vouch for)100% with Vista 32/64? I think I shall just give up and go and buy that instead.

Thanks!

 

[Dwarf]

Hi Tloram,

I have just had a look on Google and one of the things that I have come up with is that you might have a damaged or corrupted 'INFCACHE.1' file. This file is located in the following location: 'C:\Windows\inf\', and can be safely deleted. Remember to create a restore point first.
Dwarf

 

[Tloram]

Hi all. I have found and fixed the problem!

See here > CyberPowersystem: New PC - blue screen on shutdown usbhub.sys

Thanks!

 

[johngalt]

Here is the fix post:

Guys,

I persevered and found the solution to this BSOD and it is really worthwhile you taking note...

The problem was due to an outdated USB driver installed with the AlphaCool LCD that I choose with my computer.

For future reference you need to use the following driver to avoid giving your customers the same potential problems:

Alphacool Support-Forum :: Thema anzeigen - Latest USB driver package for Alphacool LCD:

You can see that this new version has "libusb0 updated to version 1.12.1". This was the driver that kept crashing my system on shutdown and reboot.

Having discussed it with the AlphaCool people, apparently the earlier version of the driver (the one that was installed on my system when it arrived) was taking hold of more USB hubs that it should have!

Quote from one of the devs:

"Main problem is the faulty driver registration from the older versions, if done manually with install.exe or alphaLCD installation without previous installed drivers. The driver itself is okay, but it also take control of other USB hubs, what should not happen and causes the crash on some computers. "

So, all fixed!

 

[Dwarf]

Hi Tloram,

Pleased to see that you have solved your problem. Unfortunately, I don't think that anyone here would have been able to come up with that solution for you as you didn't mention anything about the 'AlphaCool LCD' USB module that you had installed in your system. In fact, it was only when I followed the link that you provided in your last post that I found out about this.
Dwarf