I have had the same issue since December 1st—random restarts while doing everyday tasks. No blue screen...the computer just acts as if I told it to restart.
This has happened infrequently enough for me not to worry about it (I looked into it, but there didn't seem to be any clear resolution), but my laptop randomly restarted for the second time today so I looked back into this issue and found
this thread.
I have had these random restarts happen on two different Windows 10 computers. Seven times since December 1st on a Lenovo desktop (my primary computer), and twice since December 2nd on an HP laptop (that I don't use very frequently).
Funny thing is that every random restart (Kernel-Power, Event ID 41) is immediately preceded (at the same second or one second prior) by "FileCrypt" and "npsvcrtrig" in the Event Viewer.
For example:
Information | 1/21/2018 1:37:13 PM | Microsoft-Windows-FilterManager | 6 | None | File System Filter 'FileCrypt' (10.0, 2013-05-08T04:49:03.000000000Z) has successfully loaded and registered with Filter Manager.
Information | 1/21/2018 1:37:13 PM | Microsoft-Windows-FilterManager | 6 | None | File System Filter 'npsvctrig' (10.0, 2070-05-05T06:38:28.000000000Z) has successfully loaded and registered with Filter Manager.
Critical | 1/21/2018 1:37:13 PM | Microsoft-Windows-Kernel-Power | 41 | -63 | The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
I saw that update 1709 has been mentioned here, so I looked to check the dates when I installed that update. The random crashes started on my desktop on December 1st, and on my laptop on December 2nd. I installed Windows 10 update 1709 on November 21st on
my desktop, and on December 2nd on my laptop. I also noted that I installed the November update (KB890830) for the Windows Malicious Software Removal Tool on December 1st on my desktop [not sure
when (or if) for my laptop since it doesn't show in the update history].
Someone in this thread seemed to resolve this issue by disabling fast startup, so I'm going to try that.