Nvidia rolled out a hotfix driver on the 20th of November to prevent a bug that was eating your ssd storage. If you are a user of GeForce Gpu's then this is important. The reason being is this bug was overwriting data on your storage and it could potentially shorten the life span of your storage drive. Maybe you've seen your health go down for no reason on your storage if you've been using some of the recent drivers.
Hotfix 621.35 stops excessive background writes
It all started with the GeForce Game Ready Driver 621.14 on the 4th of November. It continued up until the 621.24 driver that came out on the 12th of November. The bug stemmed from a process called NVDisplay.Container.exe and it was running as the NVIDIA Display Container LS service. It was over writing a binary log file, nvlog.nvlgstg, over and over and over again on the windows drive.
- Bug ID: 7116722
- Affected Process: NVDisplay.Container.exe
- Affected File: nvlog.nvlgstg
- Reported Write Rate: up to 30 GB per hour
The bug was logged on Nvidia as bug 7116722. Users were seeing this loop attacking their SSD's with up to 30gb/hr writes. That's enough to potentially eat up 15% of your endurance on your 1tb storage in just one year.
This is why Nvidia rolled out the GeForce Hotfix Display Driver 621.35. To prevent all of the background writing happening.
As you can see the hotfix driver only shows one fix. 'Excessive writes to file nvlog.nvlgstg may occur in background.' We mentioned some of the Nvidia Game Ready Driver 621.01 cuts in our past coverage of Nvidia. As you can see this is a trend with their driver changes. But the actual physical damage to nand flash isn't as bad as the process counts show. Not everything that is counted in windows processes actually makes it to the nand flash.
A similar problem happened with AMD radeon drivers. This was fixed in Adrenalin 26.11.1. We've got Nvidia addressing it and giving us a patch for it. So if you've experienced this make sure you get v621.35 so that you don't see all of these log file activities going on.
Source: NotebookCheck




NVDisplay.Container.exe looping writes is a classic driver leak. Windows process counters inflate the number because of caching and retries. The actual NAND wear is likely lower than 30 GB per hour.