





















1
System Specs:
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:
amdgpu.dcdebugmask=0x10 amdgpu.runpm=0RADV_DEBUG=nomeshshaders, VKD3D_CONFIG=no_upload_hvv, VKD3D_LIMIT_TGSM_ALLOCATIONS=1, RADV_PERFTEST=gplCurrent 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.
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。