I have had cdp_mfd_sim_400.dll crash on me, flying near Livorno, Italy, trying to access the terrain page.  That's the first time that has ever happened, so I may just ignore it.

In your view, should I send the event viewer data to RealityXP, or, not worry about it?
 

Hi,

I'm sorry for the delay. Yes I'd be interested in the crash event data please.

You might want to also use this tool for this:
https://www.nirsoft.net/utils/app_crash_view.html

PM sent

Further update on your crash:

Someone is having a CTD in X-Plane when approaching LIRP twice in a row:

https://forums.x-plane.org/index.php?/forums/topic/188887-ctd-at-lirp/&tab=comments#comment-1729954

Could it be the procedure(s) for this airport, which X-Plane DB, Navigraph and the Garmin DB get basically from the same source, contain an error which makes all devices using this (these) procedures to crash?

Please note there are some DB exclusion and these may affect the GNS depending (LIRP is listed):
https://avdb.garmin.com/docs/garmin_data_exclusions.html

Plus all other Garmin Aviation Alerts and Advisories:
https://www.garmin.com/en-US/aviationalerts/category/aviation-database-alerts/

Edited August 26, 20196 yr by RXP

Hmm the other people having issues around LIRP is interesting.

One thing is for certain, if it is an issue in the 1909 Navigraph data then it may disappear with the next update. Then again it may not, ha ha.

Is it possible, in the RXP GNS code, to have an error-trapping routine where if the data suddenly disappears or is anomalous, the unit displays a NO DATA or similar error message?  Or, due to the random nature of that type of error, is it not possible to trap it?

It is not as simple as this because we're not talking about a well known piece of data. Instead, the crash you've reported is about data put in some transient memory, which the trainer typically allocate/share/free in many places and numerous times. It is not supposed to introduce any error either.

Otherwise there are other cases where the trainer explicitly checks its 'run state' and if these fail we can intercept and log these. Please see the troubleshooting section of the RXP GNS User's Manual.