TonyCarter
VALUED CONTRIBUTOR
Had a read last night & this morning, and it looks like a long-standing conflict with Corsair.
The AIDA64 team say they've spent over a decade asking Corsair to stop locking their sensor readings to a single instance - which means either AIDA64 can report them to show on your screen, or iCUE can use them to control your fan/pump speeds...BUT NOT BOTH.
The AIDA64 team suggest raising a support ticket with Corsair to add to their pile...but I'm not holding out much hope and will just disable the Commander Pro integration for now to see if it helps, before turning off the H100i integration too.
The replies from Corsair reps on the Corsair forums seem to think there is no solution as 2 programs can't ask for the same data via the same CPUID SDK, so they recommend not running 3rd party hardware monitoring programs if you want to run iCUE...which is a bit of a cop out, and strange that Hardware Monitor has no effect on iCUE which I'd assume uses the same SDK.
If that's the case, I'll simply modify the sensor panel to either show more 'useless' stuff, or make the useful stuff larger...maybe a 'speedometer' for the FPS?
Something doesn't look quite right here
The AIDA64 team say they've spent over a decade asking Corsair to stop locking their sensor readings to a single instance - which means either AIDA64 can report them to show on your screen, or iCUE can use them to control your fan/pump speeds...BUT NOT BOTH.
The AIDA64 team suggest raising a support ticket with Corsair to add to their pile...but I'm not holding out much hope and will just disable the Commander Pro integration for now to see if it helps, before turning off the H100i integration too.
The replies from Corsair reps on the Corsair forums seem to think there is no solution as 2 programs can't ask for the same data via the same CPUID SDK, so they recommend not running 3rd party hardware monitoring programs if you want to run iCUE...which is a bit of a cop out, and strange that Hardware Monitor has no effect on iCUE which I'd assume uses the same SDK.
If that's the case, I'll simply modify the sensor panel to either show more 'useless' stuff, or make the useful stuff larger...maybe a 'speedometer' for the FPS?
Something doesn't look quite right here
Last edited: