Random Crashing with 2.0 - Never Happened Before Update

Weird.

I just got done playing for 2 hours without any issues at all. I even recorded it, if you want to see.

I didn’t realize the windows game bar recorder had a 2 hour limit… lol

But I would be happy to upload it and share it with you all. Though its kinda boring. I spent most of it clearing out some of the side quests for the new zone.

Still crashed.

Stuttering went away with patch and gameplay is much smoother but still crashing. Also, it appears that it’s a bit longer this time.

3DDA5CF9-45FF-42EF-8E87-BFFE4C5C16F5

1 Like

Simply request a refund, they just wont bother unless people vote with their wallet. Its been like this for several seasons.

1 Like

Crashes every 1-5 minutes still happening. Still no support of acknowledgement from Blizzard other than some useless generic solutions page that doesn’t work or directing people to the forums which they continue to ignore.
By the way, asking for a refund to the expansion won’t even be enough since however they broke the code affects the game regardless of the expansion - they’ve retroactively made the entire game unplayable.

1 Like

The fun fact is i never saw a small indie company with so much crash on its game

Blizz is simply a joke

2 Likes

I’ve done this also. it fixed nothing unfortunately. still memory crash and i just had a new one saying bad file, scan and repair. this is a brand new Ryzen laptop. i have no issues with any game except D4 after this expansion.

if any Blizzard mods see this. i am going to stop playing D4 until this is fixed. and if it doesn’t get fixed i am going to uninstall and never purchase another Diablo anything anymore. This game is basically unplayable.

2 Likes

I think, you have to visit windows Event Viewer → Windows Log → System, filter to show only errors and warnings. Might be something wrong with file system or even worse - with ssd/hdd itself.

I had issues with multiple samsung “evo” drives, which died (bad blocks) in one year without any major load, so… might be the case?

I too have a 4090 and similar systme specs and experience the same thing. Pissed.

2 Likes

I was just wondering. For those with crashing and locking up are you all using Mouse & Keyboard or Controller?

Reason I’m asking this is I normally play with a Controller. The other day when I was playing, I decide to play with Mouse & Keyboard just to see if any of the patches might have fixed stuff since I last played and now using those inputs, I get no lockups or crashes. I haven’t tried to plug in the controller again yet to see if I crash or not, ill test that out in a few lol

I just don’t even want to play anymore - it just keeps crashing at random ,often at the worst places, like at the end of a helltide or pit run.

I have tried every gimmick in the article, and nothing works. I opened at icket, and blizzard just marked it as resolved.

I wish I had arefund

3 Likes

Keyboard and mouse 100%

2 Likes

Receiving constant crashes. 5700X3D, 16gbs Ram, RX 5700xt, windows 11.
E 2024.10.27 21:51:23.261531 4942 [Crash] Thread 'RenderThread' handling fatal error
E 2024.10.27 21:51:23.263482 4942 [Crash] Crashed thread: 'RenderThread' (0x3b40)

Same with me, Crashes every hour or so, I’ve noticed that my CPU always runs in the mid 70’s degrees at all time.
The crashes are often happening when I join a party(or leave one)
It sort of reminds me of when we couldn’t join people’s party and had to exit the game and relog. Crashes are just as bad as you have to relog there too lol
Error I get : 5476A7FC-2F2D-45B4-8CA5-32ADBCAC57E2

AMD Ryzen 9 7900 3xd
Gigabyte OC Gaming Edition RTX 4090
Corsair Vengeance 64 GB ram (2x32GB) @ 6000mhz

Game crashes during combat, or if I’m just standing still in town. It’s frustrating now! I never had these crashes before the expansion.

7800x3d / 4080 / 32gb of DDR5 memory

The crashing is becoming untenable at this point Blizz…

BC8B3347-2367-45F8-BE35-AA3EFD0CA445

I am officially done with this now…

Hopefully it will be fixed by next season.

6DDBE0D3-A74B-499F-AEBF-6A2474DA24CE

2 Likes

Crashes every hour since VoH. Tech support gives cookie cutter recommendations that fix nothing. If I restart the game about every hour before it crashes no crashes occur. I’ve gone as far as to reinstall Windows along with every other recommendation given with no avail. 100% a Blizzard problem.

7950X3D 32GB RAM 3090

2 Likes

+1
7800x3d 32gb ram 4090 Win11

100% with you there. I’ve tried changing the Paging File to auto and to a fixed min/max value, updating Firmware, BiOS, and Drivers of the graphics card (from the last known stable version). The only thing that maybe gives me a few extra stable minutes without frame stutters is disabling everything related to Crossplay, however it will still crash reliably every 1.5 hours or so. It does not happen just from porting to town anymore, though… that was a big issue previously.

To your point, as long as I time my Elixers and similar stuff to when I just log in and start playing, I can close and reopen again before the crash to start playing again. It’s the only workaround right now.

Somebody in another thread suggested turning off VSYNC, however that is simply not an option. I’m on a 55" 4K 120hz OLED screen and the tearing is unbearable even with GSYNC enabled.

It is 100% something in the game code that changed causing this. If I was Blizzard I would strongly recommend going through the code that impacted memory and or “stability” settings going from D4 to VoH. It’s been like this since launch.

TL;DR: New CPU fixed the issue.

As the original poster, I’ve resolved my issue, but I’m not marking it as “fixed” since many people are facing similar issues, and my solution wasn’t straightforward (or cheap).

After extensive troubleshooting with Windows, BIOS updates and rollbacks, platform and GPU drivers, numerous settings adjustments, and multiple reinstalls and repairs of Diablo 4, I decided to swap out my DDR5 RAM for a different set, hoping this would solve the issue.

No change. I then tried a new motherboard, using both my original RAM and a spare set I had (even purchased a new set). Still no change.

Being a PC enthusiast, I have a closet full of parts, so I kept testing.

I eventually tried a third motherboard from a different manufacturer (ASRock Taichi, MSI Tomahawk, and Asus Strix, all on the Z790 chipset). But yet again, no improvement.

After further testing, it turned out that my 13900K had a degraded memory controller. I managed to keep the system somewhat stable by switching to single-channel mode instead of dual, but it wasn’t a real solution—Diablo 4 still crashed.

Finally, after monitoring temperatures and noticing unusual fluctuations in power demand, I replaced my 13900K with a 14900KF, and the issues disappeared immediately.

I know it might sound petty, but I still suspect Diablo 4 contributed to this. I never had issues before the 2.0 update, and since then, I’ve seen (as we all have) Diablo 4 consume massive amounts of RAM and heavily utilize the page file.

My 13900K is a couple of years old, so it could be normal wear and tear, but I believe the latest D4 build put excessive stress on both RAM and the memory controller. This situation is rare, but not unheard of. I wasn’t running any overclocks other than XMP, and I even disabled XMP during most of my troubleshooting.

As a water-cooling hobbyist, temperatures were always under control and never close to TJmax, but I did notice odd and intermittent temperature spikes during my testing, which only increased my suspicion.

Since installing the new CPU, my system now handles 64GB of RAM in dual-channel setup perfectly, and I’ve played D4 for hours without any issues or crashing. I haven’t even needed to adjust the page file with the new hardware.

If you’re facing similar issues, I recommend monitoring CPU temps and power usage, particularly around the memory controller (VCCSA and VDDQ). Also, pay close attention to power draw of these, the VCORE, and your GPU compared to your PSU’s output. Inconsistent or (dirty) power could also lead to issues like mine.

This may not be the exact issue others are experiencing, but it’s worth investigating if you have the option.