I’ve run through every troubleshooting tip I can find and I am still having frequent game crashes. This has caused me to lose opals, tributes and pit progression.
I’ve tried tech support but they pushed it back on me and my system.
So, here is the latest crash code: E897CE61-4AB6-4649-A74E-906DBB1ED773
System Specs: I9-14900KF - Liquid cooled (game runs cool and stays below 70c) and updated to latest bios to fix the microcode bug
64g Ram
RTX 3080
The crashes happen after just a few hours of play, and occured even before VOH.
I’ve updated drivers, played with graphic settings (i ususally just run with the nvidia recommended and tweak from there), and followed a few guides on what others say have fixed here here on the forums but I am completely at my wits end trying to get this game stable.
So, I guess my 2 questions, are there more crash fixes coming and are you all going to do anything to compensate for the numerous materials (opals and tributes) lost due to these crashes? I was running a undercity dungeon yesterday with a unique tribute (my only one) and I crashed and lost it so you can see it’s more than a tad frustrating.
Well to answer your two questions you actually asked, with regards to the first one I would fully expect some of you to continue having issues for an unforeseeable amount of time to come.
As for the second option regarding compensation for lost consumables, I highly doubt they’re going to replace anything like that because they have no idea if you truly lost them because of a hardware problem or because you just want to get free goodies. Not to mention they probably aren’t going to care enough about that to do anything to help out. That said they do run special events sometimes where they double up things but whether that happens as a result of people losing items is another story.
Please note those are statements that are just being honest. In no way am I assuming that your problems are minimal or that you’re making up a story.
If you have the Nvidia Reflex option turned on try turning it off. It reduced the amount of crashed I had this reason from a lot (and I mean a ton) to 0.
Today’s patch (2.0.3B - version 2.0.3.58989) is…really rough.
Personally, I’ve been experiencing lots of crashes since the Vessel of Hatred release, but attempting to play today has exceeded even my frustration level (which tends to be pretty high, since I spent my career in software development – so I understand that all software has bugs).
However, I have 26 folders in Diablo IV\BlizzardError\ReportedBugs for today alone! There are a total of 194 folders in there – meaning I have experienced more than 200 crashes since the VoH release (keep in mind that many of the crashes I have experienced were not caught by Fenris and therefore have no record in the ReportedBugs folder).
Note that I played a lot of Diablo 4 during the first 6 months it was released, then took a break until shortly before VoH launched. I played dozens of hours near the end of Season 5 and the game was rock solid on my environment. Unfortunately, VoH forced me to update my Nvidia drivers (so these updated drivers could be partly to blame for the stability issues). Nevertheless, it seems that the overall quality of the game engine itself has gone down substantially with the VoH release.
I’m hoping Blizzard can get this mess sorted out soon. While I managed to only crash 18 times yesterday, the trend is definitely going in the wrong direction.
I’ll try again when I see the patch notes show another release, but – at least for now – the game just isn’t fun to play in its current state (on my particular PC).
Blizzard, if it would help to troubleshoot frequent crashes, I’d be happy to install a debug build with symbols or provide a long list of crash GUIDs. Feel free to reach out to me.
same thing. since vessel it jsut crashes to deskto pwith no error message at random, there’s no consistency to when or where, it just dies.
This is so frequent and during things like boss fights that cause materials to be lost, so that I’m basically about ot just quit altogether. This is totally unacceptable for such an expensive product.
yes, drivers are updated, even made sure BIOS is updated, reinstalled, etc etc. Just unplayable at this point
I have crashed time after time today. Usually its once every few hours but today it was every 5-10 minutes, it has happened at least 8 times just in the past four hours. It says disconnected from the server, lags out, and bam the game crashes.
Sometimes it totally takes my internet offline, but only for my PC. I have tried everything at this point and it is really frustrating considering all the materials i have lost, just like you were saying, seems like any time i use an opal i crash two minutes later.
I pay for really good unlimited fiber internet so that should not be the problem. I have zero connection issues with any other games i play, i rarely crash with any other game i play.
This is extremely demoralizing considering having payed 100$ and connection issues should be the last thing i have with the internet i pay for. please help and bring a fix.
Right now, the single biggest problem the game is having, is that it hates the later nvidia drivers with many setups.
Best driver for results right now, 561.09. You should try going back to that driver. Its not that old, and it will work fine, and may just resolve some if not all the issues. Results have varied, but one thing should be noted:
Simply rolling back or uninstalling and installing the old doesn’t always work. Sometimes you need to use the DDU tool to fully remove the later driver.
same… all of them have (@ FenrisDebug.txt) have messages like this:
E 2024.10.23 05:53:08.662589 209798 [Game] Out of memory in particle bottom acceleration structure
ps. I have 64GB RAM with unlimited page file on ssd and 3080Ti (12GB vram), seem to be bugs with (I guess, vram) memory leaks.
pps. initially, I has nvidia drivers restarts, moved back to 561.09 - these crashes stopped entirely, but game itself keep crashing once in a hour or two. No matter what I do in game, even being afk in town while smoking.
it has to be blizzard servers. I crash on both DI and D4… its always back to the load screen and it tells me I’m still on after playing… I have to log out completely to get it to recognize I’m not still in game… it’s fully Blizzard blaming shiz on us and not owning crappy servers.
Want to explain how that works? There is no such thing.
Have you set it to a specific size? THAT’S what helps. Set the min and max to 32768 for both. That should lock in your swap file and your virtual memory for the system with that amount plus your physical ram. (96GB virtual)
You shouldn’t even need a swap file with 64GB but the game likes to see a swap file in place.
The game can use a significant amount of virtual memory though.
no, it’s not about blizz servers. error log after game crash have "out of memory … " can’t tell exact phrase now, logs are on different machine, which does not crash at all yet…
well, you are right. it’s not unlimited, as hard drive have only some free space and windows usually don’t grow it more than physical memory.
“Automatically manage paging file size for all devices” - i.e. page file will grow as much, as needed.
for example, at home computer I have it allocated right now @ 32gb (as much as total memory)
anyways, “out of memory” in blizz logs is about VRam, not main ram, as I think.
i’ll tell about it in a minute, have to remote access crashing machine for this log entry…
here it is - the only suspicious thing, that I’ve noticed in log before everything started to close/shutdown in game:
“E 2024.10.23 05:52:48.734845 207891 [Game] Out of memory in particle bottom acceleration structure”
ps. will dig this log further, maybe something else get me thinking…
pps. this is main memory usage on crash time on that machine:
[Sigma] — OS memory stats ----- [Sigma] Virtual Mem Total: 69373.30 MB [Sigma] Virtual Mem Used: 38221.68 MB [Sigma] Virtual Mem Used by Process: 24479.86 MB [Sigma] Phys Mem Total: 65277.30 MB [Sigma] Phys Mem Used: 30102.46 MB [Sigma] Phys Mem Used by Process: 15931.98 MB [Sigma] — OS memory stats end-----
Sorry if I was a bit snarky earlier. But lately it just feels like some want to dismiss a suggestion without even trying it or think its crazy to make some adjustments.
I don’t blame anyone for that. We shouldn’t NEED to be doing any of this!
But its the best option to try to help get the game to play for those having issues trying some of these solutions that do work for some players.
I won’t lie, these suggestions don’t help everyone, but they do help a lot of players.
The two biggest fixes right now, are running the 561.09 version of the nvidia drivers and setting a locked size swap file.
Honestly, could not even recall, when I made it for last time… many years ago, heh. And it’s started again History repeats itself. Worth a try.
ps. Very disappointed in both nVidia and Blizzard development for this case - it seem, that they both have issues - cpu usage/crashes on latest nvidia drivers (they were almost perfect for years), D4 faults using D3D api correctly - crashing with access violation, like they passed in bad pointers etc…
yet…