Name of the game with compatibility issues: A.V.A Global
Steam AppID of the game: 1473480
System Information
GPU: AMD Radeon RX 5700 XT (Navi 10 / 1002:731f)
Video driver version: Mesa 26.1.5 (RADV)
Kernel version: Linux 6.x
OS: Arch Linux (KDE Wayland / Xwayland)
CPU: Intel Core i5-13400
Proton version: Proton Experimental (Regression)
I have tested this issue against the following versions:
[x] Proton Experimental (Fails / Hard Hang)
[x] Stable Proton 11 (Works as expected)
Symptoms
Running A.V.A Global on Proton Experimental causes an immediate GPU ring timeout and full system hard-lock when reaching the in-game main menu / Daily Rewards screen. The display goes black, flashes random colors, and loses display input signal.
This is a regression, as switching back to Proton 11 (Stable) completely resolves the crash and the game runs normally.
Kernel Log Analysis (journalctl / dmesg excerpt):
The crash is triggered by an illegal opcode in the command stream submitted via DXVK/Mesa, causing an amdgpu page fault that wedges the compute queue (comp_1.3.0) and fails a BACO reset on Navi 10:
Note regarding PROTON_LOG=1: Because this bug causes an amdgpu driver reset failure that hard-locks the host OS, file buffers do not flush to disk, resulting in an empty steam-1815300.log. The kernel dmesg log above captures the fault sequence prior to the freeze.
Reproduction
Set Compatibility to Proton Experimental.
Launch A.V.A Global (AppID 1815300).
Proceed past character creation to the main menu / Daily Rewards screen.
Result: GPU faults on command submission (dxvk-submit), monitor loses signal ("No Input"), and host system hard-locks.
Set Compatibility to Proton 11.
Result: Game runs smoothly without crashes or page faults.
Compatibility Report
System Information
I have tested this issue against the following versions:
Symptoms
Running A.V.A Global on Proton Experimental causes an immediate GPU ring timeout and full system hard-lock when reaching the in-game main menu / Daily Rewards screen. The display goes black, flashes random colors, and loses display input signal.
This is a regression, as switching back to Proton 11 (Stable) completely resolves the crash and the game runs normally.
Kernel Log Analysis (
journalctl/dmesgexcerpt):The crash is triggered by an illegal opcode in the command stream submitted via DXVK/Mesa, causing an
amdgpupage fault that wedges the compute queue (comp_1.3.0) and fails a BACO reset on Navi 10:Note regarding
PROTON_LOG=1: Because this bug causes anamdgpudriver reset failure that hard-locks the host OS, file buffers do not flush to disk, resulting in an emptysteam-1815300.log. The kernel dmesg log above captures the fault sequence prior to the freeze.Reproduction
1815300).dxvk-submit), monitor loses signal ("No Input"), and host system hard-locks.