Diablo 4 crashes on startup

Support
1

I’m trying to run Diablo 4 after the update for season 14 that went out today. I did the usual thing and swapped some runners around but then gave up after the 4th one.

Battlenet opens and runs fine with everything that I tried except GE-Proton9-27 (with that one bnet throws an error and refused to load the game library).

I couldn’t get the log to output anything for the latest version of wine staging up on kron4ek’s github. (It said something like process exited with code 0 even though the bnet launcher was currently running well. The game failed to launch in the same way as the other runners I tried though.)

I think I was just using GE-Proton 9.23 (it was whatever the default was set to when I installed the game a couple of months ago) but it chucks out the same error with GE-Proton11-1 (the newest one I could find) set as the runner.

...
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
XALIA WARNING: Unable to release element hwnd-30138 from parent hwnd-20130--1
2

Hello :slight_smile: The game crashes on startup for me, too.

I am currently trying different angles to fix this and will report back, when I find what’s causing the crash on my machine.

3

Root cause (confirmed via PROTON_LOG): The game dies inside diablo_iv_loader.dll (Blizzard’s anti-tamper loader) , it hits a BREAKPOINT (INT3) and Blizzard’s own crash handler aborts ( / Summary: BREAKPOINT). This happens before any graphics init (no D3D12/VKD3D, no Vulkan device creation).
This error is consistent across machines.

What it is NOT (all ruled out):

  • :x: GPU/driver — no Xid, no VK_ERROR_DEVICE_LOST; the Proton helper process uses the GPU fine

  • :x: Shader cache (cleared it)

  • :x: File integrity (verified)

  • :x: Proton version — fails identically on Proton Hotfix, Proton Experimental, and GE-Proton11-1

  • :x: Steam overlay (disabled it) / LocalPrefs reset

4

Hey, just wanted to add a comment.

After the latest D4 update through battlenet, the error message changed when trying to launch D4.

D4 is now running with Proton-Experimental - but tends to freeze while playing
Turned off BattlEye Anti-Cheat, which seems to have fixed the freezes.

I choose to duplicate battlenet in Lutris, right-click and Configure. Switch to the Runner Options tabs. Set Wine version to Proton-Experimental, disable BattlEye Anti-Cheat, Save. Launch D4 though the “new” battlenet

And yes, i guess i will be switching between battlenet’s for blizzards different games. Not a perfect solutions but hopefully just a temperary fix :wink:

Hope it works/helps.