شاشة الموت الزرقاء
شاشة الموت الزرقاء بالإنجلزية Blue screen of death مصطلح يطلق على الشاشة الزرقاء التي يظهرها ويندوز عند حدوث خطأ في النظام.[1][2][3] – is a critical error screen displayed by the Microsoft Windows operating systems when a serious system error occurs. It indicates a system crash, in which the operating system reaches a critical condition where it can no longer operate safely.
Possible issues that may cause a BSoD include hardware failures, an issue with or without a device driver, viruses, malware and other factors such as intentional user action.
التاريخ
 Videos of Windows 1.01 booting on an incorrect DOS version | |
 Windows 1.0 BSOD (Incorrect DOS Version): Short version, showing a failed Windows startup | |
| Windows 1.01 Blue Screen of Death: Long version, showing installation of MS-DOS 6 and Windows 1.01, and the failed startup of Windows |
Blue screens of death have been around since the first beta release of Windows 1.0; if Windows detects a newer DOS version than expected, the error message "Incorrect DOS version" alongside other text messages detailing what check failed to pass would be appended to the boot screen before starting normally.[4] This function still exists in the final release (version 1.01); however, due to the remaining detailed text messages being removed, the screen mostly prints out random characters instead.[4] This is not a crash screen, however; upon crashing, Windows 1.0 would simply lock up or exit to DOS. This behavior is also present in Windows 2.0 and Windows 2.1.
Windows 3.0 uses a text-mode screen for displaying important system messages, usually from digital device drivers in 386 Enhanced Mode or other situations where a program could not run. Windows 3.1 changed the color of this screen from black to blue. It also displays a blue screen when the user presses the Ctrl+Alt+Delete key combination to bring up a rudimentary task manager, reserved for quitting any unresponsive programs if they are available. As with previous versions, Windows 3.x exits to DOS if an error condition is severe enough.
The first blue screen of death appeared in Windows NT 3.1[5] (the first version of the Windows NT family, released in 1993), and later appeared on all Windows operating systems released afterwards. The error screens started with *** STOP: in its earlier iterations, hence it became known as a "stop error."
BSoDs can be caused by poorly written device drivers or malfunctioning hardware,[6] such as faulty memory, power supply trouble, overheating of components or hardware running beyond its specification limits. In the Windows 9x operating systems, incompatible DLLs or bugs in the operating system kernel could also cause BSoDs.[7] Because of the instability and lack of memory protection in Windows 9x OSes, BSoDs were much more common.
BSoDs are not included in the Windows Embedded Compact (formerly known as Windows CE) line of embedded operating systems.[8]
Attribution
.png&filetimestamp=20241231152951&)
.png&filetimestamp=20241231152951){kind=link}
On September 4, 2014, several online journals such as Business Insider,[9] DailyTech,[10] Engadget,[11] Gizmodo,[12] Lifehacker,[13] Neowin,[14] Softpedia,[15] TechSpot,[16] Boy Genius Report (BGR), The Register,[17] and The Verge,[18] as well as print and non-English sources like PC Authority and Austrian tech site FutureZone[19] all attributed the creation of the Blue Screen of Death to Steve Ballmer, Microsoft's former CEO. Their articles cited a blog post by Microsoft employee Raymond Chen entitled "Who wrote the text for the Ctrl+Alt+Del dialog in Windows 3.1?",[20] specifically focusing on the creation of the first rudimentary task manager in Windows 3.x. This aforementioned task manager shared some visual similarities with a BSOD, with Ballmer writing the messages that appeared on the screen.[20]
Chen had to address this widespread misinformation in a blog post on September 9, 2014. In his post, he was scathing on his evaluation of major tech news sites that had picked up on the incorrect story and performed poor or non-existent research that demonstrated complete ignorance of his original account. He indicated that, in addition to the faulty base story, over half a dozen significant sites had included other embellished or invented details in their stories, including incorrectly naming Chen as a Microsoft executive, treating Chen as an "official company spokesperson", and using unrelated images from Windows NT or Windows 95 as illustrations. In addition, he also pointed out a very special mention for the worst single distortion out of any misinformations, which belonged to BGR (Boy Genius Report), who "fabricated a scenario and posited it as real" in a rhetorical question to readers. He also found that several sources had conflated the creation of the BSoD with the fact that they occur, thus inverting cause and effect by implying that the invention of BSoDs caused fatal errors to occur instead of their actual, helpful function of giving the user information about a fatal error after the system has already become unrecoverable (such incorrect sources transitively blamed Ballmer for the existence of all fatal crashes in Windows).[21] Chen would later follow this up with a blog post the day after his initial complaint, claiming responsibility for revising the BSoD in Windows 95. His post said in detail that he was the one who "sort of" created the BSoD in its first modern incarnation in Windows 95.[22]
On the other hand, the Blue Screen of Death (also known as a Stop error) in the Windows NT family was not based on the rudimentary task manager screen of Windows 3.x, but was actually designed by Microsoft developer John Vert, according to former Microsoft employee Dave Plummer.[23] Additionally, Vert has also stated the reason why Stop error screens were assigned the color blue was because the universal color palette of the video hardware at that time was very rudimentary and he personally used a MIPS OS box and SlickEdit for programming so that the firmware and editor both displayed white text on a blue background, making it for a more consistent programming experience.[23]
الصيغ
ويندوز فيستا
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
KMODE_EXCEPTION_NOT_HANDLED
If this is the first time you've seen this error screen،
restart your computer. If this screen appears again، follow
these steps:
STEP 1: Check to make sure any new hardware or software is properly installed.
If this is a new installation، ask your hardware or software manufacturer for
any Windows updates you might need.
STEP 2: If problems continue، disable or remove any newly installed hardware
or software، or try to run Chkdsk after a restart of the computer.
Technical information:
STOP: 0x0000001E (0x80000003، 0xBFC0304، 0x0000000، 0x0000001)
You can now press Ctrl+Alt+Delete to restart the computer _
ويندوز اكس بي
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
PFN_LIST_CORRUPT
If this is the first time you've seen this 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.
If this is a new installation، ask your hardware or software manufacturer
for any 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: 0x0000004e (0x00000099، 0x00000000، 0x00000000، 0x00000000)
Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further
assistance.
A problem has been detected and Windows has been shut down to prevent damage
to your computer.
An attempt was made to write to read-only memory.
If this is the first time you've seen this 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.
If this is a new installation، ask your hardware or software manufacturer
for any 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: 0X000000BE (0XF90A0905، 0X01CD5121، 0X8055616C، 0X0000000A)
*** NDIS.sys – Address F90A0905 base at F9083000، Datestamp 41107ec3
Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further
assistance.
ويندوز ميلينيوم
An error has occurred. To continue:
Press Enter to return to Windows, or Press CTRL+ALT+DEL to restart
your computer. If you do this, you will lose any unsaved information
in all open applications.
*** Error: 0D : 0157 : 00005ED7
Press any key to continue _
ويندوز 2000
STOP: c000026c {Unable to Load Device Driver}
\SystemRoot\System32\Drivers\Fdc.SYS device driver could not be loaded.
Error Status was 0xc000012f
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.
If this is a new installation، ask your hardware or software manufacturer
for any Windows 2000 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.
Refer to your Getting Started manual for more information on
troubleshooting Stop errors.
ويندوز أن تي 3 و 4
*** STOP: 0x0000000A (0x00000000، 0x00000002، 0x00000000، 8038c510)
IRQL_NOT_LESS_OR_EQUAL*** Address 8038c510 has base at 8038c000 - Ntfs.sys
CPUID:AuthenticAMD irq1:1f SYSVER 0xf0000565
Dll Base DateStmp - Name Dll Base DateStmp - Name
80100000 336546bf - ntoskrnl.exe 80010000 33247f88 - hal.dll
80000100 334d3a53 - atapi.sys 80007000 33248043 - SCSIPORT.SYS
802ab000 33013e6b - epst.mpd 802b5000 336016a2 - Disk.sys
802b9000 336015af - CLASS2.SYS 8038c000 3356d637 - Ntfs.sys
802bd000 33d844be - Floppy.sys 803e4000 33d84553 - viaide.sys
f9328000 31ec6c8d - Siwvid.sys f95c9000 31ec6c99 - Null.SYS
f9468000 31ed868b - KSecDD.sys f95cb000 335e60cf - Beep.SYS
f9348000 335bc82a - i8024prt.sys f95cb000 3373c39d - ctrl2cap.SYS
f947c000 31ec6c94 - kbdclass.sys f9474000 3324806f - mouclass.sys
f9370000 33248011 - VIDEOPORT.SYS fe9d7000 3370e7b9 - NDIS.SYS
f9480000 31ec6c6d - vga.sys f93b0000 332480dd - Msfs.SYS
f90f0000 332480d0 - Npfs.sys fe957000 3356da41 - ati.sys
a0000000 335157ac - win32k.sys fe914000 334ea144 - ati.dll
fe0c9000 335bd30e - Fastfat.SYS fe110000 31ec6c9b - Parport.SYS
fe108000 31ec6c9b - Serial.sys f93b4000 31ec7c9d - ParVdm.SYS
f9050000 332480ab - Parallel.sys
Address dword dump Build [1314] - Name
801afc24 80149905 80149905 ff8e6b8c 80129c2c ff8e6b94 8025c000 - Ntfs.SYS
801afd24 80129c2c 80129c2c ff8e6b94 00000000 ff8e6b94 80100000 - ntoskrnl.exe
801afd34 801240f2 80124f02 ff8e6cf4 ff8e6d60 ff8e6c58 80100000 - ntoskrnl.exe
801afd54 80124a16 80124a16 ff8e6f60 ff8e6c3c 8015ac7e 80100000 - ntoskrnl.exe
801afd64 8015ac7e 8015ac7e ff8e6cf4 ff8e6f60 ff8e6c58 80100000 - ntoskrnl.exe
801afc70 80129bda 80129bda 00000000 80088000 80106f60 80100000 - ntoskrnl.exe
Restart and set the recovery options in the system control panel
or the /CRASHDEBUG system start option. If this message reappears،
contact your system administrator or technical support group.
ويندوز 98 وويندوز 95
A fatal exception 0E has occurred at 0157:BF7FF831. The current
application will be terminated.
* Press any key to terminate the current application.
* Press CTRL+ALT+DEL again to restart your computer. You will
lose any unsaved information in all applications.
Press any key to continue _
انظر أيضاً
- Screens of death
- Red Ring of Death
- Hang (computing)
- Machine-check exception (MCE)
- Windows Hardware Error Architecture (WHEA)
المراجع
- ^ "Troubleshoot blue screen errors". Support. Microsoft. 2019-04-10. Archived from the original on 2019-09-04.
- ^ "Understanding Bugchecks". TECHCOMMUNITY.MICROSOFT.COM (in الإنجليزية). 2019-03-16. Retrieved 2023-03-12.
- ^ "Blue screen data - Windows drivers". Microsoft Learn (in الإنجليزية الأمريكية). 2023-01-04. Retrieved 2023-03-21.
- ^ أ ب "Why does Windows 1.01 crash at the splash screen?". Retro Computing. August 30, 2021.
In the final release of Windows, these detailed messages were hastily removed. The code that would print them, however, was not, and this is what produces the garbage output.
- ^ Chen, Raymond (September 26, 2017). "Who implemented the Windows NT blue screen of death?". The Old New Thing. Microsoft. Archived from the original on March 15, 2019. Retrieved October 1, 2021.
- ^ Wilson, Michelle (July 25, 2019). "What is the Blue Screen of Death in Windows 10 and How to Fix it?". HP. Retrieved October 1, 2021.
- ^ Cepero, Robert (May 17, 2019). "Blue Screen of Death: Causes and Fixes". Bleuwire. Retrieved October 1, 2021.
- ^ "Blue screen - Microsoft Windows Embedded Compact VErsion 7.00 (Build 2864)". social.msdn.microsoft.com. Retrieved 2023-01-18.
- ^ Smith, Dave (September 4, 2014). "Steve Ballmer Wrote The Blue Screen Of Death". Business Insider. Business Insider Inc. Archived from the original on September 8, 2014. Retrieved September 10, 2014.
- ^ Mick, Jason (September 4, 2014). "Microsoft Exec Reveals Steve Ballmer Created Original Blue Screen of Death Message". Daily Tech. DailyTech LLC. Archived from the original on August 20, 2015. Retrieved September 10, 2014.
- ^ Fingas, Jon (September 4, 2014). "Steve Ballmer wrote Windows' first Ctrl-Alt-Delete message (updated)". Engadget. AOL. Archived from the original on September 9, 2014. Retrieved September 10, 2014.
- ^ Condliffe, Jamie (September 4, 2014). "Steve Ballmer Wrote the Blue Screen of Death". Gizmodo. Gizmodo Media Group. Archived from the original on September 11, 2014. Retrieved September 10, 2014.
- ^ Kidman, Alex (September 5, 2014). "Steve Ballmer Wrote The BSOD, So Stop Slacking Off". Lifehacker. Allure Media. Archived from the original on September 10, 2014. Retrieved September 10, 2014.
- ^ Sams, Brad (September 4, 2014). "Steve Ballmer wrote the BSOD text". Neowin. Neowin LLC. Archived from the original on September 8, 2014. Retrieved September 10, 2014.
- ^ Popa, Bogdan (September 4, 2014). "Steve Ballmer Himself Created the First Blue Screen of Death Text". Softpedia. SoftNews SRL. Archived from the original on September 10, 2014. Retrieved September 10, 2014.
- ^ Schiesser, Tim (September 4, 2014). "The original Blue Screen of Death was written by Steve Ballmer". TechSpot. Archived from the original on September 10, 2014. Retrieved September 10, 2014.
- ^ Sharwood, Simon (September 4, 2014). "Ballmer PERSONALLY wrote Windows' Blue Screen of Death text". The Register. Archived from the original on September 8, 2014. Retrieved September 10, 2014.
- ^ Warren, Tom (September 4, 2014). "Steve Ballmer wrote the Blue Screen of Death message". The Verge. Vox Media. Archived from the original on September 7, 2014. Retrieved September 10, 2014.
- ^ "Steve Ballmer schrieb "Blue Screen of Death"-Botschaft". futurezone.at. September 4, 2014. Archived from the original on December 2, 2020. Retrieved September 3, 2024.
- ^ أ ب Chen, Raymond (September 2, 2014). "Who wrote the text for the Ctrl+Alt+Del dialog in Windows 3.1?". The Old New Thing. Microsoft. Archived from the original on November 15, 2020. Retrieved November 13, 2020.
- ^ Chen, Raymond (September 9, 2014). "Steve Ballmer did not write the text for the blue screen of death". The Old New Thing. Microsoft. Archived from the original on October 25, 2020. Retrieved November 13, 2020.
- ^ Chen, Raymond (September 10, 2014). "I wrote the original blue screen of death, sort of". The Old New Thing. Microsoft. Retrieved September 3, 2024.
- ^ أ ب Plummer, David (2021-01-30). "Why are Bluescreens Blue?". YouTube. Retrieved 2023-07-07.
وصلات خارجية
- Bug Check Code Reference
- SysInternals BlueScreen Screen Saver v3.2
- Blue Screen of Death. Archived مارس 31, 2022 at the Wayback Machine on MalWiki.