I to am having this issue and crashing ever since May update & latest Diablo 3 update.
I started playing again during Season 21 patch after the may update and prior there was no crashes.
- List item
B63FE11C-6A61-49DD-9B2E-A1693E25540D
6124103F-988A-4BD2-8AA9-81AA9CEEE602
FF989361-500F-4D6D-B04B-C816DE6F5566
686E8488-550C-42CB-BB2B-E47D18819F4A
AFC72BD4-4955-4B9C-AA9C-84CB13510178
CBF9DF66-D0C1-4296-99C6-67643A1F7E05
7E81DEBB-8BC7-4F0F-A8B4-A8591F559F1B
EEEBFC66-85EA-4629-A57B-1870ED1139D0
9C586EDF-456F-4FC4-AE94-9A6F1F90583B
874F0E95-52AB-489E-BFF9-5B9CB2315CE0
7720E4DC-492E-4A1B-8FCF-8572C5B4D361
9FEDBD2F-0549-4A57-BB62-921FBA908FC5
9A7E4A0A-4571-4CA8-A4C2-571C24634DA5
1E77817D-A6C6-44B5-9A0F-1C5EB9DEC9B8
CB6B0FA2-BD92-41A9-9696-D0F562CDCBE1
8F1DC973-B32D-4B38-A105-2F5DCF2CC91A
27F68756-DD41-42C7-9A17-345F154AFD6A
4B4232F0-D260-4B8E-8C5D-5120C921BC00
( DXdiag report)
Pastebin: pWnAH43x
I also had this problem, I downgraded from Windows 10 May 2004 update to the previous Win 10 version 1909 and haven’t had any problems since then. I had already contacted Blizzard very early on shortly before the release of the Win 10 May update and they said at the time that they knew nothing about it and I had sent all the logs of the game and Win that they wanted. But you couldn’t speak of help because the ticket was simply closed by Blizzard.
1 Like
Here’s my dxdiag in pastebin: SiJpLRA1
Thanks!
Hey again all!
We’ve synced with the devs and it looks like we’ve got enough reports now. Thanks for answering the call to action and getting us those DXDiags/Error reports. I’m editing the other messages to indicate that we no longer need more data. You are welcome to continue reporting issues or work arounds that you discover, but you can save yourself some time and stop gathering the previously requested logs now.
The devs are aware and looking into the issue now. We’ll let you know as we get more insight into the problem, but for now, there are some work arounds posted in this thread. The most successful options currently are temporarily disabling sound outputs on your PC. This will result in playing without sound however. The other option is to roll back to the previous build of Windows 10 while we work on this.
8 Likes
I have found that the game freezing is more likely to occur if you are running a monk (ZMONK). In HC we have lost 4-5 Zmonk’s through game pauses.
hi,it dont matter what class u play,i play barb,crus,monk,dh and on all get freeze,most likely or more often in group play,but solo play is not 100% “safe” too,i get freeze every 3-4gr in solo,sometimes 1x and some even 4x in one rift
I tried the read only but somehow the launcher can still fix it…
But the shortcut works!
The method you found works perfect, in fact diablo has never ran better! I get solid FPS and no freeze or lag!
Something is wrong with that modex file
Turing off the sound does not work for me. Only replacing the problematic DLL did.
Yeah. the fix is replacing the file, creating a shortcut and your sound won’t work. (disabled or not).
1 Like
This problem has been around for years now and the only fix that works is to replace the fmod with another version. Doing so you lose your sound altogether. This problem will never be fixed properly.
1 Like
Another problem is raising with W10 2004, around ESENT 642.
maybe it’s the reason why we are also affected in D3.
I just verified and I am concerned about this ESENT 642 issue by the way.
svchost (3692,D,22) SRUJet: La version 9120 (0x23a0) de la fonctionnalité de format de base de données n’a pas pu être utilisée, car le format actuel de base de données 1568.20.0 est contrôlé par le paramètre 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat)
Hello there,
Is there any update as to when or whether the problem will be solved? The screen-freeze has literally ruined more than 10 attempts to push higher gr’s. I cannot reverse my windows update, nor I want to play without sound, etc. I understand that those solutions might function in the interim but I refuse to entertain such fixes.
Our team is still investigating the issue and they believe they found the source of whats been causing the issue. It’s a frustrating issue and these types of compatibility issues can take a bit of time to resolve.
Our team needs to run through testing and replicating the issue to find the cause, then work on a fix for the issue. Once a fix is in place, our QA and compatibility teams need to make sure the fix works. If they can test and verify the fix in place works, an update or hotfix will be pushed to the live servers. It can be a lengthy process, but we want to make sure the fix in place does resolve the issue before it’s pushed out.
Since a lot of replicating and testing needs to be done, it’s difficult to give an exact time frame at this time. We’ll communicate any new information or updates on this forum thread when our team has more details to share with us. Thank you for all the provided details so far, it’s greatly appreciated and helpful!
9 Likes
Dear Caterpepi,
Thanks a lot for the quick reply and the update regarding the situation. I hope you find a solution soon cause rifts have been unplayable lately.
Stay safe
2 Likes
Good to hear it is being worked on.
My tactic on my DH so far during the freeze has been to activate smoke screen, press ESC and hope for the best. On single player it usually works but I cannot play multiplayer.
1 Like
This has been a long standing issue that manifested itself in stutters. I’m glad that it became a bigger issue with the latest Windows 10 version or else it will never be taken seriously. I hope that the devs are able to eliminate the bug altogether.
1 Like
I wish that problematic lib was disabled when you disable the sound. Especially since I play without sound anyway,