BSOD while playing games, Framework Violation

Hey guys, been having a problem for awhile and have not been able to figure out a solution on my own, and this seemed like a good place to reach out.

Recently I switched out the motherboard in my set up, and did a clean install of Windows 7. I'm not 100% sure when it started, but sometime between then and now something got messed up and now my computer likes to crash whenever I'm playing games. There's no set time to how long I'll be playing that it will happen, but it is something I just assume will happen at some point when I play games. I've put off actually fixing this problem too long, so I'm reaching out for help.

I do overclock, but I also monitor temperatures. I'm pretty confident it isn't a temperature issue. It also doesn't matter how demanding the game is, it will crash if I'm playing cutting edge 3D game with all the bells and whistles enabled, or if I'm playing a simplistic 2D platformer. I don't even necessarily have to really start playing, it sometimes crashes as soon as the opening menu pops up. The BSOD mentions that there was a Wiindows Driver Framework Violation, so I'm assuming one of the drivers is corrupted or not playing nice with another one.

Everything I can think of is up to date, but I could be missing something. I'm not too savvy on the software side of computers, so I'm hoping someone here can help me. This will be a much needed learning experience.

Specs:
Windows 7 Ultimate x64 SP1
Zotac Z77ITX-A-E motherboard Z77 chipset
EVGA GTX 680 Superclocked 1058MHz
8gbs (2x4) G.Skill Ram DDR3 1600
Intel i7 Sandy Bridge 3600k OC'd 4.2ghz
Corsair Enthusiast 850W power supply

Lots of thanks in advanced if anyone can help me solve this problem.

update this driver
MotioninJoy simulate Xbox 360 controller (virtual Xinput device)
MotioninJoy simulate Xbox 360 controller(virtual Xinput device) | MotioninJoy

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {5, 0, 1202, fffffa8008145c50}

*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : MijXfilt.sys ( MijXfilt+363a )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000000000005, A framework object handle of the incorrect type was passed to
	a framework object method.
Arg2: 0000000000000000, The handle value passed in.
Arg3: 0000000000001202, Reserved.
Arg4: fffffa8008145c50, Reserved.

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


BUGCHECK_STR:  0x10D_5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  DS3_Tool.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff88000ea5b46 to fffff800030e6fc0

STACK_TEXT:  
fffff880`0ed056a8 fffff880`00ea5b46 : 00000000`0000010d 00000000`00000005 00000000`00000000 00000000`00001202 : nt!KeBugCheckEx
fffff880`0ed056b0 fffff880`06dae63a : fffffa80`0b42a7b0 fffffa80`0b42a8b0 00000000`00000004 00000000`00000001 : Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+0x8a
fffff880`0ed059d0 fffffa80`0b42a7b0 : fffffa80`0b42a8b0 00000000`00000004 00000000`00000001 fffff880`0ed05b00 : MijXfilt+0x363a
fffff880`0ed059d8 fffffa80`0b42a8b0 : 00000000`00000004 00000000`00000001 fffff880`0ed05b00 fffff880`0ed05a50 : 0xfffffa80`0b42a7b0
fffff880`0ed059e0 00000000`00000004 : 00000000`00000001 fffff880`0ed05b00 fffff880`0ed05a50 fffff880`0ed05a18 : 0xfffffa80`0b42a8b0
fffff880`0ed059e8 00000000`00000001 : fffff880`0ed05b00 fffff880`0ed05a50 fffff880`0ed05a18 00000000`00000000 : 0x4
fffff880`0ed059f0 fffff880`0ed05b00 : fffff880`0ed05a50 fffff880`0ed05a18 00000000`00000000 fffffa80`0a39e2c0 : 0x1
fffff880`0ed059f8 fffff880`0ed05a50 : fffff880`0ed05a18 00000000`00000000 fffffa80`0a39e2c0 00000000`00000040 : 0xfffff880`0ed05b00
fffff880`0ed05a00 fffff880`0ed05a18 : 00000000`00000000 fffffa80`0a39e2c0 00000000`00000040 fffffa80`0b347070 : 0xfffff880`0ed05a50
fffff880`0ed05a08 00000000`00000000 : fffffa80`0a39e2c0 00000000`00000040 fffffa80`0b347070 fffffa80`06771f30 : 0xfffff880`0ed05a18


STACK_COMMAND:  kb

FOLLOWUP_IP: 
MijXfilt+363a
fffff880`06dae63a ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  MijXfilt+363a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: MijXfilt

IMAGE_NAME:  MijXfilt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4fade6a0

FAILURE_BUCKET_ID:  X64_0x10D_5_MijXfilt+363a

BUCKET_ID:  X64_0x10D_5_MijXfilt+363a

Followup: MachineOwner
---------