FSX SP2 does CTD with FSUIPC ...Please, Help!

[trisho0]

I have the FSX SP2 installed in Windows 10 been working flawless for many years and suddenly it started CTD.
Since 2 or 3 days ago after loaded FSX and doing nothing else the SIM closes by itself without any message, simply CTD with no apparent reasons. Tried FSX loading again and it looks like a random CTD.

So, I started different things to isolate finding the file giving the CTD.
I renamed to Off the files: dll.xml, exe.xml, scenery.cfg and wxstationlist.BIN

I found from the dll.xml file edited as:

  <Launch.Addon>
    <Name>FSUIPC 4</Name>
    <Disabled>True</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>

the FSX sim loaded just fine.

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

I installed the FSUIPC last version 4.977 (Registered) and still no success.

I also, found from C:\Windows\WinSxS\ folder, 4 files SimConnect.dll and I copied one file at a time to D:\Microsoft Games\Microsoft Flight Simulator X\ folder for testing and still no success.

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

I checked Windows Event Viewer and it shows:

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: KERNEL32.DLL, version: 10.0.22000.318, time stamp: 0x28518903
Exception code: 0xc0000005
Fault offset: 0x00098d51
Faulting process id: 0x46cc
Faulting application start time: 0x01d7eb8eb8bdb4fc
Faulting application path: D:\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\WINDOWS\System32\KERNEL32.DLL
Report Id: e12f7e9d-63d1-4029-abec-cbd19f7549b2
Faulting package full name: 
Faulting package-relative application ID: 

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Contents of the FSUIPC Installation Log:

Installer for FSUIPC4.DLL version 4.977

Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=D:\Microsoft Games\Microsoft Flight Simulator X

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\DovetailGames\FSX
     Parameter"AppPath"
Not there, so looking in:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"AppPath"
... NOT found! ...
===========================================================

INSTALLATION FOR FSX:
SetupPath="D:\Microsoft Games\Microsoft Flight Simulator X\"
Checking version of the FSX EXE:
... Version 10.0.61637.0  (Need at least 10.0.60905.0)
Checking compatibility with installed SimConnect:
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\Fusion\*SimConnect*"
    Found the path, now trying "C:\WINDOWS\WinSxS\Fusion\x86_microsoft.esp.simconnect_67c7c14424d61b5b_none_fe0c6ec39ae22400\10.0\10.0.60905.0\SimConnect.dll"
    No SimConnect.dll found there
    Found the path, now trying "C:\WINDOWS\WinSxS\Fusion\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_none_48d5d2360f51e4d0\10.0\10.0.60905.0\SimConnect.dll"
Found SimConnect build 10.0.60905.0
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\*SimConnect*10.0.60905.0*"
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\Fusion\*SimConnect*"
    Found the path, now trying "C:\WINDOWS\WinSxS\Fusion\x86_microsoft.esp.simconnect_67c7c14424d61b5b_none_fe0c6ec39ae22400\10.0\10.0.62607.0\SimConnect.dll"
    No SimConnect.dll found there
    Found the path, now trying "C:\WINDOWS\WinSxS\Fusion\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_none_48d5d2360f51e4d0\10.0\10.0.62607.0\SimConnect.dll"
    No SimConnect.dll found there
    Found the path, now trying "C:\WINDOWS\WinSxS\Fusion\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_none_7a98ffdea9fe1e16\10.0\10.0.62607.0\SimConnect.dll"
    No SimConnect.dll found there
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\*SimConnect*10.0.62607.0*"
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\Fusion\*SimConnect*"
    Found the path, now trying "C:\WINDOWS\WinSxS\Fusion\x86_microsoft.esp.simconnect_67c7c14424d61b5b_none_fe0c6ec39ae22400\10.0\10.0.61242.0\SimConnect.dll"
    No SimConnect.dll found there
    Found the path, now trying "C:\WINDOWS\WinSxS\Fusion\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_none_48d5d2360f51e4d0\10.0\10.0.61242.0\SimConnect.dll"
Found SimConnect build 10.0.61242.0
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\*SimConnect*10.0.61242.0*"
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\Fusion\*SimConnect*"
    Found the path, now trying "C:\WINDOWS\WinSxS\Fusion\x86_microsoft.esp.simconnect_67c7c14424d61b5b_none_fe0c6ec39ae22400\10.0\10.0.61259.0\SimConnect.dll"
    No SimConnect.dll found there
    Found the path, now trying "C:\WINDOWS\WinSxS\Fusion\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_none_48d5d2360f51e4d0\10.0\10.0.61259.0\SimConnect.dll"
    No SimConnect.dll found there
    Found the path, now trying "C:\WINDOWS\WinSxS\Fusion\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_none_7a98ffdea9fe1e16\10.0\10.0.61259.0\SimConnect.dll"
Found SimConnect build 10.0.61259.0
    Looking for SimConnect.dll with "C:\WINDOWS\WinSxS\*SimConnect*10.0.61259.0*"
Checking if there's already a version of FSUIPC4 installed in:
       D:\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL
... Version 4.976 found.
FSX Modules folder already exists.
Okay -- installed FSUIPC4 into "D:\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Patricio Valdes\AppData\Roaming"
Now finding \Microsoft\FSX\FSX.CFG for all users, including this one
Looking in "C:\Users\Administrator\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Patricio Valdes\AppData\Roaming"
Found FSX.CFG in "C:\Users\Patricio Valdes\AppData\Roaming\Microsoft\FSX\FSX.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "The 2016 List of FSX and P3D Controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "Offset Mapping for PMDG 747QOTSII.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
   Installed "FSUIPC4_Loader.dll" okay
===========================================================

All installer tasks completed.
Registration dialog exit: selected  BOTH CHECK
Checking FSUIPC registration ...
Checking WIDEFS registration ...
Registration check for FSUIPC4 and WideFS was successful! (result code 00)

*************** End of Install Log ***************

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Contents of the FSUIPC INI file:

[General]
UpdatedByVersion=4977
History=WZMJRDI48QQZUXW7TWQB7
InitDelayDevicesToo=No
Annotate=Yes
NewInterceptTextMenu=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=No
FixMachSpeedBug=No
NewDeleteVehiclesForAES=No
AutoScanDevices=Yes
VisibilityOptions=No
OneCloudLayer=No
CloudTurbulence=No
CloudIcing=No
GenerateCirrus=No
SuppressCloudTurbulence=No
MaxIce=-4
MinIce=-4
UpperWindGusts=No
SuppressWindTurbulence=No
SuppressWindVariance=No
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=No
WindSmoothness=2
WindSmoothAirborneOnly=Yes
PressureSmoothness=0
TemperatureSmoothness=0
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
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=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
WideLuaGlobals=Yes
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
InitDelay=0
GetNearestAirports=Yes
LogOptionProtect=Yes
OOMcheck=Yes
OOMcheckInterval=10
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
LuaRerunDelay=66
Console=No
FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0
SimConnectUsed=10.0.61259.0

[Traffic Limiter]
AirportPreference=50
PlannedAirportsPreference=50
GroundPreference=50
NearerPreference=50
TargetFrameRate=0
TrafficLimit=0

[JoyNames]
AutoAssignLetters=No
0=VKBsim Gladiator
0.GUID={FD230790-16AF-11E9-8001-444553540000}

[Axes]
PollInterval=10
RangeRepeatRate=10

[Buttons]
PollInterval=25
ButtonRepeat=20,10

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No
Port=COM1
Speed=4800
Interval=2000
PosTo6Decimal=No
SimModeIndicator=No
Sentences=

[GPSout2]
GPSoutEnabled=No
Port=<none set>
Speed=4800
Interval=2000
PosTo6Decimal=No
SimModeIndicator=No
Sentences=

[WideServer]
WideFSenabled=Yes
AdvertiseService=1
Port=8002
Port2=9002

[Sounds]
Path=D:\Microsoft Games\Microsoft Flight Simulator X\Sound\
Device1=Primary Sound Driver
Device2=Speakers/Headphones (Realtek(R) Audio)
Device3=Dell AW2721D (NVIDIA High Definition Audio)
Device4=Realtek Digital Output (Realtek(R) Audio)

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Tried the sentences added to FSUIPC.ini file (without success):

[General]
WeatherReadFactor=0
NoWeatherAtAll=Yes

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Any other thoughts to give a try is great appreciated.

Patricio Valdes

 

[Pete Dowson]

3 hours ago, trisho0 said:

I checked Windows Event Viewer and it shows:

You provided lots of information but sadly not the most important parts:

1. What happens before the crash? i.e. when does it actually crash?

2. The FSUIPC4.LOG file, showing how far it got.

I suspect it must be a corrupted weather file: try deleting all of the *.wx files in your FSX Documents folder.

Pete

 

[trisho0]

2 hours ago, Pete Dowson said:

You provided lots of information but sadly not the most important parts:

1. What happens before the crash? i.e. when does it actually crash?

2. The FSUIPC4.LOG file, showing how far it got.

I suspect it must be a corrupted weather file: try deleting all of the *.wx files in your FSX Documents folder.

Pete

 

1. Before sim CTD I just launch FSX and after 1 to 3 minutes without any other actions FSX suddenly closes without message.

2. FSUIPC.log attached.

3. Deleted all files with wx extension from C:\Users\Patricio Valdes\Documents\Flight Simulator X Files and still not a success.

4. I had to change the "False" back to "True" in the FSUIPC Disabled line of dll.xml in order to keep FSX free of CTD.

I can't see what to edit or try to keep FSUIPC working friendly with FSX (lol).

Patricio Valdes

 

FSUIPC4.log

Edited December 8, 2021 by trisho0
grammar corrections

[Pete Dowson]

9 hours ago, trisho0 said:

2. FSUIPC.log attached

The log stops immediately after your Flight and Aircraft hsave loaded:

      969 D:\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT
      969 D:\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

This does really indicate some corruption in your FSX installation, and the weather files are really the most likely. You could try adding this to the [General] section in the FSUIPC4.INI file:

NoWeatherAtAll=Yes

This will stop FSUIPC making any attempt to get weather data whatsoever .

Pete

 

[trisho0]

5 hours ago, Pete Dowson said:

The log stops immediately after your Flight and Aircraft hsave loaded:

      969 D:\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT
      969 D:\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

This does really indicate some corruption in your FSX installation, and the weather files are really the most likely. You could try adding this to the [General] section in the FSUIPC4.INI file:

NoWeatherAtAll=Yes

This will stop FSUIPC making any attempt to get weather data whatsoever .

Pete

 

I mentioned at the very end of my first statement as:

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Tried the sentences added to FSUIPC.ini file (without success):

[General]
WeatherReadFactor=0
NoWeatherAtAll=Yes

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Patricio Valdes

 

 

[Pete Dowson]

Judging by your INI file, and although you've registered FSUIPC, you don't appear, at least from the settings, to actually make use of any of the purchased facilities. Is that so? Perhaps you could try a test with your FSUIPC4.key file removed or renamed so it runs as if unregistered.

Currently I'm thinking it must be some corruption in your FSX installation. I think you will probably need to try a full re-install.

Pete

 

 

[trisho0]

52 minutes ago, Pete Dowson said:

Judging by your INI file, and although you've registered FSUIPC, you don't appear, at least from the settings, to actually make use of any of the purchased facilities. Is that so? Perhaps you could try a test with your FSUIPC4.key file removed or renamed so it runs as if unregistered.

Currently I'm thinking it must be some corruption in your FSX installation. I think you will probably need to try a full re-install.

Pete

 

 

Good, I will activate the FSUIPC from dll.xml file and with the registration removed. So, in case if it still FSX doing CTD because of FSUIPC then I will leave FSUIPC disactivated. So far I can use FSX without issues as longer if the FSUIPC is sleeping (lol). To do a FSX reinstallation will be a pain reinstalling payware addons and aircrafts plus ORBX. On the another hand, if I have to do a FSX reinstallation instead then simply the FSX sim will go out of my system. I never did any FSUIPC settings anyway.

I will see what happen with FSUIPC registration removed ...

Best, Patricio

[trisho0]

I renamed the FSUIPC Key file and removed INI file. Launched FSX leaving loading not touching anything else just watch on the monitor screen. FSX had CTD and silent.

Attached INI and Log files.

Regards, Patricio

FSUIPC4.ini FSUIPC4.log

[Pete Dowson]

11 hours ago, trisho0 said:

Attached INI and Log files.

Exactly the same results. Sorry, but I think it must be a corrupted FSX file -- probably SimConnect. FSUIPC is totally dependent on that.

Pete

 

[trisho0]

40 minutes ago, Pete Dowson said:

Exactly the same results. Sorry, but I think it must be a corrupted FSX file -- probably SimConnect. FSUIPC is totally dependent on that.

Pete

 

Hi Pete, I have 2 different backup of FSX which they were working fine with FSUIPC. So, I was overwriting the Weather folder and the FSX.exe file and it appears CTD anyway.

What files can be replaced for further testings?

Patricio

[Pete Dowson]

3 minutes ago, trisho0 said:

What files can be replaced for further testings?

Impossible to tell without doing some debugging with, say Visual Studio.  With P3D it would be easy enough to uninstall and reinstall just the Client, which consists of the EXE and all the DLLs. But that's assuming a code module corruption, which seems less likely than a data one, like the FLT file and the aircraft you are loading.

Bearing that in mind you could change the default flight. Run FSX without FSUIPC then select a different flight and aircraft, and mark it as the default.

Pete

 

[trisho0]

4 hours ago, Pete Dowson said:

Impossible to tell without doing some debugging with, say Visual Studio.  With P3D it would be easy enough to uninstall and reinstall just the Client, which consists of the EXE and all the DLLs. But that's assuming a code module corruption, which seems less likely than a data one, like the FLT file and the aircraft you are loading.

Bearing that in mind you could change the default flight. Run FSX without FSUIPC then select a different flight and aircraft, and mark it as the default.

Pete

 

Good idea, replacing EXE and DLL files from my backup to the FSX folder and testing further. Selecting another flight and aircraft marking as default. Then activating FSUIPC and see what happen. I will report results.

Patricio

[aldox62]

Hi, 

I am joining this thread because I am experiencing since months now exactly this error, same Fault offset: 0x00098d51.

I am now running W11 Pro, FSX SP2 boxed, FSUIPC registered latest version, ASN16 public beta (works with W11), PMDG 737 all versions, PMDG 777 all versions, PMDG 747 QUOTS latest version, GSX level 2 latest version, various ORBX packages, one airport scenery (LIMF, Turin, Italy). I have 4 different simconnect versions installed, did not dare to touch them so far.

The issue started when I (my fault) upgraded W7 to W10, since then I've tried almost everything:

- moved to FSX:SE and then back to FSX SP2 boxed after orderly removing everything, cleaning up down to registry level and reinstalling the whole environment a piece at a time with intermediate tests

- tried various tweaks, now  my FSX.cfg just has the highmemfix tweak

- uninstalled/reinstalled all the add-on packages: aircrafts, utilities, etc. I reached the PMDG max activation limit.. 🙂

- interacted with PMDG support via tickets

- enabled/disabled the various utilities one at a time

- followed CTD guides as available on internet

- moved back and forth with different video (GTX570) and audio drivers

- added Uiautomationcore.dll as recommended by PMDG

- tested HW: memory (32GB), disks, mobo, drivers

- extensively searched on FSX major forums

- other debug actions I do not remember now..

Basically, I have great performance, 30fps almost everywhere, but the CTD hits randomly - usually not earlier than 1.5-4 hours of flying my EGLL-KSFO test flight with T7-200 or 747. Shorter flights with 737 usually go to the landing without issues. I also created a second test flight, EGLL-SBGR to exclude issues with the main saved test flight, to no avail.

Right yesterday I got the latest W11 update that touched kernel32.dll as well, and hoped for an improvement: no, the test flight failed after 3 hours. This adds to my idea that it is not a W11 issue.

The CTD appears randomly: either when I'm not sitting at the PC, or when I take some action on main FSX screen say change the flight level or work with FMC (not touching FSX menus) or when I scroll ASN16 map to keep the aircraft in view, or even when I do other things on the PC that may not directly touch the FSX environment windows on the desktop. 

That's it, just wanted to share my experience.. If there are any further debug hints these are more than welcome!

Kind regards,

Aldo

[Pete Dowson]

12 hours ago, aldox62 said:

but the CTD hits randomly - usually not earlier than 1.5-4 hours of flying
...
 

12 hours ago, aldox62 said:

The CTD appears randomly: either when I'm not sitting at the PC, or when I take some action on main FSX screen say change the flight level or work with FMC (not touching FSX menus) or when I scroll ASN16 map to keep the aircraft in view, or even when I do other things on the PC that may not directly touch the FSX environment windows on the desktop. 

Please always supply the FSUIPC4.log file after a crash (ZIP if too big), and the actual Event Viewer details from Windows, not just an offset!

As this appears to be at random it does sound likely to be a corrupted weather file, which in turn cuases something in memory to be corrupted when FSUIPC asks SimConnect to supply weather.

To test for this, try adding

NoWeatherAtAll=Yes

to the [General] section of your FSUIPC4.INI file. If this solves it then either your wxstationlist.bin file is corrupt, or one of the .wx files saved with scenarios is bad.

Pete

 

[aldox62]

Thanks Pete, 

I will follow your kind suggestions and provide the logs as you indicated if I get a crash after setting the .ini file 

In case I get no crash what should I do with the wxtationlist.bin file ? I imagine I can delete all the wx files without issues

Thanks again,

Aldo

 

 

[Pete Dowson]

2 hours ago, aldox62 said:

what should I do with the wxtationlist.bin file ?

Delete the one in your AppData\Roaming folder. FSX will regenerate it.

Pete

 

[aldox62]

Great thanks a lot

Aldo

[aldox62]

Hi Pete,

added the NoWeatherAtAll flag into the ini, and relaunched the test flight

It worked for some time - I think couple of hours, and then crashed. I was not at the PC at the moment, so no interactions

Attached the FSUIPC4.log file the and the AppCrashView info for the kernel32 error

Thanks!

Aldo

FSUIPC4.log AppCrashviewInfo.txt

[aldox62]

sorry this is the right AppCrashView file...

 

Aldo

AppCrashviewInfo.txt

[Pete Dowson]

3 hours ago, aldox62 said:

sorry this is the right AppCrashView file...

Both that and the previous one do not indicate FSUIPC as the culprit. The Log too shows normal running. I'm afraid you have something else going on.

If it NEVER crashes with FSUIPC not running then you need to check your other add-ons to see which is using FSUIPC.

Otherwise you'll need to consider an FSX re-install. Something is corrupt. It may be an add-on aircraft or add-on scenery if not the main FSX modules.  Try a different aircraft to start with. And also keep track of what scenery is in use when it crashes (i.e. where you are flying over).

Pete

 

[aldox62]

Pete,

the test flight crashed after minimum 6 hours, PC unattended along the night.

Prior to that I rebuilt the wxstations file (new one being very different from original one) and deleted all the wx files in the user\Flight Simulator Files folder.

I was quite sure it was not an FSUIPC issue, but my attention was caught by the same error that was reported in the forum and so I tried this way as well..

Thanks again for your kind and prompt support ! 

In case I find the solution I will post here to update

Kindest regards,

Aldo 

 

[trisho0]

Eventually I visit this thread to see if I find another people with FSX Fsuipc CTD. So, it appears I have to keep Fsuipc disabled to fly comfortable.

I don't think FSX in my system needs to be reinstalled since I don't have any issues with my flight plans at the moment.

Keeping an eye for new Fsuipc version.

Patricio Valdes

[Pete Dowson]

1 hour ago, trisho0 said:

Keeping an eye for new Fsuipc version.

There will be no new version of FSUIPC4 for FSX. Development was frozen some time ago. The only recent changes were for the installer to cope with the Microsoft FSX-SE Beta (years ago now) and a rebuild using a later compiler version.

FSUIPC does not cause any crashes itself. It passively receives data from SimConnect to populate the offsets. It only actively does things in response to requests from applications or the assignments made by users. It is in regular use on uncountable installations of FSX, FSX-SE and P3D versions before P3D4. Crashes tend to get blamed on FSUIPC because it is ubiquitous, but they all turn out to be due to other things on the user's system.

Pete

 

Pete

 

 

[trisho0]

Then I could give a try with an older FSUIPC Installer version. I think it could be good try since never had problems with FSUIPC in the past years with FSX.

Patricio Valdes

[aldox62]

On 1/14/2022 at 9:28 AM, aldox62 said:

Pete,

the test flight crashed after minimum 6 hours, PC unattended along the night.

Prior to that I rebuilt the wxstations file (new one being very different from original one) and deleted all the wx files in the user\Flight Simulator Files folder.

I was quite sure it was not an FSUIPC issue, but my attention was caught by the same error that was reported in the forum and so I tried this way as well..

Thanks again for your kind and prompt support ! 

In case I find the solution I will post here to update

Kindest regards,

Aldo 

 

Hi Pete, here's the update ...

Along the weekend I zapped c:\ and d:\ and restarted with a fresh W11 Pro installed right from the USB media.

Mi previous setup was an upgrade from W10 and there was a remote suspect about the whole result, even if apparently everything worked -- not considering fsx.

I moved in the meantime to FSX:SE, on d:\, and installed FSUIPC ORBX various modules and so far just PMDG T7-200 to run the test flight that I have recreated in the meantime. 

Now It looks it works fine, the 12 hours test flight is almost at the end without problems... maybe I got rid of the CTDs in the end!.

Hope this can help someone else to solve the issue!

Kind regards

Aldo