If you can’t find a specific reference to your problem, running through the following checklist stands a good chance of resolving the problem for you.This checklist is also usually the best approach to troubleshooting some specific Stop messages, such as 0x0A and 0x50.
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.
These appear only in the NT-based operating systems: Win NT, Win 2000, Win XP, and Vista. STOP messages are identified by an 8-digit hexadecimal number, but also commonly written in a shorthand notation; e.g., a STOP 0x0000000A may also be written Stop 0x A.
Four additional 8-digit hex numbers may appear in parentheses, usually unique to your computer and the particular situation.
NOTE: Many users search this site for the word minidump which often accompanies these Stop Message errors.
The fact that a memory minidump occurred tells you nothing except what you already know — that there was an error.
It is the name of the error condition and its 8-digit number that help you determine the actual error condition.
If a message is listed below, but has no articles or explanation (nothing but its number and name), post a request on the Aum Ha Forums asking about it.
STOP messages of this type are rare, obscure, and usually only of interest to programmers debugging their code.
Real-life scenarios of a computer encountering them are unlikely, so I’ve made it a lower priority to document them here; but we’ll be happy to address this in the Forum (which also will tip me off that I should add more to this present page).