brandonm

That's great Corsair brought back support for older coolers. I applaud them for that. Now it would be awesome if you fix sleep/shutdown/restart + ACPI event log errors that I have dealt since April 2020 Corsair update. Still have to rename all the CPUID dll's in iCue folder so that my computer will shutdown/sleep/restart without issue. Unfortunately that causes iCue to no longer communicate with my H115i cooler. Seems obvious that there is some problem with those dll's and the H115i. Is there something I can do to fix it. I have already went through technical support last year and was told this issue was supposed to be fixed in iCue 4 but it was not. I have already planned on moving to different brand on my next PC upgrade, but if Corsair can fix that, I will be content. I know no company is perfect.

Been a little while since I have been to the forums. I see Corsair officially no longer supports the H115i series coolers. I haven't even own mine for even two years and I guess "that's all folks". iCue hasn't worked properly with the H115i in my PC since early 2020, which was still version 3. Unfortunately, those really old versions of v3 that did work, now cause BSoD on W10 since around September 2020. Support lied to me and said that my issues were going to be resolved in v4, which of course they were not. Hahaha! Now they just officially end iCue support for this end many other products. This really screws me as I have other products that work fine with iCue, and I don't want to have to replace all of those just to get completely off iCue and Corsair forever. I guess it was my own stupidity for buying so much Corsair hardware in the first place, including a case, memory, SSD, keyboard, AIO. I am such a sucker, I will probably end up buying another Corsair AIO and like always, the big guy wins in the end. I suppose I could also just get rid of RGB cooling and go back to more simple CPU coolers.

I am certainly done with anything Corsair that uses iCue. Ever since an iCue update early 2020, my computer is unable to sleep/shutdown/restart properly and it constantly generates ACPI errors and warnings in the System log about some embedded controller. Also had many BSoD. The workaround is to rename the cpuid DLL files in the iCue folder, but that breaks functionality of iCue as my H115i AIO will not load into iCue, leaving it to only run with the out-of-box configuration (rainbow cycle lights). I contacted support and after going back-and-forth for probably a week, the final response was that the issue would be fixed in iCue 4. Of course it wasn't fixed so now I am left with this dysfunctional piece of hardware. I also own a Corsair case, keyboard, memory and nvme. Seems like they care very little about their reputation and customers.

Confirmed that Sleep/Restart/Shutdown problem still exists, not surprised. Back to renaming cpuid DLLs. This also confirms that I will likely not be purchasing Corsair products in the future, unless they decide to fix these issues. Very disappointing.

So tech support told me last year that I had to wait for this new iCue to fix my sleep/restart/shutdown issues and ACPI errors in the event log. Well I installed iCue 4 and already getting ACPI errors in the System event log. I wonder if my computer is going to sleep/restart properly? Will test later.

Also curious to how this is coming along. I have the shutdown/sleep/restart issue. I've been using a workaround fix (rename iCue's cpuid DLLs), but that has disabled some functionality of iCue. I was told by tech support that I have to wait for this next-gen version of iCue.

I was using an older iCue version fine up until September (maybe Windows Updates) and then came multiple daily BSoD caused by iCue. Only reason I was using the older version was because the newer versions prevent my computer for being able to shutdown/restart. I had no choice but to upgrade because of the blue screens. I was able to workaround the shutdown issues by intentionally breaking iCue services (renaming dlls). Corsair technical support basically told me to wait for the next major release of iCue as the shutdown issue will be fixed in that. I sure hope so, because iCue is no longer monitoring or controlling RGB on my H115i. Only reason I keep iCue installed is because I need it to load my RGB profile for my K70 keyboard. I also have Vengeance Pro which is no longer monitored. At least it stores the RGB config itself. I will say that iCue was working completely fine with my computer about a year ago. Don't know what happened around February/March as every version since has been nothing but agony. I spent countless hours troubleshooting until I realized that iCue was the cause of all problems. Really sucked because I have been working from home since March and needed my computer to be reliable.

My experience with Corsair products was always great up until an iCue update released this year. What a terrible time for it to happen because of work-from-home situation. Sleep and shutdown problems for a couple weeks until I found that iCue was causing it. Rolled back to earlier version and everything was fine up until September-October. Then came BSoDs about once a day. Again, no idea what the problem was for about a month until I discovered it was iCue again. This new version better fix these issues. Tech support told me that it should. For now, I have crippled Corsair services by renaming CPUID dlls. This has kept my PC stable, but RGB and monitoring on my H115i and Vengeance Pro are no longer functional. Fortunately, iCue is still able to load my K70 profile.

I have support ticket open and the tech has suggested updating to this version to see if it fixes my BSOD and Shutdown issues that I've experienced for about 7+ months. Reading this thread, sounds like not worth wasting my time on trying it out. I can't really deal with problems now that my computer has been stable since renaming all of the CPUID DLL files installed with iCue a couple weeks ago. iCue is partially broken now, but at least I don't need to worry about BSoD while in the middle of work. I really hope that this new version they are beta testing fixes everything. TBH, I will probably never purchase another Corsair product that uses iCue again if it isn't fixed. It's a shame because the hardware is great. EDIT: So I tried this latest update and it was only a matter of about one-half hour after installing and rebooting that my computer crashed. lol "Classic iCue"

I've had sleep/shutdown issues since either version 3.24.xxx or 3.25.xxx and up. This is the first I have seen this thread and glad that I am not alone. I always suspected it had something to do with the H115i Platinum AIO I have installed. The workaround I am using is renaming all of the CPUID DLL's that are in the iCue folder, followed by restarting iCue service. This breaks iCue from monitoring and managing RGB on the H115i (and I assume my Vengeance RGB memory), but my computer is able to shutdown/sleep properly. I also have a K70 mk2 keyboard and that seems to work fine with those DLL's no longer loading.

I suspect that these problems may be tied to the cpuid device that is installed with iCue and possibly recent Windows updates. iCue looks to license/use cpuid libraries for probing hardware metrics. I started getting BSoD over a month ago. In another thread that I started, @ckong suggested removing/renaming the cpuid DLL files located in the iCue folder under Program Files (x86). I did this the other day and have improved stability so far, but I want to give it about a week until I feel comfortable. There is one catch though. Since the cpuid libraries will no longer load, some services will not run in iCue, so some of your devices may no longer be managed by the software, or show up at all. My H115i is one such device.

I believe I have come across the "The specified account already exists" message in my days. It is an MSI Installer message. Unfortunately, it was so long ago that I don't remember what I had to do to deal with it. Did you try installing 3.27.68 again from the original installation file and then running the uninstall after? Maybe the MSI database/cache for that package is corrupt. Reinstalling should fix that allowing for proper uninstall.

You may have some orphaned services and drivers lingering. Open a Command Prompt as Administrator (right-click, select Run as Administrator) and run the below sc.exe delete commands to make sure all orphaned services and drivers have been removed from the Windows registry. After you do that, reboot and try deleting those files again. sc.exe delete CorsairGamingAudioService sc.exe delete CorsairGamingAudioConfig sc.exe delete CorsairVBusDriver sc.exe delete CorsairVHidDriver sc.exe delete CorsairLLAccess3B84E98236B28D4E075D5737DF9F567A1FB76E8A sc.exe delete CorsairLLAService sc.exe delete CorsairService

I think those cpuid DLL's are the problem. I renamed every *cpuid*.dll. It does stop the H115i AIO from RGB activity/monitoring, but I can live with that. And so far, it seems to have stopped the ACPI event errors and warnings. I need to test the shutdown issues, but so far, everything is looking positive. Thanks @ckong. I tried something earlier that I though fixed it, but I was wrong (deleted that reply).

Thank you. I will try this.