protonscr

DXVK state cache written by dGPU (NVIDIA) is read by iGPU (Intel) on next launch with prime-run, causing game crash (0xE00101C0) on NVIDIA hybrid laptops

protonclosed
ValveSoftware/Proton#9734 · opened 2026-05-02 by ACDD233 · updated 2026-05-02 · 1 comments · github
1 matching comments, n / p to jump
AACDD233 2026-05-02 github

Compatibility Report

  • Name of the game with compatibility issues: Overwatch 2
  • Steam AppID of the game: 2357570

System Information

  • GPU: Intel Graphics (RPL-S) [iGPU, system default] + NVIDIA GeForce RTX 4070 Laptop GPU [dGPU, via prime-run]
  • Video driver version: NVIDIA 580.142 / Mesa 25.x (Intel)
  • Kernel version: 6.19.14-200.fc43.x86_64
  • Link to full system information report as Gist: https://coppy.it/nameless-chidori-89
  • Proton version: proton-hotfix

steam-2357570.log

I confirm:

  • that I haven't found an existing compatibility report for this game.
  • that I have checked whether there are updates for my system available.

Symptoms

On a hybrid Intel+NVIDIA laptop (Fedora 43, Wayland), launching Overwatch 2 with prime-run %command% fails with error 0xE00101C0 on every launch except the first one after deleting the DXVK state cache.

The game log shows on first (successful) launch:

Selected GPU: NVIDIA GeForce RTX 4070 Laptop GPU Selected Graphics API: Dx11 Render Thread Failed to Start - timeout teRenderMgr_C failed to startup.

On subsequent launches the crash reporter shows the GPU is not recognized at all:

`GPU Type: Wine Adapter
GPU Driver: 35.0.99.9999 - wine.dll
Video Memory: 1024 MB

Unloaded Modules:
d3d12.dll
nvapi64.dll`

Root cause identified: The DXVK state cache (.dxvk.bin / .dxvk.lut) is written by the NVIDIA dGPU after the first successful session. On the next launch, DXVK reads the cache before PRIME render offload has fully redirected Vulkan device selection, causing the Intel iGPU to read an NVIDIA-generated cache. The GPU/driver mismatch is treated as a fatal error rather than a graceful cache invalidation, crashing the game.

This is confirmed by:

  • glxinfo | grep "OpenGL renderer" returns Mesa Intel(R) Graphics (RPL-S) by default (iGPU)
  • prime-run glxinfo | grep "OpenGL renderer" correctly returns NVIDIA GeForce RTX 4070 Laptop GPU
  • The crash only occurs when the DXVK cache files exist; deleting them restores functionality

Reproduction

  1. Set Steam launch option to prime-run %command%
  2. Delete compatdata/2357570/pfx/drive_c/users/steamuser/AppData/Local/dxvk/ entirely
  3. Launch Overwatch 2 → launches successfully; DXVK writes *.dxvk.bin and *.dxvk.lut
  4. Exit the game
  5. Launch Overwatch 2 again → crashes immediately with 0xE00101C0
  6. Delete the .dxvk.* cache files → game launches successfully again
  7. Repeat steps 4–6 indefinitely to confirm 100% reproducibility

Confirmed workarounds:

  • chmod 555 the DXVK cache directory after first launch (prevents cache being overwritten)
  • DXVK_STATE_CACHE=0 prime-run %command% (disables cache entirely)
Kkisak-valve maintainer 2026-05-02 github

Hello @ACDD233, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to https://github.com/ValveSoftware/Proton/issues/7033#issuecomment-4363820009.

Proton versions

Launch options

Launch lines

Upstream links

DLLs