I’m also hitting this on Bazzite after the Season 14 patch.
Setup:
- OS: Bazzite / Linux
- GPU: AMD Radeon RX 7900 XTX
- Kernel: 7.0.9-ogc3.2.fc44.x86_64
- Launcher: Battle.net through Steam as a non-Steam game
- Diablo IV version: 3.1.0.72592
- Battle.net successfully launches Diablo IV.exe, but the game exits after ~9-11 seconds and returns to Play.
What I tried:
- Let Battle.net patch the game normally
- Ran Scan and Repair
- Switched Proton versions:
- GE-Proton10-32
- GE-Proton11-1
- Proton Experimental
- Deleted the old Steam compatdata/prefix completely
- Reinstalled Battle.net into a fresh prefix
- Reinstalled Diablo IV fully into that fresh prefix
- Tried disabling NTSync:
- PROTON_USE_NTSYNC=0 PROTON_LOG=1 %command%
- Tried disabling DirectStorage DLLs:
- PROTON_USE_NTSYNC=0 WINEDLLOVERRIDES=“dstorage,dstoragecore=d” PROTON_LOG=1 %command%
None of the above changed the failure.
The fresh install is using GE-Proton11-1. Battle.net logs show the install completed successfully and the game is up to date:
- Diablo IV version: 3.1.0.72592
- Build/current version: 72592
- Battle.net launches:
- C:/Program Files (x86)/Diablo IV/Diablo IV.exe
- args: -nostreamline -sso -launch -uid fenris
Battle.net reports the game process starts, then exits about 10 seconds later.
The Blizzard crash report consistently shows:
BlizzardError.Summary:
BREAKPOINT
<:BlizzardError.Summary>
Stack:
DBG-ADDR<…>(“diablo_iv_loader.dll”)
DBG-ADDR<…>(“diablo_iv_loader.dll”)
DBG-ADDR<…>(“ntdll.dll”)
ntdll.dll RtlUserThreadStart+0
The offsets are consistent across old prefix, fresh prefix, reinstall, and Proton versions:
- diablo_iv_loader.dll + 0xEE4A05
- diablo_iv_loader.dll + 0x2A95C6
The Proton log shows the same thing:
Exception 0x80000003 / EXCEPTION_BREAKPOINT
inside diablo_iv_loader.dll
This does not appear to be a corrupted prefix or bad install. I reproduced it after deleting compatdata, reinstalling Battle.net, and reinstalling Diablo IV from scratch.