Yes, it is a desired feature to bugcheck when flagrant violations of the kernel rules are detected. CrowdStrike isn't special because it's security software, b

Yes, it is a desired feature to bugcheck when flagrant violations of the kernel rules are detected. CrowdStrike isn't special because it's security software, but there are good reasons you might not want to have the OS start disabling drivers randomly when the system isn't in a stable state. One reason is partly because, depending on what happened when, you might disable the wrong driver. It so happens in this case that CrowdStrike's hand was caught in the cookie jar immediately because it did something blindingly obvious to the kernel core as wrong, but there are scenarios where heap or other memory corruption happens in your CD player driver and 5 minutes later when you start using the network, it crashes because the network driver was executing off in la la land. In addition, sometimes it's just hardware failure that is a proximate cause, rather than a bad driver (I've seen bugchecks attributed to NTFS.sys that were ultimately the result of a dying hard disk).