r/iCUE

Hi, I don't quite know where to ask for advice. I have a relatively large/complex setup of iCue components. Mouse, keyboard, 10 fans, water pumps, water blocks, headset, mousepad. Maybe I forgot something else. I also have an Asus motherboard and a new gigabyte Aorus RX 9070xt. Unfortunately, with all the well-known solutions such as SignalRgb, openrgb, artemis rgb, I have not had a chance to control all the devices. Most of the time just one or two devices where not compatible with the chosen software. In addition, I would like to continue using icue, as I want to control all the functions away from the lighting. Does anyone have any idea what else I could try or do I have to put up with the fact that I have to run iCue, armoury crate and fusionrgb at the same time. I hope this is somewhat understandable and thank you in advance.

Everything was working 100% before the update. After i installed the new version, V 5.44.55. My Vengeance RGB Pro ram sticks aren't responding to any lighting profiles or changes. They just stuck in the default rainbow mode. All my other Corsair devices are working 100%, and the app does detect my ram. I also force updated the firmware of the ram sticks, but nothing works.

I have been fighting a very strange iCUE issue for days, and I am trying to determine what is actually happening and how to fix it. This setup worked perfectly for months until relatively recent iCUE and firmware updates.

My setup:

• Gigabyte Z890 AORUS motherboard
• Corsair iCUE LINK ecosystem
• Corsair AIO
• Corsair RAM
• Corsair fans connected through the iCUE LINK hub
• Windows 11

Symptoms:

• Sensors randomly stop updating after some uptime
• CorsairCpuIdService sometimes gets stuck in the "Starting" state indefinitely
• Rebooting temporarily fixes the issue
• The issue appears isolated to the Corsair software stack
• Replacing the iCUE LINK hub did NOT solve the problem

Tests already performed:

• Full uninstall and reinstall of iCUE
• Multiple reboots
• Swapped the iCUE LINK hub with another unit
• Changed internal USB headers
• Disconnected the LINK hub USB connection entirely
• Verified sensor functionality

I have found posts from people reporting sensor related issues for nearly 10 years. Frankly, it is difficult to believe that something as basic as reading hardware temperatures still suffers from these kinds of problems after such a long time.

I spent more than 5,000 euros building a PC around your ecosystem, and regardless of whether I eventually fix this problem or end up throwing this PC out the window, I can assure you that this will be the last Corsair product I ever purchase.

I will also share this experience publicly and strongly discourage anyone I speak to about PC hardware from buying Corsair products.

Now, Corsair, I am waiting for your reply and your explanation as to why, after more than a decade, your software is still suffering from what appear to be extremely fundamental engineering issues. And please do not try to gaslight me. I am an embedded software engineer, and there is nothing particularly complex about reading hardware sensors reliably.