Do this at your own risk!! Apparently there are two NON-OFFICIAL solutions:

1. Rename csagent.sys ( the file causing the BSOD ) 2. Rename c:\windows\System32\Drivers\Crowdstrike

Again, do this at your own risk. Both workaround have been reported as "working". I am Linux user so I cannot tell.

we will found a troubleshooting , we start in revovery mode and rename the path C:\windows\system32\drivers\Crowdstrike