FSUIPC crashes v4.5

[Drumcode]

I reported this originally in the Avsim CTD forum, but posting it here hoping to get some help with getting to the bottom of it. I am getting CTD either on take-off or mid air, no warnings just straight crash. 

Application error 

Log Name:      Application
Source:        Application Error
Date:          5/5/2019 8:47:25 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Simbox
Description:
Faulting application name: Prepar3D.exe, version: 4.5.11.29713, time stamp: 0x5ca56c53
Faulting module name: FSUIPC5.dll, version: 5.1.5.1, time stamp: 0x5c920d17
Exception code: 0xc0000005
Fault offset: 0x00000000000e1068
Faulting process id: 0x20cc
Faulting application start time: 0x01d503418a87d968
Faulting application path: D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: D:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.dll
Report Id: f7a5409e-1de4-4464-bfc8-01aba41755f3
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-05-05T14:47:25.954262700Z" />
    <EventRecordID>5999</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Simbox</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.5.11.29713</Data>
    <Data>5ca56c53</Data>
    <Data>FSUIPC5.dll</Data>
    <Data>5.1.5.1</Data>
    <Data>5c920d17</Data>
    <Data>c0000005</Data>
    <Data>00000000000e1068</Data>
    <Data>20cc</Data>
    <Data>01d503418a87d968</Data>
    <Data>D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data>
    <Data>D:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.dll</Data>
    <Data>f7a5409e-1de4-4464-bfc8-01aba41755f3</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

[John Dowson]

Could you please supply your FSUIPC log file at the time of the crash.

Generally such crashes are due to either an incompatibility somewhere or a corrupt file (usually weather or scenery). Have you tried re-installing the P3D client? I'm not sure what add-ons you have running as you have not supplied much information, but you could try disabling one by one to see if any have an incompatibility with P3D 4.5.

Crashes can also be due to a corrupt weather file (wxstationlist.bin), although that usually causes a crash pretty quickly. You could try removing that from your Appdata\roaming P3D4 folder - a new one will be re-created when you start.  You can also try completely disabling weather by adding

NoWeatherAtAll=Yes

to the [General] section of your FSUIPC5.ini.

Please try these actions and report back - also including your FSUIPC5.log file.

Cheers,

John

 

[Drumcode]

Will do. I am a little bit time limited so it may take me a little bit to get all this checked/tested. Please don't close the thread.

[Drumcode]

That's the best I can do for now

FSUIPC5.log

[John Dowson]

The log doesn't show much. You say the sim crashed 'on take off or mid air' but the log file you posted shows the sim shutting down just after start-up (89 seconds).

Crashes on start-up (or shortly thereafter) are usually due to corrupt weather or scenery files. I see you are using Active Sky, so please try with that disabled (from dll.xml), as well as the other tests posted above. Can you also make sure that you start with a default aircraft (and switch to the PMDG 737 later) as this can also cause issues (see https://www.avsim.com/forums/topic/526406-must-i-start-p3d-with-a-default-aircraft/).

John

[Drumcode]

Hi John,

The sim definitely did not crash on startup, but I will try it. I will also try to ping Damien on his forums and monitor any similar reports there too. I'll be in touch.

[Drumcode]

My issue is likely related to this. I'll be monitoring Ray's thread and if resolved, this can be closed.