TGTZENG Posted April 21, 2019 Share Posted April 21, 2019 (edited) So I been dealing with this problem for a long time now and it seems like searching through Google there is nobody at Corsair or on the internet that seems to know how to fix this. Everytime I shutdown my computer I get this error https://imgur.com/YkqL0rZ that prevents me from shutting down and it shows it is iCUE related. Why is this happening and does anybody out there know how to fix this? Please help because this issue has been plaguing me forever now and I've seen couple other threads with this issue but no answer for a fix. Edited April 21, 2019 by TGTZENG Link to comment Share on other sites More sharing options...
Corsair Employees Corsair Calico Jack Posted April 22, 2019 Corsair Employees Share Posted April 22, 2019 Hi! Can we get your system specs and a list of your startup software? What have you tried so far as correcting the error? Link to comment Share on other sites More sharing options...
klatoo Posted April 23, 2019 Share Posted April 23, 2019 I get the same thing http://forum.corsair.com/forums/showthread.php?t=185522 I have uninstalled and reinstalled, installed older version of iCUE (3.9.93, 3.10.125, 3.12.118) and for the first shutdown or restart no error, second time errors start back up. I have Corsair memory, CMW32GX4M4C3200C16 Link to comment Share on other sites More sharing options...
Mistajase Posted May 29, 2019 Share Posted May 29, 2019 I'm getting the same, Just after I added Corsair st100... coinsidently. Using latest icue version Link to comment Share on other sites More sharing options...
duckiofdeath Posted November 10, 2019 Share Posted November 10, 2019 I am getting the same error at shutdown or reboot: I am using iCue version 3.21.88 (latest). Windows 10 Pro 64-bit Version 10.0.18362 Build 18362 (fully updated) I have a Corsair Harpoon RGB Wireless, connected with the wireless dongle. I have tried moving the dongle to various USB 2.0 and 3.0 ports, front and rear. I have uninstalled iCue, rebooted and reinstalled it. It has been doing permanently since the day I first installed the mouse/iCue. The mouse works fine when using it. Link to comment Share on other sites More sharing options...
Unclewall Posted November 18, 2019 Share Posted November 18, 2019 I get the same thing Link to comment Share on other sites More sharing options...
SeriousTom Posted November 18, 2019 Share Posted November 18, 2019 I upgraded from 3.18.77 and now I also get this on shut down. I uninstalled 3.21.88 and went back to 3.18.77 and my errors are gone, but doing so screwed up my profiles. Seems nuts profiles get messed up between versions, is that neccesary. Link to comment Share on other sites More sharing options...
Abstractals Posted November 25, 2019 Share Posted November 25, 2019 (edited) Same error here using iCue 3.22.74 Tried updating and reinstalling with no change. EDIT: Note the activity of Adobe's Creative Cloud Core Sync process. Maybe there's a conflict between that and iCue... I just bought a H100i RGB, and have a Corsair RGB mouse. My setup: Windows 10 Pro 64 Intel Core i7 9900K ASUS Strix Z370-E Gaming Corsair H100i RGB Platinum 64GB Corsair Vengeance DDR4 3200MHz CMK32GX4M2B3200C16 ASUS GTX970 STRIX ASUS Xonar Essence STX Audio EVGA Supernova 650 P2 Platinum Edited November 25, 2019 by Abstractals Link to comment Share on other sites More sharing options...
madrabbit Posted December 6, 2019 Share Posted December 6, 2019 I'm also getting this error since the last two updates. I've disabled the iCUE.exe from windows startup for now. Link to comment Share on other sites More sharing options...
cooki Posted December 9, 2019 Share Posted December 9, 2019 same thing for me keyboard k70 Link to comment Share on other sites More sharing options...
Ramiroquai Posted December 11, 2019 Share Posted December 11, 2019 (edited) I have the same error since 2 or 3 updates ago. Any help? It's very annoying. Edited December 11, 2019 by Ramiroquai Link to comment Share on other sites More sharing options...
TDean Posted December 13, 2019 Share Posted December 13, 2019 Me too! Help?! Link to comment Share on other sites More sharing options...
Ibadez38 Posted January 6, 2020 Share Posted January 6, 2020 I have the same problem. L'instruction à 0X00000000616B0569 emploie l'adresse mémoire 0X0000000006700DA8. L'état de la mémoire ne peut pas être read. or L'instruction à 0X0000000060AE0569 emploie l'adresse mémoire 0X0000000006880860. L'état de la mémoire ne peut pas être read. When I uninstall iCue, I no longer have this problem. Link to comment Share on other sites More sharing options...
sje_123 Posted January 6, 2020 Share Posted January 6, 2020 Same here, surely there must be a fix? It started about 3 months ago, my PC wont shut down without me clicking OK on the error. I saw a reply about selecting 'run as administrator' on the program, which seems to stop the error at shut down, but this also seems to stop the program starting with windows even though it is in the start up list? Someone, or Corsair. must know about the problem, or be working on a fix. Link to comment Share on other sites More sharing options...
FrontRange Posted January 10, 2020 Share Posted January 10, 2020 I am seeing this exact issue as well. Every. Single. Shutdown. Error appears. Tried on both Intel and AMD systems. Without ICUE no error on shutdown. Link to comment Share on other sites More sharing options...
klint74 Posted January 18, 2020 Share Posted January 18, 2020 Hi, I had the same error you describe here every time when shutting down the computer, even with the same address numbers. That's even funny. This error started happening to me just after updating the iCue software, luckily, I have the hobby of saving the setup file of every driver or util I install on my computer, and I only had to return to my "old" version iCue Software v3.17.94. This is working fine for me on Win10x64 1909 (OS build 18363.535). I could not find this version on Corsair's site, but I could find it here, it is the exact same file (I compared it with the one I already had): https://drivers.softpedia.com/get/Other-DRIVERS-TOOLS/Others/Corsair-Utility-Engine-iCUE-Software-3-17-94.shtml I hope this works for you! Link to comment Share on other sites More sharing options...
Kainam Posted January 18, 2020 Share Posted January 18, 2020 I've been having this same issue for quite a long time. Link to comment Share on other sites More sharing options...
Ramiroquai Posted February 6, 2020 Share Posted February 6, 2020 Same error few months ago, and Corsair support don't help us. This is a bad joke. I can't reboot automatically because I need to click "OK" to boot normally. Link to comment Share on other sites More sharing options...
Kainam Posted February 9, 2020 Share Posted February 9, 2020 I removed the Asus Xonar software and that eliminated the shutdown error. Link to comment Share on other sites More sharing options...
SeriousTom Posted February 9, 2020 Share Posted February 9, 2020 I removed the Asus Xonar software and that eliminated the shutdown error. I kind of need my Asus Xonar softare. Does any Corsair people even look at these problems brought up, because it certainly doesn't seem so. Link to comment Share on other sites More sharing options...
tayguerr Posted February 13, 2020 Share Posted February 13, 2020 Has anyone tested whether the new driver fixed this issue for Xonar users? Link to comment Share on other sites More sharing options...
Hysteresis Posted February 14, 2020 Share Posted February 14, 2020 For me at least the crash no longer occurs with build 3.25.60. This is with the Asus Xonar drivers still in place. Link to comment Share on other sites More sharing options...
SeriousTom Posted February 15, 2020 Share Posted February 15, 2020 Has anyone tested whether the new driver fixed this issue for Xonar users? It still doesn't work for me and I'm getting sick of uninstalling and going back to old versions. Fix it please Corsair ... you changed something and broke it ! Link to comment Share on other sites More sharing options...
tayguerr Posted February 16, 2020 Share Posted February 16, 2020 Didn't work for me either. It doesn't look like Corsair even wants to acknowledge this issue so I ended up fixing it by installing third party Xonar drivers found here: http://maxedtech.com/asus-xonar-unified-drivers/ I'm really not sure if it's the Xonar driver or software that's causing the issue. Just to rule out both, I went with the 1.80a driver with the cmedia (not asus) panel. Link to comment Share on other sites More sharing options...
SeriousTom Posted February 16, 2020 Share Posted February 16, 2020 Didn't work for me either. It doesn't look like Corsair even wants to acknowledge this issue so I ended up fixing it by installing third party Xonar drivers found here: http://maxedtech.com/asus-xonar-unified-drivers/ I'm really not sure if it's the Xonar driver or software that's causing the issue. Just to rule out both, I went with the 1.80a driver with the cmedia (not asus) panel. Thanks, I was using UNi Xonar W10 1825 v1.81a r2 with asus panel. Uninstalled them and went with your suggestion and it seems to be working good. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now