Windows 10: BSOD every time Hyper-v machines are on, Windows 10 Pro v.1909

BSOD every time Hyper-v machines are turned on, Windows 10 Pro v.1909 crashes, can someone help, I cant find a reason for it and it started since previous windows version update and still persists in 1909.


Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Local kernel debugging is disabled by default. You must run "bcdedit -debug on" and reboot to enable it.Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 8 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff800`7f000000 PsLoadedModuleList = 0xfffff800`7f448190Debug session time: Thu Mar 5 09:35:44.892 2020 UTC + 0:00System Uptime: 0 days 17:52:45.435Loading Kernel Symbols..........................................................................................................................................................................................................Loading User SymbolsPEB address is NULL !Loading unloaded module list...........For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff800`7f1c1510 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800`80b00c70=00000000000001ca0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************SYNTHETIC_WATCHDOG_TIMEOUT 1caA system wide watchdog has expired. This indicates that the systemis hung and not processing timer ticks.Arguments:Arg1: 000000000fea3e7a, The time since the watchdog was last reset, in interrupt time.Arg2: 000000962648002e, The current interrupt time.Arg3: 00000096264b0f87, The current QPC timestamp.Arg4: 0000000000000003, The index of the clock processor.Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 6 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on STATIC Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 6 Key : Analysis.Memory.CommitPeak.Mb Value: 63 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: 1caBUGCHECK_P1: fea3e7aBUGCHECK_P2: 962648002eBUGCHECK_P3: 96264b0f87BUGCHECK_P4: 3BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: vmmemBAD_STACK_POINTER: fffff80080b00c68STACK_TEXT: fffff800`80b00c68 fffff800`7faeaa55 : 00000000`000001ca 00000000`0fea3e7a 00000096`2648002e 00000096`264b0f87 : nt!KeBugCheckExfffff800`80b00c70 fffff800`7fad4dec : 00000096`264b0f87 00000000`00000001 fffff800`7f354614 00000000`00000082 : hal!HalpWatchdogCheckPreResetNMI+0xd5fffff800`80b00cb0 fffff800`7f2a4ceb : 00000000`00000001 ffffee87`ca1aab50 fffff800`78fe2180 fffff800`7f2b5ff0 : hal!HalpPreprocessNmi+0x11e5cfffff800`80b00ce0 fffff800`7f1ccb42 : 00000000`00000000 fffff800`80b00ef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0xcbfffff800`80b00d30 fffff800`7f1cc914 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82fffff800`80b00e70 fffff800`7ba00003 : fffff800`7f1cb2e4 00000000`00000000 fffff800`7f1cb30a ffffee87`ca1aaa00 : nt!KiNmiInterrupt+0x214ffffee87`ca1aa950 fffff800`7f1cb2e4 : 00000000`00000000 fffff800`7f1cb30a ffffee87`ca1aaa00 00000000`00000002 : 0xfffff800`7ba00003ffffee87`ca1aa958 fffff800`7f1cb30a : ffffee87`ca1aaa00 00000000`00000002 fffff800`7f344a07 00000000`00000000 : nt!HvcallpExtendedFastHypercall+0x54ffffee87`ca1aa968 fffff800`7f344a07 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvcallpExtendedFastHypercallWithOutput+0x1affffee87`ca1aa980 fffff800`7c899d1a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvcallFastExtended+0x27ffffee87`ca1aa9c0 fffff800`7c89b635 : 00000000`00000002 ffff9688`14329e20 ffff9688`14329e20 00000000`00000000 : winhvr!WinHvpDispatchVp+0x92ffffee87`ca1aaa50 fffff800`7c89b0ec : ffffee87`ca1aaba0 ffffee87`ca1aaba0 00000000`00000004 00000000`00989680 : winhvr!WinHvpVpDispatchLoop+0x225ffffee87`ca1aab30 fffff800`7cb36823 : ffff9688`1dab02b0 00000000`00000001 00000000`00000005 ffff9688`1dab0400 : winhvr!WinHvRunVpDispatchLoop+0x4cffffee87`ca1aab70 fffff800`7cb3667d : 00000000`00000000 ffff9688`1dab0400 ffffee87`ca1aac00 00000000`00000005 : Vid!VidXSchedulerpVpRun+0x73ffffee87`ca1aaba0 fffff800`7f12a7b5 : ffff9688`1d0e9080 ffff9688`1d0e9080 fffff800`7cb36540 ffff9688`1dab02b0 : Vid!VidXSchedulerVpThreadStartRoutine+0x13dffffee87`ca1aac10 fffff800`7f1c8b5a : ffff8280`41d80180 ffff9688`1d0e9080 fffff800`7f12a760 8948e031`48003da1 : nt!PspSystemThreadStartup+0x55ffffee87`ca1aac60 00000000`00000000 : ffffee87`ca1ab000 ffffee87`ca1a5000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2aSYMBOL_NAME: winhvr!WinHvpDispatchVp+92MODULE_NAME: winhvrIMAGE_NAME: winhvr.sysSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 92FAILURE_BUCKET_ID: 0x1CA_STACKPTR_ERROR_winhvr!WinHvpDispatchVpOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {f8612d6c-5db0-509d-c4ff-cce0fea28dd1}

:)

 

Hyper-V Fails to Install on Windows 10 v.1909

A mystery to me too, I've been running Hyper-V on two W10 Pro machines, both on 1909 (build 18363.592).

You should do if Hyper-V has been installed successfully. For reference, these are the services I have....






There is also the Hyper-V Manager, which is the virtmgmt.msc snap-in for the MMC management console.

 

Hyper-V Fails to Install on Windows 10 v.1909

Like the title says, Hyper-V fails to install on Windows 10 v.1909. [OS build 18363.592] It's a mystery to me, because I successfully installed and used Hyper-V on earlier versions of Windows.

Yes, I've got the necessary hardware and BIOS support (I successfully installed and used Hyper-V on earlier versions of Windows) and there are no other hypervisors currently installed. I disabled my anti-malware software (the same brand that I was using when I previously installed Hyper-V) and added the feature from an Administrators user account.

This may be a clue: Event Viewer only has one entry made at the time I tried to install Hyper-V, but it makes no sense (to me.) It's a 7043 Service Control Manager event that says the Hyper-V Virtual Machine Manager did not close following a pre-shutdown command, but I don't even have Hyper-V Virtual Machine Manager listed as a service.

If it matters (doubt it) the install failed at 98% and, of course, Windows rolled back any changes.

I'm open to any suggestions as to what I can try to get Hyper-V to install. Thanks for your help.

 

Where is the Hyper V Manager, How to I start it ?

I am trying to setup an XP virtual Machine on Windows 10 Pro.

I followed the steps in Neil Peterson article of 5/9/2016.

System Requirements - done - ok

Install Hyper-V - done - ok

Create a Virtual Switch - skip

Create a Virtual Machine

Create a Virtual Machine with Hyper-V Manager

These steps walk through how to manually create a virtual machine and deploy an operating system to this virtual machine.

• 
  In Hyper-V Manager, click Action > New >
  Virtual Machine to bring up the New
  

Uhhhhhhhhh - this step obviously implies one knows

1) Where the Hyper-V Manager is

2) How to start the Hyper-V Manager

Isn't that odd ?