Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card). Use the General Troubleshooting of STOP Messages checklist.0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, 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.)http://support.microsoft.com/?kbid=314063&sd=RMVP0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
One of three types of problems occurred in kernel-mode: (1) Hardware failures. (2) Software problems. (3) A bound trap (i.e., a condition that the kernel is not allowed to have or intercept). Hardware failures are the most common cause (many dozen KB articles exist for this error referencing specific hardware failures) and, of these, memory hardware failures are the most common.http://support.microsoft.com/?kbid=137539&sd=RMVP
Soooo...there are two things that I would definitely do, were I in your shoes:
a. Replace the CMOS battery. I've seen failing batteries cause a plethora of seemingly unrelated BSODS where the only common factor was memory being cited as the problem.
CMOS Battery Replacement - http://www.liverepair.com/encyclopedia/art...cmosreplace.asp
b. Run Memtest86+ for the minimum time, hoping for no errors. It takes about 2-plus hours for a complete pass on either of my systems, some suggest running overnight. If no errors, suspect eliminated. If there are errors, then more investigative work must be done...since the RAM modules themselves could be bad/damaged...the motherboard sockets for the RAM could be bad/damaged...and there may be timing differences which create a problem (either FSB or individual module timings).
Memtest86+ - Advanced Memory Diagnostic Tool - http://www.memtest.org/#downiso
Icrontic » Diagnose with Memtest86+ - http://icrontic.com/articles/diagnose_with_memtest86