[Fix] High CPU Usage of iCue 3.3.103!

[k155]

I am experiencing around 35% CPU usage with iCUE in idle and around 40% with it in the foreground. I tried the troubleshooting suggested in this thread to no avail, and at this point I think I should just do a system restore to bring back the prior version of iCUE.

I could understand CPU usage as high as 10% while Corsair works on optimizations, but 35-40% is nowhere near acceptable.

[mostwantedzero]

It turns out in my case h100i v2 profile was causing the high cpu usage.

[k155]

Originally Posted by mostwantedzero

It turns out in my case h100i v2 profile was causing the high cpu usage.

I have the same same AIO as you. What settings did you change to fix the issue?

[mostwantedzero]

Originally Posted by k155

I have the same same AIO as you. What settings did you change to fix the issue?

I removed the profile "profile_h100iv2.xml" inside:

C:\Program Files (x86)\Corsair\Corsair Utility Engine\devices

Make sure you back the file up since taking removing it from that folder, It won't show up on iCue which means you can't change/view it's settings.

When i did place the profile back to the folder iCue CPU usage raised to 15%

Try it at your own risk

[solarity]

Originally Posted by k155

I have the same same AIO as you. What settings did you change to fix the issue?

Originally Posted by mostwantedzero

I removed the profile "profile_h100iv2.xml" inside:

C:\Program Files (x86)\Corsair\Corsair Utility Engine\devices

Make sure you back the file up since taking removing it from that folder, It won't show up on iCue which means you can't change/view it's settings.

When i did place the profile back to the folder iCue CPU usage raised to 15%

Try it at your own risk

Please note I am frequently updating the orginal post, I have almost re-written it 4 times in the past 16 hours. Did you try disabling the the lighting effects for the AIO cooler? As recommended by DevBiker

[DevBiker]

Keep in mind that removing that profile file will disable support for the H100i V2 in iCue. Use at your own risk.

And Corsair is aware of this issue and they have been working on it.

[solarity]

Originally Posted by DevBiker

Keep in mind that removing that profile file will disable support for the H100i V2 in iCue. Use at your own risk.

And Corsair is aware of this issue and they have been working on it.

I am one or two people away from redacting the "removing XML profile" solution. I just want to hear from a couple more people that removing the lighting effects on their devices works.

[DevBiker]

You cannot disable the lighting effects on the H100i V2. It's static. Event setting it to 0,0,0 doesn't resolve the issue.

Minimizing the iCue window dropped usage from ~13-15% to ~9-10% on my H100i V2 system. It's not ideal but moderately better.

[solarity]

Originally Posted by DevBiker

You cannot disable the lighting effects on the H100i V2. It's static. Event setting it to 0,0,0 doesn't resolve the issue.

So the only way to fix the CPU issue, is to move the XML profile to a backed up location?

[DevBiker]

Originally Posted by solarity

So the only way to fix the CPU issue, is to move the XML profile to a backed up location?

It appears so. But, again, that completely disables support for the cooler.

[solarity]

Originally Posted by DevBiker

It appears so. But, again, that completely disables support for the cooler.

Just for iCue?

It's primary function as a cooler still works? What feature set is missing?

Also did you say only the V2 is effected and other iCUE compatible AIOs are not effected?

Lastly does the LEDs go to the default or last color specified if the XML is removed?

[k155]

Originally Posted by solarity

Please note I am frequently updating the orginal post, I have almost re-written it 4 times in the past 16 hours. Did you try disabling the the lighting effects for the AIO cooler? As recommended by DevBiker

Thanks for your hard work on this.

Can you clarify what exactly you mean by disabling lighting effects on my AIO? There's no trashcan icon next to it like my other corsair devices (K95, MM880 pad, VOID pro, Lightning node pro with strips and HD120 fans, ST100). All I can do is set all 3 RGB values to 0, but that seems to have no effect.

If you don't recommend XML solution, then what else can I do while waiting for Corsair to roll out the fix? I could just keep the application closed, but then I lose my VOID pro and keyboard macros.

[DevBiker]

Originally Posted by solarity

Just for iCue?

Yup. And with iCue installed, Link won't touch the cooler.

Originally Posted by solarity

It's primary function as a cooler still works? What feature set is missing?

It does. But you won't have monitoring and, if your fan curves aren't based on the coolant temperature (as they should be), your custom fan curves won't run. And if you've not saved the profile to the cooler explicitly, it'll run in default mode. While this will likely work OK for some folks, it may not be ideal.

Originally Posted by solarity

Also did you say only the V2 is effected and other iCUE compatible AIOs are not effected?

Primarily, from what I've seen, that particular family of coolers is the most affected. My H115i PRO system doesn't have CPU utilization quite as high but still higher than I'd like - and higher than previous versions of iCue.

Originally Posted by solarity

Lastly does the LEDs go to the default or last color specified if the XML is removed?

Depends on what's saved to the cooler's memory.

[solarity]

Originally Posted by k155

Thanks for your hard work on this.

Can you clarify what exactly you mean by disabling lighting effects on my AIO? There's no trashcan icon next to it like my other corsair devices (K95, MM880 pad, VOID pro, Lightning node pro with strips and HD120 fans, ST100). All I can do is set all 3 RGB values to 0, but that seems to have no effect.

If you don't recommend XML solution, then what else can I do while waiting for Corsair to roll out the fix? I could just keep the application closed, but then I lose my VOID pro and keyboard macros.

No problem, I am glad to help.

I am still working on this and as I don't have an AIO, I haven't really looked into the settings. Though DevBiker informed me it is different than most other devices. The only CPU fix for the V2 at least is to move the XML to a backed up location. If you can live with the extra tax on your CPU you can also leave it as is, it is your call. I didn't want to recommend the moving of the XML as I thought that disable lighting effects was the best practice. As that is impossible for your AIO, moving the XML file is the only solution I have at this point. I will still work to see if I can find another solution, though I am at work right now. I am an end user like you, so I am learning as we go. I will update my front page...again. :)

Originally Posted by DevBiker

Yup. And with iCue installed, Link won't touch the cooler.



It does. But you won't have monitoring and, if your fan curves aren't based on the coolant temperature (as they should be), your custom fan curves won't run. And if you've not saved the profile to the cooler explicitly, it'll run in default mode. While this will likely work OK for some folks, it may not be ideal.

Primarily, from what I've seen, that particular family of coolers is the most affected. My H115i PRO system doesn't have CPU utilization quite as high but still higher than I'd like - and higher than previous versions of iCue.

Depends on what's saved to the cooler's memory.

So if people are fine living with some increased usage then they do nothing, if they want to reduce CPU usage, they will have to remove the XML file.

[vMax65]

Hi all, I have been reading this thread as I seem to have the same problem as I have a Corsair K65 keyboard, M65 Mouse and the H150i pro AIO so it was causing me a lot of problems as everything worked fine until I put iCue on.

For me I was getting 10 to 12% CPU usage in idle and after much playing around with icue, it turned out to be my Corsair Vengeance LED DDR4 3000 memory. This is the LED version red...not RGB!

After taking of the lighting profile from the RAM, the CPU usage went back to normal. If I put a lighting profile on the memory the CPU usage goes straight upto 10 to 12% again. I now am living with no lighting for the RAM and hope the next version sorts it out.

Hope this helps...