Friday, November 20th 2026

NVIDIA's SSD Write Bug Gets Patched in GeForce Hotfix 621.35 Driver

NVIDIA today has released the GeForce Hotfix 621.35 driver to fix the bug that was hammering SSDs while idle. There is only one fix in the release: "Excessive writes to file nvlog.nvlgstg may occur in the background," and that was all that was needed on an urgent basis. We reported the issue of constant and excessive SSD writes that was spotted by several NVIDIA users earlier this week, particularly on drivers 621.14 and 621.24. The NVDisplayContainer.exe process kept rewriting even on PCs that were just sitting idle, and the nvlog file was at the center of that bug. In some extreme cases, the idle writes were up to 30 GB per hour, while the older 621.01 driver only logged around 2 MB per 5-minute idle window.

The hotfix is built on NVIDIA's latest Game Ready driver, which is currently the 621.24 release from November 12. This is an optional download, of course, as it goes through a shortened QA process and is only offered through the NVIDIA Customer Care site. Previous fixes for the SSD write bug included rolling back to 621.01 and a temporary fix that included stopping the NVIDIA Display Container LS service. Anyone who was affected by this issue is advised to grab the hotfix as soon as possible, while others can wait for the next WHQL release. Curiously, AMD also suffered from a similar SSD write bug just a few days before NVIDIA's, and it too released optional Adrenalin drivers to patch it quickly.
Sources: NVIDIA, NVIDIA Customer Care
Add your own comment

10 Comments on NVIDIA's SSD Write Bug Gets Patched in GeForce Hotfix 621.35 Driver

#1
SiliconSeraph
Geez, that was actually pretty quick.

Sure, it should never have been an issue in the first place, but still, good diligence from Nvidia
Posted on Reply
#2
Fatloader
What’s with all the quick polls recently? Not saying they’re bad, just a bit curious.
Posted on Reply
#3
Solaris17
Super Dainty Moderator
Technology and process moves forward and things like this become a way of life, and while even coding languages had limitations and thus things like we have today couldnt really exist, you have to wonder how much of it is just new blood that doesnt think through the same lens as the older programmers.

When I started to learn you had to understand the HW side almost just as much, now its all abstracted away from your average developer.

You sure wouldnt see a delay in patching or even the bug to begin with if you were writing 30GB/hr to a 80GB WD Blue IDE drive. You would hear your mistake at around the same time you noticed your system lock up.
Posted on Reply
#4
Inferna
Remind me how much time it took AMD to acknowledge the issue then start fixing it ?
Posted on Reply
#5
freeagent
SiliconSeraphGeez, that was actually pretty quick.
You pay for it :laugh:
Posted on Reply
#6
Hecate91
Nice to see this fixed quickly, though I'd expect this to not happen in the first place with Nvidia especially if you're paying more for it.
Posted on Reply
#7
dewd
how can anyone not think this is intentional to maybe drive ssd sales? "if theyre going broke buying new ssds they cant bitch about ram or gpus"
Posted on Reply
#8
john_
InfernaRemind me how much time it took AMD to acknowledge the issue then start fixing it ?
At Nvidia's headquarters:

Engineer 1: AHAHAHAHA!!!!
Engineer 2: What?
Engineer 1: AMD's drivers are writing 500KBs/sec constantly on the drive and people are laughing at them again.
Engineer 2: Uh-oh....
Engineer 1: Isn't it funny?
Engineer 2: Oh boy.....
Engineer 1: What? ....wait..... we didn't.....Did we?
Engineer 2: .......
Engineer 1: We did. How much?
Engineer 2: Well, a couple MBs/sec.
Engineer 1: Oh boy..... Let's fix it. I read about a quick fix for the AMD drivers, maybe we can start from there.
Engineer 2: At least they haven't found yet. We might fix the drivers before they realize, or at least we will be faster than AMD.
Engineer 1: Yeah, right, yeah, that's good, it's fine, everything is fine. Well, not really with the CEO and stuff, but it's fine. Maybe no one will notice now that everyone is occupied with that thing.


That's why Nvidia fixed that faster. And while the above is an imaginary dialog, you bet someone was looking at the Nvidia drivers when the news about AMD drivers got out.
Hecate91Nice to see this fixed quickly, though I'd expect this to not happen in the first place with Nvidia especially if you're paying more for it.
It was writing more MBs/sec, I don't understand you. More than AMD's drivers. MORE. :p
Posted on Reply
#9
Hecate91
john_It was writing more MBs/sec, I don't understand you. More than AMD's drivers. MORE. :p
Yeah that's the important thing,AMD drivers were writing anything from 500kb/s to 5MB/s at worst from reports I've seen, and apparently you were less likely to be affected updating from the Adrenalin panel.
But regardless of Nvidia drivers getting fixed faster it was writing up to 30GB per hour. It's some amazing irony everyone laughed at AMD drivers yet Nvidia's AI vibe coding one upped them on how much worse it could've been.
Posted on Reply
#10
Rulumi
InfernaRemind me how much time it took AMD to acknowledge the issue then start fixing it ?
4 weeks to acknowledge and have a private fix done, 6 weeks to release a hotfix for RDNA 3 and RDNA 4 because of the outrage in news oulets. 7 weeks to release the fix for RDNA 1 and RDNA 2, and that was also the original planned date to publish the fix for RDNA 3 and RDNA 4 to the public before the news headline started making noise.
Posted on Reply
Nov 20th, 2026 20:42 PST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts