NW Doc

THE BLUE SCREEN OF DEATH.

Users of windows system are sure to have experienced, at one point or another, the terrors of "The Fatal Exception", commonly called the "Blue Screen Of Death", or BSOD. Although the BSOD has largely been thrown onto the software slag heap, in Vista, crashes haven't been totally banished. When windows encounters a condition that compromises safe system operation (i.e. a "bug"), the system halts. This condition is called a 'bug check'. It is also commonly referred to as a system crash, a kernel error, a system fault, or a Stop error. When Windows encounters such a serious error that forces it to stop running, it displays a BLUE SCREEN OF DEATH or just 'lovingly' called BSOD !

In Vista (and Windows 7), unlike XP, where the system was essentially manual, the Windows Error Reporting has been improved & streamlined. and improved in Windows 7 & Vista. One had to follow-up to see if a solution had become available. This was a rather painful process ! In Vista / 7, this entire reporting and follow-up process is automated.
These days a Vista / 7 user is more often likely to see a message as follows : "Microsoft Windows Operating System is not responding." And users are given two possibilities. They can either "Close the program" or "Wait for the program to respond." One waits in the hope that the issue will be resolved; or else then one just closes the program and gets prepared to lose information. Atleast, these messages look less daunting.

he BSODs on the other hand were/are quite traumatic and frustrating, to say the least!

The exact text of a Stop error varies, according to what caused the error. But the format is standardized and is made up of 3 parts:

PART 1.
Symbolic error name: This is the Stop Error message that is given to the OS and corresponds to the Stop Error number that appears.

PART 2.
Troubleshooting recommendations: This text applies to all Stop Errors of that particular type.

PART 3.
Error number and parameters: Its the bugcheck information. The text following the word STOP includes the error number, in hexadecimal notation, and up to four parameters that are typical of this error type.
In general, there are not too many options for any type of recovery. normally, one tries to just "reboot" the pc in the hope that the BSOD occurred because of a rare condition of some driver which was overlooked in coding and testing. But if the BSOD persists, there are some tactics that may be employed to repair the system there are over 250 "documented" BSOD codes.

Take for example, the most common BSOD :
Bugcode 0xA - IRQL_NOT_LESS_OR_EQUAL
This is a fairly common BSOD that occurs when a driver has illegally accessed a memory location while NT is operating at a specific IRQL. This is a driver coding error, akin to trying to access an invalid memory location.
Parameters:
1 - memory location that was referenced
2 - IRQL at time of reference
3 - 0 == read, 1 == write
4 - code addressed which referenced memory
Recovery/Workaround:
There is none. This is a fatal error and is a driver coding error.

Usually when a BSOD occurs, it stays for a second before the PC immediately restarts. This way we are unable to read what is written. To get around it, one has to disable the auto pc-restart option from the StartUp & System Recovery settings. Knowing the error code, can help identify the problem/solution.

Disable UAC. Control Panel > System And Maintenance > System > Advanced System Settings > Advanced tab > Under Startup And Recovery > Click Settings > Clear the Automatically Restart check box > click OK. Enable UAC.
You can download The Blue Screen Of Death (BSOD) Primer from here It opens as a pdf file in your browser. Click on 'save a copy' to save it.
In a lighter vein; If you really fall in love with the BSOD, you can download the BSOD screensaver from here.
To create your own BSOD check here - procedure mentioned applies to XP.
Incidentally Aumha is a very good resource, which gives solutions to most BSOD's.

You can also get your BSOD auto-analysed at the Microsoft® Online Crash Analysis. If you experience a Blue Screen crash event, or Stop error, while using Microsoft Windows, you can upload the error report to this site for analysis. Microsoft will actively analyzes all error reports and prioritizes them based on the number of customers affected by the Stop error covered in the error report and try to determine the cause of the Stop error you have submit.
HOW TO DEBUG MEMORY DUMPS.
To know how to debug Memory Dumps so that you can find out the cause for your BSOD, download and install the Microsoft Debugging Tools. Make certain that your pagefile still resides on the system partition, otherwise WIndows will not be able to save the debug files. There is more information on this here at Majorgeeks and Microsoft.

TROUBLE-SHOOTING WINDOWS VISTA STOP ERRORS / BSOD's.
First & Foremost, see if a System Restore or Last Known Good Configuration is able to resolve this issue.
Else, then run your ant-virus and anti-spyware and your PC Junk/Registry Cleaner. After this, Run the Windows Check Disk Utility.
Then try to identify if you've made any software or hardware change or modification.

In most cases, software is the victim and not the cause of BSOD's. So don't rule out hardware problems. It could be damaged hard disks, defective physical RAM, overheated CPU chips or anything else !

Check if you can see a driver name in the error details. If you can, then simply disabling, removing, or rolling back that driver to an earlier version can help solve that problem. Network interface cards, disk controllers and Video Adapters are the culprits, most often.

Check your memory. Use Windows Memory Diagnostic Tool. Go to Control Panel and type "memory" in the Search box. Under Administrative Tools, click Diagnose Your Computer's Memory Problems. In the Windows Memory Diagnostics Tool, shown here, select one of the options.

Check your system BIOS carefully Is an update available from the manufacturer of the system or motherboard? Check the BIOS documentation carefully; resetting all BIOS options to their defaults can sometimes resolve an issue caused by overtweaking.
Check if you are you low on system resources? Sometimes a critical shortage of Disk Space or RAM can cause BSOD's.
Check if system file has been damaged? Work in Safe Mode, as only the core drivers and services are activated. If your system starts in Safe Mode but not normally, you very likely have a problem driver. Try running Device Manager in Safe Mode and uninstalling the most likely suspect. Or run System Restore in Safe Mode.

For analyzing Crash Dumps, this MSDN print-link , DumpAnalysis & BlueScreenView Links may help you.

WHAT TO DO IF YOU SUSPECT THAT A DRIVER IS CAUSING BSOD's.
The Driver Verifier Manager & the Device Manager have been discussed here in detail. However it is also being briefly touched upon below !
If you suspect that a buggy device driver is at fault for the BSOD's, call upon a lesser known but powerful trouble shooting tool called as the Driver Verifier Manager ! Enter verifier in the search bar and hit enter to bring up Verifier.exe . Run As Administrator. This tool helps you to actually identify the flawed driver.

Now select "Create Standard Settings". Next, select the type of drivers you want to verify. Unsigned Vista Drivers are a likely cause of problems, as they are created for older versions of Windows. Click Next, till completion.
Driver Verifier Manager works in the following manner. Instead of your machine throwing up a undecipherable BSOD at you, at any time, you can make Driver Verifier to stop your computer at start up, with a BSOD which will explain the actual problem, rather accurately! You can then choose to resolve the problem by either updating, rolling back or uninstalling the offending driver.
Please do note that in the rare eventuality the the Driver Verifier Manager does find a non-conforming driver, there could be possibility that it may not be the offending one. So do exercise extreme caution. Regard the identified Driver/s with suspicious and exercise your best judgment in such case.
Having narrowed down to the problematic Driver, you have 3 options : Update, Roll Back or Uninstall the Device Driver.
To do that, open Device Manager. Open the properties dialog box for the device, and use the following buttons on the Driver tab to perform maintenance tasks:

Update Driver : This will start the Hardware Update Wizard.
Roll Back Driver : This will uninstall the most recently updated driver and will roll back your configuration, to the earlier version.
Uninstall Driver : This will uninstall completely the drivers files and registry settings for the selected hardware.
Best to always create a system restore point first.

15 MOST COMMON STOP ERRORS / BSOD's IN WINDOWS.

STOP 0x000000D1 or DRIVER_IRQL_NOT_OR_EQUAL
Probably the most common BSOD ! Occurs when a driver has illegally accessed a memory location while NT is operating at a specific IRQL. This is a driver coding error, akin to trying to access an invalid memory location. Recovery/Workaround:Usually none. But these may help KB810093 , KB316208 & KB810980.

STOP 0x0000000A or IRQL_NOT_LESS_OR_EQUAL
A kernel-mode process or driver attempted to access a memory location without authorization. This Stop error is typically caused by faulty or incompatible hardware or software. The name of the offending device driver often appears in the Stop error and can provide an important clue to solving the problem. If the error message points to a specific device or category of devices, try removing or replacing devices in that category. If this Stop error appears during Setup, suspect an incompatible driver, system service, virus scanner, or backup program. This KB314063 may show you the direction.

STOP 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA
A hardware driver or system service requested data that was not in memory. The cause may be defective physical memory or incompatible software,especially remote control and antivirus programs. If the error occurs immediately after installing a device driver or application, try to use Safe Mode to remove the driver or uninstall the program. For more information, see KB894278 & KB183169.

STOP 0x000000C2 or BAD_POOL_CALLER
A kernel-mode process or driver attempted to perform an illegal memory allocation. The problem can often be traced to a bug in a driver or software. It is also occasionally caused by a failure in a hardware device. For more information, see KB265879.

STOP OX000000ED or UNMOUNTABLE_BOOT_VOLUME
Occurs if Windows if unable to access the volume containing the boot files. But if you get this message while updating TO Vista, check that you have compatible drivers for the disk controller and also re-check the drive cabling, and ensure that it is configured properly. If you're reusing ATA-66 or ATA-100 drivers, make sure you have an 80-connector cable, and not the standard 40-connector IDE cable. See KB297185 and KB315403.

STOP 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED
The Windows kernel detected an illegal or unknown processor instruction, often the result of invalid memory and access violations caused by faulty drivers or hardware devices. The error message often identifies the offending driver or device. If the error occurred immediately after installing a driver or service, try disabling or removing the new addition.

STOP 0x00000024 or NTFS_FILE_SYSTEM
A problem occurred within the NTFS file-system driver. A similar Stop error, 0x23, exists for FAT32 drives. The most likely cause is a hardware failure in a disk or disk controller. Check all physical connections to all hard disks in the system and run CheckDisk. KB228888 will help you.

STOP 0x0000002E or DATA_BUS_ERROR
Failed or defective physical memory (including memory used in video adapters) is the most common cause of this Stop error. The error may also be the result of a corrupted hard disk or a damaged motherboard.

STOP 0x0000003F or NO_MORE_SYSTEM_PTES
Your system ran out of page table entries (PTEs). The cause of this relatively uncommon error may be an out-of-control backup program or a buggy device driver. For more information, see KB256004.

STOP 0x00000077 or KERNEL_STACK_INPAGE_ERROR
The system has attempted to read kernel data from virtual memory (the page file) and failed to find the data at the specified memory address. This Stop Error can be caused by a variety of problems, including defective memory, a malfunctioning hard disk, an improperly configured disk controller or cable, corrupted data, or a virus infection. For additional information, click KB228753.

STOP 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP
Most likely due to a Hardware failure, like defective memory chips, mismatched memory modules, a malfunctioning CPU, or a failure in your fan or power supply are the probable reasons for this BSOD. Can also occur if you have overclocked your CPU. The message gives more details. For more help see KB137539.

STOP 0x000000D8 or DRIVER_USED_EXCESSIVE_PTES
This indicated that a poorly written driver is causing your computer to request large amounts of kernel memory. Troubleshooting suggestions are identical to those found in the STOP 0X3F message. KB256004 will help you

STOP 0X000000EA or THREAD_STUCK_IN_DEVICE_DRIVER
Could occur after you install a new video adapter or an updated (and poorly written) video driver. Replacing the video adapter or using a different video driver could help. See KB293078.

STOP 0XC000021A or STATUS_SYSTEM_PROCESS_TERMINATED
Occurs if there is a serious security problem with Windows. A subsystem, such as Winlogon or the CSRSS is compromised; or due to a mismatch in system files; or if system permissions have been incorrectly modified. A common cause of this problem is some 3rd-party program. Try to identify any new program which you have installed and uninstall it.

STOP 0XC00000221 or STATUS_IMAGE_CHECKSUM_MISMATCH
This indicates a damaged page file; or disk or file corruption; or a faulty hardware. The error will indicate the exact nature and the name of the damaged system file. You may have to use the Windows recovery Environment or a System Restore or Last Known Good Configuration to resolve this issue.