Are you using the BES program? Is this application reliable? I would appreciate it if you could tell me some details.
I will do more tests after I am done with work so today in the evening. As for BES being reliable. It didn’t blow up my PC and it seemed to pop up in several tech forums. Thought, when installing it, Windows will show a warning because it won’t know the source.
Alright, I installed BES and ran my first test. I set the CPU limit to -10%. I did more than 7-8 teleports and even played Infernal Hordes with a full 4-player party. Normally, I would always get the black screen issue, but this time it didn’t happen. Of course, I haven’t fully tested it in detail yet, but even these early results made me really happy. Guys, try BES and share your results on the forum. For now, it seems like the issue is fixed for me. I will do more extended testing later and share an update.
1 Like
So let me get this straight:
We are using a tool to lower the game’s demand on the CPU in order to keep it from visually crashing with a black screen/UI?
That would lead back to something amiss with how the CPU is handling instructions.
Now.
What I would like to know, is how many of you are running AMD CPUs with this issue vs Intel CPUs with this issue and have an AMD GPU installed in either case?
For all of you, the official source of this tool is the following:
https://mion.yosei.fi/BES/
Always verify your sources, as I have done for this one. Always scan the download for any problems before using it.
This site has documentation relating to development, as well as a FAQ page on use.
Not necessarily… taking how some diagnostic logs have been seen where the client->server communication shows there seems to always be a timeout.
“My guess” is that, “something” on the code when using AMD GPUs is causing a thread starvation issue (or a max CPU): the thing is not necessarily lowering the power… the way BES works is by suspending and reenabling the threads quickly (so much that you don’t notice) but that leaves the thread scheduler free to complete their things, so the race condition/starvation doesn’t happen.
When a thread starvation situation occurs, there’s no free thread in the Diablo client code to send keep alives to the server (so it timeouts the connection and then weird things occur because it’s not even handled properly by the client)
This is still a bug in Diablo code happening when running on AMD GPUs… this is a workaround which seems to work, but it definitely doesn’t mean the actual CPU is the problem
3 Likes
Running BES @ -10%
2 1/2 hours with no black screen after teleport. That’s a typical D4 session for me.
Significantly reduced lag/lockups after teleporting. Usually my system lags/locks up after teleporting until D4 finishes whatever it was doing (asset loading?). The lag/lock would get steadily worse on each teleport until the final black screen. With BES there was just some minor lagging for a few seconds.
Note to Blizzard. This is still on you to fix. No money spent on D4 until the issue is resolved.
4 Likes
its been do this on pc for a year.It got a little better then patch and every travel your booted. my rig has all the needs to run it but nope constant disconnect every patch.
Believe it or not, this makes a lot of sense, especially when I would see a lot of communication errors in many different player logs even on systems that were more or less working just fine.
Some processes must be so resource priority hogging, they starve others of needed time and things time out.
Since this game uses multiple connections to more than one server while gaming and when you change zones, such as teleporting, it makes sense.
Prior to this, my concern was if this applies only to AMD CPUs when an AMD GPU is installed or if it also was affected on Intel based CPU that also ran AMD GPUs… That was the point of my question.
More importantly, its entirely possible this could be the reason the game runs so bad on so many systems, even outside of this one issue.
Man.
Mind blown here.
1 Like
Here is how I FIXED it
I had the same problem since VoH release
First Step: AMD Smart Access Memory (SAM) in your AMD Adrenalin Driver needs to be DEACTIVATED. Go to BIOS and deactive it. In YouTube there are several videos how to Deactive SAM in BIOS.
Second step:
Disable MPO in your Windows in the “regedit”.
In YouTube there is a Video called “Disable MPO to fix Intel, Nvidia & AMD stuttering, black screen, flickering issues on Windows”
it takes only 3 minutes to disable MPO
Last step: Go to Documents > Diablo IV and delete “LocalPrefs”
Now start Diablo IV and the blackscreen after few teleport should be gone
sry for my bad english, I’am german
2 Likes
So bad that you contradict yourself. And it all doesn’t work and has been discussed 100 times.
I have a box with an AMD GPU with an Intel processor (blackscreens), and a nVidia GPU on a Ryzen 3 CPU box (works fine).
The AMD GPU (not CPU) seems to be the common issue
tried this, it actually works on me. disabled resizable BAR support in BIOS (easy peasy, takes 1 minute), and been doing that incursion event for like 2 hours, no black screen any more.
thanks very much.
I will definitely try BES in a bit, thanks for the suggestion.
I was too happy too soon. I played for roughly 6 hours, and finally I got a black screen.
2 Likes
Have the same Problem since the expansion. This Post was very helpful.
I installed BES (set D4 to -10%), and i am playing now for 2 days (arround 6 hours) without any Blackscrenn Problem.
You have to start BES and set the Limiter everytime you start the game, but it seems to be working.
Thanks a lot !
I had also been having this exact type of disconnect all the time, no matter what I’d tried (ie, everything mentioned in this thread this the start), but this BES tool seems to have done the trick. I’m probably jinxing myself, but I haven’t had a town portal disconnect in two days. I also set D4 to -10% in the BES tool. The relief is real
2 Likes
same here.
With the BES Tools all works fine since 3 Days.
Blizzard knows now the Problem, but no fix.
But pay more and lets us milk like a Cow with the new BattlePass is fine and comes first.
1 Like
Oh good it’s not just me having this issue. AMD here too. Exiting the game is the only fix. Seems to happen randomly while teleporting. Sometimes teleport works, sometimes it doesn’t.
Ryzen 5 5600x
Radeon RX 6700 XT
h t t ps://imgur.com/a/g6M3LAu - Stupid forms have an embedded link feature but you can’t actually post links. How dumb is that.
1 Like
Use ( ` ) backtick before and after your link
or
paste the link, highlight it, then use the </> icon at the top