Some GeForce users report that Nvidia’s background software is repeatedly rewriting a log file even while their PCs sit idle. Reports involve drivers 621.14 and 621.24; one user on 621.24 put the activity at roughly 30GB an hour. A log file should keep records, not become the workload. Source Source
The reports don’t establish that an SSD is being destroyed. Rates vary, some users can’t reproduce the behavior, and Wccftech cautions that Windows process-level I/O counters don’t necessarily equal writes to the SSD’s physical NAND memory. Source Source
The same log, over and over
The reports identify NVDisplay.Container.exe, which Wccftech associates with the NVIDIA Display Container LS service, and this log file: Source Source
C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg
On Nvidia’s community forum, user Lamquin described a roughly 14.5MB log being written repeatedly on driver 621.24. A modest file size isn’t an alibi: repeated overwrites can generate activity without leaving an enormous file behind. Source
Wccftech reports observing the behavior on its own Windows 11 PC with an RTX 4090. Resource Monitor showed approximately 1.43MB/s of writes targeting that log while the machine was idle, despite Capture Highlights, ShadowPlay and the Nvidia App overlay being disabled. The snapshot doesn’t establish a sustained write rate or actual NAND wear. Source
Wccftech and Neowin also cite the same user’s comparison: roughly 515MB of process writes during five idle minutes on 621.14, versus under 2MB over the same interval on 621.01. Source Source
Neowin says that user also checked the SSD’s own health-reporting data (SMART) and found the additional writes reflected in its units-written counter. A rise in that counter doesn’t quantify physical NAND wear or establish a resulting drive failure. Source Source
Forum user mertuygr reported process-counter estimates of roughly 120–160GB/hour from one-minute samples after about 43 hours of uptime. Those short samples don’t establish a sustained physical-write rate. Source
Forum user Dankbomber1990 described unsuccessful attempts to reproduce it on both 621.14 and 621.24 using an RTX 5070 Ti. That doesn’t give the whole GPU generation a pass. The trigger remains unverified. Source
Check the destination, not just the process
To investigate your own PC, Wccftech suggests opening Windows Resource Monitor: press Win + R, enter resmon, select Disk, and watch for sustained writes from NVDisplay.Container.exe to the specific log path above while the PC is idle. Source
One forum user said disabling Instant Replay stopped their Nvidia Container activity, while Wccftech observed the log writes with capture features disabled. A busy Nvidia process isn’t, by itself, a diagnosis. Source Source
Some users report relief after reverting to 621.01, or stopping NVIDIA Display Container LS, deleting the log and restarting the service. Neither approach is a confirmed permanent fix. Wccftech warns that permanently disabling the service can prevent Nvidia Control Panel and the Nvidia App from functioning correctly. Source Source
Setting the log to read-only has also produced mixed results: several forum users say the service simply creates a fresh file after a restart. Apparently, telling this particular log to stop writing doesn’t always end the conversation. Source
Wccftech reported on November 18 that Nvidia hadn’t publicly acknowledged this specific logging problem. Check what your own machine is doing before treating a forum workaround as mandatory maintenance. Source
Comments