Think I may have solved my issue by quite a bit by launching the game in 32bit mode instead of 64bit. Still some lag here and there but seems like it’s been reduced by about 75%. It helped me so figured it might help others.
Beside the play button open the options press game settings. Then click on Diablo 3 and look for a check box that says “Launch 32-bit client (instead of 64-bit)”. Check that box and launch the game to test.
I tried the fmodex64.dll fix mentioned in the thread and that did not fix it. Then I did a scan and repair for corrupted files on the Battle.net launcher and it worked! I’ve played for 3 days with zero issues, no lag spikes, no freezing/hanging, etc.
I saw how that did not fix someone else’s issues, but it worked for me. Go figure.
The 10 second death freeze just happened 7 times in a row with about 15 seconds interval on a grift level. I exited the level and then hopped back in and it way okay. Just odd since I’ve had zero issues yesterday.
Diablo 3 repair said: Scan complete, no repair required.
Having this same problem. Game freezes for about 3-5 seconds, then continues. Mouse still moves. Also having huge lag spikes where I can still walk around, but the game is stuck.
I have the same issue. Game freezes for 5-7 sec sometimes more than 10 sec and when it come back I find myself dead ! I will not replace anything and I won’t play Diablo 3 without sound ! Next step is to play it without video
Replacing the file works but its not fun playing without sound. For ME, the solution is to drop sound channels to lowest AND run the game process with only cores 0 and 1 using the set affinity function within task manager. This works every time for me and I still have sound.
The REAL issue is how this has been going on for almost a year without a fix and how the last blue post was July last year. Scary just low little they give a F about their games and community now.
This issue sucks. I hope they resolve it soon.
Applied the fix to fmodex64.dll, works fine for me. Before i had at least one freeze in each run, it is no longer the case.
At maximal load (e.g full party high level of greater rift), the Diablo 3 game will often lagg (taking some 5 seconds to fix itself).
My theory is that it is a sub-optimal configuration of the client PC that is causing a hickup. And the hickup will cause the networking code
to lose sync with the server and hence, 5 seconds freeze lagg required for resync.
So what could be the cause?
For the computer savy of the readers I give you some hardware settings to experiment with.
Please report back if you see any improvements in lagg.
Please also write if you have other settings that could be added to the list below.
Things to check ( disclaimer! do below at own RISK!) :
-
update OS, update drivers, update BIOS, GFX firmware, etc.
remove timer hardware bios -
Check computer RAM, are all the RAM sticks rated for the same speed etc
Check BIOS settings for RAM, is the RAM running at correct speeds, using XMP, undervolted or overvolted, overclocked etc?
Set BIOS RAM settings to safe compatible settings. -
Check BIOS settings for the CPU, is the RAM running at correct rated clock frequence, undervolted or overvolted, overclocked etc?
Set BIOS CPU settings to safe compatible settings.
Try with BIOS CPU power saving settings set to disable (disable altering the voltage and disable C-state of the CPU). -
optimise and test bios settings
Look through the BIOS settings, what can be done?
Try stuff like disable High Precision Event Timer and disableing unused io-ports etc -
GFX settings, try different settings like:
e.g. nvidia nvidia panel
vsync off
threaded optimizing (multithreading) off
Energy saving setting ( set to use full GPU, “optimal performance”)
Max picture frequence (set to hz of monitor, " 60 BPS" )
PhysX setting (try setting it to cpu or gfx, avoid auto) -
diablo 3 game settings:
video:
do not enable vertical sync
do not enable reflections
do not set max forground FPS
do not set max background FPS
texture quality - low
shadow quality - low
physics - low
clutter density - off
Anti-aliasing: none
enable - Low FX
enable Low FX
do not enable SSAO
sound:
disable sound (if it seems to work without lagg , enable sound again)
disable music
set sound channels to lowest
chat:
remove all chat channels and leave all communities
- setup proper network, do not use wifi, VPN, proxy, crappy cables, old routers etc.
- use network tools as ping, trace etc to verify good connection and no packet loss
- remove all necessary program that might hog resource
- remove and disconnect all necessary hardware that might hog resource
- clean dust out from pc, set all fan to spin at max
- buy more case fans and buy better cpu cooler and overclock cpu.
Just got this freeze on me, I thought my HC char was a goner, lucky it was frozen on good spot.
Trying out the fix now.
This bug is honestly a shame, bought the game to play with friend… Getting my computer freeze every 1 min… My PC is latest config on market… And having to look for Third party fix from community… When the issue remain for 6 monthes…
Honestly, i am shocked…
Got a recent PC, with fiber gigabit connection, all drivers updated. The only thing that fixed the problem was using a recent version of fmodex64.dll.
Actually, the issue has been happening for years, with a game freeze once you enter the game, most of the time. It was fixed by restarting the game.
The only thing that changed recently was that the freeze now happens every few minutes.
Someone know where is can find this file in Hero of the Storm? I don’t want to buy Starcraft 2 for a bug…
Just reporting that I am having the same issue. It’s not constant but sporadic.
just reporting I haven’t played for several seasons but obviously was on the diablo hype train with d2r and d4 in the works so I booted up and gave you 33 hours of my time. I had the freeze bug happen at least 15 times over the course of the last week and finally my barb died in a simple rift to a game breaking bug that you have been at least aware of for almost an entire year. Yes I am bitter.
C:\Games\Heroes of the Storm\Support64\fmodex64_4_44_23.dll
You gotta change the fmodex64_4_44_23.dll to fmodex64.dll then move it to
C:\Game\Diablo III\x64\
If you still play Heroes of the Storm, I would think you would want to copy it to your Diablo III\x64 folder. Then, rename it.
xDDDDDDDDDDDDDDDDD lol no.
When this happens to anyone else do their cheat deaths fail to even proc? Because mine arent…the game freezes and next thing i know im dead and nerves of steel didnt proc.