Oh man you've violated your dog that's not good... However, we may need some more details about this violation.
=====
The following parameters are displayed on the blue screen. Parameter 1 indicates the type of violation. The meaning of the other parameters depends on the value of Parameter 1.
Parameter 1, Parameter 2, Parameter 3, Parameter 4, Cause of Error
0, The DPC time count (in ticks), The DPC time allotment (in ticks), Reserved, A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace.
1, The watchdog period, Reserved, Reserved, The system cumulatively spent an extended period of time at IRQL DISPATCH_LEVEL or above. The offending component can usually be identified with a stack trace.
This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above. The value of Parameter 1 indicates whether a single DPC exceeded a timeout, or whether the system cumulatively spent an extended period of time at IRQL DISPATCH_LEVEL or above.
====
After rebooting there should be a couple of entries in the System Event log which may identify the offending component which is not necessarily the ssd unless your have already retrieved this information and it was specifically called out. If you can post the text from those entries we might see what caused it.
