• DigitalDilemma
    link
    fedilink
    English
    21
    edit-2
    11 months ago

    It seems to be crowdstrike reacting to the new update.

    We have got ours up by the very manual process of:

    1 Boot into safe mode.

    1. Navigate to C:\windows\system32\drivers\crowdstrike

    2. Delete C-00000291*.sys

    3. Reboot normally

      • DigitalDilemma
        link
        fedilink
        English
        211 months ago

        It has a privileged service running locally - csagent.sys - that was crashing causing the BSOD.

      • @lmaydev@lemmy.world
        link
        fedilink
        0
        edit-2
        11 months ago

        I guess if the code acted as if it got a valid response without checking it could get into a very weird state. Or the code just fails hard.

        At the driver level it’s very easy to kill things.