BSOD IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe

hey everyone! i was just wondering if anyone be kind enough to have look at my crash dump as u can see from the title ive been getting blue screens. thanks

Any recent changes? Such as installing a controller?

MotionJoy ? Im getting blue screen when I plug in my usb 360 controller

Can you update the drivers for this?
fffff880`05baa000 fffff880`05bcc000 MijXfilt T (no symbols)
Loaded symbol image file: MijXfilt.sys
Image path: MijXfilt.sys
Image name: MijXfilt.sys
Timestamp: Fri May 11 23:27:12 2012 (4FADE6A0)
CheckSum: 00022009
ImageSize: 00022000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

that is the latest drivers for it no newer ones are out. i had feeling it was that it had happened before so i just uninstalled the program. is that driver wat is causing the IRQL_NOT_LESS_OR_EQUAL?? oh thanks by the way!!

Positive on two of the crashes.

The other two, 012414-12776-01 and 013014-12324-01 are not as definitive. They look to be memory management related. I would unplug that MotionJoy controller and run Memtest86+ on it overnight.

012414-9812-01.dmp - Definitely caused by the MotionJoy controller. The crash is happening in kernel mode at address fffff88005bc63eb, but I can see in the call stack return addresses indicate activity in user address space led up to the crash. It's likely an event generated by the user that requires functionality from the driver. At which point the driver stumbles and crashes the system, due to making a bad pool request. To further diagnose what's happening here you would need to enable special pool and pool tracking in Driver Verifier. I'm not a driver developer, and am still learning the aspects of debugging, but I believe most of the causes of bad pool allocations are in the code. Such as incorrect initialization sequence of variables and objects. But really, this is an issue that the developer of that driver should battle. One thing you could do is make sure you're using the "signed" version of their driver. This ensures it is WHQL certified. Not that this guarantees it is 100% fault-proof but it's normally more thoroughly tested than drivers that are not WHQL.

012414-12636-01 - This one is even more obvious that it's a problem with the MotionJoy driver. There are similar signs from the previous crash that user generated action being passed to the driver led up to the crash. The difference is in how it crashed. In this particular dump the driver attempts to reference a handle but the handle address is 00000000. i.e. empty. Obviously a handle can't reside at an empty address.