Multiple Sim stopped statements in FSUIPC4.log

[WebMaximus]

My last two flights ended in CTDs which I haven't had in quite a while. They both happened at the new Aerosoft version of EDDF (v211) so maybe the problem is with the scenery.

The first one happened after I landed and was taxing into the gate. Looking in the Windows Event Viewer Application log this first crash resulted in two error messages as seen below with only a 1 second delay and in both the faulting module reported is KERNELBASE.dll

Log Name:      Application
Source:        Application Error
Date:          2017-04-10 15:27:28
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      TheNest
Description:
Faulting application name: prepar3d.exe, version: 3.2.3.16769, time stamp: 0x56df48ce
Faulting module name: KERNELBASE.dll, version: 10.0.14393.953, time stamp: 0x58ba586d
Exception code: 0xe0434352
Fault offset: 0x000da882
Faulting process id: 0x2ad8
Faulting application start time: 0x01d2b1fde0f751df
Faulting application path: F:\Program Files (x86)\Lockheed Martin\Prepar3D v3\prepar3d.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 41694ab5-252b-4816-9092-a8227a990f00
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="2017-04-10T13:27:28.385894500Z" />
    <EventRecordID>33402</EventRecordID>
    <Channel>Application</Channel>
    <Computer>TheNest</Computer>
    <Security />
  </System>
  <EventData>
    <Data>prepar3d.exe</Data>
    <Data>3.2.3.16769</Data>
    <Data>56df48ce</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>10.0.14393.953</Data>
    <Data>58ba586d</Data>
    <Data>e0434352</Data>
    <Data>000da882</Data>
    <Data>2ad8</Data>
    <Data>01d2b1fde0f751df</Data>
    <Data>F:\Program Files (x86)\Lockheed Martin\Prepar3D v3\prepar3d.exe</Data>
    <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
    <Data>41694ab5-252b-4816-9092-a8227a990f00</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Application Error
Date:          2017-04-10 15:27:29
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      TheNest
Description:
Faulting application name: prepar3d.exe, version: 3.2.3.16769, time stamp: 0x56df48ce
Faulting module name: KERNELBASE.dll, version: 10.0.14393.953, time stamp: 0x58ba586d
Exception code: 0xc000041d
Fault offset: 0x000da882
Faulting process id: 0x2ad8
Faulting application start time: 0x01d2b1fde0f751df
Faulting application path: F:\Program Files (x86)\Lockheed Martin\Prepar3D v3\prepar3d.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: f4901ae3-7dd7-44b3-bd07-c6b2bae9e1ef
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="2017-04-10T13:27:29.312859400Z" />
    <EventRecordID>33404</EventRecordID>
    <Channel>Application</Channel>
    <Computer>TheNest</Computer>
    <Security />
  </System>
  <EventData>
    <Data>prepar3d.exe</Data>
    <Data>3.2.3.16769</Data>
    <Data>56df48ce</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>10.0.14393.953</Data>
    <Data>58ba586d</Data>
    <Data>c000041d</Data>
    <Data>000da882</Data>
    <Data>2ad8</Data>
    <Data>01d2b1fde0f751df</Data>
    <Data>F:\Program Files (x86)\Lockheed Martin\Prepar3D v3\prepar3d.exe</Data>
    <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
    <Data>f4901ae3-7dd7-44b3-bd07-c6b2bae9e1ef</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

The second crash happened shortly after I took off from the same airport during initial climb. This second crash resulted in the below error message checking the Windows Event Viewer Application log and as you can see this time the faulting module is reported being MSVCR80.dll

Log Name:      Application
Source:        Application Error
Date:          2017-04-10 22:46:43
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      TheNest
Description:
Faulting application name: prepar3d.exe, version: 3.2.3.16769, time stamp: 0x56df48ce
Faulting module name: MSVCR80.dll, version: 8.0.50727.9268, time stamp: 0x573d297f
Exception code: 0xc000000d
Fault offset: 0x00008aa0
Faulting process id: 0x9ec
Faulting application start time: 0x01d2b232e12dedfa
Faulting application path: F:\Program Files (x86)\Lockheed Martin\Prepar3D v3\prepar3d.exe
Faulting module path: C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e\MSVCR80.dll
Report Id: cd66835f-a209-42f5-80be-fb2b40aaea18
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="2017-04-10T20:46:43.025698200Z" />
    <EventRecordID>33492</EventRecordID>
    <Channel>Application</Channel>
    <Computer>TheNest</Computer>
    <Security />
  </System>
  <EventData>
    <Data>prepar3d.exe</Data>
    <Data>3.2.3.16769</Data>
    <Data>56df48ce</Data>
    <Data>MSVCR80.dll</Data>
    <Data>8.0.50727.9268</Data>
    <Data>573d297f</Data>
    <Data>c000000d</Data>
    <Data>00008aa0</Data>
    <Data>9ec</Data>
    <Data>01d2b232e12dedfa</Data>
    <Data>F:\Program Files (x86)\Lockheed Martin\Prepar3D v3\prepar3d.exe</Data>
    <Data>C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e\MSVCR80.dll</Data>
    <Data>cd66835f-a209-42f5-80be-fb2b40aaea18</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Today I quickly launched P3D for the first time after the last crash above and first everything seemed to be fine. However after a while I noticed how the sound stopped for about a second and then came back. Almost like when the simulator window looses focus. This happened a couple of times.

I then decided to check the FSUIPC4.log looking for any hints and found one thing I thought looked a bit odd. At the end of the log I had multiple Sim stopped statements and I thought normally you would only have one of those indicating your exit out of the simulator.

I need to do more testing and the first thing will be to perform a flight where the new version of Aerosoft EDDF is not involved but if you have any other tips or input and could explain the multiple Sim stopped statements in FSUIPC4.log that would be most appreciated.

[Thomas Richter]

Hi,

first thing would be to copy and paste the FULL Content of your FSUIPC4.log file into your message.

Thomas

 

[WebMaximus]

Hi Thomas,

Since writing my last post I already restarted P3D meaning the FSUIPC4.log file has been overwritten.

I've now done some cleaning of my P3D installation and will do some more testing and if the problem persists I'll post the log here.

[Pete Dowson]

10 hours ago, WebMaximus said:

At the end of the log I had multiple Sim stopped statements and I thought normally you would only have one of those indicating your exit out of the simulator.

The "SIM stopped" log entry is just a message it gets for SimConnect every time you go into a menu. It is not specifically relating to exiting the sim.

Your problems don't look in any way related to FSUIPC.

Pete

 

 

[WebMaximus]

Ah, got it.

Many thanks for the clarification Pete!