So i have an old laptop that i was playing diablo on and was wondering, is it posible to fix this issue with an old version of the file? A file from season 13 which worked fine back in the day. Just wanted to know if any1 have already tried this. I would like the game not to freeze but would like the sounds as well if possible.
Central to the freezing issue seems to be Diablo 3’s sound file (Fmodex64.dll). Replace using one from another Blizzard game. I use the one from Heroes of the Storm (fmodex64_4_44_23.dll). Demonstrates how to create batch for launching D3 executable. I have old desktop with i7-4790k for playing D3. Another thing to try is to install video driver only. Set D3 video options to low or off. Web search for D3 performance and windows guides.
Check Levithan’s YouTube posted by Gekke back in November 2020.
[[Diablo 3] How To Fix Major Game Freezes In Season 22 feat. Leviathan's First RIP + Update - YouTube](https://www.youtube.com/watch?v=prwf8lD9LfE&ab_channel=Leviathan)
I miss playing with sound.
2 Likes
AS usual a lack of response from a Blue, they7 only reply when they can blame our hardware lol
Can you prove and link this official response? It has been going on for WAY too long now.
1 Like
@METALHEAD:
(sorry - I got carried away)
No update since 10-Sept-2020.
Take a look here for a detailed description of what might be the problem…
I don’t know if all of that is factual… but it kind of make sense to me. It would explain why only players on recent Windows 10 builds are having this issue when others, such as me running 1803, don’t. It would also explain why players switching to Windows 7 or using a dual boot with a Windows 10 build prior to 2004 don’t have the problem. It could also explain why @Crinel and @Crusader are not seeing the issue in Windows 11.
The thing that bugs me is… why doesn’t Blizzard come out and say what the issue is… especially if it’s something they have no control over such as the various Windows 10 versions.
3 Likes
Blizzard blamed AMD for Act2 Desolate freezing years ago. Blizzard based their coding on AMD guidance. AMD eventually patched it after months and months. Now Blizzard is blaming Microsoft for sound file freezing issue. Quite a few are using a fmodex64.dll work around. I use the one from Heroes of the Storm.
Just another MS patch, but not a cure all. [Microsoft releases KB5004296 update for Windows 10 to fix game performance problems and more (betanews.com)](https://betanews.com/2021/07/30/microsoft-releases-kb5004296-update-for-windows-10-to-fix-game-performance-problems-and-more/)
they will never fix this , if it’s really a microsoft problem and they fix it then Blizz will just blame someone else and not fix it 
Most likely because of future collaberations, its bad to blame Microsoft because you will allways have to work closely with them for future projects.
And its weird as Developer to suggest your customers to install everything but the “newest” windows version.
I have a intagraded sound system on my win 7 computer. I have had fmod sound not ready 200ms for ever. I have tried most, but not playing with no sound.
New video cards, diffrent video cards. i have a i7 cpu tried the affinity option, i thought that helped but still chattered and fmod sound not ready200ms
Well I bought a creative AE-5 X with it’s own power to the sound card. This worked, I just installed no driver. Then went to windows control panel (sounds) and disabled othes sound systems. Then had to set it to second lowest settings and diable the enhancments, and let app take control. No fmod sound not ready in 103 griffs, I get allot of 3ms to 45ms sound READY. No chatter or freezing.
Dont reply to MealHead , Hes to involved in trying to BAN the BOTTERS lol
I don’t believe this statement has an ounce of truth to it.
The only response I saw from Blizzard concerning the Fmodex64.dll fix was that they strongly disagreed with using it.
And they said, “This appears to be a windows issue and there is nothing we can do about it.”
and yet they have created an entire PTR to try and resolve it 
1 Like
because blizzard hope all of D3 players not playing d3 anymore;so they can stop servers ;and we need to buy D2 and D4 ;and then they got more money 
makes no sense this statement lol
I had posted an update here last night regarding the surveys I had up:
If anyone was interested in seeing those.
| 2021.08.09 07:30:09.528374100 | FMOD sound ready after 200 ms |
|---|---|
| 2021.08.09 07:30:09.528472900 | FMOD Error sound not ready in 200ms |
| 2021.08.09 07:30:12.603570600 | FMOD sound ready after 200 ms |
| 2021.08.09 07:30:12.603661200 | FMOD Error sound not ready in 200ms |
| 2021.08.09 07:30:15.678771200 | FMOD sound ready after 200 ms |
| 2021.08.09 07:30:15.678860400 | FMOD Error sound not ready in 200ms |
wonder if blizzard care at all? dont think they do
1 Like
1 Like
Same here too, but my freezes break the comp, bluescreen or necessary hard shutdown. Franky, I can’t be arsed to turn into a specialist fixing this. I’ll just head back to ESO and wait for New World.
1 Like
we try all what knowed. we finish 147 with 2 sorc 2 weeks ago, but today we cant clear 145 with zmonk/zdh/zbarb (with uliana, without uliana)