Nvidia released GeForce Hotfix Display Driver 621.35 on November 20, 2026, to stop a bug in its recent Game Ready drivers that could keep writing to a PC's system SSD in the background, even while the machine sat idle. The problem traced back to driver 621.14 and carried into 621.24, the current WHQL release. It arrived about a week after AMD shipped its own fix for a very similar Radeon driver bug. Both issues are now patched, but the fixes are not identical in how they are delivered, and anyone who changed system settings as a workaround has a few things to undo.
What Went Wrong With the GeForce Drivers
The bug lives in the NVIDIA Display Container LS service, which runs on Windows as the process NVDisplay.Container.exe. This service supports the NVIDIA Control Panel and the NVIDIA App. On affected systems, it repeatedly wrote a binary log file called nvlog.nvlgstg, stored in a folder under ProgramData\NVIDIA Corporation, to the system drive.
According to reporting by igor'sLAB and HotHardware, the service did not simply add new lines to the end of the log. It rewrote parts of the file over and over. That detail explains why the file itself could stay fairly small while the amount of data physically written to the SSD kept climbing. File size alone was never a reliable way to spot the problem.
Users traced the regression to GeForce 621.14, released on November 4. Nvidia's next Game Ready driver, 621.24, arrived on November 12 with support for Warhammer 40,000: Dawn of War IV and Assetto Corsa Rally and DLSS 5 for Where Winds Meet, but it carried the same behavior. The older 621.01 driver did not show it.
How Much Data Was Being Written
The numbers vary widely from PC to PC, and the most extreme figures come from individual user reports rather than controlled testing. Here is what has been reported:
Two caveats matter here. First, Windows process counters measure all I/O a process requests, which is not always the same as what reaches the SSD's flash memory. In the same five-minute test that logged 515 MB of process I/O, the drive's own counters recorded about 270 MB of actual writes, as igor'sLAB noted. Second, the bug did not affect every system. Several users on the same driver versions reported normal write activity.
Does This Damage Your SSD?
Not immediately, and not catastrophically for most people. SSDs are rated for a total amount of data they can absorb over their life, measured in terabytes written (TBW). A typical 1 TB consumer drive is rated somewhere around 600 TBW.
To put the worst reported case in perspective, take the 30 GB per hour figure and assume a PC that runs eight hours a day. That works out to about 240 GB a day, or roughly 88 TB a year, which is about 15% of a 600 TBW rating every year. Sustained for months, that is real, avoidable wear. On a system writing a few hundred megabytes every few minutes, the impact is far smaller. And for PCs that were never affected, the impact is zero.
The practical takeaway is simple: this was worth fixing quickly, but a few days or weeks on an affected driver is very unlikely to have killed anyone's SSD. Drives also report their own total host writes in their SMART data, so anyone worried can check how much has actually been written over the drive's lifetime using the manufacturer's SSD utility or a free tool such as CrystalDiskInfo.
Nvidia's Fix: GeForce Hotfix 621.35
Nvidia's Hotfix 621.35 support page lists exactly one change:
- "Excessive writes to file nvlog.nvlgstg may occur in background" (internal bug 7116722)
Hotfix drivers come with clear conditions. Nvidia describes them as beta, optional and provided as-is, run through "a much abbreviated QA process." The company's own advice is that the safest option is to wait for the next WHQL-certified driver, and it states that the fixes will be rolled into that next official release, at which point the hotfix page is taken down.
Should You Install the Hotfix?
That depends on whether your PC is affected:
- If NVDisplay.Container.exe is constantly writing on your system, the hotfix is the cleanest fix available right now. It keeps the 621.24 features and game support while removing the bug.
- If your system shows normal write activity, there is little reason to install a beta driver. Waiting for the next WHQL Game Ready driver is the lower-risk path.
- If you rolled back to 621.01 as a workaround, the hotfix lets you return to current game support without the excessive writes.
How to Check Whether Your PC Is Affected
There are two easy ways to check on Windows. Both work best on an idle PC with games and launchers closed.
Method 1: Resource Monitor
This approach was laid out by HotHardware:
- Press Win + R, type resmon and press Enter.
- Open the Disk tab.
- In "Processes with Disk Activity," sort by the Write (B/sec) column.
- Look for NVDisplay.Container.exe. If it stays near the top and keeps writing while the PC is idle, the system is affected.
Method 2: PowerShell
Notebookcheck highlighted a PowerShell command shared by a Reddit user that reports how much the process has read and written since it last started. Run it in PowerShell:
`Get-CimInstance Win32_Process -Filter "Name='NVDisplay.Container.exe'" | Select-Object ProcessId, @{N='Read_MB';E={[math]::Round($_.ReadTransferCount/1MB,1)}}, @{N='Write_MB';E={[math]::Round($_.WriteTransferCount/1MB,1)}}`
The totals are cumulative, so run it twice a few minutes apart on an idle PC and compare the Write_MB values. A jump of hundreds of megabytes in a few minutes points to the bug. A change of a megabyte or two is normal.
Workarounds to Undo After Updating
Before the hotfix, affected users had a handful of stopgaps, each with drawbacks:
- Rolling back to 621.01. This removed the bug for affected users but brought back older issues. Notebookcheck notes this includes video playback freezes and black screens on some RTX 50 series GPUs, and it also means losing the newer Game Ready optimizations.
- Stopping the service and deleting the log file. This helped only temporarily, because the file was recreated and the writes resumed.
- Disabling the NVIDIA Display Container LS service or setting it to Manual. This stops the writes but, as HotHardware points out, the NVIDIA Control Panel and NVIDIA App depend on it, and disabling it also breaks G-SYNC.
The AMD Side: A Very Similar Radeon Bug
The Nvidia bug surfaced just after AMD dealt with its own version of the same problem. AMD confirmed in early November that Adrenalin 26.10.1 and 26.10.2 could cause excessive SSD writes. The culprit there was atieclxx.exe, the AMD External Events Client Module, part of the utility that handles tasks like monitor detection and Radeon Software hotkeys. Reported write rates ranged from about 0.3 MB/s to 1.5 MB/s, with one report of 5 MB/s. At the top end, that is more than 400 GB a day on a PC doing nothing.
AMD fixed it in two steps:
AMD's support article on the SSD write issue now lists the problem as resolved and recommends that affected Radeon RX 7000 and RX 9000 users install Adrenalin 26.11.1 or later.
Radeon Settings to Restore
AMD users who worked around the bug before the fix had two common options: disabling the AMD External Events Utility or turning off Resizable BAR (which AMD brands as Smart Access Memory). Both have costs. Disabling the utility can cause display issues, and turning off Resizable BAR can reduce performance in some games.
There is one more wrinkle on Windows 10. The 26.11.1 release notes list a known issue where Smart Access Memory may become disabled after driver installation on Windows 10, which the 26.11.2 release notes mark as fixed. Either way, after updating it is worth opening AMD Software and confirming Smart Access Memory is on, and checking the motherboard BIOS if Resizable BAR was disabled there.
Version choice matters slightly for some Radeon owners. Adrenalin 26.11.2 lists a known issue where Crimson Desert may fail to launch on RX 6000 series cards, and AMD recommends 26.11.1 for anyone affected. On the other hand, 26.11.2 adds support for Phantom Blade Zero and the Crimson Desert Enhanced: Charting the Unknown DLC, and fixes a memory leak that made applications launch progressively slower on RX 5000 cards and newer. AMD recommends using its Cleanup Utility when downgrading to an earlier Adrenalin version.
Why Both Bugs Matter for PC Players
Neither bug caused crashes, frame drops or visible errors, which is exactly why they went unnoticed by many users. Background writes do not show up in games, and most people never open Resource Monitor. Both problems were discovered by users measuring disk activity and sharing results, then picked up by hardware sites before the GPU makers responded.
Response times differed. AMD acknowledged its issue publicly and named the driver version that would fix it before release. Nvidia's fix arrived 16 days after 621.14 shipped, though only days after the reports gained wide attention. Both companies did ship fixes within weeks.
For PC players, the lessons are practical:
- Check new drivers occasionally. A quick look at disk activity in Resource Monitor after a major driver update takes less than a minute.
- Treat hotfix drivers as targeted tools. Install them when they fix a problem you actually have, and move back to the WHQL track when the next release lands.
- Write down any workaround you apply. Services set to Manual and features turned off in the BIOS are easy to forget, and they can cost performance or features long after the original bug is fixed.
Frequently Asked Questions
What is GeForce Hotfix driver 621.35?
GeForce Hotfix 621.35 is an optional beta driver Nvidia released on November 20, 2026. It is based on Game Ready driver 621.24 and contains a single fix for excessive background writes to the nvlog.nvlgstg file. It is available for Windows 10 and Windows 11 from Nvidia's Customer Care site.
Which Nvidia drivers have the SSD write bug?
Reports trace the problem to GeForce 621.14, released on November 4, and Game Ready 621.24, released on November 12. Driver 621.01 did not show the behavior. Not every system running 621.14 or 621.24 was affected.
What is NVDisplay.Container.exe?
NVDisplay.Container.exe is the process behind the NVIDIA Display Container LS service. It supports the NVIDIA Control Panel and the NVIDIA App. In the affected drivers it repeatedly rewrote a log file on the system drive, which caused the excessive writes.
Is it safe to disable the NVIDIA Display Container service?
Disabling it stops the writes, but it also prevents the NVIDIA Control Panel and NVIDIA App from working and breaks G-SYNC. With Hotfix 621.35 available, it is better to install the hotfix and leave the service set to Automatic.
Did the bug damage my SSD?
For most users, no meaningful damage is likely. Even the worst reported rate of 30 GB per hour would use roughly 15% of a typical 1 TB drive's rated endurance per year at eight hours a day. You can check your drive's total host writes in its SMART data with the manufacturer's utility or CrystalDiskInfo.
Should I install the hotfix or wait for the next driver?
Install 621.35 if Resource Monitor or PowerShell shows NVDisplay.Container.exe writing heavily while your PC is idle. If your system looks normal, Nvidia's own guidance is that waiting for the next WHQL-certified driver is the safest option, and that driver will include the fix.
Which AMD driver fixes the Radeon SSD write bug?
Adrenalin 26.11.1, released November 12, fixed the idle write issue on Radeon RX 7000 series cards and newer, plus a related issue while moving or resizing windows. Adrenalin 26.11.2, released November 18, extended the fix to RX 5000 and RX 6000 series cards on Windows 10.
Do I need to re-enable Smart Access Memory after updating my AMD driver?
If you turned off Resizable BAR or Smart Access Memory as a workaround, yes. Also check it after updating on Windows 10, because AMD listed an issue in 26.11.1 where Smart Access Memory could become disabled after installation, later fixed in 26.11.2.



