How to fix frequent restart with BSOD on newly joined VM of hyper V, as additional domain controller?

kaleem 0 Reputation points
2023-05-13T06:59:09.55+00:00

I have added a fresh VM of windows server 2016 in hyper v, everything works fine. When i enroll this vm as additional domain controller in my forest having one parent and one child domain controller with forest functional level of 2008, it gives BSOD with non paged memory area error, and continuously restart after 14 minutes. when i disable network card, it works fine. another vm is also deployed on same base server with role of hosting, and working fine. i have same os version on all domain controllers,

Windows Server Management
Windows Server Management
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Management: The act or process of organizing, handling, directing or controlling something.
420 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Khaled El-Sayed Mohamed 1,140 Reputation points
    2023-06-18T08:42:34.43+00:00

    Hi Kaleem

    continuous restarts with a Blue Screen of Death (BSOD) error can indicate a serious problem with the operating system or the hardware configuration. In the case of your Windows Server 2016 VM, it seems to be encountering a "non paged memory area" error during the boot process. To troubleshoot and fix this issue, you can try the following steps:

    Check system requirements: Ensure that your hardware meets the minimum requirements for running Windows Server 2016. Verify that you have allocated sufficient resources (CPU, RAM, disk space) to the VM.

    Update Hyper-V Integration Services: Make sure that the Hyper-V Integration Services are up to date in your VM. To do this, go to the Hyper-V Manager, select the VM, and choose "Insert Integration Services Setup Disk" from the Action menu. Follow the on-screen instructions to install the latest integration services.

    Perform a clean boot: Boot the VM into Safe Mode or perform a clean boot to eliminate any conflicting third-party applications or services. If the VM boots successfully in Safe Mode, it indicates that a third-party component might be causing the issue.

    Update VM drivers: Update the drivers for the virtual hardware components of the VM, such as network adapters and storage controllers. You can obtain the latest drivers from the manufacturer's website or the Windows Update service.

    Disable unnecessary services: In some cases, certain services or features may conflict with the VM's configuration. Disable any unnecessary services or features that are not required for the VM to function as an additional domain controller.

    Check for hardware issues: If the problem persists, it's possible that there may be an issue with the underlying hardware. Ensure that the host machine's hardware, including CPU, memory, and storage, is functioning properly.

    Review event logs: Check the event logs on both the VM and the host machine for any relevant error messages or warnings that could provide further insight into the cause of the continuous restarts.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    0 comments