kbin_space_program

  • 0 Posts
  • 336 Comments
Joined 10 months ago
cake
Cake day: February 23rd, 2024

help-circle


















  • Please go read up on how this error happened.

    This is not a backwards compatibility thing, or on Microsoft at all, despite the flaws you accurately point out. For that matter the entire architecture of modern PCs is a weird hodgepodge of new systems tacked onto older ones.

    1. Crowdstrike’s signed driver was set to load at boot, edit: by Crowdstrike.
    2. Crowdstrike’s signed driver was running unsigned code at the kernel level and it crashed. It crashed because the code was trying to read a pointer from the corrupt file data, and it had no protection at all against a bad file.

    Just to reiterate: It loaded up a file and read from it at the kernel level without any checks that the file was valid.

    1. As it should, windows treats any crash at the kernel level as a critical issue. and bluescreens the system to protect it.

    The entire fix is to boot into safe mode and delete the corrupt update file crowdstrike sent.