Share via

DC Server 2019 BSOD

Anonymous
2024-12-28T13:28:13+00:00

We have an active directory domain controller that crashed with a BSOD and still has not booted. The BSOD message states critical service failed. It is a 2019 Standard virtual machine running on Hyper V 2019 Standard as well. The Hypervisor itself is running great with no issues. I have tried all built in options such as DISM, chkdsk, sfc, safe mode, etc. None will boot it and it gets stuck in auto repair. I have access to the virtual drive as I have mounted it in another VM. No recent updates, no restore points, last know configuration did not fix, no new hardware. I ran the memory dump file through debugger but I didn't see any promising information. Any ideas on additional things to try?

Windows Server Performance and maintenance

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-12-30T18:09:19+00:00

    Hello

    Thank you for posting in Microsoft Community forum.

    Here are a few additional steps you can try:

    Check for Corrupt Active Directory Database: Sometimes, the NTDS.DIT file can become corrupt. You can try to repair it by booting into Directory Services Restore Mode (DSRM) and using the ntdsutil tool:

    • Restart the domain controller and press F8 to enter the boot menu.
    • Select Directory Services Restore Mode.
    • Log in with the DSRM password.
    • Open a command prompt and run ntdsutil.
    • Use the files command to check the integrity of the database and repair it if necessary.

    Verify Hyper-V Integration Services: Ensure that the Hyper-V Integration Services are up to date. Sometimes, outdated integration services can cause issues with virtual machines.

    Check for Driver Issues: Since the hypervisor is running fine, the issue might be with the VM's drivers. You can try updating or reinstalling the drivers from the mounted virtual drive.

    Restore from Backup: If you have a recent backup, restoring the VM from the backup might be the quickest way to resolve the issue.

    Rebuild the Domain Controller: If all else fails, you might need to consider rebuilding the domain controller. Since you have access to the virtual drive, you can back up the necessary data and configurations before proceeding with a rebuild.

    I hope one of these steps helps you get your domain controller back up and running.

    Best Regards,

    Wesley Li

    0 comments
  2. Anonymous
    2025-01-02T03:12:28+00:00

    Thanks for the reply. Unfortunately we did not have the DSRM login password from when it was first set up. The employees who set it up are no longer here and did not document the password.

    Hyper V is up to date, we do monthly updates on those servers.

    The drivers are basic vanilla drivers for the VM, nothing special at all in there. Works on all other servers.

    We were hoping for the VM backup but it required the DSRM password unfortunately.

    We have essentially rebuilt the domain controller in a new VM. We were hoping to at least get the old drive to boot to get some info such as group policy, etc off of it. We have found some ways to get them but it is very complex. I had hopes someone could look at the dump file and maybe give me an idea of what may be going on.

    0 comments