System Overview
Motherboard: ROG STRIX X870E-E GAMING WIFI(Bios 1804)
CPU: AM5 Ryzen 9 9950x3d
RAM: Corsair Dominator Platinum 64GB DDR5 6400 (2×32), QVL listed
PSU: Corsair HX1500i
Cooling: H170i Elite LCD (with Commander Core)
RGB/Fan Control: Commander Core XT
- GPU: EVGA RTX 3090 Ti FTW3
OS: Windows 11 25H2
Multiple internal powered Corsair 4 port USB hubs
All USB devices disconnect at the exact same time, then reconnect. This was happening at Idle, During active gaming sessions, and under RGB animation load. Interestingly enough this was not happening if I set my RGB to a static color. I would every so often hear the USB disconnect and reconnect sound while ono static, but nothing would actually ever disconnect. Event viewer was showing the USB Root Hub was resetting. So i started going one by one with each piece of hardware and I tested everything.
- Motherboard was RMA'd
- Ram tested at DOCP 6400 (which is QVL Listed)
- Ram tested at JEDEC 4800
- Disabled Global C states, PCIe ASPM, USB Selective Suspend
- Reformatted Windows completely
- Disconnected all of my front panel I/O(USB-A,USB-C,Power/LED/Header Wiring
- Isolated the Commander Core XT and Commander Core each on their own internal powered 9in Hub (Corsiar 4 port Internal Hub)
- Disabled ICUE SDK
- Bypassed my UPS and went straight into the wall.
After all this i was still having the same problem
I bought a 10 port Sabrent powered hub on amazon, first hooked it up to one USB-A port with all my usb devices connected to the Hub, within 10 minutes i had all my usb devices go down while the computer was idle. Finally, I hadn't tried the USB-C ports. So, I got a USB-A to C adapter and hooked it up to the first USB-C port on the back of the IO. Problem hasn't happened since I did that. Seems to be like the 10G hub still has a big problem, either firmware still isn't right, or They have bad controllers on them. My question is, is there a way to tell what firmware version I'm on, because when I update it doesn't really say. There is nowhere in windows that tells me what the firmware version is either. I've spent way more time than id like trying to figure out what was causing this, and it seems kind of sad that a 700-dollar board could have this many problems.
