New
#11
It's eminently possible that something you've installed into both systems is causing an issue, but this dump points to a page table page being corrupt so it could really be anything, software or hardware. It does have a 3rd param of ffff, so it's an underflow of some kind triggering the corruption. It could be a bad driver, or potentially some sort of hardware issue that triggers this (bad hardware, firmware bugs, etc) flipping of at least one (or more) PTEs in the page table page to a non-zero value (this very particular scenario is what triggers the bugcheck you've posted here).
If you truly believe that the RAM is good in this machine, you can try to reproduce these errors on a Windows 8.1 system, which will attempt to go about preserving the corrupted PTE value before issuing a bugcheck if this happens again, thus making it (hopefully) easier to analyze in that configuration. A trial version of Windows 8.1 would be sufficient, you wouldn't need to go out and purchase a license at all.