AlexIvo

Unless I'm misunderstanding what you're doing, the fans and pump are behaving as expected. If you set the fans to '0 rpm' they will stay at 0 rpm regardless of any changes to the coolant temp, or CPU temp, depending on what you have the sensor set as. It sounds like you want to have a fans at low or 0 rpm when the system is idle but then ramp up during sustained CPU/GPU loads. Is that correct? In which case, you will need to set a custom fan curve. By definition, 0 rpm mode will always be at 0 rpm.

I'm also adding to this thread - v. 4.26.110 still removes all sensor details and sensor order from the Dashboard upon every reboot. I've also tried all of the multiple workarounds suggested in this thread and the behaviour persists. What is the point of this feature if it has to be repeatedly configured for multiple devices every time you start your computer?

Yep, this is a known issue that doesn't appear to have a solution yet. These are my ML120 PRO RGB fans set to white via instant lighting. The top two are connected to my H110i and the bottom one is connected to the Lighting Node Pro: https://imgur.com/3Txoqu5 There was another thread about this a few months ago too if you want to read that: https://forum.corsair.com/v3/showthread.php?t=190515 :(

This behaviour is typical of running two monitoring software at the same time, e.g. HWiNFO + iCUE. If you are indeed running HWiNFO, use the portable version of the program so there is no persistent driver installed, and go to the 'Safety' tab of the options menu upon starting HWiNFO to disable 'Corsair/Asetek' monitoring.

Yes, HWInfo is the cause. You can run it together with iCUE with no issues (I do), but you have to use the portable version (i.e. no permanent driver installed) rather than the installed version, and also check the box in the 'Safety' tab of the settings to 'Disable Corsair / Asetek Support'.

Yep, sorry, there is a different method for this. You have to select a profile, click on the dropdown 'three lines' option menu, and then 'Save to Device'. This thread may also be of use: https://forum.corsair.com/v3/showthread.php?t=185977. As far as I am aware, unless you enable full software control of RGB RAM (under the 'Settings' tab for your RAM, but this consumes a large chunk of CPU resource), you can only have one lighting profile applied to the RAM and this will not change when exiting iCUE.

Go to the tab for the specific device you want to change. Then click on 'Lighting Effects' and then "Hardware Lighting'. Do this for all of the LED-capable devices you have. Note that the available hardware lighting options are more limited than 'normal' lighting effects.

This isn't a problem, it is how it is designed. You need to set a 'hardware' lighting profile to all of the devices in your system with LEDs that will run when the computer is booting, or any other time when iCUE/Corsair service is not running. Set the lighting mode to something other than rainbow spiral, which is the default.

Hi mate, So I had never noticed that issue until you pointed it out. If I set all the fans in my case to 'white' via iCUE Instant Lighting, I get this... https://i.imgur.com/3Txoqu5.jpg The two at the top are ML120 RGB Pro fans connected to my H100i Platinum CPU block headers, and the bottom one is another identical ML120 RGB Pro fan connected to a Commander Pro and RGB Fan hub. There is a clear difference in colour hue, especially with white and light blue as you also demonstrate in your video. Swapping the fans around between the H100i block and the RGB fan hub definitely changes the hue, depending on what they're controlled by, so I'm also sure it's not a fan LED issue. So I just wanted to confirm that you're not alone! No fixes as far as I am aware though...

Are you running any other monitoring software? This behaviour is usually seen when programs like HWiNFO are run at the same time as iCUE. With HWiNFO, there is a checkbox for 'Corsair and Asetek' that should be disabled if you want to run them in tandem.

Hi all, I have a total of six ML120 Pro RGB fans in my build - two attached to the H100i cpu block fan header, and four as case fans controlled by a Commander Pro + RGB Fan Hub. If I make a 100% fan curve in the 'Performance' tab of the H100i device and apply it to these two ML120 Pro fans, their maximum RPM reads ~1700 in iCUE. If I apply a 100% fan curve to the four case fans via the Commander Pro, two of the fans read a maximum RPM also ~1700, and the other two show a maximum RPM ~2400. Any chance the tachometer reading for these 'faster' fans is incorrect? They do appear to be spinning faster, with noticeably more air movement and increased noise. If not, why do all six fans not have the same maximum RPM, within the slight error of the tachometer reading? A discrepancy of ~700 RPM suggests something other than software/tachometer misreporting? Cheers. EDIT: So the ML PRO RGB Fans that come with the H100i Platinum apparently aren't the same as the ML PRO RGB Fans that you can buy separately. In my infinite wisdom I mixed the fans up and mounted the H100i fans as 'case fans', and two 'case fans' as radiator fans. The 2400 rpm fans should be on the radiator. It might be useful if it specified somewhere when you purchase the fans separately that they're NOT identical to the ones that share their name and ship with Platinum-series coolers...

I personally use HWiNFO as it reports data from pretty much every available sensor in every component in your PC. However, having multiple different software attempt to access Corsair devices simultaneously (i.e. iCUE and HWiNFO) causes conflicts, so if you decide to use HWiNFO there is an option under the 'Safety' tab in the Settings to disable Corsair/Asetek monitoring that should prevent these conflicts.

iCUE has still not been updated to show Ryzen 3000-series CPU temperatures. There are lots of other people waiting for this functionality - don't hold your breath!

Hi Citizen Crazed, Well, firstly, thank you for confirming that it isn't just me experiencing the same issues, and that my PSU isn't about to just disintegrate... What is also interesting is that if I enable HWInfo monitoring of my AX860i sensors (although it complains about dual monitoring programs), it also reports the same nonsensical temperature and efficiency values. However, if I uninstall iCUE, and go back to LINK, HWInfo is also then able to report the correct sensor numbers again. It's as though iCUE is actually altering the way the AX860i reports its status to the mobo, rather than just 'reading' the wrong values... Hopefully there is a fix for this soon!

I recently installed iCUE having been using LINK since I built my computer in 2015. I had previously had no issues with LINK correctly reporting the various statuses of my AX860i PSU e.g. temperature, fan speed, efficiency. However, having been using iCUE for 3 days now, whilst it seems to have the correct values for the rest of my system i.e. motherboard, RAM, cpu, the sensor values for the AX860i are completely nonsensical. Screenshot here: https://i.imgur.com/4hVikg9.png The temperature value reads -196 Celsius, and the power in/out values fluctuate wildly between 70% and >100%. I would be surprised if this erratic behaviour is symptomatic of a failing PSU, and I don't think it's a coincidence that this behaviour started the day I installed iCUE, when LINK never had this issue. I'm not running any other monitoring programs either. Does anyone have any advice? Cheers.