IPC request contains bad data

[Volante]

FSX freezes upon startup. Just after the FSX logo stays on screen for 5 econd, Logo window closes, and FSX remains 'active' on the Taskbar. The only way to close FSX is by means of ending the Task in Task Manager.

If SIOC 4.01 is running at the time of launching FSX, the FSUIPC status of SIOC says: 'IPC request contains bad data'.

The only thing changed since the last sucsessful run of FSX was an Leo Bodnar Axis card added. The card is now disconnected, and FSUIPC 4.900 reinstalled. Does the following log give any clues?

********* FSUIPC4, Version 4.90 by Pete Dowson *********

Running inside FSX on Windows 7

Module base=671F0000

User Name="xxxxx xxxxxx"

User Addr="xxxxx.xxxx@xxxx.no"

FSUIPC4 Key is provided

WideFS7 Key is provided

16 System time = 19/05/2013 23:53:36

16 FLT UNC path = "C:\Users\Antec\Documents\Flight Simulator X Files\"

47 Trying to connect to SimConnect Acc/SP2 Oct07 ...

47 FS UNC path = "\\COCKPIT1\Flightsim\FSX\"

359 LogOptions=00000000 00000001

359 SIM1 Frictions access gained

359 Wind smoothing fix is fully installed

359 G3D.DLL fix attempt installed ok

359 SimConnect_Open succeeded: waiting to check version okay

359 Trying to use SimConnect Acc/SP2 Oct07

Best regards

Vidar

[Pete Dowson]

FSX freezes upon startup. Just after the FSX logo stays on screen for 5 econd, Logo window closes, and FSX remains 'active' on the Taskbar. The only way to close FSX is by means of ending the Task in Task Manager.

Hmm. This looks similar to another recent report.

The only thing changed since the last sucsessful run of FSX was an Leo Bodnar Axis card added. The card is now disconnected, and FSUIPC 4.900 reinstalled.

Did remove of the axis card enable FSX to load okay?

In case it is the problem of an incomplete Registry entry for the device, can you please first download version 4.902 from the Download Links subforum, and see if that helps.

If not, please get some more logging for me. In the [General] section of the FSUIPC4.INI file, add:

Debug=Please

LogExtras=x200000

Then run FSX again and show me the FSUIPC4.LOG.

Thanks,

Pete

[Volante]

Did remove of the axis card enable FSX to load okay?

No, it did not.

4.902 Log:

********* FSUIPC4, Version 4.902 by Pete Dowson *********

Running inside FSX on Windows 7

Module base=66500000

User Name="xxxxx xxxxx"

User Addr="xxx@xxxxx.no"

FSUIPC4 Key is provided

WideFS7 Key is provided

16 System time = 20/05/2013 11:54:12

16 FLT UNC path = "C:\Users\Antec\Documents\Flight Simulator X Files\"

718 Trying to connect to SimConnect Acc/SP2 Oct07 ...

780 FS UNC path = "\\COCKPIT1\Flightsim\FSX\"

1092 #### Initialising Dlrectinput Axis Scanning ...

1108 joyGetDevCaps for device 0 returned error 165 [000000A5]

1108 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_05BA\Calibration\0"

1108 Found correct joystick Id 1

1108 ... and a "GUID" value

1124 ... okay, Acquired device!

1124 joyGetDevCaps for device 2 returned error 165 [000000A5]

1124 joyGetDevCaps for device 3 returned error 165 [000000A5]

1124 joyGetDevCaps for device 4 returned error 165 [000000A5]

1124 joyGetDevCaps for device 5 returned error 165 [000000A5]

1124 joyGetDevCaps for device 6 returned error 165 [000000A5]

1124 joyGetDevCaps for device 7 returned error 165 [000000A5]

1124 joyGetDevCaps for device 8 returned error 165 [000000A5]

1124 joyGetDevCaps for device 9 returned error 165 [000000A5]

1124 joyGetDevCaps for device 10 returned error 165 [000000A5]

1124 joyGetDevCaps for device 11 returned error 165 [000000A5]

1124 joyGetDevCaps for device 12 returned error 165 [000000A5]

1124 joyGetDevCaps for device 13 returned error 165 [000000A5]

1124 joyGetDevCaps for device 14 returned error 165 [000000A5]

1124 joyGetDevCaps for device 15 returned error 165 [000000A5]

1124 #### Completed Dlrectinput Axis Scanning

1124 LogOptions=00000000 02000011

1124 SIM1 Frictions access gained

1124 Wind smoothing fix is fully installed

1124 G3D.DLL fix attempt installed ok

1124 SimConnect_Open succeeded: waiting to check version okay

1124 Trying to use SimConnect Acc/SP2 Oct07

Vidar

[Pete Dowson]

No, it did not.

...

	 1124 #### Completed Dlrectinput Axis Scanning
	  ...
	 1124 SimConnect_Open succeeded: waiting to check version okay
	 1124 Trying to use SimConnect Acc/SP2 Oct07[/CODE]

Okay. so it isn't anything to do with the device scanning. It looks like it isn't getting an initial response from SimConnect, only the OK from the Open call (which means only that it was accepted). The next few steps should read something like this:

[CODE] 6614 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
6614 Initialising SimConnect data requests now
6614 FSUIPC Menu entry added
6724 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y[/CODE]

which would confirm SimConnect was okay. Meanwhile FSX itself would have been loading the default flight, and the next logging would show the Flight and the Aircraft details, as notified by SimConnect to FSUIPC.

One problem which can cause a crash (normally) rather than a hang at around this point, is a corrupted weather file Try deleting or renaming the .WX file associated with the default flight being loaded. Another one is a Logbook corruption -- rename Logbook.bin.

If these steps don't help, please obtain a SimConnect log to see where it is getting to in SimConnect. It may be a SimConnect corruption. There's a thread in the FAQ subforum whch tells you how to get a log.

Pete

[Volante]

Still puzzled.

I first renamed the WX file as adviced, which was followed by a 'Flight Simulator has detected a problem...... Name: FSUIPC4.DLL Version 4.902...... Do you want to run this software?' error.

No luck either response.

Renamed Logbook.bin gave same result. Renaming both files back to original did not take away the Error message.

Now the SimConnect Log. I obviously had to respond Yes to the Error question to get this:

0.00000 SimConnect version 10.0.61259.0

0.00736 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64

0.00922 Server: Scope=local, Protocol=IPv6, Address=::1, Port=49960, MaxClients=64

0.01041 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=49961, MaxClients=64

0.09841 Panels data export found and set to 20B319D8

0.09883 DLL Loaded: Path="PMDG\DLLs\PMDG_HUD_interface.dll" Version="2.0.0.1"

0.09891 File not found: Path="CPflight\CPF_DLL_FSX.dll"

- - - - -

My CPF_DLL_FSX.dll resides in 'D:\Program Files (x86)\CPFlight\' as always.

Any more clues, please?

Thanks for your effort!

Vidar

[Pete Dowson]

I first renamed the WX file as adviced, which was followed by a 'Flight Simulator has detected a problem...... Name: FSUIPC4.DLL Version 4.902...... Do you want to run this software?' error.

No luck either response.

Ah, at least a crash is better than a hang, because the Windows error log will show us something. Can you check please?

Also, it is now shown that it isn't FSUIPC with the problem -- when you say 'No' to that question fSUIPC isn't even loaded let alone started!

If it only crashed on the "Yes" answer it would looks very much like the usual SimConnect timing bug -- please review the FAQ thread entitled "FSX fails to run after FSUIPC4 first installed". Was a new FSUIPC4.LOG file produced when you answered "Yes"? If so you should show it.

Renamed Logbook.bin gave same result. Renaming both files back to original did not take away the Error message.

But something is obviously different.

Now the SimConnect Log. I obviously had to respond Yes to the Error question to get this:

Why "obviously" had to respond "Yes"? If SimConnect is run at all (as it always will be) then it will produce a log when requested!

The log you show proves that FSUIPC wasn't even loaded let alone run. The only SimConnect client loaded was PMDG\DLLs\PMDG_HUD_interface.dll. Try without that -- it is more the suspect now.

0.09891 File not found: Path="CPflight\CPF_DLL_FSX.dll"

- - - - -

My CPF_DLL_FSX.dll resides in 'D:\Program Files (x86)\CPFlight\' as always.

Well the entry in your DLL.XML doesn't say that -- in there it is stated to be in a CPFlight folder within the FSX folder. Seems you've not installed that correctly?

I think you've got a lot else going on there than you previously thought!

Regards

Pete

[Volante]

I tried tidying up a little, like uninstalling all PMDG installations and cheating the system by putting the CPFlight driver in the refferred folder.

SimConnect still wants the PMDG dll.

Starting FSX, it's splash screen is up for 5-6 seconds, then the application closes down, leaving me with these Log files:

********* FSUIPC4, Version 4.902 by Pete Dowson *********

Running inside FSX on Windows 7

Module base=672E0000

User Name="xxxxxxxxx"

User Addr="xxx@xx.no"

FSUIPC4 Key is provided

WideFS7 Key is provided

31 System time = 20/05/2013 16:41:49

31 FLT UNC path = "C:\Users\Antec\Documents\Flight Simulator X Files\"

62 Trying to connect to SimConnect Acc/SP2 Oct07 ...

78 FS UNC path = "\\COCKPIT1\Flightsim\FSX\"

390 #### Initialising Dlrectinput Axis Scanning ...

390 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_05B5\Calibration\0"

390 Found correct joystick Id 0

390 ... and a "GUID" value

390 ... okay, Acquired device!

390 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_05BA\Calibration\0"

390 Found correct joystick Id 1

390 ... and a "GUID" value

390 ... okay, Acquired device!

390 joyGetDevCaps for device 2 returned error 165 [000000A5]

390 joyGetDevCaps for device 3 returned error 165 [000000A5]

390 joyGetDevCaps for device 4 returned error 165 [000000A5]

390 joyGetDevCaps for device 5 returned error 165 [000000A5]

390 joyGetDevCaps for device 6 returned error 165 [000000A5]

390 joyGetDevCaps for device 7 returned error 165 [000000A5]

390 joyGetDevCaps for device 8 returned error 165 [000000A5]

390 joyGetDevCaps for device 9 returned error 165 [000000A5]

390 joyGetDevCaps for device 10 returned error 165 [000000A5]

390 joyGetDevCaps for device 11 returned error 165 [000000A5]

390 joyGetDevCaps for device 12 returned error 165 [000000A5]

390 joyGetDevCaps for device 13 returned error 165 [000000A5]

390 joyGetDevCaps for device 14 returned error 165 [000000A5]

390 joyGetDevCaps for device 15 returned error 165 [000000A5]

390 #### Completed Dlrectinput Axis Scanning

390 LogOptions=00000000 02000011

390 SIM1 Frictions access gained

390 Wind smoothing fix is fully installed

390 G3D.DLL fix attempt installed ok

390 SimConnect_Open succeeded: waiting to check version okay

390 Trying to use SimConnect Acc/SP2 Oct07

- - - - - - - -

0.00000 SimConnect version 10.0.61259.0

0.00755 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64

0.00937 Server: Scope=local, Protocol=IPv6, Address=::1, Port=49544, MaxClients=64

0.01058 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=49545, MaxClients=64

0.01179 File not found: Path="PMDG\DLLs\PMDG_HUD_interface.dll"

25.41733 DLL Loaded: Path="CPflight\CPF_DLL_FSX.dll" Version="<Unknown>"

25.49895 Panels data export found and set to 20B319D8

25.85651 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.9.0.2"

Still puzzeled.

Vidar

[Pete Dowson]

SimConnect still wants the PMDG dll.

It will do unless you remove its entry in the DLL.XML file.

Starting FSX, it's splash screen is up for 5-6 seconds, then the application closes down, leaving me with these Log files:

And what does the Windows error log show? I did ask before.

The FSUIPC4 log shows it is simply waiting for SimConnect. It can't do anything until Simconnect sends it the normal opening sequences. The Simconnect log finishes where it should be recording the Open request from FSUIPC, at least, possibly also CPF_DLL_FSX.dll.

It's a bit strange that the SimConnect log shows a last entry at 25 seconds after FSX is started:

25.85651 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.9.0.2"

but you see it closed down within 5-6 seconds? That's a lot of difference.

In a normal case the Simconnect log proceeds thus:

0.00000 SimConnect version 10.0.61259.0

0.00914 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64

0.04521 Server: Scope=local, Protocol=IPv6, Address=::1, Port=7858, MaxClients=64

0.04935 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=7859, MaxClients=64

1.20673 Panels data export found and set to 20B319D8

5.67281 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.9.0.2"

> 12.93797 [ 0, 1]Open: Version=0x00000004 Name="FSUIPC4"

I'm suspecting now a corrupted FSX installation in the SimConnect area, but the Windows evidence will help prove this one way or the other.

After FSUIPC has made the Open call, it does nothing except await the response, which arrives aynchronously -- over 7 seconds later in my example above. I really don't think FSUIPC can do anything in between.

Just in case it gives me any ideas, could you paste your FSUIPC4.INI file into a message please?

Regards

Pete

[Volante]

This time I restarted the PC before starting FSX.exe. (I had the feeling that the second try had different timeout than the first.)

After changing language setting, I remembered to save the Windows error message too.... :???:

********* FSUIPC4, Version 4.902 by Pete Dowson *********

Running inside FSX on Windows 7

Module base=65BA0000

User Name="xxx xxx"

User Addr="xxx@xxx.no"

FSUIPC4 Key is provided

WideFS7 Key is provided

78 System time = 20/05/2013 18:17:14

78 FLT UNC path = "C:\Users\Antec\Documents\Flight Simulator X Files\"

109 Trying to connect to SimConnect Acc/SP2 Oct07 ...

124 FS UNC path = "\\COCKPIT1\Flightsim\FSX\"

421 #### Initialising Dlrectinput Axis Scanning ...

421 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_05B5\Calibration\0"

421 Found correct joystick Id 0

421 ... and a "GUID" value

421 ... okay, Acquired device!

421 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_16C0&PID_05BA\Calibration\0"

421 Found correct joystick Id 1

421 ... and a "GUID" value

421 ... okay, Acquired device!

421 joyGetDevCaps for device 2 returned error 165 [000000A5]

421 joyGetDevCaps for device 3 returned error 165 [000000A5]

421 joyGetDevCaps for device 4 returned error 165 [000000A5]

421 joyGetDevCaps for device 5 returned error 165 [000000A5]

421 joyGetDevCaps for device 6 returned error 165 [000000A5]

421 joyGetDevCaps for device 7 returned error 165 [000000A5]

421 joyGetDevCaps for device 8 returned error 165 [000000A5]

421 joyGetDevCaps for device 9 returned error 165 [000000A5]

421 joyGetDevCaps for device 10 returned error 165 [000000A5]

421 joyGetDevCaps for device 11 returned error 165 [000000A5]

421 joyGetDevCaps for device 12 returned error 165 [000000A5]

421 joyGetDevCaps for device 13 returned error 165 [000000A5]

421 joyGetDevCaps for device 14 returned error 165 [000000A5]

421 joyGetDevCaps for device 15 returned error 165 [000000A5]

421 #### Completed Dlrectinput Axis Scanning

421 LogOptions=00000000 02000011

421 SIM1 Frictions access gained

421 Wind smoothing fix is fully installed

421 G3D.DLL fix attempt installed ok

421 SimConnect_Open succeeded: waiting to check version okay

421 Trying to use SimConnect Acc/SP2 Oct07

- - - - - - - - -

0.00000 SimConnect version 10.0.61259.0

0.00738 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64

0.00922 Server: Scope=local, Protocol=IPv6, Address=::1, Port=49791, MaxClients=64

0.01037 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=49792, MaxClients=64

0.01151 File not found: Path="PMDG\DLLs\PMDG_HUD_interface.dll"

0.15018 DLL Loaded: Path="CPflight\CPF_DLL_FSX.dll" Version="<Unknown>"

0.26665 Panels data export found and set to 20B319D8

0.62139 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.9.0.2"

- - - - - - - - -

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

<Provider Name="Desktop Window Manager" />

<EventID Qualifiers="16384">9010</EventID>

<Level>4</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2013-05-20T16:17:08.000000000Z" />

<EventRecordID>12466</EventRecordID>

<Channel>Application</Channel>

<Computer>COCKPIT1</Computer>

<Security />

</System>

- <EventData>

<Data>Flight Simulator X v10.0.61637.0</Data>

</EventData>

</Event>

- - - - - - - -

[General]

UpdatedByVersion=4902

History=QHHUK72UJA47YSI071UFD

MouseWheelTrim=No

MouseWheelTrimSpeed=1

JoystickTimeout=20

PollGFTQ6=Yes

BlankDisplays=No

FixControlAccel=No

FixMachSpeedBug=No

VisibilityOptions=No

OneCloudLayer=No

CloudTurbulence=No

CloudIcing=No

GenerateCirrus=No

SuppressCloudTurbulence=No

MaxIce=-4

MinIce=-4

UpperWindGusts=No

SuppressWindTurbulence=Yes

SuppressWindVariance=Yes

WindTurbulence=No

TurbulenceRate=1.0,5.0

TurbulenceDivisor=20,20,40,40

SuppressAllGusts=No

MaxSurfaceWind=0

WindLimitLevel=200

WindDiscardLevel=400

WindAjustAltitude=No

WindAjustAltitudeBy=2000

SmoothBySimTime=No

WindSmoothing=Yes

WindSmoothness=1

WindSmoothAirborneOnly=Yes

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=No

ShowPMcontrols=Yes

SpoilerIncrement=512

MagicBattery=No

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=No

BrakeReleaseThreshold=75

SaveDataWithFlights=Menu

ZapSound=firework

ShortAircraftNameOk=No

UseProfiles=No

TCASid=Flight

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

Console=No

EnableMouseLook=No

AxesWrongRange=No

InitDelay=0

GetNearestAirports=Yes

LuaRerunDelay=66

DeleteVehiclesForAES=Yes

InitDelayDevicesToo=No

MouseWheelMove=No

AutoScanDevices=Yes

OOMcheck=Yes

UseMidMouseBtn=Yes

Debug=Please

LogExtras=x200000

UseSystemTime=No

[JoyNames]

AutoAssignLetters=No

1=BU0836A Interface

1.GUID={8DD0F7B0-82B5-11E2-8001-444553540000}

0=BU0836 Interface

0.GUID={027F3380-8917-11E2-8001-444553540000}

[buttons]

Buttonrepeat=20,10

1=P0,6,C2021,0

2=P0,8,C2021,0

3=P0,4,Cx01003590,x00

4=U0,4,Cx01003590,x01

5=P0,3,Cx01003594,x00

6=U0,3,Cx01003594,x01

7=P0,11,Cx01000BC8,x00

8=U0,11,Cx01000BC8,x01

9=P2000,6,C2021,1

10=U2000,6,C2021,0

11=P2000,11,Cx02000BC8,x0FFF

12=U2000,11,Cx02000BC8,x0000

13=P2000,4,Cx02003590,x0000

14=U2000,4,Cx02003590,x0001

15=P2000,3,Cx01003594,x00

16=U2000,3,Cx01003594,x01

17=P2000,8,Cx01000000,x01

18=U2000,8,Cx01000000,x00

19=P2000,2,C66652,1

20=U2000,2,C66652,0

21=P0,5,C2020,0

22=P0,7,C2020,0

23=P2000,7,C2020,0

24=P2000,5,C2020,0

26=P1,2,C65957,0

27=P1,4,Cx010004F2,x01

28=U1,4,Cx010004F2,x00

[AutoSave]

AutoSaveEnabled=No

Next=1

Interval=60

Files=10

SaveOnGround=No

[GPSout]

GPSoutEnabled=No

Port=COM6

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[GPSout2]

GPSoutEnabled=No

Port=<none set>

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[WideServer]

WideFSenabled=Yes

AdvertiseService=1

Port=8002

Port2=9002

[ClientNames]

1=COCKPIT5

2=ION1

3=COCKPIT4

4=ION2

5=COCKPIT2-PC

[buttons.Boeing 737-800 Paint1]

0=P0,5,C2020,0

[sounds]

Path=D:\Flightsim\FSX\Sound\

Device1=Primær lyddriver

Device2=Realtek Digital Output(Optical) (Realtek High Definition Audio)

Device3=Realtek Digital Output (Realtek High Definition Audio)

[Programs]

//Run1=HIDE,"D:\Program Files (x86)\Aivlasoft\EFB\Aivlasoft.Efb.DataProvider.exe"

//Run2=HIDE,"D:\Program Files (x86)\SIOC\Sioc.exe"

//Run3=HIDE,"D:\Program Files (x86)\Prosim737\Prosim737.exe"

//Run4=HIDE,"D:\Program Files (x86)\ProsimMCP\ProsimMCP.exe"

//Run5=HIDE,"D:\Program Files (x86)\ProsimAudio\ProsimAudio.exe"

[JoystickCalibration.Jetstream-737]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

ElevatorTrim=-16380,0,512,16380/8

Rudder=-6270,-376,-88,8528/16

LeftBrake=-352,4048

RightBrake=-808,3115/16

Flaps=-13917,12432

Spoilers=8248,16380

[Axes]

0=0R,272,D,3,0,0,0

1=0U,256,D,7,0,0,0

2=0S,256,D,8,0,0,0

[buttons.Jetstream-737]

0=P1,1,C65752,1

1=U1,1,C65752,0

2=P1,5,Cx010004F2,x01

3=U1,5,Cx010004F2,x00

4=P1,8,Cx02005410,x0000

5=U1,8,Cx02005410,x0001

[Axes.Jetstream-737]

0=1X,256,F,x02000BD0,0,0,0

1=1Y,256,F,x01000BDC,0,0,0

- - - - - - - - -

Thanks!

Vidar

[Pete Dowson]

I remembered to save the Windows error message too.... :???:

That's a strange Windows error message. It doesn't identify the module which failed, nor the error code, nor the offset in the module. Are you sure you got the right entry? That one certainly is of no use at all as it contains no information.

I can see nothing wrong with the FSUIPC4.INI file either. I'm afraid it is getting near the point where an FSX reapir might be called for, or even a reinstall. (Ugh).

One last attempt. Use this parameter:

InitDelay=0

to delay FSUIPC's attempt to use SmConnect. Try 30 (30 seconds), for instance. see if it lasts longer.

Regards

Pete

[Volante]

Still no clue, I'm afraid.

Thank you very much for your effort, Pete! I really appreciate your serious approach and help.

This time, it seems the best thing to do is a full cleanup of the system. Oh well. It has been running for two years without a hickup. With all third party stuff being installed and removed, it would happen sooner or later. :razz:

Best regards

Vidar

Oslo - Norway

[Pete Dowson]

This time, it seems the best thing to do is a full cleanup of the system. Oh well. It has been running for two years without a hickup. With all third party stuff being installed and removed, it would happen sooner or later. :razz:

I'm reaching the point on my cockpit PC where I might have to bite the bullet and reinstall everything. After over two years with a perfectly working setup I'm now suffering from blurries (blurred ground textures) which occur within 5 to10 minutes of normal flying. I really have no idea what's changed to do this. I've tried backtracking my FSX CFG, and my video driver, and terminating as many other processes and services as I dare, yet it still occurs. I've followed all the hints I found everywhere. It's exasperating!

Regards

Pete