Thousands of Windows computers encountered the 'blue screen of death' error, the airline was paralyzed

A series of media companies, technology companies and many organizations reported that their computers running Windows 10 are experiencing the Blue Screen of Death.

At noon on July 19 Vietnam time, thousands of Windows computers in many countries around the world were stuck in a Recovery screen loop requiring users to restart the device.

Thousands of Windows computers encountered the 'blue screen of death' error, the airline was paralyzed Picture 1Thousands of Windows computers encountered the 'blue screen of death' error, the airline was paralyzed Picture 1

The cause of the incident was an update to CrowdStrike, a cybersecurity platform that provides security solutions for Windows computers. After receiving the reports, CrowdStrike has now acknowledged the problem and said it is working to fix the situation.

This incident affected thousands of users and businesses in India, Japan, Canada, Australia and many other countries, disrupting the services of many airlines and banks.

In the US, major airlines including American Airlines, Delta Airlines and United Airlines have issued orders to stop takeoffs citing communication problems.

In Malaysia, passengers at Kota Kinabalu International Airport in Sabah cannot check in their luggage for AirAsia flights.

At Changi Airport in Singapore, passengers are waiting in long lines to check in.

The incident also affected Amsterdam's Schiphol airport (Netherlands), one of the busiest aviation hubs in Europe.

In Germany, flights at Berlin Brandenburg airport were suspended due to "technical problems".

While waiting for CrowdStrike to fix the problem, a temporary solution at this time that can partly fix the problem and help overcome the blue screen error mentioned above is to find a way to boot into Safe Mode or Windows Recovery mode. Environment (press F8 during Boot) and then navigate to the C:WindowsSystem32driversCrowdStrike folder -> locate the file matching C-00000291*.sys and delete it. Finally, start the server normally.

4 ★ | 1 Vote