When I click Play from the Battle.net app, a window frame enclosing a black rectangle appears for about 3 seconds. Then, this window disappears and a dialog appears saying “The application encountered an unexpected error.”. It asks me to send a report with a random ReportID to Blizzard.
I have tried all the usual steps the Game Masters suggested (e.g. update video drivers, verify or reinstall game files, etc.). I tried disabling my Display Adapter (GPU) but the result was the same. I should be above min spec (Windows 10 Pro 19045.5737) with 128 GB RAM, AMD Ryzen 9 5950X, and RTX 3090 Ti 24 GB.
blz-log.txt is empty
The Windows event viewer shows nothing in particular.
The data captured by DebugView is limited:
[32092] tact root directory: c:/Program Files (x86)/Diablo II Resurrected/
[23584] tact root directory: c:/Program Files (x86)/Diablo II Resurrected/
[10616] MSAFD: Pending APCs in cleanup! Waiting…
[10616] MSAFD: (cleanup) … No APCs fired, keeping DLL ref count
[10884] Blizzard Error Report ID: 6254BC1A-2FEB-4762-B079-3B9FDAC628D6
[3332] tact root directory: c:/Program Files (x86)/Diablo II Resurrected/
Any ideas?
yeah i’ve got one…
Is it possible that by any chance You’ve disabled the pagefile/swapfile on all drives?
this error usualy crawls up if the game has not enaugh memory… this can happen with 128GB as well ( if for example you overdid with visual effects quality settings last time you played). the game isn’t optimized very well and ultra visual quality settings not only take up astronomus amounts of memory ( waaaay more than they should) but in some rare cases overdoing with visual effects can also lead the game to crash, for example the infamous shenk’s demise does CTD on high visual settings, and it is both an engine limitation and reckless visual 3D effect programing by Vicarious Visions, they simply overdid with the simultaneius collisions… one guy said the engine can handle 200 collisions simultaneously and shenk’s death on high generates 500, and so the engine literally gives up and goes CTD…
the default minimum of 8GB of RAM is just an assumption by blizz without turning on the swapfile the game crashes on me as well… I’ve checked the /framerate command ingame, and it would seem that the game uses all the virtual memory i have at my disposal ~24GB that’s 8GB of ram and 2x8GB of Pagefile on two separate drives…
so either you’ve set your graphics settings too high or the game’s engine is not capable of handling such high amount of memory, try to do some testing…
last two things i’d recommend is checking if you’ve set the RTX card as the prefered GPU for the D2R.exe ( high efficiency in graphic settings), or if you have the latest VC++ libraries installed plus latest NetFramework installed…