caveman19

It appears as though this service isn't strictly required for operation however. Would be nice to see a toggle to put icue into "lite" mode where all this ancillary stuff can be disabled/forgotten about or have someone bake in some logic that just stops it from trying to start itself after a few crashes.

The crash was not present until I installed the Intel Arc A770 16G GPU. Only began recently as I only installed the GPU somewhat recently so I cannot say if this happened on earlier builds or not but I suspect it probably would if that section of the app code hasn't changed at all. iCue still runs "fine". However, I get the Corsair.Service.CpuIdRemote64.exe to crash about once every 2 seconds or so. It really makes a mess out of the system logs to be honest. You wouldn't notice this issue unless you looked in task manager and saw it start and stop constantly, or if you checked the system logs and/or the reliability report and noticed that this happens an incredible amount. Just today alone, this service has crashed out 3,130 times and I can't find a way to make it stop other than uninstalling iCue which isn't ideal as that's how my fans are controlled..

@Corsair Nick Want to get this dealt with in the next update if possible. I've had to uninstall iCue due to this and it would be really nice to get control of my fans again.

removed

Corsair iCUE service is crashing with Intel Arc GPU's. Please Fix.

I get the following *constant crashing* when using an Intel Arc A770 16G. This is crapping all over the system logs. Please fix. Source Corsair.Service.CpuIdRemote Summary Stopped working Date ‎11/‎22/‎2022 11:36 AM Status Report sent Description Faulting Application Path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\Corsair.Service.CpuIdRemote64.exe Problem signature Problem Event Name: APPCRASH Application Name: Corsair.Service.CpuIdRemote64.exe Application Version: 4.30.0.1 Application Timestamp: 6311d9a5 Fault Module Name: ze_intel_gpu64.dll Fault Module Version: 1.3.24375.0 Fault Module Timestamp: 6373247d Exception Code: c0000005 Exception Offset: 000000000011da95 OS Version: 10.0.22621.2.0.0.256.161 Locale ID: 1033 Additional Information 1: 0949 Additional Information 2: 09495a09419f80e36ab02442d9b46e23 Additional Information 3: 47df Additional Information 4: 47df64cbbf444a5d7e6b95cdd8c331ca Extra information about the problem Bucket ID: b7f5803642ed16863f83a7afd457cbcc (2270843010748500940)

Some of this could potentially be attributed to the "enforce all limits" that we re-enabled in your bios. Basically, the Alder Lake chip by default wants something like 241 watts in it's PL1 (power limit 1), and then it can sustain that power for X number of seconds (generally 56 or so stock) and then reduces total package power to the PL2 which is probably something like 220 watts but I'm not actually sure for this chip. To get around this without fully removing the PL1 target is to set your PL1 equal to your PL2 and to maintain the same thermals you've been seeing so far I would set both of these to 241 watts. This will cause the turbo boost power time window (that 56 seconds I mentioned) to effectively do nothing. For my situation, room, ambient temperature, cooler setup, etc. I've set this value to 288 watts for both PL1 and PL2 but your mileage *will* vary. If you set this too high, certain loads like what can be produced with P95 can trigger over-current protection on many motherboards and/or power supplies. For me, that was right around 310 watts but sustaining that for long periods of time on anything short of LN2 would be ill-advised. For most CLC setups, power targets over 260 watts or so would be overkill as most benchmarks don't go over 240 watts or so unless you've gone overclocking with more than ~1.35v vcore under extreme load. I also would not advise pushing more than 1.375v on a CLC with this CPU as that's just a lot of watts to dissipate and CLC's just are not setup for that.

I haven't had this issue in stereo mode, however, if all of your Corsair products are compatible with the legacy version of icue you could try using that instead and see if the sound issue persists over there. Head over to https://www.corsair.com/us/en/downloads and grab the Leagy Devices version. As of this writing this is the current version to look for: CORSAIR iCUE v3.38.61 (For Legacy Devices)

Make sure you have the headset in stereo mode. It’s near the EQ settings. The fake surround is awful.

I will note that even with this setting in place I still get ~90C temps and the occasional 100C throttling blip during Small FFT runs etc. With the load settings enforced in the BIOS I also see Current/EDP Limit Throttling as well but my Cinebench scores haven't been reduced by more than 1% or so because of this. P95 AVX and the Alder Lake CPU can generate some serious load/heat, and if the TDP limits are removed, it can trip the overcurrent protection on many boards without an OC at all. My average gaming temps are are in the 50's hitting highs of 65ish and lows in the 40's. My idle and ambient temps are otherwise similar to yours. I have re-applied paste to the cooler several times as I swap the CPU into various motherboards to test OC-ability but hey. Paste I used was Arctic Silver MX-4 but I doubt the paste made much of a difference. I did not delid the CPU, but I suspect that there would be gains to be made on Alder Lake here. @c-attack It must be said that not all motherboards come with this setting enabled/disabled the same. "Auto" settings for some brands remove the TDP limits (Asus is one). Some enforce them by default (like MSI). I got lucky with my first attempt being with MSI, but swapping the chip over to an Asus I was trying to figure out why this would crash way longer than I care to admit yesterday. Not all defaults are created equal.

Asus has a setting in the bios for their "all core optimizer" or something that is enabled by default. Set this to instead "enforce all limits" and try again. It should be under the AI Tweaker menu. This setting removes (or puts in place if set to disabled like it should be) some of the built-in intel TDP limits that would otherwise keep your P95 temps in-check. I was just fighting this with my 12900k as well. Let me know if this helps.

What we want is to be able to bypass the need for iCue (as it related to RGB) all together. Put ARGB input into the corsair system and allow it to be synced to a different controller. This would allow for the ultimate flexibility. This way, you don't have to support n# of devices within iCue that are not Corsair's own but you also open up your RGB devices to a much wider audience that want their devices to be controlled externally in whatever product they see fit for their setup. A perfect example of this working well is on PowerColor "Red Devil" Radeon cards. They have an ARGB header on them and when you set "sync with motherboard signal" in their software, it just takes whatever comes down the cable you plug into the ARGB input for that device. The Corsair fan controllers could implement similar input mechanisms and then just have an "external sync" option in the iCue hardware lighting.

Adding into this a bit: Having an iCue/Fan Controller that could have it's own onboard memory and profiles which was loaded through the internal USB header but powered from the PSU directly would get us away from having to mess around with all these settings in different places within iCue. I just want to be able to set scenes, automate it, and forget about it. You can only partially get to this today but you can't have hardware lighting synced between devices and that's a real bummer. This isn't a limitation with motherboard ARGB, and is a reason to have an ARGB input to allow for optional external control of the corsair lighting. Additionally, having an ARGB input on the controller with a setting to allow for external control of the addressable devices would bring so many more people over who avoid iCue for the perceived vendor-lock it holds at the moment. iCue could be so much more with just a few extra considerations.

The limitation to being able to only control devices while unlocked is really holding iCue back. I've largely stopped using Corsair devices like the ST100 Headphone Stand because it just pukes rainbows when I lock my PC. For devices that have no onboard memory, there should at least be optional dark mode firmware to make this the default setting for when plugged into devices where iCue is not running or the user wants a device without hardware profiles to just be lights-off/no-puke.

H100i Elite Capellix owner reporting in. This thing is UNBEARABLE! In quiet mode it hums away at ~425hz. This frequency note is just about an A4 on a keyboard, yes, the one in the middle. And at 40dB I must add (with pump only no fans running at all). Marketing says 20dB 🤣 This thing is literally 4x louder than that. I also picked up some ML120 Pro fans and they're so much quieter than the ones which were pre-installed on the unit which were also supposed to be exactly the same. The pre-installed fans also have audible motor/humming noise coming from them.. insane! Oh, and they also rotate at different speeds than the other ML120's given the same % duty cycle... not sure how they can be the same if they are in-fact, not the same... Really feeling duped on this purchase. Never had issues with my old H100i from ~2013 era in quiet. Sure, it could be loud on extreme settings but extreme on that was about the same as quiet on this new Capellix unit. This is a completely different animal. Going to need an update, a replacement, or just a different unit entirely as this is so not ok given the marketing claims.