Windows 10: Server Restarting Several Times per day.

I have a Windows Server 2016 that is restarting a couple of times per day. Critical Event Viewer Page below.


Any insight would be apprecaited.


-<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>4</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2019-05-16T01:55:16.522428300Z" />
<EventRecordID>247900</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>EOTB-SERVER</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">292</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0xffffd905956f0028</Data>
<Data Name="BugcheckParameter3">0xb6000000</Data>
<Data Name="BugcheckParameter4">0x100153</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
</EventData>
</Event>

:)

 

Windows Updated(16299.309).KB4088776 Restart is required to complete.


Hi dalchina. Good news, I followed your suggestion and reinstalled the update and now it appears as "installed correctly" *Biggrin Maybe it was not necessary to run the Windows Update Troubleshooter or maybe if necessary. But using it I do not think it could have worsened something. The installation was very fast, unlike the first time it showed step 1 and step 2 completed.

Thanks for the suggestions and for the time to respond Best regards.


And thanks for the tip of that program, I'll have it on my list.

 

TPU Minecraft Server

Done. Thanks for the suggestion!*Toast :toast:

 

Problem with synching to time server


When looking through the list of events in Windows Event Viewer, I have, for a long while now, been getting, every day, several warnings that look like this:-

Event 134, Time service
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time-new.nist.gov'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9).

The most recent of these was today at 15:28. When I look at the internet time settings (via control panel), it says the clock was successfully synchronised with time.nst.gov on 22/10/2018 (today) at 16:19 (a few minutes ago). The list of time servers is as follows:-

time.windows.com
time.nist.gov
time.nw.nist.gov
time-a.nist.gov
time-b.nist.gov

My questions is this: Why is the NTP client apparently trying to synchronise using a server that isn’t in the list? Where is it getting the server name 'time-new.nist.gov' from? It’s not in the list - only ‘time.nw.nist.gov’.
If I set the time server to time.windows.com should it cure the problem?