SSD causing BSOD?

About two weeks ago I purchased a Kingston HyperX 3K 120GB SSD from Amazon. I decided to re-install Windows to go with it as I had almost no data that needed to be backed up and didn't want to deal with the hassle of cloning my HDD to the SSD. After re-installing windows and all of my drivers I started getting BSODs. So I downloaded the Windows 7 SDK and opened the dump files with WinDbg (see below). I am unsure what to do here as only programs I have that are either on the SSD or have dependencies there (DirectX) are crashing. I have run memtest and it shows nothing is wrong with my RAM. I am fairly computer literate but I'm not quite sure where to go with this as this is the first computer I've built that has had this issue.

Computer components:

• 
  ■ Asus Maximum V Extreme Mobo
  ■ Intel i7-3770k (removed overclock to test if computer would still BSOD)
  ■ Corsair H100i
  ■ 2-way SLI EVGA GeForce GTX 680 Classifieds
  ■ WD Black 1TB HDD 7200rpm
  ■ Kingston HyperX 3K 120GB SSD
  ■ 16GB (2x8) Kingston HyperX Beast RAM @ 1866MHz

Here is the dump file as shown in WinDbg:

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffffffff88008, memory referenced
Arg2: 0000000000000007, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffffa800fa5a000, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: fffffffffff88008

CURRENT_IRQL: 7

FAULTING_IP:
+6562313164303165
fffffa80`0fa5a000 f0109e0880f8ff lock adc byte ptr [rsi-77FF8h],bl

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff80000b9c540 -- (.trap 0xfffff80000b9c540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88008cd5920 rbx=0000000000000000 rcx=fffff88008cd5920
rdx=0000000000000103 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa800fa5a000 rsp=fffff80000b9c6d0 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000001
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
fffffa80`0fa5a000 f0109e0880f8ff lock adc byte ptr [rsi-77FF8h],bl ds:0001:ffffffff`fff88008=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e7d129 to fffff80002e7db80

STACK_TEXT:
fffff800`00b9c3f8 fffff800`02e7d129 : 00000000`0000000a ffffffff`fff88008 00000000`00000007 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c400 fffff800`02e7bda0 : fffffa80`151a5bf0 00000000`019d60a3 fffffa80`110e4270 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c540 fffffa80`0fa5a000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9c6d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0fa70040 : 0xfffffa80`0fa5a000


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`02e7bda0 440f20c0 mov rax,cr8

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiPageFault+260

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 51fb06cd

FAILURE_BUCKET_ID: X64_0xD1_nt!KiPageFault+260

BUCKET_ID: X64_0xD1_nt!KiPageFault+260

Followup: MachineOwner