One of the most basic problems in any live-service game is still showing up the hard way
Diablo Immortal has a fresh crash complaint on the forums, and it is not the polite kind. A new April 5 General Discussion post says the player has been dealing with crashes for around two months, with the game closing completely while Battle.net stays open, sometimes in bursts of four to six crashes in a row before things calm down again for a while.
That alone would be enough for a service piece. What makes it more interesting is the effort the player says they already put in trying to fix it. According to the post, they reinstalled the game multiple times, checked GPU drivers, reinstalled Windows, and even tested the same Battle.net account on a different PC, only to see the same pattern there too. If that account is accurate, this stops looking like one cranky machine and starts looking a lot more like a deeper game-side or account-side problem.
What the player is actually reporting
The report says the crashes can happen across a wide spread of activities, including TR, dungeons, towers, vault, and more. The player also notes that there is no lag warning beforehand, no obvious slowdown, and no clear trigger beyond the fact that the crashes keep returning in clusters. That kind of randomness is part of what makes crash bugs so maddening. A performance problem you can reproduce is annoying. A performance problem that appears to roll dice first is much worse.
The same post adds a useful detail: the player says Blizzard support directed them to the forums and suggested a developer might need to look at it, with the player even wondering whether their character might be bugged. That is not proof of an account-specific issue, but it does show the complaint is not just “my PC is old, please help.” The player had already gone through the usual support loop before posting publicly.
Why this one is worth covering
This is not yet a giant multi-page meltdown thread, so it is fair to keep expectations in check. But it is fresh enough to matter. Blizzard’s Diablo Immortal forums show “Crash spamming me!” as an active April 5 discussion topic, and the general forum page places it among the latest live threads right now. That gives it enough immediacy to count as current bug chatter rather than some dead complaint from weeks ago.
It also lands in a broader environment where Diablo Immortal’s bug-report board is still active with multiple current technical and gameplay complaints, including interaction bugs, server-load issues, tracker problems, and update-related glitches. That does not prove all of those are connected to this crash issue, but it does reinforce that the game is not exactly having a quiet, spotless technical week.
A crash bug does not need to be flashy to be destructive
That is probably the cleanest angle here. Diablo Immortal can survive a weird tooltip, a messy tracker, or one confused event toggle. Repeated hard crashes are different. If players are getting dumped out of the game four to six times in a row across multiple activities, the real problem is not class balance or event timing. It is whether the session can stay alive long enough to matter. And that is a much uglier story than most patch-note bugs ever become.
