Millions of users have recently encountered the notorious Blue Screen of Death (BSOD) errors, and the probable cause has been traced back to a CrowdStrike update. For those unfamiliar, CrowdStrike is an American cybersecurity firm that collaborates closely with Microsoft. The company has identified the issue and is actively working on a solution, having already reversed the changes that led to these disruptions.
“CrowdStrike is aware of reports of crashes on Windows hosts related to the Falcon Sensor. Symptoms include hosts experiencing a bugcheck blue screen error related to the Falcon Sensor. Our Engineering teams are actively working to resolve this issue and there is no need to open a support ticket,” stated CrowdStrike.
Related News
In addition to the BSOD errors, several Microsoft apps and services have become inaccessible. Microsoft has provided clarification on this issue through its Service Health Status updates. According to Microsoft, the root cause of the error is a configuration change in a portion of Azure backend workloads. This change caused an interruption between storage and compute resources, leading to connectivity failures that affected downstream Microsoft 365 services dependent on these connections.
“Preliminary root cause: A configuration change in a portion of our Azure backend workloads caused an interruption between storage and compute resources, which resulted in connectivity failures that affected downstream Microsoft 365 services dependent on these connections,” stated Microsoft.
What to Do to Keep Using Your Windows PC?
While CrowdStrike and Microsoft are diligently working on a fix, users can take some immediate steps to mitigate the issue:
- Boot into Safe Mode or the Windows Recovery Environment.
- Navigate to the C:\Windows\System32\drivers\CrowdStrike directory.
- Look for files named C-0000291*.sys and delete them.
- Reboot your PC in normal mode; it should start without encountering the BSOD.
As for the affected apps and services, it’s advisable not to use them immediately as they may trigger another BSOD. Users will need to wait for Microsoft to implement a backend fix. Meanwhile, you can follow the Microsoft 365 Status X handle for real-time updates on the fix and additional information. You can also revisit this article for updates on whether the problem has been resolved.
TRENDING NOW: Stay tuned for more updates as both CrowdStrike and Microsoft continue to work on resolving these issues.