We have seen this error trying to start a VM Win 10 PC on server 2016 STD:
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 28/03/2020 14:52:11
Event ID: 18560
Task Category: None
Level: Critical
Keywords:
User: NT VIRTUAL MACHINE\A9733105-1A70-4555-89G2-B9BE81F6Z7B1
Computer: hvserver.domain.local
Description:
'PC' 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 A9733105-1A70-4555-81C2-B9D781F6C7B1)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51ddfa29-d5c8-4803-be4b-2ec987915570fe}" />
<EventID>18560</EventID>
<Version>0</Version>
<Level>1</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2020-03-28T14:52:11.337506100Z" />
<EventRecordID>224</EventRecordID>
<Correlation ActivityID="{ce847bea-0366-000c-7b94-84ce6603d601}" />
<Execution ProcessID="7824" ThreadID="3112" />
<Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
<Computer>VM3.domain.local</Computer>
<Security UserID="S-1-5-83-1-2842898693-1163205232-3619275393-2876872001" />
</System>
<UserData>
<VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>PC</VmName>
<VmId>A9733105-1A70-4555-81C2-B9D781F6C7B1</VmId>
<Rax>0x504d445453455547</Rax>
<Rbx>0x0</Rbx>
<Rcx>0x0</Rcx>
<Rdx>0x0</Rdx>
<Rsp>0xf7a9c5c8</Rsp>
<Rbp>0xf7a9c630</Rbp>
<Rsi>0xf7a9c810</Rsi>
<Rdi>0xf7a9c768</Rdi>
<R8>0x0</R8>
<R9>0x0</R9>
<R10>0x0</R10>
<R11>0xf7a9c5b0</R11>
<R12>0x1</R12>
<R13>0x0</R13>
<R14>0xf7afdd18</R14>
<R15>0x1</R15>
<Rip>0x4602334</Rip>
<Rflags>0x10046</Rflags>
<FpControlStatus>7F030000000000000000000000000000</FpControlStatus>
<XmmControlStatus>0000000000000000801F0000FFFF0000</XmmControlStatus>
<Cr0>0x80010033</Cr0>
<Cr2>0x0</Cr2>
<Cr3>0x4201000</Cr3>
<Cr4>0x668</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>0000000000000000FFFFFFFF28009BA0</Cs>
<Ss>0000000000000000FFFFFFFF080093C0</Ss>
<Ds>0000000000000000FFFFFFFF080093C0</Ds>
<Fs>0000000000000000FFFFFFFF080093C0</Fs>
<Gs>0000000000000000FFFFFFFF080093C0</Gs>
<Ldtr>0000000000000000FFFF000000008200</Ldtr>
<Tr>0000000000000000FFFF000000008B00</Tr>
<Idtr>00000000000000000000000000000000</Idtr>
<Gdtr>0000000000003F0018EFFEF700000000</Gdtr>
<Tsc>0x1bad03a4</Tsc>
<ApicBase>0xfee00900</ApicBase>
<SysenterCs>0x0</SysenterCs>
<SysenterEip>0x0</SysenterEip>
<SysenterEsp>0x0</SysenterEsp>
</VmlEventLog>
</UserData>
</Event>
What can we do? - it was working fine on the last host hyper-v machine.
Edited by user
a year ago
|
Reason: Not specified
