Nvidia releases hotfix for GeForce driver bug that hammered SSDs with up to 30 GB of writes an hour

Nvidia's GeForce Game Ready Driver 621.24, released on November 12, brings optimizations for the upcoming Warhammer 40,000: Dawn of War IV and adds support for the DLSS 5 update coming to Where Winds Meet and the DLSS 4.5 Dynamic Multi Frame Generation update for Assetto Corsa Rally. However, like its predecessor, 621.14, it also carries an alarming bug that can eat into the rated lifespan of users' SSDs.
A log file rewritten on a loop
As detailed by TroubleGrid and corroborated by users on Reddit and Nvidia's forums, the NVDisplay.Container.exe process, which runs as the NVIDIA Display Container LS service, repeatedly rewrites a binary log file named nvlog.nvlgstg on the drive where Windows is installed. Users trace the regression to driver 621.14, released on November 4.
The reported figures vary widely between systems. One user recorded 515 MB of writes after idling for five minutes on 621.14, another measured over 3 GB in ten minutes, and a third estimated roughly 30 GB an hour on 621.24. The same idle test on driver 621.01 produced less than 2 MB, which is the source of the widely quoted claim that writes are running 250 times higher than normal.
How much damage could this do to an SSD?
SSD endurance is rated in terabytes written (TBW), typically around 600 TBW for a 1 TB drive. The 250x figure describes the process's write activity rather than how quickly a drive wears out, however, since Windows process counters do not always reflect what physically reaches the NAND. In the same five-minute test, the entire C: drive logged only 270 MB of writes. Even so, by our own arithmetic, 30 GB an hour for eight hours a day would consume around 15% of a typical 1 TB drive's rated endurance every year.
To check the process's activity, Reddit user "xCaliburghost" suggests running the following command in Windows PowerShell (code below):
Get-CimInstance Win32_Process -Filter "Name='NVDisplay.Container.exe'" |
Select-Object ProcessId,
@{N='RAM_MB';E={[math]::Round($_.WorkingSetSize/1MB,1)}},
@{N='Read_MB';E={[math]::Round($_.ReadTransferCount/1MB,1)}},
@{N='Write_MB';E={[math]::Round($_.WriteTransferCount/1MB,1)}}The totals are cumulative since the process last started and cover all of its I/O, so comparing two readings taken a few minutes apart gives a clearer picture of how much is being written to on an (ideally) idle PC.
Nvidia's hotfix and the earlier workarounds
Nvidia has since acknowledged the issue as bug 7116722 and, on November 20, released GeForce Hotfix Display Driver 621.35. Based on 621.24, it lists a single fix: "Excessive writes to file nvlog.nvlgstg may occur in background." As with all of Nvidia's hotfixes, it is an optional beta without WHQL certification, and the company says the safest option is to wait for the next certified driver.
Before the hotfix, the most reliable workaround was rolling back to 621.01, though that brings back its video playback freezes and black screens on some RTX 50 series GPUs. Stopping the NVIDIA Display Container LS service and deleting the log file offers only temporary relief, while disabling the service outright prevents the Nvidia Control Panel and Nvidia app from opening.
A familiar problem for AMD users
The bug surfaced just days after AMD tackled a similar problem, in which its External Events Utility (atieclxx.exe) kept writing to the system drive at idle, at reported rates comparable to Nvidia's. AMD acknowledged the issue before shipping a fix for RX 7000 series cards and newer in Adrenalin 26.11.1 on November 12, then extended it to older Radeon cards on Windows 10 on November 18.
Nvidia, by contrast, stayed silent until its hotfix arrived 16 days after 621.14 shipped, though only days after the reports gained wider attention. Some Redditors have speculated that both companies are "vibe-coding" their drivers, but there is no evidence for this, and complaints about Nvidia's Display Container constantly rewriting its logs date back to at least 2021.

















