Jump to content

Twin Otter for P3D v4 causes hang-up and CTD


ClydeCessna

Recommended Posts

The problem is still there on the version 1.21. It hangs or crashes to desktop in several seconds after engines shutdown.

I tried to disable AS Flight Recorder, tried to disable Antivirus, and other add-ons, no luck. This happens only with the Twin Otter. I'm running P3D 4.1 on Windows 10.

 

Here are the excerptions from the Windows Event Viewer.

 

Spoiler

Fault bucket 129584528079, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 4.1.7.22841
P3: 59d67e95
P4: 0000
P5: 134217984
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA7A3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA7B3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA7B4.tmp.txt
\\?\C:\Users\Ilya\AppData\Local\Temp\WERD278.tmp.appcompat.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_Prepar3D.exe_7dbfdbe783a886a39b4204a944aeaa4ab578d_911d388a_145edc2c

Analysis symbol: 
Rechecking for solution: 0
Report Id: d2ee2e05-f389-4e90-acde-a21c52377d1b
Report Status: 268435456
Hashed bucket: 67d6e0476771645646fd44e30e8461e6
Event Xml:
<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-11-29T21:21:02.208461200Z" />
    <EventRecordID>6208</EventRecordID>
    <Channel>Application</Channel>
    <Computer>IlyaProDesktop</Computer>
    <Security />
  </System>
  <EventData>
    <Data>129584528079</Data>
    <Data>5</Data>
    <Data>AppHangB1</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>Prepar3D.exe</Data>
    <Data>4.1.7.22841</Data>
    <Data>59d67e95</Data>
    <Data>0000</Data>
    <Data>134217984</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA7A3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA7B3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA7B4.tmp.txt
\\?\C:\Users\Ilya\AppData\Local\Temp\WERD278.tmp.appcompat.txt</Data>
    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_Prepar3D.exe_7dbfdbe783a886a39b4204a944aeaa4ab578d_911d388a_145edc2c</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>d2ee2e05-f389-4e90-acde-a21c52377d1b</Data>
    <Data>268435456</Data>
    <Data>67d6e0476771645646fd44e30e8461e6</Data>
  </EventData>
</Event>

 

Spoiler

The program Prepar3D.exe version 4.1.7.22841 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 1ee4
 Start Time: 01d36956ef097cc8
 Termination Time: 24
 Application Path: D:\FSGW P3Dv4\Prepar3D.exe
 Report Id: d2ee2e05-f389-4e90-acde-a21c52377d1b
 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 Hang" />
    <EventID Qualifiers="0">1002</EventID>
    <Level>2</Level>
    <Task>101</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-11-29T21:21:03.054211900Z" />
    <EventRecordID>6209</EventRecordID>
    <Channel>Application</Channel>
    <Computer>IlyaProDesktop</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.1.7.22841</Data>
    <Data>1ee4</Data>
    <Data>01d36956ef097cc8</Data>
    <Data>24</Data>
    <Data>D:\FSGW P3Dv4\Prepar3D.exe</Data>
    <Data>d2ee2e05-f389-4e90-acde-a21c52377d1b</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Binary>55006E006B006E006F0077006E0000000000</Binary>
  </EventData>
</Event>

 

This is from the Security and Maintenance Control Panel.

Spoiler

Source
Prepar3D exe

Summary
Stopped responding and was closed

Date
‎29.‎11.‎17 01:39

Status
Report sent

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:    D:\FSGW P3Dv4\Prepar3D.exe

Problem signature
Problem Event Name:    AppHangB1
Application Name:    Prepar3D.exe
Application Version:    4.1.7.22841
Application Timestamp:    59d67e95
Hang Signature:    0000
Hang Type:    134217984
OS Version:    10.0.16299.2.0.0.256.48
Locale ID:    1033
Additional Hang Signature 1:    00000000000000000000000000000000
Additional Hang Signature 2:    0000
Additional Hang Signature 3:    00000000000000000000000000000000
Additional Hang Signature 4:    0000
Additional Hang Signature 5:    00000000000000000000000000000000
Additional Hang Signature 6:    0000
Additional Hang Signature 7:    00000000000000000000000000000000

Extra information about the problem
Bucket ID:    67d6e0476771645646fd44e30e8461e6 (129584528079)

 

Link to comment
Share on other sites

  • Aerosoft

The log files do not offer any explanation so it will be damned hard to find out why this happens on your system.

 

Is P3d installed in its default location?

Addon installed with admin rights?

Running the sim with admin rights?

Link to comment
Share on other sites

4 hours ago, Mathijs Kok said:

Is P3d installed in its default location?

Addon installed with admin rights?

Running the sim with admin rights?

1. No, it's installed into its own dedicated folder on the local drive D:

2. Yes, with admin rights.

3. Yes, with admin rights.

Link to comment
Share on other sites

  • Deputy Sheriffs
23 hours ago, ClydeCessna said:

Application Path: D:\FSGW P3Dv4\Prepar3D.exe

The path makes me wondering: Why FSGW? Did you install P3D in a folder where already another Software resides like FSGW (FSGlobal Weather)? So maybe files got mixed up and causes problems.

Link to comment
Share on other sites

22 minutes ago, Mathijs Kok said:

One last thing you could try is to remove asc.dll from the panel.cfg.

Okay, I will try that and report. (Not at home right now.)

 

12 minutes ago, mopperle said:

The path makes me wondering: Why FSGW? Did you install P3D in a folder where already another Software resides like FSGW (FSGlobal Weather)? So maybe files got mixed up and causes problems.

No, no, no, this is a special P3D-dedicated folder, I wouldn't do such a stupidity as to install the sim into a folder where some other program resides. 'FSGW' simply stands for "Flight Simulator Golden Wings'. There was a project for FS2004 with this name, and I've been naming my sim install folders like this ever since (FSGW, FSGW X, FSGW P3D).

Link to comment
Share on other sites

7 hours ago, Mathijs Kok said:

One last thing you could try is to remove asc.dll from the panel.cfg.

Mathijs, this did the trick. As soon as I removed it (from the -300 wheeled config), my problems were gone. I could even finally make a flight. Then I immediately loaded a different model with the module enabled (ski equipped), started the engines, shut them down, and the CTD was back.

Link to comment
Share on other sites

Hello! I would like to chime in that I am having this issue as well, though it seems to be a tiny bit different.

 

I can sometimes get the aircraft to load if I load another aircraft first, and then switch to the Twin Otter. However, if I select it in the P3D launcher I will hear the engine sound, see a blank horizon like this, and then P3D crashes.

Please login to display this image.

 

 

Removing the asc.dll file (well, renaming it to asc.dll_bak) did not help fix this for me, unfortunately.

 

Edit: 

@ClydeCessna: Are you running ChasePlane by chance? For me the crash happens if I have ChasePlane loaded when I start the simulator, but not if I have it disabled. It works fine for me if I run the 0.3.70 version of ChasePlane, but the experimental branch 0.4.101 induces a crash to desktop or hang.

Link to comment
Share on other sites

4 hours ago, Tivec said:

 

@ClydeCessna: Are you running ChasePlane by chance? For me the crash happens if I have ChasePlane loaded when I start the simulator, but not if I have it disabled. It works fine for me if I run the 0.3.70 version of ChasePlane, but the experimental branch 0.4.101 induces a crash to desktop or hang.

No, Tivec, I don't use ChasePlane.

Link to comment
Share on other sites

I have run it with admin privileges. Strange that it didn't detect .NET Framework, though...

 

Spoiler

Microsoft Flight Simulator SimConnect Client v10.0.61242.0 - (Version Data: 10.0.61242.0)
Microsoft Flight Simulator SimConnect Client v10.0.61259.0 - (Version Data: 10.0.61259.0)
Microsoft Visual C++ 2005 Redistributable - (Version Data: 8.0.61001.0)
Microsoft Visual C++ 2005 Redistributable (x64) - (Version Data: 8.0.61000.0)
Microsoft Visual C++ 2005 Redistributable (x64) - (Version Data: 8.0.56336.0)
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.17 - (Version Data: 9.0.30729.0)
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.6161 - (Version Data: 9.0.30729.0)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17 - (Version Data: 9.0.30729.0)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161 - (Version Data: 9.0.30729.0)
Microsoft Visual C++ 2010  x64 Redistributable - 10.0.40219 - (Version Data: 10.0.40219.0)
Microsoft Visual C++ 2010  x86 Redistributable - 10.0.40219 - (Version Data: 10.0.40219.0)
Microsoft Visual C++ 2012 x64 Additional Runtime - 11.0.61030 - (Version Data: 11.0.61030.0)
Microsoft Visual C++ 2012 x64 Minimum Runtime - 11.0.61030 - (Version Data: 11.0.61030.0)
Microsoft Visual C++ 2012 x86 Additional Runtime - 11.0.61030 - (Version Data: 11.0.61030.0)
Microsoft Visual C++ 2012 x86 Minimum Runtime - 11.0.61030 - (Version Data: 11.0.61030.0)
Microsoft Visual C++ 2013 x64 Additional Runtime - 12.0.21005 - (Version Data: 12.0.21005.0)
Microsoft Visual C++ 2013 x64 Minimum Runtime - 12.0.21005 - (Version Data: 12.0.21005.0)
Microsoft Visual C++ 2013 x86 Additional Runtime - 12.0.21005 - (Version Data: 12.0.21005.0)
Microsoft Visual C++ 2013 x86 Minimum Runtime - 12.0.21005 - (Version Data: 12.0.21005.0)
Microsoft Visual C++ 2015 x86 Additional Runtime - 14.0.24123 - (Version Data: 14.0.24123.0)
Microsoft Visual C++ 2015 x86 Minimum Runtime - 14.0.24123 - (Version Data: 14.0.24123.0)
Microsoft Visual C++ 2017 x64 Additional Runtime - 14.11.25325 - (Version Data: 14.11.25325.0)
Microsoft Visual C++ 2017 x64 Minimum Runtime - 14.11.25325 - (Version Data: 14.11.25325.0)
Prepar3D v4 Content - (Version Data: 4.1.7.0)
Prepar3D v4 Professional Plus Client - (Version Data: 4.1.7.0)
Prepar3D v4 Scenery - (Version Data: 4.1.7.0)
Prepar3D v4 SDK 4.1.7.22841 - (Version Data: 4.1.7.0)
 

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

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. Privacy Policy & Terms of Use