Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CrowdStrike Update: Windows Bluescreen and Boot Loops

old.reddit.com

Post reply on HN
Print view View original

811–820 of 1001 posts

Re: CrowdStrike Update: Windows Bluescreen and Boot Loops

#811

Post by wufufufu »

Anyone have a technical writeup of the actual bug? I'm trying to explain how this could happen to people who think this is related to AI or cyber attacks.

What happened to the QA testing, staggered rollouts, feature flags, etc.? It's really this easy to cause a boot loop?

To me, BSOD indicates kernel level errors, which I assume Crowdstrike would be able to cause because it has root access due to being a security application. And because it's boot-looping, there's not a way to automatically push out updates?

Re: CrowdStrike Update: Windows Bluescreen and Boot Loops

#812

Post by matrix87 »

1024core wrote: post #716

Read on Mastodon: https://infosec.exchange/@littlealex/112813425122476301 The CEO of Crowdstrike, George Kurtz, was the CTO of McAfee back in 2010 when it sent out a bad update and caused similar issues worldwide. If at first you don't succeed, .... ;-) j/k

who is hiring these fucking idiots? they need to be blacklisted

Re: CrowdStrike Update: Windows Bluescreen and Boot Loops

#814

Post by secondcoming »

eitland wrote: post #468

Some Canonical guy I think many years ago mentioned this as their sales strategy a few year ago after a particularly nasty Windows outage: We don't ask customers to switch all systems from Windows to Ubuntu, but to consider moving maybe a third to Ubuntu so they won't sit completely helpless next time Windows fail spectacularly. While I see more and more Ubuntu systems, and recently have even spotted Landscape in the…

Ubuntu has unattended-upgrades enabled by default

Re: CrowdStrike Update: Windows Bluescreen and Boot Loops

#816

Post by jboy55 »

steelframe wrote: post #640

Wow, this hits close to home. Doing a page fault where you can't in the kernel is exactly what I did with my very first patch I submitted after I joined the Microsoft BitLocker team in 2009. I added a check on the driver initialization path and didn't annotate the code as non-paged because frankly I didn't know at the time that the Windows kernel was paged. All my kernel development experience up to that point was wi…

I was thinking, this doesn't seem like its a case of all these machines still on an old version of windows, or some specific version, that is having issues. Therefore QA just missed one particular variant in their smoke testing. It seems like its every windows instance with that software, so either they don't have basic automated testing, or someone pushed this outside of a normal process.

Re: CrowdStrike Update: Windows Bluescreen and Boot Loops

#820

Post by charles_f »

jmcgough wrote: post #131

Took down our entire emergency department as we were treating a heart attack. 911 down for our state too. Nowhere for people to be diverted to because the other nearby hospitals are down. Hard to imagine how many millions of not billions of dollars this one bad update caused.

> Hard to imagine how many millions of not billions of dollars this one bad update caused.

I mean, if the problem is that hospitals can't function anymore, money is hardly the biggest problem

Post reply on HN