Hello, I am experiencing a real annoying problem that Id never did before…
The game simply crashes after a few seconds when I hit PLAY, I cant even see the introduction, seems to be loading and then crashes.
error code ID: 4E61FF45-A581-41A4-AEF0-093AC4BF0803
Need some help here
Thanks in advance
3 Likes
Check Scan and Repair or Uninstall and re install. I had the same issue earlier, before I was able to actually get into the game, but would hard lock once I hit start session on character.
Hey, LasKi! The crashes here look like something permission related. I am curious based on the behavior if Razer Synapse may be what’s causing the problem. Would you happen to have or had razer before? Could you try the following?
- Go to the Documents folder.
- Select the Diablo III folder.
- Open the D3prefs.txt file using Notepad.
- Add or Edit the following line. The value should be 1, like so:
DisableChromaEffects "1"
- Save the file.
If the problem continues, please include a DxDiag file . Copy and paste the text file created and paste it between two ~~~ like so:
~~~
DxDiag Here
~~~
If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456 )
@KILLERx14, I wasn’t able to find any crashes sent to us, but in case it may be similar, could you try the steps above? If the problem continues for you, please start a new thread. These crashes can vary depending on the cause and troubleshooting multiple different issues on one thread can cause some confusion.
@KainV, thanks for sharing what helped with the lock ups in your situation! Reinstalling the game or a repair scan is definitely a worth while step to try.
2 Likes
im having same issue. just bought game recently. first time playing. first time using blizzard. not impressed. is this normal for blizzard system. been using steam for 10 years. 300 titles in library. I don’t recall ever having this issue.
2 Likes
hey i was having the same problem but your solution fixed it XD thanks
1 Like
likewise here, 98618119-4D03-4CA0-AD28-7F3917DCD97B
Fixed it for me as well, thanks
1 Like
sorry for the delay
I did a clean/full install of windows 10 2004 compilation and the problem was solved.
But I got 2 crashes in the last 2 days…I am worry about that because I play HC and I really got lucky and both of the crashes were using shield pylon
I will continue to investigate it but I think the problem is something related to Diablo 3 and Windows 10 compilation 2004
OMG that thing with Razer Synapse was the problem for me:-) I bought a new graphics card today and the game suddenly crashed when I tried to start it. But the game finally works after I editied that line of code. Thanks for the help @Caterpepi
1 Like
This Chroma disable fixed my Issue. Thanks for helping me. I was pulling my hair out LOL
1 Like
Hello there,
I’ve been having the same bug, and that solution didnt work. For some reason I cant find that file.
Theres no D3prefs.txt in my game files. Really need help here.
you should find your file in c:\users(your username)\documents\diablo III
Inside that folder you should have a file called D3prefs.txt. Edit it and if you don’t find the line DisableChromaEffects “0” (default) just add it and change 0 to 1
It should work
I cant find that folder on c:\users(your username)\documents\diablo III.
Its not there for some reason
EDIT: I found it, thanks!
Appreciate the updates and helping each other out! If the razer chroma fix above does not resolve the issue, please start your own thread!
Crashes can be caused by a variety of issues and may not be as straight forward. Because of the intricacies of what can cause a crash, we do not assist with multiple issues on a single thread since this can cause a lot of confusion and difficulty in communication. It’s best to have these crashing issues addressed individually.
Thanks again everyone and lending a helping hand to each other 
I know this is an older post, but I just came back to D3 and was having the issue of just random crashes, saw this thread on Razer Chroma and disabled it via the .txt file. The thing I’m curious about, if this does indeed “fix” my issue, is this something Blizz is working on a fix for, or some issue within Razer’s software?
Changing the value worked for me thank you so much!