I’m sure they have thousands of these, but here’s another one to add to the pile!! 
5D407C92-B22E-4C8B-B1BF-230EDAC94BAA
First time I’ve had the time to sit and play all week and I keep crashing multiple times mid-play. 
1 Like
For information: Since the small Blizzard update + installation of the new Nvidia drivers, I no longer encounter “FENRIS” errors in game. I can now play without returning to the desktop.
Is there a changelog of this little patch?
Are you talking about the obviously not technical issues in the “technical support” forum?
Sorry if you didn’t get that, but it is kind of obvious, that flashing your bios to resolve a non-technical issue, might not make much sense.
There you go, now you know.
Just to be clear: I consider something like “my pants are not dropping” a non-technical issue.
Alright. I give up. I’ve had enough. I’ve tried DDU, reinstalling drivers after, vsync, turning off reflex, everything. I’ve been timing it. I crash every five minutes. Even leaving it idle and sitting in town. Guess I have to go out tonight after all lmao.
CD04C6D1-2276-46A8-A5CB-9C11270C1DB5
2 Likes
No issues for me since launch until I logged in today and had to install the patch. It seems like it starts when I’m at a vendor, frames start to drop, and then the game displays extremely latency with very low frame rates. Eventually I just exited to the menu, the whole time experiencing the low frame rates in the menu with the latency. Even when I get to the main menu, the same issues persist. Not until I completely quit the game and open it back up does it go back to normal. I don’t know why but the problem only seems to start when I am at a vendor in the game.
5900X CPU, 3080 10Gb GPU, 32Mb 3200MHz CL16 RAM
I’ve had this issue after updated to latest DiabloIV patch and latest Geforce driver, after that stopped working everytime when i playing around 30mins to 1 hour. blacked out then started from BIOS screen and sometimes showed up Blue screen
my PC: i7-7700k, GTX 1080ti, Win10 Pro 64bit
in-game settings relating to graphic: only textures set to high (not Ultra) and other settings to high (max), have never turned on V-sync, turning on Reflex
and i also tried verify/repair my GameData on Battle.net client but still crashing
Edit: downgraded to previous Geforce Driver but still happening BSOD (nvlddmkm.sys) ;-;
Update for anyone that is using RTX 30 series + Intel 9th+ gen specifically while having the Memory addressing errors:
I was having the same crashes (crash log shown at the bottom), went to my BIOS and set an OC/Boost freq to BELOW 5Ghz and upped the RAM voltage by .025 (1.375 vs 1.35), game has been stable for 3 days now. If you’re having this issue, suggest going into BIOS and changing these two accordingly and seeing how your game performs. May not be a fix for everyone, but has done it for me (at least from the looks of it)
0:004> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Execute
Key : Analysis.CPU.mSec
Value: 765
Key : Analysis.Elapsed.mSec
Value: 1464
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 218
Key : Analysis.Init.Elapsed.mSec
Value: 3754
Key : Analysis.Memory.CommitPeak.Mb
Value: 100
Key : Failure.Bucket
Value: SOFTWARE_NX_FAULT_c0000005_Diablo_IV.exe!Unknown
Key : Failure.Hash
Value: {a6da1791-8dd8-38db-1de8-9ef3f8a98652}
Key : Timeline.OS.Boot.DeltaSec
Value: 20288
Key : Timeline.Process.Start.DeltaSec
Value: 716
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
Key : WER.Process.Version
Value: 3.1.0.1
FILE_IN_CAB: Fenris-0.dmp
NTGLOBALFLAG: 0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
CONTEXT: (.ecxr)
rax=000000000e78e5f9 rbx=0000020c8c510000 rcx=000000000e78e5f8
rdx=00000000000001f8 rsi=0000000000000000 rdi=0000020c87bc2180
rip=00007ff7de42131f rsp=0000002c357ff450 rbp=0000000000000000
r8=000000000e78e5f9 r9=0000000000007e00 r10=0000020eaae6fbe0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000002c357ff4e0 r15=0000002c357ff4c8
iopl=0 nv up ei ng nz ac po cy
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010297
Diablo_IV+0xf9131f:
00007ff7`de42131f 807f0900 cmp byte ptr [rdi+9],0 ds:0000020c`87bc2189=00
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff7de42131f (Diablo_IV+0x0000000000f9131f)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000008
Parameter[1]: 00007ff7ca42131f
Attempt to execute non-executable address 00007ff7ca42131f
PROCESS_NAME: Diablo IV.exe
EXECUTE_ADDRESS: 7ff7ca42131f
FAILED_INSTRUCTION_ADDRESS:
Diablo_IV+f9131f
00007ff7`de42131f 807f0900 cmp byte ptr [rdi+9],0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000008
EXCEPTION_PARAMETER2: 00007ff7ca42131f
IP_ON_HEAP: 0000020c8c517c90
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.
FRAME_ONE_INVALID: 1
STACK_TEXT:
0000002c`357ff450 0000020c`8c517c90 : 00000000`0e78e9ef 00000000`00000003 00000000`00000000 00000000`00000000 : Diablo_IV+0xf9131f
0000002c`357ff458 00000000`0e78e9ef : 00000000`00000003 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0000020c`8c517c90
0000002c`357ff460 00000000`00000003 : 00000000`00000000 00000000`00000000 00000000`00000000 0000020c`8b76dec0 : 0xe78e9ef
0000002c`357ff468 00000000`00000000 : 00000000`00000000 00000000`00000000 0000020c`8b76dec0 00007ff7`de421420 : 0x3
STACK_COMMAND: ~4s; .ecxr ; kb
SYMBOL_NAME: Diablo_IV+f9131f
MODULE_NAME: Diablo_IV
IMAGE_NAME: Diablo IV.exe
FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_c0000005_Diablo_IV.exe!Unknown
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 1.0.3.42677
FAILURE_ID_HASH: {a6da1791-8dd8-38db-1de8-9ef3f8a98652}
Followup: MachineOwner
---------
type or paste code here
type or paste code here
still crashing however, please release more patches until this is fixed.
This is very annoying esp when I am going into a NMD, it black screen and I wasted my nightmare sigils. FIX IT NOW!!
It just crashed AGAIN when I click on the teleport to NMD icon on the map after I open a NMD!!!
1 Like
Still no crashes? Or did the crashing return?
played for 3 hrs and no crash for me after lasted patch
Not sure what happened, but the game didn’t crash for almost an hour now.
Was there another hotfix after that from july 1st?
Thnx this worked for me, I just uninstalled Chroma from the softwear pack and just played 5.5 hrs straight no crashes
Trying to reduce texture to medium, and turn on DLSS balanced. It seems to stop the crashing, but still monitoring.
Seems like a VRAM issue, the game is suddenly becoming very demanding and using tons of VRAM spike after the patch.
Brand new PC
MSI MAG Z790 TOMAHAWK WIFI
4070ti
i7-13700K
128GB RAM (I need this much for my work)
Windows 11 22621.1928.
Geforce driver 531.79.
All graphics settings on max. No DLSS
The game randomly crashes in dungeons about twice an hour after last update.
(sorcerer spamming ice shards)
Firstly uninstall anything controlling RGB lightning, like G HUB, CHROMA etc.
Secondly go into bios and LOAD OPTIMIZED DEFAULTS, brings everything back to stock, remove overclocks this way, only turn on XMP so your RAM memory works as it should.
Go back and test it. Hope it helps, helped for me.
1 Like
Will try this out next.
Nevermind keeps crashing again now, I am starting to think it has something to do with the amount of players playing the game since it was worse on peak times, worked pretty stable this morning, and moving into noon it starts crashing again, could be coincidence tho…
And no I didn’t play the whole day before it started again, quite the opposite, I had a 2-3 hour break came back turned the pc on started the game and it crashed after about 10 minutes
I reduced my OC on my i7 10700k from 5.1 to 4.8 while upping my voltage from 1.33 to 1.35 a few days ago and all of my crashes stopped. I didn’t have to mess with any RAM voltages or XMP stuff.
Again, a lot of us have said this same thing in this thread for the past week but somehow they still can’t figure out the issue. I’m sure it’s not exactly easy, but I hope at least they’re actually looking at what we’re saying since people are finding legit ways to make the game stable.
Also, I’ve had that 5.1 OC for 3 years now and have had 0 issues with any games I’ve played. This is definitely something that needs to be fixed in their engine.
1 Like
Playing for around two hours without incidents so far. Stuttering is gone, no disconnects, the lag with horse still the same. I’ll test a bit more to see if it is for real. I hope it reaches all of you so we all can have fun!