Diablo 3 keeps crashing randomly with random IDs like A4561AEB-538E-40DF-952E-53488AE8E313
Even if just standing around in town doing nothing. Intervals are bit random but I never played longer than 30 mins. Greater rifts, especially exiting after finishing them seem a lot more likely to crash.
The ids as shown above are always completely random (as some other guy reported, too).
And before you start:
It’s not my PC, really. I play on a a lean Windows 11 with nothing installed except steam and battle.net (stripped even Defender and Cortana, a light version just for gaming. So no DVR and other apps). Drivers are up to date. I watch power limits and temperature and I can play 12 hours of D4 or Cyberpunk 2077 on ultra without issues, basically D3 is the only game I have problems with.
I did all the stuff people recommended:
limit processor affinity to 8/10/12 cores (I have a 14900K and YES I patched my bios a few days ago to counter the power limit issues mainly seen in Unreal Engine games - which I never had a problem before anyway).
I set compatibility mode for the launcher and the main .exe to Windows 7
I tried all graphic modes, windowed, fullscreen, borderless windowed. Sound on and off, cycled through all the other graphic options, it’s not that.
Also I played Season 30 without a problem on this machine - yes I verified the game files, too.
I have no idea what else to try. I suspect it has something to do with the really fragile always on “no udp packet allowed to disappear” concept, but pure speculation. I play on a really stable 250/250 fibre connection and tracert and ping are fine.
Not quite… but they do change. And they change because they’re the ID for your crash data in the Blizzard Customer Support data system. The system treats each crash as a unique event, so yeah… each of the crash ID is different.
Go through all the suggestions in the folllowing Support article – you’ve obviously tried some of those… so only try those that you haven’t tried so far. The words in blue are links to additional info, procedures, etc… :
Also try this:
If the issue is still there… you should likely contact Blizzard Support directly with a ticket and provide them with one or several Crash IDs in addition to the information requested on the ticket form.
So after many hours I found the reasons and this might be useful to others as the hardware scenario could be common these days.
Apparently there are two problems affecting each other. One is a problem I found in years old reddit postings on r/d3, the other one is modern cpus with their e-cores.
I tried a lot of things and as I wrote in my original posting the only CTD game is D3. The first thing I noticed was that changing sound settings sometimes lead to an instant crash.
So having an Asus Z790 mainboard with a bread and butter Realtek soundchip you would never suspect this be a thing especially if you turned off - as in unchecking the box - the sound completely, right?
Dead wrong! There is (still!) a crash scenario in the 64bit sound engine in the fmodex64.dll in \Diablo4\x64. A lot of the sound related crashes here suggest turning to the lowest settings and 16 channels. That might have helped in the past but these days you have to exchange the 988.672 byte large “fmodex64.dll” with the most recent version found on trustworthy DLL downloads sites. Some people hinted you can use the one in the HOTS client but thats a huge download. Also be aware the patcher of course detects and replaces the newer version with the old one every now and then.
The second issue is a bit more work: apparently there are scenarios when I/O loads somehow gets scheduled on high number power cores or worse on effiency cores. Modern processors have two type of cpu cores and there are hard- and software scheduler mechanisms distributing load. The D3 engine apparently is not aware and can not handle this.
There are several ways to control the so called “CPU affinity” under windows. I found the most convenient one is creating a .cmd/.bat file on the desktop (needs to be launched as admin/(elevated)
(of course adjust the path to your copy of diablo3). You can also control this via the taskmanager in the details tab but that requires you do it manually everytime you play.
The above .bat calls the client directly. The “-launch” param makes it, so that the launcher is skipped. “affinity 3” means “run only on the first and the second power core”.
Ah one thing: if you launch the client directly you might need to choose your region the first time under “options”.
Hey @Dakriz - seems like you found the way, but when I launch it I get some spikes ingame, it does not crash anymore but I get lag spikes now?
I got i9-14900KF and 4090 graphics card so there should not be any lag spikes - I remember getting lag spikes like normal diablo sometimes gets, but it lags a little too much if it makes sense.
Im very happy that u found a solution for me as well, now its just the lag I need to get fixed
Hello,
I got the same problem that D3 randomly crashes all the time after geting a new computer. It works fine on the old one. Could you please explain more detailed how to make that CPU affinity please,
Im not that good with computer stuff
