Fmode freezes Solution

Greetings from Germany,
FMODE Freezes are initiated by invalid seek Position passed to fmodex.

HowTo:
Start the launcher and let game actualize itself. Dont leave the game!
Switch to Windows Desktop, navigate to Diablo III/x64 path
Replace MSVCP140.DLL and vcruntime140.DLL (both are Visual Studio 2015) with the new
ones from Visual Studio 2019.
Now Start a game session.
No more freezes, no more Fmode 200ms error. !
After this game session exit the launcher and look at D3Debug.txt

You find a new entry: like this:

FMOD Error during ‘FMOD_Channel_SetPosition’: An invalid seek position XX was passed to this function.
I got several XX , but mostly its “2”

Please BlizzardDevs: Dont overwrite this 2 New DLL !
We all want to play the game WITH sound and WITHOUT freezes.

the New VC 2019 runtime files.
can be found here and will be public for a week or so.
“h t t ps://drive.google.com/folderview?id=1bppN9KGlalb62pxXUXWCxc5UAx4Y8wSD”

contains: msvcp140.DLL V 14.28.29337.0 signed by MS 27.1.2021
and vcruntime140.DLL V 14.28.29304.1 signed by MS 5.9.2020

Have a nice day.

1 Like

Testing this atm, will update shortly

If u got another Position than 0 or empty
after invalid seek position pls post it.
mb usefull for Devs.
I got a lot of empty Positions, but no freeze.

:slightly_smiling_face:

Just used ( http s://speedtesting.herokuapp.com/peviewer/ ) to check if fmodex64.dll actually uses these files, and guess what it uses *VCRUNTIME140.dll and so far my game has not had a fault using the ones you mention above! Will give it a few hours of testing and let you know how things go.

List of files it fmod uses to function

  • [ADVAPI32.dll]
  • [KERNEL32.dll]
  • [MSACM32.dll]
  • [USER32.dll]
  • [VCRUNTIME140.dll]
  • [WINMM.dll]
  • [WSOCK32.dll]
  • [api-ms-win-crt-convert-l1-1-0.dll]
  • [api-ms-win-crt-environment-l1-1-0.dll]
  • [api-ms-win-crt-filesystem-l1-1-0.dll]
  • [api-ms-win-crt-heap-l1-1-0.dll]
  • [api-ms-win-crt-math-l1-1-0.dll]
  • [api-ms-win-crt-runtime-l1-1-0.dll]
  • [api-ms-win-crt-stdio-l1-1-0.dll]
  • [api-ms-win-crt-string-l1-1-0.dll]
  • [api-ms-win-crt-time-l1-1-0.dll]
  • [api-ms-win-crt-utility-l1-1-0.dll]
  • [ole32.dll]
1 Like

good work, i did nearly the same.
But only msvcp140 and the runtime is relevant. THX for testing.

thanks for making me engage my brain, hopefully you nailed it!

Im sure, we found the solution.
Im running this for 3 days. No Freezes

The question is: Does Blizzard react? LoL

PLS Blizzard: Dont overwrite those files over and over. Just let US investigate this.

Only getting Error: sValidatePointInCell failed atm, slight ms of a stutter but playing better

Is this a FMOD error ?, i dont think so.
MB another construction site.
LoL

na weird fault that, only happened in one gr. rest been fine. Playing with Wizards and getting the ususal lag from to many pulls but no freezes and Im still in control when it lagged :open_mouth:

Which FMODE error in Log?
But THX anyway .
Sry. Now i See your log.
There are some Position Errors but no Freeze hints. (200ms…)
Dont know what cause this your freeze…
Dumb question: you use 32 vor 64bit D3?
The fix is for 64bit only. Sry agn dumb question
Sry agn, the first log frrm 14: 47 with the usual 200ms bug, the second without but Position errors. Hmmm.

Not sure, but MB. Warden replaced the files.
for me this is true:
With the old files (2015 Version) i have tons of freezes.
With the New Ones (2019 Version) None.
, but Position errors.
Click on runtime.DLL, show Details, 2015? , then Warden.
I know its konfusing, but Warden is also using these files…

Windows 10 will block the new files as they are from a different PC. To solve this just right click the files and tick Unblock at the bottom.

True, but thats a one time action.

1 Like

I can confirm I’m in gr115 with 3 good wiz and NO lag, no freezes and Sound works great!

1 Like

Can you update the instructions to include the unblocking files? cheers

Ok Been testing all evening and I have no issues to report. Logfile shows plenty of errors and game actually feels better in higher gr’s.

To Install I did:
1, Download the files from link at top.
2, Replace the files in D3 folder “Diablo III\x64”
3, Right click new files 1 by 1 and on click properties the bottom right of the properties box there is a tick box to unblock the files ( this is due to taking files from a different PC). Click this and then click apply then ok.

http s://ibb.co/HnqS3N1

4, Load the game as normal via the Launcher.

I’m not sure if this will persist or if we will need a simple bat file to repeat the file replacement on launch. Either way to play with sound and no issues this is worth a go.

This is the main error I have in Log now

|2021.05.01 00:30:48.125791800|FMOD Error during ‘FMOD_Channel_SetPosition’: An invalid seek position was passed to this function.
|2021.05.01 00:30:48.126094400|FMOD Memory - total: 178257920|
|2021.05.01 00:30:48.126302500|FMOD Memory - allocated: 53226392, - max allocated: 68540536|

I have removed my reply to this topic due to not following through with everything needed to do a proper evaluation. I failed to unblock the two files yet it still seem to work.

I have now unblocked the two files and am trying again.

Fingers crossed for you, ive enjoyed my night on D3 with sound, hope this works for all. Launcher does replace the bloody files though

Unfortunately the fix is not working for me. Too bad! I quite enjoy sound. Was doing a GR 113 and it froze up hard for quite some time. I confirmed I still have the two files there and were the same version as yours.

I have my sound in game set to Low (32) with default sound and Speaker set to 5.1

Logs show the following.

2021.04.30 19:56:19.287645400 FMOD Error sound not ready in 200ms
2021.04.30 19:56:22.364624900 FMOD Error sound not ready in 200ms
2021.04.30 19:56:25.440165400 FMOD Error sound not ready in 200ms
2021.04.30 19:56:28.516724500 FMOD Error sound not ready in 200ms
2021.04.30 19:56:31.593846000 FMOD Error sound not ready in 200ms
2021.04.30 19:56:34.685930700 FMOD Error sound not ready in 200ms
2021.04.30 19:56:37.761548000 FMOD Error sound not ready in 200ms
2021.04.30 19:56:41.067967700 FMOD Error sound not ready in 200ms
2021.04.30 19:56:41.115898300 I 01:56:41.115902 [BGS]
2021.04.30 19:56:41.209579100 ERROR: Ran out of explosions processing Explosion ‘g_radial_10foot_100lbs’ (max entries = 128).
2021.04.30 19:56:41.209872500 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.210142200 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.210491400 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.210806900 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.211222700 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.211409800 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.211775800 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.212049500 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.212404600 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.212828900 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.213091700 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.213269700 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.213553200 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.213851200 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.214150800 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.214411000 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.214639700 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.214897500 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.215158700 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.215416000 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.216001200 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.216363900 ERROR: Ran out of explosions processing Explosion ‘g_radial_5foot_50lbs’ (max entries = 128).
2021.04.30 19:56:41.242581900 Received pong with old sequence!
2021.04.30 19:56:44.327608700 FMOD Error sound not ready in 200ms
2021.04.30 19:56:47.403398500 FMOD Error sound not ready in 200ms
2021.04.30 19:56:50.479670700 FMOD Error sound not ready in 200ms
2021.04.30 19:56:53.570825300 FMOD Error sound not ready in 200ms
2021.04.30 19:56:56.646302700 FMOD Error sound not ready in 200ms
2021.04.30 19:56:59.723127500 FMOD Error sound not ready in 200ms