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.
- Right click your desktop and go to display settings.
- on the primary display page scroll down to Graphics settings
- Open graphics settings then uncheck Variable refresh rate.
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
Ok so i tried the replace Fmodex64 file with the one i had in my Heroes of the storm folder! And that fixed the problem! No freezing, just played for 4 hours but now i dont have any sound, but that is okay! It’s better than having the screen frozen all the time… Only sad thing is that i now have to replace the file everytime i want to play diablo since the launcher fixes the file hvem i close the game…
I have another potential solution. I did two things so I’m not sure which one fixed it. in the windows graphics settings (just search graphics settings in the type to search next to windows logo) choose diablo 3 from the dropdown/browse and set it to “high performance”.
Second, I have radeon software so in that app I set Performance > Advisors > Select gaming.
I played over an hour and no freezing at all.
edit: confirmed, played for 4 hours and no freezes. How bizarre.
edit2: freezes have come back… dunno why but when I had no freezes that was the longest stretch of diabo 3 I have played with zero freezes
1 Like
You can changed the file to “read only” or launch diablo 3 from a shortcut. Directions are listed previously in this thread.
I like the way you use .you help me at this moment.Thanks!!
I fixed this by launching the game directly. Stop using the battle net launcher for now, make shortcut directly to Diablo 3 64bit file. Add the argument ‘’-launch’’
My shortcut looks like this:
“\Diablo III\x64\Diablo III64.exe” -launch
You will need to log into diablo everytime. Make sure your reagon is set correctly before you acctualy login. this is done by going into the option before you login
1 Like
I set the region as well in my shortcut
“\Diablo III\x64\Diablo III64.exe” -launch OnlineService.Matchmaking.ServerPool=AU1"
What are all the possible server pool names for US regions?
Hi - Where did you get the replacement file from? Another game? What if you dont have any other non blizz games to take from?
I shared a link up top.
Any actual fix to this yet . Its quite frustrating
3 Likes
no fix only this workaround that does acctualy work. But it breaks your sound for the time being
I got the same issue with the Windows 10 Pro 2004. I am using the latest ATI driver and i got some freezes for 5-10 seconds. I got an USB DAC audio and a monitor with variable refresh rate if this matter.
This problem was absent in 1909. It’s really annoying. Blizzard, please fix this.
I do find it interesting that in d3 the fmod file is version 4.31.4 however the HOTS version is 4.44.23. In fact so much so that they call that at the end of the filename. It would appear that blizzard is pushing out the older version of the file with their d3 install
Some tests I did last night. This is with 451.67 of the Nvidia driver.
Variable refresh rate on or off made no difference.
Offloading the processing to the GPU via Hardware-accelerated GPU no difference
In a 105 GOD run for about 2:30mins I had 4-5 lockups it was a mess.
The GPU Clock is running at 1980, then the lockup occurs for 13s
Date , GPU Clock [MHz] , Memory Clock [MHz] , GPU Temperature [°C] , Memory Used [MB] , GPU Load [%]
2020-07-13 20:37:15 , 1980.0 , 1750.2 , 59.0 , 3335 , 25 ,
2020-07-13 20:37:16 , 780.0 , 1250.2 , 57.0 , 3344 , 6 ,
2020-07-13 20:37:17 , 570.0 , 1250.2 , 56.0 , 3347 , 12 ,
2020-07-13 20:37:18 , 450.0 , 202.5 , 55.0 , 3347 , 16 ,
2020-07-13 20:37:19 , 375.0 , 202.5 , 55.0 , 3347 , 21 ,
2020-07-13 20:37:20 , 645.0 , 202.5 , 55.0 , 3355 , 32 ,
2020-07-13 20:37:21 , 645.0 , 202.5 , 54.0 , 3355 , 31 ,
2020-07-13 20:37:22 , 750.0 , 202.5 , 54.0 , 3365 , 28 ,
2020-07-13 20:37:23 , 750.0 , 202.5 , 54.0 , 3365 , 24 ,
2020-07-13 20:37:24 , 690.0 , 202.5 , 54.0 , 3365 , 26 ,
2020-07-13 20:37:25 , 690.0 , 202.5 , 53.0 , 3365 , 26 ,
2020-07-13 20:37:26 , 540.0 , 101.3 , 53.0 , 3365 , 19 ,
2020-07-13 20:37:27 , 735.0 , 202.5 , 53.0 , 3365 , 36 ,
2020-07-13 20:37:28 , 735.0 , 202.5 , 53.0 , 3365 , 18 ,
2020-07-13 20:37:29 , 1980.0 , 1750.2 , 56.0 , 3365 , 44 ,
Your GPU load drops because it’s not in use. The FMOD error seems to be freezing the Diablo 3 process (the freeze we’re experiencing). It’s a causation and not correlation. It’s not Nvidia driver issues. It is most likely incompatibility issues that was not caught with the last version of Windows 10.
1 Like