Nvidia GeForce Drivers Writing Up to 30GB Per Hour to SSDs, Users Report
Up to 30GB of needless data per hour, written to a solid-state drive by a graphics driver doing nothing at all.
That is what users are reporting against Nvidia’s GeForce drivers — and the company has yet to respond. The problem surfaced days after AMD patched a strikingly similar bug of its own.
The culprit, according to a user posting on the official Nvidia forum, is the Nvidia Display Container LS service, Tweakers reported. Instead of appending to a log file called nvlog.nvlgstg, the service supposedly keeps emptying and rewriting it — so the wear grows worse as the file swells.
The user, Andergraude, traced the bug back to driver version 621.14. With no system activity, he measured 515MB hitting the SSD every five minutes. Another forum user reported that version 621.24 averaged 30GB per hour.
There is a workaround. Andergraude found that stopping the Nvidia Display Container LS service, deleting the log file and restarting the service cut SSD write activity by about 91 percent, Tweakers reported. Version 621.01 does not show the bug, so users on older drivers are unaffected.
“Werkt perfect. Thanks.”
said forum user CriticalHit_NL, who shared a workaround in Tweakers’ Nvidia news discussion thread
The timing is what pushes this beyond one forum thread. On November 12, AMD patched its own driver line, Adrenalin 26.11.1, fixing a similar excessive-write flaw it acknowledged had existed for at least a year. Two GPU makers logging the same class of defect within the same month has put both driver stacks under closer scrutiny.
Reactions on Tweakers ranged from relief to suspicion. One user checked his installation and found version 616.92 of the Studio driver untouched. Another, running 617.42 Studio, reported no excessive writes either. Others said they would hold off updating until Nvidia ships a fix — a habit one commenter endorsed, saying he stalls behind the newest driver release on purpose.
The scale matters. Consumer SSDs are rated in terabytes written over a lifespan, and a driver burning tens of gigabytes per idle hour can chew through that budget without the owner ever launching a game.
Whether the two bugs share a root cause is unknown. Forum commenters joked that the same large language model might have written both codebases, and that users only went looking because AMD’s flaw had already made headlines. Neither theory has any confirmation from either company.
Nvidia was founded on April 5, 1993, by Jensen Huang, Chris Malachowsky and Curtis Priem, who sketched out their first ideas in a meeting at a Denny’s diner in San Jose, California. Of some 70 startups from that era pursuing graphics acceleration for video games, only two survived: Nvidia and ATI Technologies, the latter of which later merged into AMD — the company whose driver bug drew attention to the current flaw.
In late 1999, Nvidia released the GeForce 256, its first product marketed as a graphics processing unit, the same GeForce line at the center of the present reports. In 2025, the company became the first to surpass US$4 trillion and US$5 trillion in market capitalization.
For now, the verified facts are narrow. Nvidia has not commented. The bug appears to date to version 621.14. A user-documented workaround cuts the writes by roughly 91 percent. And AMD, which faced the same scrutiny a week earlier, resolved its version of the problem on November 12 in Adrenalin 26.11.1.