USB Root Hubs - Can't clear code 41


P

PacMedTran

I plugged a Korg Nanokey into one of the four USB ports on my Dell Inspiron
E1505. Windows recognized it (dong-DING), then a few seconds later the
NanoKey, my graphics tablet and two external drives all went bye-bye
(dong-dong-dong).

In the Device Manager, all the USB Root Hubs are malfunctioned with an error
41 (drivers working, but hardware not). All of the fixes I've found on the
Web --uninstalling/reinstalling the root hubs, reinstalling drivers, running
Add New Hardware, last good configuration, etc. -- fail to fix.
Doubleplusunpleased.

I don't think that there was a power issue, because these are all integrated
ports, only one drive and the graphics tablet ran off USB power, and the USB
chipset has since passed a bootup diagnostic. Also, the peripherals
(EXCLUDING the NanoKey) are getting power during bootup, and are even
recognized for a moment before being shut down again. Windows just can't
"see" anything plugged into any of the USB ports.

Before I take the NanoKey back to the store and insert it into the salesman,
has anyone had this problem? More importantly, has anyone *fixed* this
problem? Again, I've gone through all the usual steps of uninstalling and
then reinstalling. What do you do when none of that works?
 
Ad

Advertisements

P

Paul

PacMedTran said:
I plugged a Korg Nanokey into one of the four USB ports on my Dell Inspiron
E1505. Windows recognized it (dong-DING), then a few seconds later the
NanoKey, my graphics tablet and two external drives all went bye-bye
(dong-dong-dong).

In the Device Manager, all the USB Root Hubs are malfunctioned with an error
41 (drivers working, but hardware not). All of the fixes I've found on the
Web --uninstalling/reinstalling the root hubs, reinstalling drivers, running
Add New Hardware, last good configuration, etc. -- fail to fix.
Doubleplusunpleased.

I don't think that there was a power issue, because these are all integrated
ports, only one drive and the graphics tablet ran off USB power, and the USB
chipset has since passed a bootup diagnostic. Also, the peripherals
(EXCLUDING the NanoKey) are getting power during bootup, and are even
recognized for a moment before being shut down again. Windows just can't
"see" anything plugged into any of the USB ports.

Before I take the NanoKey back to the store and insert it into the salesman,
has anyone had this problem? More importantly, has anyone *fixed* this
problem? Again, I've gone through all the usual steps of uninstalling and
then reinstalling. What do you do when none of that works?

Is there any possibility the Nanokey had a mass storage section with an
Autorun file, and has attempted to install software on your computer ?
Did the computer have any AV running, to scan mass storage devices ?
Or was the machine wide open ?

The only decent utility I know of, for looking at USB peripherals connected
directly to the computer is this. But this won't materially alter your
situation. It basically gives about as much info as Device Manager.
If you see "Endpoints" listed in the right hand window, it means the
device has been configured. Any other response, your guess is as good
as mine.

Finding this utility became harder recently, and these are the last
two links I know of. The utility used to be on archive.org, but I
guess Microsoft made them remove it. This originally was a Microsoft
download.

*******
ftp://ftp.efo.ru/pub/ftdichip/Utilities/UVCView.x86.exe
http://www.users.on.net/~fzabkar/USB_IDs/UVCView.x86.exe

File size is 167,232 bytes.
MD5sum is 93244d84d79314898e62d21cecc4ca5e

This is a picture of what the UVCView info looks like.

http://www.die.de/blog/content/binary/usbview.png

Some information on the parameters seen in UVCView.

http://www.beyondlogic.org/usbnutshell/usb5.htm
*******

Also, have a look in the setupapi.log file on your C: drive.
It should have log events for the initial insertion of the Nanokey
and later, your attempts to get anything USB running. Entries
are made there, when new hardware is discovered. When the file
gets big enough, Windows may start a new one.

C:\WINDOWS\setupapi.log

Good luck,
Paul
 
P

PacMedTran

Paul said:
Is there any possibility the Nanokey had a mass storage section with an
Autorun file, and has attempted to install software on your computer ?
Did the computer have any AV running, to scan mass storage devices ?
Or was the machine wide open ?

The only decent utility I know of...
Also, have a look in the setupapi.log file on your C: drive.
It should have log events for the initial insertion of the Nanokey
and later, your attempts to get anything USB running. Entries
are made there, when new hardware is discovered. When the file
gets big enough, Windows may start a new one.

C:\WINDOWS\setupapi.log

Good luck,
Paul

I don't think that it has any mass storage, but it was supposed to install a
driver on plug-in. No other applications were running at the time.

I tried again this morning. Tablet and two drives plugged in, NanoKey NOT
plugged in. In Device Manager I uninstalled the root hubs (5 of them), then
scanned for software changes. At first it started to "read" one of the root
hubs correctly, and my tablet started working, for about 15 sec. Then four
"unknown devices" appeared in the manager, disappeared, and the five "broken"
root hub devices showed again.

Below is the setupapi log for those events. A very long log, making this a
massive post, for which I apologize. But hopefully someone can see something
that I can't. Thanks for your help.

[2009/12/20 09:04:13 2172.350]
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe"
C:\WINDOWS\system32\devmgmt.msc /s
#-166 Device install function: DIF_REMOVE.
#I289 Removing device "USB\ROOT_HUB\4&10D90B96&0".
#I048 Device removed.
[2009/12/20 09:04:27 2172.775]
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe"
C:\WINDOWS\system32\devmgmt.msc /s
#-166 Device install function: DIF_REMOVE.
#I289 Removing device "USB\ROOT_HUB\4&2263344D&0".
#I048 Device removed.
[2009/12/20 09:04:35 2172.1199]
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe"
C:\WINDOWS\system32\devmgmt.msc /s
#-166 Device install function: DIF_REMOVE.
#I289 Removing device "USB\ROOT_HUB\4&27A8915E&0".
#I048 Device removed.
[2009/12/20 09:04:41 2172.1622]
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe"
C:\WINDOWS\system32\devmgmt.msc /s
#-166 Device install function: DIF_REMOVE.
#I289 Removing device "USB\ROOT_HUB\4&3932BA15&0".
#I048 Device removed.
[2009/12/20 09:04:48 2172.2044]
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe"
C:\WINDOWS\system32\devmgmt.msc /s
#-166 Device install function: DIF_REMOVE.
#I289 Removing device "USB\ROOT_HUB20\4&1A83CD01&0".
#I048 Device removed.
[2009/12/20 09:04:59 1112.3 Driver Install]
#-019 Searching for hardware ID(s):
usb\root_hub&vid8086&pid27c8&rev0001,usb\root_hub&vid8086&pid27c8,usb\root_hub
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\ROOT_HUB" in C:\WINDOWS\inf\usbport.inf; Device: "USB Root
Hub"; Driver: "USB Root Hub"; Provider: "Microsoft"; Mfg: "(Standard USB Host
Controller)"; Section name: "ROOTHUB.Dev".
#I023 Actual install section: [ROOTHUB.Dev.NT]. Rank: 0x00000002. Effective
driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [ROOTHUB.Dev] in
"c:\windows\inf\usbport.inf".
#I320 Class GUID of device remains: {36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\ROOT_HUB\4&10D90B96&0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [ROOTHUB.Dev.NT.Interfaces] from
"c:\windows\inf\usbport.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\ROOT_HUB\4&10D90B96&0".
#I121 Device install of "USB\ROOT_HUB\4&10D90B96&0" finished successfully.
[2009/12/20 09:05:03 1112.7 Driver Install]
#-019 Searching for hardware ID(s):
usb\root_hub&vid8086&pid27c9&rev0001,usb\root_hub&vid8086&pid27c9,usb\root_hub
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\ROOT_HUB" in C:\WINDOWS\inf\usbport.inf; Device: "USB Root
Hub"; Driver: "USB Root Hub"; Provider: "Microsoft"; Mfg: "(Standard USB Host
Controller)"; Section name: "ROOTHUB.Dev".
#I023 Actual install section: [ROOTHUB.Dev.NT]. Rank: 0x00000002. Effective
driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [ROOTHUB.Dev] in
"c:\windows\inf\usbport.inf".
#I320 Class GUID of device remains: {36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\ROOT_HUB\4&3932BA15&0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [ROOTHUB.Dev.NT.Interfaces] from
"c:\windows\inf\usbport.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\ROOT_HUB\4&3932BA15&0".
#I121 Device install of "USB\ROOT_HUB\4&3932BA15&0" finished successfully.
[2009/12/20 09:05:07 1112.11 Driver Install]
#-019 Searching for hardware ID(s):
usb\root_hub&vid8086&pid27ca&rev0001,usb\root_hub&vid8086&pid27ca,usb\root_hub
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\ROOT_HUB" in C:\WINDOWS\inf\usbport.inf; Device: "USB Root
Hub"; Driver: "USB Root Hub"; Provider: "Microsoft"; Mfg: "(Standard USB Host
Controller)"; Section name: "ROOTHUB.Dev".
#I023 Actual install section: [ROOTHUB.Dev.NT]. Rank: 0x00000002. Effective
driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [ROOTHUB.Dev] in
"c:\windows\inf\usbport.inf".
#I320 Class GUID of device remains: {36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\ROOT_HUB\4&2263344D&0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [ROOTHUB.Dev.NT.Interfaces] from
"c:\windows\inf\usbport.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\ROOT_HUB\4&2263344D&0".
#I121 Device install of "USB\ROOT_HUB\4&2263344D&0" finished successfully.
[2009/12/20 09:05:11 1112.15 Driver Install]
#-019 Searching for hardware ID(s):
usb\root_hub&vid8086&pid27cb&rev0001,usb\root_hub&vid8086&pid27cb,usb\root_hub
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\ROOT_HUB" in C:\WINDOWS\inf\usbport.inf; Device: "USB Root
Hub"; Driver: "USB Root Hub"; Provider: "Microsoft"; Mfg: "(Standard USB Host
Controller)"; Section name: "ROOTHUB.Dev".
#I023 Actual install section: [ROOTHUB.Dev.NT]. Rank: 0x00000002. Effective
driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [ROOTHUB.Dev] in
"c:\windows\inf\usbport.inf".
#I320 Class GUID of device remains: {36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\ROOT_HUB\4&27A8915E&0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [ROOTHUB.Dev.NT.Interfaces] from
"c:\windows\inf\usbport.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\ROOT_HUB\4&27A8915E&0".
#I121 Device install of "USB\ROOT_HUB\4&27A8915E&0" finished successfully.
[2009/12/20 09:05:15 1112.19 Driver Install]
#-019 Searching for hardware ID(s):
usb\root_hub20&vid8086&pid27cc&rev0001,usb\root_hub20&vid8086&pid27cc,usb\root_hub20
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\ROOT_HUB20" in C:\WINDOWS\inf\usbport.inf; Device: "USB
Root Hub"; Driver: "USB Root Hub"; Provider: "Microsoft"; Mfg: "(Standard USB
Host Controller)"; Section name: "ROOTHUB.Dev".
#I023 Actual install section: [ROOTHUB.Dev.NT]. Rank: 0x00000002. Effective
driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [ROOTHUB.Dev] in
"c:\windows\inf\usbport.inf".
#I320 Class GUID of device remains: {36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\ROOT_HUB20\4&1A83CD01&0".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [ROOTHUB.Dev.NT.Interfaces] from
"c:\windows\inf\usbport.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\ROOT_HUB20\4&1A83CD01&0".
#I121 Device install of "USB\ROOT_HUB20\4&1A83CD01&0" finished successfully.
[2009/12/20 09:05:02 1992.14]
#-199 Executing "C:\WINDOWS\system32\libusbd-nt.exe" with command line:
system32\libusbd-nt.exe
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "USB\ROOT_HUB\4&10D90B96&0".
#I163 Device not started: Device has problem: 0x13: CM_PROB_REGISTRY.
#I304 DICS_PROPCHANGE: Device could not be restarted.
[2009/12/20 09:05:02 1992.15]
#-199 Executing "C:\WINDOWS\system32\libusbd-nt.exe" with command line:
system32\libusbd-nt.exe
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "USB\ROOT_HUB\4&2263344D&0".
#I163 Device not started: Device has problem: 0x13: CM_PROB_REGISTRY.
#I304 DICS_PROPCHANGE: Device could not be restarted.
[2009/12/20 09:05:02 1992.16]
#-199 Executing "C:\WINDOWS\system32\libusbd-nt.exe" with command line:
system32\libusbd-nt.exe
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "USB\ROOT_HUB\4&27A8915E&0".
#I163 Device not started: Device has problem: 0x13: CM_PROB_REGISTRY.
#I304 DICS_PROPCHANGE: Device could not be restarted.
[2009/12/20 09:05:02 1992.17]
#-199 Executing "C:\WINDOWS\system32\libusbd-nt.exe" with command line:
system32\libusbd-nt.exe
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "USB\ROOT_HUB\4&3932BA15&0".
#I163 Device not started: Device has problem: 0x13: CM_PROB_REGISTRY.
#I304 DICS_PROPCHANGE: Device could not be restarted.
[2009/12/20 09:05:02 1992.18]
#-199 Executing "C:\WINDOWS\system32\libusbd-nt.exe" with command line:
system32\libusbd-nt.exe
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "USB\ROOT_HUB20\4&1A83CD01&0".
#I163 Device not started: Device has problem: 0x29:
CM_PROB_LEGACY_SERVICE_NO_DEVICES.
#I304 DICS_PROPCHANGE: Device could not be restarted.
[2009/12/20 09:05:33 1112.3 Driver Install]
#-019 Searching for hardware ID(s):
usb\vid_056a&pid_0017&rev_0113,usb\vid_056a&pid_0017
#-018 Searching for compatible ID(s):
usb\class_03&subclass_01&prot_02,usb\class_03&subclass_01,usb\class_03
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\Class_03&SubClass_01" in C:\WINDOWS\inf\input.inf; Device:
"USB Human Interface Device"; Driver: "USB Human Interface Device"; Provider:
"Microsoft"; Mfg: "(Standard system devices)"; Section name: "HID_Inst".
#I023 Actual install section: [HID_Inst.NT]. Rank: 0x00003101. Effective
driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [HID_Inst] in
"c:\windows\inf\input.inf".
#I320 Class GUID of device remains: {745A17A0-74D3-11D0-B6FE-00A0C90F57DA}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\VID_056A&PID_0017\5&2CD8A58F&4&1".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [HID_Inst.NT.Interfaces] from
"c:\windows\inf\input.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_056A&PID_0017\5&2CD8A58F&4&1".
#I121 Device install of "USB\VID_056A&PID_0017\5&2CD8A58F&4&1" finished
successfully.
 
P

PacMedTran

(yada yada yada)
My initial reaction is, *what* is this ? There isn't one
of those on my system (WinXP x32 SP3).

C:\WINDOWS\system32\libusbd-nt.exe

I'd say the "nano" has torpedoed your system, and you
should talk to their Tech Support for an answer. Assuming
that is where the file came from. Can you see that file
on the Nano itself ? Maybe their Tech Support can provide
a "cleaning" utility, to repair the damage done. Some
USB devices have a thing like a CD partition, on which they
have instruments of evil (bundled software for automated install).
...

You seem to have put your finger right on it.

The consensus I got from Google is that "libusbd-nt.exe is a LibUsb-Win32 -
Generic USB Library from http://libusb-win32.sourceforge.net belonging to
LibUsb-Win32."

In /system32 I found three related files: libusbd-nt.exe, libusbd-9x.exe,
and libusbd0.dll. They passed virus and malware scans. I "REMmed" these out
and then downloaded and installed the update from the sourceforge address.
Poof, problem gone; the hubs are working fine now, and my tablet and drives
are up and running again. The two .exe files don't seem to do anything, but
the .dll file was replaced by the update.

My guess is that the Nanokey either installed a corrupt DLL, or corrupted
the DLL already on the system. Now you know as much as I do. :blush:/ The
NanoKey, BTW, is an itty bitty MIDI keyboard. As far as I can see it's just
a controller; yet the installation instructions said that *it* would install
the driver when plugged in. So I will try to get some answers from Korg
before I try plugging it in again.

Anyway, all's well that ends. Thank you so much for your attention and
help. And happy holidays.
 
Ad

Advertisements

P

Paul

PacMedTran said:
You seem to have put your finger right on it.

The consensus I got from Google is that "libusbd-nt.exe is a LibUsb-Win32 -
Generic USB Library from http://libusb-win32.sourceforge.net belonging to
LibUsb-Win32."

In /system32 I found three related files: libusbd-nt.exe, libusbd-9x.exe,
and libusbd0.dll. They passed virus and malware scans. I "REMmed" these out
and then downloaded and installed the update from the sourceforge address.
Poof, problem gone; the hubs are working fine now, and my tablet and drives
are up and running again. The two .exe files don't seem to do anything, but
the .dll file was replaced by the update.

My guess is that the Nanokey either installed a corrupt DLL, or corrupted
the DLL already on the system. Now you know as much as I do. :blush:/ The
NanoKey, BTW, is an itty bitty MIDI keyboard. As far as I can see it's just
a controller; yet the installation instructions said that *it* would install
the driver when plugged in. So I will try to get some answers from Korg
before I try plugging it in again.

Anyway, all's well that ends. Thank you so much for your attention and
help. And happy holidays.

I hope it remains stable for you. It could be, the next time
you plug it in, it'll do the install again and blow away
your repair work. You may have to figure out how to stop
an autorun, if the problem persists. There might be an autorun
file on the Nano.

Paul
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top