Diablo 4 Players Say PC Crashes Are Still Killing Sessions Minutes After Login

 

If Season 12 wanted to add survival horror, crashing to desktop was a weird way to do it

Diablo 4 has another technical headache refusing to leave the room. In Blizzard’s PC Constant Crashing after a few minutes of play thread, players say the game is crashing just minutes into a session, sometimes hard enough to take the whole system down. The thread started on March 15, 2026, and it was still active on April 8, which is usually a bad sign in a game forum. Problems that disappear fast do not keep bubbling back to the top three weeks later.

What players are actually reporting

The core complaint is ugly, but very simple: launch the game, play for a few minutes, and then watch it fall over. The opening report lists a high-end PC with an RTX 5080 and says the whole system crashes after a short time in-game, while later replies describe continued crashing even after the usual cleanup routine of driver updates, reinstalls, and general PC troubleshooting. That is what gives the story some weight. This is not one person trying to run Diablo 4 on a haunted toaster from 2012.

Blizzard is at least asking for fresh crash logs

There is one useful development here. In an April 1 follow-up visible in the same discussion, Blizzard asked players to generate and send new FenrisDebug.txt files after the team enabled “a few things on our end.” That does not mean a fix is here. It does mean Blizzard appears to still be actively chasing the issue instead of pretending the thread is decorative. In practical terms, the game is still crashing, but support is clearly still collecting evidence.

Why this one matters

Crash bugs always matter a little more because they flatten everything else. It does not matter whether loot is good, builds are fun, or bosses are finally behaving if the client decides your run has lasted long enough. And for Diablo 4, this is landing in a season that already feels a bit too friendly with technical problems. We have already covered how Season 12 lag complaints were getting worse and how the black screen teleport bug still refused to die. Add repeat crashes on top of that, and the season starts to feel less cursed by demons than by QA debt.

Right now, the best headline is still “not fixed”

That is really the story. The crash thread is still surfacing in Diablo IV’s current technical support listings on April 8, which makes it fresh enough to matter and unresolved enough to be worth watching. Diablo 4 can survive balance arguments. It gets harder when simply staying logged in starts feeling like the real boss mechanic.

Read More

Diablo II: Resurrected Players Say Repeated Disconnects Are Starting to Feel Like the Real Endgame Boss

Diablo II: Resurrected just had its patch-cycle mess with the Steam launch issue and the follow-up hotfix, so you would hope things were settling down a bit. Instead, a newer complaint is now bubbling up in Blizzard’s Technical Support forum, and this one hits a lot harder if you actually play the game the way D2R tends to demand: long sessions, careful farming, and enough patience to make a monk look impulsive.

A fresh wave of disconnect complaints is popping up

A new Technical Support thread posted on April 5 says repeated disconnects are knocking players out of online sessions mid-run, with one player describing an Uber Tristram attempt that died right as Uber Diablo was about to go down. After reconnecting, the portal was gone and the whole run was effectively wasted. That is not a minor inconvenience. That is Diablo II turning your prep work into smoke.

Why this one stings more than a normal crash

In a modern live-service game, a disconnect is annoying. In Diablo II: Resurrected, it can be expensive. The forum post spells that out pretty clearly: keys, organs, Terror Zone farming time, and the kind of slow solo setup that takes actual effort can all disappear because the session falls apart at the wrong moment. If you are farming online and the game drops you at the worst possible second, there is no graceful recovery here. Sanctuary is not exactly famous for refunds.

It does not look like a one-player setup problem

That is the part that makes this worth watching. By April 6, other players had piled into the same thread saying they were seeing disconnects despite stable fiber connections, and one said the day had been the worst so far with more than 15 disconnects. Another said switching internet source did not help, while one more reported the issue showing up every five to fifteen minutes after otherwise stable play. Blizzard’s Technical Support index also shows the thread as active on April 6, so this does not look like one random complaint that vanished into the void.

Right now, the problem is uncertainty

That may be the ugliest part of all. Players can work around a known bug. They can avoid a broken skill, skip a bugged quest, or put off a farm until a fix lands. What they cannot really plan around is the feeling that any productive run might get yanked out from under them with no warning. Diablo II has always been ruthless. It just usually tries to kill you with demons first. 

Read More