BSOD: DRIVER_POWER_STATE_FAILURE after wake, usb?

I've been using the sleep function happily for months but yesterday both times I woke my computer, my computer acted funny. Both times steam quietly crashed, and some programs refused to open, others refused to close (even after killing the process) First instance gave me the above BSOD (attached) the second time, I got an Exception Breakpoint from my voice software I use all the time. And then my computer refused to shut down.

Possible culprits:
1: Hyperx Cloud II 7.1 headset, but I got it last week and sleep has been working fine.
2: Logitech unifying RF dongle for use in the wireless keyboard and mouse I got on Monday. However I unplugged it before I put the computer to sleep the second time, and this still happened.
3: Corsair K70 keyboard I used the second USB cable for the first time on Monday to plug the Logitech RF dongle into the keyboard's extra port, because somehow my computer's video card was causing interference. It worked fine in my keyboard's USB port though.

I'll troubleshoot this further but I'd like some insight into what caused the BSOD to help me narrow it down.

Curious, why are you asking about my RAM? I have four sticks in a strange (but functional) configuration due to space concerns. Is my computer complaining about it?

I've looked yet I've yet to find any drivers for the headset. All I found on their web site is a firmware update related to volume control issues. Lack of drivers is apparently intentional from what I've read.

I understand. It's a clearance issue with the two closest slots next to my processor. Needs low profile ram and only have two pieces of it. I got two more with identical timings and so far they've worked flawlessly. I'll keep it in mind if things start going squirrel.

As for the headset, I'd moved it from a usb 2.0 port to a 3.0 port when i was playing with the RF transceiver and I've sinced noticed an occasional crackling sound coming from the headset when the hard drive is heavy accessing. (And I've noticed others having the same problem when I searched) I've switched it back to 2.0 and the problem went away. Maybe that was cause of the BSOD too, I'll test and update this thread.