Nvidia recent GeForce driver updates may lead to over-intensive background writes that can cause solid-state drives to degrade quicker. It’s caused by a specific display service updating the log files endlessly in the background when the system is idle. The big issue is the amount of data written to the drive might be too much to the point it can be detrimental to the lifetime of consumer SSDs. Let’s examine how the intensive background activity affects the storage’s endurance and performance of the system.
Users trace massive idle wear to background service
Nvidia’s driver updates (621.14 and 621.24) that came out on November 4th, 2024 are causing this issue. The cause of the issue is linked to the NVDisplay.Container.exe (or NVIDIA Display Container LS) which is the service that’s constantly writing to the binary log file (nvlog.nvlgstg). User Andergraude mentions it’s the driver endlessly overwriting the log (real writes on the drive).
Up to 30GB/hr writes are estimated in the 621.24 driver. Another user, AyzekUorren, claims it’s around 30GB/hr or even 70GB if you do it for a longer time. Other testing has revealed it’s around 3GB/hr.
I/O process was 515MB for 5 mins. These numbers increase as the log file grows in size. You can temporarily lower these writes by stopping the service and deleting the log file.
This over-intense writing also affects gaming and video performance when under a load. Users mentioned that it might cause hitching while playing games. So it looks like the problem gets worse when you’re using the system.
It’s not clear what data the service is actually writing to the log. Not all systems seem to have this bug. As a solution, you can revert back to driver 621.01. This should give users stability.
There’s no mention about this bug from Nvidia. Nor do they have a fix for this problem. The open issues section under their driver page is listed N/A for version 621.24.
Recall that we covered NVIDIA GeForce Game Ready Driver 621.01. The driver had some optimizations like Call of Duty: Modern Warfare 4. Now we have a regression with recent driver updates that forces users to take action to mitigate it.



Comments (0)