7.42 update causes iCUE fans to flash off/on every 2-4 seconds

[drednaut117]

I was searching for reasons why this symptom was occurring and landed on this thread. I have the same issue and it is HWinfo but I am using 7.46-5110

 

[JAGGED]

It wont go away, seems its more a Corsair issue best thing to do is just disable the monitoring on the AIO.

 

[drednaut117]

That solved it. Had to stop monitoring for the whole Commander. Rest of sensors work and lights are fine. Thanks

 

[stanto]

H170I elite Capellix and Commander Core XT,
icue software v5.3.102
HWiNFO64 v7.51-5165
windows 11 pro v10.0.22621 build 22621

Running HWInfo causes loss of fan control and LEDs to dim/turn off.
Latest stable hwinfo causes LEDs to flash white and loss of fan control.

I then have to quit hwinfo and restart icue.

Using the beta version stated I have to disable corsair support and then I don't have the problem.

 

[darktr3d]

For me hwinfo turnoff rgb light, not possible to keep monitoring of commander core and light on with HWinfo ?

Thanks a lot

 

[JAGGED]

I think its Corsair that need to fix it.

 

[sblantipodi]

It wont go away, seems its more a Corsair issue best thing to do is just disable the monitoring on the AIO.

how can I disable the monitoring on the AIO?
I already disable the CorsairLink and Asetek support but I still have issues with icue and hwinfo when both software are running.

 

[Martin]

Disabling "CorsairLink and Asetek support" option in main settings of HWiNFO should do it. What problems do you have?

 

[sblantipodi]

Disabling "CorsairLink and Asetek support" option in main settings of HWiNFO should do it. What problems do you have?

If iCue is running and then I run HwInfo, LEDs on my fans and on my RAMs starts behaving weirdly with small hiccups, sometimes the LEDs on the RAM stops working at all...

 

[Martin]

Then that's a different conflict on SMBus. Unfortunately Corsair is known for not playing nice with anything else and no will to fix that.

 

[sblantipodi]

I had no problems on the same system some months ago, I don't know if it was an hwinfo update or an icue update to bring this problem on my PC.

 

[JAGGED]

Just disable monitoring on hwinfo (Right click Corsair Commander CORE or what ever your Corsair device is called and disable monitoring) it was worth a shot to try to get it to work, but i guess with Corsair not playing ball its better to just disable it, once its disabled in hwinfo my rgb works fine.

 

[sblantipodi]

Just disable monitoring on hwinfo (Right click Corsair Commander CORE or what ever your Corsair device is called and disable monitoring) it was worth a shot to try to get it to work, but i guess with Corsair not playing ball its better to just disable it, once its disabled in hwinfo my rgb works fine.

once disabled the "CorsairLink and Asetek support" option in main settings of HWiNFO I see no corsair devices in the monitoring section

 

[Fr0stX76]

This wont work as the collision is most likely with the SMBus, not the Corsair service, so disabling "CorsairLink and Asetek support" option will not prevent this from happening. You will need to either disable the RAM monitoring in HWinfo or stop using iCue for the RAM.

Sadly unless Corsair implement the usage of the Global\Access_SMBUS.HTP.Method in iCue, this is what will happen. Don`t hold your breath tho since, as Martin mentionned: ``Unfortunately Corsair is known for not playing nice with anything else and no will to fix that``.

 

[archaic0]

Any chance any work is still being done on this issue? I'm running HWiNFO v8.20-5640 and the issue is still present.

I've been running the Corsair Commander Core XT for a year with no issues at all. I did a system upgrade (water cooling upgrades & new main drive) and re-installed a fresh copy of Win11 and all of a sudden all of my RGB is blinking every 2 seconds when in any moving color mode and all RGB simply turns off after 2 seconds if I pick a static color. Been fighting this for a week before I finally did the right Google search and landed here. I've only been running HWiNFO constantly to monitor my new cooling setup, so that explains why I didn't notice this for the past year. *sheesh* I thought I was going crazy!

I did the things mentioned in this thread and confirmed that the issue only occurs with HWiNFO open and I can stop it by disabling the Corsair support. Closing the iCUE software turns all RGB off, so that doesn't help. In my use case though, I use the Commander Core XT for two temp sensors that are very much a core part of my monitoring with HWiNFO. I have the system temps on the board, but I have 2 temp probes for my loop water temp and the exhaust air temp that I monitor also during stress tests. I guess I just have to live with blinking RGB while I'm monitoring things with HWiNFO unless there is some fix on the roadmap.

(The blinking is secondary to reading and graphing the temp probes for me.)

On another note, anybody know why all of my RBG goes to white when I lock my Windows desktop? Commander is set to a color fade and works great until I lock my screen and then all RGB goes white. That has happened since the beginning, but I've never dug into it. Next stop will be the Corsair forums, but thought maybe with several Commander users in this thread, maybe someone knows.

Cheers!

 

[Martin]

No way to fix this without Corsair's cooperation, but there's doesn't seem to be any interest from their side.