Some Windows 11 PCs running Nvidia GeForce drivers 621.14 or 621.24 are reportedly generating unusually frequent background writes to an SSD. The activity is associated with Nvidia's Display Container process and a logging file, rather than a game installation or an obvious download. For affected users, that makes the problem easy to overlook.

Windows Latest's Abhijith M B reports user observations ranging from around 3GB to 30GB of writes per hour. Those figures deserve investigation, but they are not proof that every installation is affected or that an SSD is about to fail. The practical response is to measure your own machine before changing drivers.

What the reported Nvidia driver issue involves

According to Windows Latest, users have traced the repeated writes to NVDisplay.Container.exe, which runs as the NVIDIA Display Container LS service. The file involved is:

C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg

One report involved an RTX 4070 Super running Windows 11 25H2. The user observed 515MB of process-level writes over five minutes with the affected driver, compared with less than 2MB on 621.01. Another user reported substantially higher activity on 621.24 despite having telemetry disabled in the Nvidia App.

These are reported observations, not QloudBlog laboratory measurements. Windows Latest also notes that some users running the same drivers see no unusual activity. At the time of its report, the publication said Nvidia had not acknowledged this issue in its forums or release notes.

Why write counters need careful interpretation

An application's write total is not automatically the amount of data physically written to flash memory. Windows buffering and storage behavior complicate that relationship. Even SSD host-write counters describe traffic received by the drive, not necessarily the underlying NAND writes after the controller's internal operations.

The source illustrates the distinction: during the test showing 515MB of process writes, the system drive recorded 270MB of writes, with the SSD's SMART counter supporting the drive-level figure. Simply taking the biggest process counter and treating it as SSD wear can therefore mislead.

Sustained unnecessary writes are still worth addressing. However, endurance ratings are not countdown timers, and a brief burst of activity does not establish a long-term failure risk. The useful evidence is a repeatable increase in drive writes under comparable conditions, alongside the SSD's health information and the workload you actually run.

Check your Windows 11 PC before intervening

Start by recording your GPU model and installed GeForce driver version. Then use Windows' built-in Resource Monitor:

  1. Press Win + R, enter resmon, and open the Disk tab.
  2. Expand Disk Activity and sort by Write (B/sec).
  3. Look for NVDisplay.Container.exe and check whether its file path matches nvlog.nvlgstg.
  4. Observe the PC while it is otherwise idle, rather than during an update, game download, or backup.
  5. Repeat the observation to distinguish persistent logging from a short startup burst.
For a second measurement, record Host Writes or Data Units Written using your SSD manufacturer's utility or CrystalDiskInfo. Leave the machine idle for a consistent interval, such as an hour, and check again. Keep the measurement conditions similar and note other background activity.

Resource Monitor helps identify the responsible process; the SSD counter helps establish the broader drive-level impact. Neither measurement alone tells you exactly how much lifespan has been lost.

Rolling back can introduce a different problem

Driver 621.01 appears in the source as a version with lower logging activity in one user's comparison. That does not make it a universal recommendation.

Windows Latest reports that Nvidia documented video playback freezes or black screens affecting some RTX 50 GPUs and RTX Spark systems with 621.01. The reported fix arrived in hotfix 621.12 and subsequently in 621.14. Returning to 621.01 could therefore trade background writes for a visible stability problem on affected hardware.

The publication had not found a test establishing whether 621.12 avoids the logging issue. Treating that hotfix as a confirmed solution would go beyond the available evidence.

If your PC is unaffected, there is little reason to roll back solely because of this report. If excessive writes are confirmed, review Nvidia's current release notes and use an official, hardware-compatible driver package. Keep a known-working installer available, and test video playback as well as gaming after any change.

Avoid turning temporary workarounds into permanent fixes

The source describes a user stopping Display Container, deleting the log, and restarting the service. That reduced writes temporarily, but the file grew again. It also describes repeated clean installations with DDU that did not solve another user's problem.

Those reports do not support routine log-deletion scripts or repeated driver removal as reliable remedies. Permanently disabling the service can also disrupt Nvidia management features, including access to the Control Panel and Nvidia App, according to Windows Latest.

For managed PCs, collect the driver version, GPU model, log path, and before-and-after measurements before escalating. Test any replacement driver on a small group rather than changing an entire fleet based on an unconfirmed workaround.

The sensible priority is diagnosis, not panic: confirm persistent activity, check drive-level writes, and choose a mitigation that does not sacrifice system stability. Maintain normal backups, but do not interpret the report alone as evidence that your SSD needs replacement.

Source: Windows Latest report by Abhijith M B