Urgent.News

What's breaking now, across thousands of outlets.

Tech

The Windows blue screen of death could have looked completely different if a 33-year-old decision had gone another way

The white text on a blue background wasn't a strategic decision at all

The Windows blue screen of death could have looked completely different if a 33-year-old decision had gone another way

The Windows blue screen of death (BSOD) has been a familiar sight for many computer users over the years, signifying catastrophic errors that prevent the operating system from functioning normally. This error screen, reserved for such critical situations, displays details about the process responsible for the fatal crash and restarts the system to prevent data and hardware damage.

However, the choice of the blue color for the BSOD was not intentional but rather a matter of familiarity. Microsoft engineers working on Windows NT in the early 1990s picked the blue color because it was already in use on the MIPS workstations and the SlickEdit text editor. The blue screen has remained unchanged for decades until Microsoft decided to change it to black in 2024, ending the three-decade legacy of the blue screen of death.

The decision to change the color was driven by a more streamlined user interface, with Microsoft citing a desire for a simpler look. The change was accompanied by the removal of the sad face and QR code, which were previously included in the error screen. Despite the change, many users have expressed dissatisfaction with the new look, finding it more intimidating and less reminiscent of a fatal error screen.

Written by urgent.news from XDA Developers's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at xda-developers.com →

More in Tech

ripgrep Missed the CSV Files. I Almost Designed a Collector We Already Had.

Originally published on hexisteme notes . I was researching how to improve operations on my blog, and the research reached a confident conclusion early: there was no Google Search Console data to work…

  • Initial analysis missed CSV files due to ripgrep's default settings
  • Author reruns ripgrep with filters to include hidden files and ignore rules
  • Existing function performs required task, no need for new collector

LFM2.5-24B-A2B: Built for Fast On-Device Agents

  • LFM2.5-24B-A2B is a 24-billion-parameter reasoning model with 2-billion active parameters
  • Outperforms Qwen3.6-35B-A3B on five out of eight agentic and tool-use benchmarks
  • Achieves up to 1.7 times faster performance than comparable models on-device

Migrate Jest to Vitest With 3 Parallel Agents, One Directory Each

Book: TypeScript Essentials Also by me: The TypeScript Library — the 5-book collection My project: Hermes IDE | GitHub — an IDE for developers who ship with Claude Code and other AI coding tools Me…

  • Configure shared layer for Vitest 5 with Node.js 22.12 or later, Vite 6.4 or later.
  • Create vitest.config.ts mimicking Jest suite, set globals to true, specify environment as node.

More from Thursday 15 October →