Navigation section

Windows 10 Did reboot by it self, can't find the reason.

C

Calby

Active Member
Joined
Mar 27, 2017
Messages
99
Hi,
Today when I did wake up I did hear my HPe Microserver gen8 reboot by it self, the machine have never done this before.
It currently running Windows Server 2016 Standard but as it's "almoste" the same as Windows 10 I do post here.

I have looked in %SystemRoot%\ after some dump file but I could not find any files.

When I'm looking in Event Viewer all I can find is:
Code: 
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

And before that I can't find anything until 06:07 and the computer did reboot at 08:10.


How can I find out what did happen?
I have only installed one 3rd party and that was last night, then I did install something calles CrashPlan backup software in Java, but I have uninstalled it now to see if it helps.
 


Solution
Neemobeer
If it's doing a clean reboot (not a power lost or BSOD) you can determine what initiated the reboot as follows.
  • Open Event Viewer
  • Go to the System log
  • Select Filter Current Log...
  • Under 'Event Source' select User32
  • Event ID 1074 is a shut down/restart and 1073 is a failed shutdown or restart

Having a chance to read the rest of the posts. It does sound like you had a brief power outage.
Sort by date Sort by votes
Hi,
if you think it was a bsod then change your settings so that a dump file is produced on blue screen:

Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go.

Sometimes a 'dxdiag' will show recent crashes and the bugcheck number (if there was one) please run a dxdiag and post the results.
 


Upvote 0 Downvote
kemical said:
Hi,
if you think it was a bsod then change your settings so that a dump file is produced on blue screen:

Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go.

Sometimes a 'dxdiag' will show recent crashes and the bugcheck number (if there was one) please run a dxdiag and post the results.
Click to expand...

I did have *.dmp on and also I had check automatic restart, I don't know if it was a BSOD or not, I don't think so or I don't know is the right answere as I can't find anything.
It don't show any bugcode either.

Anyway what I have done is that I did restore it from my backup to yesterday at 06:00 I know that I did not have this issue then or I don't know but during the day yesterday the server did work a lot and no issues was presented.

Let's hope that this works, I hate to uninstall the server :(
 


Upvote 0 Downvote
Well if no bug code is present then just watch for things like high temps and what not.

Hope all goes well.
 


Upvote 0 Downvote
kemical said:
Well if no bug code is present then just watch for things like high temps and what not.

Hope all goes well.
Click to expand...

Thanks, It's strange but according to iLO (like bios for HPe servers etc) it did not note the time for the reboot and that's strange, iLO is always running even when the server is "off", I have never seen that before.

Code: 
1922        08/16/2017 08:09    08/16/2017 08:09    1    On-board clock set; was 01/01/1970  00:03:01.
1921        [NOT SET]     [NOT SET]     1    iLO network link down.
1920        [NOT SET]     [NOT SET]     1    Server reset.
1919        [NOT SET]     [NOT SET]     1    APO: Last power state restored.
1918        [NOT SET]     [NOT SET]     2    Server power restored.
1917        [NOT SET]     [NOT SET]     1    Server reset.
1916        [NOT SET]     [NOT SET]     2    iLO network link up at 1000 Mbps.
1915        [NOT SET]     [NOT SET]     1    Power restored to iLO.


So my guess is that the hole machine did loose power, or am I way off now?
iLO did also reset the clock, and that's nothing that I have notice before.
 


Upvote 0 Downvote
To be honest this isn't really my area (as you can probably tell) although one of our Guru's ( @Neemobeer ) may well know the cause.
 


Upvote 0 Downvote
kemical said:
To be honest this isn't really my area (as you can probably tell) although one of our Guru's ( @Neemobeer ) may well know the cause.
Click to expand...

Ok I do understand, well I can't findout why it did happen, if I do understand iLO correctly it was a total powerloss as iLO did loose power also.
Let's hope that it's not happening again.
I have looked and the powercords are attached as far as I can tell, but if it happens again I maybe need to investigate it more to make sure that everything works.

I'm looking at my router also now in the logs, and it did restart I think, as it did restart my VPN also and some other services according to the log right?

Code: 
Aug 16 08:12:13 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Wed, 16 Aug 2017 06:12:12 GMT^M Server: Apache^M X-Powered-By: PHP/5.6.30^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Aug 16 08:12:13 ddns update: retval= 0, ddns_return_code (,200)
Aug 16 08:12:13 ddns update: asusddns_update: 0
Aug 16 08:12:13 ddns: ddns update ok
Aug 16 08:12:13 rc_service: ntp 854:notify_rc restart_upnp
Aug 16 08:12:13 rc_service: waitting "start_vpnserver1" via udhcpc ...
Aug 16 08:12:14 openvpn[883]: OpenVPN 2.3.2 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [eurephia] [MH] [IPv6] built on Jun  2 2017
Aug 16 08:12:14 openvpn[883]: PLUGIN_INIT: POST /usr/lib/openvpn-plugin-auth-pam.so '[/usr/lib/openvpn-plugin-auth-pam.so] [openvpn]' intercepted=PLUGIN_AUTH_USER_PASS_VERIFY
Aug 16 08:12:14 openvpn[883]: Diffie-Hellman initialized with 2048 bit key
Aug 16 08:12:14 openvpn[883]: Socket Buffers: R=[122880->131072] S=[122880->131072]
Aug 16 08:12:14 openvpn[883]: TUN/TAP device tun21 opened
Aug 16 08:12:14 openvpn[883]: TUN/TAP TX queue length set to 100
Aug 16 08:12:14 openvpn[883]: do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Aug 16 08:12:14 openvpn[883]: /sbin/ifconfig tun21 10.8.0.1 pointopoint 10.8.0.2 mtu 1500
Aug 16 08:12:14 openvpn[883]: /sbin/route add -net 10.8.0.0 netmask 255.255.255.0 gw 10.8.0.2
Aug 16 08:12:14 openvpn[892]: UDPv4 link local (bound): [undef]
Aug 16 08:12:14 openvpn[892]: UDPv4 link remote: [undef]
Aug 16 08:12:14 openvpn[892]: MULTI: multi_init called, r=256 v=256
Aug 16 08:12:14 openvpn[892]: IFCONFIG POOL: base=10.8.0.4 size=62, ipv6=0
Aug 16 08:12:14 openvpn[892]: Initialization Sequence Completed
Aug 16 08:12:15 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Aug 16 08:12:15 rc_service: ntp 854:notify_rc restart_diskmon
Aug 16 08:12:15 disk_monitor: Finish
Aug 16 08:12:17 disk monitor: be idle
Aug 16 08:12:17 kernel: sizeof forward param = 160
Aug 16 08:12:20 rc_service: udhcpc 797:notify_rc start_firewall
Aug 16 08:12:20 dhcp client: bound 94.254.23.230 via 94.254.23.1 during 100000 seconds.
Aug 16 08:12:21 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 16 08:13:00 crond[463]: time disparity of 1074609 minutes detected
Aug 16 09:00:17 disk_monitor: Got SIGALRM...

Yes, the router did also restart:
Uptime 0 days 2 hours 23 minute(s) 41 seconds


So, it's safe to say it was powerloos over the hole "power thing" not it's just to investigate that.
 


Upvote 0 Downvote
Perhaps it was 'just one of those things', time will tell I guess. Neemobeer hails from across the pond so might be sleeping right now. He'll be in later tho and he certainly know's his stuff.. :)
 


Upvote 0 Downvote
I'll check back later and see if he posted but if not i'll send him a pm.. Best of luck!
 


Upvote 0 Downvote
If it's doing a clean reboot (not a power lost or BSOD) you can determine what initiated the reboot as follows.
  • Open Event Viewer
  • Go to the System log
  • Select Filter Current Log...
  • Under 'Event Source' select User32
  • Event ID 1074 is a shut down/restart and 1073 is a failed shutdown or restart

Having a chance to read the rest of the posts. It does sound like you had a brief power outage.
 


Upvote 0 Downvote
Solution
Neemobeer said:
If it's doing a clean reboot (not a power lost or BSOD) you can determine what initiated the reboot as follows.
  • Open Event Viewer
  • Go to the System log
  • Select Filter Current Log...
  • Under 'Event Source' select User32
  • Event ID 1074 is a shut down/restart and 1073 is a failed shutdown or restart

Having a chance to read the rest of the posts. It does sound like you had a brief power outage.
Click to expand...

Ok, I have restored the server already as it's busniess critical that it runs.
But as the router also did reboot at the same time, my guess is that it was due to powerloss.
Don't know why, but maybe the cord or something I'll switch it out to a new one after business hour today.
 


Upvote 0 Downvote
That's good. The added benefit is that the UPS will protect the server from brown outs which can end up damaging hardware eventually.
 


Upvote 0 Downvote
You must log in or register to reply here.
Back
Top