Tuesday, April 30th 2019
NVIDIA Releases GeForce 430.53 Hotfix Driver, Fixing High CPU Utilization Caused by Telemetry
NVIDIA today introduced their latest hotfix driver. Driver number 430.53 addresses reported issues of high CPU utilization (due to NVDisplay.Container.exe) on NVIDIA's previous 430.39 WHQL driver, which added support for their latest GTX 1650 graphics card as well as Windows' 1903 release.
A number of fixes have also been introduced by this driver version. Namely, flickering observed when 3DMark Time Spy is launched; BeamNG application crash on games launch; SLI freezes in Shadow of the Tomb Raider; and monitor flickering on the desktop when videos are being played on a secondary monitor. You can grab this latest hotfix driver release on the link below.DOWNLOAD: NVIDIA GeForce 430.53 Hotfix Driver
A number of fixes have also been introduced by this driver version. Namely, flickering observed when 3DMark Time Spy is launched; BeamNG application crash on games launch; SLI freezes in Shadow of the Tomb Raider; and monitor flickering on the desktop when videos are being played on a secondary monitor. You can grab this latest hotfix driver release on the link below.DOWNLOAD: NVIDIA GeForce 430.53 Hotfix Driver
33 Comments on NVIDIA Releases GeForce 430.53 Hotfix Driver, Fixing High CPU Utilization Caused by Telemetry
Not sure why I don't seem to be effected.
This may have been more of an issue on 2-4 core processors that a lot of people still seem to have.
I'm hoping this fixes that or I'll just roll back.
I have an MSI 1660 Ti Armor and the 425.31 Driver was terrible for me, screen flickering, much lowers fps, massively unstable.
I just tried 430.39 and while more stable than 425.31 my fps was still much lower when I ran FF XV benchmark, far cry benchmark and AC Odyssey benchmarks.
I'm back on 419.67 and everything is stable and fps is back up where it should be.
EDIT: isn't this mandatory spyware in violation of GDPR, at least in the EU? If so, I wonder how long before nvidia get slapped a juicy fine by the EU commision.
and other than disk space it really is not heavy at all... Depends. You do agree to a EULA and privacy policy on install. No names are collected either, so it is probably legal. I mean, it's not right. It's also easy to "protest" by turning off. ;)
I've fixed this issue by using only AMD. :clap:
2. I thought that the telemetry was removed ... I thought the problem was the change to real time. I remember that had saved these instructions while I pondered removing it ... then i kinda forgot about it :)
- Download and run Microsoft Autoruns.
- Type nvidia in the filter box.
- You will find Telemetry in the Task Scheduler section and the nVIDIA Wireless Controller, and ShadowPlay services further down under the registry entries.
- Uncheck NvTmMon, NvTmRep and NvTmRepOnLogon to disable telemetry.
- Uncheck Nvidia Wireless Controller Service and NvStreamKms if you don’t use Shadow Play and nVIDIA wireless controller.
- If you get an error, close the program and right click on Autoruns.exe or Autoruns64.exe and “Run as Administrator.”
This is not exactly a new subject ... i think the stall CPU utilization was caused by sending the bug reports in real time.www.howtogeek.com/280101/relax-nvidias-telemetry-didnt-just-start-spying-on-you/
Im fine at 425.42 vulkan driver atm, also at win10 1809 so no rush for wddm 2.6.