PTR Pop-Up | Focus on Freezing Issue | Has Ended

Just a note about the D3Debug.txt file.

Only the most current play session is logged in the file. In other words, if the game client is closed and reopened, it will overwrite the previous log.

So when a freeze happens, be sure to submit the D3Debug.txt file before the next play session. AND be sure to post the D3Debug.txt of the PTR (in the “Diablo III Public Test” folder, not the one from the live game!


Hello @FilthieRich,here is the link for the Pastebin page where I wrote my D3Debug code as you wanted it (D3 Freezes -

When I opened the x64 folder in my d3 folder I found this datai (fmodex64.dll):
where I used the as described in another post
I replaced datai by playing for a while and had no more still images
(freezes / lags)

I already have died 2 times because of that, with out any screenshots (I even made a farewell topic), for now I can only think about GR 75-80 or more+ (less level = almost no lags and death, very low probability do die), T15 or less, again low probability to be dead, due to the less people (bots) play one those difficulty levels (T16 have a lot people to play, bots and so on, so very high probability to die). Sometimes 4 and 5 acts become very laggy (if you try to play all acts from 1 to the last in adventure mode), but that has nothing to do with the personal computer memory and so on. Interesting fact is that Diablo can disable your internet card (or on mother board) or make it go baggy, but after some testing from the parallel PC (through the same router and so on), internet connections is always perfect, only Blizzard servers become unreachable and if you manage to kill Diablo in task manager, your Ethernet card becomes unlocked and works fine again… BTW, during one of the death, I got a tons of errors (more then 10) and then of course after 10 second of disconnect (connection loss) and (I tried my best to use some actions and so on) kick from servers, I got dead anyway… I would love to get hand on the logs to see what happened there for real… And the best solution for that problem would be for HC solo players would be offline mode (even temporal), because it’s not an honored death due to that bug… And final I haven’t used Firebird and Convention of Elements in this season before the first death only before second one I got Convention of Elements, but with out Firebird…

is the PTR live yet? It says theres a new patch available but as soon as the game quits nothing is applied or downloaded.

PTR Pop-up is now live!


My account snapshot is several days old, and I am only allowed 1 PTR copy per 24 hr period.

Wish I had copied from another server, or that I was allowed to try copying from another server instead of having to wait 24 hrs to copy again…

While I haven’t played the PTR. I will try my own test live. There might be a connection with the freezing issue and the D3D error that reads as follows. Diablo III was unable to initialize D3D. Click okay to retry. I will keep playing either season 24 or PTR and keep an eye on whether this has any effect on the freezing issue. I noticed this started happening a while ago. I don’t know how long. It might be as long as the freezing issue. If so and there is a connection then you might be able to figure out what is going on. I hope this idea helps. Regardless I will test things out myself on my end.

They may not get any useful information from your logs if you are not on the PTR.

If its not a bother, hopefully you can hop on the PTR to reproduce the issue and share the log. We have some configurations within the PTR to help us dive deep into the issue. Hope this reaches you well ShadowAegis!

1 Like

What I am wanting to know is does the freezing occur when the D3D error occurs. If it is yes and it is based on time then I can instantly conduct the test on the PTR the same way. Or if it happens on the PTR during the D3D error message I will then do as instructed. Still there can be a connection and that can be done without the D3 debug txt file.

I have never gotten that error and still have the issue. For me, it just started occurring this season and is definitely not related to internet issues as I play with someone else in the same household with a far worse/less powerful computer. He has no issues while I freeze frequently in our 2 player games even after I set my video options to low. Unfortunately, I can not do any PTR testing for 5 hours or so…

ShadowAegis, is that error accompanied with a blank grey screen?

I have gotten that for years, but it was never an issue, just hit retry. I never had any stuttering, crashes, lag, or anything negative along with that issue.

Played one GR as a standard FB Wizard. No major freezes, but constant stuttering when using Mirror Images and when the images use skills. The stuttering also happens in town, but only with Mirror Images.


Highlight your link and click the </> button, and it will allow you to post your link.

Like so:

1 Like

Mirror Images Firebirds T16:

Whirlwind-Barb Gr90:

Wizard was, as widely known, incredibly laggy and stuttering. Barb was only slightly noticable, but i do know that it is an issue when ground-stomping and manual rending into it on higher GRs (~130). Also the D3Debug has the same FMOD outputs like the FB-Wizard.
My GoD-DH GR90 Run only had like a handful of these outputs.

My Hardware:

  • i7-9700k
  • Gigabyte Aorus GTX 1080 TI Xtreme 11G (Driver v471.41)
  • 2x8GB G Skill TridentZ DDR4-3600
  • MSI MPG Z390 Gaming Edge AC

Do you want us to post D3Debug.txt files whenever we experience ANY glitches, or only when the game crashes or freezes?

What other information can we put in our post that might be helpful?

1 Like

Played Firebird Wizard Solo and the 10s freeze happened with sound turned off.

Log file


Just look at the end of the log:

2021.08.05 22:55:20.155796800	FMOD Error sound not ready in 3109.44 ms (loop count: 200)
2021.08.05 22:55:20.156025600	FMOD call duration total:  0.22 ms
2021.08.05 22:55:20.156214700	Sleep call duration total: 3109.15 ms
2021.08.05 22:55:23.259649900	FMOD sound ready after 3103.07 ms (loop count: 200)
2021.08.05 22:55:23.260004800	FMOD call duration total:  0.25 ms
2021.08.05 22:55:23.260205700	Sleep call duration total: 3102.76 ms
2021.08.05 22:55:23.260406800	FMOD Error sound not ready in 3103.07 ms (loop count: 200)
2021.08.05 22:55:23.260618000	FMOD call duration total:  0.25 ms
2021.08.05 22:55:23.260857200	Sleep call duration total: 3102.76 ms
2021.08.05 22:55:26.369948800	FMOD sound ready after 3108.74 ms (loop count: 200)
2021.08.05 22:55:26.370247900	FMOD call duration total:  0.22 ms
2021.08.05 22:55:26.370449000	Sleep call duration total: 3108.45 ms
2021.08.05 22:55:26.370698800	FMOD Error sound not ready in 3108.74 ms (loop count: 200)

It’s all because of fmodex64.dll, even with sound off. As you can see there are 3 consecutive loops for 3,1 seconds each, totally 9,3 seconds. In the beginning of the log the loop counts are in the range from 1 to 9, but in the last three the loop count is 200.

Sup Vita! Isolating the request specifically for the lag/freeze issue here. Thanks for checking in though!

1 Like