HWiNFO and Corsair Commander Pro.

[Kol12]

Have just installed a Corsair Commander Pro. It seems that if HWiNFO monitors the C-Pro it makes it go haywire, fans start ramping, incorrect values and fans disappearing from Corsair iCUE software panel. So I disabled monitoring of C-Pro in HWiNFO but it appears there is still some conflict with the iCUE software, not as haywire as previously but fans still disappearing from iCUE and 0RPM fan readings. Is there any solution to this?

 

[AlexIvo]

You need to entirely disable 'Corsair and Asetek Support' in the "Safety" table of the HWInfo settings. Just disabling monitoring of specific devices doesn't always prevent conflicts.

 

[Kol12]

You need to entirely disable 'Corsair and Asetek Support' in the "Safety" table of the HWInfo settings. Just disabling monitoring of specific devices doesn't always prevent conflicts.

I see it, thanks for the heads up. Is that a relatively new addition to HWiNFO's safety features?

 

[AlexIvo]

You need to entirely disable 'Corsair and Asetek Support' in the "Safety" table of the HWInfo settings. Just disabling monitoring of specific devices doesn't always prevent conflicts.

I see it, thanks for the heads up. Is that a relatively new addition to HWiNFO's safety features?

No worries. It's been implemented for a while, but it comes up pretty often on the Corsair forums where people can't pinpoint the issue with bizarre iCUE readings.
I'm also running a CoPro and several other Corsair devices with HWInfo, and don't have any issues once I disable that option 

 

[Martin]

This is a known collision between iCUE and any other program monitoring Corsair devices and has been discussed dozens of times on this forum too.
You should be also getting a warning about this in HWiNFO when it detects the Corsair device.

 

[Kol12]

This is a known collision between iCUE and any other program monitoring Corsair devices and has been discussed dozens of times on this forum too.
You should be also getting a warning about this in HWiNFO when it detects the Corsair device.

I got no warning after installing the C-Pro today. Maybe it's because I ran sensors only?

 

[Martin]

Maybe you got that warning earlier and dismissed it?

 

[Kol12]

Maybe you got that warning earlier and dismissed it?

I don't know, it's history now though I guess. So can you clarify is it impossible to monitor anything from the Corsair Commander Pro in HWiNFO? It would be nice to get some of the C-Pro stuff into the RTSS OSD via HWiNFO but it seems like that device and HWiNFO really don't get on too well together...

 

[Martin]

It is possible, but you must avoid running the Corsair iCUE software in parallel with HWiNFO.

 

[Arctucas]

If I use the Commander Pro only for monitoring temperature probes such as the XSPC http://www.xs-pc.com/temperature-sensors/g14-inline-10k-sensor-black-chrome and http://www.xs-pc.com/temperature-sensors/flat-sensor-10k, I should only use HWiNFO and not install the Corsair software?

 

[Martin]

Yes, I don't recommend running any other monitoring tool along with Corsair software.

 

[Arctucas]

And HWiNFO fully supports the Commander Pro?

 

[Martin]

Yes, it should.

 

[Sergred]

Good day. Why do conflicts continue even if the HWiNFO is closed? And how to eliminate it, if possible?
In the process of debugging fan modes, both software are still required. And so you have to restart the computer, which is very inconvenient.
By the way, the same thing happens if you close the Corsair and run the HWiNFO.

 

[Martin]

There should be no conflicts when you close HWiNFO unless you have some other applications running that might be accessing the Corsair device.

 

[Sergred]

There should be no conflicts when you close HWiNFO unless you have some other applications running that might be accessing the Corsair device.

Thanks, I will search.