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

747-400 CTDs in P3D V4.5

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

    747-400 CTDs in P3D V4.5

    Good day,

    I have been experiencing CTDs on my 747-400 recently. The sim loads to 100 percent, then goes black for a while, then P3D closes. Another thing I've tried was to load the default scenario with the F-22 at KVPS, then load the 747 after. This occurs at any airport I've tried using (tested using EHAM and KVPS). I have looked at the Event Viewer and I have gotten a Kernelbase.dll error. No other addons were running at the time these happened. It has run fine in the past, and I was able to complete two long-hauls fairly recently. My specs are in my signature, and the 747 is updated to the newest version available in the Ops Center.

    Code:
    Faulting application name: Prepar3D.exe, version: 4.5.14.34698, time stamp: 0x5e94b5c2
    Faulting module name: KERNELBASE.dll, version: 10.0.18362.959, time stamp: 0x7b90c1b5
    Exception code: 0xc0020001
    Fault offset: 0x000000000003a799
    Faulting process id: 0x2138
    Faulting application start time: 0x01d65c084d7f493c
    Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report Id: 71e63bb3-14be-40b8-8d1b-688abae79f5a
    Faulting package full name:
    Faulting package-relative application ID:
    I have gone through some solutions to no avail, including
    • Running Windows Update
    • Updating graphics card drivers
    • Updating C++ redistributables
    • Clearing P3D.cfg
    • Clearing shaders
    • Disabling GSX/Addon Manager (has contributed to this in the past)
    • Adding PMDG entries to the dll.xml (oddly, the 747 worked fine in the past without them!)
    Hope anyone will be able to help me with this. Feel free to ask me for more info regarding the problem. Thanks in advance!
    Miguel Ceballos
    P3Dv4: 747-400 QOTS II, FSX:SE: 737NGX and MD-11
    Specs:
    Intel Core i3-7100U, NVIDIA GeForce MX150 @2GB VRAM, 4GB RAM, 1TB HDD
    Other addons: GSX, FSXWX, FSCaptain 1.8.2, LittleNavMap, SimToolkitPro

    #2
    Hello Miguel,

    from http://www.prepar3d.org/forum/viewtopic.php?t=135620


    The first thing you need to do if an overclocked (or even a non-overclocked) system becomes unstable, is to check if the ventilation openings, fans etc are clogged. If so, clean them.

    However, in such a case it may not always be a kernelbase.dll error that comes up.

    For this error, google "kernelbase.dll error" or a similar string. There will be a lot of possible causes and resolutions coming up, you need to go through them all and apply solutions as appropriate for your system

    This is not a P3D error per se, it is a Windows error that P3D triggers.
    Jude Bradley
    System specs: Windows 10 Pro 64-bit, i9-9900KF Gigabyte Z390, RTX-2070, 32GB RAM Prepar3D V5 X-Plane 11.50 Beta tester for MS2020
    http://downloads.pmdg.com/forum/Signatures/PMDG_Banner_777_Pilot.jpg

    Comment


      #3
      Originally posted by Philippine747 View Post
      Good day,

      I have been experiencing CTDs on my 747-400 recently. The sim loads to 100 percent, then goes black for a while, then P3D closes. Another thing I've tried was to load the default scenario with the F-22 at KVPS, then load the 747 after. This occurs at any airport I've tried using (tested using EHAM and KVPS). I have looked at the Event Viewer and I have gotten a Kernelbase.dll error. No other addons were running at the time these happened. It has run fine in the past, and I was able to complete two long-hauls fairly recently. My specs are in my signature, and the 747 is updated to the newest version available in the Ops Center.

      Code:
      Faulting application name: Prepar3D.exe, version: 4.5.14.34698, time stamp: 0x5e94b5c2
      Faulting module name: KERNELBASE.dll, version: 10.0.18362.959, time stamp: 0x7b90c1b5
      Exception code: 0xc0020001
      Fault offset: 0x000000000003a799
      Faulting process id: 0x2138
      Faulting application start time: 0x01d65c084d7f493c
      Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
      Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
      Report Id: 71e63bb3-14be-40b8-8d1b-688abae79f5a
      Faulting package full name:
      Faulting package-relative application ID:
      I have gone through some solutions to no avail, including
      • Running Windows Update
      • Updating graphics card drivers
      • Updating C++ redistributables
      • Clearing P3D.cfg
      • Clearing shaders
      • Disabling GSX/Addon Manager (has contributed to this in the past)
      • Adding PMDG entries to the dll.xml (oddly, the 747 worked fine in the past without them!)
      Hope anyone will be able to help me with this. Feel free to ask me for more info regarding the problem. Thanks in advance!
      Miguel open a support ticket at support.pmdg.com
      Danny Z.Cebis

      Comment


        #4
        Originally posted by Jude Bradley View Post
        Hello Miguel,

        from http://www.prepar3d.org/forum/viewtopic.php?t=135620


        The first thing you need to do if an overclocked (or even a non-overclocked) system becomes unstable, is to check if the ventilation openings, fans etc are clogged. If so, clean them.

        However, in such a case it may not always be a kernelbase.dll error that comes up.

        For this error, google "kernelbase.dll error" or a similar string. There will be a lot of possible causes and resolutions coming up, you need to go through them all and apply solutions as appropriate for your system

        This is not a P3D error per se, it is a Windows error that P3D triggers.
        Hi, thanks for the suggestion!

        My ventilation seems to be okay, and my unit is not overheating. Will have to give it a clean later on anyway... but for now I think I can discount this.
        Miguel Ceballos
        P3Dv4: 747-400 QOTS II, FSX:SE: 737NGX and MD-11
        Specs:
        Intel Core i3-7100U, NVIDIA GeForce MX150 @2GB VRAM, 4GB RAM, 1TB HDD
        Other addons: GSX, FSXWX, FSCaptain 1.8.2, LittleNavMap, SimToolkitPro

        Comment


          #5
          Originally posted by Ausflight View Post

          Miguel open a support ticket at support.pmdg.com
          Will do. Thanks!
          Miguel Ceballos
          P3Dv4: 747-400 QOTS II, FSX:SE: 737NGX and MD-11
          Specs:
          Intel Core i3-7100U, NVIDIA GeForce MX150 @2GB VRAM, 4GB RAM, 1TB HDD
          Other addons: GSX, FSXWX, FSCaptain 1.8.2, LittleNavMap, SimToolkitPro

          Comment


            #6
            Hi all,

            Just an update. I have reinstalled P3D, and when I did, there was no luck. However, after disabling RAAS in the dll.xml, the CTDs have dissapeared. Hopefully someone will find this information useful. Thanks for all your suggestions!
            Miguel Ceballos
            P3Dv4: 747-400 QOTS II, FSX:SE: 737NGX and MD-11
            Specs:
            Intel Core i3-7100U, NVIDIA GeForce MX150 @2GB VRAM, 4GB RAM, 1TB HDD
            Other addons: GSX, FSXWX, FSCaptain 1.8.2, LittleNavMap, SimToolkitPro

            Comment

            Working...
            X