Windows Blue Screen of Death Situation in a Nutshell

There was a recent outage that happened Worldwide with a recent small update that originated from a new developer that just started working in Cybersecurity Software CrowdStrike.

Thank You for Watching this Video, if you enjoyed it Subscribe to the Channel for more.

If you want to be part of some big giveaways that are always happening, Join my Discord Server so you can stay in touch with me and the community that enjoys Gaming, PC Tech Memes and General Stuff:

You can Find me on other social Media Accounts where I constantly Post Memes, Informative Videos and Fun Gaming Content:

Instagram:

Twitter:

For business inquiries and brand promotions, you can contact me in this email:

[SIPEROTH]

Intel: Thank God it wasn't our chips this time behind this blue mess.

[markusTegelane]

The funniest part is that there is no remote fix for this, they literally have to physically go to thousands of computers, boot them into safe mode, delete a few files, then restart normally.

[socinety]

fun fact, niktek was trying to fix the blue screen error they got for hours, that's why they're posting this now

[gamtax]

So basically a security software firm just did a worldwide DDos themselves, one of the things they SHOULD protect their customers from.

[TSgotstolengoddamm]

that update was probably compiled on a intel 14th gen 14900ks processer clocked at 6.5ghz

[kinocchio]

I honestly thought Crowdstrike was a cigarette company.

[winni]

Well if your system depends on only once security company and doesn't have any backup system, you're doomed to experience this.

[kavky]

I can't wait for Monday when I have to reinstall OS on almost 100 workstations.

[burgersteak]

As a linux user, it was really funny how CrowdStrike made a single code error then went to a BSoD loop

[DragonOfTheMortalKombat]

Funny how serious this was but I didn't experience anything related to this at all

[LexaSkye]

windows 7 users: wait you guys got update?

[techwizard]

Plenty of reasons to hate Microsoft but this was Crowd strike's fault.

[itisworking]

This was such a common error in C++, they simply forgot to add a null check in the latest related datafile. Its confusing how can it go through testing then production. Like a simple reboot with that file in their own test environment could have shown the error 🤦‍♂️🤦‍♂️. Crowdstrike really need to eval their pipelines

[bananamonster]

All fun and games until the error gets a second phase or skynet if you may

[CC-]

0:14 I wasn't expecting Charlotte Motor Speedway to have the same issue as every company relying on Windows.

[vinterskog]

The Y2K bug is 24, 5 years late.
Edit: Indeed, year 20000 isn't quite here yet!

[inukaasith]

For those who looking for context, This happened basically for all windows versions which had falcon sensor installed.

A antivirus company Crowdstrike released an update for Falcon Sensor (antivirus software) which was broken

(there was a file named which contained all 0 values. Falcon driver which starts alongside windows tried to dereference a NULL pointer from the corrupt file)

This caused windows kernel to crash (these drivers run on ring 0, which means they have high privileges, but something bad happens os crashes with it too) and Windows stuck on a bootloop

solution was to boot into safe mode and delete the file

(Information found from internet)

[nursultannazarov]

AI is teasing us with what's coming.

[paulthedoge]

People really misinterpreted this situation. It's crowdstrike's fault for these millions of bluescreens, not microsoft's. Also only servers running the crowdstrike antivirus are affected, which is the reason why these issues never got to personal computers.

[Tamay.]

Meanwhile Lufthansa using Windows 95 protected them from the outage