Announcement

Collapse

PMDG Forum Rules

1) SIGN YOUR POSTS. Since 1997, we have asked users to sign their real name, first and last, to all posts in the PMDG forum. We do this in order to keep conversations personal and familiar. You took the time to be here, we want to get to know you. This is one of the few rigid rules that we enforce regularly. We do so because we feel that forums in which users must engage one another personally are generally warmer, more collegial and friendly. Posts that are unsigned will be quietly removed without comment by the moderators, so to make your life easy- we recommend enabling your forum signature so that you never need to remember. Do this by clicking the username pull-down at the top right, then selecting "User Settings." You will find the signature editor on the ACCOUNT tab, about half way down the page. Look for "Edit Post Signature." Be sure to click the "Show Signatures" box.

2) BE NICE. We are all simmers here and no matter our differences of opinion, we share a common love of aviation, computing and simulation. Treat everyone else in the forum with respect even when you disagree. If someone frustrates you, walk away from the conversation or ask for a moderator to get involved. Speaking of Moderators, they prefer not to be treated as "The Thought Police" but if any behavior infringes on the enjoyment of another user or is otherwise considered to be unacceptable in the moderator's judgment, it will be addressed in keeping with our view of ensuring that this forum remains a healthy environment for all simmers.

3) BE LAWFUL: Any behavior that infringes upon the law, such as discussion or solicitation of piracy, threats, intimidation or abuse will be handled unsympathetically by the moderators. Threats and intimidation may, at the moderator's discretion, be provided to law enforcement for handling.

4) BE FACTUAL: When you post, always be factual. Moderators will remove posts that are determined not to be factually accurate.

5) RESPECT COPYRIGHTS: Posting of copyrighted material such as flight manuals owned by Boeing or various airlines is not allowed in this forum. If you have questions related to copyrighted material, please contact a forum moderator for clarification.

6) RESPECT PMDG: We love to hear what you like about our products. We also like to hear what you think can be improved, or what isn't working. Please do tell us and we will always treat your feedback with value. Just be sure to treat the team respectfully, as they do put a significant amount of effort into building and maintaining these great simulation products for you.

7) RESPECT PMDG DEVELOPERS: All of the developers will spend some time here. Given the ratio of developers-to-users, it simply isn't possible for us to answer every post and private message individually. Please know that we do try to read everything, but developer workload is simply too high to manage personal contact with tens-of-thousands of users simultaneously. In most cases, members of the development team will stick to conversations in the forum and will not answer private messages.

8) RESPECT OTHER DEVELOPERS: PMDG has always advocated for a strong development community and we have many friends within this community. Every developer offers something unique that helps to make the simming community larger and more vibrant. We insist that you treat our friends respectfully.

9) RESPECT MODERATORS: Moderators have a tough job, and none of them enjoy having to stomp out negativity. If a moderator has to weigh in to keep a thread peaceful, please respect that effort and refrain from giving the moderator any grief.

10) If you require official support for any of our products please open a support ticket through the support portal, https://support.precisionmanuals.com

11) This forum is designed primarily as a vehicle for the PMDG development team to interact with our customers, and for customers to interact with one another in a manner that is positive, supportive and assists in the general advancement of understanding the simulation and helping to make this and future simulations better. Any other use of this forum is not permitted, including but not limited to discussion of pricing policies, business practices, forum moderating policies, advertising of non-PMDG products, promotion of events, services or products that are not approved in advance by PMDG or any other topic deemed unacceptable by any forum administrator

12) HAVE FUN: This is the whole point of it all.
See more
See less

CTD after click to open Airport Map in EFB

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    CTD after click to open Airport Map in EFB

    Hi Captains,

    I sporadically get a CTD when clicking to open the Airport Map in the NGXu's EFB. Has anyone else experienced this? Here is the error info:

    Source
    Prepar3D exe

    Summary
    Stopped working

    Date
    ‎5/‎21/‎2021 4:22 PM

    Status
    Report sent

    Description
    Faulting Application Path: C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe

    Problem signature
    Problem Event Name: APPCRASH
    Application Name: Prepar3D.exe
    Application Version: 5.1.12.26829
    Application Timestamp: 5fb44f72
    Fault Module Name: mso20win32client.dll
    Fault Module Version: 0.0.0.0
    Fault Module Timestamp: 6093ad5f
    Exception Code: c0000005
    Exception Offset: 0000000000018c89
    OS Version: 10.0.19042.2.0.0.256.48
    Locale ID: 1033
    Additional Information 1: 390b
    Additional Information 2: 390b2c0e7e8271e202b5febec30dd55d
    Additional Information 3: 5c4f
    Additional Information 4: 5c4fce758116efe5164fbeeade15c936

    Extra information about the problem
    Bucket ID: 99e1c4b9e1b90d07b084f84ddb56c55d (1190349214808720733)


    Thanks!

    Luis
    Luis Linares

    #2
    g2d.dll has been the fault module on the other CTDs after I try to open the airport map
    Luis Linares

    Comment


      #3
      Yep. Happened once here. I use it on every single flight and it’s very rare that CTD, maybe 1 every 100 flights or more so I did not care. Not an scenery issue because I did the same flight later and worked fine.
      Joan Alonso

      Comment


        #4
        The faulting module "mso20win32client.dll" caught my eye. I've seen crash reports in this forum several times with this module implicated.

        This module is a part of your Office365 I believe (I do not use that product so I can only go by what I read). A google of this module turns up thousands of links but maybe you can find an earlier post in this forum with a potential solution.

        The obvious is to make sure your Office is up to date.
        Dan Downs KCRP
        i7-10700K 32GB 3600MHz 2080Ti

        Comment


          #5
          Yes, avsim and other developer forums are full of it.

          https://a2asimulations.com/forum/vie...?f=139&t=71964

          solution down the page
          Last edited by Ephedrin; 21May2021, 17:59.
          i7-6700k, GTX 1080TI, 32GB DDR4 RAM @2666MHz, 4k
          Marc Ehnle

          Comment


            #6
            Originally posted by Ephedrin View Post
            Yes, avsim and other developer forums are full of it.

            https://a2asimulations.com/forum/vie...?f=139&t=71964

            solution down the page
            Thanks for the info!
            Luis Linares

            Comment

            Working...
            X