The black screen of death (BlSoD) is a colloquialism used for the black error screen displayed by some operating systems after encountering a critical system error which can cause the system to shut down to prevent damage.
Examples include:
- the "failure" screen in Microsoft Windows 3.x
- the screen displayed by the OS/2 operating system in the event of either a system error from which it cannot recover (a TRAP screen) or a "hard" error in a program running in "full screen" mode (a less serious application failure).
- Kernel panic in Linux.
The black screen of death has been present in all versions of OS/2.
Contents |
The Windows black screen of death
Windows 3.x
In Windows 3.x the black screen of death is the behaviour that occurred when a DOS-based application failed to execute properly. It was often known to occur in connection with attempting certain operations while networking drivers were resident in memory. (Commonly, but not exclusively, it was seen while the Novell NetWare client for DOS, NETX, was loaded.)
The system would switch the display to text mode, but would display nothing, leaving the user looking at an entirely black screen with a blinking caret in the upper left corner. At this point, the user could do nothing but perform a cold reboot to get the system running normally again.
According to Wallace McClure of ASP.net[1], the phrase was originally coined in the summer of 1991 by Ed Brown, a technician with Coca-Cola Company's IT department in Atlanta, GA. He reports that the company was rolling out Windows 3.0 within the Global Marketing group and when the users would attempt to run WordPerfect, they would randomly receive a BlSOD.
Though undocumented, Windows 1.0 and 2.0 also utilizes a black screen of death for the same reasons as shown above.
Later versions of Windows
Windows 95, Windows 98, Windows 2000, Windows ME, Windows XP, Windows Vista, and Windows 7 also display a Black Screen of Death when the operating system cannot boot. This is usually due to a missing file. This also happens when the user enables file compression on all files and the operating system compresses. Often the user must reinstall Windows. If the missing file is critical to the boot process, however, more often than not the boot screen will inform the user of the missing file. If the operating system is compressed, it will not be able to boot, even into safe mode.
In late 2009 several new reports of the Black Screen of Death in Windows XP, Windows Vista, and Windows 7 emerged. At first several claims pointed at a Windows Update, however, it was later recanted by Prevx as an erroreous report. [2] and [3]
Microsoft reported that no security update was causing the issue, and it may be tied to malicious software, or malware. [4] and [5]. In other cases, the black screen of death was replaced with the Blue Screen of Death.
A black screen can also be caused by display driver problems, or selecting a mode that the monitor cannot display, though this may result in a warning on the monitor, or even in damage to a CRT monitor if it is not protected against excessive scan rate. When A display driver is updated the black screen of death appears, but this is really just because it's being updated and it goes away after updating is fully done. Driver updates on dual-display setups can sometimes cause a faux-Black Screen of Death, particularly if the monitors' display orientation is reset and one of the monitors is disabled or powered down. This is easily remedied by checking the secondary monitor.
A black screen with boot failure may also be caused by bios corruption, a need to reset CMOS, or replace the CMOS battery.
The OS/2 black screen of death
In OS/2, a black screen of death is either a "TRAP screen" or "full-screen hard-error VIO pop-up". They switch the display adapter to text mode. The display is 80 columns by 25 rows, with white lettering on a black background and a black border, and uses the text mode font of the display adapter.
TRAP screens
A "TRAP screen" occurs when the kernel encounters an error from which it cannot recover, a system crash. Usually this is a result of faulty (or overclocked) hardware or a hardware malfunction, but it may also result from a software error in either the kernel or a device driver.
The "TRAP screen" contains a dump of the processor registers and stack, and information about the version of the operating system and the actual processor exception that was triggered.
The only actions the user can take in this situation is to perform a soft reboot by pressing Control-Alt-Delete or to perform a system dump by pressing Control-Alt-NumLock twice.
Hard error screens
A "full-screen hard-error VIO pop-up" occurs when a process incurs a "hard" error, either an outright application program crash or a potentially recoverable hard error (such as an attempt to access a floppy disc device where no disc has been inserted into the drive).
The screen is displayed by the "hard error daemon" process, which handles hard errors from all other processes. Technically, the screen is a "VIO pop-up" screen. All processes (except the one that has incurred the error, any that also incur hard errors whilst the first error is being displayed, and any that themselves wish to display a "VIO pop-up" screen) continue to run, and the system continues to operate as normal. The hard error daemon uses a VIO pop-up when either the system has been booted into text mode or the hard error has occurred in a process running in a full-screen session.
The "pop-up screen" contains information about the processor exception that was triggered and the identity of the process.
The user is prompted for the action to be taken, and may choose
- to end the process,
- to display more information (which comprises a dump of the processor registers and stack for that process),
- to retry the operation (if appropriate — I/O errors are retryable, CPU errors are not), or
- to ignore the problem and continue (if appropriate — I/O errors are ignorable, CPU errors are not).
Game consoles
Xbox
When a game crashes while it is loading, a black screen with text such as "An error has occurred, the disc may be dirty or damaged" may appear. This can be seen in Need For Speed Underground 2 if a race fails to load or when Madden NFL 06 fails to load a game.
Wii
The Nintendo Wii can encounter a Black Screen of Death if: A power surge occurs during an update, or update data is written incorrectly. Both of these result in a non-recoverable brick. A different Black Screen of Death can also occur when using homebrew applications, but they do not usually lead to data loss or bricking.
There is another type of Black Screen of Death caused by a defective bluetooth module. This one gets fixed after replacing the defective/broken module.
Nintendo DS
A "black screen of death" can occur at the very beginning of a Metroid Prime Hunters online match. The Nintendo DS's screens turn black and the system must be shut off to fix the problem (which can result in the player's connection history dropping). This is often due to a general system error or a failing connection, which creates an error in the system.
Xbox 360
Later versions of the E74 error uses an entirely black background instead of it having a black background with a hue of very dark green (the latter is considered a Green Screen of Death).
References
- ^ Origin of BSOD - Wallace B. McClure
- ^ http://www.prevx.com/blog/141/Windows-Black-Screen-Root-Cause.html
- ^ http://www.prevx.com/blog/142/Windows-Black-Screen-recap.html
- ^ http://www.msnbc.msn.com/id/34223754/ns/technology_and_science-security/
- ^ http://blogs.technet.com/msrc/archive/2009/12/01/reports-of-issues-with-november-security-updates.aspx
|
||||||||||
This entry is from Wikipedia, the leading user-contributed encyclopedia. It may not have been reviewed by professional editors (see full disclaimer)
