I don’t recall anyone having the problem using HDMI audio, at least I didn’t anyway when I tested D3 on my Win 10 installation (I dual boot as I built a hackintosh). Since nearly every motherboard uses some form of Realtek chipset, I’m curious to see if there are any correlations to either driver version, chipset version, or combinations of both that trigger this. I’d also be curious as to whether disabling the Realtek device in the device manager stops the freezes. If so, then it would indicate a conflict between realtek’s drivers and FMOD’s more recent versions.
Changing drivers has no affect nor does disabling the device in device manager. I have tried HDMI, USB Atmos headphones, removing and disabling sound in windows, only fix is actually disable game in sound.
D3 hasn’t frozen the past 2 days GR 110-125, since I reinstalled AMD 21.4.1 driver only. Didn’t install package. Am still using default D3’s FMOD. Installed MS generic sound driver. Turned off sleep / hibernate (Win10 power setting). D3 video low/off, low fx enabled, vsync enabled. D3 sound 16, stereo, enabled but set to “1.”
Doesn’t anyone else see this as a problem? The fact that this person had to go through about 10 different steps JUST TO FIX an issue that a multi-billion $ company won’t fix.
Those of you both having this problem or not having this problem, take the time to visit this thread and complete the two quick surveys. I’m trying to gather some data to find a common link to what might be responsible for this problem.
A friend of mine had the same problem and it got fixed when he reduced the amount of sound channels. For testing I raised the amount of mine and it started freezing, not as hard but it was still very annoying. But reducing the amount of sound channels to 32 works for the both of us. I hope it will help you aswell!
I am having the same freeze 5-15 seconds in greater rifts over 100 solo or group play. I disabled my realtek sound on my Asus Maximus Hero IX and installed a new SoundBlaster AE-7. It did not solve the problem. Clearly the problem exists with Blizzard. The game is barely playable and not fun in group play when the freeze occurs.
I fixed this in a different way. I rebuild my old PC with witch i played D3 in the past. It consists from 3570K cpu 270x gpu Windows 7 64bit. On this PC diablo never freezes. I play Firebird Wizz. Also on this computer the game has even mutch more fps on higher settings then my actual 1800x 1080ti win10 one. Sadly it has some other problems like you must set the Battlenet launcher to 32bit in Safe mode(took me time to figure it out,in normal mode the launcher crashes so fast in sucsesion that you cant go to settings). Also the radeon driver likes to crash and restart witch happen maybe once per play session. Still mutch more playable then on modern PC
I have played a lot of games over the years. D3 has had it’s moments with lag in areas, like when in multiplayer, but never in my years 1982 since I was given a Dick Smith System 80 have I experienced a game where you have to modify the programs sound or cpu files to make it playable.
Yes I have had to lower settings, but never knowingly and with knowledge by the programmers and providers had to alter some code to make it work efficiently.
They have blamed windows yet I have not heard of any other game with freezes due to FMOD errors.
I am not going to play without sound, and I am not going to lose another HC toon.
So, I am going to boycott and check back in a month to see if there is a blue post about a bug fix.
IMO, Blizz are too busy working on D4, D2R and D Immortal to waste time on D3. Just my opinion.
Please don’t hold your breath as you will wake up in the emergency room.
Blizzard has had the problem listed by thousands for two years and no fix nor any info regarding it except for them saying to not use the fmod fix.
The Fmodx64 fix works for me and I am mainly HC.
Another problem I’ve had for last 5 - 6 years is when ever I launch the Battlenet launcher I get a Windows error message window that says, “a undefined USB device has been unplugged.”
Battlenet has many Windows issues and does not know how to fix them.
I have a scary feeling that we are looking into this more then Blizz is…
We’ve heard NOTHING about this in the past patch notes yet almost everyone is affected by it on PC.
Blizz, do you “hear us”?
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)
PTR notes have nothing logged for bug fixes. LAckOfVision has ruined Blizzard.