{
  "id": 20832118,
  "title": "New Nvidia bug is killing SSDs — is it “AI code incompetence,” users ask?",
  "url": "https://urgent.news/2026/11/20/new-nvidia-bug-is-killing-ssds-is-it-ai-code-incompetence-users-ask",
  "topic": "culture",
  "section": "Culture",
  "published": "2026-11-20T00:04:18.000Z",
  "source": {
    "name": "Tom's Guide",
    "slug": "tom-s-guide",
    "url": "https://www.tomsguide.com/computing/hardware/new-nvidia-bug-is-killing-ssds-is-it-ai-code-incompetence-users-ask"
  },
  "original_language": "en",
  "account": "A newly discovered bug in Nvidia's latest GPU driver updates has sparked concerns that it might be causing SSDs to deteriorate faster than they should, leading to performance issues such as stuttering and mouse lag. TroubleGrid reported that the bug, present in updates 621.14 and 621.24 of the Nvidia GeForce Game Ready Driver, forces NVDisplay.Container.exe to write excessive amounts of data to an Nvidia log file, causing it to grow as much as 30GB per hour. This rapid growth in log file size can degrade the SSD's performance, resulting in longer degradation times than usual. Conspiracy theories suggest that Nvidia may be intentionally causing SSD damage to force customers to buy new ones, while others blame AI-written code for the issue. CEO Jensen Huang previously advocated for more AI-generated code in Nvidia's development process. The easiest way to avoid the bug is to roll back the graphics card driver to version 621.01, the last known patch without the issue. However, this will disable certain Nvidia features, such as G-Sync, color settings, and display scaling.",
  "summary": "A newly discovered Nvidia driver bug is prematurely killing SSDs by writing excessive information on them.",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}