Windows 10 restarting at random times

Fuhrer,

Thanks for the information. dxgkrnl is LDDM Graphics Subsystem.

My System:

Processor AMD A8-6500 APU with Radeon(tm) HD Graphics, 3500 Mhz, 2 Core(s), 4 Logical Processor(s)

How do I go about updating the firmware?

Hmm... I think tom, you have to really have it checked. I had the same error with one of the computers I was working on. After I had it tested with a new graphics card, it didn't worked. But when I updated all the firmware (totally different from a driver) it worked just fine.

I'm not sure if the testing part would work for you, but what the others experience is pretty different than what you have. Thanks to Nuewerld though, I had an idea where to start.

Use your msinfo32 on the run box and look for the dxgkrnl says if its microsoft or not?

I appreciate your efforts, but you don't answer any of my questions. Also, do you feel Neuwerld also has a "Hardware" problem that responds exactly like my "Hardware" problem?

Obviously you don't think the info I provide is of much use. I sent you the build information and driver info, yet you again ask me to load the latest driver and OS build

Here is the link to the latest dump. 10:50   2/8/18

https://1drv.ms/f/s!AqRMMjsjigz\_k0o1tlZI7-3BNmdI

I have not heard back from Kenny. Is his group working on this problem in parallel to you? Is it time to escalate? 

My OS: Version 1709 Build 16299.214. (the latest)

My AMD Radeon HD8570D is currently 15.200.1062.1004 - 18.2.1 Feb7

This is not a hardware problem! These problems started on Dec 15, 2017 the day Windows was update to Version 1709. Along with the reboots, users are not being logged off/out (as previously reported), also since December 15, 2017. Is there a way to remove Version 1709?

• Does Microsoft take responsibility for OEM driver that MICROSOFT installed as part of an update?
• Is the dump pointing to the display adapter or some other driver?
• Am I updating the correct driver?
• Should the mini dump, you requested, been triggered?
• Has Trevor and/or others resolved this problem?

Thanks for your efforts, but looking at working hardware that coincidentally failed on the same day Microsoft updated the software is quite a stretch. Along with the log out problem of the same date.

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.

We understand your misgivings, Tom. That's why we also suggested to have the case isolated further (even if the dump file had shown the issue to be hardware) by suggesting that you do the manual update to the latest release for  Windows 10 Version 1709. This update came out on January 31, 2018 and you may get it from this link.

It would be good to install the latest drivers, as well as the latest OS update so we can be certain that our findings on the dump file information is accurate.

Do keep us posted with the result.

Regards.