Technology

37707 readers

80 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

137

To Fix CrowdStrike Blue Screen of Death Simply Reboot 15 Straight Times, Microsoft Says (www.404media.co)

submitted 3 months ago by [email protected] to c/[email protected]

46 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 5 points 3 months ago (2 children)

Most of our machines at my office run Win 10 or 11 and we haven't had the blue screen. I was wondering why we hadn't experienced this. Still don't know.

[–] [email protected] 4 points 3 months ago

You don't use CrowdStrike presumably

[–] [email protected] 4 points 3 months ago (1 children)

Azure is MS's cloud computing. As long as you weren't using MS OneDrive, or 365 Office, or something else that relied on MS cloud, you're good.

[–] [email protected] 23 points 3 months ago* (last edited 3 months ago) (2 children)

Actually it's due to whether your company uses CrowdStrike or not.

The issue is not being caused by Microsoft but by third-party CrowdStrike software that’s widely used by many businesses worldwide for managing the security of Windows PCs and servers.

Supposedly, one of the fixes (aside from rebooting and hoping it grabs the update fire) is to delete a single file in the CrowdStrike directory after booting into safe mode.

[–] [email protected] 6 points 3 months ago (1 children)

I just spent the morning doing this with my help desk team, although we just do it via command prompt at the recovery screen. We've had a 100% success rate so far at 93 devices and counting. I'm glad our organization practices read only Friday, at least.

[–] [email protected] 3 points 3 months ago

Tbh, I would then also not update anything on Thursdays (which does maybe do overnight procedures) since it may be breaking over night then, leaving you just little time to fix before the weekend :D

This kinda can be extended up until Monday, I know, but, at least in Germany, on Fridays people go home way sooner than other days.

[–] [email protected] 2 points 3 months ago (2 children)

Yes, but Azure platform itself was using it. So many of those systems were down overnight (and there's probably still stragglers). The guy you responded to specifically called out Azure-based services.

[–] [email protected] 4 points 3 months ago* (last edited 3 months ago) (1 children)

Sure, but the OP of the thread didn't.

Most of our machines at my office run Win 10 or 11 and we haven't had the blue screen. I was wondering why we hadn't experienced this. Still don't know.

So it isn't whether you're using Azure, it's whether you're using CrowdStrike (Azure related or not)

[–] [email protected] 2 points 3 months ago (1 children)

So it isn’t whether you’re using Azure, it’s whether you’re using CrowdStrike (Azure related or not)

No. Azure platform is using Crowdstrike on their hypervisors. So simply using Azure could be sufficient to hurt you in this case even if your Azure host isn't using Crowdstrike itself. But yes, otherwise it's a mix of Windows+Crowdstrike.

[–] [email protected] 4 points 3 months ago* (last edited 3 months ago)

Can you source your claim, that Azure hypervisor uses CrowdStrike? Because a Microsoft spokesperson told Ars that that issue was unrelated to the CrowdStrike update.

[…] cited as "a backend cluster management workflow [that] deployed a configuration change causing backend access to be blocked between a subset of Azure Storage clusters and compute resources in the Central US region."

A spokesperson for Microsoft told Ars in a statement Friday that the CrowdStrike update was not related to its July 18 Azure outage. “That issue has fully recovered,” the statement read.

[–] [email protected] 3 points 3 months ago* (last edited 3 months ago)

Microsoft services were, in a seemingly terrible coincidence, also down overnight Thursday into Friday. […]

A spokesperson for Microsoft told Ars in a statement Friday that the CrowdStrike update was not related to its July 18 Azure outage. "That issue has fully recovered," the statement read.

from https://arstechnica.com/information-technology/2024/07/major-outages-at-crowdstrike-microsoft-leave-the-world-with-bsods-and-confusion/

They were not "using it". And there's no "stragglers still".