Jump to content
Corsair LogoCorsair Logo
Corsair Community
CORSAIR COMMUNITY Survey, we want to hear your feedback!

H115i Elite Capellix Commander Core disconnecting on iCUE start up

dreadlockunicor

By dreadlockunicor
in iCUE Software

 Share

Recommended Posts

dreadlockunicor

dreadlockunicor

Posted
Posted

I know this has been posted countless times, but this seems to have been an issue for YEARS. I just bought a H115i Elite Capellix, theres some glitchiness I'm willing to overlook like the flickering corsair logo, but not being able to control anything connected to the Commander Core is driving me crazy. When I install iCue, I hear the USB connection sound. However, immediately upon starting iCUE it disconnects. It does not reconnect unless I restart and keep iCue from starting on start up. I've tried both USB headers and still the same result. Corsair has clearly made this too complicated for their muppet software devs. The cooler itself seems to be underperforming as well. I'm going to rip this thing out if I can't get a fix in a week or two.

 

Motherboard: ASUS ROG Strix x570-E Gaming

Link to comment
Share on other sites
AMDZ

AMDZ

Posted
Posted

I have an ASUS Cross Hair VII that doesnt support PCI 4. I hear the USB disconnect, and I cannot see my H100I and my lightning Node core anymore. I have manually set PCI to GEN3 anywhere I can in the bios..still hear the usb disconnect sound when icue starts up and the LNC and H100i do not appear anymore. I cannot control the rgb lights on them now :(

Help please!

Link to comment
Share on other sites
Aeternus

Aeternus

Posted
Posted
Make sure you aren't experiencing the PCIe 4.0 bug on the X570 platform that is causing USB disconnects by setting your PCIe from Auto or 4.0 to 3.0 and see if the issue persists.

 

Holy crap this actually worked for me. I set all my x570 Dark Hero PCIE slots to 3.0 and the entire issue with the 2 USB ports on Commander Pro not working went away. When the system powers on, I hear one single USB connect sound and everything is detected as it should be in iCUE. It's been about 25 minutes and I restarted twice and no issues yet.

Link to comment
Share on other sites
Aeternus

Aeternus

Posted
Posted
Holy crap this actually worked for me. I set all my x570 Dark Hero PCIE slots to 3.0 and the entire issue with the 2 USB ports on Commander Pro not working went away. When the system powers on, I hear one single USB connect sound and everything is detected as it should be in iCUE. It's been about 25 minutes and I restarted twice and no issues yet.

 

Nevermind, problem came back this morning. I even set PCIE back to auto, rebooted, then back to 3.0, and it's doing the same repeated disconnect. How stupid and annoying...worked perfectly fine all day yesterday.

Link to comment
Share on other sites
  • Corsair Employees
Corsair Notepad

Corsair Notepad

Posted
  • Corsair Employees
Posted
I bought an NZXT USB 2.0 hub as that was helping some people, but it STILL disconnects immediately on starting up the app, even with the newest 3.37 version. I'm about to return this.

 

Did you try my suggestion to make sure its not the AGESA 1.1.0.0 bug with PCIE 4.0 causing the USB disconnects? Have you made sure your chipset driver is completely updated by going to AMD's website directly and downloading an installing it?

 

 

My board doesn’t support pcie 4.0...even when i change to 3.0 from auto issue of disconnect occurs.

 

Your motherboard has two internal USB 2.0 headers but only one is going to be a full USB header which is what you need to make sure you are plugging it into. For your motherboard its the USB header marked USB1112 if you are using the header that is also apart of the ROG_EXT that is marked USB15 it is not likely to work as it should.

 

Also make sure you have downloaded and updated the AMD chipset driver from AMD's website directly as suggested to the previous individual.

 

 

Nevermind, problem came back this morning. I even set PCIE back to auto, rebooted, then back to 3.0, and it's doing the same repeated disconnect. How stupid and annoying...worked perfectly fine all day yesterday.

 

Your system specs aren't listed so its a little difficult to really suggest anything. What motherboard, CPU, and GPU do you have?

Link to comment
Share on other sites
Aeternus

Aeternus

Posted
Posted
Your system specs aren't listed so its a little difficult to really suggest anything. What motherboard, CPU, and GPU do you have?

 

ASUS Crosshair VIII Dark Hero (x570)

AMD 5900x

EVGA 3090 FTW3 Ultra

 

I havent manually installed my chipset drivers because the date of the newest chipset driver is older than the date of the BIOS version it shipped with so presumably it's the newest version as well.

Link to comment
Share on other sites
Aeternus

Aeternus

Posted
Posted
Chipset drivers are completely different than BIOS versions. You should always download and install the latest chipset driver that is available for the x570 chipset from the AMD website.

 

I installed whatever the latest download chipset drivers are and it didn't resolve. Interestingly, yesterday this worked for a little while after starting up. PC made the USB disconnect/reconnect sound about 10 times but it ultimately "caught" and worked for the rest of the night. This morning after booting up I let it disconnect/reconnect for about 10 minutes but it never caught on so I ended up just shutting down and unplugging the two USB 2.0 devices on Commander since I had to start working.

Link to comment
Share on other sites
dreadlockunicor

dreadlockunicor

Posted
  • Author
Posted
Did you try my suggestion to make sure its not the AGESA 1.1.0.0 bug with PCIE 4.0 causing the USB disconnects? Have you made sure your chipset driver is completely updated by going to AMD's website directly and downloading an installing it?

 

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.

Link to comment
Share on other sites
Aeternus

Aeternus

Posted
Posted

Hey dread, I actually just came in here to say that I updated my Dark Hero to the latest Beta Version 3202 drivers (AGESA 1.2.0.0) and so far I "don't have any issues".

 

So I flashed bios, set optimized defaults, shutdown and plugged my stuff back into Commander Pro, and I had exactly the same problem. Actually it was worse, the rate at which stuff was disconnecting and reconnecting was almost comical.

 

I restarted, set all of my PCIE and NVME lanes to 3.0 (they were set to AUTO after the BIOS update/default optimizations) and the issue went away. I restarted again, set the lanes to 4.0 (in ASUS it's listed as GEN 4) and the issue still hasn't returned. I shut down entirely, removed power, held power button to purge, plugged power back in, started back up, and the issue still hasn't come back. I won't get too excited because this problem has been hard to tack down, and as you can see above I thought it was fixed, but then came back... but so far this feels promising. Basically I get into Windows, hear one USB connect sound, and the fans kick into the proper lighting profiles that I had set (since the Lighting node core is connected to one of the Co Pro USB ports.)

 

Fan speed control is correct too. I have two custom profiles for 65% speed and 100% speed and they're responding properly. So just to recap what's working for me so far:

1) Updated chipset drivers from ASUS with whatever the most recent version listed was

2) Updated BIOS to Beta Version 3202 (AGESA V2 PI 1.2.0.0). These were released 1/14/2021

3) Set all my lanes to anything that is NOT AUTO, both Gen 3 and Gen 4 work

 

I'll report back in a couple days if this still works, or I'll report back as soon as it stops working.

Link to comment
Share on other sites
Aeternus

Aeternus

Posted
Posted (edited)
I'm on AGESA 1.2.0.0, tried both gen 3, gen 4, and auto for onboard devices, and updated my AMD chipset with the most recent one from AMD. USB hub or no hub. Most up to date iCue. Still disconnecting on iCue startup on all permutations.

 

But for devices connected directly to motherboard USB port, those work fine? Although I think you just said that even your Co Pro fan speeds are acting weird and presumably that is plugged into a USB 2.0 slot? If I were in your position, knowing that you have your board functionally set up the same as mine, I would probably:

 

1) Completely blow iCUE away just delete it entirely. Plug in nothing except Commander Pro to a USB 2.0 port on the mobo directly. Reinstall iCue, ensure that fan speed is working correctly by making a couple of quick custom profiles. On my other PC which is uhhh.... Intel 2066? Occasionally the pre-set profiles of Quiet, Balanced, and Extreme wouldn't work right. In fact, once after an iCUE update I had the same problem where the speeds would be all over the place, Quiet ran at extreme speeds, etc. So I just set my own custom curves and that worked perfectly.

 

2) Plug in any LED header components to the 2 LED ports to Commander Pro. Make sure it's picking those up properly. E.g. if you're using a Corsair lighting strip, connect it (since it connects directly to CoPro) and make sure you can control the ARGB.

 

3) Plug in one thing that connects to a Co Pro USB headers. If it doesnt work, try connecting it directly to a Motherboard USB 2.0 port... does iCUE recognize it? It should, since this takes the USB forwarding issue totally out of the equation.

 

4) If iCue is fine, meaning that items plugged directly into the Mobo are detected, but Co Pro still gives you problems, I would personally throw in the towel and explore other options like a PCI expansion slot internal USB card, and USB 2.0 splitter cable that goes directly to the mobo, or I would re-purpose a USB 3.0 Gen 1 or Gen 2 slot and get a 2.0 adapter to use that for direct connection. I know it's not ideal, but I would rather give up some front panel I/O functionality to have this working until it somehow gets sorted out.

 

5) Consider RMA of Co Pro if you're still having big control problems with the speed issue because that's 100% a Co Pro thing.

 

Edit - make sure in between plugging or unplugging stuff from Commander Pro you shut down. I speak.......from experience.

Edited by Aeternus
Additional info
Link to comment
Share on other sites
dreadlockunicor

dreadlockunicor

Posted
  • Author
Posted
But for devices connected directly to motherboard USB port, those work fine? Although I think you just said that even your Co Pro fan speeds are acting weird and presumably that is plugged into a USB 2.0 slot? If I were in your position, knowing that you have your board functionally set up the same as mine, I would probably:

 

1) Completely blow iCUE away just delete it entirely. Plug in nothing except Commander Pro to a USB 2.0 port on the mobo directly. Reinstall iCue, ensure that fan speed is working correctly by making a couple of quick custom profiles.

 

I don't think I've made it clear, I cannot detect it ever, never have, and looking like I never will. If I could create fan profiles out of the nether I would, but I can't because this thing has never been detected by iCue, just disconnected. Its all operational on default factory settings, but I cannot control it through software.

Link to comment
Share on other sites
aagstn

aagstn

Posted
Posted
I've been dealing with this for a week with an H100i Elite Cappellix. I tried not starting iCue with Windows and starting it after a few minutes. Sometimes it detects my devices and sometimes it doesn't. Today it isn't detecting anything. After a couple of reboots, the H100i will show up, but with a red exclamation point. I'm done with this software. I'm going to yank out the H100i and just try to find an air cooler.
Link to comment
Share on other sites
TheOco

TheOco

Posted
Posted (edited)

I am having similar issues as well.

 

Setup:

Asus Prime X570-Pro (BIOS 2802)

Ryzen 5 3600

Corsair Vengeance LPX 64GB DDR4-3600

 

Accessories:

Corsair H100i Elite Capellix AIO cooler

Corsair iCue Commander Pro

Corsair iCue Commander Core (came with the AIO)

3x Corsair SP120 RGB Pro Fans

2x Corsair ML120 RGB Pro Fans (came with AIO cooler)

1x Corsair ML120 RGB Pro Fan (bought separately)

 

I just built this rig and immediately started experiencing these same USB/iCue issues. Here are the main points:

 

  1. Commander Pro & Commander Core plugged into MoBo USB header = Commander Pro shows up in iCue, but Commander Core does not. (First Config)
  2. Commander Core plugged into USB hub on Commander Pro which is plugged into MoBo = Same result as above. (Current Config)
  3. I have all fans plugged into the Commander Pro, and all RGB leads (+ the AIO pump connector) plugged into the Commander Core.
  4. Fan profiles seem to work just fine, as does my AIO pump, but since my Commander Core is my RGB hub, I have no ability to control RGB lighting. It runs whatever "hardware lighting" scheme I had set up and saved to the profile that I x-fer'd over from my last rig.
  5. Every now and then I'll hear the USB disconnect sound and a random USB device will disconnect. Typically my XBOX One Controller which I leave plugged in via USB. The controller disconnects while in game, which is supremely frustrating.
  6. I've had the H100i AIO for a few months now, and was using it with great success on my last rig using only the Commander Core.
  7. I added the Commander Pro when I built this new rig because I was tired of the SP120 fans running at 100% all the time. The Commander Core won't control 3-pin fans like the Commander Pro will.
  8. I have not tried all of the suggestions in this thread, but will start doing so promptly. So far I've updated Windows, chipset drivers from AMD website, all other mobo drivers directly from ASUS, and video card drivers directly from nvidia.

 

I guess my question is what exactly is the conflict? My last rig (which was old as dirt, AM2+) ran iCue perfectly with zero issues. Now, on a modern, relatively popular platform, it's breaking the USB system?

 

I'm going to try deleting iCue software and unplug all of the controllers (switching to MoBo fan headers) to verify that all other USB issues go away. After that I'll try all other suggested fixes and report back what my results are, but I'm not super confident after reading thru your experiences. I don't even care that much for RGB to be honest - it was just something fun to mess with - but if it causes my USB controller to freak out, that's a deal breaker. The problem is that I really like the iCue fan control system, so I'd like for it to work so I can get my money's worth from the components I purchased.

Edited by TheOco
Link to comment
Share on other sites
Aeternus

Aeternus

Posted
Posted

Ok and after shutting down the the night (after working fine all day), I powered up this morning and it was disconnecting more than ever. This is total insanity, I'm throwing in the towel. I think I'm going to sacrifice my front USB 3.0 and just get an internal 3.0 to 2.0 adapter unplug my H1000i entirely and not connect it, and connect my Lighting Node Core directly to mobo with the adapter.

 

FWIW I dont think this is any sort of issue with my Corsair products, based off everything going on with this I'm convinced it's a driver/software issue with x570.

Link to comment
Share on other sites
TheOco

TheOco

Posted
Posted (edited)

Update:

  1. Updated to BIOS 3001 = No change
  2. Unplugged Commander Pro & Commander Core from the USB headers but kept both units plugged into SATA power and left all of the fans/AIO/RGB connectors connected.

 

Since I unplugged the Commanders from USB, I have functioning fans and the Static Hardware lighting, however there is no fan speed profile so all fans just run at about 850 rpm, with no change in speed when the CPU heats up. Looks like I'll be removing the Commander Pro completely and using MoBo headers for fan control. The Commander Core will have to stay since it's necessary for the H100i to function. At some point, I will plug the Commander Core into the USB 2.0 header by itself and see if the problem remains. I'm expecting it will.

 

FWIW I dont think this is any sort of issue with my Corsair products, based off everything going on with this I'm convinced it's a driver/software issue with x570.

 

That's kind of where I'm at with this as well. I haven't done much testing since last night, but since I did what I listed above I have yet to have my Xbox One controller (plugged in via USB to 3.2 Gen2 port) disconnect. The controller has been the biggest offender aside from the Commander Pro. However, I'm not convinced this is resolved as others have had "high-functioning" days and "low-functioning" days. Time will tell.

 

I'm considering a workaround for this situation as well, and would like some input. If I use a PCIe add-in card like THIS ONE, and use the internal 2.0 header it has on it to connect my Commander Pro, would that bypass the chipset USB controller? See, I'm not sure if the card has it's own USB controller, or if it just "piggy-backs" on the chipset in order to add more ports. If it has a proper USB 2.0 controller with its own drivers, then the problem would be circumvented, right?

 

I'm going to do some more extensive testing with this setup to make sure it works flawlessly with nothing on the internal USB 2.0 headers before I spend another dollar on this rig. If it fails, I'm not sure what options I have, since it seems to be X570 & B550 related. The only viable option would be to replace MoBo and CPU with Intel units.... total bummer.

Edited by TheOco
Link to comment
Share on other sites
Aeternus

Aeternus

Posted
Posted

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.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...