Solved Windows 10 Reboots
-
@WrCombs said in Windows 10 Reboots:
Ran updates and restarted the PC, since then it's rebooted twice..
same issue..
Update all drivers from the PC manufacturer to their latest Win10 drivers. If they don't have Win10 drivers, downgrade to 8.1 or 7, or but a new PC.
-
@Obsolesce said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
Ran updates and restarted the PC, since then it's rebooted twice..
same issue..
Update all drivers from the PC manufacturer to their latest Win10 drivers. If they don't have Win10 drivers, downgrade to 8.1 or 7, or but a new PC.
Not my choice on buying a new Pc or downgrading.
-
@WrCombs said in Windows 10 Reboots:
@Obsolesce said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
Ran updates and restarted the PC, since then it's rebooted twice..
same issue..
Update all drivers from the PC manufacturer to their latest Win10 drivers. If they don't have Win10 drivers, downgrade to 8.1 or 7, or but a new PC.
Not my choice on buying a new Pc or downgrading.
So I take it there are no Win10 drivers installed then?
-
@Obsolesce said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
@Obsolesce said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
Ran updates and restarted the PC, since then it's rebooted twice..
same issue..
Update all drivers from the PC manufacturer to their latest Win10 drivers. If they don't have Win10 drivers, downgrade to 8.1 or 7, or but a new PC.
Not my choice on buying a new Pc or downgrading.
So I take it there are no Win10 drivers installed then?
Not that I'm seeing, all it says is the "best driver" is already installed.
-
That seems a bit of the top for a suggestion - not saying it's wrong, but I've never seen the requirement to get a new machine because Windows 10 was installed and something was causing it to reboot.
Personally - I'd wipe and reload it long before buying a new machine, but you're remote, so that's a harder decision.
Have you used the MS Fixit tool for Windows Update? that might do the trick.
-
@Dashrender said in Windows 10 Reboots:
That seems a bit of the top for a suggestion - not saying it's wrong, but I've never seen the requirement to get a new machine because Windows 10 was installed and something was causing it to reboot.
Personally - I'd wipe and reload it long before buying a new machine, but you're remote, so that's a harder decision.
Have you used the MS Fixit tool for Windows Update? that might do the trick.
what damage could it do?
I'll give it a shot. -
@WrCombs said in Windows 10 Reboots:
@Dashrender said in Windows 10 Reboots:
That seems a bit of the top for a suggestion - not saying it's wrong, but I've never seen the requirement to get a new machine because Windows 10 was installed and something was causing it to reboot.
Personally - I'd wipe and reload it long before buying a new machine, but you're remote, so that's a harder decision.
Have you used the MS Fixit tool for Windows Update? that might do the trick.
what damage could it do?
I'll give it a shot.The Fixit? none that I know of.
-
@Dashrender said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
@Dashrender said in Windows 10 Reboots:
That seems a bit of the top for a suggestion - not saying it's wrong, but I've never seen the requirement to get a new machine because Windows 10 was installed and something was causing it to reboot.
Personally - I'd wipe and reload it long before buying a new machine, but you're remote, so that's a harder decision.
Have you used the MS Fixit tool for Windows Update? that might do the trick.
what damage could it do?
I'll give it a shot.The Fixit? none that I know of.
I'll give it a shot and see if that fixes it then .
-
DISM and sfc /scannow are your friends. Just make sure that you launch the cmd window as administrator
-
@scotth said in Windows 10 Reboots:
DISM and sfc /scannow are your friends. Just make sure that you launch the cmd window as administrator
-
@Dashrender said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
@Dashrender said in Windows 10 Reboots:
That seems a bit of the top for a suggestion - not saying it's wrong, but I've never seen the requirement to get a new machine because Windows 10 was installed and something was causing it to reboot.
Personally - I'd wipe and reload it long before buying a new machine, but you're remote, so that's a harder decision.
Have you used the MS Fixit tool for Windows Update? that might do the trick.
what damage could it do?
I'll give it a shot.The Fixit? none that I know of.
did not find anything either.
-
@WrCombs said in Windows 10 Reboots:
@scotth said in Windows 10 Reboots:
DISM and sfc /scannow are your friends. Just make sure that you launch the cmd window as administrator
This is good. In addition to sfc, DISM will restore your local store of Windows files to put back in place in case of corruption / issues with the installation. One other thing to try is a chkdsk /f or /r if you want. These are just insurance moves if the logs don't reveal anything obvious.
-
Also from an administrative cmd prompt, you could run start /w cleanmgr.exe and get rid of stale update files, old installations, ... I usually keep dump and log files. It takes a while for a restart if you remove any update files because it rebuilds your updates database during restart.
-
@scotth said in Windows 10 Reboots:
Also from an administrative cmd prompt, you could run start /w cleanmgr.exe and get rid of stale update files, old installations, ... I usually keep dump and log files. It takes a while for a restart if you remove any update files because it rebuilds your updates database during restart.
that scares me.
LOL this is a live site right now.
This has been happening since the first of the year apparently.
First I heard about it was a week ago. -
@WrCombs said in Windows 10 Reboots:
@scotth said in Windows 10 Reboots:
Also from an administrative cmd prompt, you could run start /w cleanmgr.exe and get rid of stale update files, old installations, ... I usually keep dump and log files. It takes a while for a restart if you remove any update files because it rebuilds your updates database during restart.
that scares me.
LOL this is a live site right now.
This has been happening since the first of the year apparently.
First I heard about it was a week ago.Nothing like walking into a room full of angry women. Take someone with you to stop the hemorrhaging.
-
Could it be overheating and then going to various levels of power management / throttling to manage the thermal load?
-
@notverypunny said in Windows 10 Reboots:
Could it be overheating and then going to various levels of power management / throttling to manage the thermal load?
Only way to check that would be on site.. Correct?
-
@notverypunny said in Windows 10 Reboots:
Could it be overheating and then going to various levels of power management / throttling to manage the thermal load?
If this is counter in a restaurant, I'd bet good money that it's covered by bags or napkins or some kind of advertisement. Our POS systems use separate power bricks and the are constantly covered up and they cook nicely.
EDIT: This is one thing that actually results in a conversation with the person on site. It's a foolish expense.
-
@notverypunny said in Windows 10 Reboots:
Could it be overheating and then going to various levels of power management / throttling to manage the thermal load?
It's only rebooting after hours, and my boss just said " there's a program telling it to restart. and then restart again and then restart again."
-
@scotth said in Windows 10 Reboots:
@notverypunny said in Windows 10 Reboots:
Could it be overheating and then going to various levels of power management / throttling to manage the thermal load?
If this is counter in a restaurant, I'd bet good money that it's covered by bags or napkins or some kind of advertisement. Our POS systems use separate power bricks and the are constantly covered up and they cook nicely.
Lol I've seen this happen as well.
But this is the Server that's having the issues.
