Random Crashing with 2.0 - Never Happened Before Update

Thanks for the help, hope some other people find all of this information useful.

This exactly! No problems for 3 days straight of many many hours played and no crashes. Hit 60, started doing season stuff then right back to crash after crash after crash. Never stops and now I just expect it as part of the normal gameplay.

Appreciate the response! Gave it a try this morning and for the most part didnā€™t have issues. Increase min/max of page file to the recommended values, SSD has enough free space (160gb free which is over the 90gb rec), and some with the high res texture pack removed. For those still willing to try and make the game work, definitely give these a try because it helps.

It wasnā€™t until I got to a wb, waited until the last minute and then crashed. Frantically tried getting back in game but got stuck in a queue for 3 minutes and the wb was already dead by the time I got back in. Iā€™m willing to do some due diligence to try and make the game work here but this is demotivating and makes me just not want to play the game. It is worth noting that it gets significantly worse in the new areas of the game, for example this wb was in Nahantu and until then I had not been having issues.

I really like it and want to but the hoops weā€™re having to jump through in parallel to other games are pretty silly. I feel like Iā€™m spending more time trying to bend over backwards to make this work than Iā€™m actually able to play it. The technical requirements list 16gb as the amount of mem needed for ray-tracing to be on and working, when that clearly isnā€™t enough. Not that disabling it has really helped my issue either. (I can run Cyberpunk 2077 with all the bells and whistles on and HD texture pack mods installed without issue, and thatā€™s considered to be one of the more resource punishing games out there).

I honestly wouldnā€™t have bought this if I didnā€™t think my pc would struggle to run it, hopefully some optimization is done by the time next season comes out because right now the juice just ainā€™t worth the squeeze

Yeah, its a struggle, and it shouldnā€™t be. In that part we agree. I feel fortunate that I donā€™t experience these issues myself.

I have the game under Battlenet on PC and a second copy on another account under Steam. I did that mostly to be able to help troubleshoot Steam players.

But both seem to run fine on here, aside from having to stay on top of tweaks to keep the performance where I want it to be.

1 Like

For what it is worth, almost a month laterā€¦ I am still experiencing this same issue. I have updated to all the latest graphics software, OS, etcā€¦ still the issue persists. I NEVER crashed before they launched VoHā€¦

1 Like

The best thing to do to assist me in helping figure out a solution is to provide a copy of the latest FenrisDebug from your most recent crash.

You can use pastebin.com to share the contents of that file. Then you can provide a copy of the URL here to view. The forum has been allowing most people to post the URL directly, but if you cannot, highlight the URL and use the </> button in the toolbar above the reply box to render the URL un-clickable so it can be posted without having to modify it.

Same config as my computer. Mine is about a year old. Game crashes too. It should be able to run it easily. Bliz is just not doing a good job with this whole thing. Sad thing is Iā€™ve never had these issues with any of their games before.

2 Likes

First issue:

I 2024.11.28 18:32:00.062988 0 [Sigma] Disk Free Space: 35.99GB / 475.69GB (7.57%)

Your drive is nearly full. This will affect the game performance a LOT. I stand by the recommendation of keeping pretty much any drive that is actively used at no more than 66% in use. A drive that is used only as storage of files and not actively changed or updated constantly can be as full as needed. But active drives should never be that full.

You are causing the drive performance a significant loss as well, especially those drives that have wear leveling features like your Samsung as they have to keep the data moved around and attempt to write on the drive evenly. The fuller the drive, the harder that has to work, the lower the performance of it, and the faster the drive wears out.

I 2024.11.28 18:32:02.934852 0 [Game] - NVIDIA GeForce GTX 1660 SUPER (0x10de|0x21c4)

Considering you are running a GTX 1660, and using a standard 1080 display, if you have the high res packs installed, remove them. You arenā€™t benefiting from them at all.

Might not hurt to have GPU scheduling turned on. Your Windows 10 version should support it I think. Under your Display panel, under Graphics.

I 2024.11.28 18:32:03.837920 0 [Game] Video_Driver 566.14

Using the latest driver has had mixed results. The best results are using the 561.09 version still at this time. Its not that old and the game will be fine on it, as well as other games. I myself am still running on 551.31 from clear back in January of this year. O_o

Couple of suggestions regarding graphic settings for this system/card:

  • Disable Distortion
  • Disable Chromatic Aberration
  • Check the box for ā€œLow FXā€
  • Use the Medium Graphics option
  • Set an FPS cap of 60 for your frame rate (for now)
  • Disable Peripheral Lighting as well - You have a Razor peripheral, but its giving an error trying to load it. Just disable this feature.

Now with your provided file it shows that you exited the game normally according to this line:

I 2024.11.28 19:45:41.568259 227281 [Game] ---------------- UIModalNotificationManager::ShowModal 2: Are you sure you want to exit Diablo IV?

If you have a file from a time when you crashed, that could help me see what might have caused it to do that.

But I would try to make the above adjustments or some of them anyway. Especially with regards to your available drive space. That drive is very full and is impacting your gaming performance.

The graphic settings suggested, FPS cap and stuff will help bring the game performance to a more stable level. That in turn may lower the amount of crashing or disconnects.

1 Like

If you feel inclined, you can also provide me a copy of your FenrisDebug as instructed for the previous post and I can review it for any suggestions.

Copy the contents and use pastebin.com to share it.

Thanks,

Wow! thanksā€¦ I did see a notice a few months ago (when it got to around 50GB left)ā€¦ thanks for pointing this outā€¦ I will have to offload some things to my other drive.

1 Like

New wrinkle in problem have 2 older char. when first free play was offered i have no problems game running them. Bought the diablo 4 expansion bundle still have np with older char. then started new char. in 1/2 day 3 crashes with new char. The new char is seasonal if that matters.

Figures. You arenā€™t the first to state something similar.

If you can, get me a copy of the FenrisDebug from the latest crash.

You can use pastebin.com to share it.

Same issue here, I have an Intel Core i9-14900HX, an NVIDIA RTX 4070, 32 GB of RAM, the game is installed on an SSD, and all drivers are up-to-date.

See my post in your own thread.

Iā€™m game chat always talks about it

300+ replies here

Countless of posts taking about freezing after taking portals after patch

Countless of posts taking about random crashing with high end PCs with AMD and Nvidia gpus. Amd and Intel CPUs

Clearly this is a blizzard issue, just amazing how not a single blue post for months about this now. Blizzard deserves whatā€™s coming to them this Friday for not even caring about their own flagship game

1 Like

Yesterday, decided to buy Diablo: Vessel of Hatred and start to play again cause the new class Spiritborn looked good to me. Last time I played was quite a while back without any problems.

For what ever reason the same is randomly crashing on me. Seems like itā€™s crashing around every hour give or take course I never looked at a clock or anything.

Iā€™m running an 9th Gen i7 9700K , RTX 2060 12GB, 32GB DDR4 RAM, 2TB NVMe drive for games, 250GB NVMe drive for OS, Windows 11 Pro. Running the latest updates for both Windows and drivers.

I can play literally any other game out there without a single issue.

I been playing around with the graphics settings within Diablo IV. I ended up changing ā€˜NVidia Reflex Low Letencyā€™ to Disabled. Since I changed that from enabled to disabled I no longer been crashing least of yet anyways.

[EDIT] Nope, itā€™s still crashing.

Just an update for all the NVIDIA GPUā€™s in this thread there were brand new drivers on Thursday(December 5th). Iā€™m going to update and will be playing about 4 hours straight to see if I get a crash.

edit: Nerp. Still crashing. Made it to about 3 hours this time. When I crashed I was just putting a ring back into my stash.

I read through the patch notes.

Not much stands out that sounds like it would help with Diablo IV.

There are notes regarding using rollback or driver uninstall from the device manager. In a short, donā€™t use those methods, according to nVidia:

5.12 Do Not Use Windows Rollback for Graphics Drivers

  • To reinstall a previous or older NVIDIA graphics driver, do not use the Windows rollback feature. This method will not reliably restore all the previous driver files.
  • Instead, use the Windows Add and Remove programs to remove the current driver, and then install the older driver using setup.exe.

5.13 Uninstalling Drivers Using Device Manager is Not Supported

5.13.1 Issue

  • On all supported versions of Microsoft Windows, uninstalling the NVIDIA driver using the Windows Device Manager may not remove associated files or applications.

5.13.2 Explanation

  • Microsoft has confirmed that this behavior is by design. If you wish to uninstall the NVIDIA driver, it is recommended that you do so using Add and Remove Programs.

You can view the patch notes here:

https://us.download.nvidia.com/Windows/566.36/566.36-win11-win10-release-notes.pdf

The other verified way of removing a driver completely to install a version you want to use is to use the Display Driver Uninstaller tool (DDU):

https://www.wagnardsoft.com/display-driver-uninstaller-DDU-

Yeah this was more me just rolling dice this morning to see if something happened for the better.