Jump to content
The simFlight Network Forums


Recommended Posts



Just had FSX crash on me -- on investigating with Event Viewer I was interested to note that FSUIPC was the faulting module.


Obviously it may well be 'one of those things' that never crops up again, but would be interested to hear any thoughts.

Log Name:      Application
Source:        Application Error
Date:          06/05/2016 23:00:27
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Desktop
Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: FSUIPC4.dll, version:, time stamp: 0x56d78d28
Exception code: 0xc0000005
Fault offset: 0x0004e371
Faulting process ID: 0xf94
Faulting application start time: 0x01d1a7d61e645296
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.dll
Report ID: d8270765-d77c-4e23-afc3-bd5c22423210
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <TimeCreated SystemTime="2016-05-06T22:00:27.000000000Z" />
    <Security />

Any ideas? I did initially think it could be connected to the access violation referred to in the FAQ at http://forum.simflight.com/topic/73518-possible-solution-for-fsuipc-access-violation/- but closer investigation of the registry reveals that that particular key is not in existence, so therefore it must be something else.


Many thanks,



Link to comment
Share on other sites

The data you've posted would be useful if it related to the currently supported version, 4.95. Please update and try again. Also, next time, please show me the FSUIPC4.LOG file, as far as it gets. That could also provide a vital clue.


From the offset the most likely area of FSUIPC is the Lua interpreter, so details of any Lua plug-ins you have running may be relevant too, as well as a description of what might have been going on at the time.



Link to comment
Share on other sites

Ah -- I shall do! Thanks Pete. I'd only updated in the last couple of weeks so it didn't occur to me there might be a new version!


Interesting that it could be connected to the LUA interpreter.


For information and completeness, here's the FSUIPC4.LOG:

********* FSUIPC4, Version 4.949h by Pete Dowson *********
fsx.exe version = 10.0.62615.0
Reading options from "D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 8.0
Module base=5AEB0000
User Name="Simon Kelsey"
User Addr="simon.kelsey87@gmail.com"
FSUIPC4 Key is provided
WideFS7 Key is provided
      125 System time = 06/05/2016 21:32:51
      125 FLT UNC path = "\\DESKTOP\My Documents\Flight Simulator X - Steam Edition Files\"
      141 ------ Module Version Check ------
      141        acontain.dll: 10.0.62615.0
      141             api.dll: 10.0.62615.0
      141        controls.dll: 10.0.62615.0
      141      fs-traffic.dll: 10.0.62615.0
      141             G3D.dll: 10.0.62615.0
      141        language.dll: 10.0.62615.0
      141            sim1.dll: 10.0.62615.0
      141        visualfx.dll: 10.0.62615.0
      156         weather.dll: 10.0.62615.0
      156          window.dll: 10.0.62615.0
      156 ----------------------------------
      672 Trying to connect to SimConnect Steam ...
      719 FS UNC path = "\\DESKTOP\FSX2\"
     1110 ---------------------- Joystick Device Scan -----------------------
     1125 Product= Pro Flight Cessna Yoke
     1125    Manufacturer= Saitek 
     1125    Vendor=06A3, Product=0BD3 (Version 1.22)
     1125    Serial Number= RD011175
     1125 Product= Logitech MOMO Racing 
     1141    Manufacturer= Logitech 
     1141    Vendor=046D, Product=CA03 (Version 0.25)
     1141    Serial Number= Logitech 
     1141 Product= SideWinder Precision 2 Joystick
     1156    Manufacturer= Microsoft
     1156    Vendor=045E, Product=0038 (Version 1.8)
     1156    Serial Number= Microsoft
     1156 -------------------------------------------------------------------
     1172 LogOptions=00000000 00000001
     1172 -------------------------------------------------------------------
     1172 ------ Setting the hooks and direct calls into the simulator ------
     1172 --- CONTROLS timer memory location obtained ok
     1172 --- SIM1 Frictions access gained
     1172 --- FS Controls Table located ok
     1172 --- Installed Mouse Macro hooks ok.
     1172 --- Wind smoothing fix is fully installed
     1172 --- All links checked okay
     1172 -------------------------------------------------------------------
     1172 SimConnect_Open succeeded: waiting to check version okay
     1172 Trying to use SimConnect Steam
    24156 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0)
    24156 Initialising SimConnect data requests now
    24156 FSUIPC Menu entry added
    24188 \\DESKTOP\FSX2\flights\other\FLTSIM.FLT
    24188 \\DESKTOP\FSX2\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.air
    29500 Weather Mode now = Theme
    75360 \\DESKTOP\FSX2\SimObjects\Airplanes\Aerosoft Airbus A319 IAE\A319IAE.air
   118750 System time = 06/05/2016 21:34:50, Simulator time = 21:35:18 (20:35Z)
   118766 Aircraft="Airbus A319 British Airways BA-GDBCF"
   282266 Starting everything now ...
   282344 ASN active function link set
   282344 Ready for ASN WX radar
   316406 Sim stopped: average frame rate for last 36 secs = 19.3 fps
   351016 Advanced Weather Interface Enabled

LUA plugins -- just DynamicFriction and a couple related to the Aerosoft Airbus. AirbusX_Thr1 & AirbusX_Thr2 (which enable control of the Airbus thrust levers via FSUIPC) and Transponder_ab (which sends the SB offset from the transponder switch). There is also an A2A transponder LUA but I presume that wouldn't have been loaded.


As to what was happening -- not very much! It was an Aerosoft connected flight deck flight, so don't know whether that could have had any bearing on it, but other than that wholly unremarkable: we'd been flying for almost an hour and were just in the cruise (FL280, just south of the Scottish border). Just about to start descent, but I don't think that had actually been initiated when the crash occurred.


Hope that's useful -- however, I will go and update forthwith!





Link to comment
Share on other sites

Interesting that it could be connected to the LUA interpreter.


Actually, looking at the Log that's not so likely. This line, being the last logged, is a very clear indicator:


351016 Advanced Weather Interface Enabled


Not sure why it took nearly 6 minutes for FS to get to this stage. Was it sitting at the selection screen a while?


Anyway, the fact that the crash occurred immediately after FSUIPC started reading the weather from SimConnect points to a corrupted file -- either the .WX file being loaded, or the wxstationlist.bin file in the folder where your main FSX.CFG file resides.


These files are just binary data, with no checks included, and if the get corrupted -- perhaps from a previous crash, or partial update from a weather supplier, then when SimConnect interprets them in order to provide FSUIPC with the extended METAR strings being requested, it cause a crash -- sometimes in WEATHER.DLL, sometimes in it's callback in FSUIPC, sometimes actually in simconnect itself, though that's pretty unusua because that DLL is really just a sort of "stub" passing things on to the relevant part of FS.


Try deleting, or moving out, the .WX files from your FS files folder in your Documents, and just deleting the wxstationlist.bin file. As you are using ASN you don't need the .wx files, and the .bin file will be regenerated in any case.



Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.