May 10, 2026, 12:48am 1

System Specs:

• OS: CachyOS x86_64
• Kernel: 7.0.4-1-cachyos
• CPU: AMD Ryzen 5 7500F
• GPU: PowerColor Radeon RX 9060 XT 16GB (Navi 44 / RDNA 4)
• RAM: 32GB Corsair Vengeance DDR5 (CMH32GX5M2E6000C36) @ 4800MHz JEDEC
• Motherboard: MSI PRO B650-S WIFI (BIOS 1.N2, March 2026)
• PSU: CoolerMaster MWE Gold 850W
• Display: 2x monitors via DisplayPort
• DE: KDE Plasma 6.6.4 on Wayland

The Problem:
Diablo 4 launched via Lutris/Proton causes random hard system reboots with zero log trace. No MCE errors, no amdgpu driver timeout, no GPU reset message — the system just instantly dies and reboots. Other games (e.g. Borderlands 4) run completely stable at stock GPU clocks for hours with no issues.

What the logs show:
After extensive investigation, the previous boot logs showed:

amdgpu 0000:03:00.0: MODE1 reset
amdgpu 0000:03:00.0: GPU mode1 reset
amdgpu 0000:03:00.0: GPU smu mode1 reset

And on boot:

amdgpu 0000:03:00.0: [drm] REG_WAIT timeout 1us * 150000 tries - optc401_disable_crtc line:237

The Diablo 4 Fenris engine log simply cuts off mid-session with no error — the OS dies underneath the game before it can write anything.

What I’ve already tried:

• Updated BIOS to latest (1.N2, March 2026 — fixed initial data fabric sync flood)
• Added kernel parameters: amdgpu.dcdebugmask=0x10 amdgpu.runpm=0
• GPU power cap via LACT (130W) — reduces frequency but doesn’t eliminate crashes
• Lutris env vars: RADV_DEBUG=nomeshshaders, VKD3D_CONFIG=no_upload_hvv, VKD3D_LIMIT_TGSM_ALLOCATIONS=1, RADV_PERFTEST=gpl
• Proton version: GE-Proton10-34 (pinned)
• DXVK enabled, VKD3D handling DX12
• RAM running at stock JEDEC 4800MHz (XMP/EXPO disabled)
• rasdaemon running — captures zero hardware errors during crashes

Current state:
The MODE1 resets no longer appear in logs after adding the kernel parameters, but hard reboots continue during D4 gameplay. No other game is affected. Crash leaves absolutely no trace in journalctl, dmesg, rasdaemon, or the game’s own Fenris debug log.

I believe this is an RDNA 4 + VKD3D/Proton interaction bug specific to Diablo 4’s DX12 rendering path. Crash report bundle attached.

Any help or pointers to relevant upstream bugs appreciated. Happy to test patches or provide additional logs.