Crashing on loading games online and offline

Bug Report
1

Even after the patch, the following errors persist (This is not present on fresh PC restart, but typically repeats after first launch). I am able to press play, launch into the blizzard, then D2R animations, then Crash to desktop with “an unexpected error occurred”.

REPORT IDs:
3BE14581-D62D-4C38-BDDF-90B558FF0D03
A27D3055-9D52-4168-93C1-F4B2F58B2D10
25E3CD6D-9A5D-4B30-ABCE-529156D3EEF6

Occasionally (typically after restarting computer) will be able to launch the game properly, then will open the loading screen for the selected online game but it crashes to desktop while loading a game on the server (no error messages).

i5 2500k
NVIDIA GTX 1660
12GB RAM
Windows, video drivers are up to date.
No AV software other than windows defender.

Took advice to go through startup items and can get the game to launch properly when disabling MOST startup items. Cannot figure out which program(s) specifically cause the startup crash (log file shows: NVSDK_NGX_D3D12_Init failed, error code: -1160773631).
When able to start up, however, it still wont load a game successfully. Checked blz-log file and it has a ton of render errors and an error that it couldn’t connect to server. On occasion game says to check internet connection when failing to load game (no connectivity issues).

New REPORT IDs for this type of crash:
D6E3B6BB-431C-4115-891C-630C90EE105A
77E32674-C365-4510-8272-4AF3ED558887

DxDiag file:

https://file.io/kBnx85puKPKf

In case the file doesn’t come through, I wanted to share the following that seemed applicable:

Diagnostics

Windows Error Reporting:
+++ WER0 +++:
Fault bucket 1335767992094347026, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: D2R.exe
P2: 1.0.420.0
P3: 614e1db3
P4: StackHash_f824
P5: 10.0.19041.1202
P6: 4f115fac
P7: c0000374
P8: PCH_2E_FROM_ntdll+0x000000000009D8C4
P9:
P10:

+++ WER1 +++:
Fault bucket 1424725434336261698, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.19041.746
P3: 6be51595
P4: KERNELBASE.dll
P5: 10.0.19041.1202
P6: c9db1934
P7: c00001ad
P8: 000000000010be3e
P9:
P10:

+++ WER2 +++:
Fault bucket 1424725434336261698, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.19041.746
P3: 6be51595
P4: KERNELBASE.dll
P5: 10.0.19041.1202
P6: c9db1934
P7: c00001ad
P8: 000000000010be3e
P9:
P10:

+++ WER3 +++:
Fault bucket 1551820502204675292, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: D2R.exe
P2: 1.0.395.0
P3: 614bd478
P4: StackHash_0000
P5: 10.0.19041.1202
P6: 4f115fac
P7: c0000374
P8: PCH_84
P9:
P10:

+++ WER4 +++:
Fault bucket 1424725434336261698, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.19041.746
P3: 6be51595
P4: KERNELBASE.dll
P5: 10.0.19041.1202
P6: c9db1934
P7: c00001ad
P8: 000000000010be3e
P9:
P10:

+++ WER5 +++:
Fault bucket 1424725434336261698, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.19041.746
P3: 6be51595
P4: KERNELBASE.dll
P5: 10.0.19041.1202
P6: c9db1934
P7: c00001ad
P8: 000000000010be3e
P9:
P10:

+++ WER6 +++:
Fault bucket 1424725434336261698, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.19041.746
P3: 6be51595
P4: KERNELBASE.dll
P5: 10.0.19041.1202
P6: c9db1934
P7: c00001ad
P8: 000000000010be3e
P9:
P10:

+++ WER7 +++:
Fault bucket 1424725434336261698, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.19041.746
P3: 6be51595
P4: KERNELBASE.dll
P5: 10.0.19041.1202
P6: c9db1934
P7: c00001ad
P8: 000000000010be3e
P9:
P10:

+++ WER8 +++:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.19041.746
P3: 6be51595
P4: KERNELBASE.dll
P5: 10.0.19041.1202
P6: c9db1934
P7: c00001ad
P8: 000000000010be3e
P9:
P10:

+++ WER9 +++:
Fault bucket 1424725434336261698, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.19041.746
P3: 6be51595
P4: KERNELBASE.dll
P5: 10.0.19041.1202
P6: c9db1934
P7: c00001ad
P8: 000000000010be3e
P9:
P10:

3 Likes
2

I am getting the same errors, have they found a fix for you yet?

3

Fault bucket 1915947619033821095, type 5
Event Name: D3DDRED2
Response: Not available
Cab Id: 0

Problem signature:
P1: VEN_10DE
P2: 10.18.13.5362
P3: 0x887A0006
P4: 7
P5: D2R.exe
P6: 1.0.498.0
P7:
P8:
P9:
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA4A2.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA4E2.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA53F.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA5BD.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_VEN_10DE_d5573a6cb0649386ea0b3ab8a71542e3196d0_00000000_620bef68-b660-4a35-bda8-dd340485a084

Analysis symbol:
Rechecking for solution: 0
Report Id: 620bef68-b660-4a35-bda8-dd340485a084
Report Status: 2147487744
Hashed bucket: f13984c578d1fb24da96d03558c42fa7
Cab Guid: 0

4

since you can’t fully post you dxdiag without a reply. Here ya go

5

Appreciate that bump. Have submitted a tech support ticket and really appreciate the intention of the Technical Specialists. We’ve gone over several DxDiag, MsInfo and blz-log files and those REPORT ID codes to no avail. I’ll avoid posting more here, but can share this link to get these files on your system if submitting your own support ticket: Obtaining System Files - Blizzard Support. The blz-log file is in your D2R directory folder.

After reviewing these two separate and seemingly common crash patterns with the technician and in no particular order, I’ve troubleshooted the following:

  1. did a selective startup without any applications loading at startup (Closing Background Applications - Blizzard Support)
  2. ensured no cloud drive services are syncing “C:\Users(YourUSERname)\Saved Games\Diablo II Resurrected”
  3. deleted the D2R settings file to restore default settings - located in the “C:\Users(YourUSERname)\Saved Games\Diablo II Resurrected” folder
  4. ran windows systems file check (Repairing Windows System Files - Blizzard Support)
  5. scanned for malware with Windows Defender and Malwarebytes
  6. did an extended windows Memtest (Running Memory Tests - Blizzard Support)
  7. ensured all drivers and Microsoft programs are updated
  8. ensured NVIDIA drivers are up to date (Updating Your Drivers and Operating System - Blizzard Support)
  9. restored NVIDIA settings to default (Resetting Video Driver Settings - Blizzard Support)
  10. ensured there is no system overclocking of CPU
  11. updated D2R
  12. scanned to repair D2R (Repairing Battle.net Games - Blizzard Support)
  13. repaired any registry errors and cleaned the system junk with Ccleaner
  14. Uninstalled an old version of Citrix Indirect Display Adapter.
  15. Changed Pagefile.sys from 0MB to “Automatic” management by Windows (previously set to zero with thought that this would optimize SSD)

Continue to get random DWM.exe crashes in MsInfo log.
After doing #15, game launches successfully, as it should.

After increasing the size of my pagefile then and fixing that first problem, the tech support suggested that there might be an error with an old installation of the graphics drivers that was causing the second crash when loading game from the lobby. After following the instructions below, I was able to play the game reliably!

• It’s possible the video drivers were corrupted prior, it’s an easy fix though, let’s try a display driver uninstaller so we can reinstall fresh drivers.

  1. Download the Video Drivers from your video card manufacturer’s webpage
  2. Download the Display Driver Uninstaller tool - (http :// www. wagnardsoft. com/forums/viewforum.php?f=5) Go to Display Driver Uninstaller under Announcements, then click on “Offical Download Here”
  3. Open and Extract the DDU.
  4. Click on Clean and Restart.
    Note: Safe mode is not required, but can yield better results.
  5. Restart, then Install the Drivers from Step 1.

Hopefully the above steps can help someone else with similar issues. Please share what issue you had and what worked for you!! (and donate an soj when we finally meet in game??)