Desktop (Windows/MSIX): failed preview-pane navigation hangs GPU compositor -> watchdog kills GPU process -> whole app dies

Status Closed — duplicate

Reported on v2.1.219

Maintainer reply None cached

Activity 6 comments · opened Jul 27, 2026 · closed Aug 25, 2026

Summary

On Windows, when the in-app Preview/Browser pane fails to navigate to a local dev server, the pane's GPU compositor is left waiting for a frame. Almost exactly 12 seconds later the GPU process is killed with a constant exit code, the main process then exits with a fatal 0x80000003, and the entire app disappears — no crash dump, no WER report.

Reproduced 14 times over 3 days. The trigger sequence appears in main.log before every occurrence.

Repro

Open a Claude Code session on a Vite/React project that has .claude/launch.json defining a dev server.
Let the agent start the dev server and open the preview pane (preview_start).
navigatePreview fails (empty error field).
~12s later the app dies.

Log signature

[Preview] Starting server with config { name: 'dev', port: 8080, ... }
[Preview] Process spawned { pid: NNNN }
[Preview] Server ready (HTTP responding)
[Preview] navigatePreview failed { origin: 'http://localhost:8080', error: '' }
   ... ~12s gap ...
GPU process gone: { type: 'GPU', reason: 'crashed', exitCode: 101457950, serviceName: 'GPU' }

Process exit codes captured by an external watcher (ordered by actual exit time):

gpu-process   exit 101457950 (0x060C201E)   <- dies first
main          exit -2147483645 (0x80000003) <- 250-400ms later, STATUS_BREAKPOINT
renderers/utilities  exit 0                 <- teardown

0x060C201E is identical on every occurrence and is not a Windows exception code; combined with the absence of any exception record this indicates a deliberate watchdog termination, not a fault. The 0x80000003 on main matches Chromium's fatal "GPU process isn't usable" path.

A closely related symptom that shows up ~400 times in the same logs:
Screenshot timed out after 5s: the Browser pane is not displayed, so the page is not compositing frames.

Ruled out (with evidence)

| Hypothesis | Evidence against |
|---|---|
| GPU driver | Reproduced on both an outdated Intel iGPU driver and after updating + forcing the discrete NVIDIA GPU. Zero display-driver TDR events (Display 4101 / nvlddmkm / igfx) in the System event log across all 14 crashes. |
| Hardware acceleration | Setting isHardwareAccelerationDisabled: true did not help — it forces WebGL onto d3d11-warp-webgl (software WARP) and the GPU process still dies with the same code. Removing it and confirming real hardware (ANGLE (NVIDIA ... D3D11) via WEBGL_debug_renderer_info) also still crashes. |
| Third-party injection | GPU process module list contains only Windows and app DLLs — no injected overlay/AV modules. |
| Vendor "optimizer" software | Crashes continue with MSI AI Engine off and the Nahimic audio service disabled. |
| Memory / disk / thermal / sleep | Commit 13.8/29.9 GB, pagefile peak 96 MB, no Resource-Exhaustion events, SSD healthy, no disk errors, no sleep/resume events at crash times, no CPU throttling events. |

Why it's hard to diagnose from the user side

No artifact is produced at all: Crashpad/reports stays empty, there is no WER ReportArchive entry, and no Application Error event for claude.exe — while other apps on the same machine do log normally. The app's own log ends mid-second with no shutdown lines, so nothing in-app records its own death.

Environment

Claude Desktop 1.24012.9 (MSIX install; note [CCD-autoupdate] Disabled: MSIX install, so this build never self-updates)
Claude Code 2.1.219
Windows 11 26200, 16 GB RAM
Hybrid graphics: Intel UHD (Alder Lake) + NVIDIA RTX 3050 Laptop
16 MCP servers configured

Suggested fix direction

Failed preview navigation should tear down or reset the pane's compositing surface rather than leaving it awaiting a frame. Additionally, a GPU-watchdog kill arguably shouldn't escalate to a fatal main-process exit — recreating the GPU process (or falling back) would keep the app alive and turn this into a degraded pane instead of total data-losing app death.

Workaround

Avoid the in-app preview pane entirely; view dev servers in an external browser.

View original on GitHub ↗

4 Comments

naokikato-byissues · 1 month ago

Additional data point / same exit code, different trigger — AMD Radeon (non-hybrid) environment

Seeing the exact same exit code on Claude Desktop 1.24012.9, but reproduced without a failed preview navigation — simply opening the in-app browser pane (browser preview / Claude_Browser MCP tools) and letting the loaded page initialize WebGL/WebGPU is enough to kill the GPU process within ~5–10 seconds, taking the whole app down with it.

Environment: Claude Desktop 1.24012.9 (MSIX), Claude Code 2.1.208, Windows 11 Pro 10.0.26200, AMD Radeon(TM) Graphics (integrated only, no hybrid GPU), driver 32.0.21043.19003 (2026-06-26).

5/5 reproductions over two days, all with identical exit code 101457950 (0x60C201E): Jul 27 (JST) 10:56 and 11:43; Jul 28 (JST) 09:17, 09:56 and 11:58.

main.log:

2026-07-28 09:17:11 [info] [PreviewContext] Opened preview user tab { serverId: 'preview-local_db858747-...', tabId: 'tab-1', openTabs: 2 }
2026-07-28 09:17:21 [info] GPU process gone: { type: 'GPU', reason: 'crashed', exitCode: 101457950, serviceName: 'GPU' }

Log ends there every time — next line is a manual relaunch.

Renderer log (unknown-window.log) just before the 11:58 crash:

2026-07-28 11:58:19 [warn] WebGL: INVALID_ENUM: getInternalformatParameter: invalid internalformat (repeated ~20x)
2026-07-28 11:58:20 [warn] The powerPreference option is currently ignored when calling requestAdapter() on Windows. See https://crbug.com/369219127
2026-07-28 11:58:20 [warn] WebGL: CONTEXT_LOST_WEBGL: loseContext: context lost

Regression: stable on 1.24012.1 (heavy browser-pane usage Jul 22–24, 4–6 parallel tabs, zero crashes; GPU process gone events were always reason 'killed', never 'crashed'). First browser-pane use after auto-updating to 1.24012.9 (~Jul 24–25) crashed within 6 seconds.

This suggests the identical exit code isn't tied to one specific trigger (failed preview navigation vs. WebGL init on pane open) or GPU vendor (Intel/NVIDIA hybrid vs. AMD integrated) — the common thread seems to be a GPU-process crash that escalates to a full app kill instead of the app surviving or falling back to software rendering.

trungkt134 · 1 month ago

Thanks @naokikato-byissues — that's a useful independent confirmation, and your "not tied to one trigger or GPU vendor" reading matches what I see.

One correction though: the regression window is wider than 1.24012.1 → 1.24012.9.

I went back through my rotated logs. On this machine the identical exit code 101457950 (0x60C201E) occurs across three versions, including 1.24012.1 which you found stable:

version switches:
  2026-07-21 10:21:40  -> 1.22209.3
  2026-07-22 09:42:52  -> 1.24012.1
  2026-07-25 01:47:25  -> 1.24012.9

GPU crashes (all exitCode 101457950, all reason 'crashed'):
  2026-07-21 11:42, 11:49                       <- on 1.22209.3
  2026-07-23 00:15, 00:26, 00:43, 00:56, 03:01  <- on 1.24012.1
  2026-07-25 14:01 ... 2026-07-26 00:29 (10x)   <- on 1.24012.9

So bisecting only 1.24012.1 → 1.24012.9 would likely come up empty.

Ruling out "I just wasn't using the pane before": older logs show 1,622 [Preview] operations from 2026-06-07 through mid-July with zero occurrences of 101457950. GPU-process-gone events do appear in that period, but with clearly benign shutdown codes:

reason: 'killed',  exitCode: 1073807364    (0x40010004, DBG_TERMINATE_PROCESS)
reason: 'crashed', exitCode: -1073741205   (0xC000026B, at logoff/shutdown)

The first 101457950 on this machine is 2026-07-21 11:42:39. Notably that's ~80 minutes after the app updated to 1.22209.3, and the first [Preview] use in that session was 10:47:55 — so the pane was exercised before the first crash, not only after.

That makes 1.22209.3 (or something shipped alongside it) a better starting point for the bisect than 1.24012.1.

Environment for this data point: Claude Desktop 1.24012.9 (MSIX), Claude Code 2.1.219, Windows 11 26200, hybrid Intel UHD (Alder Lake) + NVIDIA RTX 3050 Laptop.

Also worth adding to the "vendor/config independent" evidence: I reproduced it on this machine both while WebGL was on real hardware (ANGLE (NVIDIA ... D3D11), confirmed via WEBGL_debug_renderer_info) and while forced onto software WARP (--use-angle=d3d11-warp-webgl via isHardwareAccelerationDisabled). Same exit code both ways — so it isn't the hardware path itself failing.

joneberhard · 1 month ago

<html>
<body>
<p style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility; color: rgb(225, 224, 217); font-family: "Anthropic Sans", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(32, 32, 31); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Confirming this on older hardware than the other reports, with a detail that may narrow the trigger: <strong style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-weight: 500; font-variation-settings: "opsz" 16, "wght" 560; text-rendering: optimizelegibility;">the previewed page contained no WebGL or WebGPU at all.<h3 style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-size: 15px; font-weight: 600; text-rendering: optimizelegibility; margin-block: 20px 6px; padding-block: 0px; color: rgb(225, 224, 217); font-family: "Anthropic Sans", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(32, 32, 31); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Environment</h3><div class="overflow-x-auto" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); overflow-x: auto; text-rendering: optimizelegibility; color: rgb(225, 224, 217); font-family: "Anthropic Sans", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(32, 32, 31); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">
Claude Desktop | 1.24012.9.0, MSIX
-- | --
Claude Code | 2.1.219
Electron | 42.7.0
OS | Windows 10 Home 22H2, build 19045
CPU / board | i7-7700K, MSI Z270
GPU | NVIDIA GTX 1080 (Pascal, 2016), driver 32.0.15.8266, dated 2026-06-08
RAM | 48 GB, ~35 GB free at crash
Displays | single, no HDR
Hardware acceleration | enabled (default)

</div><p style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility; color: rgb(225, 224, 217); font-family: "Anthropic Sans", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(32, 32, 31); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><strong style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-weight: 500; font-variation-settings: "opsz" 16, "wght" 560; text-rendering: optimizelegibility;">3. The pane was not displayed. The screenshot error explicitly says the Browser pane is not displayed and the page is not compositing frames. So the compositor was being asked for a frame from a hidden pane when it hung.<p style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility; color: rgb(225, 224, 217); font-family: "Anthropic Sans", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(32, 32, 31); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><strong style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-weight: 500; font-variation-settings: "opsz" 16, "wght" 560; text-rendering: optimizelegibility;">4. Not 100 % reproducible here. Counting <code node="[object Object]" data-epitaxy-inline-code="" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-family: "Anthropic Mono", ui-monospace, monospace; font-feature-settings: "calt" 0, "liga" 0; font-variation-settings: normal; font-size: 12px; font-variant-ligatures: none; text-rendering: optimizelegibility; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(255, 255, 255, 0.08); color: rgb(225, 224, 217); border-radius: 4px; padding-block: 1px; padding-inline: 2px; line-height: 1.4;">Created session preview context</code>, there were <strong style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-weight: 500; font-variation-settings: "opsz" 16, "wght" 560; text-rendering: optimizelegibility;">24 distinct preview sessions across those 6 days and 1 crash. The other 23 produced no WebGL/WebGPU lines at all, so they never engaged the GPU path.<p style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility; color: rgb(225, 224, 217); font-family: "Anthropic Sans", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(32, 32, 31); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><strong style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-weight: 500; font-variation-settings: "opsz" 16, "wght" 560; text-rendering: optimizelegibility;">5. <code node="[object Object]" data-epitaxy-inline-code="" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-family: "Anthropic Mono", ui-monospace, monospace; font-feature-settings: "calt" 0, "liga" 0; font-variation-settings: normal; font-size: 12px; font-variant-ligatures: none; text-rendering: optimizelegibility; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(255, 255, 255, 0.08); color: rgb(225, 224, 217); border-radius: 4px; padding-block: 1px; padding-inline: 2px; line-height: 1.4;">capturePreviewScreenshot failed</code> is not the predictor. It fired <strong style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-weight: 500; font-variation-settings: "opsz" 16, "wght" 560; text-rendering: optimizelegibility;">3,098 times in 6 days harmlessly. The useful signal is <code node="[object Object]" data-epitaxy-inline-code="" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-family: "Anthropic Mono", ui-monospace, monospace; font-feature-settings: "calt" 0, "liga" 0; font-variation-settings: normal; font-size: 12px; font-variant-ligatures: none; text-rendering: optimizelegibility; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(255, 255, 255, 0.08); color: rgb(225, 224, 217); border-radius: 4px; padding-block: 1px; padding-inline: 2px; line-height: 1.4;">navigatePreview failed</code> followed by the watchdog-shaped gap.<h3 style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-size: 15px; font-weight: 600; text-rendering: optimizelegibility; margin-block: 20px 6px; padding-block: 0px; color: rgb(225, 224, 217); font-family: "Anthropic Sans", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(32, 32, 31); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Confirming the "no Windows trace" point</h3><p style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility; color: rgb(225, 224, 217); font-family: "Anthropic Sans", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(32, 32, 31); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Nothing in Windows records this, which makes it easy to misdiagnose:<ul style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px 0px 0px 20px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); list-style: outside; text-rendering: optimizelegibility; gap: 6px; flex-direction: column; display: flex; color: rgb(225, 224, 217); font-family: "Anthropic Sans", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(32, 32, 31); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><li style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility;"><code node="[object Object]" data-epitaxy-inline-code="" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-family: "Anthropic Mono", ui-monospace, monospace; font-feature-settings: "calt" 0, "liga" 0; font-variation-settings: normal; font-size: 12px; font-variant-ligatures: none; text-rendering: optimizelegibility; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(255, 255, 255, 0.08); color: rgb(225, 224, 217); border-radius: 4px; padding-block: 1px; padding-inline: 2px; line-height: 1.4;">Crashpad\reports\</code> empty</li><li style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility;">no Application-log fault event for <code node="[object Object]" data-epitaxy-inline-code="" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-family: "Anthropic Mono", ui-monospace, monospace; font-feature-settings: "calt" 0, "liga" 0; font-variation-settings: normal; font-size: 12px; font-variant-ligatures: none; text-rendering: optimizelegibility; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(255, 255, 255, 0.08); color: rgb(225, 224, 217); border-radius: 4px; padding-block: 1px; padding-inline: 2px; line-height: 1.4;">claude.exe</code></li><li style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility;"><strong style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-weight: 500; font-variation-settings: "opsz" 16, "wght" 560; text-rendering: optimizelegibility;">zero display-driver TDRs, provider <code node="[object Object]" data-epitaxy-inline-code="" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-family: "Anthropic Mono", ui-monospace, monospace; font-feature-settings: "calt" 0, "liga" 0; font-variation-settings: normal; font-size: 12px; font-variant-ligatures: none; text-rendering: optimizelegibility; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(255, 255, 255, 0.08); color: rgb(225, 224, 217); border-radius: 4px; padding-block: 1px; padding-inline: 2px; line-height: 1.4;">Display</code> event 4101, count 0 all time</li><li style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility;">no WHEA or disk errors around the crash</li></ul><p style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility; color: rgb(225, 224, 217); font-family: "Anthropic Sans", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(32, 32, 31); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">I spent a week concluding the app "was not crashing" on the strength of an empty Event Viewer. Only <code node="[object Object]" data-epitaxy-inline-code="" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-family: "Anthropic Mono", ui-monospace, monospace; font-feature-settings: "calt" 0, "liga" 0; font-variation-settings: normal; font-size: 12px; font-variant-ligatures: none; text-rendering: optimizelegibility; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(255, 255, 255, 0.08); color: rgb(225, 224, 217); border-radius: 4px; padding-block: 1px; padding-inline: 2px; line-height: 1.4;">main.log</code> records it, and its last line is the cause of death.<h3 style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-size: 15px; font-weight: 600; text-rendering: optimizelegibility; margin-block: 20px 6px; padding-block: 0px; color: rgb(225, 224, 217); font-family: "Anthropic Sans", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(32, 32, 31); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">One caution for anyone landing here from search</h3><p style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility; color: rgb(225, 224, 217); font-family: "Anthropic Sans", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(32, 32, 31); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">On this machine <code node="[object Object]" data-epitaxy-inline-code="" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-family: "Anthropic Mono", ui-monospace, monospace; font-feature-settings: "calt" 0, "liga" 0; font-variation-settings: normal; font-size: 12px; font-variant-ligatures: none; text-rendering: optimizelegibility; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(255, 255, 255, 0.08); color: rgb(225, 224, 217); border-radius: 4px; padding-block: 1px; padding-inline: 2px; line-height: 1.4;">--disable-gpu-compositing</code> could not be applied at all. Windows denies <code node="[object Object]" data-epitaxy-inline-code="" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-family: "Anthropic Mono", ui-monospace, monospace; font-feature-settings: "calt" 0, "liga" 0; font-variation-settings: normal; font-size: 12px; font-variant-ligatures: none; text-rendering: optimizelegibility; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(255, 255, 255, 0.08); color: rgb(225, 224, 217); border-radius: 4px; padding-block: 1px; padding-inline: 2px; line-height: 1.4;">CreateProcess</code> on binaries under <code node="[object Object]" data-epitaxy-inline-code="" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-family: "Anthropic Mono", ui-monospace, monospace; font-feature-settings: "calt" 0, "liga" 0; font-variation-settings: normal; font-size: 12px; font-variant-ligatures: none; text-rendering: optimizelegibility; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(255, 255, 255, 0.08); color: rgb(225, 224, 217); border-radius: 4px; padding-block: 1px; padding-inline: 2px; line-height: 1.4;">C:\Program Files\WindowsApps</code> for a non-elevated user, and the package declares no <code node="[object Object]" data-epitaxy-inline-code="" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-family: "Anthropic Mono", ui-monospace, monospace; font-feature-settings: "calt" 0, "liga" 0; font-variation-settings: normal; font-size: 12px; font-variant-ligatures: none; text-rendering: optimizelegibility; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(255, 255, 255, 0.08); color: rgb(225, 224, 217); border-radius: 4px; padding-block: 1px; padding-inline: 2px; line-height: 1.4;">AppExecutionAlias</code>, so there is no path that both activates the package and forwards Chromium flags. Electron's single-instance lock also silently discards the arguments if any instance is already running. It needs an elevated launch.<p style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility; color: rgb(225, 224, 217); font-family: "Anthropic Sans", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(32, 32, 31); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Given #81840 reports the crash reproducing with hardware acceleration fully disabled, that may be moot anyway.<h3 style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px 0px 16px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-size: 15px; font-weight: 600; text-rendering: optimizelegibility; margin-block: 20px 6px; padding-block: 0px; color: rgb(225, 224, 217); font-family: "Anthropic Sans", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(32, 32, 31); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Possibly related</h3><p style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); text-rendering: optimizelegibility; color: rgb(225, 224, 217); font-family: "Anthropic Sans", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(32, 32, 31); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">The July 24 to 25 incident on this machine left the package <code node="[object Object]" data-epitaxy-inline-code="" style="box-sizing: border-box; border: 0px solid color(srgb 1 1 1 / 0.1); margin: 0px; padding: 0px; outline-color: rgb(85, 152, 231); scrollbar-width: thin; scrollbar-color: rgba(225, 224, 217, 0.35) rgba(0, 0, 0, 0); font-family: "Anthropic Mono", ui-monospace, monospace; font-feature-settings: "calt" 0, "liga" 0; font-variation-settings: normal; font-size: 12px; font-variant-ligatures: none; text-rendering: optimizelegibility; background: none 0% 0% / auto repeat scroll padding-box border-box rgba(255, 255, 255, 0.08); color: rgb(225, 224, 217); border-radius: 4px; padding-block: 1px; padding-inline: 2px; line-height: 1.4;">Modified, NeedsRemediation</code> with no known cause. #81123 reports exactly that outcome from a browser-preview GPU crash, on the same OS build and package version. I cannot prove they are connected here, but it fits.
</body>
</html>

trungkt134 · 28 days ago

Cross-linking two other open issues that are almost certainly the same defect, plus a consolidated matrix — there are now five independent environments reporting the identical exit code, spread across three issues, none of them triaged yet.

Related issues: #81123 (2026-07-25) and #81840 (2026-07-28).

Consolidated environment matrix — all `exitCode 101457950` (0x60C201E)

| Source | OS | GPU | HW accel | Trigger → death | Reprod. |
|---|---|---|---|---|---|
| this issue | Win11 26200 | Intel UHD + RTX 3050 (hybrid) | both on and off | navigatePreview failed → ~12 s | 17 crashes |
| @naokikato-byissues | Win11 Pro 26200 | AMD Radeon iGPU only, no hybrid | on | open pane, page inits WebGL → 5–10 s | 5/5 |
| @joneberhard | Win10 Home 19045 | GTX 1080 (Pascal, 2016) | on | navigatePreview failed, no WebGL on page | 1 of 24 sessions |
| #81840 | Win11 26200 | RTX 4090 + AMD iGPU (dual) | off, WARP confirmed | open browser pane → ~1 s | 3/3 |
| #81123 | Win10 Pro 19045 | RTX 3060 Ti | on | open browser pane → ~2 s | 2/2 |

What is invariant

The exit code, and the shape: GPU process dies, main follows with fatal 0x80000003, nothing lands in Crashpad / WER / Application log, and zero display-driver TDRs anywhere.

What varies — i.e. what can be ruled out as the cause

GPU vendor and era: Intel iGPU, AMD iGPU, Pascal (2016), Ada (4090), Ampere (3060 Ti). Hybrid and non-hybrid both.
OS: Windows 11 26200 and Windows 10 19045 (Home and Pro).
Hardware acceleration: crashes with it on and off. #81840 verified WARP was genuinely active (D3D10Warp.dll loaded, zero nv* DLLs) and still crashed — so the hardware path is not the failing component.
WebGL/WebGPU on the page: present in some reports, entirely absent in @joneberhard's. Not required.
Time to death: ~1 s, ~2 s, 5–10 s, ~12 s.

Two discriminators worth chasing

**#81840: only the browser preview crashes.** A [Preview] Created Claude page preview in the same session did not. That narrows it to the browser-pane code path rather than preview infrastructure generally.
@joneberhard: the pane was hidden. The compositor was being asked for a frame from a pane that was not displayed. That is consistent across reports and looks like the common precondition — more so than WebGL, which the varied data rules out.

Severity is higher than "a crash"

#81123 documents the GPU crash leaving the MSIX package Modified, NeedsRemediation, after which remediation fails with 0x80073D02 and the app will not launch at all until a reinstall-over-top. So a rendering fault in a preview pane can brick the installation. Worth weighting when prioritising.

Suggested framing for a fix

Independent of whichever trigger hangs the compositor, the escalation path looks like the real defect: a GPU-process loss should degrade the pane, not terminate the application. Recreating the GPU process — or falling back — would turn every report above into a cosmetic glitch instead of an app kill that interrupts running sessions and can damage the package.

Showing cached comments. Read the full discussion on GitHub ↗