Today, July 19, countless Microsoft Windows 10 users encountered the Blue Screen of Death issue (BSOD), which resulted in their PCs shutting down or restarting. According to Microsoft, the disruption resulted from a third-party security upgrade that made PCs malfunction or turn Blue.
Around the world, Windows devices experienced outages due to the “blue screen of death” (BSOD), which also caused problems for banks, airlines, IT companies, and other industries. Be aware that Windows is not the cause of this. It is started by Crowstrike, a third-party endpoint security software. According to reports, the problem, which left devices trapped in a boot loop, surfaced after a CrowdStrike upgrade. Microsoft described the issue as being caused by a CrowdStrike agent system file failure and reported the fault with the STOP code “PAGE_FAULT-IN-NONPAGED_AREA.”
The Blue Screen of Death (BSOD): What is it? A serious issue that causes Windows to abruptly shut down or restart is what causes the Blue Screen of Death (BSOD) error. In certain US regions, 911 emergency services have also been impacted by Microsoft’s software outage, in addition to Microsoft 365 and Microsoft Store.
Microsoft said, “We’re working on rerouting the impacted traffic to alternate systems to alleviate impact in a more expedient fashion. More info is posted in the admin center under MO821132 and on http://status.cloud.microsoft”
Due to a communication difficulty, American, United, and Delta Airlines halted their planes while Berlin Air ceased all of its operations.
Also Read: Comparison: OnePlus Nord 4 Vs Poco F6
“The underlying cause has been fixed, however, residual impact is continuing to affect some Microsoft 365 apps and services. We’re conducting additional mitigations to provide relief. More details can be found within the admin center under MO821132 and on https://status.cloud.microsoft”
The company further added, “We’re continuing to resolve the residual impact
and monitoring the Microsoft 365 apps and services while they fully recover. More details can be found within the admin center under MO821132 and on https://status.cloud.microsoft”
Workaround Steps:
- Launch Windows via the Windows Recovery Environment or Safe Mode.
- Open the wdStrike directory in C: \Windows\System32\Drivers\Cro.
- Find and erase the “C-00000291*.sys” file.
- Give the host a regular reboot.
Note: Keep in mind that these are stopgap measures that might not work on all impacted systems, particularly those protected by BitLocker. This workaround won’t function if the laptop provided by the company has very limited resources and isn’t even able to access the boot menu.
, which resulted in their PCs shutting down or restarting.){kind=link}