Search the Community
Showing results for tags 'icue crash'.
Hello, I am new here, so sorry if I am not posting in the correct place. I have been running into an issue with my k95 where I see the red triangle with an exclamation point next to it (will be posting issue in another thread). This lead me to discover another issue. When attempting to resolve the issue with my K95 by quitting and restarting iCUE, I have been experiencing constant crashes of the iCUE software. I am unable to get it to start up again after quitting. Steps to replicate: 1) Quit iCUE 2) Launch iCUE 3) Observe system tray where iCUE icon appears 4) Wait a couple minutes and hover mouse over iCUE icon in system tray 5) iCUE icon disappears and is not running In addition to my system specs, I have the following Corsair peripherals: K95 RGB PLATINUM XT Mechanical Gaming Keyboard — CHERRY® MX Brown Dark Core RGB Pro SE
I have been using iCUE for over a year and I have noticed in the past couple months that iCUE appears randomly to stop reading ALL sensor data. When I view the Dashboard, where all the system metrics displayed, everything is flatlined. This is seriously problematic because my CPU cooler fans are controlled through iCUE and when the temps rise and iCUE freezes, my fans to not accelerate as they should. I have done plenty of reading on this already and have tried several different possible solutions but have had no success in correcting this issue. Please help, I don't want my CPU to get cooked because of a software issue (if that's the case). ADDITIONAL SPECS: I have my PC specs listed on my profile, however, it does not mention that I am using the Commander Pro. I have 3 Corsair LL140 140 mm Fan and 3 Corsair RGB LED Light Strips connected to it. Also, I am using the Corsair H115i PRO as my CPU cooler. I have attached the system and info logs to this thread: icue-sensors-stop-reading.zip
I'm using the latest version of iCUE and sometimes it doesn't start on its own when I start my computer. Every time this happens I get a 0xc5 error code on event viewer. What could it be? Here's the event data iCUE.exe 126.96.36.199 5f354c18 Qt5Core.dll 188.8.131.52 5e7dfb32 c0000005 0006bcae 2854 01d682a250b197ff C:\Program Files (x86)\Corsair\Corsair Utility Engine\iCUE.exe C:\Program Files (x86)\Corsair\Corsair Utility Engine\Qt5Core.dll
So, I built this new PC a couple of months ago and I was trying to trace an intermittent crash that was getting more and more common as time went on. It started off as maybe once a week, and by last week I had a day where it was about every 10 minutes. I've finally managed to trace it to the iCUE software. I can force it to happen way more often by having iCUE open to monitor my hardware and not just down in the system tray... which is rather inconvenient since that means I can't monitor my temps etc. Specifically, I think its the CorsairServices in task manager, but it tends to crash and close iCUE in the process. First my PC gets sluggish, then discord will turn into a black window, then if Im not fast enough to get task manager open and close CorsairServices my entire PC will freeze and eventually all three monitors will go black. In the past I would just have to force reboot my PC because it wouldn't recover, but I have now discovered that having removed some LED backlights that I was just powering in the back of my PC (they weren't talking to anything and as far as I could tell my PC didnt even recognise them as a device) sometimes it now manages to recover from the crash and close iCUE down. Some intense googling and I can see there are people that have had this black screen crash since 2017. I haven't found any solutions anywhere other than "stop using iCUE and find alternative RGB and monitoring software". Almost everything that is RGB and that I want to monitor is Corsair. I would REALLY like to therefore use Corsair's software. Are there any fixes for this? Are there any fixes in the work for this? Can any of the staff actually advise if anything is being done or is it just still conveniently being ignored because the devs think its too niche and not widespread enough to address?