this post was submitted on 19 Jul 2024
181 points (95.9% liked)

Not The Onion

12200 readers
836 users here now

Welcome

We're not The Onion! Not affiliated with them in any way! Not operated by them in any way! All the news here is real!

The Rules

Posts must be:

  1. Links to news stories from...
  2. ...credible sources, with...
  3. ...their original headlines, that...
  4. ...would make people who see the headline think, “That has got to be a story from The Onion, America’s Finest News Source.”

Comments must abide by the server rules for Lemmy.world and generally abstain from trollish, bigoted, or otherwise disruptive behavior that makes this community less fun for everyone.

And that’s basically it!

founded 1 year ago
MODERATORS
kescusay@lemmy.world
181
To Fix CrowdStrike Blue Screen of Death Simply Reboot 15 Straight Times, Microsoft Says (www.404media.co)
submitted 3 months ago by Viking_Hippie@lemmy.world to c/nottheonion@lemmy.world
14 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.sdf.org/post/19765669

you are viewing a single comment's thread
view the rest of the comments
[–] vikingtons@lemmy.world 13 points 3 months ago (3 children)

Is anyone able to read the full article? Is this a boot loop OS detection feature?

[–] PineRune@lemmy.world 22 points 3 months ago (2 children)

I saw in another thread: sometimes upon booting, the updater has just enough time to grab the fixed update before BSOD so keep trying.

I saw some SysAdmin threads as it was happening say to boot into safe mode, navigate to the affected file, and delete it.

[–] MajorHavoc@programming.dev 13 points 3 months ago (1 children)

boot into safe mode, navigate to the affected file, and delete it.

Yeah. That's the easiest, unless the drive is encrypted.

I imagine the folks going for the 15 reboots approach are doing so because it's easier than waiting in line for their IT help desk to deliver them their boot encryption key.

[–] Revan343@lemmy.ca 3 points 3 months ago

it's easier than waiting in line for their IT help desk to deliver them their boot encryption key

Especially when the encryption keys are all stored on a Windows server that's bootlooped

[–] vikingtons@lemmy.world 1 points 3 months ago

I haven't been affected by this personally, just curious at this point what the variables are hah

[–] mkwt@lemmy.world 20 points 3 months ago

Sounds like a race condition in a kernel driver. Try it enough times and maybe you can get clear of it once without triggering.