Tech Products

Nvidia’s GeForce driver bug wrote up to 30 GB an hour to idle SSDs

Susan Hill
Add us on Google

Nvidia‘s latest GeForce drivers for Windows have been rewriting the same log file on the system drive, over and over, while the PC sits doing nothing. On some machines that meant gigabytes of writes an hour from a single background process, the kind of constant churn that eats into a solid-state drive’s rated lifespan. Nvidia has now acknowledged the bug and shipped an optional hotfix.

Anyone with a GeForce card who installed one of the two most recent Game Ready drivers may be affected. The culprit is NVDisplay.Container.exe, the process behind the NVIDIA Display Container LS service. Users found it truncating and rewriting a binary log called nvlog.nvlgstg instead of adding to it, so the write volume grows as the log grows, and it keeps going when nobody is gaming.

The measurements come from users, not from Nvidia, and they vary widely. One owner on Nvidia’s forums logged 515 MB of writes from the process after five minutes of idling on driver 621.14, against less than 2 MB on the older 621.01. Another measured more than 3 GB in ten minutes, and a third estimated roughly 30 GB an hour on 621.24, according to reports compiled by the troubleshooting site TroubleGrid. Wccftech reproduced the behavior on an RTX 4090 system at about 1.43 MB per second, around 5 GB an hour if sustained.

For scale, a typical 1 TB consumer SSD is rated for about 600 terabytes written over its life. Notebookcheck calculated that 30 GB an hour for eight hours a day would use up around 15% of that budget every year, spent by a process that should barely touch the disk. On a clean driver, the same idle test writes a couple of megabytes.

The alarming figures need a caveat. Windows counts writes that land in the file cache, so per-process totals can overstate what physically reaches the flash chips: in the same five-minute test that showed 515 MB from Nvidia’s process, the whole C: drive logged only 270 MB. Several users checked their systems and found nothing unusual, so not every installation misbehaves. And the fix is a hotfix, an optional beta without Microsoft‘s WHQL certification, which Nvidia says most people can skip in favor of the next certified driver.

Checking takes about a minute. Open Resource Monitor by typing resmon into the Windows Run box, go to the Disk tab and look for NVDisplay.Container.exe writing to nvlog.nvlgstg every few seconds. The older workarounds all cost something. Rolling back to 621.01 brings back the video playback freezes and black screens that driver caused on some RTX 50 series cards. Stopping the service and deleting the log only helps until the file grows back, and disabling the service outright locks you out of the Nvidia Control Panel and the Nvidia app, where G-SYNC and color settings live.

Nvidia is not the only one. AMD recently fixed a near-identical problem in which its External Events Utility, atieclxx.exe, kept writing to the system drive on idle PCs. Complaints about Nvidia’s display service hammering its own logs also go back years: a related bug that rewrote a different file in the same folder was fixed in a driver in 2021.

The regression arrived with driver 621.14 on November 4 and carried over into 621.24 on November 12, whose release notes listed no open issues. Nvidia stayed silent for 16 days, then logged the problem as bug 7116722 and released GeForce Hotfix Display Driver 621.35 on November 20. Built on 621.24, it lists a single change: excessive writes to the nvlog.nvlgstg file in the background. The bug and the fix are the same on Windows 10 and 11 in every market. AMD’s fix arrived in Adrenalin 26.11.1 on November 12 for RX 7000 series cards and newer, and reached older Radeon cards on Windows 10 on November 18.

Nvidia has not said which certified Game Ready driver will carry the fix. Until it does, affected owners must choose between an uncertified beta and an SSD that spends its idle hours rewriting a log nobody reads.

Tags: , , , , ,

Add us on Google

Discussion

There are 0 comments.