Enabling Nvidia DLSS helped and yesterday I played all day without error 
Today, however, I entered the game and noticed that there was an update and after this update the problem returned, 10 minutes can’t even play and it kicks out of the game, thanks blizzard!
There’s nothing like paying 90 euros for a game and not being able to play it, even a dungeon can’t be completed
I logged a ticket and was told to post here as they only had the copy and paste answers 
Same error here.
1660 Super- 535.98 Nvidia drivers
i5-10400F
16 RAM
I expected to play the game in medium quality. No way, it seems…
I can’t add much more to this topic. We are all trying to update or change game settings and system configurations. But after all… the game freezes my PC again…
My refund was not approved because I “played” for 3 or 4 hours. I don’t want to open the game again. Let’s see if they fix the game for the people that wasted 70€ or more and can not play the game…
@Cruyvvers
Can we have an update on this please. 3 days ago you said you had enough files for now.
It seems like this issue was introduced by a patch. To me it would appear that 1.0.2e is the most likely candidate however it seems strange that 1.0.2d was released on the 5th while 1.0.2e was released on the 4th.
As it is being stated that people are being refused a refund due to playing the game to much perhaps you can provide the community with information so that we can help. After all we don’t actually want a refund, at least most of us anyway, we just want to be able to play the game properly.
Cheers.
45 minutes of trying to play:
19:35 GMT 337F69AB-9568-4CBA-83D7-B4C1CBB7FA78
19:40 GMT 3B06D7B9-5955-4CE4-93E0-A6D7D86431C5
20:05 GMT C3DCD7A6-A6B4-4C69-9BAF-9648D2A9302C
20:08 GMT 7B222515-5FD1-48EB-86E1-A3562DE91A7A
20:10 GMT 8E40CFBA-7A37-4D32-B460-86535A36DB6C
20:16 GMT 87FB8ABF-3AC6-46CC-AF96-306E7D92052A
The GPU dedicated memory keeps increasing when I enter a new area, dungeon, cinematic, etc… I need to change the default graphic settings (middle → low → middle) to reset this.
Interact with an NPC overloads the hardware resources/consumption somehow.
The same issue again.
yesterday it was working fine
3887A0A8-D9D0-47ED-86A9-FA5C2761F4DF
Same issue here, played early no problems until a few days ago and now it crashes randomly. The frequency of these crashes is infuriating. Same issues that others have described.
I have attempted to modify the chroma setting, fixed and repaired files, reinstalled game, reinstalled gfx drivers, reverted gfx drivers, cleared driver cache, disabled adaptive sync, set frame rate limits to 60fps, turned off all newer NVIDIA features.
Blizzard needs to fix this asap.
Please provide an update. this situation is really bad
Got gtx970 as well, but still having crashes(
Fenris FenrisDebug
LocalPrefs LocalPrefs
Great, and my ticket has just disappeared. I guess closed without notifications. Great job, Blizzard
I am facing the same issue as well on Windows 10 + nVidia 472.19 (HP Omen Laptop, Manufacturer provided driver).
My friend who bought the same exact laptop (as we got them on a good deal) is facing also the same issues but he opted for latest Win11 + Latest nVidia 535.98.
Can you guys press start and type “event viewer” and open it. Then click on Event Viewer (Local) on the top-left side.
Now, under “Summary of administrative events”, expand “Error” and look for “nvlddmkm” under “Source” column. Double click it. Me and my friend see many (~90-100) errors at exactly the same time (down to the second) as when the crash occured. All of them are a variation of:
“The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.”
Now, if you click again on Event Viewer (local), and again under summary, but this time expand “Warning” and Double click “Display” under Source column. Here we see 1 error per crash with the message:
“Display driver nvlddmkm stopped responding and has successfully recovered.”
which points to the fact the nVidia driver crashes, which I assume the message we get in the FENRIS output “[Prism] Device removal detected” is making sense. From the point of view of the game, the driver which it needs shuts down.
I do not think there is anything wrong with the nVidia driver, or our hardware or anything, but all has to do with the game.
Again, we are talking about a 2 year old driver (mine) + the newest driver, all exhibiting the same exact errors.
I have no clue why this happens, is the game trying to call some invalid functions of the nvidia driver? Only Blizz knows, but that’s why I want to check if everyone has the same errors in event viewer, so we can provide as much detail as possible.
I want to add that besides this crash, for us the game is running perfectly, no overheating, no apparent issues up until it crashes, between every few hours down until even like 20 minutes.
I have the same issue described already many times in this thread. I bought the early access version of the game on June 1 and got to play for dozens of hours without issue for the first week, but then one of the small patches around June 7 (sorry, I don’t know which one exactly) messed everything up. In my case the game crashes every 10 minutes and I had no issues at all for the first week. This is terrible.
Hardware: AMD Ryzen 7900X CPU, Radeon 6750 XT GPU, 32GB RAM, Windows 10.
Hi @Seerix,
Yes, this is currently the information that Event Viewer is recording in my system every time there is a crash in Diablo 4.
While cycling through all the possible solutions I’ve come across on the internet (re-installing the graphics card, updating drivers, downgrading drivers, adding registry entries, performing a selective startup, re-installing the game, and a whole host of other things) the error message has changed slightly. For example in my original post, DX12 Fenris error - #24 by Stoneddragon-2396, the error was the following:
Graphics SM Global Exception on (GPC 2, TPC 3): Physical Multiple Warp Errors
Graphics SM Warp Exception on (GPC 2, TPC 3): Out Of Range Address
Graphics Exception: ESR 0x515e48=0xb000e 0x515e50=0x4 0x515e44=0xc5eb76 0x515e4c=0xe000000f
On another iteration the execption stated that a string was to large:
\Device\Video4
Variable String too Large
NVRM: Graphics TEX Exception on (GPC 2, TPC 0): TEX FORMAT
Graphics Exception: ESR 0x50ca24=0x80000000 0x50ca28=0x0 0x50ca2c=0x0 0x50ca34=0x0
The things that have remained consistent throughout is that there is warning stating:
Display driver nvlddmkm stopped responding and has successfully recovered.
And that the first Error states:
The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
My guess is that a patch release has resulted in a driver function being called with a parameter that is to large in some scenario. This is causing an exception in the graphics card driver causing it to crash. The game can then no longer access the driver so it then crashes. The driver recovers so you can then relaunch the game and repeat the whole process again.
Incidently you can see it in one view if you use Event Viewer → Windows Logs → System.
Cheers.
Same fenris issue since Day 1. Reducing graphics settings and underclocking GPU help reduce the frequency of crashing, but the game still reliably crashes every 30-60 minutes. I can leave it running in town, come back to my PC, and it will be on the desktop with the error window.
Same. I’m running 4 rigs, and only my AMD (which is also my most recent build) crashes. Even my Deck is handling it like a champ.
Yesterday was fine, but starting from today when I try to open the game, it crashes and exits itself. A pop-up window appears with a message that says “Fenris” and something about an unexpected problem, along with a long code. I have tried reinstalling the game multiple times and have set up my Windows firewall to allow Diablo 4 to run. Since my PC only has one graphics card (RTX4090), the iGPU doesn’t apply to me. Sometimes, after reinstalling the game, I can enter it, but it crashes again after a few seconds. I have also tried using the “scan and repair” option, modifying the installation, deleting and reinstalling the high-resolution textures, but the problem persists. I have closed all other applications and browsers, but it didn’t work. Additionally, I have tried modifying the “LocalPrefs.txt” file and setting ‘1’ for the DiabloChromEffects, but it didn’t solve the problem. Another step I have tried is reinstalling the graphics card driver, but it didn’t work either.
Today I installed 2 more sticks of ram (2x8) so now total of 32 and started getting the fenris error after just a few minutes ingame, hadn’t happened before (might have been pure luck :D). Now i have removed two sticks and left it with 16gb and played a few hours with no error. I’m kinda confused, is the problem with my ram or is it the game, don’t know if I should return the ram and get my mkney back or wait for blizzard to do something about it…
same thing is happening to me and ive tried everything. have yet to play the game bc i cant even get through the creating of a guy before it crashes
copied from another forum post.
Sadly a lot of people are having this error and there’s no real fix, some people have success turning off nvidia reflex, others turning off steam/discord overlay, others reducing the load of their VRAM by setting textures to medium / reducing resolution / ramping their GPU fan up to 100% at all time to cool the VRAM (GPUs don’t take VRAM temps into consideration for fan speed). with successes very mixed.
It does seem to be an issue with VRAM temps as this game is badly optimised and runs it HARD AND HOT. I’ve been arguing with support for days now and are refusing a refund because it’s been over 2hours (due to troubleshooting taking well over 2hours) which is unethical, shady, and here in Australia ILLEGAL (already reported them to ACCC).
The same issue. Please fix!!
Fenris: https://pastebin.com/bPrLayA2
LocalPref: https://pastebin.com/RhP5KzXm