Evolution of Windows BSOD Screen 1985-2022

preview_player
Показать описание
Evolution of Windows bsod screen from 1985 to 2022 but it is in short version

changes from the 2021 Version:
1. added the new Windows 11 bsod screen
2. excluded the Windows insider preview and Windows Server Version blue screen as it is a short Version.

Please note:
Windows Longhorn RSOD screen is actually a boot error of Windows Longhorn build 5048,but not crashing screen. All Windows Longhorn builds used the same bsod crashing screen as the Windows XP,vista and 7 have.

Please like and subscribe :)

Music used:
LFZ - Popsicle [NCS Release]
Music provided by NoCopyrightSounds
Рекомендации по теме
Комментарии
Автор

*The first Windows Blue Screen is like an alien language.*

NyxieFurry
Автор

In some versions of Windows 7/8/8.1, the text would say "Your computer ran into a problem that it couldn't handle, and now it needs to restart."

AJOTR-animations-productions
Автор

When the windows versions are so old they look like ancient Egyptian hieroglyphs.

zZeimos
Автор

My dad installed windows 11, it was easter midnight 2022 (i think so) when my dad installed it. Few days later, i was going to play in my dad computer and i pressed a button in the keyboard. The home screen appeared but nothing appeared. After few minutes it blue screened. As i was scared of bsods, i runned crying. And thats how i got my first bsod. It was horrible.

windowsvista
Автор

aw hell nah who put windows 3.0 talking enchantmant table 💀

nevtf
Автор

A problem has been detected and Windows has been shut down to prevent damage to your computer.

If this is the first time you've seen this stop error screen, restart your computer. if this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. I this is a new installation, ask your hardware or software manufacturer for and Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.

Technical information:

*** STOP: 0x847075cc)

windowsbackup
Автор

i really like how detailed nt 3 and nt 4's bsod were. sure, a power user like me can diagnose and fix it myself, but i understand why microsoft dumbed it down overtime. the stop codes and parameters are more important than memory addresses to most users that arent programmers.

for windows 8 onwards, they need to provide more info on screen than just the stop code. that'll require examining the dump files instead, if possible.

percentmicky
Автор

The 1607 to 1909 uses the 2004 to present and the 1607 to 1909 uses all versions since 1607 and it only occurs if Windows crashes during installation and typing wininit on command prompt recovery mode

SebastiansEpicVideosOfficial
Автор

Windows 1.0 and 2.0 didn’t actually have a BSOD. Im pretty sure the first Windows OS that ever used one was Windows 3.0, and it used the 3.1 one.

scuti
Автор

Windows 1.0:
POV: Windows 1.0 speaks gibberish

realwarriors
Автор

"Omg bsod?"
"Nah black screen of death"

dark-o
Автор

When an OS is so old that a single BSOD crashes the text

windowsbackup
Автор

1.0 and 2.0 it not actually BSOD, it is only an Assembly error when you use higher MS-DOS 3.0

xpfan
Автор

3.0 had a *BLACK* screen of death similar to the Win3.x one

MyComputerStudios_
Автор

I remember this song from dominoes falling with planks!!

cadenchristner
Автор

the music is just perfect for the video

blackstonepanther
Автор

Windows 1.0 to 3.0 be like: *enchantment table*

JPThibauShorts
Автор

In 3.1 it's not an error. This can be opened by Ctrl alt delete

GamePlayandmore-bv
Автор

Everybody gangsta until it goes enchanting table

polnareff
Автор

Windows NT 3.x and 4.0 is Really Confusing

joln