Blue screen of death
|Component of Microsoft Windows|
|Introduced in||Windows 3.0 build 55|
Windows NT 3.1 October 1991 build
|Last included in|
A blue screen of death (also known as the blue screen, bug check, or Stop error) is a common name for the screen that occurs during a system crash in Microsoft Windows operating systems. It is shown when the operating system can no longer function safely due to a fatal system error.
History[edit | edit source]
Early versions[edit | edit source]
Contrary to popular belief, Windows 1.0 and Windows 2.x did not have a crash screen. When early Windows is run on a newer version of MS-DOS, it will print out an "Incorrect DOS version" error message, followed by garbled contents of the memory during the boot before loading into the Windows shell, which is often thought to be a crash screen, however, it is only a bug in the logo code. Whenever Windows did crash, it often resulted in a system hang or the shell returning back into DOS.
A modal dialog for displaying important system messages was first introduced in Windows 3.0 and was mostly used by virtual device drivers in 386 enhanced mode. This was a full screen message in text mode, which suspended Windows until being dismissed by the user. Initially, it used a black background, although Windows 3.1 later changed it to blue. The look of the modal dialog was virtually unchanged through the rest of the classic Windows series.
In Windows 3.x, this was mostly used in situations where a program couldn't continue running until the user resolved an issue, such as device conflicts or disk swaps. However, severe system errors still caused Windows to exit back to MS-DOS, similarly to the older versions. The interface was also used for a simple task manager in Windows 3.1, which could be invoked by pressing Ctrl+Alt+Del while running Windows in the 386 enhanced mode. The task manager allowed the user to terminate an unresponsive program, or if there's no unresponsive programs, simply allow the user to exit the screen or press Ctrl+Alt+Del again to reboot the system. Steve Ballmer wrote the original message for the Task Manager warning.
Windows 9x[edit | edit source]
Windows 95 used the modal dialogs to report severe system errors instead of exiting to DOS, which earned it the blue screen of death nickname. Windows 9x is unique in that it allows the user to continue after a system error, although it often resulted in an unstable system. The user interface was also used in early Windows 98 builds for ACPI subsystem errors, which notably used a red background instead of blue. Early builds of Windows Me briefly replaced the "It is now safe to turn off your computer" with a blue screen modal dialog at one point.
Windows NT[edit | edit source]
On Windows NT, blue screens are also commonly known as STOP errors, referring to the
*** STOP label that introduces the error code. The first known build to implement a blue screen is the October 1991 build of Windows NT 3.1. Earlier builds merely print the error code to a debugger, if attached, and trigger a breakpoint in an infinite loop. According to John Vert, the developer who originally wrote the code in the NT kernel that was responsible for controlling the screen in text mode, the white-on-blue color was chosen in order to match the MIPS' firmware display, as well as the default color scheme of the SlickEdit text editor many NT developers used at the time.
Initially, a system crash only resulted in the error code being printed out to the screen, although later during Windows NT 3.1 development it was extended to also display the stack trace and a list of loaded drivers and their base addresses. From Windows 2000 build 1796.1 onwards, the message was simplified to only include possible instructions for the user should they encounter the blue screen and now renders in 640x480 graphics mode instead of 80x50 text mode. The font was changed to Lucida Console in Windows XP build 2474.
During the development of Windows 8, the blue screen underwent many significant changes. Around build 7814, the blue screen was updated to support higher resolutions using VBE 2.0 and anti-aliasing. At first, this updated blue screen only appeared if the system crashed at boot, however, by the time of build 7880 it was used for all bug checks. It would be quickly replaced to a more simplified black screen in build 7899, and would remain until build 8045 released with a black screen that would resemble the RTM. The background color was later changed to a shade of cerulean in build 8064.
In Windows 10 build 14316.1000, a QR code was added to the blue screen, linking to Microsoft's website for diagnosing blue screen errors. Windows 10 build 14993 changed the color and wording of the bug check screen to green for Insider builds in order to be able to quickly distinguish between Insider and production build bug reports.
In Windows 10 May 2020 Update and above, the wording was changed from "Your PC ran into a problem" to "Your device ran into a problem", but otherwise, the layout remained the same.
In Windows 11 build 22000.51, users who are not in the Windows Insider Program will receive a black screen of death instead of the usual blue. The black screen can also be toggled on by changing the
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CrashControl\DisplayPreReleaseColor DWORD value to
0. The QR code was also dropped for server builds starting with Windows Server build 22463.
Implementation[edit | edit source]
In classic Windows, the blue screen is implemented by the
SHELL_SYSMODAL_Message routine in the Shell VxD. The routine temporarily halts the system and then proceeds to tell the display driver to switch the display to text mode. It sets the background and foreground color, clears the screen and displays the message. It then waits for a valid keypress before switching back to graphics mode and resuming operation. On Windows 9x, it is most commonly called from
VWIN32.VXD, which displayed the infamous message about an occurring exception.
The blue screen on NT-based systems is implemented in the
KeBugCheckEx functions, which are contained in the kernel executable. The difference between the two functions is that the former accepts only the bugcheck code as an integer parameter, while the latter also accepts four more integers as bugcheck parameter codes, which can have different meaning depending on the bug check code. A component running in kernel mode can call either function to bring the system down in controlled manner if it detects a fatal uncorrectable error that can lead to data corruption. The respective function then takes care of switching to a compatible video mode, rendering the blue screen itself, saving a memory dump, and, if enabled, restarting the system.
User mode processes can also trigger a bug check if they hold the shutdown privilege by using the
NtRaiseHardError system call in
ntdll.dll with the
OPTION_SHUTDOWN_SYSTEM flag, which transitions the system to kernel mode and then triggers a
FATAL_UNHANDLED_HARD_ERROR bug check.
Gallery[edit | edit source]
Classic Windows[edit | edit source]
Corrupt swap file warning in Windows 3.0 build 55
Task Manager warning in Windows 3.1 build 043e
Task Manager warning in Windows 3.1 build 068
Task Manager warning in Windows 3.1
ACPI error in Windows 98 build 1400
System crash in Windows Me
Windows NT[edit | edit source]
System crash in the October 1991 build of Windows NT 3.1
System crash in Windows NT 3.1 build 340.1
System crash in Windows NT 3.1
System crash in Windows 2000 build 1631.1
System crash in Windows 2000 build 1835.1 (note the darker text)
System crash in Windows 2000 build 1906.1
System crash in Windows 2000
System crash in Windows XP build 2442
System crash in Windows XP build 2462
System crash in Windows XP build 2474
System crash in Windows 8 build 7880
System crash in Windows Server 2012 build 8250
System crash in most Insider Preview builds since Windows 10 build 14993
System crash in most server Insider Preview builds since Windows Server build 16203
System crash in Windows 11 build 22000.51 and later
System crash in Windows Server build 22463 and later
References[edit | edit source]
- Microsoft Docs. Interpreting a Bug Check Code, 20 April 2017.