Urgent.News

What's breaking now, across hundreds of outlets.

AI

I built the same website twice with Claude Code, and one free design skill made all the difference

A tale of two websites (and one very useful skill)

I built the same website twice with Claude Code, and one free design skill made all the difference

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.

All 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.

Gemini 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.

Claude 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.

In 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.

Rewritten by urgent.news; may contain errors — check the original.

Source: xda-developers.com

Other reports of this story

Every outlet that reported this, and when →

Read the original at xda-developers.com →

Report a problem with this story

More in AI

Beyond Chatbots: Building an Observable Multi-Agent Study Coach with Gemini, Google ADK & Docker

Build. Learn. Evaluate. Observe. What if an AI study assistant could do more than answer questions? What if it could generate a personalized certification study plan, explain technical concepts using…

  • Study Coach combines Gemini, Google ADK, and Docker for multi-agent AI workshop
  • Components include Study Planner, Topic Expert, Quiz Generator, and Document Agents
  • Local deployment with Python, Streamlit, Docker, and observability services

More from Sunday 22 November →