Need help, x52pro problem

[jetace]

Hi, my x52pro stutck's and stops responding, until i unplug and reconnect him again . Some time this kicks me out of game to the "blue screen" .Any help about this problem ?

Im using Win7x64 and have latest driver, and SST instaled.:cry:

[Sarge55]

Try un-installing the driver, cleaning the registry and re-installing the driver.

 

Which driver are you using? "Saitek_X52Pro_Flight_Controller_SD6_64.exe"

 

If you haven't already, try the Saitek forum as well. http://www.saitekforum.com/index.php

[jetace]

x52

 

Yes, im using latest saitek drivers, which i have downloaded from saitek site.

About cleaning registry, u mean to manualy remove all entries related to saitek in registry?

[Sarge55]

Use a registry cleaner after un-installing then go through the registry for any stray Saitek references for the X-52.

 

Remember, removing the wrong things in the registry can cause significant problems so make sure you are comfortable working in the registry.

[Panzertard]

Also quite possible, BSOD (Bluescreen) may indicate you have a assignment conflict.

Please see TROUBLESHOOTING - Help us helping you. post #3, assignment conflict.

[EtherealN]

I think this just might be exactly the same thing I had - I recently purchased a new x52 (non-pro) and would suffer lockups where the driver fails and causes windows to be unable to shut down, and unplugging the stick caused a BSOD.

 

This was caused by having names for buttons be longer than the width of the MFD lines. Anything longer than 16 letters (spaces count as a letter for this) caused the program to become unresponsive although axes still worked. For example "Track While Scan" without the quite marks would just barely fit, but "Left Mouse Button" is one letter too long and causes this to happen.

 

The solution was to go through the profiler and ensure that the names of my bindings are short enough.

[jetace]

I think this just might be exactly the same thing I had - I recently purchased a new x52 (non-pro) and would suffer lockups where the driver fails and causes windows to be unable to shut down, and unplugging the stick caused a BSOD.

 

This was caused by having names for buttons be longer than the width of the MFD lines. Anything longer than 16 letters (spaces count as a letter for this) caused the program to become unresponsive although axes still worked. For example "Track While Scan" without the quite marks would just barely fit, but "Left Mouse Button" is one letter too long and causes this to happen.

 

The solution was to go through the profiler and ensure that the names of my bindings are short enough.

hmm, maybe u right about long names, sometimes they dont displayed correctly on MFD (they diplayed with errors), Thank you very much, ill try to rewrite long names and we'll see....

[jetace]

problem solved(i hope)

 

EtherealN i wish to thank you very much ! Four day from how i have changed names in SST profile and there is no more lock ups , crashes and blue screens

I think my problem is solved :thumbup:

[Slayer]

16 characters is the exact width of the MFD display, anything longer will make it scroll across the window but sometimes it sticks and the MFD just quits working. I suspected that this was the cause but don't have many commands named longer than 16 characters, good find.

[Devrim]

Hi...

 

I was using X52Pro with my Dell laptop. I had no issue with it. Since using new desktop system (chek my signature) my system has crashed (Blue Screen) two or three times. Today it was forth!.

 

At first, I didn't understand the problem. I thought it was memory card or anything... Finally I decided it is X52Pro. Last time system crashed when I unplugged the X52 from USB port. And today it crashed when I click on "Test Profile" in SST Software.

 

As I read in this page, I shortened the commands name, although none of one was longer than 16 chr. Then, I clicked on "Test Profile" and it didn't crash.

 

It seems OK. But I'm not sure that's the problem.