Latest Patch Black Screen with GUI still showing after teleport

I’ve played for roughly the last week without a crash. So for me at least the game seems better after their “stability improvements” or maybe with AMD 25.5.1 drivers. But I probably wasn’t seeing as many crashes as a lot of people on here. I’m still convinced this is a complex issue where lots of factors combine to cause the crash. Fixing one factor may alleviate the issue for one user but not others because they’re getting the crash for a different reason.

Side note: I haven’t used BES. So can’t put down the last week being crash free to that.

edit: Nearly forgot, the damned game is still losing memory though. Every time I shut down diablo I have less free RAM than when I started it. So I’m needing to reboot more frequently. Which could also be why I’m seeing less crashes.

Oh yeah it totally is multiple factors, but they add up to the CPU getting over-reserved it seems (maybe while waiting for VRAM space to free up, I don’t know). So like that issue’s still going to happen, but at least it sounds like BES is making it so the whole system doesn’t lock up while it’s working through the other issues which makes the game playable. I haven’t tried the BES thing myself since I just switched to playing on Xbox this season (getting used to a controller in this game is weird).

1 Like

A (likely) final update to this experiment track (added RAM; no BES):

After a week of play with the extra RAM, the following points can be made:

  • The extra RAM has definitely decreased the frequency of the crashing, but has not eliminated it.
  • The game is still crashing on average twice a day.
  • Possibly related: The game usually starts stuttering a bit a few minutes before it crashes.
    • It can also stutter and not crash, hence why it may be unrelated.
  • Higher numbers of people at the source of a teleport seems to make it more inclined to crash. Obviously it is unknown how many people are at the destination, but it has been noted that the Tree of Whispers as the destination increases crash chances too, and it usually has a few people around currently.
  • Desire to group with other people is at zero, as this seems to greatly increase the crash chance.
  • Desire to play the game at all is rapidly declining.
  • Desire to recommend the game to anyone is in the negative.

Hopefully this will help in the diagnostics, assuming anyone cares at this point.

2 Likes

Fresh black screen teleport, hit U and got Error Code 300035. Throwing this tidbit out there if it helps.

Has anyone tested Season 9 PTR yet?

Patchnotes:

We are disabling the DirectStorage setting to investigate performance issues. If you’d like to continue using DirectStorage to take advantage of faster load times on supported NVMe drives, you can re-enable it through these steps:

Open the Battle.net Launcher
Navigate to Diablo IV—"(Gear Icon) next to Play"—Game Settings
Check "Additional command line arguments"
Add: -enableds"

Check your chat log: Party Voice chat enabled…

But you’re not in a party

I don’t know if the current patch still has DirectStorage disable by default, but using -enableds + 1.24 DS modules seems to offer a very good loading of asset experience. A lot of the latency I’d experience after a map transition / travel has gotten far smoother, and haven’t had a black screen waypoint travel in awhile.

And I checked, the BNet client isn’t replacing the dll’s with 1.22. Something you may want to try.

It’s apparently 15 days since my last comment and I still haven’t had the TP bug since then.

I did have a single driver timeout yesterday (black screen everything locked up for 10 seconds or so), but the game recovered, I didn’t lose my connection and I was able to keep playing.

I did notice after that timeout I had two Diablo IV processes showing as suspended in Resource Monitor after I shut down the game. For me at least, it looks like when something goes wrong in D4 it leaves a new process suspended but consuming a chunk or RAM and virtual memory. These processes do not show up in Task Manager, just Resource Monitor. Killing the processes in Resource Monitor frees all the ram and VM back up.

I’ve been keeping an eye out for these suspended D4 processes since I realised it was happening and clearing them out. Maybe that’s part of the reason why I’m getting less (no) TP bug action.

Hope season 9 doesnt include new TP to black sceen feature