STOP 0x000000C2: BAD_POOL_CALLER
Usual causes: Device driver, ?Memory.
Your latest dump file lists
SaiK0836.sys as the probable cause. This is your Saitek Cyborg X Joystick driver.
As a Priority:
Can you get a snip of the Memory tab of CPU-Z and attach it please (editing and attaching to your first post will be best, if you can).
SaiBus.sys Wed Jun 03 11:09:19 2009
SaiK0836.sys Thu Aug 28 10:03:54 2008
SaiMini.sys Wed Jun 03 11:09:18 2009 The SaiBus (Saitek Magic Bus driver) and the SaiMini (Saitek Magic Mini driver) were not included in the Saitek Cyborg X Joystick driver update. The SaiK0836 was, but strangely still a 2008 date. There is one from 2010 but cannot lay my hands on it (or the others) at the moment. I suspect the first two may not have updates.
nusb3xhc.sys Fri Nov 19 01:34:25 2010 Go to your
Motherboard Mfr. Support website
(or Link Removed - Invalid URL) and update your
USB 3.0 drivers. A June 2011 set are available
Here (In no way related, but you might as well have the newest drivers on your system you can get your hands on).
Might be worth seeing if there are newer Direct X drivers etc. but I don't think there is.
Could you try gaming/using the pc with the joystick unplugged, see if it crashes while in that scenario?
Looked like directx (de)initialisation failure again.
How did you get the possible cause of the problem please? Is there any driver causing troubles database one can use? Do you compare the list of initialised drivers as minidump says against such database? Or is it possible to trace the problem using straight the minidump?
After opening the dump file you can check your drivers against this list:
Link Removed . Actually a good site, has bsod codes, useful links etc.
How did I get the possible causes? I could say I'm a genius

)) but it's just a matter of time. With that, and the driver list you get to learn what drivers are good, not so good and the downright evil.
For example, if someone has a stop error code of 7F and it blames the netio.sys driver, I can say with 99.99% certainty its the Zone Alarm firewall that's causing the blue screens.
Then it's just a process of elimination, but always get rid of the downright evil drivers/software first.
Sorry no better news at the moment!!
EDIT!!! The latest version of Core Temp runs fine with Windows 7 apparently (I use Speedfan) but I'd leave it out for now, unless you think you may have temp issues.