TheOco Posted January 18, 2021 Posted January 18, 2021 There is also a new sata-powered NZXT USB 2.0 hub but one of the comments says that on Gigabyte x570 they're getting our disconnect problem. Although, on the older molex-powered one people dont seem to have the same problem? Regardless, I think I'll only go straight into the Mobo. I wonder if something like https://www.amazon.com/WYMECT-Motherboard-Header-Extension-Splitter/dp/B07NTL8179/ would work or if there would be lesser functionality because it's cheap and is cutting a corner somewhere. I think the problem with any hub like this is that they still use the USB 2.0 mobo header, which is the I/O we don't want to use since that's where the driver/chipset issue resides. Any device plugged into one of these hubs gets routed thru the USB 2.0 header and subsequently thru the USB 2.0 controller on the chipset. On my setup, since I unplugged the Commanders from the 2.0 headers, I've had zero problems with USB devices. I did some looking last night for an adapter and wonder if THIS ONE would provide a workaround. Using this adapter, you'd be connecting the Commander Pro to the USB 3.0 mobo header. It would take away my ability to have ports on the front of my case, but might be worth it to test the theory that it's 100% USB 2.0 which is causing the problems and that USB 3.0 is stable.
Aeternus Posted January 18, 2021 Posted January 18, 2021 That's exactly what I've been thinking of doing, except things plugged directly into my USB 2.0 headers work perfectly fine. I have my Commander Pro and Commander Core plugged into my two mobo USB 2.0 headers and they work fine and have never once disconnected on x570. So I might get the adapter you linked and plug my Lighting Node Core into it (since it's currently plugged into my Co Pro and using that as a USB hub is where I'm having my issues).
TheOco Posted January 18, 2021 Posted January 18, 2021 (edited) That's exactly what I've been thinking of doing, except things plugged directly into my USB 2.0 headers work perfectly fine. I have my Commander Pro and Commander Core plugged into my two mobo USB 2.0 headers and they work fine and have never once disconnected on x570. So I might get the adapter you linked and plug my Lighting Node Core into it (since it's currently plugged into my Co Pro and using that as a USB hub is where I'm having my issues). Ah, I must have missed those details. However, I wonder if when you do get the 2.0 - 3.0 adapter, if you plug your Commander Pro into that, and then plug your Commander Core and Lighting Node Core into the hubs on the Commander Pro, would everything then work as it should? I'm also curious as to why your board doesn't disconnect your Commander Pro while mine does like clockwork. Nothing is recognized on the 2.0 hubs on my Commander Pro, and just having it plugged in causes my entire USB system - including my USB 3.2 ports - to experience disconnects. Edited January 18, 2021 by TheOco
Kaiser84 Posted January 22, 2021 Posted January 22, 2021 There is also a new sata-powered NZXT USB 2.0 hub but one of the comments says that on Gigabyte x570 they're getting our disconnect problem. Although, on the older molex-powered one people dont seem to have the same problem? Regardless, I think I'll only go straight into the Mobo. I wonder if something like https://www.amazon.com/WYMECT-Motherboard-Header-Extension-Splitter/dp/B07NTL8179/ would work or if there would be lesser functionality because it's cheap and is cutting a corner somewhere. I have the molex one and keep getting usb disconnection with a Rog B550-E and a h115i Cappellix
dreadlockunicor Posted January 22, 2021 Author Posted January 22, 2021 Literally no fixes work. This POS is getting returned. ARCTIC Liquid Freezer II is going in. No RGB bull**** is worth this big of a headache. Keep it simple, stupid. At least on the bright side for Corsair I had to upgrade my 450D case to an Air 540 to get this THICC radiator to fit.
Kaiser84 Posted January 23, 2021 Posted January 23, 2021 (edited) Only way to solve is connecting to a USB 3 instead of USB 2 with an adapter. Solved all problems, I have both GEN 4 in BIOS, the Corsair controller will disrupt any USB you connect it to, so you can only fix this by isolating it in another controller, luckily I have two USB 3 connectors, so I can use one for the iCue and one for the front panel. Edited January 23, 2021 by Kaiser84
USS_Ustafish Posted January 23, 2021 Posted January 23, 2021 The PCI-E 4.0 bug isn't an issue as I've set everything to gen 3 and it still didnt work. I even updated to 1.2.0.0 AGESA. Chipsets are all up to date, but now my RGB is static, my fans are at full blast on default, and I still can't detect the cooler...this continues to be a horrible experience for a premium product. Same. I've had better luck with cheap UpHere and Dark Horse RGB than I'm having with this Corsair garbage, that I payed TOP DOLLAR for. I honestly don't understand how this junk justifies such a premium.
dreadlockunicor Posted January 24, 2021 Author Posted January 24, 2021 ARCTIC FREEZER II was the solution. Never buying a Corsair AIO again. 27C idle, 72C on hour stress test, quiet as can be, no stupid software. YEET, good riddance, I'm out.
puglord Posted February 20, 2021 Posted February 20, 2021 ARCTIC FREEZER II was the solution. Never buying a Corsair AIO again. 27C idle, 72C on hour stress test, quiet as can be, no stupid software. YEET, good riddance, I'm out. Good info thanks. This thread is the same issue I've been struggling with, except with a ROG Maximus XII Hero motherboard. Worse part of the saga of the driver issue for me was I finally gave up - then randomly a week later it started working as if nothing was wrong. ...then ran reliably for about 2-3 days and then would randomly disconnect one fan on the radiator, if I would do a firmware update it would come back. Rebooted the other day and it's back to having a driver error. Such trash for the price.
Recommended Posts