Claude Desktop: GPU process repeatedly crashes when opening embedded browser/preview pane (Windows, hybrid Intel+NVIDIA GPU)
Claude Desktop version: 1.32352.0 (also reproduced on 1.30096.5, so not update-related)
OS: Windows 11 Pro
GPU: Intel UHD Graphics (driver 31.0.101.1999, dated 2022-05-31) + NVIDIA GeForce GTX 1650 Ti (driver 32.0.15.9579, dated 2026-03-04) - hybrid/Optimus laptop
Summary
The Claude Desktop app repeatedly closes itself. Log analysis (%APPDATA%\Claude\logs\main.log) shows the Electron GPU process crashing with the same exit code every time:
GPU process gone: {
type: "GPU",
reason: "crashed",
exitCode: 101457950,
serviceName: "GPU"
}
Reproduction pattern
In 3 of 4 observed crashes, the crash occurs 5-12 seconds after this log line:
[Preview] Created session preview context
[Preview] Created browser preview { serverId: ... }
i.e. the crash correlates strongly with opening the in-app embedded browser/live-preview pane (used when Claude opens a website preview / uses the Browser tool), not with GPU choice.
What I tried (did not fix it)
- Updated Claude Desktop from 1.30096.5 to 1.32352.0 - crash still occurred afterward with the same exit code.
- Forced the app to use the NVIDIA GPU instead of Intel via Windows Settings > System > Display > Graphics settings (verified in registry:
HKCU\Software\Microsoft\DirectX\UserGpuPreferences->Claude_pzs8sxrjxfjjc!Claude = GpuPreference=2) - crash still occurred afterward with the identical exit code (101457950).
Since the crash reproduces identically regardless of which physical GPU is selected, this looks like a Chromium/Electron GPU-process issue specific to spinning up the embedded browser/preview webview context, rather than a GPU driver compatibility issue per se.
Additional notes
- Crashpad reports folder (%APPDATA%\Claude\Crashpad\reports) is empty, so no crash dump is being captured for this failure.
- No memory pressure at time of crash (system free memory ~2.7-3.4GB out of 16GB, stable, no OOM trend).
- No hardware-acceleration toggle is exposed in the app to test disabling GPU rendering entirely.
Request
Would appreciate guidance on:
- Whether disabling hardware acceleration is possible via a flag/config file
- Whether this is a known issue with the embedded preview/browser pane on hybrid-GPU Windows laptops
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗