Not that all your statements wouldn't be false on their own anyway, but the fact that CrowdStrike actually had the very same issue a month ago on Linux systems, where their very same software (Falcon Sensor) caused the very same kind of kernel fault (which is called kernel panic under Linux, but it's the same thing as a BSOD) completely obliterates any claims that tries to push the blame on Microsoft, who in reality
1. was not a tiny bit responsible for this issue
2. couldn't have done anything better to prevent it
3. was the first to offer a remedy for its users, providing not only detailed instructions on how to recover, but also a bootable image that does the repair automatically.