I agree that if the initial problems showed up the Steel Series keyboard driver that is woefully outdated, it's a good solid culprit of this. You should be able to uninstall your drivers for it and Windows will default it to the regular keyboard drivers. Try seeing if the system stabilizes with the regular MS drivers instead of the Steel Series ones. You may need to uninstall any Steel Series software to make sure the drivers are gone, and you may even need to go as far as to use Driver Fusion (free program) to get rid of em entirely.
This kernel dump you sent was actually a 0x116 bugcheck, which means a video card driver failure. The version of the drivers you use for your video card have been known to have bugs, so try updating to a latest version or downgrading to one prior to the 310.x series. As far as deep-diving into this crashdump, I cannot find anything solid to work with. I have some suspicious items, but nothing I can honestly confirm as I don't think I can skillfully traverse it well enough to verify.
Oh, and turn on
Driver Verifier and send us any new crashdumps caused by it. Please follow instructions carefully and entirely, otherwise it won't work or we'll get false positives. Send us the minidumps for now, no need for kernel dumps at this time.
Analysts:
Subcode for 0x116 crash shows a STATUS_INSUFFICIENT_RESOURCES error. I'm starting to learn that this is a very generic error and is not so affiliated with lack of memory as originally suspected. I also saw in the raw stack that there was a c0000022, or
Access Denied, in that the process tried to access an object but not been given rights to do so. I'm not sure if this is triggering the other error or not, and I'm not sure what object it's referring too. However I can venture to guess it's a registry key at the very least. That's all I can seem to glean from this so far. Perhaps have the guy do a CHKDSK if he hasn't already?