That is was a Crowdstike issue not a Windows issue.

From my understanding, it's true that CrowdStrike wrote the faulty code and submitted it to Microsoft. Microsoft shares blame in that they didn't properly vet and test the kernel-level patch CrowdStrike had submitted.