Hyper-V Host Blue screens when I power on a VM

Hi,

I have a Windows 2016 standard server that I have installed Hyper-V on.

I have created a VM and before I can install Windows Server on the VM or if even just leave it to power on, the physical machine blue screens.

The Memory.dmp file give me the following info:

Microsoft (R) Windows Debugger Version 10.0.17763.1 X86

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 14393 MP (16 procs) Free x64

Product: LanManNt, suite: TerminalServer SingleUserTS

Built by: 14393.3383.amd64fre.rs1_release.191125-1816

Machine Name:

Kernel base = 0xfffff802`1f888000 PsLoadedModuleList = 0xfffff802`1fb8b020

Debug session time: Thu Feb 27 23:04:52.935 2020 (UTC + 0:00)

System Uptime: 0 days 0:10:45.421

Loading Kernel Symbols

...............................................................

................................................................

....................................

Loading User Symbols

PEB is paged out (Peb.Ldr = 0000000f`657bc018). Type ".hh dbgerr001" for details

Loading unloaded module list

.......

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {1, 1e00, fffff8021fc2d540, 0}

*************************************************************************

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: TickPeriods ***

*** ***

*************************************************************************

Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+42a )

Followup: MachineOwner

---------

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

or above.

Arguments:

Arg1: 0000000000000001, The system cumulatively spent an extended period of time at

DISPATCH_LEVEL or above. The offending component can usually be

identified with a stack trace.

Arg2: 0000000000001e00, The watchdog period.

Arg3: fffff8021fc2d540, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

additional information regarding the cumulative timeout

Arg4: 0000000000000000

Debugging Details:

------------------