Windows 10: System restarts itself sometime after a shutdown

I have multiple PC's running W10 v1511. For some reason at least one of them and I suspect more than one will automatically restart after it has been shutdown. The restart does not occur immediately, in fact, it is several hours before the magic happens! The reason I know it's happening is the system will be in a sleep state when I check it in the morning after I know I shut it down the night before. The PC in question is the one that I have described in my system specs. I know all about the "Wake On" settings in the in the Intel network controller. I have them all turned off (unchecked) but that only effects the system when in sleep mode? Is there some other setting that could be causing the system to refuse to stay shutdown? Any idea on what the heck is going on would be appreciated.

:)

 

System restarts after sometime without user interaction.

Hi,

Thanks for the update and response.

I understand that you are still facing issues with the BSOD.

Follow the below methods and check if it helps.

I suggest you to remove all the external devices before you restart the computer.

Method 1: Try booting the system in Safe Mode and check the status of the issue.

Safe mode starts Windows with a minimal set of drivers and services. If a problem doesn't reappear when you start your PC in safe mode, you can eliminate the default settings and basic device drivers and services as possible
causes. Refer the link below for steps to boot in Safe Mode.

http://windows.microsoft.com/en-us/...ther-startup-settings-in-windows-10#v1h=tab01

Method 2: In Safe modeUse check disk command for any errors on hard disk


Warning: Microsoft does not recommend interrupting the CHKDSK process. Microsoft does not guarantee the integrity of the disk if the CHKDSK program is interrupted .For safety
you can back up your data before using the

check disk command.

Use the check disk commands as follows:

a. Press Windows Key + X, then choose Command prompt (Admin) from the context menu.

b. In search window type 'cmd' and ENTER. Right click and select 'Run as administrator'.

c. Type at the command prompt CHKDSK /P and press ENTER to scan the disk.

d. Then type CHKDSK C: /F /R and press ENTER to repair corrupt sectors, if there are any.

NOTE: The root drive has to be C: and the command may schedule a task at the system startup, if it does, then press Y to schedule a task and restart the computer to perform chkdsk.

Once chkdsk completes, boot to the desktop and then check.

Important: While performing chkdsk on the hard drive if any bad sectors are found on the hard drive when chkdsk tries to repair that sector if any data available on that might be lost.

Hope this information is helpful. Please do let us know if you need further assistance, we’ll be glad to assist you.

 

System restarts after sometime without user interaction.

I started the computer in safe mode , and computer ran with a BSOD .

now how am i going to find what's responsible for the BSOD while computer is idle?

 

Have you by any chance scheduled a task to run at a certain time of the day or week ?

 

I have not installed any tasks but there are several tasks installed by various software programs I use. This is really strange because I have one other machine with almost the same system specs and the software installed and it does not start itself from the shutdown state. Obviously, there is something different between the two systems.

I logged "on a piece of paper" that I shutdown the problem system at 3AM today! So we'll try to watch and see when it comes back to life on it's own. I'll also go check when the tasks were last run in the Task Scheduler.

 

Ok, it looks like the system reboots on it own exactly 24 hours after shutdown - at least that is what it did today! I can tell that since the system was in an S3 sleep state by the time I checked it but the Task Manager shows when all the startup tasks were last run. I'll verify that this is true tomorrow since I shut it down at a slightly different time this morning.

Like I said above, I have other systems with similar hardware and software (including startup tasks) and they do not startup on their own when shutdown. Hope the 24 hour detail sheds some light on what is going on with this system.

 

Another day and another W10 auto restart from the shutdown state exactly 24 hours from the time I manually shutdown it down! Somebody must have a clue on what the heck is going on with this one PC.

I can say without question that my problem system restarts itself from a shutdown state every 24 hours. It makes no difference what time I shut id down it down it restarts itself exactly 24 hours later. Someone must have some idea on what heck W10 v1511 is up to?! I suppose it's no big deal as far a energy consumption is concerned since the system uses ~0 watts when in the sleep state. But it ain't right and I'd sure like to get to the bottom of the issue. Help!!!

 

Not getting much help with this issue!

Just to add to my woes, I now have two machines that restart themselves EXACTLY 24 hours to the second after they have been SHUTDOWN. The problem has probably been on both systems all along I just never paid close attention to why they were in sleep mode - I just assumed I forgot to shut them down! Both systems are built on an ASRock Z97 Extreme6 MB and a 4790K processor running with default BIOS settings. Both systems have a relatively fresh install of W10 v1511. I have two other systems built on an ASRock Z77 Extreme4 MB with a 3770K processor and a 2600K processor. Neither of these two systems have the problem. All four systems have the same software installed! I can't believe I'm the only one in the world with this issue, minor though it may be?

 

Problem solved! Disabled the Intel Smart Connect Technology option in the BIOS and the Reboot issue goes away. Apparently the ASRock Extreme6 BIOS implementation of the Z97 chip is a little different than the Extreme4 Z77 implementation. The Default setting on both MB's was Enabled yet the Z77's (at least mine) don't have the Reboot "problem". The guys on the Malwarebytes Forum jumped all over me when I tried to blame that program. They directed me to the BIOS issue almost immediately!