95
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Jul 2024
95 points (97.0% liked)
Technology
34415 readers
623 users here now
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
founded 5 years ago
MODERATORS
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.
Navigate to C:\windows\system32\drivers\crowdstrike
Delete C-00000291*.sys
Reboot normally
Yeah, CS posted this in a support article. Gonna be fun watching their share price on the Nasdaq overnight.
What's their ticker? I looked up BSOD but that's not it...
lol - it should be after this. CRWD...
You looked up Blue Screen of Death's stock price‽
I mean that's a fair assumption of what their ticker might've been
Maybe a stupid question but why would not reaching an online service (?) blue screen your computer?
It's the other way around. All those PCs are bluescreening at boot. So that prevents fixing the system remotely and on a large scale. Now poor IT guys have to fix evey single one by hand.
It has a privileged service running locally - csagent.sys - that was crashing causing the BSOD.
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.
Missing data in the boot sequence if that data is stored as a cloud init or a key is needed for auth during boot. So if you're running thin clients and rely on something like Ansible, but now the thin client can't get to the service it can't boot, so critical error.