Unknown USB Device (Device Descriptor Request Failed) with X870E TOMAHAWK WIFI

uVSthe157902e5

uVSthe157902e5

New member
Joined
Apr 20, 2025
Messages
14
Does anyone know how to fix this? I am running a MAG X870E TOMAHAWK WIFI with Windows 11 24H2.


Screenshot 2025-04-19 202321.png
 
Sort by date Sort by votes
Un-plug the device and plug it back in

My headphones sometimes cause this to happen
This time was Game controller
1745128783871.png
 
Upvote 0 Downvote
Alan J T said:
Un-plug the device and plug it back in

My headphones sometimes cause this to happen
This time was Game controller
View attachment 201144
Click to expand...
Thanks for the reply. It's there even when nothing is plugged into the USB ports. The only things I have plugged into the USB headers on the motherboard are the USB ports on my PC case and a 5.25" bay media hub with more USB ports card readers.
 
Upvote 0 Downvote
It's the reader, I had the same problem. I had mine plugged into a usb port on motherboard. So easy to verify it unplug the reader from the USB motherboard port.
 
Upvote 0 Downvote
autotech21200 said:
It's the reader, I had the same problem. I had mine plugged into a usb port on motherboard. So easy to verify it unplug the reader from the USB motherboard port.
Click to expand...
Thanks, I unplugged the USB 2.0 ports on my case and the error went away. I plugged them back in and the error is still gone. Hopefully the error does not come back. I didn't think it was the ports themselves since any USB device I plugged into them worked fine. Do you have any idea what exactly caused the error?
 
Last edited:
Upvote 0 Downvote
uVSthe157902e5 said:
Do you have any idea what exactly caused the error?
Click to expand...
Most likely drivers are not loading correctly
Another cause is that the Device powering up with no drives getting loaded causes an error.
I have a USB Blu-ray player Burner that will do it every time if it is connected.
So I only plug it in when I use it
 
Upvote 0 Downvote
Alan J T said:
Most likely drivers are not loading correctly
Another cause is that the Device powering up with no drives getting loaded causes an error.
I have a USB Blu-ray player Burner that will do it every time if it is connected.
So I only plug it in when I use it
Click to expand...
If the driver is not loading correctly, is it a Windows bug that can be fixed in software or is that a sign of hardware failure on the case's part?
 
Upvote 0 Downvote
On mine is that with my reader was older so it wasn't picking it up I bought a newer reader and put it in there and didn't have that problem anymore if you use the reader you have now with the USB device it'll probably come up and say air unknown device but it'll still read whatever you plug into it
 
Upvote 0 Downvote
Device Descriptor Request Failed means that there is a problem with communications on one of your “active” USB devices. You don’t get that type of error if there is no device connection.

There are several causes for this:
1. The USB devices isn’t getting enough power (most common)
2. Overclocking
3. Loose USB cable and/or USB port itself is not ensuring solid electrical contacts (which relates to #1)
4. Driver issue (if you device has been working or it’s intermittent than unlikely to be a driver issue)
5. If it’s a USB-C device, try getting USB-C to A adapter and plug into a USB3-A port.

Unfortunately the USB specification and even cable type specification is horrible … USB-C being the worst connector and port specification. USB-C ports are fragile at best and prone to electrical contact issues. The connector itself doesn’t lock into position (like say DP connectors or RJ45) so it’s easily wiggled loose over time and use. Add to the USB-C mess are the cable types and their rating which only until recently are required to put the speed rating on the cable. Then we have USB-C data only vs. USB-C power and data vs. USB-C power, charge and data, video support, 10G, 20G, 40G etc. USB-IF (a non-profit organization funded by only those companies that want a new spec) is hopelessly under funded and much of what they do is to appease the few companies that toss them $$$ to make a spec they want (often do to size rather than safe functionality, looking at you Apple).

And then we have the actual USB controller specification that left huge holes of interpretation leaving circuit designs getting different implementations which is why we have all these, “oh that chipset has issue with some USB devices”.

Then we have limits on the number of connected devices, supposed to be 127 per USB port … which is almost comical. In real world application you’ll be lucky to get 12 USB devices working correctly until they all start to power cycle trigger OS warnings/errors.

I’ve tried my best to move away from devices that rely on USB-C or A and buy devices that operate via Ethernet RJ45. These devices aren’t subject to the ridiculous short cable length max that USB is limited to. Since most local ethernet networks these days are 10G or higher, you get the same speed benefits, can run hundreds of feet without signal issues, access to the device thru a well established network protocol allowing for centralized management, can operate real world many more devices/connections. I’m hoping device manufacturers get a clue and stop using USB specifications and go with RJ45 ethernet.
 
Upvote 0 Downvote
The error came back. :mad:

The PC I'm having the issue with is the Thermaltake V100 Perforated. The problem only affects the front USB 2.0 ports.

https://thermaltakeusa.com/products/v100-perforated-ca-1k7-00m1nn-01

The error in Device Manager keeps coming back. It disappears temporarily, usually after I disconnect and reconnect the USB header, but then reappears after a few power cycles. I’ve tried reattaching the cable and it clears the issue for a bit, but then it returns again after rebooting a few times. Why would the error disappeared and then come back?
 
Upvote 0 Downvote
Is your PC overclocked at all? (EXPO and XMP is overclocked)? If yes, disable that and test.
If problem persists, then it’s likely the cable connection between your motherboard and case external USB port (the USB tester below would confirm). You’ll need to verify the pins in the housing are not being pushed out and making good contact. But again, below tool should reveal any voltage changes over time (allow for logging).

Do you have a USB port diagnostics tool? I use this one because it also can display D-/D+ (data) and log over time:
https://www.amazon.com/FNIRSI-Multi...ion-Measurement/dp/B0BJ253W31?ref_=ast_sto_dp
But it might be cheaper to just buy a PCIe USB 2.0 card and slot it into your motherboard. Not sure why you linked the Thermaltake case?
 
Upvote 0 Downvote
Thanks so much! That might’ve been the issue. EXPO was originally set to Profile 1 — I disabled it, and the error disappeared. I then went back into the BIOS and re-enabled Profile 1, and the error didn’t return. So far, so good! I had linked to the Thermaltake case earlier because that’s the one I’m using, just in case the issue was related to the USB ports on the case itself. Thankfully, that doesn’t seem to be the problem.
I guess if the error comes back, that would mean I can’t rely on the factory EXPO profile, and I’d need to manually tune a custom one instead?
 
Upvote 0 Downvote
I would turn EXPO off for a while and continue without EXPO for a week or so (or however long of a duration you think is good to confirm) to see if it really does “fix the issue”. You’ll take a bit of a performance hit, but this is just for diagnostics purposes. If your issue returns with EXPO off, then that likely narrows the problem down to USB cable/connection issue. I would NOT turn EXPO off then back on again immediately … give it some time OFF.

IMHO, EXPO and XMP profiles are almost pointless, they give a “rough” idea of how a SINGLE module might work on a specific motherboard. Since motherboards vary in build quality, number of layers, etc. use EXPO profiles as a “guide” and not the final setting. Even when looking in the MEMORY QC listing of a motherboard manufacturer, you’ll rarely see an exact match UPC/serial to modules that are sold retail.

If you can confirm EXPO off for a week or so is a fix for your USB issue, then you’ll have to do a custom EXPO profile and see what works (pain to do as it requires A LOT of memory stress testing).
 
Upvote 0 Downvote
Yes, RAM will use JEDEC spec which is typically lower voltage (1.1-1.2). It will run at default clocks, it will be slower on average by about 5-10%. I would not call this “under-clock” it’s more “default spec” clock.

Like I suggested, you want to run this for a week or so as diagnostic test … if you don’t encounter your USB issue, then you know is related to your EXPO memory profile.
 
Upvote 0 Downvote
robain155e02e2 said:
Yes, RAM will use JEDEC spec which is typically lower voltage (1.1-1.2). It will run at default clocks, it will be slower on average by about 5-10%. I would not call this “under-clock” it’s more “default spec” clock.

Like I suggested, you want to run this for a week or so as diagnostic test … if you don’t encounter your USB issue, then you know is related to your EXPO memory profile.
Click to expand...
The error came back. I turned off EXPO, did a power cycle, error is gone again. I'll keep EXPO for now unless I see the error come back.

This is the RAM I have. Whatever profile I had going displayed the advertised specs. Are those not the default clocks?
 
Upvote 0 Downvote
You must log in or register to reply.
Back
Top