3 ms·
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\D
by h4kunamata 2y ago
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.