TL DR: Game crashed on launch because of Razer Chroma, it happens quite a lot but it’s not listed as a common issue. I can say this is not the first time a Razer program crashed my Blizz games (SCII), but I am sure a guide on self-identifcation could help the work load of Blizzard support. I’m not sure if a general Razer Incompatabillty issue should be added to the known problematic programs as I know many Blizz games have no problem with Razer, that’s for them to decide.
As I said in my case, D3 crashed because of a ChromaSDK.dll file.
#Diablo 3 was unable to initialize direct3d crash how to
I would suggest to add a simple guide on how to use the Windows Event Viewer, it’s an application which shows you the events that happened on your PC, and if an app crashed, it shows you why, super helpful. That’s not too uncommon but the thing is, Blizzard does not offer a way to quickly self-identify the problem in their guides. As it happens, Diablo 3 is incompatable with a certain version of Razer Chroma. There are many many reasons to it but my problem was not covered in any of the basic google searches. So there is a very common crash in Diablo 3 in which the screen displays the D3 logo, becomes grey and then the game crashes.
0 kommentar(er)
