Game Crashing specifically after patch 1.0.3 (June 27th) (Addressed with Patch)

Look through the bug reports. Every time my game crashed for this reason i found this:

I 2023.06.30 16:17:27.137447 [Game] [30.06.2023 17-17-27][streamline][info]commonentry.cpp:668[ngxLog] Info: No buffer registration synchronization needed!

You would think engineers would know how to use the directx API by now.

2 Likes

Still happening. This is pretty bad. RIP hc…

Just turned my fog & shadow quality down to lowest along with keeping textures on low, definitely eeks out a little more stability & leeway for the memory leak. Will definitely still crash randomly even after u reset ur textures back down to low VRAM usage lol. Ahhhhh computers are silly.

Hey thanks for your info and please provide updates if it changes.

I’m testing some hardware acceleration (only) options atm. Will try OC remove if this fails.

I had random crashes after this week’s patch and troubleshooted anytime I could.
What seems to have done it in the end was:
Lowering my OC (went from 4.8 to 4.7 GHz on my i5-9600K)
Setting FidelityFX Super Resolution 2 to Off
Disabling NVIDIA Reflex Low Latency

After doing this I had nly one crash after completing a sidequest (which was once in a 6h+ gaming session)

Mind you I have done a LOT of things (messing around with settings mainly several times, using only 1 monitor, etc) but only after doing what I mentioned above did I get a stable experience.

I had no issues whatsoever before this week’s patch that introduced the random crashes.

Here are my specs if it can help:
i5-9600K (OCed at 4.7 GHz)
16 GB RAM
GTX 1060 6GB
Running on an SSD.

Just an update on this.

The team has been working to figure out the source of the crash that players are experiencing. We will be working to prioritize and get something rolled out over hotfixes and client patches as soon as possible to address these.

14 Likes

I just finished my session with no crashes, probably like 3-4 hours of game play. I did have some minor stutters and one major one, but no crashes (only after putting graphics settings to my preference).

Fingers crossed this works for all the i9 windows 10 peeps.

Blue post to the rescue!

Hope the hotfix will drop sometimes very soon , because not being able to play for more than 3 days now sucks , i can bet people can’t wait any longer :confused:

Its been so frustrating that I bought a game for 100 euro’s this week, was able to play 1 day, then 4 days of this problem that makes it unplayable with complete radio silence from blizzards end.

A small comment like this goes a long way to feel heard and to give some peace of mind now, so thank you.

1 Like

Yeah it’s been 7 days for me, i still can’t play 5 mins without crashes, like this should be blizzard number one priority, like 1000s of people can not play the game they payed for. This ridiculous and still no fix. Try everything.

Thank you for the update. Should we anticipate any form of fix prior to the July 4th holiday? If a client update is needed, perhaps a beta client opt-in could be provided that those affected could test with?

Can you guys at least acknowledge that this thread is also exists [Main Thread] Game Freezes/Crashes GPU fans screaming when opening specific UI Elements - June 2023 - #421 by Meatface1975-1765 ?

If you don’t know, there is x3 stress to GPU when opening vendor window(ui). GPU goes from ~100watts and 50c to ~300watts and 70c. Yes, just by opening VENDOR ui. Stop ignoring this Blizzard. Ty.

1 Like

10th gen cpu here, same.
For the start i removed all OC from DRAM and CPU - no-crash-session, about 5-6 hours of nonstop helltide-NMs.
Then i turned on DRAM OC back - still no crashes.
Now i have only 3 options difference between constant crash setup - VCCIO, VSSIA voltages and offset value of my undervolting. Turn on offset - we’ll see, how it will go then.

1 Like

Hot fix is out. Working for you all?

1 Like

what hotfix ? no client update

There isn’t one, he’s Trollin’.

It’s actually there, but I didn’t notice any update downloading and if it downloaded itself and I didn’t notice it, it still crashes the game anyway…

1 Like

there’s literally zero mention to the issue we’re having in the bug fixes so yeah not fixed yet …

I HAVE A FIX. I had the same problem as you guys after the patch, mostly crashing in kovashad, sometimes in other areas. Fenris crash etc. Start the battlenet app, change it to APPEAR OFFLINE, then launch diablo. In game change to windowed, apply changes, then change it back to fullscreen windowed. I havent crashed in like 5 hours yesterday and whole morning today. DO this everytime you launch the game until blizz fix it

Edit. I dont know why it works(must be a memory leak), but it works