New patch didn’t fix the crashing.
Crashed after playing for 1 hour 21 minutes. Fenris code 18B772A8-CDA1-480D-BB0A-234CC4B637E4
2 Likes
I crashed 6 times already. 5 x during Dark Citadel and 1 x after killing Andariel. 6 crashes in less then 1 hour! Go figure…
2 Likes
Still crashing with Fenris on 2.0.3 patch.
2 Likes
Can confirm still crashes with patch 2.0.3 and eats up a lot of RAM.
1 Like
While I was in a rift walker
4EDADF31-3277-45AE-B06D-E43715E88E0B
1 Like
No change for me, 2.0.3 still crashes approx. every hour.
1 Like
I never experienced any crash or performance issue until this new season started. It seems the latest patch made it even worse. The game crashed 4 times yesterday. One time all the mobs just froze during a Horde while I was still able to move around. Impossible to leave the arena, had to exit the game. The other problems happened while teleporting to town. The 2D static layer with the game HUD was visible, sound was fine but for the rest it was all black screen. Again, had to close the game and reconnect.
There is a new patch every couple of days but so far, I haven’t seen much improvement when it comes to the stability of the game.
5 Likes
still getting Fenris error
I was having this too, had to set an alarm on my phone for 1 hour and then restart… but sometimes being in a dungeon I’d go over, and BAM CTD. However, what I did was change my page file size from 8GB max to 50GB max, and now I can play several hours without a problem.
Rolling back Nvidia driver to 561 fixed it for me. I had tried everything else. Please install the last driver before the current one and try.
blizzard fix your god damn f’ing game already this is bs that the crashing is still going on to this day
Mine is stable now, with latest NVidia driver. I don’t think it’s good idea to downgrade the driver just for one game, as generally an update is to fix or improve something. I suggest to reduce the textures to mid, if you got some vram issue.
i usually play in 4k everything on high and before the new xpac it was working flawlessly but since the update maybe a hour in and it crashes
2 Likes
yep, sound like an out of VRam memory. Maybe they have put more textures with VoH so it reach the limit, especially in 4k. It comes very fast, as a single 4k texture take around 90MB depending of the compression. With 100 4k textures, you’re already at 9GB.
It’s hard to manage VRAM, most games just crash when you are out of VRam.
Me too… 12700KF and 4060… Random crashes about every 2 hours.
i’m fed up 
with all the constant crashing , now i can’t launch Diablo 4 anymore beacause supposedly " my windows is not supported" all the diablo team are a joke ,never acknowledge the problems that everyone has.
“don’t ruin all that work”
Still closing down.
C783DF01-D183-433E-B479-148B1CC6319A
same here intel i7 14700kf with a Nvidia 4060ti (i know its a 4060ti) 32gb ddr5 and it has been crashing like crazy!!! and with each patch it seems to be getting worse and i havent had these problems post VoH
Yep still happening with latest update.
Intel 14700KF
Nvidia 4070
It does seem to happen less with Nvidia driver 561.09 but I haven’t tested the one for Veilguard. The Thone and Liberty update was causing Fenris errors about once an hour. Other things that seem help:
- Textures to Medium (high if you can support it)
- Disable peripheral lighting
- Manually set your swap file size (see other posts)
- Weirdly disabling browser hardware acceleration in the BattleNet app helped stabilize the game (don’t ask me why - this makes no sense)
None of this makes sense. When the game is running, honestly it runs well. No issues on any other games. Even if this were not a game issue, the error message box is like the devs / qa’s are trolling. I mean just put the error log in the window for the love of god.
1 Like