So from further investigation, experimentation, and research on the issue, it does seem that it may be a TDR error, as the dev above stated, but it is a TDR error that is caused by Diablo 2 Resurrected itself.
From further testing and research, D2R is NOT properly optimized, and specifically has a problem with Nvidia cards which causes them to overwork and overheat, which leads to the crashes. There are a number of possible solutions to this which I have minimally tested so far, but have gotten some potentially positive results for.
The solutions that I have seen are to go into the Nvidia control panel, and through the GPU itself, cap the FPS, and turn on Vsync. Another possible solution is to drop the resolution scale in D2R.
What seems to be happening is that whatever poor optimization was occurring with D2R was amplified with 2.4, thus necessitating the need for these solutions.
In last night’s minimal testing, I did have a few crashes initially upon adjusting my settings, but after toying around with the Nvidia settings and then the in game settings a bit, and a few crashes and restarts, I was able to get enough game time in to at least complete a Travincal run. Due to my schedule, I was only able to get about 15 minutes of gameplay in after getting it up and running before I had to turn the game off due to scheduling. I don’t know if this is a permanent fix, or if it was just a particular run that lasted a bit longer before crashing.
So while yes, the conclusion of a TDR error does seem to be correct, the TDR errors are caused by D2R itself and its poor optimization. Hence why there are 0 issues with any other games or programs.
This is an issue that needs to be addressed by Blizzard.