The Blue Screen of Death: Why Windows Crashes in Blue and Who Chose It

Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode!

The blue screen of death was not designed by psychologists to calm anyone down. When Windows NT 3.1 introduced the first true critical error screen in 1993, Microsoft developer John Vert wrote it to match what he already stared at all day: a MIPS workstation and the SlickEdit text editor, which defaulted to white text on a blue background. This episode traces the screen from the garbled text of Windows 1.01 and 2.03, through the blue task manager summoned by Control-Alt-Delete in Windows 3.1, to the stop error that halts everything.

That halt is a protective act. Windows 95, 98, and Millennium Edition let programs and the core system share memory and offered to continue after an error, which rarely ended well. Windows NT isolated the kernel and, when something went wrong inside it, stopped cold to keep corruption off the hard drive while dumping memory for engineers. The episode also covers the hexadecimal codes, the sad face introduced with Windows 8, the QR code of Windows 10, and the black screen announced for Windows 11 version 24H2 after the CrowdStrike outage of July 2024.

• In 2014, tech outlets misread a Raymond Chen blog post and credited Steve Ballmer with inventing the crash screen. Ballmer had only written the text for the Windows 3.1 task manager dialog.
• Chen clarified that he himself created the Windows 95 version of the error screen.
• At Comdex in 1998, a scanner plugged in by Chris Capossela crashed a Windows 98 beta in front of Bill Gates, who joked that this must be why it was not shipping yet.
• On Windows 95 and 98, a path using the reserved DOS device name con twice could crash the machine, and malicious websites hid it in their pages.
• Windows Insider builds crash to a green screen, and the Linux software suite systemd has added its own blue screen for critical boot failures.