Microsoft dev says Steve Ballmer didn’t write the text for the Blue Screen of Death: “There are three different blue-colored screens, and each has a different author”

A Microsoft developer breaks down the three types of Blue Screen of Death (BSOD) errors and who gets the credit.

When you purchase through links on our site, we may earn an affiliate commission.Here’s how it works.

What you need to know

What you need to know

What do we know aboutthe dreaded Blue Screen of Death (BSOD) erroraside from its annoying nature? “It’s a full-screen error that signifies a critical system failure related to a specific operation, which inevitably leads to a total device crash and forced reboot.”

Windows users might occasionally encounter the error during an upgrade, startup, or normal use.

There’s been an increasing interest in the ‘phenomenon,’ especially afterthe CrowdStrike global IT outagethat leftover 8.5 million Windows devices with dreadful BSOD errors for hours. Veteran Microsoft Software Engineer Dave Plummer (aka Dave’s Garage) recently shed light on the matter,explaining the massive outage caused by the faulty kernel driver. He spent most of his time debugging the errors while working at the company.

Interestingly, “there’s a 30-year mystery surrounding Microsoft’s Blue Screen of Death.” More specifically, who actuallywrotethe now-infamous BSOD? There’s been controversy revolving around who gets credit (or shame).

Adding some confusion to the matter, a 2014 blog post by Microsoft developer Raymond Chen indicated that erstwhile Microsoft CEO Steve Ballmer wrote the text for the Ctrl+Alt+Del dialog in Windows 3.1, which was misconstrued by some to mean he wrote the text for the Blue Screen of Death.

But that’snot the case.

Developer Chen has now cleared the air and indicated that Ballmerdidn’twrite the text for the BSOD. Ina new blog postfrom July 30, 2024, Chen indicated, “There is no mystery over who wrote the Blue Screen of Death, despite what some may want you to believe.”

Get the Windows Central Newsletter

Get the Windows Central Newsletter

All the latest news, reviews, and guides for Windows and Xbox diehards.

Who wrote the Blue Screen of Death in Windows?

Multiple reports identify Steve Ballmer, John Vert, or Raymond Chen as the BSOD’s authors. However, it’s not that simple because there are three different blue-colored screens, each with a different author.

Right off the bat, Chen lists the Windows 3.1 Ctrl+Alt+Del screen, which the developer calls a blue screen of unhappiness, not death. Did you know Windows 3.1 didn’t have a BSOD? Whenever the operating system crashed, users would get the “black screen of death.”

It’s worth noting that former Microsoft CEO Steve Ballmer wrote the text Windows 3.1 Ctrl+Alt+Del screen but not the code to display the message.

Next, the Windows 95 kernel error. Chen says most users consider it a Blue Screen of Death, but Windows 95 lets users skip or ignore the error. However, choosing to ignore it might crash your system. The developer admits he didn’t write the early version of the Windows 95 blue screen message but brought it to its final form in 1995, which is often misconstrued as Windows NT’s Blue Screen of Death.

Finally, John Vert wrote the Windows NT kernel error. Chen calls it the “true Blue Screen of Death” since the system is “unrecoverably dead at this point.”

Overall, it’s a fascinating trip down the memory hole for what is, like it or not, one of the most unique and defining features of the Windows operating system.

The real question, however, is not who authored the BSOD, but should Microsoft ever try to change it again to something different, and what would that look like?

Kevin Okemwa is a seasoned tech journalist based in Nairobi, Kenya with lots of experience covering the latest trends and developments in the industry at Windows Central. With a passion for innovation and a keen eye for detail, he has written for leading publications such as OnMSFT, MakeUseOf, and Windows Report, providing insightful analysis and breaking news on everything revolving around the Microsoft ecosystem. You’ll also catch him occasionally contributing at iMore about Apple and AI. While AFK and not busy following the ever-emerging trends in tech, you can find him exploring the world or listening to music.