Summary of Reddit Comments on Fixing Windows BSOD

Recommendations for Fixing Windows BSOD

• Detach and Attach EBS Volume: Detach the affected EBS volume, attach it to a working EC2 instance, remove the affected Crowdstrike file, and reattach it to the old instance.
• Steps to Fix:
  • Write down faulty EC2 EBS volume ID and availability zone.
  • Stop EC2 instance forcefully.
  • Detach the EBS volume and attach it to a new or different Windows EC2 instance in the same availability zone.
  • Remove the Crowdstrike file from the EBS volume on the new instance.
  • Attach the repaired EBS volume back to the initial EC2 instance.
• Issues with EC2Rescue: Some users found using EC2Rescue to fix the issue requiring another EC2 instance in the same region, creating some complications.

Pros and Cons

Pros

• Step-by-step guide provided for fixing the issue at hand with clear instructions.
• Users sharing links to official AWS documentation and tools for automating the remediation process at scale.
• Collaboration on creating scripts and tools to assist in fixing the affected instances.
• Community support and willingness to help in resolving the Windows BSOD issue.

Cons

• Labor-intensive and time-consuming process to fix the BSOD issue across multiple EC2 instances.
• Challenges with VMs not booting properly even after attempting to fix the issue.
• Issues with detaching volumes from running VMs leading to potential data corruption.
• Difficulties in managing a large number of affected hosts, especially in secure environments with restrictions on local admin access.
• Frustration with Crowdstrike for the faulty update causing widespread issues and the time-consuming manual fix required.

Additional Insights

• Dump Files: Request for dump files for accurate analysis of BSODs detailing the process to produce and share them for troubleshooting.
• Challenges with Bitlocker: Difficulties accessing command prompt without the Bitlocker key, causing challenges in fixing the issue.
• Concerns with Crowdstrike: Criticisms towards Crowdstrike for the faulty update causing widespread disruptions and the manual intervention required to resolve the issue.
• Community Support: Advice given on taking breaks, staying hydrated, and not burning out while dealing with the aftermath of the BSOD issue.

This comprehensive summary provides insights into the steps, challenges, pros, and cons associated with fixing Windows BSOD caused by the Crowdstrike file issue. Users shared experiences, recommendations, and tools to assist in resolving the issue effectively.