![]() I always like to narrow it down with the following: Sources of TDR errors can be caused by many different issues. This is supported by the Dxdiag in the crash logs showing multiple TDR events: Your crashing is related to a TDR error, this occurs when the GPU doesn’t respond to windows on time or reports back an issue. I am posting this in hopes that it can be seen and recognized as an issue that needs attention before the ladder launch.įranchise408 Your crashing is not linked to a bug. I know the devs have stated the delayed release of launch from the time of 2.4 was to make sure they could clean up any issues before starting the ladder. None of these attempts have remedied the situation. *Scan & Repair (no problems were detected) *Running the Diablo 2 program as administrator *Reduced graphics from Ultra to High (a suggestion I’ve seen on this forum - again was able to run the game very well with Ultra graphics previously) *Tried running the game in Windows 7 Compatibility mode (a suggestion I’ve seen on this forum) Things I have attempted to remedy the situation: I had minimal performance issues with the game before 2.4, and would regularly play for hours at a time with no crashes. I am on PC, Windows 10, with an Nvidia GeForce 1060 3GB. I am crashing anywhere and everywhere in the game) I’ve seen people talking about crashes during Countess runs. It is not limited to just a specific zone (i.e. Sometimes it’s as quick as within the first 5 minutes, sometimes I might get 10-20 minutes in before it crashes, but it is consistently happening everytime I log in. Ever since the 2.4 launch, I am having constant and consistent crashes on PC everytime I log into the game. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |