none
Hyper-V-Worker event id 18590

    Pergunta

  • 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

    quinta-feira, 17 de maio de 2018 18:26

Todas as Respostas

  • 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:   

    quinta-feira, 17 de maio de 2018 19:03
  • Hi ,

    This problem similar to power off unexpected. It should no related logs was logs. May I know did we perform any actions when the problem happen?

    If this is cluster environment, we may try to analyze the cluster logs under the path C:\Windows\cluster\reports\cluster.log.

    Best Regards,
    Frank


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    terça-feira, 22 de maio de 2018 02:07
  • Hi,
    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

    Best Regards,

    Frank

    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    sexta-feira, 25 de maio de 2018 08:41
  • Hi,

    Was your issue resolved? 

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.
    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.
    If no, please reply and tell us the current situation in order to provide further help.


    Best Regards,
    Frank

    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    segunda-feira, 28 de maio de 2018 08:57
  • It appears the original question asker did not reply.. I have the same problem and I will provide the information for my issue

    infrastructure - standalone

    server version on hyper v host -server2012 r2

    server version on vm that is crashing - server2012 r2

    quarta-feira, 25 de julho de 2018 13:01