protonscr

Space Marine 2: crash from unimplemented ID3D12DeviceRemovedExtendedData1

vkd3dopen appid 2183900
HansKristian-Work/vkd3d-proton#3206 · opened 2026-08-08 by globalghost · updated 2026-08-08 · 0 comments · github · game page · search this game
Gglobalghost 2026-08-08 github

Game crashes shortly after reaching the title screen (or after loading, if D3D11 is forced via -d3d11) with EXCEPTION_ACCESS_VIOLATION (write to 0x0). Crash happens immediately after d3d12_device_QueryInterface returns E_NOINTERFACE for GUID {9727a022-cf1d-4dda-9eba-effa653fc506} (ID3D12DeviceRemovedExtendedData1). Game appears to query this to set up GPU crash-dump telemetry (DRED) on startup and doesn't null-check the result.

ID3D12DeviceRemovedExtendedData1 isn't declared in include/vkd3d_d3d12.idl (only the base ID3D12DeviceRemovedExtendedData and the ...Settings/Settings1/Settings2 variants are). vkd3d-proton already stubs ID3D12DeviceRemovedExtendedDataSettings for the same reason ("Fixes some games that rely on this existing" per CHANGELOG) — this looks like the same class of fix, just the sibling interface.

Reproducible identically under forced D3D11 (-d3d11, DXVK active) — the game creates a separate D3D12 device purely for this telemetry, independent of the render API, and crashes there too, with the same fault address in both cases.

Software information

Warhammer 40,000: Space Marine 2, Steam AppID 2183900. Default settings. Crash occurs before reaching the main menu, so in-game settings are not a factor.

System information

  • GPU: NVIDIA RTX 3080
  • Driver: NVIDIA 610.57.04 (open kernel modules)
  • Wine version: Proton Experimental
  • VKD3D-Proton version: 3.1.0, build 2c7ba22c5326145

steam-2183900-redacted.log.gz

Proton versions