Forum Discussion
BSOD on Server 2016 hal.dll (WATCHDOG_VIOLATION)
Host or guest BSOD? Hopefully the Hyper-V role is only role on host and active directory domain services are on a separate VM windows instance.
Dave Patrick Host BSOD unfortunately. And nope, all the roles are installed on the host itself. It is not something done by me or my colleagues, and its not within our power to change. The host is powerful enough to virtualise the roles, but the client is reluctant to do so.
So the system is more or less contaminated with (at least) the following:
- AD/DNS/DHCP/IIS/NAP roles installed
- Symantec antivirus manager (not just the client)
Which makes it all the harder to really guarantee a stable system, even if we end up finding what causes this. The host has not crashed yet since we last ran some basic repair commands, but we'll keep an eye on it ..
I'd work to move the roles (other than Hyper-V) off the host by standing up the required guests. You can do this rather easily. I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting. Then stand up the new guest, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.
To the bsod issues. I'd check here and with manufacturer about support for Server 2019
https://www.windowsservercatalog.com/
Also check with manufacturer for the latest ROM bios, firmware, chipset and driver support pack.
