212
To Fix CrowdStrike Blue Screen of Death Simply Reboot 15 Straight Times, Microsoft Says
(www.404media.co)
Dudes rebooting 14 times:
this post was submitted on 19 Jul 2024
212 points (97.3% liked)
News
23014 readers
10 users here now
Welcome to the News community!
Rules:
1. Be civil
Attack the argument, not the person. No racism/sexism/bigotry. Good faith argumentation only. This includes accusing another user of being a bot or paid actor. Trolling is uncivil and is grounds for removal and/or a community ban.
2. All posts should contain a source (url) that is as reliable and unbiased as possible and must only contain one link.
Obvious right or left wing sources will be removed at the mods discretion. We have an actively updated blocklist, which you can see here: https://lemmy.world/post/2246130 if you feel like any website is missing, contact the mods. Supporting links can be added in comments or posted seperately but not to the post body.
3. No bots, spam or self-promotion.
Only approved bots, which follow the guidelines for bots set by the instance, are allowed.
4. Post titles should be the same as the article used as source.
Posts which titles don’t match the source won’t be removed, but the autoMod will notify you, and if your title misrepresents the original article, the post will be deleted. If the site changed their headline, the bot might still contact you, just ignore it, we won’t delete your post.
5. Only recent news is allowed.
Posts must be news from the most recent 30 days.
6. All posts must be news articles.
No opinion pieces, Listicles, editorials or celebrity gossip is allowed. All posts will be judged on a case-by-case basis.
7. No duplicate posts.
If a source you used was already posted by someone else, the autoMod will leave a message. Please remove your post if the autoMod is correct. If the post that matches your post is very old, we refer you to rule 5.
8. Misinformation is prohibited.
Misinformation / propaganda is strictly prohibited. Any comment or post containing or linking to misinformation will be removed. If you feel that your post has been removed in error, credible sources must be provided.
9. No link shorteners.
The auto mod will contact you if a link shortener is detected, please delete your post if they are right.
10. Don't copy entire article in your post body
For copyright reasons, you are not allowed to copy an entire article into your post body. This is an instance wide rule, that is strictly enforced in this community.
founded 1 year ago
MODERATORS
Can't read the rest of the article because paywall but apparently users have chimed in saying rebooting 15 times worked for them. Whether they were serious or not remains a question. I can also imagine it was a time-related thing and after 15 reboots enough time has passed for it to be fixed so the user thought 15 times was the magic number.
Regardless, it's been a shit show.
Paywall bypass- https://archive.is/fA4pK
Much appreciated. Now I have access to the quote:
“We have received feedback from customers that several reboots (as many as 15 have been reported) may be required, but overall feedback is that reboots are an effective troubleshooting step at this stage."
So fuck the headline, the real message is: yes, rebooting is an effective troubleshooting step at the moment.
I don't know the exact timing of that message in the timeline of the incident, so it could be early "please restart and see if issue persists" or late "something was updated, rebooting will probably help", I don't know.
ArsTechnica has a bit more detail. I'll quote the important bit below.
... try to reboot affected machines over and over, which gives affected machines multiple chances to try to grab CrowdStrike's non-broken update before the bad driver can cause the BSOD.
This seems like an interesting application of a "race condition". They are hoping that the update outraces the program starting up enough to crash...
My understanding is, it's just a matter of if the Crowdstrike updater service manages to connect to the internet long enough to download the patch before the core service takes a shit.
My team and I last night were lucky enough that our computers came back up after a single reboot following the BSOD. VPN and certain applications were wonky the rest of the night.
We had nearly 300 servers impacted, almost 100 still down. All planned maintenance for the weekend has been cancelled. Incidents like these make me very glad I climbed the IT ladder enough to not be in a support role anymore.
“Have you tried turning it off and on again 15 times?”
I gave up after 14! Silly me.
After time 14, updates. Begin again.
If you do it 15 times while holding down the B key Mew appears for you to catch too!
But only if you look under the mousepad.
I tried this but only found a lava cookie. Did they change this for Windows 11?
Hilariously, if Microsoft required WHQL certification for AV kernel drivers like they do for every other, this would have never happened. It would have been discovered in the first hour of testing easy.
Nope, done it probably 50 times. Fake news :)
You expect me to use my feet to count that high??
Reminds me of the good ol' days.