Windows XP Common Stop Messages

This is great! but what about including some screenshots of this common errors. This is good for those who are more visual. it is just a thought.

How to install:

It is useful to know a bit about Windows architecture (kernel vs user mode, etc.) when debugging but it is possible to do this without that knowledge.

In order to use this tool you need a memory dump or mini dump from a Windows machine and the exact symbol files for every file loaded into memory at the time of the crash. Putting a symbol file tree together used to take days but Microsoft has automated the most difficult part of the debug process by letting you dynamically pull the correct symbol files via http from a huge symbol tree they have made available online.

You can download winDBG here.

Once installed you go to file...symbol search path and enter SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols (where C:\websymbols is a local dir to store files in) and hit reload. You are then ready to load the dump file.

Here are the results of running the !analyze -v command.

Note almost all DBG commands are prefixed with a !

!analyze -v is by far the most common command and will tell you what cause almost all 0xE, 0x1E, 0xA and 0x1A bluescreens and will give you useful information from most others.

When you first load a dump file winDBG will automagically run just a !analyze and give you its best guess as to the issue. In this case it tells us: Probably caused by : AGRSM.sys ( AGRSM+5ace5 )

This can be confirmed by the full output of !analyze -v

Get the *.dmp file from the effected machine and run it through the debugger. Google the error.