I think there might be an issue with the integrated usb controller in my ryzen 5 1600.
USB devices are constantly failing, randomly disconnecting and at times not even visible when cold booting.
I have tried three different wireless network adapters with the same results. All drivers are up to date, latest chipset drivers and mobo firmware has been installed.
Steps I have done to resolve the issue:
- replaced mobo, ram, power supply.
-used latest firmware on both motherboards
-used latest chipset drivers
- checked voltages are correct
-tested multiple adapter drivers
- installed fresh installs of windows 10 3 times
-adjusted windows power settings
Current motherboard is MSI B350 Tomahawk with latest firmware, but I have also tested with an ASROCK B350 motherboard with the same results.
please tell me what my options are and if this is a known issue.
I am unable to return the processor to the store it was purchased from because it has passed the date of the stores return policy.
I'm having similar issues with a Threadripper 1950x and an Asus Zenith Extreme mobo. Our USB device disconnects randomly, and when it is connected, performance latency is huge. Also have latest drivers, firmware, and even tried a PCIe USB card with the same results.
That sounds like it might be a different issue because of the pcie card if
the card contains its own usb controller. double check your power supply to
make sure it is beefy enough for your system, check your voltages and
consider replacing it with a higher wattage unit.
We are seeing it will all of the onboard USB controllers as well. Power supply has plenty of clearance to power the card, so I'm pretty sure that's not the issue. When the issue we're seeing presents itself, it is basically exactly the same for onboard USB as it is for the PCIe USB card. Just thought I'd chime in since it sounded similar to what I've been seeing, even if it's Ryzen vs Threadripper.
Well, I solved the problem for finally. Had to manually override the USB drivers that Windows wanted to use, with the ones in the AMD Chipset package. Don't know why it wouldn't use those to begin with, and it wants to revert back to the generic Microsoft drivers if I allow it to. Really frustrating that installing the AMD Chipset drivers didn't force Windows to use its drivers in the first place. If it helps, I manually selected the drivers from C:\AMD\AMD-Chipset-Drivers\Packages\Drivers\SBDrv\USB... and then the corresponding ones for the controllers and hubs.
I've tried those drivers and I Believe they are only for windows 7 I wasn't
able to get them to work can to tell me exactly what files and the location
u are using.... Are u running windows 10 or 7?
I'm running Windows 10, and it does appear that the only ones in there are Windows 7, but they seem to work fine, and definitely better than the default Microsoft ones. For the hubs I'm using C:\AMD\AMD-Chipset-Drivers\Packages\Drivers\SBDrv\USB30_ZP\amdhub\W764A\ and for the controllers I'm using C:\AMD\AMD-Chipset-Drivers-Software\Packages\Drivers\SBDrv\USB30_ZP\amdxhc\W764A\.
My system is Ryzen 2700x and Asrock X570 Phantom Gaming and USB3_3_4 do not work. 1st just one of these ports did get errors and other port works, then both of these did not. They charge devices. other port do not detect anything and other give error. Even in BIOS these ports do not work. I had RMA'd motherboard and both of them same USB port did not work.
Somehow one random Kingston Datatraveller 100 G3 stick worked. Now I updated AMD drivers via Asrock page called AllIn1(v19.10.16_19H1_WHQL) and now both USB port works as they should (will see how long)
Now CPU-> says that i got AMD AGESA Combo-AM4 188.8.131.52 and this is somekind of microcode, but does it have anything to do with USB controller??
I also have this issue. I at first thought it was my motherboard, which has it's own problems, but after switching from an MSIx470 Gaming Plus to an Asus x570 Tuf Plus Wifi, I still have the same issues. I am unable to share USB ports, period. USB will also randomly drop out. So it is obvious at this point the processor is at fault.