Narrowing down if it's mesh shaders or raw access chains would likely be helpful. Running with Proton Experiment debug branch and VKD3D_CONFIG=breadcrumbs and posting log might also help too.
I was able to play with just VKD3D_DISABLE_EXTENSIONS=VK_NV_raw_access_chains and it did not crash once.
I will try running as you say and get back to you.
ok, if it's just raw access chains, it's pretty clear it's a driver bug that NV needs to resolve.
Alrighty, thanks for taking a look! I'll post over in Nvidia.
proton experimentalx1 2026-07VKD3D_DISABLE_EXTENSIONS=VK_NV_raw_access_chains`x1 2026-07VKD3D_CONFIG=breadcrumbs`x1 2026-07PROTON_DLSS_UPGRADE=1`x1 2026-07VKD3D_CONFIG=descriptor_qa_checks`x1 2026-07VKD3D_DISABLE_EXTENSIONS=VK_EXT_mesh_shader,VK_NV_raw_access_chainsx1 2026-07VKD3D_DISABLE_EXTENSIONS=VK_EXT_mesh_shader,VK_NV_raw_access_chains`x1 2026-070x80070057x1 2026-07
Summary
Subnautica 2 (Steam appid 1962700, UE 5.6, D3D12) intermittently crashes with
VK_ERROR_DEVICE_LOST→DXGI_ERROR_DEVICE_REMOVEDduring normal gameplay on NVIDIA. Kernel log shows an Xid 13 Graphics SM Warp Exception (MMU Fault) attributed to the game process at crash time. SettingVKD3D_DISABLE_EXTENSIONS=VK_EXT_mesh_shader,VK_NV_raw_access_chainsfully resolves the crashes.System
Reproduces on
Identical failure signature on both. DLSS Frame Generation on/off makes no difference (also reproduces with Streamline DLSS-G inactive).
PROTON_DLSS_UPGRADE=1was set in all sessions (DLSS 310.7.0).Symptoms
Crash occurs 1–20 minutes into gameplay, often shortly after entering new areas / streaming new content. Proton log at crash time:
followed by UE5:
Kernel log at the same timestamp:
Possibly related shader validation failures
Every session also logs five of these early on (with matching compute PSO creation failures, hr 0x80070057):
(The game appears to ship compute shaders with a hard WaveSize(64) requirement.) Unclear whether related to the device loss — listed for completeness.
Note: vkd3d-proton already detects this title ("Detected game Subnautica2-Win64-Shipping.exe, adding 2 configs... adding shader quirks for specific shaders").
Workaround
No crashes since applying this (previously crashing every session). Have not yet bisected which of the two extensions is responsible; can do so if useful.
Available on request
VKD3D_CONFIG=descriptor_qa_checkslog from a crash with the workaround removed, if that would help identify the offending shader