{
  "id": 21267954,
  "title": "I asked ChatGPT, Claude and Gemini what was killing my SSD, and only gave me a fix I'd trust",
  "url": "https://urgent.news/2026/11/22/i-asked-chatgpt-claude-and-gemini-what-was-killing-my-ssd-and-only",
  "topic": "ai",
  "section": "AI",
  "published": "2026-11-22T19:00:20.000Z",
  "source": {
    "name": "XDA Developers",
    "slug": "xda-developers",
    "url": "https://www.xda-developers.com/i-asked-chatgpt-claude-and-gemini-what-was-wearing-out-my-ssd-and-only-one-found-it/"
  },
  "original_language": "en",
  "account": "A few days ago, the author tested three chatbots – Gemini, Claude, and ChatGPT – to determine how each would help diagnose a slow SSD. The author provided the chatbots with the same vague description of a symptom: their SSD was wearing out faster than it should, with CrystalDiskInfo showing a sudden increase in total writes.\n\nAll three models began their investigation with Resource Monitor, excluding Nvidia's NVDisplay.Container.exe from their initial suggestions. ChatGPT was the best at the start, but its suggestions were largely unhelpful, as it asked the user to meticulously track write counts and log file sizes, which would not stop the process. The author was left without a permanent fix.\n\nGemini started with Resource Monitor as well, but it asked the user to sort by writes instead of total disk activity. It then correctly identified the NVDisplay.Container.exe and its log file, and provided the usual workaround of stopping the NVIDIA Display Container LS service, clearing the nvtopps folder, and restarting it. However, when asked for a permanent fix, Gemini suggested that a driver update would cause the writes to return, and recommended locking the nvtopps folder, which the author found counterproductive.\n\nClaude followed a similar path as Gemini, but it was the only model to ask for the user's driver version. It correctly identified the NVDisplay.Container.exe from the process list and suspected the Nvidia overlay, which did not help in this case. When asked for a permanent fix, Claude performed a web search and provided the tried and tested workaround of stopping the NVIDIA Display Container LS service, deleting the nvlog.nvlgstg file, and restarting the service. Claude also suggested rolling back to driver version 621.01, which would fix the issue, but it missed the permanent fix – Nvidia's 621.35 hotfix released a day earlier.\n\nIn conclusion, while all three models quickly identified the problematic process, only Claude performed a thorough web search and provided the permanent fix. The author concludes that relying solely on chatbots for troubleshooting SSD issues can be misleading, and users should usually turn to search engines for a more reliable solution.",
  "summary": "All three knew it was Nvidia, only one knew how to clean up its mess",
  "key_points": [
    "ChatGPT, Claude, and Gemini diagnosed SSD wear using Resource Monitor",
    "Gemini identified NVDisplay.Container.exe and provided service stopping workaround",
    "Claude performed web search, offering permanent fix with Nvidia driver hotfix"
  ],
  "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."
}