• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Bug in NVIDIA Game Ready Driver 531.18 Causing High CPU Utilization

If everyone is going to disable this telemetry because they're paranoid, then Nvidia drivers will sure go to hell quality wise.
 
If everyone is going to disable this telemetry because they're paranoid, then Nvidia drivers will sure go to hell quality wise.
You act like they aren't already.
 
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!
You can just block it with your firewall and be done with it. That's why I never experienced this bug. No connection, no telemetry sent.
If everyone is going to disable this telemetry because they're paranoid, then Nvidia drivers will sure go to hell quality wise.
There are people like me who block a lot of stuff not cause of paranoia,
but just because we want all the bandwidth we can get.
 
You can just block it with your firewall and be done with it. That's why I never experienced this bug. No connection, no telemetry sent.

There are people like me who block a lot of stuff not cause of paranoia,
but just because we want all the bandwidth we can get.
What are the addresses to block?
 
What are the addresses to block?
Block the process entirely; no need to block specific ports or address spaces.
No part of the driver other than the telemetry needs internet access
and telemetry not communicating won't break your drivers or anything like that.
 
right .. 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
 
Looks like that's not the case, unfortunately, as the bug did come back a few hours later.
Still good feedback

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
It sets an existing flag in the NVIDIA driver inf file to "true"
 
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.
 
Apparently, nVidia has come up with a fix for this issue. Waiting for NVCleanInstall to get the update.
 
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.
 
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.
 
Why NVCleanstal has option to disable MPOs ?
 
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!
 
Last edited:
Back
Top