https://www.bloomberg.com/news/articles/2024-07-22/crowdstrike-crwd-outage-nets-short-sellers-461-million-windfall?embedded-checkout=true

***I have looked into this and found out that they sent a file into the "Kernel" side where CrowdStrike operates, and they KNOW crashes there can be catastrophic. (as opposed to the "User" side) which basically the User and Kernel do not communicate and Kernel does not allow interaction. One would have to understand and know how to introduce the code instruction into the Kernel.

So it wasn't a Windows malfunction. It wasn't an update malfunction except for the fact they used it as a way to cyberattack their own cyber security system.
It is a very tedious and long explanation, but just know that this was NO accident. A file (long numeric code) they knew would bring the blue screens flying was purposely sent in. I have the data crash screen.

It is boring to most people so I haven't posted it. But I might later to also give a file that can restore if it happens again.

These people made almost a billion dollars!!!

They ARE probably going to do it again!

`The difference between the two:

Kernel Mode

In Kernel mode, the executing code has complete and unrestricted access to the underlying hardware. It can execute any CPU instruction and reference any memory address. Kernel mode is generally reserved for the lowest-level, most trusted functions of the operating system. Crashes in kernel mode are catastrophic; they will halt the entire PC.

User Mode

In User mode, the executing code has no ability to directly access hardware or reference memory. Code running in user mode must delegate to system APIs to access hardware or memory. Due to the protection afforded by this sort of isolation, crashes in user mode are always recoverable. Most of the code running on your computer will execute in user mode.