Claude Code Auto-Update Nearly Bricks PC — DNS Nightmare After Driver Update
A developer on r/ClaudeAI recounts a harrowing experience after asking Claude Code to help with a GPU performance issue (GPU running at 70% power). The AI decided to automatically update the drivers, leading to a cascade of failures that took over 24 hours to resolve.
What Happened
- PC crashed and wouldn't boot
- Required System Restore to recover
- WiFi connected but had no internet
- DNS requests were all being routed to
10.2.0.1— a dead Mullvad VPN server — due to an NRPT registry entry restored by System Restore
Steps Taken (Failed)
- System Restore, Winsock reset, TCP/IP reset, DNS changes, full Windows Network Reset
- Driver reinstallation, uninstalling Mullvad, removing WireGuard adapter
What Finally Fixed It
Wireshark revealed all DNS traffic was going to 10.2.0.1 instead of the router. Running this PowerShell command resolved the issue:
Get-DnsClientNrptRule | Remove-DnsClientNrptRule -ForceKey Lesson
AI tools have no way to test driver compatibility before installing. Drivers break things at a system level that can be extremely difficult to recover from. Always update drivers manually from the manufacturer's website, verify release notes, and only update with a specific reason.
Specs
- Motherboard: MSI PRO B840-VC WIFI
- WiFi card: MediaTek Wi-Fi 7 MT7925
- OS: Windows 11 25H2
This is a strong cautionary tale: don't let Claude Code auto-update drivers.
📖 Read the full source: r/ClaudeAI
👀 See Also
KV Cache Quantization Issues in Local Coding Agents at High Context Lengths
A Reddit analysis identifies aggressive KV cache quantization as the cause of infinite correction loops and malformed JSON outputs in local coding agents like Qwen3-Coder and GLM 4.7 at 30k+ context lengths, recommending mixed precision or reduced context as workarounds.
The Blind Spots in Claude Code Workflow Posts: Recovery, Constraints, and Permission Management
Happy-path Claude Code workflows are common, but they miss recovery from bad edits, constraint enforcement, and permission management—critical for real-world use.
MTP Acceptance Rate: 50% Threshold Determines Speculative Decoding Benefit
MTP (Multi-Token Prediction) via speculative decoding on Gemma-4 26B shows benefit only when draft token acceptance rate exceeds 50% — based on mlx-vlm benchmarks on M4 Max Studio.
Claude Code token audit reveals hidden costs from default tool loading
A developer analyzed 926 Claude Code sessions and found 45,000 tokens loaded at session start, with 20,000 tokens coming from system tool schema definitions. Enabling the ENABLE_TOOL_SEARCH setting reduced starting context from 45k to 20k tokens, saving 14,000 tokens per turn.