dgor Posted March 26, 2018 Report Share Posted March 26, 2018 Hi Pete, I'm new to P3D v4 and was wondering if you could help me. I'm using the latest version of FSUIPC but it is causing a strange crash-to-desktop very soon after loading (I load the sim, it instantly freezes and a few seconds later exits). No error message is displayed. It happens with and without addon aircraft at any airport, and always straight after loading the scenario. At first, I thought it was my FSXWX addon which uses FSUIPC and SimConnect. FSXWX generates an "unhandled exception" report after the crash. However, the above crash also happens without FSXWX running. The only way I've been able to solve it is by uninstalling FSUIPC. Strangely, at first the sim worked fine as long as FSXWX generated the weather, and crashed if I did not load FSXWX first. However, now the sim crashes completely regardless of whether FSXWX is/was running. I've googled the error message it generates (hresult: 0xc000014b) but this seems to be fairly unspecific and represents a broken connection between that and P3D. I didn't change anything or install anything new between the last time the sim worked and now - it has just stopped working on its own. As I said, there is no error message created from the sim at all. I can't see any relevant events in the Windows Event Viewer (forgive me if I'm missing something). The FSUIPC log is as follows: ********* FSUIPC5, Version 5.124 (27th February 2018) by Pete Dowson ********* Running inside Prepar3D v4 Module base=7FFE94A80000 Windows 10 Pro 64 Bit reported as Build 16299, Release ID: 1709 (OS 10.0) Prepar3D.exe version = 4.2.21.24048 Reading options from "C:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.ini" Checking the Registrations now ... User Name="" User Addr="" FSUIPC5 not user registered WIDEFS7 not user registered, or expired 0 System time = 26/03/2018 20:01:55 0 FLT path = "C:\Users\[me]\Documents\Prepar3D v4 Files\" 0 ------ Module Version Check ------ 0 acontain.dll: 4.2.21.24048 0 api.dll: 4.2.21.24048 0 controls.dll: 4.2.21.24048 0 fs-traffic.dll: 4.2.21.24048 0 G3D.dll: 4.2.21.24048 0 language.dll: 4.2.21.24048 0 sim1.dll: 4.2.21.24048 0 visualfx.dll: 4.2.21.24048 0 weather.dll: 4.2.21.24048 0 window.dll: 4.2.21.24048 0 ---------------------------------- 0 Using PDK events 0 Using DialogMode 16 FS path = "C:\Lockheed Martin\Prepar3D v4\" 16 LogOptions=00000000 00000001 16 ------------------------------------------------------------------- 16 SimConnect_Open succeeded: waiting to check version okay 16 Opened separate AI Traffic client okay 2766 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.2.21.24048 (SimConnect: 4.2.0.0) 2766 Initialising SimConnect data requests now 2766 FSUIPC Menu entry added 2766 ... Using Prepar3D with Academic License 4000 C:\Users\David Gorman\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml 4000 C:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air 21844 Loading Complete ... 22922 User Aircraft ID 2 supplied, now being used 22922 Aircraft loaded: running normally now ... 23062 System time = 26/03/2018 20:02:18, Simulator time = 14:00:01 (19:00Z) 24031 -------------------- Starting everything now ---------------------- 24109 Weather Mode now = Global 24109 Weather Mode now = Theme 24109 Weather Mode now = Custom I previously googled the problem and saw a lot of similar issues but nothing that resolved my case. I've tried deleting wxstationlist.bin, Prepar3D_default.fxml, Prepar3d_Default.wx and all previous flight files under My Documents. My FSUIPC isn't registered. I hope I have provided useful information, please let me know if not. Many thanks in advance for any help. Dave Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 26, 2018 Report Share Posted March 26, 2018 3 hours ago, dgor said: I'm using the latest version of FSUIPC but it is causing a strange crash-to-desktop very soon after loading (I load the sim, it instantly freezes and a few seconds later exits). No error message is displayed. It happens with and without addon aircraft at any airport, and always straight after loading the scenario. The log indicates that it is definitely a corrupted weather file. Those cause SimConnect to crash when FSUIPC starts requesting weather information. You can test this for yourself by adding NoWeatherAtAll=Yes to the [General] section of the FSUIPC5.INI file. 3 hours ago, dgor said: I've googled the error message it generates (hresult: 0xc000014b) but this seems to be fairly unspecific and represents a broken connection between that and P3D. You've obtained the Windows crash data but not shown the details! You do realise these might be useful, in particular naming the particular module (DLL) which crashed? Please don't keep these things to yourself. 3 hours ago, dgor said: I've tried deleting wxstationlist.bin, Prepar3D_default.fxml, Prepar3d_Default.wx and all previous flight files under My Documents. What about all the other .wx files? Which wxstationlist.bin file did you delete? It needs to be the one in the same folder as your current Prepar3D.cfg file (users -> your name -> AppData -> Roaming -> LM -> P3D4). 3 hours ago, dgor said: My FSUIPC isn't registered. Even more pointing towards the weather data, because FSUIPC is doing very little else for you -- just receiving data from SimConnect so it can support the application interface. Pete Link to comment Share on other sites More sharing options...
dgor Posted March 27, 2018 Author Report Share Posted March 27, 2018 Hi Pete, Thanks for getting back. The error message I alluded to (which is from FSXWX, not P3D) is as follows: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014B at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveDispatch(SignalProcDelegate pfcnSignal) at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveMessage() at FSXWX.Form1.DefWndProc(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ContainerControl.WndProc(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8825 (WinRelRS3.050727-8800) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- FSXWX Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Lockheed%20Martin/Prepar3D%20v4/FSXWX.exe ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8825 (WinRelRS3.050727-8800) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8825 (WinRelRS3.050727-8800) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8825 (WinRelRS3.050727-8800) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- Accessibility Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8825 (WinRelRS3.050727-8800) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll ---------------------------------------- Microsoft.FlightSimulator.SimConnect Assembly Version: 10.0.61259.0 Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421) CodeBase: file:///C:/WINDOWS/assembly/GAC_32/Microsoft.FlightSimulator.SimConnect/10.0.61259.0__31bf3856ad364e35/Microsoft.FlightSimulator.SimConnect.dll ---------------------------------------- msvcm80 Assembly Version: 8.0.50727.9348 Win32 Version: 8.00.50727.9348 CodeBase: file:///C:/WINDOWS/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9348_none_d08c1480442bf1e1/msvcm80.dll ---------------------------------------- System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8825 (WinRelRS3.050727-8800) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8827 (WinRelRS3.050727-8800) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Core Assembly Version: 3.5.0.0 Win32 Version: 3.5.30729.8833 built by: WinRelRS3 CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. -- Yes, that is the wxstationlist.bin file I have deleted. All other .wx files I have found have been deleted too. Just tried adding those lines to the FSUIPC.ini file and it seems to be working again - thank you! I am surprised as that doesn't seem to be affecting the way FSXWX interacts with the sim. I would have thought that disabling FSUIPC weather control would render my weather addon useless. Interesting, thanks again! Dave Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 27, 2018 Report Share Posted March 27, 2018 4 hours ago, dgor said: he error message I alluded to (which is from FSXWX, not P3D) is as follows: I cannot debug FSXWX, sorry. You must send such crash data to its author. If P3D is crashing then there should be a P3D crash log in the Event viewer. it is that I need to see, 4 hours ago, dgor said: Yes, that is the wxstationlist.bin file I have deleted. All other .wx files I have found have been deleted too. Okay. So not a corrupt weather file then. 4 hours ago, dgor said: Just tried adding those lines to the FSUIPC.ini file and it seems to be working again - thank you! I am surprised as that doesn't seem to be affecting the way FSXWX interacts with the sim. I would have thought that disabling FSUIPC weather control would render my weather addon useless Does FSXWX use FSUIPC for weather? I don't know it at all. But everything you've now said points to FSXWX as the culprit, not FSUIPC. Pete Link to comment Share on other sites More sharing options...
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