killersloth

I was idling around 5c over water temp and getting corsair display adapter crashes on boot on 3.29.110. Rolled back to 3.25.60 as someone else had stated it was stable, working as expected on that old release... shame.

Corsair should just replace the icon for iCUE with an overflowing bowl of spaghetti with their next update. The first step is acceptance.

I've had to roll back to 3.17.94 after the last 5 or 6 updates now due to some issue or another. Waiting for some release notes and feedback on 3.28.75 before I go down that hole again.

This happens to me sometimes, I'd think it's got more to do with motherboard not quite reporting right. I have to shut down the pc, flip the psu switch off, and press the power button to drain it completely. Then boot up normally and it displays all the correct info in dashboard again. I felt like it may be a board issue because I had to do the same thing to fix Aura when RGB used to act up on me.

Had a couple days of relatively light issues with 3.25.60, crashes in background that seemingly recover without me even noticing and dashboard inaccuracies. This morning however, after ICUE crashed on boot, it refused to start whatsoever. After rebooting it continued to crash, tried a shutdown and flipping the PSU switch off for a bit and still crashing. Had to just go in and uninstall, twice actually, first time I didn't check the box to delete data for all users and it continued to crash after reinstall. Went back to 3.17.94, so far so good. If you haven't updated to 3.25.60, just don't. edit: Solid day of gaming with no issues from ICUE when using 3.17.94. Definitely going to be hesitant about updates from here out...

So, after running a day without Corsair.Service.DisplayAdapter.exe running, I put it back in and it's working problem free now. idk...

This Corsair.Service.DisplayAdapter issue is kind of similar to the Corsair Gaming Audio Service problem, seems sloppy. If you rename or delete "~\Corsair\CORSAIR iCUE Software\Corsair.Service.DisplayAdapter.exe" your GPU will not show up in dashboard but you'll no longer get that error on startup. Usually get some random 0rpm fans showing up in dashboard, this is new though.