and don’t do that, i using 1909 and both eu and na stutter and rubberbad like hell. NA are worse with this, like 10 times more horrible then EU servers.
Dear Blizzard, when are you gonna fix that? Because if its changes in windows - MS are clearly not gonna change anything because of one game.
Game are clearly unplayable even on sc, i don’t want to imagine what happening on hc…
Hi - I am getting the exact same issue, but with WoW. The game is now completely unplayable.
I have had this freezing for 5-10 seconds ever since updating to windows 2004 as well. Thank you for the fmod replacement file that works flawlessly in the interim. Here is my D3Diag
https://pastebin.com/iZLkbLwh
Here is my DxDiag
https://pastebin.com/Dwctqc0U
Same here ever since patch last week game runs fine at 144hrz and then every 3 mins or so game freeze/shutter fps drops and hrz’s go to 20-30; then back to 144hrz and g-sync is fine for 3 whole mins.
Before i get a mod msg; updated nvidia/network and bios (was a pain but done) And no ryzer synapse software and windows 10 was recently updated automatically. So its either windows 10 update or blizzard update when all the issues started last week. Also happens in HOTS too.
After installing the NVIDIA GPU driver 451.48 and enabling the function of Hardware-accelerated GPU scheduling, the freeze time from FMOD error reduced.
Old D3Debug.txt (446.14)
|2020.06.18 23:28:05.917795600|FMOD Error sound not ready in 200ms|
|2020.06.18 23:28:09.037317500|FMOD Error sound not ready in 200ms|
|2020.06.18 23:28:12.139540100|FMOD Error sound not ready in 200ms|
New D3Debug.txt (451.48)
|2020.07.08 20:45:22.249232000|FMOD Error sound not ready in 200ms|
|2020.07.08 20:45:22.569906900|FMOD Error sound not ready in 200ms|
|2020.07.08 20:45:22.897240200|FMOD Error sound not ready in 200ms|
7 posts
It’s the same frequency for me with or without h.a.g.s. It’s seemingly random when FMOD error occurs and random how often.
Thanks! Replacing the .dll file fixed all of my freezing issues.
I had the same issues replacing the fmodx64.dll fix my problems but i have no sound now any way to fix the sound issue after replacing the file?
FOUND A FIX; its the windows background pictures (mine was set to slideshow every 1-3 mins to change pics). Once I set the background to solid color - freezing went away.
FOUND A FIX; its the windows background pictures (mine was set to slideshow every 1-3 mins to change pics). Once I set the background to solid color - freezing went away.
This wasn’t a cause for me as mine is set to change every hour. The freezing is more frequent than that.
Mine is not set to change at all and it is still freezing pretty frequently.
Is there any ETA on a fix for this or I am expected to play the whole season without sound?
I used the ‘workaround’ and it seem to solve the freezes, tho it indeed removes the sound. You can also use a ‘fmodex64.dll’ from another game that you have installed. For example Dark souls uses it too and seem to work fine.
Also make sure that you set the file to ‘read only’ in the properties. The battlenet launcher just ‘fixed’ the file and set it back to its old version.
Anyone try the new Nvidia driver to see if this might fix the issue? I saw this in the notes " Windows 10 Only Several games randomly freeze for a few seconds during gameplay"
Who is the one that needs to fix this issue? Is it Blizzard, Microsoft or Nvidia?
I tried three recent Nvidia drivers from 446.14 to 451.67.
v446.14 → freezing for 5-10 seconds
v451.48 → freezing for about 1 second or less
v451.67 → freezing for about 1 second or less
These can be identified by the timestamp of FMOD errors in D3Debug.txt.
I tried to most recent driver, no dice still long freezes associated to the FMOD error
I tried the new driver too. And nothing has changed, still get the 5 seconds freeze from time to time 
Hey All,
Same issue. I had started another thread as I didnt see this one. However rolling back for me is not an option as its a clean install. Also for the people that have had the install for more than 10 days their old windows install will get removed.
However I had run previously TechGPU while the game was running and you can see the graphics drop for about 8 secs.
(3 Columns are) GPU Clock [MHz] , Memory Clock [MHz] , GPU Temperature [°C]
2020-06-12 22:17:45 , 1980.0 , 1750.2 , 59.0 ,
2020-06-12 22:17:46 , 375.0 , 202.5 , 56.0 ,
2020-06-12 22:17:47 , 375.0 , 202.5 , 56.0 ,
2020-06-12 22:17:48 , 375.0 , 202.5 , 55.0 ,
2020-06-12 22:17:49 , 300.0 , 101.3 , 55.0 ,
2020-06-12 22:17:50 , 300.0 , 101.3 , 55.0 ,
2020-06-12 22:17:51 , 300.0 , 101.3 , 54.0 ,
2020-06-12 22:17:52 , 300.0 , 101.3 , 54.0 ,
2020-06-12 22:17:53 , 1470.0 , 1750.2 , 55.0 ,
2020-06-12 22:17:54 , 1980.0 , 1750.2 , 58.0 ,
Seams I may have solved my crashing issue where each time the game would crash there was a different error.
Okay so here’s what I did.
Step by step.
Success! no more crashing in Diablo 3 or weird FPS issues when attempting to use the fps limiter in game.
This happens to me every few rifts in diablo 3. There is no rhyme or reason except that I have not seen it happen in town. The game completely freezes for 5+ seconds and I am usually dead right after. Greater rifts are so hard when this happens all the time. I play in windowed mode and the entire window turns white with the windows loading wheel when it happens. The sound is a repeat of my last used skill which would be whirlwind. this is my DxDiag in pastebin.
ZmvA3Kjh