locked
Server Rebooted Unexpectly RRS feed

  • Question

  • Today morning my windows 2008 R2 server restarted unexpectly. At 4.45 am i got Event id 1126 and 1128 followed by Id 57 and ID6008. Could you help me to explain and resolve this issue.

    Saturday, October 21, 2017 5:15 AM

Answers

  • HI

    Based on you events, it seems that your hard drive got stuck. Ik could be a driver or a harddisk issue. i would recommend a check disc.

    Saturday, October 21, 2017 7:44 AM
  • Hi,

    Please proved detail information about the Events you had mentioned, except for Event ID, please provide appropriate log name, source and general message. 

    For Event ID 6008 "The previous system shutdown at Time on Date was unexpected." It may be due to:
    1. Hardware going bad
    2. Hardware firmware or driver is misbehaving
    3. Mini filter drivers (i.e. antivirus and other security software) is/are misbehaving

    If possible, please have a full disk/hardware scanning, contact the hardware provider/supporter, they may have tool which may help you to complete the health scanning. Besides, please manually update the firmware/BIOS/relate drivers and check the result. 

    If this problem happens frequently, you may try to disable 3rd party process, including anti-virus/protection software temporarily and check the result. 

    How to troubleshoot an Event ID 6008 "The previous system shutdown at Time on Date was unexpected.":
    https://blogs.technet.microsoft.com/yongrhee/2015/05/22/how-to-troubleshoot-an-event-id-6008-the-previous-system-shutdown-at-time-on-date-was-unexpected/

    Best Regards,
    Eve Wang

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

    Monday, October 23, 2017 7:02 AM

All replies

  • HI

    Based on you events, it seems that your hard drive got stuck. Ik could be a driver or a harddisk issue. i would recommend a check disc.

    Saturday, October 21, 2017 7:44 AM
  • Hi,

    Please proved detail information about the Events you had mentioned, except for Event ID, please provide appropriate log name, source and general message. 

    For Event ID 6008 "The previous system shutdown at Time on Date was unexpected." It may be due to:
    1. Hardware going bad
    2. Hardware firmware or driver is misbehaving
    3. Mini filter drivers (i.e. antivirus and other security software) is/are misbehaving

    If possible, please have a full disk/hardware scanning, contact the hardware provider/supporter, they may have tool which may help you to complete the health scanning. Besides, please manually update the firmware/BIOS/relate drivers and check the result. 

    If this problem happens frequently, you may try to disable 3rd party process, including anti-virus/protection software temporarily and check the result. 

    How to troubleshoot an Event ID 6008 "The previous system shutdown at Time on Date was unexpected.":
    https://blogs.technet.microsoft.com/yongrhee/2015/05/22/how-to-troubleshoot-an-event-id-6008-the-previous-system-shutdown-at-time-on-date-was-unexpected/

    Best Regards,
    Eve Wang

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

    Monday, October 23, 2017 7:02 AM
  • Hi,

    How things are going there on this issue?

    Please let me know if you would like further assistance.

    Best Regards,
    Eve Wang

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

    Thursday, October 26, 2017 2:51 AM
  • Hi,

    Is there any update?

    Please click “Mark as answer” if the reply is helpful. It would make this reply to the top and easier to be found for other people who has the similar problem.

    Best Regards,
    Eve Wang

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

    Monday, October 30, 2017 5:47 AM