Blue Screen with new SSD?!

[LozzaNewport]

Hey Guys,

So i set my ssd up and was all good for about 2 hours, went out to dinner with nothing open and a couple hours later i come back and its in sleep mode, i turn it on and i restart it cause a bunch of updates and it blue screens twice. 
With an error of DRIVER_IRQL_NOT_LESS_OR_EQUAL e1d63x64.sys
Do you guys know of anything i can do to fix it?

I used blue screen viewer and it showed me the dump and thats it below.

 

==================================================

Dump File         : 070814-8921-01.dmp

Crash Time        : 8/07/2014 7:33:01 PM

Bug Check String  : DRIVER_IRQL_NOT_LESS_OR_EQUAL

Bug Check Code    : 0x000000d1

Parameter 1       : 00000000`0000001c

Parameter 2       : 00000000`00000002

Parameter 3       : 00000000`00000000

Parameter 4       : fffff880`04f66654

Caused By Driver  : rdpbus.sys

Caused By Address : rdpbus.sys+5a6e8c8

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Crash Address     : ntoskrnl.exe+5a440

Stack Address 1   : 

Stack Address 2   : 

Stack Address 3   : 

Computer Name     : 

Full Path         : C:\Windows\Minidump\070814-8921-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 9200

Dump File Size    : 297,288

Dump File Time    : 8/07/2014 7:33:35 PM

==================================================

 

Thanks everyone in advance for the help

[ZacDaMan72]

Reading from Microsoft:

 

Cause

 

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high.

This bug check is usually caused by drivers that have used improper addresses.

If the first parameter has the same value as the fourth parameter, and the third parameter indicates an execute operation, this bug check was likely caused by a driver that was trying to execute code when the code itself was paged out. Possible causes for the page fault include the following:

 

- The function was marked as pageable and was running at an elevated IRQL (which includes obtaining a lock).

- The function call was made to a function in another driver, and that driver was unloaded.

- The function was called by using a function pointer that was an invalid pointer.