Frequent BSOD, no overheating, SSD recently installed

[eightmints]

I've recently installed a new solid state drive (about a month ago) and though I doubt this is the issue I thought I'd mention it just in case. I've attached a minidump. Thanks in advance!

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

[COLOR="red"]BugCheck 3B[/COLOR], {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 [COLOR="Red"]nvlddmkm.sys[/COLOR]
*** 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: [COLOR="red"]nvlddmkm.sys[/COLOR]
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed [COLOR="red"]Oct 23[/COLOR] 16:51:50 [COLOR="red"]2013[/COLOR] (52676AFE)
    CheckSum:         00C0CF0F
    ImageSize:        00C37000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Name	[COLOR="red"]NVIDIA GeForce GTX 260[/COLOR]

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

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

Use !analyze -v to get detailed debugging information.

[COLOR="red"]BugCheck 50[/COLOR], {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+:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html