I never had Diablo 4 crash as much as it does now, in fact I rarely ever encountered it across the last 2 years. I can’t pinpoint the exact date when things started to go awry, but it’s maybe weeks or a month ago.
I get constant Graphics Initialization Failed game crashes, almost in 5 minute intervals.
I put up the Task Manager monitor just to see what’s going on. I have enough RAM (64GB) and with the game running I use up about 22GB, my CPU (AMD 5950X) and a MSI Suprim X 4090 GPU (max 60°C) aren’t overheating and neither are they used at 100% all the time. The crash simply occurs randomyl and I can’t even finish a single infernal hordes run sometiems of 6 waves…
I already lowered all the quality graphics settings to the bare minimum. I left resolution scaling on DLSS super resolution and limited max foreground fps to 240 and background to 30, limited cutsences enabled, peripheral lighting enabled and vertical sync disabled. View distance is set to far.
What else can I do to try to fix this? I still believe it’s a fautl on Blizzard’s end, since I never had these issues before and my PC is more than capable to handle any graphics settings on D4.
I’m using the very latest NVidia driver and the very latest Windows 11 version.
4 Likes
If your Drivers are up to date.
Start by turning Ray Tracing off.
And your 4090 probably doesn’t need DLSS either. You can turn resolution scaling off.
Set your backgroundfps to 8. Yes 8.
Set your foreground to 120 and go from there incrementally up till you, see problems again.
Also lower your shadow, contact shadows, and clutter settings to high or medium.
Uncheck the last 2 boxes Distortion and Chromatic Aberration. You can turn these back on or up one at a time once you get to stable.
Also run HWMonitor or something similar that can show you temps and thresholds hit as you play for both CPU and GPU.
Forgot to mention, ray tracing is completely off.
I’ll turn down the fps of fore- and background. All the quality settings are already on the most minimal setting already, so nothing to lower there.
While I can do these adjustments, I still believe that the main problem lies with Blizzard’s tweaks during the latest few updates. I never had this issues before and I was running all the best possible settings for years now…
1 Like
Oh I don’t doubt it is Blizzard and patch related…I did a search and this popped up
look through that in case someone found a solution.
I have a 3090ti and have had to troubleshoot at many patches and that is basically how I would start…lower settings till it stabilizes then work back up.
Try this also, it may help, in nVidia control panel Manage3d settings/Shader Cache Size…
Set that to something else. Hit apply, then set it back, and hit apply. What that will do is force the shader cache folder to refill.
I disabled DLSS, lowered everything to minimum, deactivated the distortion and chromatic aberration, lowered FPS, cleared the shader cache as you recommended. Everything’s at the lowest possible setting basically (FPS I can go down further but 120 shouldn’t be all that much with everything on zero) yet it still produces the Graphics Initialization Failed error… this is truly some diabolic ish…
Thanks for your recommendations, but nothing seems to work. I cannot imagine that this isn’t Blizzard’s fault. Hope they see this thread and chime in and explain where the issue might…
1 Like
Yeah sometimes you just need working code. 
Sorry I could not be of more help.
Did that other thread help at all?
Never buy flagship graphics card…premium price comes with premium issues…
Look im only on 3060 no issues at all at 1440p
Lol I got a laptop with a 6800 rtx and it runs it with max graphics and ray tracing, having to lower graphics to play d4 with a 4090 is just insane, and people still think there isn’t a memory leak issue lol
2 Likes
You should update your motherboard BIOS. Are you running a 14th gen intel CPU? I was having very similar issues that started a few months ago until I updated my Bios. I’ve been playing for about a week straight and have not crashed once.
The only problem I get once in a while is weird stuttering, not FPS drops, no change in FPS at all actually. It’s a continuous effect as if the frames are displayed in the wrong order. It only happens with DLSS frame generation enabled. The issue stops when I disable frame generation. So I turned it off, I don’t need it anyway.
Here’s the thing though: every time I log on, it’s enabled again. I can only conclude Blizzard is doing something wrong and I’d be very surprised if this is the only thing wrong with the game. My advice is, double-check your settings when you log on, make sure everything is what you’ve set it to. It might no longer be.
Dlss is only used if the card is unable to render graphics natively…these new tech/gimmick comes eith odd issues
Not the other way around
My unlimited foreground FPS (while actually playing and having a lot going on on the screen) is more than twice what I set the limit to. I set it to a few frames over the refresh rate of the lousy monitor I’m currently using because it’s pointless to have my GPU exert itself unnecessarily. I absolutely have no need for frame generation, and if somehow I did, I’d want to see that need by seeing the game struggle so I can fix my settings myself. I don’t want an option I expessly disabled to automatically be re-enabled.
Come to think of it, the last time the bug happened was right after a complete freeze lasting for over a second. I guess that’s the trigger to mess with my settings.
Ok, DLSS is fake frames. now thats out of the way =)
-
Now how i fixed my issue with random crashes now and then, and my friend having constant crashes.
Redownload the game without High-resolution assets. or remove them from the current install. ( i would recommend reinstalling the game, so its no confusion in files. )
-
for the part where some of you have settings resetting.
Can have something to another setting linked to it.
But most likely a config error,
Suggestion, go to : C:\Users\USERNAME\Documents\Diablo IV
back up localprefs/localprefsPTR and delete the file.
make new settings and see if that helps.
If any of this helped you, let me know !
try setting the battle net client to exit after the game starts.
its overlay could be causing the crash.
Yeah most of the issues in this game are with higher end cards…if you haven’t noticed by now.
I always say turn ray tracing off until you fix the issue because their implementation of RT is pretty bad.
1 Like
Thanks for all the suggestions, guys! Here’s a list of everything I’ve tried so far:
-
All graphics preferences set to minimum and all the extra higher quality options, like ray tracing and DLSS, deactivated
-
Reduced FPS down to 60 (foreground) and 5 (background)
-
Reinstalled the game with and without high-resolution assets to two separate drives (both SSDs)
-
Set the battle.net client to exit after game start
-
Installed the latest BIOS firmware for my Gigabyte B550 Vision D Motherboard which is equipped with an AMD 5950x CPU
-
Made sure I got the latest Nvidia drivers and Windows 11 updates installed
-
Reset the shader cache
None of it worked, the game still leads to the same graphics initialization error.
I’m using a Samsung G9 ultrawide monitor which can handle up to 240Hz, not sure if this is important info or not.
At this point, I’m not sure what else I should try. I’m heavily leaning towards one of the latest few updates being the culprit behind all this. Blizzard messed with a well-working setup and now it’s just crapping out after 2 waves of infernal hordes… i really hope they hotfix this mess. Maybe it’s messed up due to the PTR of season 9? I really don’t understand what’s going on and how you can mess up a working formula this much…
1 Like
Ugh. I bought a G9 at Micro Center and had so many problems with it I took it back and got a different OLED. Too many games don’t support the ultra wide, random 1.5 second black screens while gaming, and weird graphic errors. Had it paired with a 4070 ti. Beautiful monitor, but way too buggy for my taste.
That is your problem. Roll back to the March 2024 572.83. Anything newer my laptop will not initialize D4. I have a 4080 in my gaming PC. It will initialize with the latest driver but 572.83 works better. The newer driver seems to run out of memory faster.
If 572.83 doesn’t work keep trying older versions until one does. S6 I had to use a 1 year old driver to stabilize the game.
Check for overheating as well. There are programs to force the GPU fans to run wherever you want rather than stock reactive settings. I have had to do that in the past.
Was fine until VoH released then all these crashes/issues started. Very bad coding for the extra map, etc.
Thank you for the feedback.
I run d4 on a 5800x3d with a 3090ti, in windows 10.
the difference we have, is your game using 22gb ram, and my game is running on 9…
What caused my friends constant crashes, was he was close to max usage, but i was not.
somehow it fixed my problem with random crashes tho =)
I guess you did all the things like enabled game mode in windows and such.
At this time nothing else comes to mind, but i let you know if some more solutions come to mind =) GL