Unknown Usb Device (device Descriptor Request Failed) Driver Error

0 views

Skip to first unread message

Martez Fields

unread,

Aug 3, 2024, 10:57:05 AM8/3/24

to issuchorern

It's listed under USB controllers in device manager. I unplugged and replugged my H100i Platinum AIO from the USB header this morning and noticed it went away but the error returned. Also my Void Pro Wireless headset is disconnecting/reconnecting when this occurs multiple times, 5-6 and then reconnects. Been watching device monitor all day and have actually witnessed the headset do that in it.

That's likely caused by the iCue crash bug/USB disconnect/reconnect on iCue startup with H1xxi RGB Platinum coolers. If it happens multiple times, the USB driver can crash and then you get that error. Restarting your computer should fix it until it happens again, but you'd likely want to try the workaround in my signature and see if that helps to keep it away afterwards. The more USB devices you have connected, the higher the probability will be that the driver crashes when it happens.

Also, you can try deleting the device that gives an error from devices manager and restarting your computer. It should be re-initialized and hopefully properly installed it on the next Windows Startup.

Here's something even weirder: Anytime I reboot now I get the constant disconnect/reconnect sounds and it usually leads to the device descriptor error in devman. To fix this I have to totally power down for about two minutes (shut down, hit switch on PSU, unplug PSU and let sit). Then after a restart I have to run the repair option in iCUE to get it to recognize all devices and work normally again. No errors at all until I have to reboot and then go through the whole process again. Attaching logs.

This is unrelated to iCUE at this point. The driver is just not registering correctly or it's getting blocked by something on launch or there's something wrong with the cooler's USB connection. It has to be on of those things.

I may have fixed this but in doing so created a new problem. I'm running two copro's with the AIO. I had the copro's connected in series to one USB header on the motherboard and the AIO connected to the other. Also right next to these headers is a USB 3.1 header that I had a hub plugged into and was wondering if maybe all those together is causing too much of a power draw? (I'm not an electrical engineer so this is a SWAG at it from me.)

I totally uninstalled iCUE including registry entries, shut down and did some rewiring. Now I have each of the copro's going to the two motherboard headers and the AIO connected to the header on copro #1. I have another USB 3.1 header on the side of the board so switched that hub over to it. Booted back up, reinstalled iCUE (3.15.101), setup the fans and light strips and all is working fine, no USB disconnect sounds (except for an initial one when I launch iCUE, I don't have it set to run on startup, don't get any after it is up) and I no longer have the device descriptor error in devman, even after reboots.

Problem is now the RGB from the h100I flickers. Every 30 seconds to a minute the two fans connected to it and the actual cooler lights will flicker. Have tried repairing iCUE to no avail. So close to having it all run perfect, any ideas?

Where did you learn your engineering and blaming skills? :eek: I can provide kernel walks to prove that it is your 2017 driver that can't participate in the bus enumeration, thus not being able to start.

The USB standard supports up to 127 devices, and USB hubs are a part of the standard. A typical USB four-port hub accepts 4 "A" connections. A hub typically has four new ports, but may have many more.

I've been having this issue for weeks now.
I have a Logitech mouse on an Asus x571GT laptop, and one day the Bluetooth connection to my mouse suddenly disappeared.
I checked and the Bluetooth on my laptop disappeared. I checked DEVICE MANAGER and the Bluetooth was gone (unless I selected to show hidden devices) but under the Universal Serial Bus, one of the drivers is called "unknown usb device descriptor request failed" appeared.

If my Bluetooth is working, that error isn't there. The second my Bluetooth disappears, "unknown usb device descriptor request failed" appears under Universal Serial Buses dropdown menu.

I've searched online and...

3) I've uninstalled "unknown usb device descriptor request failed" and restarted the computer. Sometimes the Bluetooth returns and everything is fine for a couple of minutes/hours/days before it suddenly disappears again, and "unknown usb device descriptor request failed" driver reappears

Before, I did not.
But I did find one solution where I had to add the 'unknown usb device descriptor request failed" into the registry, unplug the USB device, power off, and while it was powered off, I disconnected the Power adapter from the laptop. Waited a minute or two, and plugged back in the power adapter, powered it back up, and once I relogged into Windows, then plugged the USB back in.

So far, it's working.....
So far....

uninstalling the intel bluetooth software from "Programs and Features" where you would uninstall software, as opposed to uninstalling device drivers from "device manager" is what solved this problem for me. i uninstalled the software that way and installed the drivers for the bluetooth from my motherboard manufactures website fixed it.

Believe me, I tried EVERRRRRRRRRYTHING.
The latest solution I just tried was selecting the 'unknown usb device descriptor request failed" and adding it to the registry and restarting the computer.
I just did it 30min ago, and so far it's working.
But with this 'unknown usb device descriptor request failed" sometimes it works for a few minutes, hours, days before it crashes.

Hopefully this solution works

If your operating system, BIOS, and drivers are up to date and the issue persists even after performing a full power cycle and uninstalling the intel Bluetooth software from "Programs and Features", the last steps would be to check this issue with Asus since they may need to run some tests on their laptop.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

In order to resolve this issue, your device or any other devices you want to connect with this same issue, I suggest you do this; Open the Windows PowerShell (Admin) and type: chkdsk /f/r/x. It will inform: 'The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)' select Y then re-boot your machine and follow the on screen prompts.
After the reboot, again, Windows PowerShell (Admin) and type: sfc /scannow and allow the process to finish.
Now clean the registry with a reputable program such as CCleaner then take a note of the device/s name and select 'run' from the Windows menu list bottom left.
Type 'regedit' without the apostrophes and open the registry.
Select 'Edit' then Search... and type the brand name of the device in the search bar.
The search results will point you to a series of strings of the device that was giving the *(device descriptor request failed) code 43* error message.
Every string in the registry with the name of your device will need to be deleted but ensure it is the device's name from which was generating this error example; Logitech, Seagate, whatever brands device name that has generated this error code!
Ensure you have removed every last trace of your devices name in the registry.
Then after completion use the CCleaner again to remove all known traces and re-install the devices software if this is the case.
Your device will come back to life without the error message and start to work again.
Reasons why this happen are not entirely certain but often PC's pick up spyware/malware/virus's and corrupt the registry's strings other times, updates and upgrades in particular over lap information and again, corrupt the software and its registration process.

Selecting "USB xHCI Complaint Host Controller" the same issue but shows the "Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)" on device manager. Selecting "Chipset Controller" installing the Chipset Controller on the device manager but the propery shows that "No drivers are installed for this device" . But "Unknown USB Device (Device Descriptor Request Failed" disappears but placing USB, the USB is not found.

Registry Disclaimer: The further steps will involve registry manipulation. Making mistakes while manipulating registry could affect your system adversely. So be careful while editing registry entries and create a System Restore point first.