You say all 3 blades are experiencing similar issues? Are they all Server 2019 installs - any differences between the installs apart from the fact one's a DC? The fact it's happening on all 3 blades is very odd (side note - that BigTwin is a nice looking machine!). What's common between them - storage, RAM, power?
I'd suggest trying driver verifier on one of the non-production machines and seeing if it's stable - if it starts BSODing or crashing more with driver verifier we might be able to narrow it down to a driver issue -
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista
For debugging weird issues like this that don't happen regularly, it might be worth giving Sysmon a try as it can be useful at capturing events that normally go unnoticed in Event Viewer:
Sysmon - Windows Sysinternals. It's a bit of a pain to set the config up correctly, but there's a very good reference here:
SwiftOnSecurity/sysmon-config. Sysmon is normally used for monitoring and diagnosing malware & security issues, but can be helpful at capturing what happens before stuff goes wrong.
Another useful tool would be to set up ProcDump to capture dump files of any processes that crash:
ProcDump - Windows Sysinternals. The command for that is
procdump -ma -i C:\dumps, which will save any process crash dumps into C:\dumps. This can be useful if there's some process that's crashing and bringing the server down (although that's unlikely from the symptoms)
. More info:
Community
I wonder if forcing a BSOD when the machine is hung would reveal anything?
Forcing a System Crash from the Keyboard - Windows drivers
Sorry I can't offer an answer, but hopefully I've come up with a few useful points!
-Stephen
