I wish that were the case, but the memory has been tested repeatedly. That was my first check. I've also replaced the power supply and my sound card to start with and updated all my drivers that I can think of.

Your PC is crashed with intel interrupt code d and it is general protection fault. 90% of the problem is related to hardware problem and 10% is related to device driver error. One minidump is insufficient to find out the culprit. Zip 5 to 6 minidump and attach the zip file here.

BTW hardware error does not mean faulty ram and it means ram. CPU, m/b, PSU or video card. Usually half of hardware error is related ram. You must aware that some faulty ram can pass memtest.

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000