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

Only thing to do now is wait afaik.

We now know that they know that we don’t know what’s going on…

1 Like

What they could do, is roll back the patch so more people can play while they find the issue. 80%-90% of these issues came after the patch. I do not understand the reasoning of the team to keep it up.

2 Likes

Did you get an actual response?

1 Like

The reason is that the majority of the playerbase is NOT having this issue, and can you imagine the murderous screaming if Blizz suddenly rolled back all the class and XP buffs? People would have their heads.

The number of people with this issue is LARGE, but it’s still in the MINORITY.

They responded in this thread. Scroll up.

Problem is that us x box and ps5 users are still hosed.

2 Likes

These changes were not there from launch for some “clever” game design on their part and i dont see any more backclash than what they already received for that. If anything, the reasonning of: “sorry, we wrote the patch badly and some users cannot play” would be their best line of reasoning so far. Would buy some good faith.

S o I crashed earlier with task manager open and watched the memory creap up to around 18gb then it crashed. No spikes or dips in anything. Just a straight crash. ( this was running high settings, DLSS set to ultra performance reflex off)

Loaded back in, turned off DLSS, and lowered to Medium settings. Since doing this. Ram has only gone as high as 16.5 and no lower than 15.4 at the time of writing this post. Touch wood, everything seems to be stable now.

I tried everything ppl have been suggesting and nothing had worked until just now. I turned my CPU OC from 5.1 to 4.8 and i have been completely stable for almost an hour now. Something is definitely funky if this is solving the issue for some of us.

Especially weird that it worked just fine before the patch with the 5.1 OC

Edit: Processor is i7 10700k with 32 gb ram and 3080 ti

Finally got them on Twitter saying they know about the isue and are trying to resolve it please please for the love of God go to Twitter and light them up.

1 Like

Hey Blizz team. I was playing fine by myself for ~1hr and then I went to do a Legion and when I got around other players, i outright crashed to desktop.

You can find a Fenris crash debug at the Pastebin link below:
d4-Fenris-Debug - Pastebin.com

Please keep us updated and don’t forget about us. It hurts to play D4 now, crash after crash after crash. Have had more than 10 today. Never ever crashed before this patch.

1 Like

I saw that @Pezradar on twitter Adam Fletcher has finally acknowledged it here on a blue post above and on his twitter. Here is the Link to it! Blow it and him up with your crash codes etc. https://twitter.com/ThePollus/status/1674344038323847171 . At least they finally Acknowledge and the word is getting around now! Literally 0 issues till the patch the other day. We have reinstalled/updated drivers/graphics and windows updates… you name it close all apps. It’s the patch 100% that is casuing an issue for some players. Maybe bugged items found in game causing it… idk… but just start making the thread known as a 911! :heart:

2 Likes

https://twitter.com/BlizzardCS/status/1674453737081798656 Looks like they’re investigating increased crashing on all platforms.

They also have replied on twitter here: https://twitter.com/BlizzardCS/status/1674503101074534404

I expect there are other replies too, but I stopped scrolling after finding those.

Yep, until this last patch I have never crashed. Not even once.
Since the last patch, constant CTD while in combat or even just idling at town. Had a hard lock last night while looking at my inventory.
This is not related to any heat or PC issues on my side. Definitely a new problem with the game itself. Pretty crappy to say the least. I can’t even get in a decent game session without a CTD.

2 Likes

i had this same issu at the release of the game but only on the last quest of act 1 in the instance ‘‘pursuit of lilith’’ and after a hotfix it was gone, but right now since last update june 27 it.s litteraly unplayebale game crash every 2-3 minutes fix your god damn game FFS

I have completely deep dived this issue is after patch! No issues prior Along with the rest of us and 0 changes. We have updated graphics drivers/windows updates/disabled all apps razer chroma etc. Not just PC players its happening to either! The patch broke somethinc. We get fenris error either after log in or within 1-3 minutes either in town in stash or fighting mobs then log back in needing to repair. Its totally unplayable atm for TONS of people we need a PTR in the future to test before patchs come out! =/ My brother can play 0 issues but I cant, Ive changed nothing and it doesnt make sense why some can and some cant… but its happeneing to alot of people! We need a ROLLBACK please! =/ We have tried EVERYTHING. Thank you for finally Acnkowleding the problem! I hope it gets fixed ASAP we have been waiting days since patch praying you see our responses! lol =/

3 Likes

I’ve also repaired files and uninstalled and reinstalled over 5 times trying deleting everything and anything diablo 4 before reinstalling. It’s now 100% solved guarenteed the patch itself. =/

Reword that you meant zero issues prior to the patch

1 Like

So that hasn’t worked. It’s better, in terms of no memory creepage. But it still just straight crashes.

My latest Fenris code 951D33E3-B3E4-4EB4-8F1E-B04C5FB19319