Windows 10 Hyper-V fail to start: Microsoft-Windows-Hyper-V-Worker/Admin Event 18560

Question

Created Several Virtual Machines on Windows Server 2019 ( Xeon E5-2670 ) with Hyper-V configuration version 5.0 (for Compatibility with Server 2012 R2).

Exporting and running on other machines hasn't been a problem, but recently I started testing on a couple of my Ryzen 3700x boxes, other virtual machines created with Hyper-V Configuration version 8.0 can launch just fine, but those with Configuration version 5.0 keep giving me Triple boot errors.

I would prefer to keep with configuration version 5.0, anyone know how to fix up exported images so they run on AMD class machines???

Tkanks!

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
 <System>
  <Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51ddfa29-d5c8-4803-be4b-2ecb715570fe}" /> 
  <EventID>18560</EventID> 
  <Version>0</Version> 
  <Level>1</Level> 
  <Task>0</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000000000000000</Keywords> 
  <TimeCreated SystemTime="2021-08-08TXXXXXXXXX" /> 
  <EventRecordID>6708</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="15088" ThreadID="3684" /> 
  <Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel> 
  <Computer>XXXXXXXXXXXX.com</Computer> 
  <Security UserID="S-1-5-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" /> 
 </System>
 <UserData>
  <VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
  <VmName>XXXXXXXXX</VmName> 
  <VmId>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</VmId> 
  <Rax>0x1fec0000083</Rax> 
  <Rbx>0x604fd8</Rbx> 
  <Rcx>0x5</Rcx> 
  <Rdx>0x800000</Rdx> 
  <Rsp>0x6284e0</Rsp> 
  <Rbp>0x628538</Rbp> 
  <Rsi>0x18</Rsi> 
  <Rdi>0x200</Rdi> 
  <R8>0x200</R8> 
  <R9>0x200</R9> 
  <R10>0x1fec0200000</R10> 
  <R11>0x62a028</R11> 
  <R12>0x801000</R12> 
  <R13>0x0</R13> 
  <R14>0x1</R14> 
  <R15>0x200</R15> 
  <Rip>0x3fff6e8a</Rip> 
  <Rflags>0x2</Rflags> 
  <FpControlStatus>7F030000000000000000000000000000</FpControlStatus> 
  <XmmControlStatus>0000000000000000801F0000FFFF0200</XmmControlStatus> 
  <Cr0>0x80000033</Cr0> 
  <Cr2>0x629d58</Cr2> 
  <Cr3>0x600000</Cr3> 
  <Cr4>0x660</Cr4> 
  <Cr8>0x0</Cr8> 
  <Xfem>0x1</Xfem> 
  <Dr0>0x0</Dr0> 
  <Dr1>0x0</Dr1> 
  <Dr2>0x0</Dr2> 
  <Dr3>0x0</Dr3> 
  <Dr6>0xffff0ff0</Dr6> 
  <Dr7>0x400</Dr7> 
  <Es>0000000000000000FFFFFFFF080093C0</Es> 
  <Cs>0000000000000000FFFFFFFF10009B20</Cs> 
  <Ss>0000000000000000FFFFFFFF080093C0</Ss> 
  <Ds>0000000000000000FFFFFFFF080093C0</Ds> 
  <Fs>0000000000000000FFFFFFFF080093C0</Fs> 
  <Gs>0000000000000000FFFFFFFF080093C0</Gs> 
  <Ldtr>0000000000000000FFFF000000008200</Ldtr> 
  <Tr>0000000000000000FFFF000000008B00</Tr> 
  <Idtr>000000000000DF02D89C620000000000</Idtr> 
  <Gdtr>00000000000017000060600000000000</Gdtr> 
  <Tsc>0x415c4a</Tsc> 
  <ApicBase>0xfee00900</ApicBase> 
  <SysenterCs>0x0</SysenterCs> 
  <SysenterEip>0x0</SysenterEip> 
  <SysenterEsp>0x0</SysenterEsp> 
  </VmlEventLog>
 </UserData>
</Event>

Answer 1

Yup, that did it.

I had set

Set-VMProcessor -VMName $VirtualMachineList -CompatibilityForMigrationEnabled $True

In my export script. But Processor Compatibility is really on used for live migrations, so the step was not necessary.

Thanks Trev!

Answer 2

Hi,

Is the Ryzen 7 3700X box also running Server 2019 (to my knowledge, it seems we can install win10 only, please correct me if I'm wrong)? For server 2019, configuration 5.0 is supported, while win10 not. We can use Get-VMHostSupportedVersion to check this.

For more details, we may refer:

https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/upgrade-virtual-machine-version-in-hyper-v-on-windows-or-windows-server

Alex
If the response is helpful, please click "Accept Answer" and upvote it.

Answer 3

OK I have some more information on this.

I've been creating some Hyper-V Virtual Machines on my Ryzen 3700x box (Windows 10 version 21H1), configuration version 8.0.

After working on the VM's for a day, I shut the VM's down, and two days later I can't start them up. Again I get the 18560 event ID:

"'HYD-DC1' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. If the problem persists, contact Product Support. (Virtual machine ID 41576D32-DCE5-4AE4-8866-8316EF2F9BC2)"

So the problem persists.

Answer 4

There is a lot to unpack here.

• Yes I am aware that you can re-attach the VHDx files to get them to work.
• I'm recreating VM's all the time. So re-attaching isn't practical.
• This happens consistently on my machine.
• I need a REAL solution.

How do I get support to fix this Hyper-V platform bug?

Answer 5

I faced the same issue on my Ryzen based host. Disabling 'Processor Compatibility' in the VM settings resolved it in my case.