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.