Hello,

Today I approved restart for my Windows 8.1 because of waiting updates to be finnished. Unfortunately I get BSOD (blue screen of death) after. During a day research I found that kb3025417 (March 2015 antimalware platform update for Windows Defender in Windows 8.1 and Windows 8) causes BSOD (blue screen of death) at windows startup. So windows just cycles BSODs at boot.

First I thought there is some problem with driver - there was update of bluetooth drivers in kb3029606 (Update to improve Bluetooth driver diagnosis in Windows 8.1), so I susspected there is some hardware incompatibility. But windows does not generated any dump file, what is strange because it complicated to find root cause so easy.

Fortunately there was restorepoint generated yesterday, so I was able to return Windows configuration from just day ago. Installing update by update I found that kb3025417 causes BSOD. Installing rest of updates from windows update rollout from March 10th 2015 was withouth problem. Just kb3025417 I may not install.

Google does not say anything about this problem. Is anybody here having same issue with this update?

Rgds

   Rado

• Edited by radoslavv Saturday, March 14, 2015 8:41 PM
• Changed type Brandon RecordsModerator Monday, March 23, 2015 4:10 PM Issue presented in original post.

Hi, I THINK I have same problem.

After updating in early March I got no reboot anymore. I have since then trying to fix problem, but without success.

This is my post here: 

https://social.technet.microsoft.com/Forums/windows/en-US/ff478da9-2f24-4a48-9811-b15789074872/windows-81-not-booting-boot-manager-failed-to-find-os-loader?forum=w8itprogeneral

I want to try to roll back, like you did. How did you do a "system restore" if you could not access windows? Could this be launched from command line? Also, was your latest Restore Point created automatically?

Thanks!

Hello Deason,

   I have decided to not to install another antivirus and antispyware software. So I am using Windows Defender only - it seems to be not very bad.

   Strange is there is no way to somehow detect where the problem is. It seems something wrong happens in kernel during Windows boot/startup that prevents dump file making (windows does not start so deep to be able to do this? even kernel dumps are enabled). So normally I do not have a way to find root cause - could you give advice on this?

   I think this KB changes something in boot files and there seems to be some torubles. I do not use any SW for HDD encryption or anything that starts before/during boot process (like non MS antivirus and antimalware SW). Therefore I think there may be something wrongly fixed/developed in this KB in MS.

Rgds

Rado