Windows 10: Your windows insider build ran into a problem - Green screen

i was trying to install an app then this thing appear and restarts my computer

:)

 

Windows Insider Build ran into a problem: whats failed: WdFilter.sys

I got a Green Screen of Death...Please help with step by step instruction-

It started while I was on the internet. It won't go into anything but safe mode-and that's with a lot of patience.

Windows Insider Build ran into a problem and needs to restart. We're just collecting some error info, and then we'll restart for you.

Stop Code: SYSTEM SERVICE EXCEPTION

whats failed: WdFilter.sys

When I go to the windows insider in the settings it gives me the error code 0x80072ee2

My computer is a

HP Intel (R) Pentiu (R)

CPU G2020T

@2.50 GHZ

2.49GHZ

Ram 4.0

64 bits

windows 10 pro Insider preview

version: 1709

Installed on 1/21/18

OS build 17074.1002

 

windows insider build ran into a problem

Windows 10 pro Version 1809

OS Build 17763.402

My surface pro 4 was all good until today when I was trying to wake it up the green screen poped up with error message "your windows insider build ran into a problem and needs to restart," stop code of which is SYSTEM_SERVICE_EXCEPTION. After collecting
the error info surface restarted and ended up the same green screen. Funny thing is since I have two user accounts, I am able to open another account without a problem but not my main account.

I can enter safe mode but I wonder do I have to reset my surface or re-install windows to solve this problem? I have many apps and files and don't want to lose them all. Is there any other option I can try?

Thanks in advance!

 

green screen on insider preview build 18362.30

after this update i am getting error when ever i try to shut down or put my system to sleep

the error says that your insider build ran into a problem and needs to restart we are collecting info & at the very end it says what failed :ndis.sys

this green screen stays right there unless i press the power button.

please any one having fix for this ? help !