<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bsod on Locodigital</title><link>https://locodigital.com.br/en/tags/bsod/</link><description>Recent content in Bsod on Locodigital</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 14 Sep 2026 09:00:00 -0300</lastBuildDate><atom:link href="https://locodigital.com.br/en/tags/bsod/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows ME: 26 years of the OS Microsoft wanted to forget</title><link>https://locodigital.com.br/en/technology/windows-me-at-26-the-os-microsoft-wanted-to-forget/</link><pubDate>Mon, 14 Sep 2026 09:00:00 -0300</pubDate><guid>https://locodigital.com.br/en/technology/windows-me-at-26-the-os-microsoft-wanted-to-forget/</guid><description>&lt;p&gt;Today marks 26 years since Microsoft put something on the shelves that promised to be the future of home computing — and ended up being the company&amp;rsquo;s biggest embarrassment to that point. On 14 September 2000, Windows Millennium Edition reached stores. Thirteen months later, Windows XP buried it so deep that most users preferred to pretend ME had never existed.&lt;/p&gt;
&lt;h2&gt;What was Windows ME?&lt;/h2&gt;
&lt;p&gt;Windows ME shipped as the successor to Windows 98 SE for the home market. The pitch was modern features: System Restore, Windows Movie Maker, Windows Media Player 7 and better integration with the digital cameras and USB devices that were taking off at the time.&lt;/p&gt;</description></item><item><title>CrowdStrike: the day one update caused 8.5 million BSODs</title><link>https://locodigital.com.br/en/technology/crowdstrike-the-july-2024-outage-and-the-global-bsod/</link><pubDate>Sun, 19 Jul 2026 10:00:00 -0300</pubDate><guid>https://locodigital.com.br/en/technology/crowdstrike-the-july-2024-outage-and-the-global-bsod/</guid><description>&lt;p&gt;It was 04:09 on 19 July 2024 when a 40 KB file left CrowdStrike&amp;rsquo;s servers heading for millions of computers around the world. Seventy-eight minutes later, hospitals were down, planes weren&amp;rsquo;t taking off and airport terminals were displaying the most famous blue screen in computing. No hacker. No ransomware. No intrusion. A single wrong field in a configuration file was enough to produce the biggest cyber outage ever recorded.&lt;/p&gt;
&lt;p&gt;Two years on, the incident is still generating lawsuits, debates about kernel access and changes to how security software is updated across the entire industry.&lt;/p&gt;</description></item></channel></rss>