GPU Process Crash Report

Help
1

Steps to reproduce

  • Install Obsidian 1.9.12 on Windows 11 build 26100.4946 (24H2, ge_release).
  • Use a clean vault (sandbox / no plugins / default theme).
  • Launch Obsidian normally.
  • Observe crash: GPU process repeatedly exits, Obsidian closes with APPCRASH.

Did you follow the troubleshooting guide? [Y/N]

Y – Reproduced in sandbox vault, no plugins, no snippets, default theme.

Expected result

Obsidian should launch normally and open the vault UI.

Actual result

  • Obsidian crashes on startup, fails to start normally, exiting with APPCRASH.
  • GPU process fails repeatedly before loading GPU driver DLLs.
  • WER (Windows Error Reporting) crash report shows 0x80000003 (EXCEPTION_BREAKPOINT) in Obsidian.exe.
  • Only workaround:
Obsidian.exe --disable-gpu --in-process-gpu

with Hardware Acceleration disabled in settings

Environment

  • Obsidian: 1.9.12 (Electron-based)
  • OS: Windows 11 build 26100.4946 (24H2, ge_release)
  • GPU: AMD Radeon 780M Graphics
  • Reproducibility: 100% (every launch)
  • /!\ Observation: No third-party DLL injection (overlays, AV hooks) visible in ProcMon traces.
  • /!\ Crash occurs before GPU vendor DLLs (atidxx64.dll, igd10iumd64.dll, nvldumd.dll) are loaded.

Additional information

  • ProcMon trace: GPU process is spawned multiple times with --type=gpu-process, each terminating in milliseconds.
  • No overlays or third-party DLL injections (Discord, RTSS, AV hooks) detected.
  • GPU driver DLLs (atidxx64.dll, etc.) are not even loaded before the crash.
  • Error log excerpt:
[ERROR:content\browser\gpu\gpu_process_host.cc:957] GPU process exited unexpectedly: exit_code=-2147483645
[FATAL:content\browser\gpu\gpu_data_manager_impl_private.cc:415] GPU process isn't usable. Goodbye.
  • Crash Signature (from .wer):
Exception Code: 0x80000003
Fault offset: 0x000000000717c12b
Report ID: d503b010-3934-42c5-ac99-584452179b63
Bucket ID: bedc006354dd4661626d58896c78cda6

Technical Findings

  • ProcMon trace: GPU process is spawned repeatedly (--type=gpu-process), each terminating within milliseconds.
  • .wer crash report shows only Microsoft system DLLs loaded.
  • GPU drivers are not yet involved at crash time.
  • Flags tested:
    • --disable-gpu → still crashes
    • --use-angle=warp → still crashes
    • --use-gl=swiftshader → still crashes
    • :white_check_mark: --disable-gpu --in-process-gpu → works

This points strongly to Chromium/Electron GPU sandbox incompatibility with Windows 24H2.

2

It doesn’t happen to me on 24h2. maybe try to updated your GPU drivers if you can.

3

After trying absolutely everything, the only solution I found was to reinstall Windows with the same build and keeping my personal files

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.