Doctor

NOTE: When a STOP message occurs, Windows can create a debug file for very detailed analysis. To do this, it needs a workspace equal to the amount of physical RAM you have installed. If you resize your Win XP pagefile minimum to less than the size of your physical RAM, you will get an advisory message that your system may not be able to create a debugging information file if a STOP error occurs.My advice is to go ahead with this change if you want, but simply remember the limitation so that you can change it back if you need to troubleshoot STOP messages. Some general troubleshooting principles are suggested in the Resource Kit for approaching STOP messages overall.

Troubleshooting Stop messages: General Strategies
Troubleshooting Specific Stop Messages
MSDN List of WinXP STOP Messages (If not a complete list, this one certainly is extensive!)
Blue Screen Preparation Before Contacting Microsoft {KB 129845} Win NT, Win 2000, Win XP (General remarks on STOP messages)


0x00000001: APC_INDEX_MISMATCH MSDN article
0x00000002: DEVICE_QUEUE_NOT_BUSY MSDN article
0x00000003: INVALID_AFFINITY_SET MSDN article
0x00000004: INVALID_DATA_ACCESS_TRAP MSDN article0x00000005: INVALID_PROCESS_ATTACH_ATTEMPT
(Click to consult the online MSDN article.)
Generally, use the General Troubleshooting of STOP Messages checklist above to troubleshoot this problem. 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 currentstatus of a fix from Microsoft.

You receive the Stop error “Stop 0x05 (INVALID_PROCESS_ATTACH_ATTEMPT)” in Win XP SP2 or Server 2003 {KB 887742} Win XP SP2 (all subversions); Server 2003; Tablet PC Edition 2005

0x00000006: INVALID_PROCESS_DETACH_ATTEMPT MSDN article
0x00000007: INVALID_SOFTWARE_INTERRUPT MSDN article
0x00000008: IRQL_NOT_DISPATCH_LEVEL MSDN article
0x00000009:IRQL_NOT_GREATER_OR_EQUAL MSDN article
0x0000000A: IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online MSDN article.)
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not havepermission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)

Troubleshooting “Stop 0x0A” Messages in Windows {KB 165863} Win NT, Win 2000, Win XP
Troubleshooting a Stop 0x0000000A Error in Windows XP {KB 314063} Win XP

Possible Resolutions to STOP 0x0A, 0x01E,and 0x50 Errors {KB 183169} Win NT, Win 2000, Win XP
During upgrade to Win XP {KB 311564} Win XP
STOP 0x0000000A Error Message When You Change from AC Power to DC Power {KB 316676} Win XP
“Stop 0x0000000A” Error Message When You Fast Switch Between Users {KB 310918} Win XP
While booting NT on same partition as Win 2000 or XP {KB 227301} Win NT, Win 2000, Win XP
Windows XPRestarts When You Try to Shut Down Your Computer {KB 311806}
“Fatal System Error” When You Try to Use a Hewlett-Packard 5100C ScanJet {KB 307129} Win XP (with Brother printer)
Computer May Hang During a Heavy Load with an Ericsson HIS Modem {KB 319810} Win 2000, Win XP
STOP 0x4E, STOP 0x1A, STOP 0x50, and STOP 0xA Errors Occur When You Try to Start the Computer {KB 271955} Win NT 4.0(corrupt physical RAM)
“Stop: 0x0000000A (00000063, 0000001c, 00000000, parameter4)” error message on a Windows 2000-based computer {KB 837384} Win 2000 (program error, hotfix available)
How to Use Driver Verifier to Troubleshoot Windows Drivers {KB 244617} Win 2000, Win XP, Server 2003
Error Message When Installing Windows Vista on a Computer With More Than 3 GB of RAM: STOP...