Saitek stick maybe crashing Black Shark and Computer often

[Ramstein]

My Saitek C52 Pro joystick maybe crashing Black Shark and Computer often. I will bew in a game and the computer will reboot. It is not Black Shark causing the reboots.

 

I have this problem with my X52 Pro. I also can see the cause of this is because it is when I have my Stick profile turned on. The Computer error message I get after the computer reboots shows the error '256' which also show that it's the Saitek files reported in the 'mini-dump'.

 

One note though, it only seems to happen in Black Shark. It does not seem to have this randon crash/reboot in Il-2. Since I mainly only play those two flight sims, I do not know if it happens in other other sims.

I suspect that the stick has parts that wear out after a couple years, sending spike and bogus key presses in some combination which cause the reboot. The reboot happens with no warning. it is a huge PITA. Not much can be done when the stick is a couple years old. Only thing that can be done is to buya new stick. I don't think my Saitek pedals have anything to do with this reboot problem.

 

I do use an HP 7 port USB opowered HUB. Not that makes any difference. Only other USB device I use is a (new)Logitech USB headset with microphone.

 

:joystick:

[Feuerfalke]

I doubt it has anything to do with the stick or weardown of buttons or parts. The buttons are only active when pushed and there is not much that could cause this and the sticks sensors are hall-sensors - they do not suffer from the mechanical wear-out from older sticks. After all, you can reaffirm this, by opening the gamecontroller-panel and check the inputs of axis and buttons.

 

But IMHO it's something different for three reasons:

 

1. A lot of players use the X52 and X52pro, nobody reported these reproducable crashes.

2. If it was your stick, you'd have the problem not only when running a game, but even in windows. Remember, your stick will input data, no matter what game you run or if you run a game at all.

3. If IL2 and BS are the games you play, BS is the more likely candidate to crash if there is a problem with your PC, as it is WAY more demanding than IL2, especially for the central components like CPU, RAM and your mainboard.

 

Use a monitoring tool and check your CPU temperature while playing DCS. This should always be one of the first things to check when having a problem with DCS.

[Panzertard]

If you use the SST software:

- You need to ensure that you dont have any conflicts with SST and "Other" inputs in DCS.

If you have such conflicts, it may cause BSOD - I've experienced this first hand.

 

Basicly I had to goto DCS->Options -> Controls and

 

1. Select Ka-50 "Real" / "All"

2. Click in the "x52 Pro Stick" column, then "Clear Category"

3. Click in the "Saitek Pro Rudder" column, then "Clear Category"

 

4. Select Ka-50 "Real" / "Axis Command", repeat #2 and #3.

5. Select Ka-50 "Game" / "All", repeat #2 and #3.

6. Select Ka-50 "Game" / "Axis Command", repeat #2 and #3.

 

Now assign the joystick Axis to Pitch / Roll / Collective etc.

Then go back to your SST and assign keys etc.

 

No more BSOD's for me.

[Ramstein]

the Windows minidump reports the saitek stick file as the file when it crashes..

and it all adds up..

 

it only happens when the Saitek Black Shark profile is enabled..

:joystick:

 

I am unable to re-create it,, it only happens when it happens..

 

I will check everything again..

 

it does not happen every night, but it can happen once every weeek or 2x..

Edited January 7, 2010 by Ramstein

[Ramstein]

so far, no reboots. I removed my zoom controls from the joystick completely. I only now am only using the keyboard for zoom view.

Not going to call it a complete success until a long time passes without inicident.

 

:joystick:

[Panzertard]

I only had those dreaded BSOD's before I properly unassigned conflicting assignments.

Not seen BSODs since unassigning. ;)

I still have Zoom assigned to the Slider though.

(Famous last words, I'm going to fly a little bit again today)

[Ramstein]

well,

it was defintely the BS Saitek profile that caused my computer crash reboots..

 

I think I made a profile that no longer has the crash/reboot problems..

the Zoom in/out function using either the rotaries, or slider had big problems..

 

I am trying the zoom in/out using POV2 up/down, and so far so good,,

 

I have my profile up on the Saitek forums..

Saitek X52 Pro

:joystick:

 

FYI