Today, I was working on my laptop when suddenly the screen turned blue with some error text displayed. At first, I thought it was a malware issue. Then, one of my colleagues called me and asked if I knew anything about it; her screen had also turned blue. After a few moments, more staff members experienced the same issue. We were worried as we were unsure if it was due to a virus, a cybersecurity attack, or a technical problem.
Our Tech Team informed us and confirmed that there was a Microsoft Global Outage. The problem was so widespread that it affected airlines, government offices, businesses, emergency services, and many other sectors globally. We started scrolling through our social media feeds and found that many users were uploading screenshots of the blue screen errors.
Let’s talk about what the blue screen error is and how this problem suddenly arose globally.
Microsoft officially announced that there are many reasons behind blue screen errors. It can be a result of serious problems that cause Windows to shut down and restart immediately. A software or hardware problem can also be a reason behind this. – Source
However, in this particular case, there is another explanation.
Crowdstrike has admitted that this blue screen problem is a consequence of a Windows update that was rolled out on Friday. The company said that its engineering team is working to solve the problem.
Here’s what The Economics Times tells us about the blue screen problem. I hope you find this helpful.
CERT-In issued an advisory regarding a major Microsoft Windows outage caused by a CrowdStrike Falcon Sensor update, leading to system crashes and “Blue Screen of Death” errors. The government is coordinating with Microsoft to resolve the issue, while CrowdStrike has reverted the update changes. – Source
I hope this global problem will be resolved as soon as possible and that the Microsoft team working on the blue screen issue will fix it soon.
Date- 22-07-2024: As per the latest report, Microsoft announced that the global tech outage issue has been resolved now.
