When Blue Screen of Death occurs, Microsoft Windows will displayed STOP Message, each Stop Error is accompanied by a specific error description and an eight-digit hexadecimal number error code and usually only of interest to programmers debugging their code, so it’s not familiar. With running through the following checklist stands a good change of resolving this problem. This checklist is also usually the best approach to trouble shooting some specific error code when Blue Screen of Death / BSOD occurs.

At the top of the Microsoft Windows Blue Screen of Death, we will find the error description, which will be in all uppercase letters with multiple words tied together with underscore characters. For example, see the following BSOD excerpt :

A problem has been detected and Windows has been shut down to prevent damage to your computer.
PAGE_FAULT_IN_NONPAGED_AREA

Immediately following the error description, you’ll find some general troubleshooting steps. In some cases, following these steps will lead you to a solution. (Keep in mind that this same information appears in just about every BSOD.)

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.

After the general troubleshooting information, you’ll find the Technical Information section, which contains the eight-digit hexadecimal number error code. The code is usually accompanied by four error-dependent values enclosed in parentheses. (These values typically aren’t necessary information, but you may want to take note of them.) If a file was directly associated with the problem that caused the BSOD, it will also be listed here. In this case, you can see that the file ati3diag.dll is tied to the problem:

Technical information: *** STOP: 0x00000050 (0x8872A990, 0x00000001, 0x804F35D7, 0x00000000)
*** ati3diag.dll - Address ED80AC55 base at ED88F000, Date Stamp 3dcb24d0

Following the Technical Information section, you’ll see another generic section. This one alerts you to the fact that Windows XP has dumped the contents of system memory to a file on the hard disk:

Beginning dump of physical memory Physical memory dump complete. Contact your system administrator or technical support group for further assistance.

Armed with these details, you can visit Microsoft’s online Help and Support page and search the Knowledge Base for more detailed troubleshooting and solution information.

In the following checklist, common Blue Screen of Death Stop Message Code in Microsoft Windows 2000 / XP.

STOP: 0×00000001
APC_INDEX_MISMATCH
Explanation : This is a kernel internal error. This error could be caused by a mismatch between KeEnterCriticalRegion and KeLeaveCriticalRegion in a file system.

STOP: 0×00000002
DEVICE_QUEUE_NOT_BUSY
Explanation : This is a Windows 2000 character-mode Stop message. It indicates that a device queue was expected to be busy, but was not.

STOP: 0×00000003
INVALID_AFFINITY_SET
Explanation : This is a Windows character-mode Stop message. It indicates a null of incorrect subset affinity.

STOP: 0×00000004
INVALID_DATA_ACCESS_TRAP
Explanation : This is a Windows 2000 character-mode Stop message. It indicates an incorrect data access trap.

STOP: 0×00000005
INVALID_PROCESS_ATTACH_ATTEMPT
Explanation : This is a Windows 2000 character-mode Stop message. It indicates a problem with an owned mutex or a mutex with a process already attached. A specific problem is known to exist with Win XP SP2 and Server 2003 in combination with certain antivirus programs, firewalls, and similar software; see the article linked below for details and current status of a fix from Microsoft.

STOP: 0×00000006
INVALID_PROCESS_DETTACH_ATTEMPT
Explanation : This is a Windows 2000 character-mode Stop message. It indicates a problem with an owned mutex or an unclean APC state.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Netvouz
  • DZone
  • ThisNext
  • MisterWong
  • Wists
  • Slashdot
  • Technorati
  • YahooMyWeb