[Intro]
Hello!
Everyone who has worked on a Windows PC has encountered the blue screen of death (BSOD). It can arise for absolutely any reason: from a driver error to an error about the loss of the system partition at the boot stage.
In the past, the BSOD could appear trivially as a result of the operation to remove the CD while reading it.
The BSOD has changed many times over 30 years and in this video I propose to look at how blue screen of death has changed, which for a while was not even blue at all.
The BSOD first appeared in Windows 3.1, called by the Ctrl+Alt+Delete key combination and serving as a kind of Task Manager.
That is, through this screen, it was possible to remove the hung application and continue to work with the system. If you pressed the combination twice, the computer would restart.
However, in the case of a global failure, the BSOD did not appear: the system was forced to shut down and either just a black screen or MS-DOS console.
In the Windows 9x, the blue screen design has not undergone any changes, but it has started to appear more frequently.
If the system behaved unstable, if there was an error in the address path in memory or if there was a system driver error, this screen would always appear. The user had two ways to solve the problem: either to restart the computer or to continue working with the system by pressing Enter.
However, the second variant of the solution rarely helped, because the system often hung up anyway.
But not always the system could offer the user a solution to the problem: if during booting a VFAT device initialization error occurred, then the user saw a BSOD with a driver initialization error, the message stopping the driver loading and the message "System halted".
In Windows NT Family, compared to Windows 9x, the blue screen of death has completely changed.
It now began to show up only when an error occurred in kernel or driver code running in kernel mode or in system processes that are running in user mode, which is unrecoverable.
[in the mode that comes after the loader and is accompanied by the appearance of the cursor and GUI]
BSOD has also become more informative.
When a blue screen of death appears in Windows NT and similar systems, the only option is to reboot the computer, but it is automatic by default if you have not changed the system behavior settings at the time of the BSOD.
The system also creates a record in the system log with the parameters of the error. And if memory dumping is enabled in the settings, the system log will also show the cause, the stop code, the time of the error itself, and the name of the driver where the error occurred.
The design of BSOD has also been changed. The color, of course, remains the same, but a lot of additional information has appeared: the error code and name, the parameters that explain the error, the address of the error location if the system has the possibility to specify it and the name of the file/driver where the error occurred.
In Windows 2000, the blue screen has been greatly simplified in terms of appearance and information.
It now contains only the error code, its name, and tips about what if this is the first time you have encountered the death screen or if you have seen it more than once.
From Windows XP to and including Windows 7, the death screen has changed again. It changed its font and became more elongated, saying that "a problem has been detected and Windows has been shut down to prevent damage to your computer",...
...the name of the driver that caused the problem, troubleshooting tips and technical information in the form of an error code, a rewrite of the driver name where the problem occurred and the memory address.
However, if any system process fails and abruptly terminates (for example winlogon.exe which is the logon component and calls other system processes),...
...you will get a blue screen of death, which will only have an error code and no other information except "The Windows Logon Process system process terminated expectedly with a status of..."
In Russian version of Windows XP-7 - this BSOD has corrupted symbols, but in English version everything is fine.
In Windows 8, BSOD has undergone a redesign.
The color has changed from dark blue to sky blue, the font from Consolas to Segoe UI, and in general - absolutely everything has changed.
Now BSOD does not contain technical information and tips to solve the problem.
Now it contains first a sad smiley face, an inscription about restarting and an error code, the solution of which is suggested to find on the Internet.
But, in one beta build of Windows 8, the screen of death was not blue, but completely black and did not contain a sad smiley face - immediately the inscription that "Your PC needs to restart".
BSOD from Windows 10 not change comparing Windows 8, except for one thing: a QR-code appeared.
By scanning the QR leads to the main Windows help page on the Internet.
There is also a new kind of BSOD: in addition to the blue screen, there is also a green screen from 2016 - it is only available in Windows 10 Insider Preview builds.
But in the release version of Windows 11, the death screen suddenly became black again. For what reason this was done is unknown.
[Although I can assume that they were trying to make a single color service screens. That is, the " Please wait" screen became black, the "Shutting down" screen also became black and why not make the BSOD black.]
But soon the color was restored to its previous version.
It doesn't contain anything new, it's the same font, smiley face and text. Absolutely identical to the latest builds of Windows 10.
Anyway, that's how the blue screen of death has changed over more than 30 years.
A lot of designs have changed, but the point remains the same - to notify the user about a problem with the system and give some technical information.
However, the so-called blue screen is not only present in Windows.
It is also present in ReactOS and in mobile devices like Windows Mobile. Other operating systems have their own stop screens.
That's all, if you liked the video - leave a like it, please.
You can also subscribe to the channel to support me. See you later!