Dump files have their own formatting, which can be understood by utilities such as the "dumpchk" program. Unfortunately, even after "decoding" the contents of a dump file, the resulting output can often take some work to decipher.
When the system creates dump files, it usually also logs an error report in one of the Event Logs; you might find a clue there:
Open the Event Viewer utility in your Administrative Tools control panel and look through your System and Application logs for entries flagged with "Error" or "Warning", especially those whose time-stamps coincide with the occurence of the crashes. Double-clicking on such an entry will open a properties window with more detailed information on the error; post the details from a representative sample of some of the different error messages (please don't post duplicates of a given entry, or flood us with the entire contents of the logs).
To post the details:
In the Properties window of a given entry, click on the button with the graphic of two pieces of paper on it; the button is at the right of the window just below the up arrow/down arrow buttons. You won't see anything happen when you click the button, but it will copy all of the details to the Windows clipboard. You can then paste the details into your next post here.
by the way: XP Pro SP2, no recent hardware changes, but its been diong this since i put this computer together (2 weeks ago) off and on randomly. This specific error was a memory management error but i believe its from the same source as the IRQL error.
OK- it looks like your original BSOD error was a 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL error, which is usually attributed to a device driver issue or faulty/mismatched RAM. The 0000001a error is the memory management error.
Given that two errors can be caused by RAM-related issues, and that you indicated that the problem had been present since the system was built, I would:
1. Check the mobo and RAM module specs; make sure the RAM is of a compatible type/speed for the mobo.
2. Check the RAM modules to make sure that they are firmly and properly seated into their mobo slots. Check all other connections and components while you're in there.
3. If you have more than one RAM module installed:
* Run the system with only one module installed at a time. If the system only BSODs when a particular module is installed, you've found a likely culprit.
* Run an extended test with the free memtest86 RAM test utility. I usually run the tests for at least hours.
4. Recheck the driver software packages you've installed. Make sure that there aren't any known compatibility issues with your particular versions and/or their related hardware devices. Update or reinstall drivers if no other likely causes have been turned up yet.
i only receive the error when im using the system heavily (playing FPS shooters) and i have NEVER had one from playing Flight Simulator 2004. Which is weird because FS uses more CPU and system memory than an FPS in 99% of cases.... any ideas?
memtest is not a Windows executable program (it's acutally Linux-based), so you need to make the boot floppy (or CD). The process is really pretty easy.
I suggested that you check the RAM and other components first not only because the errors often point to a hardware (or driver) problem, but also because you said that you just built the machine and have been getting the errors since then. In other words, you could waste time looking for a software/program fault when in fact, you may have a faulty/mismatched/mis-installed piece of hardware.
to add onto the IRQL BSOD's, i get one with ha20x2k.sys also, which is a Creative Labs X-Fi Sound card driver. And yes, i have installed the newest drivers and it was doing this before i installed the new drivers. GOD HELP ME haha. . . . i really appreciate you bearing with me.
As this is one of the first posts that comes up on Google when searching for "Error code 0000001a", I figured I'd post my fix here...
Despite all the suggestions around checking for bad memory, the culprit in my case was that my Server 2003 virtual hard disk was running low on disk space. This was likely causing issues with the pagefile - hence, the potential "memory" issues. As soon as I freed up disk space, the 0000001a errors went away.