Agree. I froze twice today.
1 Like
Just to tune in, I also freeze from last 2 patches.
Now playing without sound and using Starcraft II *.dll and game not freezing.
Would really like to get this issue patched/fixed.
1 Like
Swapping files is not a fix by any means, worst case they could put a tick box in game to ACTUALLY disable the sound engine, the option in game only mutes, so bug persists.
They need to update the fmod and move on, reading on fmod forums it does not appear to be to difficult to accomplish.
2 Likes
July 20th was our last blue response. Pretty sad. Still having random freezes.
1 Like
Same problem here, freezing and disconnection… (Mac OS Catalina)
1 Like
No, it wasn’t. They made posts in August and September 2020.
I explained this about a dozen posts ago… here.
Regardless, it’s pretty shocking that they haven’t even updated the thread in six months, for a problem that’s rapidly approaching its anniversary.
Can we please get an Update on this issue?? nearly 6 months since the last update.
Thanks in advance
1 Like
My partner and I both with different PC builds started having this issue as well a few weeks back. It makes rifts near on impossible at times …screen freezes between 5 seconds and 15 seconds or more and when you are back you are dead… makes meeting the time near on impossible and makes playing pretty miserable.
Hello - I lost 7 hardcore characters this season (22) to about 10-15 seconds freezes. All of them were while playing with friends in greater rifts. No freezes in anything else for me and it never happened before this season personally. As about now Hardcore is officially unplayable. I’ve heard that the bug is still here in the new version ptr 2.7 but there’s a LOT of maintenance and shutdowns of the test servers. Which I think could mean they are working hard on something… It could be this bug we never know.
If they were working on it, they would at least acknowledge it and update us. S23 looks to be a quiet one for me 
2 Likes
I’m not PC expert but I’m pretty sure it’s not an issue with the computer as ppl have different hardwares/softwares installed/different version of Windows. Don’t think it’s from internet/wifi lagging either because ppl have different internet service provider/different modem & wifi router etc. For those who are also having this freeze issue, the only thing in common is that we play D3. So where do you think the problem originate from?
2 Likes
Did you read any of this thread. The problem relates to Blizzard using and old version of FMOD, the new Windows 10 update has caused this out of date file to become an issue. Blizzard can update FMOD but it could be a a large task. One would hope they are working on a fix atm, but don’t hold your breath as they wont even acknowledge the fault.
Guys and girls this thread needs attention, please post here daily until we get a answer from Blizzard!
Okay.
- I’m running Windows 10 Pro 64-bit, Version 20H2 (OS Build 19042.870).
- I’ve completed Season 22 on all 3 Regions.
- My
fmodex.dllandfmodex64.dllfiles are Version 0.4.34.20 - I am running D3 in 64-bit.
- I am not experiencing freeze issues.
Blue post… fixed topic… a lot of bla bla bla and the solution doesnt not exist… if you doesnt know how to fix, at least give us some position about anything… we are asking for help about this issue for more than one year… its a shame!!
5 Likes
Fine. The new season is starting soon and the blizzard still hasn’t fixed the bug. Thank you.
4 Likes
I am running Window 10 Pro 64=bit Version 20H2 Build 19042.870
Only completed one region
Both my FMODs are 4.34.20
I am running in 64-bit and have ran it in 32-bit
I AM experiencing freezing issues, can happen multiple times in one rift, or go several without it happening, can happen in bounties as well. Ryzen 2600X, 32gb ram, AMD 5700 8GB evoke card, game installed on m.2 NVME Samsung 970 Plus 1TB and have tried on standard hard drive as well.
This issue is still happening as of today for me. I implemented the replacement .dll file without sound and that solved my problem. I had to modify my pathways for the Diablo III folder, and I added an exit command, so it closes the terminal window automatically, but if you launch using that custom .bat file, it works fine. Have your sound enabled and when it launches, you should hear nothing. That’s how you know it worked.
@echo off
copy /Y "{Path to}\Diablo III\x64\fmodex64.dll.new" "{Path To}\Diablo III\x64\fmodex64.dll"
cd "C:\Program Files (x86)\Battle.net\"
Battle.net.exe --exec="launch D3"
exitThis works well but why should we play with no sound and also break T&C’s -modifying files? A year after the fault started they should have implemented an approved work around until fixed.
4 Likes
Still 10sec-freezing… do something Blizzard…
6 Likes