Jump to content
Corsair Community

Nvidia RTX 3080 Founders Edition: RGB control gets stuck/freezes after some time


Recommended Posts

 

Dear community,

Dear @c-attack, @DevBiker, @Corsair Nick, @Corsair Albert@Greybeard,

 

the RGB control for my RTX 3080 Founders Edition gets stuck after some time of usage. When the issue appears the RGB effect freezes and stays at the current state. Changing the profile/effect won't be applied. The only solutions are to restart iCUE or to reboot. I don't know if it happens in idle, but it definitely happens while gaming.

My system

  • Hardware
    • ASUS ROG Maximus XI Hero (WI-FI) (newest BIOS: 2004)
    • Intel Core i7-9700K
    • 2x Corsair Dominator Platinum RGB (newest Firmware 1.04.28)
    • Nvidia GeForce RTX 3080 Founders Edition (newest BIOS: 94.02.27.00.13)
    • Corsair iCUE H115i ELITE CAPELLIX (newest Firmware 2.6.201)
    • 6x Corsair ML140 RGB-PWM (8-LED Fan Series)
    • be quiet! Dark Power Pro 12 1200W
    • Corsair K70 RGB MK.2 LP (newest Firmware 3.24)
    • Corsair Glaive RGB Pro (newest Firmware 3.31)
  • Software
    • Windows 11 (clean install)
    • iCUE version (clean install): 4.18.209 (newest release)
    • Nvidia driver (clean install): 497.29 (newest driver)
    • HWiNFO: 7.16-4650 (newest release)
      • CorsairLink and Asetek support disabled
    • MSI-Afterburner: 4.6.4.16255 (newest release)
  • Sidenotes
    • There's no other RGB-software installed besides iCUE
    • It happens with and without HWiNFO and/or MSI-Afterburner being installed/running

Debug-Logs

This is an example for what can be found in the debug logs (CUELogs/2022-01-02T21-58-57.log) when it happens:

 

  • 2022-01-02 21:58:57.151 C cue.plugin: Cannot call: "setLedsColors" "Nvidia/NvidiaPlugin.dll"
  • (...)
  • 2022-01-02 21:58:59.929 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"

 

Please let me know how to fix this issue myself or what you need in order to fix the bug in a future release of iCUE - thanks.

 

Kind regards

Tobias

 

Link to comment
Share on other sites

Yeah I have a RTX 3070 OC and it had the RGB partial LED lighting issue early 2021 and parts of 2020 but it’s been fine 6 months since I used the ASUS iCue download on the Corsair page, helped the RGB having the red triangle too. Recently it stopped working again not sure why I updated it all still nothing. One photo is startup as Armoury Crate can control LEDs fine but when iCue kicks in no.

C418EB00-18A9-4DB5-9302-F1EBBB7520BE.jpeg

830BD0E5-67F1-45D4-A3EC-76DC5B15DE41.jpeg

Link to comment
Share on other sites

This surely is an issue for you but has nothing to do with my problem described in this topic.

The result might seem similar, but the cause is completely different. I assume you're using the ASUS plugin, which I don't.

Edited by t0niX
Link to comment
Share on other sites

Update: Clean install of Windows 11, no HWiNFO, no MSI Afterburner and no RivaTuner Statistics Server (which shouldn’t be a problem anyways) installed.

Nvidia driver 511.23 installed.

After starting Warzone it took only a couple of minutes until the RGB (static white) on my RTX 3080 froze. If I switch effects (e.g. to rainbow) every single component switches RGB colors but my RTX 3080. And yes, iCUE is configured correctly, the effect should be applied on all components.

This is a software/driver related bug.

 

PS: Restarting iCUE fixes the issue instantly (until it happens again).

Edited by t0niX
Link to comment
Share on other sites

  • 2 weeks later...

Here's another update. I was able to catch the exact moment it happened in the debug logs. It - again - happened instantly after starting to play Call of Duty: Warzone.

2022-01-25 23:07:15.360 W qrc:/qml-imports/com/corsair/cue/deviceview/DynamicGeometryView.qml:185: TypeError: Cannot read property 'extensionsScalingRatio' of null
2022-01-25 23:07:15.377 W qrc:/qml-imports/com/corsair/cue/deviceview/DynamicGeometryView.qml:185: TypeError: Cannot read property 'extensionsScalingRatio' of null
2022-01-25 23:07:21.397 I cue.devices.dram: Dram sensor updating skipped: "vid<1b1c>pid<000004>serial<DOMINATORPLATINUMRGB>index<0>"
2022-01-25 23:07:21.830 C cue.plugin: Call failed: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:07:22.462 W cue.sensors.system_info: Update values already requested for: SensorDataCache::Resolution::OneSecond
2022-01-25 23:07:22.462 I cue.devices.dram: Dram sensor updating skipped: "vid<1b1c>pid<000004>serial<DOMINATORPLATINUMRGB>index<0>"
2022-01-25 23:07:22.511 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:07:22.511 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:07:22.518 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:07:22.518 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:07:24.585 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:07:24.585 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:07:25.218 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:07:25.218 W cue.plugin.protocol.sensors: Invalid sensor requested: "vid<0>pid<0>serial<NvidiaPlugin.dll:NVIDIA_220610DE_146710DE_A1_2206_1_0>senstype<power>sensindex<0>"
2022-01-25 23:07:25.218 W cue.plugin.protocol.sensors: Invalid sensor requested: "vid<0>pid<0>serial<NvidiaPlugin.dll:NVIDIA_220610DE_146710DE_A1_2206_1_0>senstype<temperature>sensindex<1>"
2022-01-25 23:07:25.218 W cue.plugin.protocol.sensors: Invalid sensor requested: "vid<0>pid<0>serial<NvidiaPlugin.dll:NVIDIA_220610DE_146710DE_A1_2206_1_0>senstype<power>sensindex<0>"
2022-01-25 23:07:25.218 W cue.plugin.protocol.sensors: Invalid sensor requested: "vid<0>pid<0>serial<NvidiaPlugin.dll:NVIDIA_220610DE_146710DE_A1_2206_1_0>senstype<temperature>sensindex<1>"
2022-01-25 23:07:30.206 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:07:35.208 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:07:40.210 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:07:45.210 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:07:50.206 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:07:55.206 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:08:00.206 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:08:05.206 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:08:10.206 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:08:15.206 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:08:20.206 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:08:25.206 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:08:30.207 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:08:35.207 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:08:40.207 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:08:45.290 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:08:50.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:08:55.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:09:00.268 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:09:05.270 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:09:10.270 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:09:15.270 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:09:20.268 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:09:25.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:09:30.271 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:09:35.268 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:09:40.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:09:45.271 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:09:50.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:09:55.272 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:10:00.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:10:05.271 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:10:10.270 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:10:15.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:10:20.272 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:10:25.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:10:30.268 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:10:35.271 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:10:40.271 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:10:45.268 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:10:50.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:10:55.270 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:11:00.270 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:11:05.275 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:11:10.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:11:15.268 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:11:20.271 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:11:25.268 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:11:30.271 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:11:35.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:11:40.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:11:45.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:11:50.268 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:11:55.268 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:12:00.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:12:05.270 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:12:10.268 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:12:15.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:12:20.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:12:25.270 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:12:30.274 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:12:35.268 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:12:40.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:12:41.899 W cue.profiles.mic_prop_sync: Cached sidetone is Unknown
2022-01-25 23:12:41.911 C cue.plugin: Cannot call: "setLedsColors" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:12:42.514 C cue.plugin: Cannot call: "setLedsColors" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:12:42.517 W cue.profiles.mic_prop_sync: Cached sidetone is Unknown
2022-01-25 23:12:42.836 C cue.plugin: Cannot call: "setLedsColors" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:12:42.837 W cue.profiles.mic_prop_sync: Cached sidetone is Unknown
2022-01-25 23:12:43.144 W cue.profiles.mic_prop_sync: Cached sidetone is Unknown
2022-01-25 23:12:43.158 C cue.plugin: Cannot call: "setLedsColors" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:12:45.269 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"
2022-01-25 23:12:50.282 C cue.plugin: Cannot call: "readDeviceProperty" "Nvidia/NvidiaPlugin.dll"

Any ideas?

Link to comment
Share on other sites

  • 1 month later...
Posted (edited)

Alright guys - after months, days, hours, and hours, and hours of trial and error, LOTS of testing and even more frustration I've finally found THE solution to my problems with iCUE and can enjoy my PC again ever since.

I'm confident that adjusted CPU priorities are the missing part to the puzzle. It seems that every time a process is taking up very high CPU load (in my case CoD: Warzone) iCUE/some of its services ran into timeouts and have triggered flatlining of sensor data/freezing of RGB effects. Since I've adjusted the priorities (see attached screenshot) I haven't had a single issue.

It is extremely unfortunate that in more than 10 months since I created my first ticket and after over 100 emails no one from Corsairs support has been able to help me out or resolve the issue. I would welcome an official statement on the drama I (and others) have experienced.

I'm happy to share this with you and I'm even happier about everybody I'm able to help out with the above information. Please share your feedback!

Enjoy!! 🙂

220307_iCUE_Solution.png

Edited by t0niX
Link to comment
Share on other sites

I'm having this same exact issue with similar parts.  I see other threads with the similar issues from September. I thought it was hopeless. It's sad that after all of this, there hasn't been any real help. This fix worked for me. So will this be using more power or even power while idle since those processes are set to high? Thanks for the tip, it is very much appreciated. 

  • Thanks 1
Link to comment
Share on other sites

I‘m glad this fix worked for you!!

From my understanding the priority of a process simply tells the CPU which processes should be handled with higher priority under load. If (background) processes with higher priority are loading up a lot of CPU you eventually will notice FPS spikes/hiccups while gaming.

Regarding power consumption I don’t see any difference as the processes are just handled with higher priority, not consuming more power than before. This might be different if you’re CPU is running under high load and processes are being priorized/handled differently though.

Link to comment
Share on other sites

  • 3 weeks later...

Thank you @t0niX there's finally a workaround/fix, it looks like it worked for me too. Right now I'm using high priority for all the stated processes/services, and so far it's good, if after some hours I have an issue I'll change to real time for CueLLAccessService.exe

  • Like 1
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
 Share

×
×
  • Create New...