Two recent GeForce driver releases appear to be rewriting a log file continuously while a PC sits idle, pushing gigabytes of unnecessary writes onto the system SSD every hour. The reports surfaced on Nvidia's own forums and were compiled by Tom's Hardware, and they cover driver 621.14, released November 4, and 621.24, released November 12.
The writes come from NVDisplay.Container.exe, the service behind the Nvidia Control Panel and the Nvidia App. A user posting under the name Andergraude described the behaviour as new in 621.14, with the process "continuously rewriting the binary log file" that lives at nvlog.nvlgstg. Measurements taken from Windows Resource Monitor, Windows performance counters and CrystalDiskInfo put the load at about 270MB of real drive writes every five minutes, or roughly 3GB an hour. A second user reported the newer 621.24 reaching "about 30gb per 1h" in longer sessions, even with telemetry switched off in the Nvidia App.
What the numbers do to a drive
A typical 1TB SSD carries a five-year warranty rated for about 600TB of total writes. At the measured 3GB an hour on a machine that never sleeps, the annual total lands near 28TB, about 5% of the rated endurance. At the higher end of the reports, 30GB an hour for eight hours a day adds up to roughly 15% of endurance each year, spent on nothing.
That is not enough to kill a drive, but it is enough to matter when buyers pay a premium for endurance and when flash prices have been climbing. The totals also include everything else the system writes, so the logging service is a share of the figure rather than all of it; the rollback comparison is the cleaner evidence, since the same five-minute test on driver 621.01 produced under 2MB. The volume also grows as the log file grows, according to the same thread, which means the slowest cases get worse the longer a machine runs. Stopping the service and deleting the log resets it temporarily. Three clean reinstalls using DDU did not fix it for one of the users, and the process also appeared to cause hitching in games and video playback, suggesting the cost rises under load.
Rollback is the fix for now
Nvidia has not acknowledged the bug. The release notes for 621.24 list its open issues as "N/A", and no hotfix has been announced. The workaround circulating in the threads is to return to 621.01, where the same five-minute window produced less than 2MB of writes, and users who rolled back reported that the behaviour stopped.
Anyone who wants to check a machine can open Resource Monitor and look for NVDisplay.Container.exe writing to nvlog.nvlgstg, then read the SMART Data Units Written value in CrystalDiskInfo or the drive vendor's toolbox and watch whether it climbs while the PC is doing nothing.
The same shape as AMD's utility
The pattern repeats one from last month, when AMD's External Events Utility, atieclxx.exe, was found copying its own executable every second on idle systems. That case, which we covered when Radeon owners started comparing notes, produced rates between 0.3 and 5MB per second against the roughly 0.9MB per second measured in the Nvidia test, and AMD let it run for more than three weeks before shipping an optional update.
A logged background service that writes in a loop is a maintenance problem rather than a security one, but it lands in the same category as the month's other quiet software failures: unglamorous defects in code that runs on millions of machines, found by users rather than by the vendor's test lab. The practical advice until Nvidia responds is to check the counter, and if it is climbing, to install the older driver.