I’ve never experienced this ever with diablo 4
Getting this error after it crashes. And it crashes a lot, during a boss fight, looking at loot, going through a door.
8B8718BB-364F-4B80-A82D-CEDFD85E683F
And yes I’ve tried everything, reinstalling the game, moving the game to a different ssd.
I don’t know what to do anymore, this is pulling me out of the game.
Same here
216D5B01-36AF-4D41-AD41-6BB1EBC52938
Game crashed at least 8 times in first 12 hours of vessel launch for me. pc, windows 11, rtx 3070, latest nvidia drivers, 4k borderless windowed. Nothing else crashes on my machine ever. Did scan/repair.
It happens at the most random times.
Some people are playing hardcore, so it cant imagine this is happening to everyone. Crash reoprter is coming up every time, so blizzard is getting the crash reports.
Yep frequent Fenris game crashes…just now got one while doing Hell tide. Heil Blizz 
Same here, we need a hotfix for this. Its happening after the latest patch/vessel of hatred release. Never happend before, all other games working well. Got fenris errors with severel error codes, PC reboot and crash to desktop. i bought a 40€ DLC for beta testing… AGAIN! The start of classic was also a terrible experience. THAT CANT BE HAPPEN AGAIN!
Refund is coming
Same problem here, tried restarting, repairing, windows updates, running with -disableds as command line, lowering all settings to medium. On Windows 11 24H2 with latest video card driver. 7800X3D, 64GB RAM and a 4080 super. It only happens to this game and never happened in any previous patch. Is unplayable due to the amount of crashes I am getting.
Fenris is in game for like year+ btw DO NOT expect any fix for it. You can lower how often it happen but cant get rid of it and people who say they find fix are simply lying. I am having it too and i did NOT spend thousands of Euro on high end PC to play at low settings and resolution Blizzard…
same here crashing constantly, worked okay few months ago, since expansion crashes.
E4B96B0D-7414-4E3F-98F6-582EDC98ABF8
Same. Unplayable since DLC and ‘patch’ today - before that np. Crahes to desktop, frozen loading screens for dungeons (however small/big/quest related), lags etc.
Guys,
i found the problem to be nvidias latest driver. Revert back to driver Version 561.09.
My FPS is back to what it was before the patch, as it was more than halfed after it and i didn´t crash so far.
Exacly. This is nvidia fault.
On 561.09 is fine.
Only partially. Reverting the driver fixes the BSOD’d but, not the game, crashes. The game crashing, stuttering, etc are all due to the VoH patch. It’s hitting lots of folks. There are posts all over the net atm, about it. Mine just crashed, even after I reverted my drivers back to 561.09. Blizz doing what Blizz does best.
Can confirm that the game randomly crashes since the update. Tried reverting to Nvidia drivers 561.09 as some people suggested, but this didn’t help. Just before crashing, the game starts to stutter and lag. Errors also seem random, sometime it says data is corrupted, sometimes it shows out of memory (which is clearly not the case with only 40% of memory used), sometimes I just get BSODs or CTDs.
Random crashes to desktop happen to me, not frequent but they do happen. All latest drivers and 32gb ram doesn’t help.
Same problem here crashes up to bsod.
Asus Rampage 6 Encore
i9 10980XE
2 x 2080 Super Strix 8GB with nvlink
64GB Ram
I do some checkups
Check for updates windows 11 → all installed / nvidia → Version 565.90
RAM check with ramdisk — passed
GPU check with nvidia tool mats/mods — passed on both cards
Reinstall the whole System / Windows / install driver → no result error is not fixed.
Check the Minidump from Windows
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
nvlddmkm+0x138a899:
fffff804628ea899 c70001000000 mov dword ptr [rax],1 ds:002b:0000000000000000=???
FAULTING_THREAD: ffff840fbf5b2040
EXCEPTION_RECORD: fffff4076c2acf18 – (.exr 0xfffff4076c2acf18)
ExceptionAddress: fffff804628ea899 (nvlddmkm+0x000000000138a899)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000
CONTEXT: fffff4076c2ac700 – (.cxr 0xfffff4076c2ac700)
rax=0000000000000000 rbx=0000000000000000 rcx=0a7361d083010000
rdx=c00004d6bfde1676 rsi=0000000000000018 rdi=ffff840fbf5be000
rip=fffff804628ea899 rsp=fffff4076c2ad150 rbp=0000000000000141
r8=0000000000000010 r9=0000000000000010 r10=0000000000000001
r11=fffff4076c2ad0a0 r12=000000000000000e r13=0000000000000141
r14=ffffd408c665ffe4 r15=0000000000200000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
nvlddmkm+0x138a899:
fffff804628ea899 c70001000000 mov dword ptr [rax],1 ds:002b:0000000000000000=???
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
WRITE_ADDRESS: fffff804b5fc34b0: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000000000
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000000
EXCEPTION_STR: 0xc0000005
It looks thats an application / Nvidia driver problem.
Please Blizzard Entertainment please Fix this or get in touch with Nvidia to solve this Problem.
Cheers
Shinji
Adding my annoyance here.
Totally unacceptable. I’m level 53 on my character and that has been purely through repeated run throughs of the same questline over and over again because the PC crashes with the dreaded nvlddmkm issue and it sends me back to the start of the chain. Most time, I can’t even get to log in before it crashes.
Oddly, this same issue occurred many times towards the start of D4 when it was released, but patches clearly fixed this as they seemed to have disappeared.
Now, with VoH it’s back with a vengeance … and way worse than before.
Yes, yes - I’ve tried DDU/driver rollback, playing with config, re-installing, uninstalling, installing, changing my net cables from orange to green/yellow/red ones and even leaping over the garden-fence whilst juggling half-filled bottles of piss but still to no avail !!!
FFS Blizz/NVidia - communicate - this forum topic is one of MANY around. I understand “teething” issues - but these are not teething issues, these are core and fundamental problems that need addressing your end, and not palming us off with endless “have you tried resetting your router to default IP address and clearing the contents of your freezer?”.
I am paragon 154, and my D4:VoH has crashed (to desktop / crash reporter) EVERY 40-90 minutes all the way there, like clockwork… never had crashes in og:D4… or any game really…
Still happening on 2.0.2c - I’ve done 2x scan/repair and a full uninstall/reinstall, windows update, driver update, everything. Nothing I can do fixes it.
I put up with the crashes during leveling… but now that I’m doing runs that cost materials to start, and it’s crashing in the middle and ruining my run and stealing my mats… I am pretty unmotivated to keep getting wacked and losing scarce materials. So I’m resigned to grinding whispers and running the pit for glyph upgrades. (and i am not even thinking about playing hardcore, which I love and normally play)
I am here writing this post, because a crash just ruined an awesome upgraded undercity run. Ugh.
please fix, blizzard!
With so many people having this happen, I don’t think it’s hardware related, but for reference…
Intel i9-12900KF (24 core)
32GB RAM
NVidia 3060 Ti / 8GB vram
Windowed fullscreen - 4k
Now I know it’s not worth wasting time on reinstalling. I had similar crashes in beta d4.
On 560.94 is fine. ( RTX 3070 + Ryzen 5 5600X - Win 24H2)
“!!!The situation has changed, after twelve hours it crashed again.!!!”
Same, it seems like it has been every boss fight the game has crashed at some point during it