August 6th, 2024

Who Wrote the Blue Screens of Death

The Blue Screen of Death has three versions with different authors: Steve Ballmer for Windows 3.1, Raymond Chen for Windows 95, and John Vert for Windows NT, clarifying previous misconceptions.

Read original articleLink Icon
Who Wrote the Blue Screens of Death

The article clarifies the authorship of the Blue Screen of Death (BSOD) in Microsoft Windows, dispelling claims of a 30-year mystery. It identifies three distinct blue screens, each with a different author. The first is the Windows 3.1 Ctrl+Alt+Del screen, which was written by Steve Ballmer, although it is not a true BSOD. The second is the Windows 95 kernel error message, which was finalized by Raymond Chen, though he did not create the initial version. Lastly, the true BSOD, associated with Windows NT, was authored by John Vert. The article emphasizes that the confusion arises from misidentifying these different screens and their respective authors, rather than a singular mystery surrounding the BSOD's creation.

- The Blue Screen of Death has three different versions, each with distinct authors.

- Steve Ballmer wrote the text for the Windows 3.1 Ctrl+Alt+Del screen.

- Raymond Chen finalized the Windows 95 kernel error message.

- John Vert is credited with the true Blue Screen of Death for Windows NT.

- Misunderstandings about the BSOD's authorship stem from conflating different screens and their contexts.

Link Icon 12 comments
By @sickblastoise - 9 months
Funny I started reading the article and knew who the author was once they said they introduced the blue screen of death, none other than Raymond Chen. If you're ever reading an article with the microsoft icon in the tab, and think "Wow this is pretty intriguing or thought provoking!", just scroll up and you will see Ray's face, he's been killin' the microsoft blog for 20+ years. Here's one from 2003: https://devblogs.microsoft.com/oldnewthing/20031224-00/?p=41...
By @rawgabbit - 9 months
What I want to know is who wrote these haikus.

First snow, then silence. This thousand-dollar screen dies So beautifully

Yesterday it worked. Today it is not working. Windows is like that.

By @legitster - 9 months
If you like this early Windows lore, Dave Plummer (creator of the original Task Manager) has a Youtube where he dives into this stuff: https://youtu.be/KgqJJECQQH0?si=E36pUB9CQeGTy_bu&t=525

While there were three different blue screens of death, all modern ones derive from John Vert's for Windows NT. And the shade Vert chose was the default screen background color from the MIPS RISC machine he built on.

By @par - 9 months
As soon as I saw the author was Raymond Chen, I immediately knew I was in for some true BSOD lore.
By @diggan - 9 months
But the article is from July 30th, 2024, and last time I used Windows 10/11 and it crashed, it was neither of those.

So who wrote the latest iterations?

By @cainxinth - 9 months
Ballmer personally wrote the Win 3.1 BSOD... Who knew?
By @francisofascii - 9 months
What I found annoying is the output does not seem helpful at all. Even if you are tech savvy or an IT manager, does the memory dump information help you diagnose the problem? Did the Microsoft programmers at least benefit from it?
By @wdfx - 9 months
Has anyone ever successfully used the BSOD register, memory, stack, status dump information to diagnose and fix a fault?

Are those values even useful given that the machine is halted and there's no way to inspect or read any additional information about what was running and where it was in memory?

I suspect there are a select few that can do this, but for the rest of us it's a reboot and reload situation. Also, those that could use this information probably also could fix and resolve the crash without it?

So, what's the point of even dumping that info to screen, instead of putting up a simple "oops, I died, time to restart" message?

By @ComputerGuru - 9 months
I must disapprove of the anachronistic usage of fonts in those blue screen renders!
By @greatNespresso - 9 months
I was discussing this some time ago with a friend, I get the feeling that error messages these days try too much to apologize instead of providing the user with hints and clear explanations to solve the issue. It's all about emoji faces crying "boohoo there was an error" with a childish tone.

Can't wait to see AI avatars crying in front of you for failing to summarize an article.

By @amelius - 9 months
Like, could they have made the UX any worse?