After reading a lot of posts on this issue, I decided to run the game on my old workhorse PC with the Windows 7 Premium operating system.
Surprisingly, I played a full, continuous 10 hours in Hardcore mode without a single stutter, freeze or disconnect. This is compared to my new, high-powered rig running Windows 10 which earlier in the day, froze 4 times in the space of an hour.
edit: Played 8 hours Wednesday, Gr 80 to GR 120, both solo and multiplayer without any problems whatsoever. Most enjoyable session of D3 Iâve had for months!
My thinking is itâs an old game built for an old operating system. So far, it seems rock solid. Though fmodx is part of the issue, I think Windows 10 is the ultimate culprit. Considering that every issue of Windows has been plagued with errors and problems, this comes as no surprise. Only every 3rd or 4th iteration of Windows seems to be adequately functional. i.e. Windows for Workgroups 3.11, Windows 7 and possibly Windows 11 as per Crinel above.
Iâll post again if this issue rears its ugly head in its ânewâ environment.
1 Like
Still working on this?
Even if you said you are I wouldnât believe it tbh. 1+ year later and this issue still exists and hasnât been solved.
1 Like
My 150 member clan is really frustrated with this âsound freezeâ. Most of the clan has stopped playing HC because of the issue. Is there any word for Blizz as to what is going on. Is it a Blizz issue or a Windows 10 issue? A simple question why no answer?
TLDR. I donât know if this was answered. With Diablo running, Open task manager>Details tab>Diablo 3>Right Klik and select set affinity>unselect all and select 1&2. close. You need to do that every time you log on. That should fix the micro freezes. You can play with sound with this fix.
this dosent work for me still the same
Hi Crinel,
with the W11 version 22000.1, Diablo 3 ran extremely well and very quickly, without errors.
With the W11 version 22000.65, Diablo also ran well, but I often noticed micro stutters.
Greetings from Germany. 
Happy belated birthday thread!
We understand you are a small indie company but 1+ year seems to be a long time to solve a game breaking bug guys.
4 Likes
So I take it the issue isnât going to get fixed on Blizzardâs end.
Thanks for the thousands of hours of gameplay though (actually playing).
Looking forward to D4! 
Hey guys (please excuse the 2nd rate english), i had this issue this last season⌠i play mainly support (Monk/DH in group) and DH (solo). I have found 3 fixes so far and right now i can say for sure that one of them works for me.
So:
- i found on youtube a thing with the TCP settings in registry - for delay and other things (i do not think it works)
- the FMOD file thingy (it does and does not work - one instance worked fine, the next it did not)
- my own stupid intervention
- after i opened the game i opened the task manager (i have win10) and found out that the blizz app launcher had 2 instances: one in apps and one in background. I asked myself âwhat is this?â (to the background process) âwill it kill the game? well⌠if it does i will open it againâŚâ i stopped that process and the game had 1 crash in about 6 hours of playtime⌠it was the game itself that crashed, BUT no lags what-so-ever. NONE! It might be that the launcher from the background was mainly at fault for meâŚ
I have the same problem with my new gaming PC. Blizzard PLEASE FIX THIS PROBLEM
Blizzard does not take care about you guys or this error.
It is still present after 2 years.
A fast and short solution can be to disable the entire sound for the Mirror images and spectral blades.
Seems impossible for Blizzard since they have no guys working on this. For this reason we have to disable the entire sound of D3 with the fmodex64 workaround which helps to prevent lags and disconnects but you have to play without soundsâŚ
Horrible what Blizzard is doing.
that is one reason why they are getting worse and losing players.
2 Likes
I believe they did NOT fix the freeze issue with 2.7.1. The fmodx64.dll is untouched!
If so this company is a disgrace to all faithful D3 playersâŚi canât put my frustration into words.
Even with 717 replies and nearly 85k views in this thread this severe game breaking issue is COMPLETELY IGNORED. Unbelievable.
I will never ever buy Diablo 4 if they handle âfixingâ important bugs in that manner.
UPDATE: Well done, STILL 5-10 sec freezes on my Razer 17" Notebook with mobile RTX 2080! Nothing happenedâŚNothing fixed. Thanks.
Replacing the fmodx64.dll again fixes this severe problem but you will have no sound at all. Looks like all the players that suffered from this problem are done with D3.
2 Likes
Thatâs when you buy graphics for a lot of money and AMD goes fine
Freeze is from game or server. You can do nothing until Blizzard fix itâŚ
Still happening all the time in Season 24
Having freezes that exceed 10 seconds now actually, lost a hc character to it, not sure if i can be bothered lvling another
omg when is this thing going to get fixed??? Lol⌠Waiting for an official fix from the D3 team.
Oh boy a new season! I canât wait to ignore it because this issue persists!
2 Likes
I had posted (much) earlier in support of the StarCraft 2 fmodex64 dll band-aid-ing this.
I just noticed (after getting booted) that an update today has put an fmodex64.dll file with todayâs datetime stamp into the x64 folder. Fingers crossed that this might be a fix???
Will be testing once I can get back in and report.
Yup still happening in season 24.
1 Like
