I suspect the Ram really. Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.
Code:
BugCheck 50, {fffffab001e4030b, 0, fffff80002f4f75e, 5}
Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiTrimWorkingSet+1de )
Followup: MachineOwner
---------
BugCheck 50, {fffffaa005b0a9d8, 0, fffff800031a342e, 5}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+3e )
Followup: MachineOwner
---------
BugCheck A, {fffff68000013a80, 0, 0, fffff80002ea7957}
Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+11b )
Followup: MachineOwner
---------
BugCheck 1A, {41790, fffffa8001c4ba40, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )
Followup: MachineOwner
---------
BugCheck 24, {1904fb, fffff8800ad91f58, fffff8800ad917c0, fffff80003213b60}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2cc9 )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff80002ff4f8c, fffff88008eceef0, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
Followup: Pool_corruption
---------
BugCheck 1A, {41790, fffffa8000f2c220, ffff, 0}
Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+3e4 )
Followup: MachineOwner
---------
Hard drive controller was blamed too. Please proceed the following things:
Disk Check
HD Diagnostic (Download HD diagnostic test from manufacture site)