Blue Screen Windows 7

History[edit]

The term "Blue Screen of Death" originated during OS/2 pre-release development activities at Lattice Inc, the makers of an early Windows and OS/2 C compiler. During porting of Lattice's other tools, developers encountered the stop screen when null pointers were dereferenced either in application code or when unexpectedly passed into system API calls. During reviews of progress and feedback to IBM Austin, the developers described the stop screen as the Blue Screen of Death to denote the screen and the finality of the experience.^{[citation needed]}

BSoDs have been present in all Windows-based operating systems since Windows 3.1. (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.

Format[edit]

Until Windows Server 2012, BSoDs showed white text (CGA color code: 0x0F; HTML color code: #FFFFFF) on a navy blue background (CGA color code: 0x01; HTML color code: #0000AA) with information about current memory values and register values. For visually impaired users, Microsoft has added a utility that allows the user to change a setting in SYSTEM.INI that controls the colors that the BSoD code uses to any of the 16 CGA colors.^{[citation needed]} Doing so requires the edit or addition of the "MessageBackColor=X" and "MessageTextColor=X" lines to the [386enh] section of the SYSTEM.INI, where X is a hexadecimal number from 0 to F corresponding with a color in the CGA 16-color palette. Windows Server 2012 and Windows 8 use a cerulean background instead. (HTML color code: #2067b2)

Windows 95, 98 and Me BSoDs use 80×25 text mode. BSoDs of Windows NT family use 80×50 text mode on a 720×400 screen. Windows XP BSoDs uses the Lucida Console font while the Vista BSoD uses the Consolas font. Windows Server 2012 uses Segoe UIand renders the BSoD at native resolution.

Windows NT[edit]

A stop error as seen in Windows XP

ReactOS, an attempt at creating a free and open-source implementation of a Windows NT-compatible operating system, also features its own BSoD similar to the Windows NT/XP one

In Windows NT family of operating systems, the blue screen of death (officially known as aStop error, and referred to as "bug checks" in the Windows Software development kit andDriver 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 and 2000, 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.^[2]

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" to a "complete dump" which is effectively a copy of the entire contents of physical RAM. The resulting memory dump file may be debugged later, using a kerneldebugger. 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 arandom 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. Windows XP also allows for kernel debugging from the machine that is running the OS. 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

Details[edit]

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:^[3]

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.

Windows Server 2012 and Windows 8 have dropped all of the above in favor of a concise description and an error name. Technical data may be extracted from Windows Event Log.

Windows 9x[edit]

A blue screen of death, as appears onWindows 9x

The blue screen of death frequently occurs in Microsoft's home desktop operating systemsWindows 95, 98, and Me. Here it is usually less serious, but much more common. 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/Me 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.

On the GUI-based members of the MS-DOS-Win95 stream of operating systems and reportedly OS/2, the most common BSoD is the 25x80 screen which is in fact the operating system's way of reporting an interrupt due to a processor exception; it is therefore a more serious form of the Illegal Operation GPF/IPF error boxes seen in a couple of forms on these operating systems. Indeed, the memory address of the error is given and the error type is a hexadecimal number from 00 to 11 (0 to 17 decimal) and is most commonly 0E (Page Fault) or 0D (General Protection Fault), with invalid opcode (06), division by zero (00), and stack fault (0C) being less common and Overflow (04) and the Double Fault (08) forming a third tier of more rare processor exception errors. Assembly language and graphics programmers may see some of the others on occasion but as a rule 0E and 0D are the fatal exceptions that may crop up in everyday use. The error codes are as follows:^[4]

• 00: Division fault
• 01: Corrupted operating system^{[citation needed]}
• 02: Non-Maskable Interrupt
• 03: Hardware malfunction^{[citation needed]}
• 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
• 0F: System board malfunction or corrupted^{[citation needed]}
• 10: Coprocessor Error Fault
• 11: Alignment Check Fault

Common reasons for BSoDs are:

• 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.^[5]

The BSoD can appear if a user ejects removable media while it is being read on 9x/ME. This is particularly common while usingMicrosoft Office: if a user simply wants to view a document, they might eject a floppy disk before exiting the program. Since Microsoft Office always creates a temporary file in the same directory, it will trigger a BSoD upon exiting because it will attempt to delete the file on the disk that is no longer in the drive.

This type of blue screen is no longer seen in Windows NT, 2000, and XP. In the case of these less serious software errors, the program may still crash, but it will not take down the entire operating system with it due to better memory management and decreased legacy support. In these systems, the "true" BSoD is seen only in cases where the entire operating system crashes.

Perhaps the most famous instance of a Windows 9x BSoD occurred during a presentation of a Windows 98 beta by Bill Gates atCOMDEX on April 20, 1998. The demo PC crashed with a BSoD when his assistant (Chris Capossela, who is still working for Microsoft as Corporate VP in the Information Working business unit) connected a scanner to the PC, trying 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."^[6]

Windows CE[edit]

Windows CE 5.0

The simplest version of the blue screen occurs in Windows CE except the versions forPocket PC. The blue screen in Windows CE 3.0 is similar to the one in Windows 95 and 98.

Windows 3.1[edit]

Windows 3.1 was the first version of Windows to use the Blue Screen of Death. In Windows 3.1's 386 enhanced mode, the Blue Screen is also displayed when Control-Alt-Delete is pressed. In a beta version of Windows 3.1, the screen basically looked the same, but it used a black background instead of a blue one.

Similar screens[edit]

OS/2 and MS-DOS suffered the Black Screen of Death. Early builds of Windows Vista displayed the Red Screen of Death after a boot loader error.^[7][8]

Xbox[edit]

An early development version of theMicrosoft Xbox showing a blue critical stop error during a presentation of a racing game at the CeBIT in March 2005

Although the Microsoft Xbox usually shows a Green Screen of Death when a critical error occurs, this model was seen showing a BSOD during the presentation of Forza Motorsportat the CeBIT computer fair in Hannover in March 2005. Additionally the recalled Game Kakuto Chojin displays a BSOD as an error message when the disc is dirty.^{[citation needed]}

Mac OS X 10.5 Leopard[edit]

Leopard features a blue screen but not that of death. Leopard's blue screen was part of a regular boot process in some situations. Some users, upgrading from Mac OS X 10.4 Tiger to Mac OS X 10.5 Leopard and having installed Application Enhancer, experienced a similar experience to a blue screen of death: on booting, the screen remained blue for an indefinite period of time because Application Enhancer's framework was not compatible with the new handlers that Leopard included. However, Apple became aware of the problem and posted a solution.^[9] Nevertheless, Leopard's blue screen was not meant to inform and/or describe an error as the blue screen is just a consequence of the regular boot process.

In the new Finder sidebar, all Windows PCs connected to the same local network of a Mac running Leopard are shown with an icon representing an Old CRT monitor displaying the blue screen of death. ^[10]

iPhone 5s[edit]

In September and October of 2013, mainstream outlets reported iPhone 5s randomly showing a blank blue screen after which reboots occur, as well as random reboots without a blue screen. The Verge attributes the blue screen and reboots to iWorks, a bundled app of iPhone 5s.^[11][12][13] More possible problems for the BSOD are iWork apps, when people multi-task, FaceTime, Safari, Camera, and when people press the home button.^[14] Another issue could be if one uses an app that isn't made for iOS 7 or that the app isn't updated to run the new iPhone 5s's 64 bit processor.

References[edit]

1. ^ Jump up to:^a b "Blue Screen Data". MSDN Library. Microsoft. 9 April 2013. Retrieved 22 August 2013. "When Microsoft Windows encounters a condition that compromises safe system operation, the system halts. This condition is called a bug check. It is also commonly referred to as a system crash, a kernel error, or a Stop error. [...] If no debugger is attached, a blue text screen appears with information about the error. This screen is called a blue screen, a bug check screen, or a Stop screen."
2. Jump up^ Microsoft Windows NT Workstation Resource Kit (1st edition ed.). Redmond, WA: Microsoft Press. 29 October 1996. ISBN 1-57231-343-9.
3. Jump up^ STOP: 0x00000001 (parameter, parameter, parameter, parameter) APC_INDEX_MIS
4. Jump up^ "What Are Fatal Exception Errors". Support. Microsoft. 19 January 2007. Retrieved 16 October 2013.
5. Jump up^ Microsoft Corporation (2000). "Patch Available for "DOS Device in Path Name" Vulnerability". TechNet. Microsoft. Retrieved 4 March 2006.
6. Jump up^ Garmon, Jay (12 April 2007). "Video: Bill Gates, meet the Blue Screen of Death". TechRepublic. CBS Interactive. Retrieved 20 December 2013.
7. Jump up^ Best, Jo (11 May 2005). "Red screen of death?". CNET. CBS Interactive. Retrieved 9 September 2013.
8. Jump up^ Farrell, Nick (3 June 2005). "Microsoft sees red over blue screen of death". The Inquirer. Incisive Media. Retrieved 9 September 
9. 2013.
10. Jump up^ "Blue screen" appears after installing Leopard and restarting
11. Jump up^ Leopard Blue Screen of Death as you can see in CoverFlow

Mengetahui Penyebab Blue Screen Pada Komputer

Posted on19 March 2013 by Ivan Hermawan

Saat sedang asyik-asyiknya bermain dengan game atau sedang mengerjakan tugas dari kantor dan tiba-tiba / mendadak muncul layar biru di monitor, itu menandakan ada kesalahan yang cukup fatal di sistem operasi atau biasanya juga karena kegagalan di sisi hardware.
Blue Screen sering terjadi mungkin karena ada ketidakcocokkan file DLL ataupun bugs di kernel sistem operasi. Kerusakan fisikpun dapat menjadi penyebab terjadinya blue screen / layar biru diantaranya adalah adanya kerusakan di kipas komputer spt yg saya alami, memori yang rusak, mesin mainboard terlalu panas, power supplies yang hampir jebol, dsb.
Jika terjadi blue Screen, biasanya Windows akan menciptakan sebuah file kecil (walaupun sering tidak kita sadari) yg melaporkan kepada kita akan adanya error di sisi mana. Memang secara spontan, blue screen akan mencetak informasi di monitor pada saat terjadinya keadaan tsb, tapi biasanya setelah itu, kita menjadi panik dan bingung yg akhirnya lupa untuk menganalisa apa yang menjadi penyebab terjadi Blue Screen crash tsb, ya mungkin saja munculnya error message tsb diikuti dengan countdown untuk shutdown di Windows supaya jika shutdown maka tidak akan terjadi kerusakan lebih parah misalnya, seluruh CPU bertambah panas karena overheating dan yg paling fatal adalah terjadi korslet listrik di rumah / kantor tempat kita bekerja.

Jika anda cukup ahli dalam menganalisa pesan yang ditampilkan saat terjadi blue screen, sebuah tool bagus bisa membantu menyimpan informasi blue screen sehingga dapat membantu kita menganalisa dan menjawab mengapa terjadi blue screen. Tool ini diberi nama BlueScreenView.
Dapat diunduh dan bisa dipakai secara instant tanpa proses instalasi.
BlueScreenView dapat berjalan di segala lingkungan Windows > Windows XP/Server 2003/Server 2008/Vista/7. Silahkan menganalisa kerusakan sistem komputer dengan tool ini.

Jenis-jenis Blue Screen

Arti Error Blue Screen Windows :

1. IRQL_NOT_LESS_OR_EQUAL (0X0000000A)

Error ini yang paling sering muncul pada saat terjadi Blue Screen.
Pesan kesalahan ini biasanya disebabkan kerena ada ketidakcocokan driver yang terinstall di komputer.
Penyebabnya:
- Driver yang bentrok atau tidak cocok
- Permasalahan pada Video Card, hal ini mencakup video card yang di overclock melebihi batas atau Anda baru berganti Video card dan Anda belum menguninstall driver Video card lama dari chipset berbeda
- Permasalahan pada Audio Card, meliputi kesalahan konfigurasi atau bug dalam driver sound card

2. NTFS_FILE_SYSTEM atau FAT_FILE_SYSTEM (0X00000024) atau (0X00000023)

pesan error ini setidaknya sudah sedikit memberikan gambaran di mana kerusakan berada, yaitu ada di partisi atau filesystemnya tetapi bukan di harddisknya.
Kita bisa melakukan pengecekan dengan memeriksa kabel SATA atau PATA atau bisa mengecek partisi dengan tool chkdsk.

3. UNEXPECTED_KERNEL_MODE_TRAP (0X0000007F)

Bila Anda mendapatkan pesan error seperti ini, dapat disebabkan karena:
- Overclock Hardware yang berlebihan
- Komponen komputer yang terlalu panas
- BIOS yang korup
- Memory dan CPU yang surim

4. DATA_BUS_ERROR

Pesan error ini disebabkan karena adanya kemungkinan bahwa memory atau slot memory di motherboard rusak.

5. PAGE_FAULT_IN_NONPAGED_AREA

Pesan error ini disebabkan karena adanya kerusakan hardware, termasuk memory utama, memory video card, atau memory di processor (L2 Cache)

6. INACCESSIBLE_BOOT_DEVICE

Pesan error ini disebabkan karena adanya kesalahan dalam konfigurasi jumper harddisk yang salah, virus boot sector, driver IDE controller yang salah, atau kesalahan driver chipset.

7. VIDEO_DRIVER_INIT_FAILURE

Pesan error ini disebabkan karena adanya Kesalahan terjadi pada instalasi driver video card yang kurang sempurna, restart pada saat instalasi atau juga dapat terjadi karena kesalahan dalam instalasi driver.

8. BAD_POOL_CALLER

Pesan error ini disebabkan karena adanya Kesalahan ini dapat terjadi karena kesalahan atau driver yang tidak kompatibel. Sering terjadi saat melakukan instalasi XP dari upgrade, atau bukan dari instalasi baru.

9. PEN_LIST_CORRUPT

Pesan error ini disebabkan karena adanya kerusakan RAM

10. MACHINE_CHECK_EXCEPTION

Pesan error ini disebabkan oleh cacatnya CPU, atau yang di overclock secara agresif, serta power supply yang kekurangan daya atau rusak.

Tips cara Memperbaiki Blue Screen Of Death pada Komputer :

1. Periksa Kondisi Komputer Secara Umum
Sebelum melakukan troubleshooting lebih lanjut, langkah pertama yang harus kita lakukan adalah memeriksa kondisi komputer secara umum, diantaranya adalah :
Periksa kebersihan didalam Casing CPU. Bersihkan debu dan kotoran lainnya bisa denga kuas dan vacuum cleaner, bila perlu siapkan electrical contact cleaner untuk membersihkan Motherboard.
Periksa kondisi suhu tiap-tiap komponen seperti Power Supply ( pastikan fan berputar secara normal), VGA Card dan Heatsink Processor.
Pastikan berbagai komponen (seperti RAM, VGA Card, konektor IDE / SATA, konektor Power Supply, dll) sudah terpasang dengan benar, untuk memastikannya bisa dengan mencabut dan memasangnya kembali.
Bila Anda baru saja memasang komponen hardware baru (misal VGA Card), cabut aja dulu dan coba jalankan komputer kali aja peyebab BlueScreen dari kompone tersebut.

2. Gunakan Mode “Safe Mode “
Langkah selanjutnya adalah menjalankan Windows dalam Mode “Safe Mode” yang merupakan salah satu pilihan pada menu Advance Boot Option Windows XP, yaitu dengan menekan berulang-ulang tombol F8 pada saat sistem akan melakukan startup. Setelah Windows berhasil masuk ke Safe Mode, lakukan beberapa troubleshooting berikut:
Bersihkan hardisk dari antivirus, mallware & spyware dengan cara menjalankan program virus scanner , misalnya Norman Anti Mallware.
Uninstall Driver yang bermasalah, caranya dengan masuk ke jendela Computer Management klik Device Manager dan carilah komponen yang ada tanda serunya, atau driver komponen yang baru saja diinstall atau diupdate.
Bila perlu uninstall dulu program antivirus yang terpasang, bila kondisi kondisi komputer sudah normal bisa diinstall lagi dan pastikan database engine-ya selalu up to date.
Kita juga bisa menggunakan utility “System Restore” untuk mengembalikan setingan computer ke kondisi sebelumnya. Caranya klik Start, All Program , Accessories, System Tools, System Restore.

3. Periksa Kondisi Hardisk
Kondisi hardisk yang bad juga bisa mengakibatkan terjadinya BlueScreen, oleh karena itu periksa kondisi hardisk dengan menjalankan perintah CHKDSK. Jalankan juga program Defragmentasi Hardisk untuk memastikan hardisk bekerja secara optimal.

4. Periksa Kondisi Memori / RAM
Periksa kondisi Memori / RAM, pastikan telah terpasang dengan benar, dan jalankan program utuk memeriksa kondisi Memori misalnya “Windows Memory Diagnostic”.

5. Repair Sistem Operasi Windows.
Adakalanya BlueScreen terjadi karena ada beberapa file Windows yang corrupt, untuk mengatasinya cara yang paling gampang adalah dengan melakukan Repair pada sistem operasi Windows kesayangan Anda tersebut.

6. Gunakanlah Tools untuk menganalisa Penyebab Terjadinya BlueScreen.
Carilah Dump File pada hardisk komputer yang mengalami BlueScreen, biasanya di C:\WINDOWS\Minidump lalu copy ke komputer kita dan jalankan aplikasi WhoCrashed atau BlueScreenView untuk mencari peyebab BlueScreen.