My H115i Elite Capellix and my other two ML140 RGB fans connected to the commander core included with cooler are not spinning immediately upon turning on my PC.

[Polus6]

Hello everyone. After updating to Windows 11 and rebooting my system, the two fans included with the H115i Elite Capellix and two additional ML140 fans automatically turn white and they don't spin for about three seconds. My ASUS X670E-A motherboard then makes a beep, I get an error that I can't replicate and therefore, I don't what it says, and the time it takes to boot is longer. From what I read on other forums, this could be a defect with the cooler itself, the commander core, or both. From what I can tell, my CPU temps are fine. Does anybody know how to solve this issue?

[Polus6]

55 minutes ago, Polus6 said:

Hello everyone. After updating to Windows 11 and rebooting my system, the two fans included with the H115i Elite Capellix and two additional ML140 fans automatically turn white and they don't spin for about three seconds. My ASUS X670E-A motherboard then makes a beep, I get an error that I can't replicate and therefore, I don't what it says, and the time it takes to boot is longer. From what I read on other forums, this could be a defect with the cooler itself, the commander core, or both. From what I can tell, my CPU temps are fine. Does anybody know how to solve this issue?

Ok. I somewhat remember what the error message is BIOS said. It something about the cpu_fan and pump not being connected. I confirmed on the instructions for the H115i Elite Capellix that the pump tachometer is supposed to plug into the cpu_fan and from what I can tell, I don't have to plug any connector into the pump header. I don't know if this will help, but I have a 7800X3D and this exact model of RAM: F5-6000J3038F16GX2-TZ5NR with EXPO enabled. I am on BIOS version 1004. 

[c-attack]

If you get a momentary CPU boot error, that’s the motherboard and AIO not communicating in the initial first second. Neither anything with Windows or CUE should affect that since they’re not running yet. Is this a new motherboard or did you just do a BIOS update?  That’s usually when this type of thing will occur. If it’s persistent, you can go into the bios and disable the “CPU boot error protection”. Asus tends to make this obscure and hard to find. Go to the Advanced BIOS (F7) -> monitor column. Scroll down to the cpu fan speed (rpm) line. Hit enter and a box with “ignore” will pop up. Select it and save/exit. There are plenty of other ways the system will let you know if the pump doesn’t start, including a building roar from the fans.
 

If you’ve just done a Win 10->Win 11 update, do yourself a favor and go to the Windows Settings-> Apps and find Corsair iCUE. On the drop down menu select “modify”. Follow the prompts for a repair install. This will not erase profiles or settings and if you’re lucky will clean up any twisted mess of drivers caused by the update process. 

[Polus6]

I just installed the CPU yesterday after not using the motherboard. The motherboard is brand new never-been-used before. The only time I used the board was to update the BIOS via BIOS flashback before the CPU arrived. Also, the fans don't spin initially and the building roar you mentioned happens after about five seconds of not spinning. They will immediately spin to maximum RPM and then slow down after Windows is booted. I will follow your advice and come back afterwards. Thank you in advance. 

[Polus6]

8 hours ago, c-attack said:

If you get a momentary CPU boot error, that’s the motherboard and AIO not communicating in the initial first second. Neither anything with Windows or CUE should affect that since they’re not running yet. Is this a new motherboard or did you just do a BIOS update?  That’s usually when this type of thing will occur. If it’s persistent, you can go into the bios and disable the “CPU boot error protection”. Asus tends to make this obscure and hard to find. Go to the Advanced BIOS (F7) -> monitor column. Scroll down to the cpu fan speed (rpm) line. Hit enter and a box with “ignore” will pop up. Select it and save/exit. There are plenty of other ways the system will let you know if the pump doesn’t start, including a building roar from the fans.
 

If you’ve just done a Win 10->Win 11 update, do yourself a favor and go to the Windows Settings-> Apps and find Corsair iCUE. On the drop down menu select “modify”. Follow the prompts for a repair install. This will not erase profiles or settings and if you’re lucky will clean up any twisted mess of drivers caused by the update process. 

Could this be a sign of pump failure or a faulty water cooling unit or just some ASUS motherboard spaghetti code? From what I've heard, a lot of people have been having issues with ASUS motherboards especially regarding the 7000X3D platform. 

[c-attack]

I think it’s probably more basic. When the Commander Core first gets power, it does a fan check to see which headers are populated. That should be something like a one second blip of power. What you’re describing makes me think the PSU is not delivering power down the SATA line to the Com Core and pump. This triggers the cpu boot error because the pump can’t talk back without power, then the fans over-rev because the small amount of liquid in the cooling channels was trapped their got a moment causing a perceived liquid temp spike, which then makes the fans react strongly. The fans should start spinning the moment you touch the power button. 
 

Could there be something wrong with the Commander Core?  Yes, it’s possible. However, I would first try a different SATA connection from the PSU. If you are sharing a line with a couple of HDDs, get it off there. Either way, a different physical SATA cable from a different socket should rule this out. The motherboard itself can’t interfere with this and that controller should still work if you power on with the 24 pin jumper in place and the motherboard disabled. 

[Polus6]

4 hours ago, c-attack said:

I think it’s probably more basic. When the Commander Core first gets power, it does a fan check to see which headers are populated. That should be something like a one second blip of power. What you’re describing makes me think the PSU is not delivering power down the SATA line to the Com Core and pump. This triggers the cpu boot error because the pump can’t talk back without power, then the fans over-rev because the small amount of liquid in the cooling channels was trapped their got a moment causing a perceived liquid temp spike, which then makes the fans react strongly. The fans should start spinning the moment you touch the power button. 
 

Could there be something wrong with the Commander Core?  Yes, it’s possible. However, I would first try a different SATA connection from the PSU. If you are sharing a line with a couple of HDDs, get it off there. Either way, a different physical SATA cable from a different socket should rule this out. The motherboard itself can’t interfere with this and that controller should still work if you power on with the 24 pin jumper in place and the motherboard disabled. 

I had already connected the Commander Core to it's own SATA cable from the beginning. I only have two SATA connections in my build, each with their own cable plugged in to the first connection including the commander core.

[Polus6]

I'm starting think there is a problem with the commander core. I swapped the position the SATA power cable was plugged into and I still have the same problem. Not only that, but I also followed your advice on repairing the iCUE software and now I can't even control the lights on it or change fan speeds. When I use auto detect, none of the fans are detected despite them being turned on and connected to the commander core. I decided to ultimately uninstall iCUE and reinstalled it and now it seems to be working. I restarted my computer and my fans still do not spin immediately. However, I did get the error message again. 

[c-attack]

13 hours ago, Polus6 said:

I'm starting think there is a problem with the commander core.

It seems like it.  So you can seek a replacement through Corsair by starting a support ticket from the link at the bottom of the page that takes you back to the proper Corsair.com site.  Going this route may allow you to keep the AIO in place, but swap in a new Commander Core they ship you.  They will ask about the SATA power, so this was a necessary step ahead of time if you go this route.  

 

The other options is to swap the whole thing for another through your purchase retailer.  This may be faster depending on the vendor.