The game started to crash at the character select screen again. It only started to happen the last 2 to 3 days. Somewhere between Sept 25 to Sep 29.
Anyone else having this issue?
Tried to restrict to 60fps, windows mode, turn off HDR, vsync off, dlss off etc. etc.
Nothing helps
i5 12600k and RTX 3070 Ti
Sort of the same.
I can’t even get to character select. The game crashes right just as the Blizzard logo is loading (that red screen). Sometimes it crashes before then.
I can’t tell the exact date. I haven’t loaded up the client in a couple of weeks. There was an update I downloaded for the game not too long ago. Unfortunately, I let it download but didn’t attempt to play to see if that was the root cause.
Here is another thread where I had other suggestions as well:
Have either of you tried renaming the LocalPrefs file? (while the game and the launcher aren’t running)
Barring that.
Try a DNS Flush. Command prompt, put in
ipconfig /flushdns
and then hit Enter.
Then restart your PC (restart, not shut down) and try again.
You can also set the launcher to Exit when playing a game so that it closes. Sometimes that helps.
Yeah none of those worked.
So guess just wait until Blizzard gets around to fixing it.
It was working fine for me the weekend of sept 22.
I did notice i had to download something not too long ago.
I tried everything mentioned in your second post.
I had this issue I think around mid June but it went away for all of Season 1. Now it is doing the same thing. When my game crashes my PC reboots. Is there a setting that is making this happen? I would have thought maybe just the game would crash.
I have another pc. i5 6600k on gtx 1070. It works fine so I’m not really sure what the issue is.
Well, in a sense, that’s good.
It means it has to be something with your PC the game doesn’t like.
Now exactly what that might be is the question.
Its cases like these, that I wish I could have the PC on my bench in front of me and troubleshoot the issue. But alas, that isn’t an option.
It was one reason I even had gone as far as trying to force one to goof up, but that didn’t work either. (I had literally built an AMD system in an effort to make a system that would fail to play the game or crash) All I ended up with was a game that could play at 4K on a box that it shouldn’t have been able to. It did struggle, but that was it. It would play, just with poor performance. I ended up giving up on that project and selling that system and gave the video card to my son. lol
I am still having this behavior a couple of weeks later.
Even did full uninstall and reinstall. Same issue.
Maybe? It worked fine though during launch and a good chunk of S1.
yup I’m in the same boat… D4 worked without any issues up to last weekend. now constant random crashes to desktop between 0-10 minutes in.
if I run D4 in background / browser in foreground it seems to crash faster than staying ingame the whole time.
other games (like Starfield, Cyberpunk 2077, Destiny 2) work with no issues at all.
tried so many things to fix this with no result (closed all bg apps, removed all unneeded peripherials, played without controller, reinstalled battle.net +d4, removed settings file, tried without xmp, updated bios, run at stock/disabled all oc, updated windows, run sfc, …)
(pc, win11, 32gb ram, i13900k, rtx4090, 4k, hdr, temps all ok/green)
I can’t even make it to character selection. It crashes at the Blizzard logo, every time.
Both of you try running it in a windowed mode as a test.
You can manually edit the LocalPrefs file to do this, if the game won’t start:
Documents\Diablo IV\
LocalPrefs.txt
Look for the lines:
DisplayModeWidth “2560”
DisplayModeHeight “1440”
Change these to something lower than your monitor resolution. Such as 1440x900. (if you have 1920x1080 for example)
Then save the file and try the game again.
Some others have noted this affected the game so it would run. which is weird. Just wanted to see if it had any effect.
Same crash behavior. I always ran it in windowed mode.
DisplayModeFlags "0"
DisplayModeWindowMode "1"
DisplayModeWinLeft "0"
DisplayModeWinTop "0"
DisplayModeUIOptWidth "1024"
DisplayModeUIOptHeight "768"
DisplayModeWidth "1920"
DisplayModeHeight "1080"
DisplayModeRefreshRate "-1"
DisplayModeColorSpace "0"
DisplayModeMSAALevel "0"
Monitor "0"
True with original 1920x1080 and 1440x900 as you suggested.
Incidentally, after crashing, if I reopen the file it is set back to 1920x1080. I know the file is “saving” though as I can open and close the file without relaunching client and it keeps the 1440x900. Launching the client, set it back to 1920x1080.
I also downloaded newest nvidia driver from 2 days ago. Still no go (problem has been going on for about 2 weeks).
ok so this is really weird… as recommended I changed the setting from “Windowed (Fullscreen)” to “Windowed”.
then I played for about 45 minutes without any crash (did a few whispers and a dungeon). even put a browser window in front of the diablo window, no crash at all.
then I changed the setting back to “Windowed (Fullscreen)” and still no crash. restarted diablo (still “Windowed (Fullscreen)”) and no crash at all.
As I’m typing this the browser window is in front of the D4 fullscreen display, but it does not crash any more!?
Will have to test for a longer time but at the moment it seemed that setting to “Windowed” for some time “healed” (?) the game.
Totally unexpected but thanks for the advice. Guess I can now finish my season journey after all 
Well, that’s odd.
Maybe you have a permission issue with your game.
Try this, as a dumb idea:
Create a new account profile under Windows. Make sure it has Admin rights.
Log into that account. Fire up Battlenet and login.
Try to play here and see what it does.
It is not a permission issue with the game.
No other games suffer from this. Just D4.
What would be useful is if there was a crash report or log file of some kind I could look into. It just crashes to desktop though and says nothing.
Finally! Solved it.
So here are the steps I took.
GpuCrashReportingMode "1"
Watched install dir for a crash report/log of some kind. Noticed it was generating _FenrisDebug-# (0-6) which it kept overwriting. Timestamps didn’t quite line up, but definitely were changing. So opened up the file with the most recent timestamp.
Looked through the log and found this:
...
I 2023.10.16 15:22:23.071503 [CTelemetry] Application initialization completed in 4.77s
I 2023.10.16 15:22:23.072678 [Game] Initializing ChromaCorsair
I 2023.10.16 15:22:23.072754 [Game] Initializing ChromaRazer
I 2023.10.16 15:22:23.074352 [Game] ChromaRazer dll found (2.9.0.12|2.10.4.0)
I 2023.10.16 15:22:23.074637 [Game] ChromaRazer Init failed with error 0x426
I 2023.10.16 15:22:23.074910 [Game] ChromaEffects failed to initialize
...
Haven’t had a razer keyboard in over a year, so not sure why this popped up and only staretd failing in the last couple of months, but sure, whatever. Also, this isn’t a gpu crash report so not sure if #1 did anything.
There is also a FenrisDebug file which I found later which may always have “latest” and explain why the suffix files didn’t seem to line up with timestamp (e.g. old files get rolled up and not outright deleted - keeping a 7 file history).
DisableChromaEffects "1"
I set it from 0 to 1.
Boom game now launches.
No amount of uninstall, reinstall, modify install, low res assests, whatnot had solved it.
So if I had to guess, Blizzard has a bug that causes the game client to crash when it detects chroma software but cannot initialize it. I have razer synapse stuff installed, but configured to not start with windows.
Would have been nice if someone from Blizzard had helped me debug their app or at least pointed me to the debug/error file without having to just “figure it out”.
Yeah, this is a known problem actually. Been looking on here to find the source thread on it, but haven’t yet. But it was on the forum here at one point.
But it hasn’t affected everyone. I have it installed, but its not crashing mine. (currently using a Basilisk V2 mouse and sometimes use one of their keyboards)
Not usually my first go-to as a response to the issue you were having. But anyone experiencing similar issues can also disable Peripheral Lighting in game (Chroma Effects in the file)
Mine has been disabled since day one of launch. Probably why I don’t have issues.
I know you think you solved a big problem, and I’m glad you found it and fixed it for your system though. But this is why a lot of us suggest disabling the Peripheral Lighting options in the game settings. 
As for the suggestion, at the time there is no reason to think it wouldn’t be. And its an easy enough thing to test, and you can delete the extra account afterward. *shrug
But you solved it so, no worries.
I’m gonna test this out when I get home.
Edit - Didn’t work for me.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.