Nvidia GeForce driver bug reportedly hammers SSDs with up to 30GB of writes per hour

Hardware & Components

Nvidia GeForce driver 621.14 blamed for up to 30GB of idle SSD writes per hour

GeForce drivers 621.14 and 621.24 are accused of hammering SSDs with up to 30GB of writes per hour via a runaway log file. Nvidia has not acknowledged the bug.

By
Sophie Lindqvist
Filed
Channel
Hardware & Components
Read
4 min read

Nvidia's GeForce driver 621.14 is reportedly writing up to 30GB per hour to SSDs on otherwise idle PCs. At the high end, that could consume roughly 15% of a 1TB drive's rated endurance every year. Nvidia has not acknowledged the bug. No fix or hotfix exists at this time.

The issue surfaced in an Nvidia forum post by user Andergraude, who described it as "new in 621.14," released November 4. According to the user, the driver operates by "continuously [rewriting] the binary log file" with "real writes" to the drive. The writes come from NVDisplay.Container.exe, the "NVIDIA Display Container LS" service, which logs to the nvlog.nvlgstg file. That service is required for the Nvidia Control Panel and Nvidia App to function. What the log contains is not clear. Not every system is necessarily affected.

The user's "real writes" distinction matters. A per-process write counter does not equal writes that reach the drive. The measurements came from Windows Resource Monitor, Windows performance counters, and CrystalDiskInfo. The drive's Data Units Written counter matched Windows' own reporting. One test showed 515MB of process I/O accompanied by 270MB of total writes to the C: drive over five minutes — roughly 3GB per hour, in line with the user's own estimate. Worse, "the write volume increases as the file grows."

What confirmed measurements show

The confirmed figures are modest but real. Driver 621.01, the previous version, produced less than 2MB of writes per five minutes. Driver 621.14 produced 270MB in the same interval. A second user in the thread confirmed that rolling back resolves the problem.

Reinstallation does not. That second user performed three clean reinstalls using DDU, the standard display-driver removal tool. The problem persisted. The background writing also degraded gaming and video playback, reportedly causing hitching. That suggests the problem worsens under load rather than staying confined to idle systems.

How bad can it get?

A separate thread covers driver 621.24, released November 12. User AyzekUorren reports writes reaching "about 30gb per 1h" there — and "70gb or even more" during longer sessions. This occurred with telemetry disabled in the Nvidia App. The same user noted that every Alt+Tab added between 500MB and 1GB of writes, at least on that system. These are single-user reports, not verified measurements across hardware configurations.

The endurance math is still sobering. A typical 1TB SSD carries a 600TB write rating over a standard five-year warranty. At 270MB per five minutes, a never-sleeping PC would accumulate roughly 28TB per year — close to 5% of rated endurance, and that figure includes everything else the system writes. At 30GB per hour and eight hours of daily use, the annual toll could reach 15% of drive endurance, spent on nothing.

This is not a drive killer. But SSD prices remain elevated, and users guard endurance closely. Avoiding unnecessary writes is a reasonable priority.

The AMD precedent

A similar bug appeared in AMD's video driver last month. The culprit there was the External Events Utility, atieclxx.exe, which reportedly copied its own executable every second on an idle PC. Reported write rates for the AMD bug ranged from 0.3 to 5MB/s. The total drive write rate measured in the 621.14 test was around 0.9MB/s. AMD took more than three weeks to fix its issue, and the fix arrived as an optional update — a timeline worth remembering when estimating Nvidia's response.

What affected users can do

Checking for the bug is straightforward:

  • Open Resource Monitor and look for NVDisplay.Container.exe activity.
  • Look for the nvlog.nvlgstg file in the write list.
  • Check the SMART Data Units Written value with CrystalDiskInfo or the drive vendor's SSD toolbox.

Stopping the service and deleting the log temporarily reduces the writes. The only reliable workaround today is a rollback to driver 621.01 or earlier. Nvidia's release notes for 621.24 list "N/A" under Open Issues, so an official fix has no stated timeline. The company fixed a similar logging problem in 2021 with driver update 471.96, and that fix appeared in the release notes — which suggests acknowledgement, when it comes, will be visible in the same place.

Source: Tom's Hardware

Share this article:

More from Sophie Lindqvist

Sophie Lindqvist

Show full bio

News editor covering money, funding and market shifts around Semiconductors, chip manufacturing, hardware, AI compute at Chip Dispatch.

1,153 articles

Related articles

« Previous article