no restore points system was fresh instaled a month ago
but thank you was worth a shot
Having the same problem, followed all the steps and within 10 minutes game froze, went into d3 debug and still getting FMOD Error sound not ready in 200ms
yes the 2004 update was giving me ingame freezes as well. Kept dying each time it unfroze again. Just uninstalled the 2004 update. Hopefully it is fixed now!
@Farmerkimber,
Since you play on Europe, I thought I should point out that there’s a helluva good description on the Europe English Technical Support forum… here: HugeRandom Freeze singleplayer&multi - #7 by NvRmoR3-2527 - Technical Support - Diablo 3 Forums
It’s not step-by-step but with that and all the material above… it should be more than enough. No one should have to spoon feed you workarounds for an issue Blizzard is already working on.
The fix is not disabling sound. The fix (for the freeze) is replacing the FMOD file with the one listed above in this thread which will disables your sound whether you like it or not. You then have to create a shortcut to the game so you are not using Battle launcher. Instructions are listed above in this thread.
Any word on if this will be fixed before the end of the season, or should I just give up and go play PoE for a couple months?
Replace dll works for me, that’s fine for me, I’ve been playing without sound for a long time, I prefer to play listening to heavy rock.
Disable the bnet client from auto updating D3, replace the dll … profit until they fix it. No special shortcuts needed.
Maybe Nvidia’s hotfix will help solve the problem for people with Nvidia graphics. Hotfix 451.85 The hotfix is intended to prevent freezing in many games
This problem does not have anything in common with the graphics driver at all. The external DLL that is used for audio mixing is causing DiabloIII.exe process to freeze.
4 posts were merged into an existing topic: Diablo 3 randomly crashing
That does not work. Battle net now sais there is an update available. I am not able to launch. So the shortcut is the best way
So replacing the DLL didn’t work for me. Still images are still there
Is there an estimate on when the hotfix can be expected to hit the server?
This is what I do.
Firstly, get the new DLL and copy it to your Diablo3 X64 folder and name it “fmodex64.dll.new”.
Create a .bat file from the line below.
copy /Y “C:\Program Files (x86)\Diablo III\x64\fmodex64.dll.new” “C:\Program Files (x86)\Diablo III\x64\fmodex64.dll”
After you launch the battle.net client it will repair Diablo3 and replace the fmodex64.dll file with the latest. So, run the .bat file you created above and then run Diablo3 from the launcher. You need to run the .bat file every time before launching Diablo3. You know it hasn’t worked when your game has sound.
How long does it take for a Billion dollar gaming company to come up with some solution to these freezes?
I freeze 2-3x per greater rift any any left solo or groups. Mine last 15-30 seconds every time.
The most strange part is that they are still researching the problem. Come on, how long does it take to install Windows 10 2004? Seriously?
Right this topic is a month old.
I get hit hard with this bug.
A bit more convenient is what I have been doing:
Copy the new fmodex64.dll to the Diablo 3 x64 folder and name it “fmodex64.dll.new”.
Create a .bat file with the following lines:
@echo off
copy /Y "C:\Program Files (x86)\Diablo III\x64\fmodex64.dll.new" "C:\Program Files (x86)\Diablo III\x64\fmodex64.dll"
cd "C:\Program Files (x86)\Battle.net\"
Battle.net.exe --exec="launch D3"
That will replace the dll file and launch Diablo 3 via the battle.net launcher. This will bypass the D3 login screen.