Inphra Posted October 21 Posted October 21 (edited) Issue: - "QmlRenderer.exe" has high CPU usage (5-15%) - Due to high CPU usage, CPU cannot clock down to save energy resulting in higher idle temps (~8C) - Setting framerate of LCD to 1 lowers the processes CPU usage, but not completely (this is not ideal nor a fix) - Clean installation (full wipe) did not resolve the issue - Murals are not enabled and all LEDs are set to a static colour Specs: - 13700K - 4090 FE - H150i Elite LCD (only supported RGB device on system) - iCUE 5.19.104 Additional Notes: - Issue has been recently introduced - The most recent post on this very issue is here: Edited October 21 by Inphra
c-attack Posted October 21 Posted October 21 (edited) You need the QMLrender for the LCD. https://forum.corsair.com/forums/topic/191554-high-cpu-usagevoltage-with-geforce-56590-driver/ Edited October 21 by c-attack
kingmotley2 Posted October 26 Posted October 26 Have the same issue. I don't even have anything running on the LCD, just the default water temp and it drives one core of my CPU to 100%. I just renamed it to QmlRenderer.exe.bak and then killed the process. I would be nice to actually be able to use the LCD, but not when it eats and entire core.
Inphra Posted Wednesday at 02:25 AM Author Posted Wednesday at 02:25 AM I've updated to the latest driver and there appears to be an improvement. It does appear to be taking anywhere from 0.5-2% CPU. While this is certainly better than 10+%, I'm wondering what the CPU usage was prior to this issue coming up? Does anyone have any recollection or anyone on a previous version of the nvidia driver that can share?
Cor.Fan Posted Wednesday at 06:56 AM Posted Wednesday at 06:56 AM Qmlrenderer is used by gpu to render the interface of applications on windows and on screens. My iCue showed more than 10% usage and temps of cpu on idle where around 50c. Now, I have 28c cpu temp and usage won't go over than 2-3%. My gpu usage while iCue is running won't go over 1%. Previous nvidia gpu drivers had high cpu usage but they fixed it with version 566.14
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now