Frequent BSOD, no overheating, SSD recently installed

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800028848c4, fffff880021cd030, 0}

Probably caused by : ntkrnlmp.exe ( nt!KeSetTimer+14 )

Followup: MachineOwner
---------

fffff880`021ccb10  fffff880`0f114e9aUnable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xc7e9a

1: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f085000 fffff880`0fcbc000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Oct 23 16:51:50 2013 (52676AFE)
    CheckSum:         00C0CF0F
    ImageSize:        00C37000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

Name	NVIDIA GeForce GTX 260

Use this link to perform an automatic detection of your Nvidia card and determine if you can install an updated driver:
NVIDIA Driver Downloads - Automatically Detect NVIDIA Products

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8003e079035, 8, fffff8003e079035, 2}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!TimersProc+197 )

Followup: MachineOwner
---------

You need to test your RAM DIMM's/motherboard RAM slots for errors.

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Use this tutorial to help you use MemTest86+:
RAM - Test with Memtest86+