Jump to content
Corsair Community

Not able to control RGB of Dominator Ram in Icue all of a sudden


loquacious45

Recommended Posts

I have tried re-installing Icue after uninstalling it through Revo. I have tried repairing it through windows settings. I have turned my computer off , rebooted, restarted etc and everything works in that I can control the all of the RGB for the fans and the hub also my graphics card and keyboard but no matter what I do the ram does not show up. t has been working fine for months and now refuses to work. The ram still lights up in a rainbow style and I can access the ram temps and frequencies via Icue dashboard I just cannot access the RGB as it does not show up to work with (see attached screenshot. I have no idea what else to do.

Screenshot 2024-09-04 073309.png

Link to comment
Share on other sites

There was a change in the services that handle background tasks for CUE and there seems to be an issue for some users on moving from 5.17 to 5.18 directly.  Corsair's directions are below.

https://www.reddit.com/r/Corsair/comments/1f3ku3u/known_issue_fix_memory_not_being_detected_by_icue/

 

Other users started rolling back to legacy CUE 4.33 while waiting for a solution and it seems when you update to CUE 5.18 from within the app on CUE 4.33 it side steps this issue.  I've been trying to puzzle out why this works and clean installing CUE 5.18 does not, but I don't have a solid answer.  Since you have CUE Link stuff, none of that will work on CUE 4.33 so you might try to services edit in the first link.  

 

Link to comment
Share on other sites

3 hours ago, c-attack said:

There was a change in the services that handle background tasks for CUE and there seems to be an issue for some users on moving from 5.17 to 5.18 directly.  Corsair's directions are below.

https://www.reddit.com/r/Corsair/comments/1f3ku3u/known_issue_fix_memory_not_being_detected_by_icue/

 

Other users started rolling back to legacy CUE 4.33 while waiting for a solution and it seems when you update to CUE 5.18 from within the app on CUE 4.33 it side steps this issue.  I've been trying to puzzle out why this works and clean installing CUE 5.18 does not, but I don't have a solid answer.  Since you have CUE Link stuff, none of that will work on CUE 4.33 so you might try to services edit in the first link.  

 

Thank you very much I have been tearing my hair out on this one ... the fix seems to have worked!!!

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...