the driver in question was tested and passed WHQL. CrowdStrike included functionality in the driver to interpret a downloadable file (similar to an antivirus signature file). The file in the problematic update was malformed, and the CrowdStrike driver did not handle this case properly; Windows was unable to continue given the exception in question[1].
No operating system can guarantee that a driver will never cause the machine to crash. This wasn’t Microsoft’s fault.
https://blogs.windows.com/windowsexperience/2018/12/19/drive...