Frequent Daily crashes of Diablo 3

Hello, I have a reasonably powerful system. AMD 5900X, 32GB RAM, NVIDIA 3070 GPU.

Over the past month, I have experienced regular crashes of the game. This may occur when playing for 3 minutes or 60 minutes. It happens in Adventure Mode, and in Campaign Mode. It happens in Solo and Cooperative games. Suddenly the game crashes and I get the Blizzard Crash window with the crash ID.

This happens so often that I’ve captured the Crash Dates and the Blizzard Crash Reference ID numbers to maintain my sanity and to ask for help.

To attempt to rectify this condition, I have updated all Windows patches. I’ve updated all NVIDIA graphics drivers. I have “repaired” the Diablo 3 install. I have uninstalled and re-installed Diablo 3 completely as well. Yet this condition persists.

Here are my recent ID captures:

4/28/2022	D7D64314-2E61-493E-8270-A1F8BDDF6F52
4/28/2022	5998462A-29D9-4C9A-A6A7-D0FB46D031BE
5/14/2022	BC8E1A08-F5FE-4C8E-9EF3-ECDD93CBFC22
5/16/2022	A77D271E-C528-42F4-9459-B50998161954
5/17/2022	FD8FC6C8-C12F-4C48-853B-A2EE31016289
5/19/2022	917A18D9-632D-4CF5-8EC6-F39422D07A1A
5/20/2022	836BD40F-F135-49A5-866B-6DD5E8D0F833
5/23/2022	1A039BD1-4AEA-483C-A2FC-5CE34DEB07F2
5/24/2022	B009ABEA-2A3C-4D1A-9D95-7A44FA10464E
5/24/2022	18B00105-5330-432A-88D6-0F18C674FC3F
5/24/2022	56F6938B-33DB-44B2-92A0-CB918CEF4358
5/25/2022	E5524650-779F-482E-BFF7-CA8688DF58D4

I’ve learned to live with the fact that Diablo 3 is potentially unreliable on my particular system, but if the Diablo Support servers have any more information based on these references that would help - I would be happy to learn how to improve my experience.

I have taken the MSInfo.txt export and the DxDiag.txt exports. All info seems normal. Other applications are not crashing. Sometimes, but not every time, the windows log also shows an application error. But there is no obvious root cause of this condition.

Is there any information in my Error references?
Thank you

24h update:
I realize I am only one player. And not terribly active on the forums. Just to keep my records up to date, I’ve had 2 additional crashes since my last post, yesterday. here are the IDs:

5/25/2022	86366A00-42B8-4266-A2CA-0B8DA5F5E2C8
5/26/2022	09CB6F15-52CF-410D-8418-8383329DB24C

If you have any insights from your tracking system, it would be appreciated! Thanks Blizzard team.

3 Likes

Howdy GTLucky,

After looking over the crash logs, it seems like something is conflict with the graphics but it’s not clear exactly what is causing the problem. It may be due to a background program though, such as security software. If you do have security software, then I recommend adding D3 as an exception.

If this persists, we should grab the MSinfo. You can upload it through Pastebin and then paste the link here.

If you have issues pasting here, post the link with a space (ex: Pastebin (dot) com/123456).

First, Thank you Zenlaka! I appreciate the check.

Here is the pastebin link:

The problem does persist, here are the updates from the original post:

5/27/2022	A02ADACF-1618-4165-91DE-467435F364DB
5/29/2022	E09163D4-7DFF-4452-883C-2EFBE66049E3
5/30/2022	3F66FFD8-A812-41D5-B5DF-DE0AC9A1FCFA
6/1/2022	F9E62669-BC0E-4301-B2E6-E78F082D6951
6/1/2022	291E4FCF-2466-42C6-B88D-0EDB82496EDD

Just out of interest do you have a 3070Ti? Since the Nvidia driver update on 24/05/22. As soon as I load the game up onto the character screen of D3 it Bricks my card, I’m talking 100% GPU usage and hitting 100 Celsius until my pc turned itself of to save the card thank god it did or I would be £950 in the red. Tried capping fps, changing vsync options nothing worked and no one really cares enough about the game anymore to offer actuall advice other than “Get cooling” as if a 10 year game should rock 100% gpu

That sounds troubling! No, I have a regular 3070. And the temps stay in the “normal” range and usage as I play. I checked this both in resource monitor and in the NVIDIA overlay UI. Thanks for the suggestion. I hope you can find a solution for your overheating!

Howdy GTLucky,

I looked over the crash logs and system files but didn’t notice any specific cause. However I would recommend disabling or temporarily uninstalling the Glasswire Firewall temporarily to see if there’s any change. If this persists, try closing all other third party programs while testing.

Hello Zenlaka,

Thank you x2 for replying again. I have tried disabling the Glasswire Service and restarting the computer with good results. I did have one crash but it has been rather stable for 2 days. I will continue to play and monitor and will update here by this weekend if this suggestion is the final solution. At that point I will investigate if there is a way to add D3 to an “approved application list” within the Glasswire program to avoid future conflicts. Almost there!

Update - 6/13
It is true, the crashes have reduced in frequency quite a bit since disabling Glasswire. However there have been a few more. I will post here for investigation.

6/6/2022	8025216C-F0EF-42BB-8C19-596E1CD2FDE7
6/9/2022	1F7860AB-A6D2-4855-8BE1-A9B01ECF0F28
6/13/2022	B2E2F731-489B-4CBA-BA7A-940F1EA857C1

Thank you.

Hi Blizzard,

My issue continues to persist. I have disabled the program mentioned by the agent. But even after a week away, coming back has re-engaged the problem. My Diablo III crashes every day.

It makes me want to stop playing and take up other games. That’s sad! I love this game. But this is over the top, every day. Regardless of the in-game activity. Here are the last sets of crashes.

6/16/2022	C987939F-6555-4394-9140-B04D6750CE22
6/16/2022	0CDCE76D-E1A6-4AFC-95F2-43A8B0E3D732
6/17/2022	086C7EB9-3AAC-43C8-9C39-89A5EA82999C
6/18/2022	241009CD-3275-4062-9ECC-E5196E98F056
6/29/2022	B3A55C3D-1704-4346-A47C-2ED7A3D2DEFB
6/29/2022	66601028-9233-46B6-A38E-3632C46C5170

Please, can someone help me discover what is causing the above crashes? Any hints to my troubles??

Thank you

1 Like

Howdy GTLucky,

Sorry about the delay in responding. I looked over the new crash reports but don’t see anything specific sticking out in these logs. The only thing I can see is that some of these errors are C0000005, which you can read about here.

If these crashes are still happening, you may want to try lowering the graphics and testing windowed mode to see if there’s any change. Otherwise, try uninstalling that Glasswire application and restarting the PC to test the game to see if the crashes stop. You can always reinstall Glasswire afterwards.

If none of this helps, I would suggest creating a support ticket with a link to this forum thread and new system files so we can try to resolve these crashes as quickly as possible.

Well, no luck. Thank you Zenlaka for following up on this thread. I have opened a ticket. I updated all of my drivers, I’ve repaired, and reinstalled the game 4 more times, choosing different SSD just in case. I’ve used the “Scan and Repair” button on the Battle.net launcher. But still, I cannot enjoy Diablo 3 for any regular amount of time.

8/15/2022 29CFAC6A-9C2F-4159-ACEE-050F411814A4
8/22/2022 B64BD81D-4596-4E62-8FB1-E7F458127417
8/22/2022 00564946-CA92-43AA-8883-FBCB506D85CF
8/25/2022 E6A615B4-CE30-4CAD-9620-187783485569
8/25/2022 4B6A1CB2-FB4C-409C-9B84-04275C6084FD
8/26/2022 2C5CC395-9EAC-42D1-947D-224B0EC1324C
8/26/2022 1441C842-09EB-4824-9DB4-D2047A67090A
8/27/2022 96A8BC34-8BB8-43B0-BC54-C22135EC05E2
8/28/2022 AD962BB2-49F2-4B61-9E98-1FBF15E2D348
8/28/2022 ECDE4CBA-F9B4-49A5-92D7-6417FD26C1ED
8/28/2022 89E9338F-0746-4C74-954A-BC83AEBF2E2C
8/29/2022 1768187C-0474-49DD-91D5-A976EE3F8EFF

So, there are the most recent Crash Error IDs. I am hoping the support ticket will provide some remedy. Thank you again for checking in!
GTLucky

I was having similar problems. I messed around with so many registry settings, and tried so many official and unofficial drivers that I created other stability issues and had to re-install windows. When I did, I set it so that when windows updates, it doesn’t update my drivers. That was two months ago, and the game has only crashed once since then.

Not saying it will work for you, or anybody else. Worked for me, though.