Blue Screen of Death
|This article needs additional citations for verification. (October 2013) (Learn how and when to remove this template message)|
A stop error, better known as a Blue Screen of Death (also known as a blue screen or BSoD) is an error screen displayed on a Windows computer system after a fatal system error, also known as a system crash: when the operating system reaches a condition where it can no longer operate safely.
BSoDs have been present in Windows NT 3.1 (the first version of the Windows NT family, released in 1993) and all Windows operating systems released afterwards. (See History of Microsoft Windows.) BSoDs can be caused by poorly written device drivers or malfunctioning hardware, such as faulty memory, power supply issues, overheating of components, or hardware running beyond its specification limits. In the Windows 9x era, incompatible DLLs or bugs in the operating system kernel could also cause BSoDs. Because of the instability and lack of memory protection in Windows 9x, BSoDs were much more common.
On 4 September 2014, several online journals, including Business Insider, DailyTech, Engadget, Gizmodo, Lifehacker, Neowin, Softpedia, TechSpot, The Register, and The Verge attributed the creation of the Blue Screen of Death to Microsoft's former CEO Steve Ballmer while citing a source that did not say that: An article by Raymond Chen (Microsoft employee) titled "Who wrote the text for the Ctrl+Alt+Del dialog in Windows 3.1?" The article was about the creation of the first rudimentary task manager in Windows 3.x, which shared visual similarities with a BSoD. In a follow up on 9 September 2014, Raymond Chen complained about this widespread mistake, claimed responsibility for revising the BSoD in Windows 95 and panned BGR.com for having "entirely fabricated a scenario and posited it as real". Engadget later updated its article to correct the mistake.
Until Windows Server 2012, BSoDs showed silver text on a navy blue background with information about current memory values and register values. Windows Server 2012, Windows 8 and Windows 10 use a cerulean background instead.
Windows 95, 98 and ME BSoDs use 80×25 text mode. BSoDs in the Windows NT family use 80×50 text mode on a 720×400 screen. Windows XP BSoDs use the Lucida Console font while the Windows Vista and 7 BSoD uses the Consolas font. Windows 8, Windows Server 2012 use Segoe UI and attempt to render the BSoD at native resolution, otherwise defaulting to 640x480.
In Windows NT family of operating systems, the blue screen of death (officially known as a stop error and referred to as "bug check" in the Windows software development kit and driver development kit documentation) occurs when the kernel or a driver running in kernel mode encounters an error from which it cannot recover. This is usually caused by an illegal operation being performed. The only safe action the operating system can take in this situation is to restart the computer. As a result, data may be lost, as users are not given an opportunity to save data that has not yet been saved to the hard drive.
The text on the error screen contains the code of the error and its symbolic name (e.g. "0x0000001E, KMODE_EXCEPTION_NOT_HANDLED") along with four error-dependent values in parentheses that are there to help software engineers fix the problem that occurred. Depending on the error code, it may display the address where the problem occurred, along with the driver which is loaded at that address. Under Windows NT, the second and third sections of the screen may contain information on all loaded drivers and a stack dump, respectively. The driver information is in three columns; the first lists the base address of the driver, the second lists the driver's creation date (as a Unix timestamp), and the third lists the name of the driver.
By default, Windows will create a memory dump file when a stop error occurs. Depending on the OS version, there may be several formats this can be saved in, ranging from a 64kB "minidump" (introduced in Windows 2000) to a "complete dump" which is effectively a copy of the entire contents of physical memory (RAM). The resulting memory dump file may be debugged later, using a kernel debugger. For Windows WinDBG or KD debuggers from Debugging Tools for Windows are used. A debugger is necessary to obtain a stack trace, and may be required to ascertain the true cause of the problem; as the information on-screen is limited and thus possibly misleading, it may hide the true source of the error. By default, Windows XP is configured to save only a 64kB minidump when it encounters a stop error, and to then automatically reboot the computer. Because this process happens very quickly, the blue screen may be seen only for an instant or not at all. Users have sometimes noted this as a random reboot rather than a traditional stop error, and are only aware of an issue after Windows reboots and displays a notification that it has recovered from a serious error. This happens only when the computer has a function called "Auto Restart" enabled, which can be disabled in the Control Panel which in turn shows the stop error.
Microsoft Windows can also be configured to send live debugging information to a kernel debugger running on a separate computer. If a stop error is encountered while a live kernel debugger is attached to the system, Windows will halt execution and cause the debugger to break in, rather than displaying the BSoD. The debugger can then be used to examine the contents of memory and determine the source of the problem.
A BSoD can also be caused by a critical boot loader error, where the operating system is unable to access the boot partition due to incorrect storage drivers, a damaged file system or similar problems. The error code in this situation is STOP 0x0000007B (INACCESSIBLE_BOOT_DEVICE). In such cases, there is no memory dump saved. Since the system is unable to boot from the hard drive in this situation, correction of the problem often requires using the repair tools found on the Windows installation disc.
Before Windows Server 2012, each BSoD displayed an error name in uppercase (e.g. APC_INDEX_MISMATCH), a hexadecimal error number (e.g. 0x00000001) and four parameters. The last two are shown together in the following format:
error code (parameter 1, parameter 2, parameter 3, parameter 4) error name
Depending on the error number and its nature, all, some, or even none of the parameters contain data pertaining to what went wrong, and/or where it happened. In addition, the error screens showed four paragraphs of general explanation and advice and may have included other technical data such the file name of the culprit and memory addresses.
With the release of Windows Server 2012, the BSoD was changed, removing all of the above in favor of the error name, and a concise description. Windows 8 added a sad emoticon as well. The hexadecimal error code and parameters can still be found in the Windows Event Log or in memory dumps. Windows 10 Build 14393 added a QR code for quick troubleshooting.
The blue screen of death frequently occurs in Microsoft's home desktop operating systems Windows 95, 98, and ME. In these operating systems, the BSoD is the main way for virtual device drivers to report errors to the user. It is internally referred to by the name of "
_VWIN32_FaultPopup". A Windows 9x BSoD gives the user the option either to restart or continue. However, VxDs do not display BSoDs frivolously — they usually indicate a problem that cannot be fixed without restarting the computer, and hence after a BSoD is displayed the system is usually unstable or unresponsive.
The most common BSoD is on an 80×25 screen which is the operating system's way of reporting an interrupt caused by a processor exception; it is a more serious form of the general protection fault dialog boxes. The memory address of the error is given and the error type is a hexadecimal number from 00 to 11 (0 to 17 decimal). The error codes are as follows:
- 00: Division fault
- 02: Non-Maskable Interrupt
- 04: Overflow Trap
- 05: Bounds Check Fault
- 06: Invalid Opcode Fault
- 07: "Coprocessor Not Available" Fault
- 08: Double Fault
- 09: Coprocessor Segment Overrun
- 0A: Invalid Task State Segment Fault
- 0B: Not Present Fault
- 0C: Stack Fault
- 0D: General Protection Fault
- 0E: Page Fault
- 10: Coprocessor Error Fault
- 11: Alignment Check Fault
Reasons for BSoDs include:
- Problems that occur with incompatible versions of DLLs: Windows loads these DLLs into memory when they are needed by application programs; if versions are changed, the next time an application loads the DLL it may be different from what the application expects. These incompatibilities increase over time as more new software is installed, and is one of the main reasons why a freshly-installed copy of Windows is more stable than an "old" one.
- Faulty or poorly written device drivers
- Hardware incompatibilities
Damaged hardware may also cause a BSoD.
In Windows 95 and 98, a BSoD occurs when the system attempts to access the file "
c:\con\con" or "
c:\aux\aux" on the hard drive. This could be inserted on a website to crash visitors' machines. On 16 March 2000, Microsoft released a security update to resolve this issue.
A famous instance of a Windows 9x BSoD occurred during a presentation of a Windows 98 Beta by Bill Gates at COMDEX on April 20, 1998: The demo PC crashed with a BSoD when his assistant, Chris Capossela, connected a scanner to the PC to demonstrate Windows 98's support for Plug and Play devices. This event brought thunderous applause from the crowd and Gates replied after a nervous pause: "That must be why we're not shipping Windows 98 yet."
Windows Phones running Windows Mobile 10 Beta also features a Blue Screen of Death with a white sad smiley on it. It is caused by an update error in the system, which can be fixed by downgrading from Windows 10 Mobile Beta to Windows Phone 8.1 using the official Windows Phone Recovery Tool in the official Microsoft website.
- Smith, Dave (4 September 2014). "Steve Ballmer Wrote The Blue Screen Of Death". Business Insider. Business Insider Inc. Retrieved 10 September 2014.
- Mick, Jason (4 September 2014). "Microsoft Exec Reveals Steve Ballmer Created Original Blue Screen of Death Message". Daily Tech. DailyTech LLC. Retrieved 10 September 2014.
- Fingas, Jon (4 September 2014). "Steve Ballmer wrote Windows' first Ctrl-Alt-Delete message (updated)". Engadget. AOL. Retrieved 10 September 2014.
- Condliffe, Jamie (4 September 2014). "Steve Ballmer Wrote the Blue Screen of Death". Gizmodo. Gawker. Retrieved 10 September 2014.
- Kidman, Alex (5 September 2014). "Steve Ballmer Wrote The BSOD, So Stop Slacking Off". Gizmodo. Allure Media. Retrieved 10 September 2014.
- Sams, Brad (4 September 2014). "Steve Ballmer wrote the BSOD text". Neowin. Neowin LLC. Retrieved 10 September 2014.
- Popa, Bogdan (4 September 2014). "Steve Ballmer Himself Created the First Blue Screen of Death Text". Softpedia. SoftNews SRL. Retrieved 10 September 2014.
- Schiesser, Tim (4 September 2014). "The original Blue Screen of Death was written by Steve Ballmer". TechSpot. Retrieved 10 September 2014.
- Sharwood, Simon (4 September 2014). "Ballmer PERSONALLY wrote Windows' Blue Screen of Death text". The Register. Retrieved 10 September 2014.
- Warren, Tom (4 September 2014). "Steve Ballmer wrote the Blue Screen of Death message". The Verge. Vox Media. Retrieved 10 September 2014.
- Chen, Raymond (2 September 2014). "Who wrote the text for the Ctrl+Alt+Del dialog in Windows 3.1?". The Old New Thing. Microsoft. Retrieved 10 September 2014.
- Chen, Raymond (9 September 2014). "Steve Ballmer did not write the text for the blue screen of death". The Old New Thing. Microsoft. Retrieved 10 September 2014.
- Microsoft Windows NT Workstation Resource Kit (1st ed.). Redmond, WA: Microsoft Press. 29 October 1996. ISBN 1-57231-343-9.
- STOP: 0x00000001 (parameter, parameter, parameter, parameter) APC_INDEX_MIS
- "What Are Fatal Exception Errors". Support. Microsoft. 19 January 2007. Retrieved 16 October 2013.
- Microsoft Corporation (2000). "Patch Available for "DOS Device in Path Name" Vulnerability". TechNet. Microsoft. Retrieved 4 March 2006.
- Garmon, Jay (12 April 2007). "Video: Bill Gates, meet the Blue Screen of Death". TechRepublic. CBS Interactive. Retrieved 20 December 2013.
- "Advanced Configuration and Power Interface Errors on Red Screen". Support (1.3 ed.). Microsoft. 10 August 2007. Retrieved 19 July 2014.
- Best, Jo (11 May 2005). "Red screen of death?". CNET. CBS Interactive. Retrieved 9 September 2013.
- Farrell, Nick (3 June 2005). "Microsoft sees red over blue screen of death". The Inquirer. Incisive Media. Retrieved 9 September 2013.
- "Behold the Windows 10 GSOD -- Green Screen of Death". BetaNews. 2016-12-29. Retrieved 2017-01-13.
- Warren, Tom (December 29, 2016). "Windows 10 testers will now get a Green Screen of Death". The Verge. Vox Media. Retrieved 1 February 2017.
|Wikimedia Commons has media related to:|