Atlas Alerts incident

Microsoft Windows Crash due to Crowdstrike Issues

Critical Resolved View vendor source →

Atlas Alerts experienced a critical incident on July 19, 2024 affecting Atlas Alert, lasting 10d 3h. The incident has been resolved; the full update timeline is below.

Started
Jul 19, 2024, 11:41 AM UTC
Resolved
Jul 29, 2024, 02:50 PM UTC
Duration
10d 3h
Detected by Pingoru
Jul 19, 2024, 11:41 AM UTC

Affected components

Atlas Alert

Update timeline

  1. identified Jul 19, 2024, 10:20 AM UTC

    A recent worldwide Crowdstrike issue is causing a blue screen error on all recent versions of the Windows operating system running the Crowdstrike software. The only known workaround for affected Windows devices at this time is to: 1. Boot Windows into Safe Mode or the Windows Recovery Environment. 2. Navigate to the C:\Windows\System32\drivers\CrowdStrike directory. 3. Locate the file matching "C-00000291*.sys", and delete it. 4. Boot the host normally. This would require administrative access to complete the steps above. IS&T is working to restore central services that rely on Microsoft Windows. If you need assistance with you're Microsoft Windows desktop, please contact your local IT group or contact [email protected]. Crowdstrike has not yet posted any information to fully resolve this issue. As soon as we receive updates from Crowdstrike and/or Microsoft, we will update the community.

  2. identified Jul 19, 2024, 11:41 AM UTC

    A worldwide technology outage is causing a blue screen error on all recent versions of the Microsoft Windows operating system running Crowdstrike software. Crowdstrike is in the process of resolving the issue. In the meantime, MIT IS&T has a workaround for affected Windows devices. Please contact your local IT group or contact [email protected] for assistance. Crowdstrike has not yet posted any information to fully resolve this issue. As soon as we receive an update from Crowdstrike and/or Microsoft, we will update the community.

  3. monitoring Jul 22, 2024, 01:13 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 29, 2024, 02:50 PM UTC

    This incident has been resolved.