BSOD playing RIFT, error 0x0000001a Caused by ntoskrnl.exe

OK. I can't think of anything else unfortunately...but lets try one more thing to see if it could be anything else, and not the SSD.

Please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode

There are several things going on the looks of it.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 180, fffffa800f6a4620, fffff88008369430}

*** WARNING: Unable to verify timestamp for rzpmgrk.sys
*** ERROR: Module load completed but symbols could not be loaded for rzpmgrk.sys
Probably caused by : rzpmgrk.sys ( rzpmgrk+1430 )

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

Check for an update to the Razor drivers.

Code:

fffff880`0840cd60  ffff0000`007612cf
fffff880`0840cd68  fffff880`03b79fd8Unable to load image \SystemRoot\system32\drivers\aswSP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSP.sys
 aswSP+0x63fd8
fffff880`0840cd70  fffff880`0840ce40
fffff880`0840cd78  fffffa80`0f718b30

Avast is flagged as an issue - replace it with MSE for testing.

Code:

fffff880`0bfe4028  fffff880`0bfe57a0
fffff880`0bfe4030  fffff880`0bfe5770
fffff880`0bfe4038  fffff880`040d941dUnable to load image \SystemRoot\system32\DRIVERS\e1d62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1d62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1d62x64.sys
 e1d62x64+0x2041d
fffff880`0bfe4040  fffffa80`0d5805e0
fffff880`0bfe4048  00000000`00000000
.
.
.
    Loaded symbol image file: e1d62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\e1d62x64.sys
    Image name: e1d62x64.sys
    Timestamp:        Tue Feb 04 19:56:22 2014 (52F0B23E)
    CheckSum:         0008376D
    ImageSize:        0007A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please see if an update is available for your Intel Gigabit adapter.

The most recent .dmp files all point to the NVidia driver.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800f24f994, fffff8800abd7af0, 0}

Probably caused by : nvlddmkm.sys ( nvlddmkm+1b6994 )

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

Please uninstall it completely, then reinstall it using this guide:
NVIDIA Drivers - Avoid Problems