Windows 10: Windows 10 GSOD before windows 10 updates

Hello,

I have two pc's on build 17074, both of them started to get GSOD's on the same day, I saw that the crash happened just before windows got ready to update to build 17115. In settings, I would see the build preparing to install and then change to pending restart. If I chose to "restart and update" it would crash immediately and if I chose to do nothing it would crash in 3 minutes max.

The next day I successfully managed to update my main pc that was on 17074 to 17115 ( I had the option to restart and update instantly on launch so I pressed it and it worked).

Now my second pc is a university laptop with no GPU (I first thought it might have been an nvidia driver issue, since I did a full reinstall in safe mode on my main pc to fix this GSOD). My laptop just won't start the update process. If I try to press the update button on the start menu it will crash, and If I do nothing it will crash after 15 minutes .

If I can manage to update my pc then my problems will be solved. Strange thing is, that my main pc which I managed to update is running a really broken windows 10 install ( I updated from windows xp to windows 7 and then to windows 10, so its a really old install, it usually has many issues etc...) and my laptop, which is running a relatively clean install and it never has windows related issues.

So.. a brief rundown:

Main PC [Old install, usually quite unstable] ( broken 17074 --> safe mode (uninstalled nvidia drivers) --> tried to quickly update --> now on build 17115)
Laptop PC [Relatively clean] (broken 17074 --> tried quick install (failed 8 times or so, always GSOD ) -->safe mode ( to collect logs) --> still broken)

I took some logs with the beta and non-beta versions of the log collectors.

BETA log collector: ERNESTAS-LPC (2018-03-18 19 54).zip
Non- Beta Log collector: ERNESTAS-LPC-2018_03_18_195346,70.zip

:)

 

Windows 10 Unexpected shutdown on start up

OK, so i figured it out myself

Found the logfile in "C:\Windows\Minidump".

You need the Windows Development Kit to open it and a bit of googling to understand it.

Found out that a Daemon driver caused an error. Removed Daemon but this didn't solve it. (ps: Daemon itself worked normally).

I let hibernate my computer again and found another error with sptd2.sys: SCSI Pass Through Direct layer

More google and ended up on the duplexsecure site. Downloaded the W10 version and voila: problem fixed.

For the Windows support team: It would be really helpfull if you could pass problems to a more skilled helpdesk who can do more than proposing the standard solutions in case those won't work.

Cheers

 

Windows 10 Unexpected shutdown on start up

OK, so I also found out that this occurs when sleepmode (for me after 3 hours) changes into hibernate mode.

Seems like the going into hibernate and/or starting up from HIbernate results in a shutdown. In safeboot it works perfectly.

Anyone any idea how I can figure out where it goes wrong. Is there a way to log this (I couldn't find it in bootlog)

 

Same problem as this guy: WdFilter.sys failure results in repeated Green Screen of Death - Microsoft Community

 

As the insider builds are changing so rapidly I would recommend you work directly with Microsoft on this one, maybe you can just download the 17115 or newer 17123 insider version and install that.

 

I has a bad feeling that no one could help since I am on an insider build... oh well...

So I took a risk - since the GSOD always had "WdFilter.sys" listed as the cause and that was preventing me from doing a clean install , I just deleted it from system32/drivers. The risk paid off since I was able to get into windows long enough to trigger the update! (I did not want to risk it, so I do not know if that is a permanent fix) , since the file belonged to windows defender it was broke *Smile .

So now I updated to 17115 and instantly got the option to go to 17120, so I did. Now everything is working and all is well. I believe that many people are having this issue ( it can't be random luck that two pc's got the same issue on the same day).

While it may have worked for me, I do not recommend trying this. If you have nothing else to do then you can give it a shot, though I'd recommend doing an update to a new build soon after since it "clean" installs windows again.

Will mark this as solved in a couple of days since I want to be sure this issue is fixed.