Ah such a shame - thanks Blizzard for releasing a patch, I was very hopeful but sadly I still crash with fenris error… this unfortunately hasn’t solved it yet for me (and it looks like many others also). Please keep trying! We believe in you!! 
PS. here’s another fenris code, in case it helps:
93817ABF-AFBC-42A4-8681-1AE04A3F1C52
I’d say based on what seems to be the metric Blizz judges their updates by, that this update is a resounding success; that metric being making things worse than the previous update.
Crashing every 20-30 mins
After downloading this evening’s patch (not the hotfix, the actual patch) I’m crashing hard enough that there’s not even a fenris error window where I can report it. Just straight to desktop as if it were never even launched.
This is way worse than it was even an hour ago.
So far so good over here! A few frame dips, but no crashes yet. Noice!
I can’t even run around town now before crashing. Somehow it is significantly worse. Previously I might have been lucky enough to finish a nightmare dungeon before I crashed. Now I literally can’t even play the game at all.
Freezes within 10 secs and then black screen and reboot. Try again Blizzard.
I managed to fix my crashing after hours of trial and error so i hope this can help someone still crashing even after the patch today. For reference i was crashing in game leading up to the game crashing at character screen 5-6 times in a row with the black screen reboot until i gave up. I’ll number the steps I took to make it simple.
Uninstall Diablo IV, then uninstall Battle.Net through windows.
*I think this this is where the problem is. I noticed battle.net and blizzard folders still in 3 different locations after uninstalling.
Right click windows start menu and go to file explorer. Make sure to turn on show hidden items. View>Show>Hidden Items
We will be deleting any folder associated with blizzard/battle.net/Diablo after the uninstalling. For me it was in 3 different places on my C drive under these locations.
Last step was to Type cmd (Command Prompt) in the Start menu search bar, then click Run as administrator. Type chkdsk and hit Enter.
*Corrupted data was actually found and fixed in my case.
Restart PC. I have not crashed since.
Reinstall everything and pray it works. Good Luck yall.
edit User folder location was missing a step.
Awesome. this last little patch fixed my crashing issue as well. I don’t even see a VRam memory leak anymore. DLSS off everything maxed out even textures. 9700k @5ghz and a rtx3080 with 32GB system RAM and 1440p res. I’m seeing about 9.8gb VRam usage out of 10gb. but it’s not rising, just steadily jugging along.
Are you reading the posts still the patch didn’t work.
For those still having problems and using intel, try disabling Intel Turboboost (BIOS)
That was the fix for me
4 day weekend for blizz has started…
I’m going to try uninstalling a reinstalling a 37.4 gig download to fix it.
LOL I know right.
I’ll get right on that “fix”.
Yup same issue here. Was not a problem before this update.
Still crashing. Game goes real laggy/stuttery and then straight to desktop.
2 crashes in under an hour in this latest update.
This was not a problem prior to 4 days ago.
Edit:
Aaaaand another one. Barely 5 minutes in.
45E2996C-88D0-4BB2-A6D9-7AC5DBA7656B
might have fixed it for me… we’ll see but so far it’s been 3 NMD’s without crashing! before this update i was at 1 MAX
So i woke up, saw the new patch for crashing. Hoping it will finally resolve but NOPE.
I 2023.07.01 01:08:00.820054 [Crash] GetLastError() = 126
The specified module could not be found.
E 2023.07.01 01:08:00.820180 [Game] pm_dx12::Device:
Map Failed - Error : DeviceLost, SystemCode : 0x887A0006 (DXGI_ERROR_DEVICE_HUNG)
E 2023.07.01 01:08:00.820201 [Game] [Prism] Buffer pmUploadStream::Reserve() - DeviceLost, Device removed reason : S_OK
I 2023.07.01 01:08:00.820206 [Crash] Thread ‘RenderThread’ handling fatal error
just crushed after new update
Ah okay makes sense now, my game just froze and crashed, was wondering if anyone else is having the same issue, yeah whatever recent update was done did not fix it.