I have a Hyper-V guest that has suddenly stopped working and will not boot. Error message is:

Log Name:      Microsoft-Windows-Hyper-V-Worker-Admin
Source:        Microsoft-Windows-Hyper-V-Worker
Date:          25/08/2015 16:05:53
Event ID:      18590
Task Category: None
Level:         Critical
Keywords:      
User:          NT VIRTUAL MACHINE\DEBE1FE4-84A3-4490-AA2C-B7D75FAFA5C2
Computer:      xxxx
Description:
'xxxx' has encountered a fatal error.  The guest operating system reported that it failed with the following error codes: ErrorCode0: 0x7B, ErrorCode1: 0x5A5A28D0, ErrorCode2: 0xC0000034, ErrorCode3: 0x0, ErrorCode4: 0x0.  If the problem persists, contact Product Support for the guest operating system.  (Virtual machine ID DEBE1FE4-84A3-4490-AA2C-B7D75FAFA5C2)
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-2ECB715570FE}" />
    <EventID>18590</EventID>
    <Version>0</Version>
    <Level>1</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2015-08-25T15:05:53.516856100Z" />
    <EventRecordID>386</EventRecordID>
    <Correlation />
    <Execution ProcessID="3836" ThreadID="3376" />
    <Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
    <Computer>srv-host-a</Computer>
    <Security UserID="S-1-5-83-1-3737001956-1150321827-3619105962-3265638239" />
  </System>
  <UserData>
    <VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
      <VmName>xxxx</VmName>
      <VmId>DEBE1FE4-84A3-4490-AA2C-B7D75FAFA5C2</VmId>
      <VmErrorCode0>0x7b</VmErrorCode0>
      <VmErrorCode1>0x5a5a28d0</VmErrorCode1>
      <VmErrorCode2>0xc0000034</VmErrorCode2>
      <VmErrorCode3>0x0</VmErrorCode3>
      <VmErrorCode4>0x0</VmErrorCode4>
    </VmlEventLog>
  </UserData>
</Event>

This guest has been running for over a year without any issues.

Anyone seen this before?

Thanks

Mike

• Edited by Mike Gibson99 Tuesday, August 25, 2015 3:25 PM

Something must have changed.

The detail here: The guest operating system reported that it failed with the following error codes: ErrorCode0: 0x7B

indicates a Stop 7B error.  This is usually a boot device issue.  Where the OS of the machine is unable to detect the boot device.

It is most common when a machine is restored from back or converted from physical to virtual or hypervisor to hypervisor.

Boot to the repair console and repair the machine.

Hi Brian

Many thanks for your reply.

I have tried various repair options, which one(s) did you mean

Thanks

Mike

The error that is actionable is this:

'xxxx' has encountered a fatal error.  The guest operating system reported that it failed with the following error codes: ErrorCode0: 0x7B,

Did you try to boot the VM to the recovery console and try to repair the VM OS?

I can boot into the recovery console OK and get to a Command Prompt.

Mike

Hi Mike,

Please first check your Hyper-V storage health or the SAN storage connectivity, If all this work properly  base on my experience when this error occur I can reboot Hyper-V host then the issue will gone.

Another possible is the server power management configured incorrect, please try to disable any power save option then monitor the issue again.

More information:

Slow Performance on Windows Server 2008 R2 when using the Balanced Power Plan

https://support.microsoft.com/en-us/kb/2207548

VM shutdown actions don't run when a host shuts down because of a low battery

http://support.microsoft.com/kb/3058418/EN-US

Im glad to be of help to you!