Tuesday, March 7th 2023

Bug in NVIDIA Game Ready Driver 531.18 Causing High CPU Utilization

Last week's release of NVIDIA's Game Ready Driver introduced a new bug with the NVIDIA Display Container process that increases CPU usage by as much as 15% after closing a game. NVIDIA has recently confirmed the bug on their forum in a feedback thread and assigned it a bug track ID of 4007208. The problem appears to stem from a telemetry service known as NvGSTPlugin.dll, or Game Session Telemetry Plugin, which is loaded by NvidiaContainer after a game has been run. Some users are reporting that completely removing the offending .dll solves the problem entirely and a guide on how to do so has been posted on the r/nvidia subreddit in a thread about the release. If that sounds like far too much hassle then the prevailing advice is to simply remain on driver version 528.49 until the issue is resolved. NVIDIA is expected to release a hotfix driver as early as tomorrow to address this and possibly other issues.

Update Mar 7th: NVIDIA issued a hotfix driver release for this bug.
Source: Tom Warren (Twitter)
Add your own comment

40 Comments on Bug in NVIDIA Game Ready Driver 531.18 Causing High CPU Utilization

#26
tabascosauz
W1zzardright .. maybe that ensures the DLL never gets loaded
Looks like that's not the case, unfortunately, as the bug did come back a few hours later. Not a problem anyways as the hotfix is out, but does make me wonder what exactly NVCleanstall does when it says it "disables" driver telemetry
Posted on Reply
#27
W1zzard
tabascosauzLooks like that's not the case, unfortunately, as the bug did come back a few hours later.
Still good feedback
tabascosauzNot a problem anyways as the hotfix is out, but does make me wonder what exactly NVCleanstall does when it says it "disables" driver telemetry
It sets an existing flag in the NVIDIA driver inf file to "true"
Posted on Reply
#28
umeng2002
I had the bug, and deleted the offending file. But then I used nvcleanstall and enabled the remove telemetry option, and that takes care of the issue too.

The nvcontainer "contains" components for the driver. So you can kill the telemetry without killing the container, which is needed for the driver to work properly. When nVidia started shoving telemetry down everyone's throats, they had the telemetry service separated from other driver components. To try and trick people and stop them from removing the telemetry, nvidia just wrapped everything up including telemetry in the nvcontainer service.
Posted on Reply
#29
trparky
Apparently, nVidia has come up with a fix for this issue. Waiting for NVCleanInstall to get the update.
Posted on Reply
#30
umeng2002
Actually after more testing, nvcleanstall DIDN'T fix the issue. in the bugged driver. So I installed the hotfix driver with nvcleanstall. You don't need to wait for nvcleanstall to update. Download the hotfix and tell nvcleanstall to use the downloaded exe.
Posted on Reply
#31
Unregistered
Just block the telemetry by your firewall...
I didn't install the hotfix and I never saw this bug, but I did see on other forums that people with the same GPU (and CPU) had the problem.
Posted on Edit | Reply
#32
Klemc
Why NVCleanstal has option to disable MPOs ?
Posted on Reply
#34
Klemc
umeng2002Yes
But why please ?
Posted on Reply
#36
Klemc
Allright.

Oh, and i had an error message about the HDAudio sleep timer disable option (during install), i have no speakers on my monitor, could be the reason ?

And also, if i set DSR to ON and select reolutions i need, then turn NVContainer sevice OFF and use NvidiaProfileInspector only instead NVCP after, is it good ?

//

EDIT :

R0H1T said:
You can simply disable it as a service, enable when you need to open the Nvidia control panel. You don't need to run it to enable the display driver, in fact it's one of the most disposable component from the driver package!
Posted on Reply
Add your own comment
Dec 22nd, 2024 06:51 EST change timezone

New Forum Posts

Popular Reviews

Controversial News Posts