SSD NVMe M.2 installé sur une carte mère, éclairage bleu

GeForce 621 Drivers: Abnormal SSD Writes Reported

For the past few days, GeForce card owners have reported unusual behavior from recent drivers: an Nvidia process appears to be continuously writing to the system drive, even when the PC is idle. Reported volumes range from a few hundred megabytes to several dozen gigabytes per hour. Nvidia has not yet responded publicly. Here is what we know, what remains to be confirmed, and how to check your machine in two minutes.

What is being reported with drivers 621.14 and 621.24

According to The FPS Review, which compiled testimonials published on Nvidia forums, the process involved is NVDisplay.Container.exe, linked to the Windows service "NVIDIA Display Container LS". It repeatedly overwrites an entire log file located at C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg. Since the file is overwritten in its entirety rather than appended to, the write volume increases as the log grows.

This logging mechanism already existed in earlier versions. What appears to have changed is the rate: it seems to have ramped up starting with Game Ready driver 621.14, and cases are also being reported with 621.24, released on November 12.

Reported measurements

These are user-reported figures, not laboratory tests. The exact configurations (graphics card, SSD, Windows version) are not specified by the sources.

Driver Reported writes Context
621.01 (clean install) less than 2 MB in 5 minutes Idle PC, forum testimonial
621.14 about 515 MB in 5 minutes Idle PC, same testimonial
Unspecified over 3 GB in 10 minutes Another forum testimonial
621.24 about 30 GB per hour Telemetry disabled in the Nvidia app

Source of the figures: Nvidia forum testimonials compiled by The FPS Review (November 19, 2026).

Should you worry about your SSD?

An SSD supports a limited amount of writing, expressed in TBW (terabytes written) by the manufacturer. The FPS Review calculated the worst-case scenario: 30 GB per hour for eight hours of inactivity per day would represent about 87 TB per year, or nearly 14% of the endurance of a given 600 TBW SSD. This is the author's extrapolation from the highest reported figure, not an observed average.

In other words: nothing that will damage an SSD in a few days, but unnecessary wear that is better to identify. Not all PCs seem to be affected with the same intensity: the Kotaku journalist who tested their own machine indicates that their SSD was less affected than in other testimonials.

How to check your PC

Checking is done using tools built into Windows:

  • Resource Monitor: open it from the Start menu, go to the Disk tab, then sort the list by "Write (o/s)". See if NVDisplay.Container.exe and the nvlog.nvlgstg file appear at the top of the list while the PC is idle.
  • Task Manager: Details tab, right-click the column headers to add "Write I/O bytes". Note the process value, leave the PC idle for ten minutes, then compare.

A few megabytes in ten minutes is nothing unusual. Several hundred megabytes or more over the same period correspond to the described behavior.

Workarounds mentioned

None are official. They come from users and have not been validated by Nvidia:

  • Revert to driver 621.01, which testimonials describe as unaffected. This is also what the Kotaku journalist did.
  • Stop the "NVIDIA Display Container LS" service, delete the log file, then restart the service. The writes drop back down, but the file rebuilds over time: it is a reprieve, not a fix.
  • Permanently disabling the service is not recommended: you lose access to the control panel and the Nvidia app.

If your figures are normal, there is no reason to touch anything.

What is confirmed, what is not

  • Observed by users: the process, the file involved, and the write volumes mentioned above.
  • No communication from Nvidia: at the time the articles were published, the manufacturer had neither acknowledged the problem nor announced a fix. The 621.24 release notes make no mention of it.
  • Speculation: some internet users attribute the bug to AI-generated code. Kotaku relays this hypothesis, specifying that it comes from online discussions. Nothing supports it at this stage, nor do the formulas like "writes multiplied by 250" circulating without verified measurements.

AMD Adrenalin 26.11.2: a similar issue fixed on the Radeon side

The timing is notable: on November 18, AMD released its Adrenalin Edition 26.11.2 driver, whose list of fixes specifically mentions excessive writes to the system drive at rest, for the Radeon RX 5000 and RX 6000. We had already mentioned this type of problem with the 26.11.1 version.

According to the release notes summary published by GameGPU, this driver also brings:

  • support for Phantom Blade Zero and the "Charting the Unknown" expansion for Crimson Desert;
  • a fix for a memory leak that lengthened application launch times (RX 5000 and newer);
  • fixes for crashes on RX 9000 during streaming with OBS Studio, and on the first launch of Resident Evil Requiem after a shader cache reset;
  • a fix for driver timeouts in War Thunder.

Among the known issues, AMD notes that RX 6000 cards may not launch Crimson Desert with this version and temporarily recommends staying on 26.11.1 in this case. Occasional crashes also persist on RX 7000 in Assassin's Creed Black Flag Resynced.

Our advice

A recent graphics driver is not always the best fit for your usage. If your PC is working well and the new driver does not concern a game you play, waiting a few days for the initial feedback remains a healthy habit. And regardless of the manufacturer, taking a look at the Resource Monitor after an update costs nothing. At DSGate, every PC is assembled and tested in Paris with a driver validated in the workshop before shipping.

Sources: The FPS Review (19/11/2026) ; Kotaku (19/11/2026) ; GameGPU, AMD Adrenalin 26.11.2 driver notes (19/11/2026).

Back to blog

Leave a comment