Tech_Greek

Most developers don't get kudos after fixing things directly (especially after the dumpster fire that was prior versions), but I wanted to take a second to say, I don't know what changed behind the scenes for a solid release, but kudos. The performance is exactly what I have expected out of Corsair since day one and so I'm happy to be able to recommend your products again. I have the ability to switch to a Windows PC and Mac Mini with my devices. If you can pull off the same feature set on MacOS with the low CPU usage as I've found in the Windows version, I would be thrilled.

I too have had this same experience for a while on both Windows and MacOS. This issue has made me give up on Corsair honestly because we are talking YEARS of issues with iCUE and I've been around since the start of it all and EVERYTHING DEPENDS ON IT. I've spent thousands of dollars of my own money on Corsair products over the years for myself and my family (if not in the same year) and that's not including the client's custom builds that I've built and highly suggested Corsair for build quality. You've got the build quality down for the most part; the hardware doesn't really have issues and has always been top notch, but there's absolutely NO reason for software to take YEARS upon years for a decent stable build that does not rack out your CPU. Signed, a friggin Systems Architect/Senior Networking & Systems Engineer who wishes Corsair would become organized enough to put out decent software.

Boot camp now, I discovered high cpu usage with Corsair.Service.CpuIDRemote64.exe (15% usage every other second). Disabled the EXE via making "EVERYONE" block on that particular file which prevents Corsair iCUE from invoking it again. (C:\Program Files (x86)\Corsair\CORSAIR iCUE Software) My iCUE Corsair.Service.CpuIDRemote64.exe High CPU usage is now gone with it. There's a simple solution here Corsair and I'm kind of confused as to why I'm the one telling you this: allow us to disable system information capture. We don't need five programs capturing our hardware status for an OSD - use the Windows Game Bar if you're that interested in OSD instead of depending on your own overlay. You're more than likely making your own software super unstable with this. K.I.S.S. METHOD is needed.

Well, I seem to be "OG" status around here with Corsair/iCUE :laughing:. Back at it, years later, high CPU usage on Big Sur. Fresh install of Big Sur on a Mac Mini. Killing the process makes the system snappier for sure but re-launching it makes it sluggish again. Where do I collect logs? Where do I send them? EDIT: Discovered that 4000 Hz polling is the equivalent of trying to ask are we there yet a million times to my Mac Mini and once I dropped it down to 1000hz it stabilized dramatically as it was micro stuttering. (It had no issues on the PC). CPU Usage is still high with iCUE regardless.

Here's my little fun rig. I hit 5.0 Ghz last night for a few hours on Aida 64 full stress test before backing it back down to 4.8 for daily, Real temp said 40-50* left before TJMAX. I'll be changing from the vengeance blue ram to the vengeance pro ram. It's quieter than your average blu-ray player, it had to be since it's my HTPC :) http://imagizer.imageshack.us/v2/640x480q90/661/11e68f.jpg http://imagizer.imageshack.us/v2/640x480q90/538/6190b3.jpg