Nvidia acknowledges CPU utilization spikes in GeForce driver 531.18
Cover your face: Nvidia GPU customers who’ve just lately seen unusually excessive CPU utilization after exiting a sport ought to know that the corporate is conscious of the problem and is engaged on a repair. Those severely impacted by this subject ought to take into account quickly rolling again the motive force.
Nvidia has up to date the checklist of identified points for GeForce driver 531.18 to substantiate that customers have reported excessive CPU utilization after quitting a sport. Developers are engaged on a repair, which shall be launched on Tuesday.
Some customers have reported a 15% improve in CPU utilization after closing the sport. Checking the “Processes” tab revealed that Nvidia Container was the perpetrator. More exactly, the newest model of the Nvidia Game Session Telemetry Plugin seems to be the supply of the issue.
FYI – we are going to launch a patch driver tomorrow with the repair
— Sean Peltier (@PellyNV) March 6, 2023
Most customers most likely should not mess with the Nvidia driver information, since neutralizing the DLL file requires deleting or shifting it with administrator privileges. However, for these keen to take action, blocking or deleting the plugin’s DLL information can do the trick. Some Redditors posted directions for doing this, if you’ll.
The further 10-15% of CPU utilization could not hassle some folks, however it could have an effect on CPU-intensive duties. Those who need a direct resolution and do not need to mess with inside information ought to reboot their PC after quitting the sport or roll again to an earlier driver till the repair arrives.
Nvidia additionally added another identified points to the notes for 531.18. It can generally trigger Adobe Premiere Pro and Assassin’s Creed Origins to crash. Additionally, customers of laptops with GeForce GTX 10-series, MX250, or MX350 GPUs might even see random bugchecks.
While this subject could also be inconvenient for some, Nvidia’s driver points are minor in comparison with AMD’s current issues. Adrenalin 23.2.1, launched in February, bricked some Windows installations after most Radeon GPU customers needed to wait two months for brand spanking new drivers, though this was extraordinarily uncommon. The Red group is engaged on an official repair for the problem, however unchecking the “Factory reset” field when putting in the motive force ought to stop it from displaying up.