So often I see a whole host of major fixes, re-installs and other unpleasant efforts. In many cases they are required, but sometimes only because of a bunch of failed intermediate tries.
In the case of the Saitek controllers - THEY ARE SENSITIVE TO STATIC - but so are all computer components and it seems, particularly USB devices.
While this may not help the OP (but unplugging anything "hot" has a risk of static discharge), here is a post from an AVSIM forum that may help...
The Saitek bits have demonstrated a love/hate relationship with static electricity. Probably because they have metallic part in the stick/yoke/throttles for strength they will pick up the smallest static charge from the user. This happens often and most likely when you step away and return to the computer after walking on carpet ( or petting the cat) but also from the fabric of some chairs. The effects range from a small "zap" to the fingers, to an audible "pop". The effect tends to be a disruption of the USB connection to the computer.
Since the first time this happened to me (X-52 stick & throttle - on descent in a RTWR practice leg on final) I am always on the alert. The cure? Disconnect the Yoke and/or stick and/or pedals from the computer one-at-a-time (you will hear the USB conect tone), wait a second or two then reinsert the plug for each (hear the tone again). If you have the profile manager running and esp. if you have a profile set, you have to reselect it from the taskbar to enable any special functions. Occasionally it will be ALL parts, but is usually just one. (nasty way to lose toe brakes on a short runway too!)
I now have all my Saitek USB connections either on the front face of the computer or a USB hub right next to the monitor for easy access as a result. Oh, have also been told of one case where a cat walking across the pilots feet on the pedals had the same effect.
It does not seem to impair the internal electronics and is more a USB issue as the same static zap can (has) disrupted my USB headset on TeamSpeak.
Could this scramble the programming? perhaps, or at least the data exchanged at the time, but not likely. If the software is impaired, it can also be from attempts to deal with a transient issue (static) that was thought to be software. Could it be a more serious hardware issue? Yes, if there was a static charge large enough to hurt internal chips.
At this point it's hard to suggest a best route, but a removal (unplug hardware before removing software), regedit purge of the Saitek bits (as mentioned above) and a reinstall sure beats "throw it away, buy something else and write a nasty letter to Saitek". Be methodical.. test each part ( hard and soft) before adding the next bit. Then, look at the environment... dry, esp. in winter? Carpet? Wool socks? Pets? -- there are preventative measures that can be employed ( short of simming underwater which has it's own hazards)