protonscr

Dragon's Dogma 2 3.2 causes AMDGPU GPUVM fault on RX 6700 XT

vkd3dopen
HansKristian-Work/vkd3d-proton#3267 · opened 2026-09-03 by TheOperator3712 · updated 2026-09-04 · 2 comments · github
TTheOperator3712 2026-09-03 github

Please describe your issue as accurately as possible. Include screenshots or videos if relevant

Software information

Dragon's Dogma 2 (Steam AppID 2054970), update 3.2, during normal gameplay. The update is reported to include a newer RE Engine version. The game is running through Steam Linux Runtime Sniper and GE-Proton10-34.

System information

  • GPU: AMD Radeon RX 6700 XT (Navi 22, PCI 0000:03:00.0)
  • Driver: Mesa RADV 26.1.7 / AMDGPU kernel driver
  • Kernel: 7.1.8.arch1-3 (linux-zen was also installed)
  • Firmware: linux-firmware-amdgpu 20260810-1
  • Session: Wayland / Hyprland
  • Wine/Proton: GE-Proton10-34
  • VKD3D-Proton version: bundled with GE-Proton10-34 (exact bundled revision not recorded)
  • Steam Linux Runtime: Sniper

Symptoms

At 11:50:02 MDT on 2026-09-03, the game triggered an AMDGPU GPUVM protection fault. Audio continued, but the display stopped updating. The GPU reset failed and Hyprland subsequently crashed. A forced shutdown was required.

Log files

Relevant journal excerpt:

Sep 03 11:50:02 kernel: amdgpu 0000:03:00.0: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:539)
Sep 03 11:50:02 kernel: amdgpu 0000:03:00.0:  Process DD2.exe pid 16447 thread vkd3d_queue pid 16764
Sep 03 11:50:02 kernel: amdgpu 0000:03:00.0:  in page starting at address 0x0000800020400000 from client 0x1b (UTCL2)
Sep 03 11:50:02 kernel: amdgpu 0000:03:00.0:  GCVM_L2_PROTECTION_FAULT_STATUS:0x00501431
Sep 03 11:50:02 kernel: amdgpu 0000:03:00.0:  Faulty UTCL2 client ID: SQC (data) (0xa)
Sep 03 11:50:02 kernel: amdgpu 0000:03:00.0:  PERMISSION_FAULTS: 0x3
Sep 03 11:50:04 kernel: amdgpu 0000:03:00.0: ring gfx_0.1.0 timeout
Sep 03 11:50:04 kernel: amdgpu 0000:03:00.0: Ring gfx_0.1.0 reset failed
Sep 03 11:50:04 kernel: amdgpu 0000:03:00.0: GPU reset begin!. Source: 1
Sep 03 11:50:04 steam: radv/amdgpu: The CS has been cancelled because the context is lost. This context is innocent.
Sep 03 11:50:04 steam: radv: GPUVM fault detected at address 0x800020400000.
Sep 03 11:50:10 kernel: amdgpu 0000:03:00.0: GPU mode1 reset failed
Sep 03 11:50:10 kernel: amdgpu 0000:03:00.0: ASIC reset failed with error, -62
Sep 03 11:50:10 kernel: amdgpu 0000:03:00.0: GPU Recovery Failed: -62
Sep 03 11:50:15 kernel: amdgpu 0000:03:00.0: flip_done timed out
Sep 03 11:51:03 kernel: amdgpu 0000:03:00.0: [drm] Failed to initialize parser -125
Sep 03 11:51:03 uwsm_hyprland.desktop[1601]: Hyprland has crashed

The same GPU previously produced the same broad SQC-data GPUVM protection-fault class on 2026-06-26 while Chromium was running, but that incident recovered through an AMDGPU ring reset. No OOM condition was present.

Questions

  1. Does this match a known VKD3D-Proton issue with the newer RE Engine workload used by Dragon's Dogma 2 update 3.2?
  2. Is there a recommended VKD3D configuration or workaround to avoid this fault on Navi 22/RADV?
  3. What additional diagnostics or exact VKD3D-Proton build information should be collected?

The game is not officially supported on Linux. This report is intended to identify whether the D3D12 workload is being translated incorrectly or exercising an unsupported VKD3D/RADV path; it does not assume Capcom is responsible for a Linux fix.

Mmbriar 2026-09-03 github

First of all it would probably be good to try with latest vkd3d-proton and not with some old build from proton-ge 10. Mesa 26.1.7 is also old and is not what is shipped by Arch currently. Also you could just include the full proton log compressed as .zip instead of letting some AI generate questions.

TTheOperator3712 2026-09-04 github

steam-2054970.zip

I have updated to Mesa 26.2.1 and GE-Proton 11-6, and retested. Here is the Proton log from the crash. The issue persists.

Full environment info:

Mesa 26.2.1
Linux 7.1.9
linux-firmware-amdgpu 20260810-2
RX 6700 XT
GE-Proton 11-6
vkd3d-proton build c9c6bf2e9c18252 (the crash log reports application version 3.1.0; build information is on lines 8052-8053)

One additional piece of relevant information: I experienced this same crash behavior in Monster Hunter Wilds in 2025. MHWilds also uses RE Engine, and is likely on a similar version of the engine to what Dragon's Dogma 2 has just updated to.

Also, my system is running Omarchy rather than stock Arch, so its package versions do not necessarily track the latest Arch packages.

The crash is also rather time-intensive to reproduce, as it seems to only occur after at least an hour of playtime.

Proton versions