Okay Some more troubleshooting after the problem arose again has taught me the following. This worked for me, your mileage may vary...
It seems
the driver causing the conflict (for me) is the
Rockfire Joystick driver VibrateGameDeviceDriver 5.0. So for people using that (crappy) joystick, just go with the standard USB joystick driver instead and forget about the force feedback.
If you have this driver installed and are experience bsod crashes,
uninstall VibrateGameDeviceDriver and reboot.
After a check with
WhoCrashed(nifty program) I get the following dump analysis. I think dyncalm.sys has something to do with the joystick's dynamic calibration system (it sounds that way). If that is so my suspicions would probably be correct. The windows driver does not use dynamic calibration of the joystick and therefore works.
My 5c
On Wed 15.8.2012 23:00:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081612-44179-01.dmp
This was probably caused by the following module: dyncalm.sys (Dyncalm+0x38B8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF84680A5D, 0xFFFFFFFFC6A5B7B0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: dyncalm.sys .
Google query: dyncalm.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On a later check, yes, it's the joystick's dynamic calibration driver...
http://systemexplorer.net/file-database ... yncalm-sys Well, there ya go. Yay!
Mike, if you can please delete all my double posts. Somehow they did not show up for me.