Saitek Switch Box Issue

[uniform7]

Maybe someone has had this happen. I have the Saitek X52 Pro and the Pro Yoke systems connected and working great. I recently purchased the Saitek Switch box but when I use it with the other saitek controls when I exit and change planes and or relocate I crash fsx usually with a g3d.dll error. Payware, default and freeware aircraft no difference. The switth Box works fine except for that. Have tried SPAD and Saitek Software/drivers. Here is what Have done:

SaitekSwitch panel causes FSX to crash after
1st.Ending Flight
2nd.Changing Planes
3rd.changing Airports
CTDmostly a g3d.dll error
WhatI have checked:
Testedon another computer with X52 Pro and Pro Yoke flight systems withdrivers for all installed. Works fine. Build:
AMD6300 Radeon 7770 DirectX 64-bit Operating System Windows 7


FSUIPCregistered installed.
UIAutomationCore.dllinstalled
Issuewith Build:
IntelCore i7-4770K, ASUS MAXIMUS VI HERO Motherboard, , 8GB Memory , EVGAGeForce GTX 770 4GB Video Card, Corsair Enthusiast 750W 80+ BronzeCertified ATX Power Supply, Windows 7 64bit, Corsair Hydro Series H55CPU Cooler Overclocked to 4.2 at 1.25V

Tested using Keyboard andmouse with Saitek Switch Box. Works fine.
TestedX52 Pro only with Switch Box. Causes error
TestedPro Yoke only with Switch Box. Causes error
Testedboth X52 Pro and Pro Yoke connected. Causes error
Testedall three again with drivers removed. Causes error


FSUIPCregistered installed.
UIAutomationCore.dllinstalled

[Naismith]

My experience with the Switch box is that it is the least reliable of all of Saitek products. I find that it cannot be connected to the PC via a powered hub which is a pest. It doesn't like USB3 and insistes on USB2 only. Some of the switches appear to be cosmetic and have no function even with default aircraft. These are the cowl, taxi and strobe. Sometimes the gear switch works sometimes not. Seems if it is connected for a long time to the PC it just gives up altogether and I have to crawl under the desk and unplug/re plug the USB cable and inevitably bang my head, curse & holler like a sailor and frighten the dog. I also have the Radio panel and the Multi panel, X52 joystick and Saitek Cessna yoke and 2 of their throttles quadrants (3 if I include the one which came with the yoke). These all work flawlessly (thru' my powered hub Saitek!)
I also utilise SPAD and avoid Saitek own flakey software like the plague.

[uniform7]

My experience with the Switch box is that it is the least reliable of all of Saitek products. I find that it cannot be connected to the PC via a powered hub which is a pest. It doesn't like USB3 and insistes on USB2 only. Some of the switches appear to be cosmetic and have no function even with default aircraft. These are the cowl, taxi and strobe. Sometimes the gear switch works sometimes not. Seems if it is connected for a long time to the PC it just gives up altogether and I have to crawl under the desk and unplug/re plug the USB cable and inevitably bang my head, curse & holler like a sailor and frighten the dog. I also have the Radio panel and the Multi panel, X52 joystick and Saitek Cessna yoke and 2 of their throttles quadrants (3 if I include the one which came with the yoke). These all work flawlessly (thru' my powered hub Saitek!)
I also utilise SPAD and avoid Saitek own flakey software like the plague.

The USB# and USB3 thing is interesting. For me all the switches work at least so far just the crash it creates and only if I have the other Saitek gear connected. In fact I just used my old Thrustmaster with it and no issues.

[Inductotherm]

I have the switch box, along with autopilot, yoke and pedals, and throttle. all are connected to a powered hub then to pc. everything works. I do have to unplug the autopilot once fsx is up and replug it to get everything working right. also i manually start the fsx saitek service once fsx is up and before i start a flight. then cowl and all switches work great!

[uniform7]

I have the switch box, along with autopilot, yoke and pedals, and throttle. all are connected to a powered hub then to pc. everything works. I do have to unplug the autopilot once fsx is up and replug it to get everything working right. also i manually start the fsx saitek service once fsx is up and before i start a flight. then cowl and all switches work great!

These are the kind of errors I'm getting and like I said, only on the one computer and only when having the X52 or the Pro Yoke or both plugged in.


Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x6a1f1000
Faulting process id: 0xef8
Faulting application start time: 0x01d294ebabd44f76
Faulting application path: C:\FSX\fsx.exe
Faulting module path: unknown
Report Id: 341218cb-00ee-11e7-9073-e03f498468c0


Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58
Exception code: 0xc0000005
Fault offset: 0x0002e766
Faulting process id: 0xae8
Faulting application start time: 0x01d293bb0f095323
Faulting application path: C:\FSX\fsx.exe
Faulting module path: C:\FSX\g3d.dll
Report Id: 7653517d-ffb0-11e6-a8e8-e03f498468c0


Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: ntdll.dll, version: 6.1.7601.18798, time stamp: 0x5507b3e0
Exception code: 0xc015000f
Fault offset: 0x00084a6b
Faulting process id: 0x12e4
Faulting application start time: 0x01d294fbfc845557
Faulting application path: C:\FSX\fsx.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll

[uniform7]

These are the kind of errors I'm getting and like I said, only on the one computer and only when having the X52 or the Pro Yoke or both plugged in.


Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x6a1f1000
Faulting process id: 0xef8
Faulting application start time: 0x01d294ebabd44f76
Faulting application path: C:\FSX\fsx.exe
Faulting module path: unknown
Report Id: 341218cb-00ee-11e7-9073-e03f498468c0


Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58
Exception code: 0xc0000005
Fault offset: 0x0002e766
Faulting process id: 0xae8
Faulting application start time: 0x01d293bb0f095323
Faulting application path: C:\FSX\fsx.exe
Faulting module path: C:\FSX\g3d.dll
Report Id: 7653517d-ffb0-11e6-a8e8-e03f498468c0


Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: ntdll.dll, version: 6.1.7601.18798, time stamp: 0x5507b3e0
Exception code: 0xc015000f
Fault offset: 0x00084a6b
Faulting process id: 0x12e4
Faulting application start time: 0x01d294fbfc845557
Faulting application path: C:\FSX\fsx.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll

I looked on the CP that works with the Switch Box and wondering if any of these updates have anything to do with it.
Microsoft Visual C++ 2015 Redistributable (x86)-14.0.23506


Microsoft Visual C++ 2013 Redistributable (x86)-12.0.30501


Microsoft Visual C++ 2012 Redistributable (x86)-11.0.61030


Microsoft Visual C++ 2012 Redistributable (x64)-11.0.61030


Microsoft Visual C++ 2010 x86 Redistributable-10.0.30319


Microsoft Visual C++ 2010 x64 Redistributable-10.0.30319


Microsoft Visual C++ 2008 Redistributable-x86 9.0.30729.6161


Microsoft Visual C++ 2008 Redistributable-x64 9.0.30729.6161


Microsoft Visual C++ 2008 Redistributable-x86 9.0.30729.17


Microsoft Visual C++ 2008 Redistributable-x64 9.0.30729.17


Microsoft Visual C++ 2005 Redistributable x64


Microsoft Visual C++ 2005 Redistributable


MSXML 4.0 SP2 (KB954430)
MSXML 4.0 SP2 (KB973688)
MSXML 4.0 SP2 Parser and SDK