[BUG] Windows: fatal GPU process crash (exitCode 101457950) during Claude Code sessions kills entire app; MSIX package requires Repair to relaunch

Status Closed — duplicate
Reported on v2.1.229
Maintainer reply None cached
Activity 1 comment · opened Aug 16, 2026 · closed Aug 20, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Environment

  • Claude Desktop app 1.30096.5 (MSIX / Microsoft Store install, package Claude_pzs8sxrjxfjjc), Claude Code Desktop 2.1.229, bundled Node 24.18.0
  • Windows 11 build 26200, 16 GB RAM
  • GPU: AMD Radeon(TM) integrated graphics (Ryzen APU), driver 31.0.21924.61

What happens

Running a coding task in a Claude Code project inside the Desktop app: within minutes the Chromium GPU process crashes and the entire app closes instantly. main.log always ends with:

GPU process gone: { type: 'GPU', reason: 'crashed', exitCode: 101457950, serviceName: 'GPU' }

After the crash the app will not reopen until running Repair (Settings > Apps > Claude > Advanced options). All in-flight sessions are lost.

Evidence from logs (Aug 13-16)

  • 10 identical fatal crashes, all exitCode 101457950; each one is the final line of its session - the GPU process is never relaunched, the whole app dies with it.
  • Not memory-related: the two most recent crashes happened with ~5.6 GB free system RAM and the app's process tree at ~840 MB.
  • No Windows TDR / display-driver events in the System event log at any crash time - the failure is contained to the Chromium GPU process.
  • Reproduced identically with hardware acceleration disabled: crash 75 seconds after app launch, GPU process running with --use-angle=d3d11-warp-webgl.

Workaround (confirmed on this machine)

Disabling Browser tools (Settings > Claude Code > Browser) stops the crashes - stable since, where previously it crashed within minutes of starting a task. Trade-off: removes the in-app preview/browser entirely.

Related

Closely related to #80444, #81159, #81698, #82967 (same exit code / symptoms). Filing to add an AMD integrated-GPU datapoint and a confirmed mitigation. In-app feedback already sent: ID cd0b17bf-c4a9-4218-b698-73e5df73d2f6.

Requests

  1. Fix the GPU-process crash, or fall back to software rendering instead of killing the whole app.
  2. Recover gracefully without corrupting the MSIX package (no Repair required).
  3. Let running Claude Code sessions survive or auto-resume after a GPU-process crash.

What Should Happen?

The app should not die when the GPU process fails: it should fall back to software rendering (or relaunch the GPU process) instead of terminating the entire app. The MSIX package should remain launchable without requiring Repair, and running Claude Code sessions should survive or auto-resume after a GPU-process crash.

Error Messages/Logs

2026-08-16 01:21:13 [info] GPU process gone: {
  type: 'GPU',
  reason: 'crashed',
  exitCode: 101457950,
  serviceName: 'GPU'
}

(final line of main.log before the app dies; identical signature in all 10 crashes: 2026-08-13 19:21:26, 19:37:25, 19:42:15, 19:47:06; 2026-08-14 03:51:43; 2026-08-15 03:18:58, 19:00:52, 22:05:43; 2026-08-16 01:21:13, 01:56:43)

Steps to Reproduce

  1. Windows 11 machine with AMD integrated graphics only, Claude Desktop installed from the Microsoft Store (MSIX).
  2. Open a Claude Code project in the desktop app (Code tab) and start any coding task.
  3. Let the agent work. Within ~1-25 minutes the entire app closes instantly; main.log ends with GPU process gone: { type: 'GPU', reason: 'crashed', exitCode: 101457950 }.
  4. Try to relaunch: the app fails to open until Repair is run (Settings > Apps > Claude > Advanced options).
  5. Repair, reopen, start another coding task: same crash. Reproduced 10 times between Aug 13-16, including once 75 seconds after launch with hardware acceleration disabled.
  6. Disable Browser tools (Settings > Claude Code > Browser) and repeat: no crash (stable since).

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.229 (Claude Code Desktop, bundled in Claude Desktop app 1.30096.5 MSIX)

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information

Using the Desktop app GUI (Code tab), not a terminal - selected "Other" for Terminal/Shell. GitHub's duplicate detector also suggests #86287 (same crash family); filing this report to add an AMD integrated-GPU environment datapoint and a workaround confirmed on this machine (disabling Browser tools). Full main.log excerpts, Crashpad/WER checks and per-crash memory readings available on request.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗