I am in no capacity a Blizzard employee by any means, but I am a decent diagnostian. Unfortunately, we need a LOT more information from you to be able to see why you’re crashing. Your system specs all use known compatible components that work, and if they’re all up to date, that means we’re looking at realistically 1 of 2 possibilities, 1 being dying / bad / not strong enough components and 2 being unknowingly bad configuration of soft/hardware. Since we know the game works on all your pieces of hardware as components of other peoples computers, and the games run fine on those computers, we know it’s not the game itself. To conclusively get further though, we need to know what OS you’re running, RAM serial # since you did not list it, Power supply model# and rough age, Ram test reports, what errors you’re getting when you crash, and if you’ve had to change any data, power, or processor related settings maybe for other games or as global settings, as well as your .net version and windows iteration.
It is important to note that even though other games run smoothly, that does not AT ALL clear you of the possibility of hardware issues either. One of the biggest culprits d2 seems to suffer from is VDroop, which causes your PSU to not supply enough power to components fast enough when u have a PSU rated under a platinum(ish), likely because of the graphical demand of the game, versus possibly aging components, given you’re on a 2700x. Even though other games may be even more graphically intense, they’re coded in more modern / efficient languages/engines, which helps tremendously.
If you wanted to go the whole 9 yards with testing, you could run a prime95 test in concurrence with a passmark test to see if you truly do suffer from vdroop issues, but this is the most intense system test combination I can possibly think of, so monitor the buhgeezus out of ur Temps while doing it and disengage prime95 first if there’s even a remote suspicion of struggle. The truth would lie here though, which could occur only seconds after engaging prime95. If your system can handle these tests at the same time for roughly 30 minutes, the psu is solid as a rock. If you BSOD, you’re looking at component failure or lack of component power / waning power or other HW issues like possible MOBO failure.
Another setting d2r seems to disagree wildly with is power saving settings of just about any sort both within windows as well as your bios, which also goes hand in hand with the explanation of the vdroop issue.
The only thing we have now is that with your hardware knowingly working on the game, we can can reasonably and conclusively tell you it has very little if anything at all to do with the game itself. If you want further direct help from myself, you can find me at my discord. A link is retrievable by visiting my twitch (originalx9) and typing !discord, but I don’t have the link on hand right now because I’m on a road trip in a hotel on my phone typing this.
My gut however is saying that if crashes are consistently happening in all areas of the game at random times, it’s most likely power related, especially having proven time and time again myself that this game is notorious for causing vdroops, even in 2 of my 1300 watt gold rated psu’s.
This can sometimes be managable by lowering graphics settings, closing unnecessary background tasks, and removing all power savings settings in both your windows and bios settings. Essentially, killing any process that causes your computer to create more work for your power supply.
Consult with a professional before addressing your bios please.
And as a final comment, the game still does have crashes but they are very few and far between these days. Even if your system is 100%, you still may crash every so often. I usually go weeks without one though at this point. It’s come a very long way.
