[Main Thread] Windows 19041 - Freezing for 5-10 seconds

This is happening to me quite often in > 100 grifts. Replacing the DLL does seem to work but that’s quite a sucky solution. Any more time being put into this @Blizzard ?

Any more on this? this post is really old, and this is still happening, i would love to have sound again!

Wasn’t having any issues until I got into GR 90 plus yesterday now it’s freezing. Going to try grouping without a wizard to see if it’s related to the mirrors.

We are getting professional correspondence on a go stuff your self basis.

5 or 10 seconds? you’re lucky. I get this quite regular for up to 1 or 2 mins.

Replacing the dll file worked for me, but the next time I went to load Diablo 3, my launcher “updated” and re-replaced the dll back to the original… any way to prevent this? I set the file to read-only, and it still updates and replaces it every time I go to launch the game.

Hey Blizz, this isn’t an isolated incident, this is happening to me as well… and it is extremely annoying. This issue appears to be more widespread than you are aware, I created my own thread on this issue just a moment ago and noticed this thread. Please look into this issue for us.

1 Like

It appears you can DL a new copy of fmodex64.dll. I’m trying it now. Hopefully, this fixes this issue. Thanks!

ping to make them hopefully do something about the issue.

My win 10 pro got updated to 20H2 yesterday, since then the game freezes from time to time, for more than 5 sec.
Each time, FMOD error in the debug.txt file:

|2021.04.15 12:48:23.478513300|FMOD Error sound not ready in 200ms|
|---|---|
|2021.04.15 12:48:26.621911700|FMOD Error sound not ready in 200ms|
|2021.04.15 12:48:29.763096600|FMOD Error sound not ready in 200ms|

I just got 3 freezes in a row in a GR 100.
How come this has not been fixed, the 1st post about the error is almost 1 year old !

edit: win 10 20H2, I9-9900KF, RTX 2080 TI

2 Likes

I wanted to add to this thread. I too have been having these lock ups since around season 21, but it has been playable. It would happen once or twice a rift when running with friends. Usually did not happen solo. This season however, playing wizard, they were just terrible. The anger I had was unreal gamer rage lol. I died so many times doing my GR 100+ pushes due to the freeze. My Debug.txt also had the

“FMOD Error sound not ready in 200ms”

on each freeze. I do not play with sound normally and had tried a huge list of options. It was worse on higher GRs. It is worse with playing with others. I have tried different computers, different graphics cards, different graphic settings on multiple PCs. All freeze. None of my friends have this issue so I’m sure it is a strange combo of just the right hardware pieces and the D3 files.

I used a temp fix from this forum to fix it. I have a PowerShell script that I wrote to copy the fmodex_4_23.dll from HotS folder and overwrite and rename into the D3 folder. I play with the x64 client, but I have to replace both the x64 and the non-x64 (32-bit) version for this to work. I have to run the script one time, each time, before I launch D3. So far I have had zero lock ups following this process. Before I would have 5 - 10 freezes per rift.

Here is the code I use just to add it. I provide no support or warranties. Use at your own risk. It checks for a backup of the original files with the extension “.old”. If it doesn’t find them it looks for the original files and renames it with the “.old” extension. Then it copies the files from HotS to your D3. If you do not have HotS installed you can use Starcraft 2 I have been told, but only HotS worked for me. If you do not have either you can download either game. They are both free.

You will need to change the variables to match your install paths for your files.

#Original code copied from: [Main Thread] Windows 19041 - Freezing for 5-10 seconds - #631 by Delenn-2659
#Remove-Item -Path “C:\Program Files (x86)\Diablo III\x64\fmodex64.dll”
#Copy-Item “\fmodex64_4_44_23.dll” -Destination “C:\Program Files (x86)\Diablo III\x64\fmodex64.dll"

$BackupDllx64 = “G:\Diablo III\x64\fmodex64.dll.old”
$BackupDll = “G:\Diablo III\fmodex.dll.old”

$DllSourceX64 = “E:\Blizzard\Heroes of the Storm\Support64\fmodex64_4_44_23.dll”
$DllSource = “E:\Blizzard\Heroes of the Storm\Support\fmodex_4_44_23.dll”

$DllDestinationX64 = “G:\Diablo III\x64\fmodex64.dll”
$DllDestination = “G:\Diablo III\fmodex.dll”

IF(Test-Path $BackupDllx64){
Copy-Item $DllSourceX64 -Destination $DllDestinationX64
}ELSE{
Rename-Item $DllDestinationX64 -NewName “fmodex64.dll.old”
Copy-Item $DllSourceX64 -Destination $DllDestinationX64
}

IF(Test-Path $BackupDll){
Copy-Item $DllSource -Destination $DllDestination
}ELSE{
Rename-Item $DllDestination -NewName “fmodex.dll.old”
Copy-Item $DllSource -Destination $DllDestination
}

The CMD (.bat) scripts on this thread should work just fine too. Just adding some Pwsh love into the mix.

There are lots of things covered in this thread, but I think Blizzard to focus on the FMOD error and what combo of hardware is causing the issue. Or just upgrade the .dll to the version used in HotS and move on.

1 Like

I can’t even play with friends, and barely solo, because of this lockup bug. It’s completely unbearable. It happens literally every session. if my game doesn’t just close completely on its own (without error dialogue or bug submission report), it just hard locks up for 5-10 seconds at a time, or stutters to the point I can’t control my character without just becoming overwhelmingly frustrated

This definetly helped.

Drop sounds levels to 16.
Disable cores other than 0 and 1 by using the affinity functions withing task manager.

No freezes and crashes anymore, but the affinity change HAS to be performed every time you launch the game again.

1 Like

Throw my name on the pile. When participating in Greater Rifts higher than 90 with a party of other players using certain mechanics (maybe AoE effects) the games frame rate sporadically very frequently drops below 1FPS whenever I’m near them in combat.

CPU usage, GPU usage, internet usage & internet latency don’t spike during these stutters.

Lowering audio channels to 16 helps, but there are still common occurences of FPS spiking below 1FPS.

Ryzen 3700X
Geforce 1070Ti (Latest driver)
Asus Crosshair Hero VIII WiFi (latest UEFI & chipset drivers)
Geforce Control Panel > Prefer Maximum Performance
Windows Power Plan > High Performance
Latest stable Windows 10 release
Realtek ALC1220 (latest driver from Microsoft Catalogue)

Well, I have nothing new to say here that has not been said. The game is unplayable for me. Constant 10 sec freezes every 30-45 sec in higher GRs on fire wizard. Even in other classes there is sluggishness.

Sound is off, setting all turned off or set to lowest settings. Well, got guardian so I guess the season is now over for me as I do not see this being fixed anytime soon if ever.

1 Like

Sad but True : Very old Issue, complete silence from Blizzard about this issue.
I am not even shure it would be legal for us to replace that .dll as we alter the original installation, even so it does fix our problem… haha

At the cost of losing all sound… afaik.

If you don’t care anymore, at least give us permission to access the data files, we will gladly do it for you :frowning:

Can confirm, this has worked for me.

Noticing a slight drop in FPS due to higher load on the individual cores, but i’ll take that over not being able to run rifts any time of the day.

Just discovering the topic, lost 2 HC character due to it this season. Playing HC, i’m ready to eventually die, but like this it totally killed my mood to play the game.

2021.04.16 20:10:45.160472000 FMOD Error sound not ready in 200ms
2021.04.16 20:10:48.622704900 FMOD Error sound not ready in 200ms
2021.04.16 20:10:51.753477200 FMOD Error sound not ready in 200ms
2021.04.16 20:10:52.921546100 Screenshot - tLockedRect pitch 10240, dest pitch 10240
2021.04.16 20:10:52.925408800 sBlitHWCursorToBuffer : writing cursor begin
2021.04.16 20:10:52.925576400 sBlitHWCursorToBuffer : writing cursor end
2021.04.16 20:10:53.896766900 >>> Azathoth BnetGuild::RequestGuildNewsList_TryRequestNow guildId=120809 wasNewNewsAvailable=0 isUserInitiated=0 waitedMs=0
2021.04.16 20:10:53.896998800 SendGuildMessage hero:Azathoth id:150 attribute { name: “Version” value { string_value: “2.7.0.74291” } } attribute { name: “CustomMessageId” value { int_value: 150 } } attribute { name: “CustomMessage” value { message_value: “\010\351\257\007\020\310\317\201\323\307\205\307\251\t” } } attribute { name: “CustomMessageDestination” value { uint_value: 1 } } attribute { name: “GuildShard” value { int_value: 9 } } count:31
2021.04.16 20:12:09.930592800 [Telemetry] (TELE): Requested sending batch messages by multi-part http POST messages count 1
2021.04.16 20:12:21.184381000 >>> Azathoth Quit game reason=8
2021.04.16 20:12:21.200554800 ClientSocket Disconnect
2021.04.16 20:12:21.200768700 UIStartup_ClientDisconnected msg=The game connection has been lost: your client has been disconnected from the server.
2021.04.16 20:12:21.200857900 Disabling loading screen for 31, 0
2021.04.16 20:12:21.200920400 >>> Azathoth ===== Battle.net SetD3GameServerDisconnected (expected=1) ===== The game connection has been lost: your client has been disconnected from the server.
2021.04.16 20:12:21.215520300 GameDisposeGames()
2021.04.16 20:12:21.215613600 ENDING GAME

1 Like