Help! Possible Simconnect issue! (FSUIPC) FATAL ERROR

Jarvis He · July 29, 2014

Hello!

I've been having problems with FSUIPC. I keep crashing on start up.

Here's the FSUIPC.log:

********* FSUIPC4, Version 4.929c by Pete Dowson *********

Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"

Running inside FSX

Module base=22A40000

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

436 System time = 28/07/2014 10:08:07

436 FLT path = "C:\Users\Jarvis He\Documents\Flight Simulator X Files\"

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

483 FS path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

982 Assuming running on Vista or later in compatibility mode!

998 LogOptions=00000000 00000001

998 SIM1 Frictions access gained

1014 Wind smoothing may be by ASN, not FSUIPC, if it is running

1014 Will switch smoothing action when ASN starts/stops

1014 G3D.DLL fix attempt installed ok

1014 SimConnect_Open succeeded: waiting to check version okay

1014 Trying to use SimConnect Acc/SP2 Oct07

1014 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

1014 Initialising SimConnect data requests now

1014 FSUIPC Menu entry added

1060 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT

1060 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

Here's the Install log:

Installer for FSUIPC4.DLL version 4.929

Looking in registry for FSX install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

Parameter"SetupPath"

... >>> OK! FOUND FSX! <<< ...

Looking in registry for ESP install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\ESP

Parameter"AppPath"

... NOT found! ...

Looking in registry for Prepar3D install path:

HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\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\Prepar3D v2

Parameter"AppPath"

... NOT found! ...

===========================================================

INSTALLATION FOR FSX:

SetupPath="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

Checking version of the FSX EXE:

... Version 10.0.61472.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

Found SimConnect build 60905 (Original)

Found SimConnect build 61242 (SP1 May07)

Found SimConnect build 61259 (Acc/SP2 Oct07)

Checking if there's already a version of FSUIPC4 installed in:

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL

... No previous valid version found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path:

... found as "C:\Users\Jarvis He\AppData\Roaming"

Now finding \Microsoft\FSX\FSX.CFG for all users, including this one

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\Jack He\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Jarvis\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Jarvis He\AppData\Roaming"

Found FSX.CFG in "C:\Users\Jarvis He\AppData\Roaming\Microsoft\FSX\FSX.CFG"

Now checking DLL.XML ...

... There is a previous DLL.XML, checking for FSUIPC4 section.

... FSUIPC4_Loader 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 created okay!

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 "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 "Offset Mapping for PMDG 737NGX.pdf" okay

Installed "FSUIPC4 Offsets Status.pdf" okay

===========================================================

All installer tasks completed.

Registration for FSUIPC4 was successful! (result code 00)

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

Pete Dowson · July 29, 2014

The most likely reason is that you have a corrupted weather file. Try deleting (or moving out) the .WX file associated with the default flight, i.e.

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.WX

and also delete the wxstationlist.bin file which you'll finf in the same folder as your FSX.CFG file, i.e. in

C:\Users\Jarvis He\AppData\Roaming\Microsoft\FSX

When either of these binary files get corrupted, it messes up SimConnect's weather reading facilities and as soon as FSUIPC starts reading the weather it causes a crash. Unfortunately SimConnect doesn't check these files, it just assumes they are okay.

Pete

Jarvis He · July 30, 2014

Thanks for the quick support but I'm still getting fatal crashes after deleting this. By the way, this is a totally new FSX installation.

Pete Dowson · July 30, 2014

Thanks for the quick support but I'm still getting fatal crashes after deleting this. By the way, this is a totally new FSX installation.

how are you identifying FSUIPC as the cause?

To get crash information, go to the Windows event viewer and find the crash report. It will give details -- I would need the Module name, the error code and the module offset, as a minimum.

But before doing anything more, you need to update to the currently supported version of FSUIPC. You say it's a totally new installation of FSX, yet you are using FSUIPC version 4.929c which dates right back to March! The current version is 4.934 or later. (4.934a is available in the Download Links subforum).

Pete

Jarvis He · July 30, 2014

how are you identifying FSUIPC as the cause?

To get crash information, go to the Windows event viewer and find the crash report. It will give details -- I would need the Module name, the error code and the module offset, as a minimum.

But before doing anything more, you need to update to the currently supported version of FSUIPC. You say it's a totally new installation of FSX, yet you are using FSUIPC version 4.929c which dates right back to March! The current version is 4.934 or later. (4.934a is available in the Download Links subforum).

Pete

Problem Event Name: APPCRASH

Application Name: fsx.exe

Application Version: 10.0.61472.0

Application Timestamp: 475e17d3

Fault Module Name: FSUIPC4.dll

Fault Module Version: 4.9.3.4

Fault Module Timestamp: 53b60191

Exception Code: c0000005

Exception Offset: 00018f7f

OS Version: 6.1.7601.2.1.0.256.48

Locale ID: 1033

Additional information about the problem:

LCID: 1033

---------------------------

Windows Error Log

Log Name: Application

Source: Application Error

Date: 7/30/2014 4:50:44 PM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: Jarvis-PC

Description:

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: FSUIPC4.dll, version: 4.9.3.4, time stamp: 0x53b60191

Exception code: 0xc0000005

Fault offset: 0x00018f7f

Faulting process id: 0x2534

Faulting application start time: 0x01cfac37d68032fe

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll

Report Id: 2c1ec2f9-182b-11e4-ad7b-90e6ba879d00

Event Xml:

<Channel>Application</Channel>

<Computer>Jarvis-PC</Computer>

</System>

<Data>FSUIPC4.dll</Data>

<Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>

<Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll</Data>

</EventData>

</Event>

Edited July 30, 2014 by Jarvis He

Pete Dowson · July 31, 2014

Okay. That information most definitely points to the weather requests, and the only time I've seen this is when there is a corruption somewhere in the weather files.

To verify this you can prevent FSUIPC asking for weather completely by setting the "WeatherReadFactor" to 0 in the [General] section of the FSUIPC4.INI. Try that.

BTW, was that data when using 4.934 or 4.934a? Do you think you could try again with this version (it's my latest unreleased build), before you change the WeatherReadFactor, please:

FSUIPC4935b.zip

If it still crashes, please show me that data again. It should allow me to pinpoint exactly what is wrong with the data. Maybe I can then protect FSUIPC against bad weather data.

Regards

Pete

Jarvis He · July 31, 2014

1st question, is WeatherReadFactor supposed to be set to 1 or 2? Mine was set to 2. Changing it to 1 seems as if that fixed it. Your latest build works great after this fix but without it, it crashes. I'm pretty sure that earlier data was from 4.934. Thanks for the fix!

Here's some new data from the crash:

Log Name: Application

Source: Application Error

Date: 7/30/2014 11:07:57 PM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: Jarvis-PC

Description:

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: FSUIPC4.dll, version: 4.9.3.5, time stamp: 0x53d98683

Exception code: 0xc0000005

Fault offset: 0x00018f81

Faulting process id: 0x1708

Faulting application start time: 0x01cfac6c9149f304

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll

Report Id: debdf022-185f-11e4-ad7b-90e6ba879d00

Event Xml:

<Channel>Application</Channel>

<Computer>Jarvis-PC</Computer>

</System>

<Data>FSUIPC4.dll</Data>

<Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>

<Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll</Data>

<Data>debdf022-185f-11e4-ad7b-90e6ba879d00</Data>

</EventData>

</Event>

Pete Dowson · July 31, 2014

1st question, is WeatherReadFactor supposed to be set to 1 or 2? Mine was set to 2. Changing it to 1 seems as if that fixed it. Your latest build works great after this fix but without it, it crashes. I'm pretty sure that earlier data was from 4.934. Thanks for the fix!

The value of that parameter simply changes how often the weather is being read. A value of 0 stops FSUIPC reading or writing weather altogether. A non-zero value sets the interval at which it is read in half seconds, so the default of 2 is every second. Setting it to 1 makes it read twice as often, which should make it crash faster!

I'll check the data you appended. Thanks.

Pete

Pete Dowson · July 31, 2014

I'll check the data you appended. Thanks.

Found it. It wasn't about corrupted weather data after all! It looks like you are using an out of date version of Active Sky Next -- FSUIPC is tripping up on a response from its module "as_btstrp.dll". Could you check, please?

I'll add some protection for FSUIPC in this area, in the next version.

Pete

Sign In

Help! Possible Simconnect issue! (FSUIPC) FATAL ERROR

Recommended Posts

Jarvis He

Link to comment

Share on other sites

Pete Dowson

Link to comment

Share on other sites

Jarvis He

Link to comment

Share on other sites

Pete Dowson

Link to comment

Share on other sites

Jarvis He

Link to comment

Share on other sites

Pete Dowson

Link to comment

Share on other sites

Jarvis He

Link to comment

Share on other sites

Pete Dowson

Link to comment

Share on other sites

Pete Dowson

Link to comment

Share on other sites

Create an account or sign in to comment

Create an account

Sign in

Browse

Activity

Important Information