The entire error:
“Graphics initialization failed, please ensure that your drivers are up to date and no other 3D applications or games are running and try again”
Interesting. I’ve seen a few graphics card-related errors since this recent patch, 3 in total. Has never happened prior. Can confirm that graphics card drivers are updated and I don’t have any other 3D applications or games running. Haven’t moved my PC once or moved it in any way to warrant a faulty or damaged graphics card, nor a PCIE slot connection/PSU cable coming loose.
I have for some reason been barred from posting links in this forum, don’t know if this is just the way things are on the Technical Support forum. Don’t know how to facilitate it, so I’ll explain:
It’s just a regular windows error pop-up with a grey background. This came up after my Diablo program was extremely zoomed in for ~45 seconds (second monitor was inoperable for most of that time) and then both monitors going black for ~10-15 seconds.
No Fenris code available or anything else to critically analyze.
System specs:
- Ryzen 7 9800x3D (CPU Boosted)
- GIGABYTE RTX 3070 (OC’ed via Afterburner)
- 32 GB DDR5 (6000 MT/S)
- Windows 11 Pro
Didn’t see this error with this exact spec pre-patch. Just had the unfortunate crashes every few hours that I talked about constantly on here through the start of the season (which has lessened besides these few graphics card-related errors).
One step forward, one step back. Lol.
8 Likes
Yep, I never had the error until the latest patch, Blizz seem intent on breaking the game after every patch!
2 Likes
No, you haven’t been barred, any more than anyone else here.
What you can do, is paste the URL, then highlight the URL you just pasted, then click the </> button in the menu above the reply box. That will render the link un-clickable.
You can also use pastebin.com to share the contents of the entire FenrisDebug file located in your Diablo IV installation folder. (You may have several copies, use the latest one, or the one dated for when you had the crash)
Open the file, highlight all the contents, copy, then paste them at the above site, create a new paste (you don’t need an account, just give it a name) and it will create a URL you can use here.
We can then review the file to see if anything stands out.
This!!! 100% This is happening to me all the time.
Pastebin says file to big
Copy the file in two parts. Like the first part in one file and the rest in a second file.
Did…still to big. I cant post ot here…im sure that would be a bad idea.
Even tried 1/3
Guess a reinstall of D4 cant hurt. IDK what else to do.
Tried a few older drivers with the same results
The last line says [Crash] TerminateProcess via DefaultTerminateCallback with code 0
Crashed 7 times so far today…same error. Blizzard do something!
This happens at random times, now i was just chilling by the tree of whispers doing nothing and crash… or like yesterday evening was in a 4 man doing gr110 on the last 2min diablo just froze up and had to force close the game walking in the desert same this random freeze… so i hope you wil fix it soon blizz
same here. Happens everyday after playing for a couple of hours. this bug exists for so many players, and Blizz just does not care? how easy it is to be a Blizz dev
I didn’t have the error until today. It sucks doing Infernal Hordes only to get kicked out of the game half way through and lose all progress. The stability issues with d4 are very frustrating.
I have the same issue now, started today after the patch and keep crashing with this message…
All my drivers updated, (4070 Ti Super)
Joining the club as well. Never seen this before until the patch.
Just wanted to give an update from my previous post. I was hesitant to uninstall/reinstall the game due to it’s size and Blizzard’s slow download speed but I got sick of the crashes. After a clean install I have not had any instability all day. There is no way I would have been in the game this long without a crash before. I can’t say it will fix your problem but it did for me. I will provide an update if anything changes.
Update: Just logged out a few minutes ago. Still no crashes.
1 Like
It didn’t work for me, I re-installed D4 and it ran for like 3 hours, than graphic error… Been having this issue for 3-4 days now… quite annoying while playing HC
Same here, first scan and repair after clean install both not works. I hope they fix it… I dont want to start anything like infernal or undercity, already lost way too much because this crash
1 Like
Sorry to hear 
Hopefully a solution is found.
Other than GPU, what are the rest of the specs of your machine? Where is your D4 folder stored (in bnet app under the settings cog select open in file explorer to see the full path)?
And now it crashed again, so definitely didn’t work with reinstall. 9:22pm
I’ve had no issues with Diablo IV until recent days, maybe an update after the lunar ended?
RTX 4060 Ti
Ryzen 7800X3D
and now it crashed again 11:44pm
I still have not crashed today. There must be multiple things causing these errors and that is why it’s so hard to troubleshoot. Some things I did this week.
- I saw a post on the General Forum saying to upgrade Nvidia drivers titled “PSA: NVIDIA Driver Updates to Prevent Crashes” which said to " update to driver 572.42 and perform a clean install by selecting "Custom (Advanced) during driver installation.".
- I installed the new driver and I immediately started having crashes with the Graphics initialization failed message. Imgur → /a/OrFodne
- I put up with the crashes for 2 or 3 days.
- I reverted my graphics drivers to 572.16(Jan 30th) but still crashed with same message but sometimes I crashed due to lack of ram and I have 48 gb of ram.
- I uninstalled and reinstalled D4 without the high res pack and I set the quality preset to Low.
- I’ll keep updating this. I don’t have a ton of faith that my problems are solved.
Update 2/20 @11:33pm Still no more crashes. Two times after talking to an npc tonight I thought the game would crash but it recovered.
Update 2/22 @12:53am Still not one crash. I wish I knew what the difference was as other people have tried the same steps without resolution 
Update 2/23 @11:45pm Still no crashes. Crazy
Update 5/18 @ 2am Crashes returned So frustrating.
1 Like