Sanctuary has plenty of horrors already. The loading screen does not need to become one of them.
Diablo 4 has a black screen bug making the rounds again, and this one sounds especially miserable because it tends to hit right after teleporting. According to Blizzard’s own main black screen thread, players are getting dumped into a blank screen while the HUD, cursor, chat, or even music can still keep going in the background. In other words, the game is not fully dead. It is just dead enough to ruin your session.
What players say is actually happening
The reports are pretty consistent. Players say the bug often shows up after teleporting to town or other overworld locations, and the usual fix is the least glamorous one possible: close the game and start over. Several posts in the thread describe the bug hitting multiple times in a single day, with one player saying it now happens every time they play and another saying the game has become “basically unplayable.”
That is what makes this a real story and not just one grumpy forum post. Blizzard’s current PC Bug Report board still lists the black screen teleport thread among the most active Diablo 4 bug topics on April 6, with hundreds of replies and well over 18,000 views. That is a lot of people staring into the void, and not in the philosophical Diablo sense.
Why this one matters more than a random visual bug
A weird animation glitch is funny once. A teleport bug is different, because teleporting is basic Diablo housekeeping. You sell junk, stash gear, hit the occultist, jump back out, and keep the run going. When that loop starts randomly bricking the game, it wrecks the rhythm of play more than a lot of flashier bugs do. Players in the thread say the issue kills momentum, ends runs, and in some cases makes them want to stop the season entirely.
There is also a hardware angle people keep circling. A number of affected players list AMD GPUs, though not every report does, and no official Blizzard post in the thread has pinned the problem on one vendor. So right now, that part stays in the “possible pattern, not confirmed cause” bucket.
Blizzard has at least acknowledged it, but not fixed it
That is the current state of play. In the same forum thread, Blizzard support rep Joynueer asked players to send in FenrisDebug.txt logs by email so the team could narrow the issue down. That is better than silence, but it is not a fix, and players in the thread are clearly past the point where “please send logs” feels comforting. They want the game to stop eating teleports. Fair enough.
