arnonmoscona Posted May 7, 2017 Report Posted May 7, 2017 (edited) I am running FSX-SE with a registered version of FSUIPC4 (4.966c). At some point it started crashing during sim startup (see screeshot of error message). If I say "yes", meaning run FSUIPC the FSX would crash after a few second, never reaching the main screen. If I say "No" and it does not run FSUIPC then the sim runs fine (except all FSUIPC control mappings are not there, naturally) So it's clear that the problem is with FSUIPC. the FSUIPC log looks like: ********* FSUIPC4, Version 4.966c (17th April 2017) by Pete Dowson ********* Windows 10 Pro 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0) fsx.exe version = 10.0.62615.0 Reading options from "D:\SteamLibrary\steamapps\common\FSX\Modules\FSUIPC4.ini" Running inside FSX Steam Edition on Windows 10 Module base=21000000 User Name="Arnon Moscona" User Addr="arnon@moscona.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 0 System time = 07/05/2017 11:29:23 0 FLT path = "C:\Users\Arnon\Documents\Flight Simulator X Files\" 0 ------ Module Version Check ------ 0 acontain.dll: 10.0.62615.0 0 api.dll: 10.0.62615.0 0 controls.dll: 10.0.62615.0 0 fs-traffic.dll: 10.0.62615.0 0 G3D.dll: 10.0.62615.0 0 language.dll: 10.0.62615.0 0 sim1.dll: 10.0.62615.0 0 visualfx.dll: 10.0.62615.0 0 weather.dll: 10.0.62615.0 0 window.dll: 10.0.62615.0 0 ---------------------------------- 16 Trying to connect to SimConnect Steam ... 32 FS path = "D:\SteamLibrary\steamapps\common\FSX\" 94 ---------------------- Joystick Device Scan ----------------------- 94 Product= vJoy - Virtual Joystick 94 Manufacturer= Shaul Eizikovich 94 Serial Number= 2.0.5 94 Vendor=1234, Product=BEAD (Version 2.5) 94 Assigned joystick id 1 (Registry okay) 94 GUID= {109593D0-2812-11E7-8002-444553540000} 110 Product= Saitek Pro Flight Quadrant 110 Manufacturer= Saitek 110 Vendor=06A3, Product=0C2D (Version 2.2) 110 Assigned joystick id 0 (Registry okay) 110 GUID= {F6B633E0-27FB-11E7-8002-444553540000} 110 ------------------------------------------------------------------- 110 ---------- Making INI JoyNames Section ---------- 110 Joy#0: OEMName = "Saitek Pro Flight Quadrant" 110 Joy#0: GUID = {F6B633E0-27FB-11E7-8002-444553540000} 110 Joy#1: OEMName = "vJoy Device" 110 Joy#1: GUID = {109593D0-2812-11E7-8002-444553540000} 110 ------------------------------------------------- 125 LogOptions=00000000 00000001 125 ------------------------------------------------------------------- 125 ------ Setting the hooks and direct calls into the simulator ------ 125 --- CONTROLS timer memory location obtained ok 125 --- SIM1 Frictions access gained 125 ASN active function link set 125 --- FS Controls Table located ok 125 --- Installed Mouse Macro hooks ok. 125 Wind smoothing may be by ASN, not FSUIPC, if it is running 125 Will switch smoothing action when ASN starts/stops 125 --- SimConnect intercept for texts and menus option is off 125 --- All links checked okay 125 ------------------------------------------------------------------- 125 SimConnect_Open succeeded: waiting to check version okay 125 Trying to use SimConnect Steam 125 Opened separate AI Traffic client okay 985 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0) 985 Initialising SimConnect data requests now 985 FSUIPC Menu entry added 985 c:\users\arnon\documents\flight simulator x files\KFHR runway default C172.FLT 985 D:\SteamLibrary\steamapps\common\FSX\SimObjects\Airplanes\C172\Cessna172SP.air 5297 Weather Mode now = Theme 15297 D:\SteamLibrary\steamapps\common\FSX\SimObjects\Airplanes\A2A_C182\C182.air 30657 User Aircraft ID 1 supplied, now being used 30672 Aircraft loaded: running normally now ... 77438 System time = 07/05/2017 11:30:40, Simulator time = 11:29:28 (18:29Z) 77438 Aircraft="C182_N6182G" 86235 Starting everything now ... 113938 Sim stopped: average frame rate for last 36 secs = 39.6 fps 113938 Max AI traffic was 0 aircraft 119547 Advanced Weather Interface Enabled 984938 Sim stopped: average frame rate for last 866 secs = 39.4 fps 984938 Max AI traffic was 22 aircraft (Deleted 0) 1003391 === DLLStop called ... 1003391 === Closing external processes we started ... 1004391 === About to kill any Lua plug-ins still running ... 1004547 === Closing global Lua thread 1005547 === About to kill my timers ... 1005844 === Restoring window procs ... 1005844 === Unloading libraries ... 1005844 === stopping other threads ... 1005844 === ... Button scanning ... 1005938 === ... Axis scanning ... 1006047 === Releasing joystick devices ... 1006047 === Freeing macro memory 1006047 === Removing any offset overrides 1006047 === Clearing any displays left 1006047 === NOTE: not calling SimConnect_Close ... 1006047 === AI slots deleted! 1006047 === Freeing button memory ... 1006047 === Closing my Windows ... 1006047 === Freeing FS libraries ... 1007047 === Closing devices ... 1007047 === Closing the Log ... Bye Bye! ... 1007047 System time = 07/05/2017 11:46:10, Simulator time = 11:43:53 (18:43Z) 1007047 *** FSUIPC log file being closed Minimum frame rate was 29.1 fps, Maximum was 51.7 fps Minimum available memory recorded was 681Mb Average frame rate for running time of 902 secs = 39.4 fps Maximum AI traffic for session was 22 aircraft Memory managed: 414 Allocs, 413 Freed ********* FSUIPC Log file closed *********** Windows events viewer reports: Fault bucket 116369054293, type 5 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: fsx.exe P2: 10.0.62615.0 P3: 559f9a9a P4: FSUIPC4.dll_unloaded P5: 4.9.6.603 P6: 58f49845 P7: 000c1530 P8: c0000005 P9: 00000008 P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER761B.tmp.WERInternalMetadata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: 97e2a750-dbcb-4f7e-80d4-79d0fd52401f Report Status: 268435456 Hashed bucket: c7775473b222922783f15dfd14ad6d8d The detail of the events in the event viewer is: - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-05-07T21:35:43.137821800Z" /> <EventRecordID>6570</EventRecordID> <Channel>Application</Channel> <Computer>ORIGIN</Computer> <Security /> </System> - <EventData> <Data>116369054293</Data> <Data>5</Data> <Data>BEX</Data> <Data>Not available</Data> <Data>0</Data> <Data>fsx.exe</Data> <Data>10.0.62615.0</Data> <Data>559f9a9a</Data> <Data>FSUIPC4.dll_unloaded</Data> <Data>4.9.6.603</Data> <Data>58f49845</Data> <Data>000c1530</Data> <Data>c0000005</Data> <Data>00000008</Data> <Data /> <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER761B.tmp.WERInternalMetadata.xml</Data> <Data /> <Data /> <Data>1</Data> <Data>97e2a750-dbcb-4f7e-80d4-79d0fd52401f</Data> <Data>268435456</Data> <Data>c7775473b222922783f15dfd14ad6d8d</Data> </EventData> </Event> I have a bunch of add-ons installed, including: ORBX and other sceneries A bunch of aircraft (although for the experiment, FSX loads with the default C172 - not that it ever gets there if I allow FSUIPC to run...) AS16 F1 GTN750 and F1 GNS530 - neither of them installed into the default C172 Right now, the sim is not really usable for any aircraft that require FSUIPC or that have custom mappings in FSUIPC - which is basically all the stuff I fly, pretty much. Oh, i would add that if I rename FSUIPC4.ini to something else, I get the same symptoms, so i don;t think it's a configuration problem. Any idea? Thanks Arnon Edited May 7, 2017 by arnonmoscona
arnonmoscona Posted May 7, 2017 Author Report Posted May 7, 2017 More experimentation: Noticed that the FSUIPC log file was older. It may be from before the problem started. That's must be confusing, I bet. Ran the FSUIPC installer again. Still getting the message on sim startup. Tried to put the FSUIPC4_Loader.dll file in the modules directory. Still getting the error on sim startup. Removed FSUIPC4_Loader.dll from the modules directory. On whim, decided to see again what happens if I allow the sim to run FSUIPC despite having the message - lo and behold! the sim works now. Before it would just crash before the main screen shows up. Now it shows the message, but survives to fly. So now I am double confused. What happened? Why am I still getting the message? If it's any help, here's the latest log from a session when I allowed it to go past the message and conducted a very short flight with the default C172. Hope it helps to clarify. Note that the vjoy device is for a Brunner yoke (button mapping - not axis) ********* FSUIPC4, Version 4.966c (17th April 2017) by Pete Dowson ********* Windows 10 Pro 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0) fsx.exe version = 10.0.62615.0 Reading options from "D:\SteamLibrary\steamapps\common\FSX\Modules\FSUIPC4.ini" Running inside FSX Steam Edition on Windows 10 Module base=21F80000 User Name="Arnon Moscona" User Addr="arnon@moscona.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 0 System time = 07/05/2017 15:04:35 0 FLT path = "C:\Users\Arnon\Documents\Flight Simulator X Files\" 0 ------ Module Version Check ------ 0 acontain.dll: 10.0.62615.0 0 api.dll: 10.0.62615.0 0 controls.dll: 10.0.62615.0 0 fs-traffic.dll: 10.0.62615.0 0 G3D.dll: 10.0.62615.0 0 language.dll: 10.0.62615.0 0 sim1.dll: 10.0.62615.0 0 visualfx.dll: 10.0.62615.0 16 weather.dll: 10.0.62615.0 16 window.dll: 10.0.62615.0 16 ---------------------------------- 32 Trying to connect to SimConnect Steam ... 32 FS path = "D:\SteamLibrary\steamapps\common\FSX\" 94 ---------------------- Joystick Device Scan ----------------------- 94 Product= vJoy - Virtual Joystick 94 Manufacturer= Shaul Eizikovich 94 Serial Number= 2.0.5 94 Vendor=1234, Product=BEAD (Version 2.5) 110 Assigned joystick id 1 (Registry okay) 110 GUID= {109593D0-2812-11E7-8002-444553540000} 110 Product= Saitek Pro Flight Quadrant 110 Manufacturer= Saitek 110 Vendor=06A3, Product=0C2D (Version 2.2) 110 Assigned joystick id 0 (Registry okay) 110 GUID= {F6B633E0-27FB-11E7-8002-444553540000} 110 ------------------------------------------------------------------- 110 ---------- Making INI JoyNames Section ---------- 110 Joy#0: OEMName = "Saitek Pro Flight Quadrant" 110 Joy#0: GUID = {F6B633E0-27FB-11E7-8002-444553540000} 110 Joy#1: OEMName = "vJoy Device" 110 Joy#1: GUID = {109593D0-2812-11E7-8002-444553540000} 110 ------------------------------------------------- 125 LogOptions=00000000 00000001 125 ------------------------------------------------------------------- 125 ------ Setting the hooks and direct calls into the simulator ------ 125 --- CONTROLS timer memory location obtained ok 125 --- SIM1 Frictions access gained 125 --- FS Controls Table located ok 125 --- Installed Mouse Macro hooks ok. 125 --- Wind smoothing fix is fully installed 125 --- SimConnect intercept for texts and menus option is off 125 --- All links checked okay 125 ------------------------------------------------------------------- 125 SimConnect_Open succeeded: waiting to check version okay 125 Trying to use SimConnect Steam 125 Opened separate AI Traffic client okay 1016 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0) 1016 Initialising SimConnect data requests now 1016 FSUIPC Menu entry added 1032 c:\users\arnon\documents\flight simulator x files\KFHR runway default C172.FLT 1032 D:\SteamLibrary\steamapps\common\FSX\SimObjects\Airplanes\C172\Cessna172SP.air 9750 Weather Mode now = Theme 21235 User Aircraft ID 1 supplied, now being used 21235 Aircraft loaded: running normally now ... 64235 Aircraft="Cessna Skyhawk 172SP Paint1" 64235 System time = 07/05/2017 15:05:39, Simulator time = 15:04:45 (22:04Z) 84938 Sim stopped: average frame rate for last 20 secs = 52.0 fps 84938 Max AI traffic was 0 aircraft 97047 Starting everything now ... 97078 ASN active function link set 97078 Ready for ASN WX radar 98219 Advanced Weather Interface Enabled 349532 Sim stopped: average frame rate for last 261 secs = 53.1 fps 349532 Max AI traffic was 18 aircraft (Deleted 0) 351766 C:\Users\Arnon\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 381907 === DLLStop called ... 381907 === Closing external processes we started ... 382907 === About to kill any Lua plug-ins still running ... 383063 === Closing global Lua thread 384063 === About to kill my timers ... 384266 === Restoring window procs ... 384266 === Unloading libraries ... 384266 === stopping other threads ... 384266 === ... Button scanning ... 384360 === ... Axis scanning ... 384469 === Releasing joystick devices ... 384469 === Freeing macro memory 384469 === Removing any offset overrides 384469 === Clearing any displays left 384469 === NOTE: not calling SimConnect_Close ... 384469 === AI slots deleted! 384469 === Freeing button memory ... 384469 === Closing my Windows ... 384469 === Freeing FS libraries ... 385469 === Closing devices ... 385469 === Closing the Log ... Bye Bye! ... 385469 System time = 07/05/2017 15:11:01, Simulator time = 15:09:05 (22:09Z) 385469 *** FSUIPC log file being closed Minimum frame rate was 39.6 fps, Maximum was 70.4 fps Minimum available memory recorded was 1353Mb Average frame rate for running time of 281 secs = 53.0 fps Maximum AI traffic for session was 18 aircraft Memory managed: 127 Allocs, 126 Freed ********* FSUIPC Log file closed ***********
Pete Dowson Posted May 7, 2017 Report Posted May 7, 2017 1 hour ago, arnonmoscona said: So it's clear that the problem is with FSUIPC. No, it isn't at all. Look at the evidence: 1. BOTH logs show completely successful sessions with FSUIPC running and closing normally. 2. The error Windows shows that FSUIPC wasn't even loaded:What is "P4: FSUIPC4.dll_unloaded" What is happening is that it isn't being loaded -- something is stopping it, yet SimConnect, the part of FS which is loading it, still tries to enter it. This causes the "BEX" error which is basically attempted execution of data or rubbish as if it were code. Quote On whim, decided to see again what happens if I allow the sim to run FSUIPC despite having the message - lo and behold! the sim works now. Before it would just crash before the main screen shows up. Now it shows the message, but survives to fly. If you read the FAQ about this (in the FAQ subforum) you will see it is always best to tell it to try running. It often recovers. The error on loading, occurring even before FSUIPC starts, is generally caused by a previous session which crashed on exit rather than closing down correctly. When the sim is closed properly, FSUIPC has threads which are among the last to close. These are threads doing things like tidying up any loaded plug-ins, ensuring connected applications know what is happening, and, if WideFS is being used, notifying the other PCs so that the closure is tidy all round. So, next time it happens you need to look for a PREVIOUS crash, not "FSUIPC_Unloaded", which might help explain what caused a crash on exit. Pete
arnonmoscona Posted May 7, 2017 Author Report Posted May 7, 2017 I'll look out for it. Thanks for the quick response
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now