protonscr

DCS Crashes after respawn

dxvkopen d3d11not our bug
doitsujin/dxvk#5799 · opened 2026-07-18 by PANkefir323 · updated 2026-07-24 · 1 comments · github
1 matching comments, n / p to jump
PPANkefir323 2026-07-18 github

Please describe your issue as accurately as possible. Include screenshots or videos when relevant.
DCS World crashes with ACCESS_VIOLATION in d3d11.dll consistently
when respawning in multiplayer (selecting a new aircraft slot after death). The crash occurs in the render thread
during scene reinitialization (respawn destroys and recreates the scene).

Stack trace shows: d3d11 → dx11backend → graphicscore → scenerenderer → visualizer

This is reproducible 100% of the time on multiplayer servers (tested on
4YA Caucasus PVE server). Singleplayer does not trigger this crash.

Software information

DCS World Steam Edition (appid 223750), version 2.9.27.25340
Graphics settings: mostly low, shadows=low, MSAA=1x, no upscaling
No additional mods beyond standard DCS modules
Running through GE-Proton (Proton-GE)

System information

  • GPU:AMD Radeon RX 7600 XT (RADV NAVI33)
  • Driver:Mesa 26.0.2, RADV
  • Wine version:GE-Proton11-1
  • DXVK [version:]2.7.1 (bundled with GE-Proton11)

Log files

steam-223750-crash.log

DCS World crash file:

-------------- 20260718-164918 --------------

DCS/2.9.27.25340 (x86_64; MT; Windows NT 10.0.19045)
C:\windows\system32\d3d11.dll

C0000005 ACCESS_VIOLATION at 00006fffd329b7cd 00:00000000

SymInit: Symbol-SearchPath: 'S:\common\DCSWorld\bin;', symOptions: 532, UserName: 'steamuser'
OS-Version: 10.0.19045 () 0x0-0x1
0x000000000020b7cd (d3d11): (function-name not available) + 0x0
0x000000000020c796 (d3d11): (function-name not available) + 0x0
0x0000000000024884 (d3d11): (function-name not available) + 0x0
0x0000000000136706 (d3d11): (function-name not available) + 0x0
0x0000000000094191 (d3d11): (function-name not available) + 0x0
0x000000000003699d (d3d11): (function-name not available) + 0x0
0x00000000000305d3 (d3d11): (function-name not available) + 0x0
0x000000000003a602 (dx11backend): (function-name not available) + 0x0
0x000000000003bae1 (dx11backend): (function-name not available) + 0x0
0x00000000000570e5 (graphicscore): (function-name not available) + 0x0
0x0000000000054110 (graphicscore): (function-name not available) + 0x0
0x000000000001ec84 (scenerenderer): (function-name not available) + 0x0
0x000000000015aa75 (visualizer): (function-name not available) + 0x0
0x0000000000048ee4 (edcore): (function-name not available) + 0x0
0x000000000004a5f3 (edcore): (function-name not available) + 0x0
0x00000000000346e1 (edcore): (function-name not available) + 0x0
0x000000000002323b (ucrtbase): (function-name not available) + 0x0
0x0000000000011609 (kernel32): (function-name not available) + 0x0

Ddoitsujin maintainer 2026-07-18 github

From the log:

err:   DxvkMemoryAllocator: Memory allocation failed
err:     Size:      22369792
err:     Alignment: 256
err:     Mem types: 0,2,3,5,7,8,9,10
[...]
err:   Heap  Size (MiB)  Allocated   Used        Reserved    Budget
err:    0:    15838       14624       13300       13231       14658      
err:    1:     8176        8019        7168        8102        8176

I don't know why this game requires so much VRAM, but a combined 24GB clearly doesn't cut it, you'll probably want to try increasing the amdgpu GTT size (e.g. via kernel options: amdgpu.gttsize=24576 to allow up to 24GB of system memory to be used)

Proton versions

DLLs