Blue Screen Memory_management, not RAM

overall, looks like a hardware problem. Only thing I can think of that might help is to blow the dust out of the computer and run hardware tests on the system. (and update the ethernet driver)

I guess I should also say you should check for corrupted system files and run a virus scan.
but it looks like you run malwarebytes. try the system file checker just in case you have a corrupted file.
start cmd.exe as a admin
run
sfc.exe /scannow

note: the debugger did not detect any core corruption in windows files

=============
third bugcheck was also in memory management but unrelated to virtual memory
also looks like another hardware problem.


===================
looked at the second bugcheck, another memory location corrupted in how it maps memory to the pagefile.
either something overwrote memory or you have a hardware failure.
since the machine is so old (before 2009) I would run compressed air over the fans, and motherboard to clean out any dust.

You might also be getting read error from the hard drive pagefile. You might go into control panel and turn off the pagefile.sys in the virtual memory settings, reboot, rename the pagefile.sys to pagefile.old and turn it back on in control panel to create a new one but in a different spot on your hard drive. If this works, it means your hard drive is in the process of failing.
(you can run seatools to help test your drive)


machine info: BIOS Release Date 08/12/2009
Manufacturer Gigabyte Technology Co., Ltd.
Product Name GA-MA770-UD3
Processor Version AMD Athlon(tm) 64 X2 Dual Core Processor 6000+
Processor Voltage 8eh - 1.4V
External Clock 200MHz
Max Speed 3200MHz
Current Speed 3000MHz

========================


just looked at first memory .dmp, it was a attempt to copy memory to a bad memory location.
very hard to say why. It could be a general memory corruption caused by hardware.
the only real driver problem I see is your network driver is very old 2009 and you have nvidia streaming installed (2014) the nvidia driver requires a proper working network driver so you should update
\SystemRoot\system32\DRIVERS\Rt64win7.sys Thu Feb 26 01:04:13 2009
it is a Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
get a new one from http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

Note: i don't think it is the cause of this crash though.
You indicated that you did a memtest86 run so update the ethernet driver, maybe it was corrupting memory. (really can not tell with this bugcheck, will look at the others)

I don't think it would be a direct cause, but a over heated GPU would pull more power from the motherboard and that could cause your motherboard's power to fluctuatate, which could cause the power to the memory to be too low. Maybe, but I would not count on it. If memtest86 passes, a more likely direct cause would be a bug in a driver. it that is the case, each time you do a reboot of your system windows will load the drivers in a different order and you might get a different bugcheck or none at all. it the corruption can be in code that is not checked or did not have to run.