F5F Stay Refreshed Hardware Desktop iCUE no longer displays CPU, GPU, or drive temperatures.

iCUE no longer displays CPU, GPU, or drive temperatures.

iCUE no longer displays CPU, GPU, or drive temperatures.

V
Voraah
Junior Member
6
01-21-2023, 06:35 AM
#1
I first noticed around two months ago that the iCUE dashboard no longer displayed any of my equipment temperatures except for the H115i AIO, RAM, and PSU temps—all Corsair products. At the time, I didn’t give it much thought. However, during recent stress tests, my CPU reached over 100°C and the fans didn’t increase. During a Prime95 test, the CPU hit 115°C and the PC shut down because of thermal protection. I checked the fan settings and attempted to set a new curve, but there was no option for CPU temperature. It seems my fans have been running at idle without controlling CPU temps. I searched online for fixes and found others reporting success by opening a specific service file, but my attempts only resulted in errors. Corsair mentioned problems with iCUE 3 and an expired certificate, which they said were fixed in iCUE 4, though that doesn’t seem to apply to my setup.
V
Voraah
01-21-2023, 06:35 AM #1

I first noticed around two months ago that the iCUE dashboard no longer displayed any of my equipment temperatures except for the H115i AIO, RAM, and PSU temps—all Corsair products. At the time, I didn’t give it much thought. However, during recent stress tests, my CPU reached over 100°C and the fans didn’t increase. During a Prime95 test, the CPU hit 115°C and the PC shut down because of thermal protection. I checked the fan settings and attempted to set a new curve, but there was no option for CPU temperature. It seems my fans have been running at idle without controlling CPU temps. I searched online for fixes and found others reporting success by opening a specific service file, but my attempts only resulted in errors. Corsair mentioned problems with iCUE 3 and an expired certificate, which they said were fixed in iCUE 4, though that doesn’t seem to apply to my setup.

H
Hr_Valdemar
Junior Member
42
01-21-2023, 07:16 AM
#2
Hi @MISTERDIEABETIC , I don't know if you have solved this problem in the meantime but if you have not, here is a fix that worked for me: Go into "C:\Program Files\Corsair\CORSAIR iCUE 4 Software" and rename "Corsair.Service.CpuIdRemote64.exe" to e.g. "Corsair.Service.CpuIdRemote64(renamed).exe". Then rename "Corsair.Service.CpuIdRemote.exe" to "Corsair.Service.CpuIdRemote64.exe". The next time you start your system it should work. I tried creating a task that would launch "Corsair.Service.CpuIdRemote.exe" but this did not work reliably. The above method works almost 100% reliably for me. I guess that the 64bit version of the file/service tries to access a restricted memory section and therefore is stopped from executing. The 32 bit version does not seem to have that problem.
H
Hr_Valdemar
01-21-2023, 07:16 AM #2

Hi @MISTERDIEABETIC , I don't know if you have solved this problem in the meantime but if you have not, here is a fix that worked for me: Go into "C:\Program Files\Corsair\CORSAIR iCUE 4 Software" and rename "Corsair.Service.CpuIdRemote64.exe" to e.g. "Corsair.Service.CpuIdRemote64(renamed).exe". Then rename "Corsair.Service.CpuIdRemote.exe" to "Corsair.Service.CpuIdRemote64.exe". The next time you start your system it should work. I tried creating a task that would launch "Corsair.Service.CpuIdRemote.exe" but this did not work reliably. The above method works almost 100% reliably for me. I guess that the 64bit version of the file/service tries to access a restricted memory section and therefore is stopped from executing. The 32 bit version does not seem to have that problem.