Tried ALL ways, nothing is useful. Before patch all was FINE but now “Fenris” keep showing.
Blizzard Team, I do not want to offend you but what else you want from players?
My Hardware is not top of the line playing in 4K (is this not enough for 60 FPS that will cause crash) ???
I9 12900k
128GB ram 3600mhz
ROG RTX 3090TI or SLI (tried both ways)
980Pro storage
Power 1600W
Internet min speed @ 800 mbps
Fresh install Windows 10
ALL driver up to date
SYSTEM temps are all below 73 degree C during gameplay
ONLY Blizzard software is running NO other 3rd party software
ANY Blizzard Tec Support can help?
3 Likes
C774ADF4-1882-4FB7-8FBA-E7236A8A1580 another
Getting the same error. Does everyone having this error have an RTX card? Seems to be that a fair number of people posting do. Might be an issue with that which is frustrating but could be helpful for blizzard to debug
I have a RTX 3080ti with an i9
Played Both betas! Early Release! Put max hours into the game and i’ve never had this error “Fenris”. If my game ever crashed before it would be right after a hard lag but this crash happens immediately and happens over and over again. Right after this hotfix came out it started doing it almost right away i played for like 10mins before my first crash and then i try to play again and it started happening as soon as i logged back in. Please Fix this whatever your added in this hotfix it really be doing the opposite!
1 Like
Would you mind finding your fenris debug logs? They are in the main diablo 4 directory. Each one of mine looks somewhat like this:
|I 2023.06.28 14:05:48.373766|[Game] Client entered world | world: Sanctuary_Eastern_Continent | CWorldID: 524289|
|—|—|
|I 2023.06.28 14:05:48.502731|[WarpManager] Warped into destination|
|I 2023.06.28 14:05:48.846720|[WarpManager] Starting outro effect default_warp_effect_outro (239915)|
|I 2023.06.28 14:05:48.859426|[Game] Client: sHandleDisconnect | connection_id: 12|
|I 2023.06.28 14:05:48.859512|[Game] ClientDisconnect | connection_id: 12 | reason: 8 | connections_remaining: 1|
|I 2023.06.28 14:05:48.859516|[Game] ConnectionBase::Disconnect | connection_id: 12 | reason: 8 | connectiontype: 4|
|I 2023.06.28 14:05:49.842850|[WarpManager] Portal completed|
|W 2023.06.28 14:05:50.026969|[Online.Systems.CPresence] Unhandled fenris game account presence field | presence_field_id: 11|
|I 2023.06.28 14:07:35.218576|[Crash] Thread ‘MainThread’ handling fatal error|
|I 2023.06.28 14:07:35.219879|[Crash] UnhandledExceptionFilter|
|I 2023.06.28 14:07:35.220027|[Crash] Crashed thread: ‘MainThread’ (0x454c)|
… followed by
UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005) at:
DBG-OPTIONS
DBG-ADDR<00007FF6E06017E6>(“Diablo IV.exe”)
DBG-OPTIONS<>
The only common denominator in the logs is the “[Online.Systems.CPresence] Unhandled fenris game account presence field | presence_field_id: 11|”, which can repeat multiple times in the lines preceeding the first [crash] lines.
Same problem here, i have spent +200 Houres in the Game with no Chrash. After the Patch Yesterday - it Crashs all 5 mins.
3 Likes
I don’t think there’s a legit fix. Everytime I make adjustments and get a day or two with no crash, they do a minor patch and the crashes reoccur.
People who didn’t have the crashes in my clan started getting it yesterday after the patch. I am pretty sure it’s some kind of memory leak issue.
I hope this gets enough attention so it gets fixed right away! Im sad to see it happening to so many others like myself who put alot of hours into the game cause we are enjoying it so much and then all of a sudden unable to even enjoy more then a few minutes. Seems like this error been around from what i heard but it’s evolved with this new update!
Yup. Not really sure what my stats are for how long it usually goes before crashing, but capping everything at 60 fps including my monitor seemed to help stability a bit. Still crashes tho. Just gonna finish renown and maybe level some low lvl toons so I don’t lose all my nightmare keys.
1 Like
It’ll get fixed, but can’t guarantee a new update won’t bring it back in new and exciting ways xD. Sucks but overall I can’t be mad at blizzard, game dev is hard & compared to most launches these days D4 has been 9 out of 10. I accept a little suffering on my end for the… 100s of hours ive already put in without crashes lol.
1 Like
100000% a memory leak issue. Pull up ur VRAM usage, then start teleporting from town to town. each town you hit you will see the VRAM usage go up by at least 0.3GB. This will happen until it reaches max and your game crashes. The game is not expunging data from earlier zones, but instead just stacks all of it until it reaches max VRAM. I feel like blizzard knows this and doesnt want to admit they have a ton of amateurs coding their game.
6 Likes
I have 100 of these fenris crashes now, latest one is 18634D47-8D50-48D7-9F30-C47A281D1CCA.
Is there any word on if Blizzard is at least aware of the issue? Tracking? Findings? ETA on fix? 1 month? 2 months? Will we be offered refunds since the game is unplayable for me?
Thank you.
4 Likes
I had no issues last patch until yesterday. Maybe its a minion necro thing? Also I uninstalled 3 times reinstalled deleted all old files/settings/firewall bs/made bios only recognize pci-exppress since one fix claimed it was using integrated graphics/updated graphics drivers from the original diablo relased ones with nvidia to the current ones/updated windows drivers/deleted cache of whole computer under all temp file categories/basically ive tried everything lol and still I crash within 1-3 minutes of playing. I am a necro minion build if that has anything to do with it I have not tried making a new character…when I scroll through twitter comments on the post for new patch yesterday and reddit as well many people claiming they are having the same issue so im like 99% its on BLIZZARDS end. PLEASE FIX! =/
2 Likes
Sucks I’ve done everything you’ve done too and still nothing works i still crash within 10mins. If anything all that stuff delays the crash but as soon as it crashes the next crashes happen more frequently. Happens on both my new character Rouge and and main i started the game with lvl 90+ Druid. Still trying hoping i would fix itself but it doesn’t look like it’s going too just wish we can get a response from Blizzard letting us know something smh
2 Likes
Gonna test this out later!! makes sense, longer sessions w/o crashes usually involved less tping back to sell items.
wish that worked for some of us that don’t even have integrated ><
248 replies on the June 27 crash thread and still radio silence from blizzard. Smh. Guess it’s time to ask for a refund this is atrocious for a game I paid 100$ that I can’t even play anymore
6 Likes
Alright update! So, if you are crashing from a vram issue this might help. Changing the texture settings (from low to high, high to low, doesnt matter just change the setting) will RESET the memory leak! For instance, on low textures my vram steadily increased over time to about 7gb for just diablo 4. Changing the textures from low to high cut that back down to about 5.5gb. Same thing on high textures, vram goes up steadily, change it to medium or low and it will drop back down to ~5.5gb.
I still crash occasionally, but this will certainly help with the memory leak issue. Just change your texture setting when you port back to town and hopefully the Vram won’t get so high that you crash in every dungeon.
Edit: Crashed 30 seconds after posting this with textures reset xD still, might help
What you say is possible on people with memory leaks. I’m crashing before getting into town. I crash on char selection or earlier. The dump files shows memory violation exception. I’m sure they didn’t check for a null pointer on the new patch. Noob devs for sure
Same crashing issue here – Since before update and continuing on. Have over max specs that were recommended on release.