A GeForce driver bug could write up to 30 GB per hour to SSDs

Nov 20, 2026 6 min

Users link GeForce drivers 621.14 and 621.24 to excessive SSD writes. Version 621.01 is the alternative some say works for them.

GeForce card users say drivers 621.14 and 621.24 write data nonstop to their SSDs, even when the PC is idle. Some report up to 30 GB per hour through NVDisplay.Container.exe, a process associated with the NVIDIA Display Container LS service; Nvidia has not confirmed the bug.

The complaints appeared on Nvidia forums and Reddit communities, and were covered by TroubleGrid, Tom’s Hardware, Kotaku, and PCWorld. The effect is not the same on every computer: measurements vary, and it is still unclear how many systems are affected.

A background process writes to the log over and over

Reports identify NVDisplay.Container.exe as the process performing the writes. TroubleGrid says the activity targets the nvlog.nvlgstg file, located in the Nvidia folder inside ProgramData. According to that publication, the service rewrites the binary log instead of merely appending new information.

The NVIDIA Display Container LS service is related to the operation of the Nvidia Control Panel and the Nvidia app. Tom’s Hardware reports that user Andergraude described the problem as «new in 621.14» and mentioned the continuous rewriting of the file. It is unclear what information the log contains or why the behavior becomes so intensive.

The figures vary. One user cited by Tom’s Hardware measured about 3 GB written per hour with version 621.14; another calculated up to 30 GB per hour with 621.24. TroubleGrid also reports a test in which the process wrote 515 MB in five minutes with 621.14, compared with less than 2 MB in five minutes after a clean installation of 621.01 under the same conditions.

Driver versionReported activityMeasurement source
621.01Latest version described as clean; less than 2 MB in five minutes in a comparative testTroubleGrid
621.14About 3 GB per hour; another test measured 515 MB in five minutesTom’s Hardware and TroubleGrid
621.24Up to 30 GB per hour in one reportTom’s Hardware and other outlets

The figures are not directly comparable: they come from different systems and methods. TroubleGrid warns that Windows per-process write counters may include data passing through the cache. In one of the cited tests, the 515 MB attributed to the process coincided with 270 MB of total writes to the C: drive, while the person conducting the test also checked the SSD’s SMART counter.

Tom’s Hardware estimates that 30 GB per hour could amount to consuming up to 5% of the rated endurance of a typical 1 TB SSD per year. This is a projection based on that write rate, not a measurement of actual wear across all affected drives. PCWorld adds that some users have also noticed performance problems in games.

The most durable reported fix is to roll back to 621.01

The solution most often mentioned in reports is rolling back to driver 621.01, which predates the versions in question. TroubleGrid reports cases where the intensive writing stopped after changing versions; Kotaku also says that rolling back the driver reduced activity in the test it describes. This is not an official Nvidia fix and has not been confirmed by the company.

That change means giving up any fixes and improvements introduced in 621.14 and 621.24. TroubleGrid also warns that an older driver may not include Game Ready support for newer titles. Its instructions recommend downloading the 621.01 installer before removing the current version and not relying on Windows’ rollback option to restore all driver files.

There is a temporary measure for those who find the specified process and file: stop NVIDIA Display Container LS, delete nvlog.nvlgstg, and restart the service. TroubleGrid cites a test in which writes fell from 515 to 48 MB in five minutes, a 91% reduction. But the same outlet notes that the file grows again and that the figure comes from a single published measurement.

Permanently disabling the service would also stop the reported activity, according to users cited by Tom’s Hardware and TroubleGrid, but there is a practical cost: the Nvidia Control Panel and Nvidia app would not open while the service was stopped. TroubleGrid warns that this prevents users from changing options such as G-SYNC, color settings, display scaling, and per-game 3D settings.

Reports do not prove that all SSDs are at risk

The complaints have spread across PC subreddits, including r/pcgaming and r/pcmasterrace, as well as Nvidia forums. Even so, it is unclear how many computers are experiencing the bug. PCWorld and Tom’s Hardware agree that the frequency and volume of writes are based on user reports, not a public assessment by Nvidia.

A Tom’s Hardware user said that, on their system with 621.24, an Nvidia process reached write speeds of 19 MB per second and reappeared after being closed. They said stopping NVIDIA Display Container LS halted the process. Another participant replied that they had observed unusual activity and had also disabled the service.

On Reddit, some comments speculated that Nvidia might be deliberately damaging drives to encourage people to buy replacements. Others linked the bug to using artificial intelligence tools to write code. The cited reports provide no evidence to support the sabotage theory or to show that AI code generation caused the error.

“Trying to destroy our computers so we stop hoarding all their RAM,”

— Reddit user

Polygon recalls that Jensen Huang had expressed a wish for developers to use chatbots and AI agents more often for programming. That history fueled speculation on social media, but it does not establish a connection between those tools and the behavior of NVDisplay.Container.exe.

Nvidia has not confirmed the problem

Version 621.14 was released on November 4, and 621.24 arrived on November 12, according to Tom’s Hardware and the dates reported by the other outlets. PCWorld says Nvidia has neither confirmed the bug nor offered an official fix. TroubleGrid also notes that the 621.24 release notes list no known issues, although that is not the same as a public response to the complaints.

The case comes shortly after a similar bug attributed to an AMD driver. Kotaku and PCWorld say AMD released a fix for that problem; TroubleGrid distinguishes the two cases: the AMD issue was related to atieclxx.exe, while the one attributed to Nvidia involves NVDisplay.Container.exe and a different log file.

For now, the most concrete check for an affected user is to verify which process is writing and which file is receiving the data. If NVDisplay.Container.exe is not associated with nvlog.nvlgstg, the measures reported for this bug do not apply to that activity. Version 621.01 remains the alternative some users recommend while they wait for a response from Nvidia.

Sources: Polygon.com, Kotaku, Tom's Hardware, PCWorld, TechPowerUp, TroubleGrid, NVIDIA