ah memtest86 is run from a floppy disk and not via windows. If you downloaded the file from memtest86: precompiled memtest86 Windows & DOS, then copy the folder contents to a floppy disc. Though the notepad instructions say linux only follow the instrutions in creating a bootable floppy and then boot to the floppy and run the test. This method ensures your testing ALL the memory. Also, sgt shultzs idea of removing memory modules to find the bad is a good idea unless your only using one module. Then you'll have to get a known good one and take out yours and put in the known good one and see if the problem clears up.
Mem dumps usually have an error code. If you can give us the error code, would help alot.
Background: mem dumps are associated with a critical system error and the computer can not run. Therefore the mem dump for trouble shooting what might be a cause. First thing to look at is a memory module problem. Either the memory module is going bad OR there could be a configuration problem in the BIOS, anywhere from voltage control & settings to frequency settings. Many people try to overclock their systems and that can cause the problems your seeing. A hinky power supply or a power supply that does not provide adequate power can cause your problems [along with incorrect voltage settings or control for memory modules]. Trouble shooting these kinds of problems are process of elimination. Best first place to start is the memory.
One other area I'll mention is people using ghost images of Windows XP. I know of people who try to use a ghost image of XP on another computer [so they don't have to buy another copy of XP] and run into some problems. This is associated with the Ghost image hardware not exactly the same on the target computer the ghost image is being installed on. One other problem I've run into is unstable mainboards e.g. a hinky or bad mainboard bios flash, and//or chipset drivers being just plain bad. VIA had this problem a while back.