Jump to content

CTD


strider
 Share

Recommended Posts

Had yesterday also 2 CTD's
The first one pointed towards my nvidia graphics driver. So i updated it. Flew same trip as before. This time the flight lasted longer, but in the long Final towards. 

 

Searched in the log for TBM Related errors

Right at the beginning i found this, guess it points to the Charts feature?

Quote

2019-07-01 18:43:47 TBM900[helpers.c:1029]: Cannot stat D:\X-Plane 11\\Output\TBM900\charts.db\aeronav.faa.gov\1906: Zugriff verweigert

2019-07-01 18:43:47 TBM900[helpers.c:1029]: Cannot stat D:\X-Plane 11\\Output\TBM900\charts.db\autorouter.aero\1906: Zugriff verweigert

It say's Access denied

Also a little later

Quote

2019-07-01 18:47:00 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 1052

2019-07-01 18:47:00 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2002

2019-07-01 18:47:00 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2013

2019-07-01 18:47:00 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2045

2019-07-01 18:47:00 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2095

2019-07-01 18:47:00 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2838

2019-07-01 18:47:00 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 3319

2019-07-01 18:47:00 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 4611

2019-07-01 18:47:00 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5558

2019-07-01 18:47:00 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5569

2019-07-01 18:47:00 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5600

2019-07-01 18:47:00 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5651

2019-07-01 18:47:00 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 6394

And at the end it looks like this

Quote

LiveTraffic 1562002730.8 WARN  src\LTFlightData.cpp:2129/CreateAircraft: Tracking data for '440159' (man '', mdl '') lacks ICAO a/c type code, will be rendered with standard a/c A320
LiveTraffic 1562002771.8 WARN  src\LTFlightData.cpp:2129/CreateAircraft: Tracking data for '738444' (man '', mdl '') lacks ICAO a/c type code, will be rendered with standard a/c A320
LiveTraffic 1562002909.9 WARN  src\LTFlightData.cpp:2080/CreateAircraft: Reached limit of 10 aircrafts, will create new ones only after removing outdated ones.
2019-07-01 19:47:20 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000
2019-07-01 19:47:27 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION
Backtrace is:
0 00007FFFB57B8139 D:\X-Plane 11\Resources\plugins\LiveTraffic\64\win.xpl+0000000000058139 ()
1 00007FFFB57909D4 D:\X-Plane 11\Resources\plugins\LiveTraffic\64\win.xpl+00000000000309D4 ()
2 00007FFFB58ABED4 D:\X-Plane 11\Resources\plugins\LiveTraffic\64\win.xpl+000000000014BED4 ()
3 00007FFFB5794B4F D:\X-Plane 11\Resources\plugins\LiveTraffic\64\win.xpl+0000000000034B4F ()
4 00007FFFB5794B40 D:\X-Plane 11\Resources\plugins\LiveTraffic\64\win.xpl+0000000000034B40 ()
5 00007FFFB5794B40 D:\X-Plane 11\Resources\plugins\LiveTraffic\64\win.xpl+0000000000034B40 ()
6 00007FFFB5794B40 D:\X-Plane 11\Resources\plugins\LiveTraffic\64\win.xpl+0000000000034B40 ()
7 00007FFFB579445F D:\X-Plane 11\Resources\plugins\LiveTraffic\64\win.xpl+000000000003445F ()
8 00007FFFB5794CCF D:\X-Plane 11\Resources\plugins\LiveTraffic\64\win.xpl+0000000000034CCF ()
9 00007FFFB58D29F8 D:\X-Plane 11\Resources\plugins\LiveTraffic\64\win.xpl+00000000001729F8 ()
10 00007FF806813E26 C:\WINDOWS\System32\ucrtbase.dll+0000000000013E26 ()
11 00007FF806813D4B C:\WINDOWS\System32\ucrtbase.dll+0000000000013D4B ()
12 00007FF806813D04 C:\WINDOWS\System32\ucrtbase.dll+0000000000013D04 ()
13 00007FFFB5884A22 D:\X-Plane 11\Resources\plugins\LiveTraffic\64\win.xpl+0000000000124A22 ()
14 00007FFFB5884B48 D:\X-Plane 11\Resources\plugins\LiveTraffic\64\win.xpl+0000000000124B48 ()
15 00007FF80A418F07 C:\WINDOWS\SYSTEM32\ntdll.dll+0000000000048F07 ()
16 00007FF80A4135BC C:\WINDOWS\SYSTEM32\ntdll.dll+00000000000435BC ()
17 00007FF80A436DCD C:\WINDOWS\SYSTEM32\ntdll.dll+0000000000066DCD ()
18 00007FF80815D62A C:\WINDOWS\System32\KERNEL32.DLL+000000000001D62A ()
19 00007FF80A2BA2E5 C:\WINDOWS\System32\msvcrt.dll+000000000003A2E5 ()
20 00007FF80A2BA955 C:\WINDOWS\System32\msvcrt.dll+000000000003A955 ()
21 00007FF80A2AF2FD C:\WINDOWS\System32\msvcrt.dll+000000000002F2FD ()
22 00000000809CF802 D:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+00000000009DF802 ()
23 00000000809CF8B7 D:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+00000000009DF8B7 ()
24 0000000080189B29 D:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+0000000000199B29 (cairo_scaled_font_destroy+c9)
25 00000000801A5C11 D:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+00000000001B5C11 (_cairo_gstate_rotate+51)
26 0000000080195409 D:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+00000000001A5409 (cairo_rotate+19)
27 000000008002CEA5 D:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+000000000003CEA5 (draw_perf_ind+805)
28 000000008002EB3A D:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+000000000003EB3A (eicas_render+11a)
29 000000008014E136 D:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+000000000015E136 (worker+136)
30 00007FF808157974 C:\WINDOWS\System32\KERNEL32.DLL+0000000000017974 ()
31 00007FF80A43A271 C:\WINDOWS\SYSTEM32\ntdll.dll+000000000006A271 ()

Maybe the plugin LiveTraffic is the Problem?

I Also use ASXP, but found nothing in the log at the time of the CTD
 

Quote

19:35:37:0361-Building cloud data...
19:35:37:0406-XPL METAR at aircraft position: MDEG 5.500000 52.500000 0.00 28010KT 56SM SCT024 17/16 Q1016
19:35:37:0441-Copying cloud data file...
19:35:38:0982-Cloud data load signalled
19:35:38:0987-Aircraft location on cloud data load: lat = N52° 37' 4.38" lon = E05° 39' 12.21" alt = 16544 feet
19:35:38:0992-Ground elevation at aircraft location on cloud data load: -12
19:47:33:0495-failed to receive sim events: Error reading from pipe. Internal error: 109
19:47:33:0500-XPlane connection not established!
19:47:33:0515-failed to send pws info: Error reading from pipe. Internal error: 109
19:52:45:0939-1 new items have been added to the user edited version of  Weather stations data. K77S
19:52:47:0512-ASMapImage file in use while copying blank image on exit

 

Regards

Log.txt

Edited by flieger28
ASXP
Link to comment
Share on other sites

Deactivated Livetraffic and was able to do the flight which yesterday crashed. However after the flight, engine off, i opened acelogbook. And another Crash

AceAPI [ AceLogbook ]: Landing.
AceAPI [ AceLogbook ]: Valid flight.
AceAPI [ AceLogbook ]: Saving database: [X-PLANE]/acelogbook.csv
1:45:54.735 I/ATC: Airport flow changed at EHKD!
CurFlow: AUTOGEN: West NewFlow: AUTOGEN: North
1:45:54.735 I/ATC: Changing EHKD CabState from 0 to 1
1:45:54.735 I/ATC: All departures are done at EHKD. Advancing...
1:45:54.735 I/ATC: Changing EHKD CabState from 1 to 2
1:45:54.735 I/ATC: All arrivals are done at EHKD. Advancing...
1:45:54.735 I/ATC: Changing EHKD CabState from 2 to 0
1:46:05.283 I/ATC: Airport flow changed at EHBD!
CurFlow: ATC Flow Calm Winds 03 NewFlow: ATC Flow Severe Winds 03
1:46:05.283 I/ATC: Changing EHBD CabState from 0 to 1
1:46:05.283 I/ATC: All departures are done at EHBD. Advancing...
1:46:05.283 I/ATC: Changing EHBD CabState from 1 to 2
1:46:05.283 I/ATC: All arrivals are done at EHBD. Advancing...
1:46:05.283 I/ATC: Changing EHBD CabState from 2 to 0
1:46:17.485 I/ATC: Airport flow changed at EHEH!
CurFlow: rwy 21 Flow under 5 kt NewFlow: rwy 03 Flow
1:46:17.485 I/ATC: Changing EHEH CabState from 0 to 1
1:46:17.485 I/ATC: All departures are done at EHEH. Advancing...
1:46:17.485 I/ATC: Changing EHEH CabState from 1 to 2
1:46:17.485 I/ATC: All arrivals are done at EHEH. Advancing...
1:46:17.485 I/ATC: Changing EHEH CabState from 2 to 0
2019-07-02 21:13:54 TBM900[elec.c:1202]: MAIN GEN tripped (25.1A, 28.2V, rpm: 0)
2019-07-02 21:16:18 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000

Link to comment
Share on other sites

This kind of error only happens occasionally and under specific circumstances.  The major problem with it, as it states "something has reinstalled our exception handler", it does not state what has reinstalled the exception handler.  So it's almost impossible to pinpoint.  It could be to do with the location, plugins that are running, or some other kind of random element.  If it keeps happening repeatedly, I'm afraid the only other thing left to do is to remove all plugins (except Gizmo), and re-try, while adding the plugins back, 1 at a time, and trying each time until it happens again.  That will tell you if it's a plugin related issue.  

 

Link to comment
Share on other sites

And here is another user with a similar problem and CTD as below:

 

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2002

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2013

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2045

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2095

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2838

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 3319

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 4611

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5558

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5569

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5600

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5651

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 6394

2019-07-09 13:42:51 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000

Link to comment
Share on other sites

8 hours ago, jetset said:

And here is another user with a similar problem and CTD as below:

 

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2002

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2013

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2045

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2095

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 2838

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 3319

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 4611

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5558

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5569

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5600

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 5651

2019-07-09 10:34:43 TBM900[navaiddb.c:512]: Error parsing D:\X-Plane 11\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 6394

2019-07-09 13:42:51 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000

We need the entire log file.  Because that error is so vague, the first, among many things we look at, is what other plugins are installed.  

Link to comment
Share on other sites

Since this is a CTD thread, I'll leave this here.

I have no issues whatsoever with the TBM 900. I can fly around and complete multiple flights without a single issue. I haven't had a CTD while flying ever. However, my sim crashes upon exit every single time I am parked on the ramp with the TBM 900 and quit the sim. If I swap aircraft before exiting, all is well. What can my issue possibly be?

 

2019-07-11 18:45:36 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION
Backtrace is:
0 00007FF60A7B4FB0 F:\X-Plane 11\X-Plane.exe+00000000009A4FB0 ()
1 00007FFA41A0158A F:\X-Plane 11\Resources\plugins\XPLM_64.dll+000000000001158A ()
2 00007FF9E3A55B04 F:\X-Plane 11\Resources\plugins\SkunkCraftsUpdater\64\win.xpl+0000000000035B04 ()
3 000000000000000D F:\X-Plane 11\X-Plane.exe+000000000000000D ()
4 00000165DDB6C918 F:\X-Plane 11\X-Plane.exe+00000165DDB6C918 ()

 

Log.txt

TBM900_Log.txt

Edited by shivanandrs
Link to comment
Share on other sites

Hi Goran,

I haven't had the Something reinstalled our exception handler CTD for a long time. After installing the stuff needed to use IVAO (X-IVAP & Teamspeak) XP generally crashes after 10 or 20 minutes, even sitting on the ground, making it completely impossible to use. I understand that you guys have a hard time finding the root cause because of a lack of clues, but it seems the Hot Start TBM has a particular problem with many  plugins (IF that is in fact a cause) , which most planes do not have. Please, please, work more on this... Creating an instrumented image to get additional traces when crashing comes to mind... Thanks !

Link to comment
Share on other sites

These are not that easy to isolate, due to the fact in a lot of cases, it's the TBM exploiting bugs in other software.  I'm not saying this is happening 100% of the time, but it does happen a lot.  Check your log.txt file after a crash, and scroll down to the bottom.  The "backtrace" should tell you exactly what caused the crash.  

In your particular instance, the crash could well be a combination of IVAO and Teamspeak, AND maybe another plug in or plug ins, along WITH the TBM.  Of course, we'll take a look and see what can be done, but the difficulty of this depends on what other plugins you have, and if any of those have any bugs in them.  

First step is the backtrace.

Link to comment
Share on other sites

Hi Goran,

Thanks for your reply. I didn't include the log, because it never seems to be useful for this crash. Which is why I'm mentioning that you might provide instrumented code to help you make progress. I would certainly volunteer to run it.

I've seen you write several times that the TBM is "exploiting bugs in other software". That's a strange way of putting things. IF that is the problem (remains to be seen), please stop "exploiting" buggy code ?!?!

Do you know of other products causing this CTD ? It  has been around for a long time now. I don't see any progress. Eliminating other plugins isn't a solution, at best a temporary workaround.

This started to re-occur for me after installing IVAO. IVAO may be causing problems with the TBM, but IVAO is being used successfully by thousands of other users with other planes, the TBM shouldn't crash with it.

Thank you.

Note: It could be that I have not installed IVAO correctly, but when there's no CTD, it seems to work fine.

Log.txt

Link to comment
Share on other sites

Xpst, I do understand your frustration. But we need to remember the TBM pushes xplanes limits in so many ways, like little or no other payware does. I think Hotstart could easily get rid of the problems if they stop coding around xplanes limitations and just provide default functionality packed in a nice looking model. That would mean no custom G1000, no synthetic vision, no custom weather radar or TAWS, etc... 

... You get the idea.

 

I highly appreciate what they do even if that means I have to stop using specific third party plugins temporarily. 

Link to comment
Share on other sites

"exploiting bugs in other plugins" isn't done deliberately by any developer.  Also, I'm only echoing Saso's comments about how 1 add ons code can conflict with another one, in an exploitative way and cause a crash.  These bugs are almost always accientally overlooked by the developer. 
An example is X-Plane crashing whenever the Saab was run with xEnviro.  Jim (Saab coder)and Ben (Gizmo creator) combed through the Saab code AND Gizmo code to see if there was anything that could cause a crash.  They found nothing.  I approached Andrej, xEnviro's developer, and told him about this, and he thought I was crazy when I told him it's almost definitely something with his software.  He finally relented and sent out test builds to a few testers, and within half an hour, the testers sent in results, and he found a bug within xEnviro that would cause it to crash...only while fetching weather, and only when the Saab was running.  He was very surprised. 
Using that example, we could agree the Saab was exploiting an overlooked bug in the xEnviro code.  It wasn't intentional by us, but it shed light on an annoying problem people were having, and it has now been addressed in the latest xEnviro update.  

Now imagine us approaching every developer, asking them to check through their code to see if there are any issues with their software.  Wouldn't go down to well.  

In your case, I would bet money that it's a problem with IVAO.  Unlikely that it's teamspeak.  As I said, I'll note this down and present it to Saso.  If it IS the TBM, you can bet he'll find it and fix it.  
In any case, we appreciate your patience.  
 

Link to comment
Share on other sites

I have far too many sim aircraft, but I love fast planes so the TBM 900 was too tempting to avoid purchasing. In the beginning, I had about 1 crash in every 3 flights, which I found unacceptable. I don't use IVAO, by the way. What I found in the logs was that no entry was written for a long time, then suddenly the exception handler reset appeared which caused the CTD.

I'm no programmer, but I'm a software specialist, having been a software advisor for many huge developers of professional software. Problem-seeking and solving is thus a strength of mine. I believe the CTD is caused by the aircraft itself, its systems. I thought of the X-1000, which I'm no huge fan of, with moving maps and whatnot. So I tried to turn off the synthetic vision, but still got the CTD. Then I turned off the FPS message appearing every time the sim loads new weather and clouds. And... I haven't had a crash in 5 or 6 trips now. Coincidence? Perhaps, I'll fly more trips to see and experience.

Nice aircraft, but I would like the spinner cone adjusted, please, so that it moves smoothly and not askew. And the X-1000's FD cue doesn't work when turning off AP during ILS and RNAV approach. Overall, a fantastic sim aircraft which has dethroned my favourite single prop aircraft in any sim. So nice to be able to put registration on the aircraft! Well done to the devs!

Link to comment
Share on other sites

  • 2 weeks later...

I love the plane and how it flies ..... when it flies.

For me it has been a frustrating experience, with nothing but crashes and "Memory could not be read" messages.
No other aircraft in X-Plane give me these problems, only the TBM does. I just tried a little flight from EDDH - Hamburg to EKCH - Copenhagen and 3 times X-Plane just crashed to desktop and 1 time the weird memory error. Just to be sure I'll run a memtest later, but since no other aircraft in XPlane, nor any other application gives me this error I'm thinking my memory is actually fine.
Yesterday I had the same problems flying from EHRD to EDDH, it took three attempts, with 2 CTDs and 1 successfull flight.

The log reads the same as mentioned before:

2019-07-25 09:45:29 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION
Backtrace is:
0 0000021435750104 D:\X-Plane 11\X-Plane.exe+0000021435750104 ()
1 000002174A81F96C D:\X-Plane 11\X-Plane.exe+000002174A81F96C ()

I really like the plane (although i do think some clickspots are a little hard to find, especially in the dark) and I would really like to fly it, but for now it's parked in the hangar, because 85% of my flights seem to end in CTDs (which is really frustrating if you just spent half an hour or more on flightplanning, etc.)

Any idea what could be the problem? I read something about LiveTraffic which could be a problem, has that been confirmed?

Link to comment
Share on other sites

Could you post your entire log after the crash? 

My guess is your settings are too high for either your RAM or VRAM.  The TBM is very graphics heavy, with over 2 million polygons and around 40 different objects and textures.  But it still runs on many systems as long as the settings are configured for the type of hardware you have.

Link to comment
Share on other sites

Well, I updated XPlane to the latest beta 11.35 and also disabled LIveTraffic.
Where in the earlier attempts XPlane often crashed very early on (still on the ground in EDDH), this time I almost made it to Copenhagen, but unfortunately just before turning onto the ILS i got an error again, but this time it is a different error, so it seems disabling LiveTraffic solved at least part of the problem.

I doubt it is hardware related, but here are my PC specs:

  • Asus ROG Strix X470-F GAMING
  • AMD Ryzen 7 2700 Wraith Boxed
  • G.Skill Ripjaws V F4-3200C14D-16GVK
  • Asus ROG STRIX-GTX1080-8G-GAMING
  • NZXT Kraken X62

 

 

TBM900_Log.txt

Log.txt

Edited by HansMatthijssen
Link to comment
Share on other sites

I see a potential problem.  16GB RAM, and you have a LOT of plugins installed.  Plugins chew up a lot of RAM.  Removing LiveTraffic just lightened the load on the RAM and that's why you didn't get a crash until much later in the flight, likely when you may have been approaching some dense scenery.  Do you have a lot of orthoscenery installed?  Are your settings dialled up very high?

As a test, remove half your plugins, preferably ones that you don't use very often, and then try again.  Just make sure you leave Gizmo in there.

 

Link to comment
Share on other sites

I'm with @Goran_M on this one.  I have 16GB RAM as well but have never had a crash with the TBM.  Like many XP users I have far too many payware aircraft - I experience much higher FPS and much lower RAM / VRAM usage with all of them.  I also use Ortho and the usual suspects for plugin's.  The use of HD Mesh AND Ortho AND the TBM has the potential to overwhelm your hardware.  The CPU is just "OK" for XP but it is a bit slow - all those cores (over 4) don't help. I have an i5-6600K@4.1, 16GB of 3000 RAM and a 1070 8GB - settings are HDR, max compressed and high objects.  No shadows, parked aircraft or AI.  Absolutely no issues with the TBM.  35+ FPS at MisterX KLAX.  Try disabling the HDMesh - that may help.  You have "hung" a lot of "stuff" on your XP install and may have hit a wall...

Link to comment
Share on other sites

I guess that makes sense.
Most of the plugins are things i bought/use though, like X-Camera, Active Sky and the RealityXP GTN (which i could disable when flying the TMB I suppose) and some small 'connector' plugins for Navigraph and LittleNavMap. I do have HDMesh installed, but no Orthophotos for the region where the crashes occur, instead I'm using "Enhanced Autogen" for that region.

I will start to monitor how much RAM is used and if necessary upgrade to 32GB (and possibly  a 3700X in a while).
Thanks all for your support.
 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...