Seriously, Win10, What's with the restart?
-
I was using my laptop then took a break for lunch. Came back and it had restarted. I checked Windows Updates and it said there was one installed successfully on 02/13. Why did my computer suddenly restart? I looked in Event Log (System):
event log:
The previous system shutdown at 12:19:13 PM on 2/17/2018 was unexpected.
Next I find this:
Event log:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. (Source is Kernel-Power)
It's a laptop so has battery backup, so probably not a loss of power. Here's another weird one (not sure what bugcheck is):
Quote:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffd4095cacd830, 0xffffee8039c5ac40, 0xffffd40965c8ebd0). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 8d730435-e93f-4b3c-8ffa-bfafe4115fec.
Right before the restart I see:
Event Log:
The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x491f7fffff, got 0x1fffffff. Low Energy peripheral role functionality will not be available.
Maybe it went low power, then the device didn't support it so the system crashed? I don't know. :~ EDIT I did find one in the Event Log (Application) that occurred right before the reboot time:
Application Event Log:
SettingSyncHost (11192,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.
EDIT Apparently that is a BETA Win 10 1709 feature. :| I found this which mentions this problem does cause CRASHES! EseDiskFlushConsistency - win10 1709[^] X| EDIT 2 I'm wondering if this was the same restart problem
A reboot just bit me too. I had a dozen+ tabs open in two browsers researching something, 2 instances of VS. I was in the other room eating dinner when I hear the BIOS beep from my computer. Thanks a lot Windows Update KB4074588. That was absolutely not planned or communicated. The process c:\windows\system32\svchost.exe (MYNAMEHERE) has initiated the restart of computer MYNAMEHERE on behalf of user NT AUTHORITY\SYSTEM for the following reason: Operating System: Service pack (Planned) Reason Code: 0x80020010 Shutdown Type: restart Comment:
-
If you had gone one more entry in the log, you'd see this: "Windows 10 was detected. The system is inherently unstable."
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Strangely enough, I have been running Windows 10 for a year here at work and on three different machines at home, and haven't experienced a single crash on any of those. About half of the 300 PCs we have at work run W10 (the rest runs W7), and I haven't heard about any instability problems with any of those, in spite of lots of special hardware drivers, updated all the time, and a large number of tools deeply intertwingled with the OS, such as a multitude of debuggers and hardware monitors. But then: These systems are maintained by people who know how to handle Windows systems. They do not try to force the systems to be as Linux lookalikes as possible - that is bound to cause trouble. Just like if you try to manage a Linux box as if it were a Windows machins: Then it turns out that Linux is not quite as stable as rumours seem to suggest... One morning a few weeks ago, a few dozen of our machines at work had restarted at the same time in the middle of the night, while the majority of the machines were unaffected. The restart affected both W10 and W7 machines. We never found a good explanation, and concluded that since it is winter time, with lots of snow breaking down trees that fall over the power lines, the power grid sometimes can't perfectly suppress the spikes caused when switching over to another distribution line, and we experience a small spike in the power outlets. Some PC power supplies handle this well, others are knocked out and cause a restart when stable power is again available. We didn't investigate this further; most of our machines "survived". A couple of nightly builds had to be rerun, but going deeper into it would not be cost effective.
