iCUE/SignalRGB fail: nvidia driver update 572.83

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I can confirm the latest iCUE version 5.25.97 on Windows 11 23H2 fails to detect the RAM modules: Corsair Dominator Platinum RGB CMT64GX5M2B6000Z40 x 4 installed on Motherboard: ASRock B650E Steel Legend WiFi.

The detection failure seemed to start happening after updating/re-installing nvidia graphics driver to version: 572.83-desktop-win10-win11-64bit-international-dch-whql.exe

I also had some trouble with asus armoury crate failing to login but after a de-install/re-install/update and finally repair/reset it works again so at least the graphics card smart/temperature color is working again.

Even more bizar:

SignalRGB also completely stopped working !

All PC cables were un-plugged/re-plugged to rule out any electrical issues.

This must definetly be some software issue, most likely with the latest nvidia graphics driver. I did not tell it to do a clean install, just continue using settings, I was only afraid of maybe losing color profile DCI P3 D65 for monitor, but that's probably a windows setting. Not sure if performing a clean install might help.

This issue sucks pretty badly for two reasons:

1. Summer is coming and the dominator set was a great way to observe multiple system component temperatures !

2. Now the RAM set is stuck in "device-mode" which I set to some red christmas lights falling down to indicate the system is booting... but now it's stuck in that mode, which kinda sucks and is annoyingly distracting...

I hope this issue gets resolved soon.

Yesterday I did have an electric shock discharge on the keyboard while the system was off... but I doubt that has anything to do with it, so far the rest of the system seems to be working fine as well as the leds working, also 2 hours ago SignalRGB was still working, the issues clearly started with software updates...

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Skybuck Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 18 Apr 2023 Status: Offline Points: 1575	Post Options Post Reply Quote Skybuck Report Post Thanks(0) Quote Reply Topic: iCUE/SignalRGB fail: nvidia driver update 572.83 Posted: 20 Mar 2025 at 11:25pm
	I can confirm the latest iCUE version 5.25.97 on Windows 11 23H2 fails to detect the RAM modules: Corsair Dominator Platinum RGB CMT64GX5M2B6000Z40 x 4 installed on Motherboard: ASRock B650E Steel Legend WiFi. The detection failure seemed to start happening after updating/re-installing nvidia graphics driver to version: 572.83-desktop-win10-win11-64bit-international-dch-whql.exe I also had some trouble with asus armoury crate failing to login but after a de-install/re-install/update and finally repair/reset it works again so at least the graphics card smart/temperature color is working again. Even more bizar: SignalRGB also completely stopped working ! All PC cables were un-plugged/re-plugged to rule out any electrical issues. This must definetly be some software issue, most likely with the latest nvidia graphics driver. I did not tell it to do a clean install, just continue using settings, I was only afraid of maybe losing color profile DCI P3 D65 for monitor, but that's probably a windows setting. Not sure if performing a clean install might help. This issue sucks pretty badly for two reasons: 1. Summer is coming and the dominator set was a great way to observe multiple system component temperatures ! 2. Now the RAM set is stuck in "device-mode" which I set to some red christmas lights falling down to indicate the system is booting... but now it's stuck in that mode, which kinda sucks and is annoyingly distracting... I hope this issue gets resolved soon. Yesterday I did have an electric shock discharge on the keyboard while the system was off... but I doubt that has anything to do with it, so far the rest of the system seems to be working fine as well as the leds working, also 2 hours ago SignalRGB was still working, the issues clearly started with software updates...