If your SSD stays busy after you close a game, open Windows Resource Monitor and look for NVDisplay.Container.exe writing repeatedly to nvlog.nvlgstg. That specific pattern is the reason to consider NVIDIA’s GeForce 621.35 hotfix. The same file gives you a way to check whether the update worked on your PC.
Check which file NVIDIA is writing
On 20 November 2026, NVIDIA released 621.35 for a background logging issue tracked as 7116722. GeForce users had reported the symptom on 621.14 and 621.24. If you already have one of those versions installed, take a short reading before updating.
- Open NVIDIA Control Panel. Under Help, choose System Information and note your GPU and driver version.
- Close your game, let downloads and updates finish, and note how long the PC has been running. Leave the NVIDIA services and log file alone during the check.
- Press Windows key + R, type resmon and press Enter. On the Disk tab, expand Processes with Disk Activity. Click Write (B/sec) to bring the busiest writers to the top.
- Tick NVDisplay.Container.exe if it appears. In Disk Activity below, look in the File column for a path ending in nvtopps\\nct\\nvlog.nvlgstg. Check the Write (B/sec) value on that file’s row.
- Watch for five minutes at the idle desktop. Record the approximate write rate and whether the row stays active, appears in bursts or disappears. A screenshot showing the process, file and rate makes a useful comparison later.
If a different file accounts for the writes, clear the process filter and follow the busiest file row. For example, if you find atieclxx.exe on a PC with Radeon graphics, there is a separate check for that AMD process.
AMD Radeon SSD Writes at Idle: How to Check atieclxx.exe
Compare 621.24 and 621.35 at idle
If the log keeps receiving writes, the 621.35 hotfix is available through NVIDIA Customer Care for compatible GeForce PCs running 64-bit Windows 10 or 11. It is an optional beta driver with a shorter testing cycle than a WHQL-certified release. If the symptom is absent and you prefer the normal release cycle, look for issue 7116722 in the notes for a later certified driver.
Get GeForce Hotfix Driver 621.35 from NVIDIA
After installing the package, restart and confirm 621.35 in System Information. Open Resource Monitor again. Use the same five-minute window, apps and idle conditions as your baseline. If the original writes appeared only after a few hours or after the display woke, repeat the check at that point too.
| What you see on 621.35 | What it tells you |
|---|---|
| The same log was busy on 621.24 and stays quiet during the matched retest | The repeated writes cleared during this check. Keep the two readings together. |
| The log still receives repeated writes under the original conditions | Save the GPU, both driver versions, uptime, file path and write-rate readings for NVIDIA support. |
| The log goes quiet but the drive stays busy | Untick the NVIDIA process and sort Disk Activity by Write (B/sec) to identify the next writer. |
What the numbers say about your SSD
The file row identifies where Windows sees activity. A process’s I/O write counter totals its write activity, and Windows can hold file changes in memory before sending them to disk. Multiplying a momentary write rate by 24 hours cannot tell you how much data reached the SSD in a day.
For a drive-level check, use your SSD utility if it shows the NVMe SMART counter called Data Units Written or Total Host Writes. Record the value for the drive containing the log at the start and end of each idle window, excluding the driver installation. Subtract the starting value from the ending value in the same units. That change covers writes from every process reaching the controller. A utility that rounds to whole gigabytes may show the same number twice during a short check.
SSD wear is a separate question. The NVMe Percentage Used field is the manufacturer’s estimate for the drive as a whole. Neither it nor the host-write total identifies how much flash wear one NVIDIA process caused.
FAQ
Keep the hotfix installed. Confirm the version in NVIDIA Control Panel and look for repeated writes to the log under the conditions that concerned you. A quiet check tells you what the PC is doing now. Measuring the size of a change would require a comparable earlier reading.
Yes. A program can rewrite existing content while the file stays much the same size. Watch the file’s Write (B/sec) column over time to see whether the NVIDIA process keeps writing to it.
Leave the service running and keep the log in place for the comparison. Removing the file or stopping the writer changes the condition you are trying to observe. If an earlier workaround is still active, record it alongside the driver version. A quiet log under that workaround cannot tell you whether the driver fixed it.




