none
Hyper-V-Worker event id 18590

    Question

  • Would like to know the cause and how to solve this issue. Vm rebooted unexpectably and this system should have high availability due to redundant hosts supporting microsoft failover cluster, no cluster events found only Hyper-V-Worker event id 18590 the minute the system rebooted.

    Have found no information relevant about this event and have not found either info on this particular vm error codes combination, our virtual machine is rebooting unexpectably with error 41

    "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

    nothing more.

    The host only reports the hyper v worker with following info:

    - System
    - Provider
    [
    Name]
    Microsoft-Windows-Hyper-V-Worker
    [
    Guid]
    {51DDFA29-D5C8-4803-BE4B-2ECB715570FE}
    EventID 18590
    Version 0
    Level 1
    Task 0
    Opcode 0
    Keywords 0x8000000000000000
    - TimeCreated
    [
    SystemTime]
    2018-05-15T20:08:35.506202300Z
    EventRecordID 161
    Correlation
    - Execution
    [
    ProcessID]
    5424
    [
    ThreadID]
    5692
    Channel Microsoft-Windows-Hyper-V-Worker-Admin
    Computer CHU-MTF-MD-TMS2.AUTOTMS.NET
    - Security
    [
    UserID]
    S-1-5-83-1-2261632595-1252162391-1381914804-3329928821
    - UserData
    - VmlEventLog
    VmName MODEL-SRV-TMS-VM
    VmId 86CDC653-7B57-4AA2-B458-5E5275AE7AC6
    VmErrorCode0 0x50
    VmErrorCode1 0xcc762000
    VmErrorCode2 0x1
    VmErrorCode3 0x36baf2d8
    VmErrorCode4 0x0

    Thursday, May 17, 2018 6:26 PM

All replies

  • Hi!

    Could you be kind and provide some more information regarding this issue?

    • How does your Hyper-V infrastructure look like? (cluster/standalone)
    • What version of Windows Server are you running on your Hyper-V hosts?
    • What version of Windows Server are you running on your VM which is crashing?

    Kind regards,
    Leon


    Blog: https://thesystemcenterblog.com  LinkedIn:   

    Thursday, May 17, 2018 7:03 PM