I guess 610.88 will have to hack it for a while longer. Glad I didn’t update.
It sounds like both companies use the same AI model to update their drivers. 🤣
At this point I’ve got to really wonder if the AI/memory cartels are actively sabotaging our machines to drive up prices.
for the amd case, it was a legit defect/oversight regarding the abrupt removal of the pcie filter driver
A non-disk driver running disk operations doesn’t sound like a good idea
Logging events to a file doesn’t seem extremely out of the ordinary, especially for a helper program. It’s the inefficiency of the process which is the issue here.
If anybody is wondering, the article says it can happen with driver version 621.14 to 621.24.
Article is all about Windows; is Linux impacted?
Almost never but you can run iotop to see disk activity.
If the billy goats can’t physically get to the hardware we have at home, they’ll throw “bugs” at us to kill it remotely.
Half of us (or more) can’t afford to rebuy at their artificially inflated prices. So, we’ll get Chromebooks and cloud services.
Eventually I figure we will be down to running various steam-link-like apps on devices that have just enough power to render video, connect to whatever version of the internet we are left with, and Bluetooth.
Cunts.
My thoughts as well. “Ooops we accidentally pushed a driver that killed your SSD, our bad!”
If I remember right, that quite literally happened.
Some specific M.2 drives that had a specific type of module SkHynix or Samsung of whatever revision were affected.
I think the drive didn’t outright die but it wouldn’t boot from it anymore? Something like that? It wasn’t catastrophic to a power user but to a normal person it definitely was.
It was about 1-2 years ago I think.
30 GB per hour is quite a bit, damn
Wonder if AMD and NVIDIA using Claude is why both encountered the same issues not too far apart on Windows with things increasingly relying on the same source for advice. Which is also why both seem to be fine in the writing department on Linux due to Claude or whatever AI agent used didn’t suggest things that would lead to issues.
I wonder if this could be exploited to mass infect corporations as code stops being written and more and more trust is put into having AI do everything. And even QA is probably being trusted to AI.
this one for amd wasn’t introduced by a code change, rather than a packaging change which wasn’t properly evaluated after.
I don’t think there has ever been an internal test case monitoring disk r/w. I hope one was made in light of all of this
Good thing I haven’t updated my drivers in forever










