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,

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

p3d v4.5: 747-8 and 737-700: Prepar3d crash after GPU 3D spike?

  • Filter
  • Time
  • Show
Clear All
new posts

    p3d v4.5: 747-8 and 737-700: Prepar3d crash after GPU 3D spike?

    Hi folks,

    happily I (successfully) installed the QOTSII and NGX yesterday.

    However, during my flights
    ... I suffered prepar3d crashes:
    The program simply vanished,
    and in the task manager I found a 100% spike in the 3D graph.

    What's going on?
    Somebody else experiencing this?

    Thanks in advance.
    Andre(as) Berg --- i7 8700K 12MB 3.7G. MSI Z370 Tomahawk. DDR4 16G. SSD 500G M.2. MSI RTX2080 DUKE 8G

    Additional information:
    I could complete the long distance flight without a 2nd prepar3d crash.
    Andre(as) Berg --- i7 8700K 12MB 3.7G. MSI Z370 Tomahawk. DDR4 16G. SSD 500G M.2. MSI RTX2080 DUKE 8G


      Any information in event viewer?
      Last edited by Jude Bradley; 06Jul2020, 21:32.
      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


        Hi Jude,

        that's the error I found in System:

        The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.

        06.07.2020 20:58:49
        <Event xmlns="">
        - <System>
        <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
        <EventID Qualifiers="0">10010</EventID>
        <TimeCreated SystemTime="2020-07-06T18:58:49.963577700Z" />
        <Correlation ActivityID="{32ffeec6-a1ef-48f9-aa26-ca962a66dbad}" />
        <Execution ProcessID="748" ThreadID="1992" />
        <Security UserID="S-1-5-21-1333033633-3193039413-4183067695-1001" />
        - <EventData>
        <Data Name="param1">{9BA05972-F6A8-11CF-A442-00A0C90A8F39}</Data>

        But this error came after my frustrated power-off:

        06.07.2020 20:58:48
        The process C:\Windows\System32\RuntimeBroker.exe (...) has initiated the power off of computer ...on behalf of user ...\User for the following reason: Anderer Grund (nicht geplant)
        Reason Code: 0x0
        Shut-down Type: power off

        A couple of minutes before Application reported:
        06.07.2020 20:54:35
        Updated Avira Antivirus status successfully to SECURITY_PRODUCT_STATE_ON.

        Any ideas?
        Does look as if connected to the prepar3d crash.
        Andre(as) Berg --- i7 8700K 12MB 3.7G. MSI Z370 Tomahawk. DDR4 16G. SSD 500G M.2. MSI RTX2080 DUKE 8G


        • Ephedrin
          Ephedrin commented
          Editing a comment
          Putz mal den Lüfter deines Netzgeräts

        Hi folks,

        it happened again on my second trial to fly EHAM-EGPO:
        Climbing out from rwy 24 just before ROKAN and FL380 prepar3d crashed.

        Before the sound sounded weird.
        - I pressed Q twice as it sometimes helps to recover the sound, but the simulation was already doomed and crashed a second later.
        Again a GPU 3D spike
        No Errors in the Event Viewer System,
        but Application shows one:
        svchost (13644,R,98) TILERPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\sstemprofile\AppData\Lo cal\TileDataLayer\Database\EDB.log

        These prepar3d crashes take some joy out of my flights.
        (This time I store every couple of minutes the situation, so I can step in again, but....)

        After reloading the ACARS OOOI is lost...

        Any ideas?
        Last edited by 19ab67; 07Jul2020, 20:34. Reason: editiorials
        Andre(as) Berg --- i7 8700K 12MB 3.7G. MSI Z370 Tomahawk. DDR4 16G. SSD 500G M.2. MSI RTX2080 DUKE 8G


          From the Windows Reliability History:

          Faulting Application Path: C:\_prepar3Dv4_\Prepar3D.exe

          Problem signature
          Problem Event Name: APPCRASH
          Application Name: Prepar3D.exe
          Application Version:
          Application Timestamp: 5bfdbb35
          Fault Module Name: StackHash_4faa
          Fault Module Version: 10.0.18362.815
          Fault Module Timestamp: b29ecf52
          Exception Code: c0000374
          Exception Offset: PCH_7D_FROM_ntdll+0x000000000009CBC4
          OS Version: 10.0.18362.
          Locale ID: 1031
          Additional Information 1: 4faa
          Additional Information 2: 4faa67ba6e3b8d0b54d3f6be323338ac
          Additional Information 3: 052e
          Additional Information 4: 052e853156492f7fb04a3b5b2c411735

          Extra information about the problem
          Bucket ID: 98ae099dd0d5118ff94b44d3db35c863 (1822626150908020835)

          Andre(as) Berg --- i7 8700K 12MB 3.7G. MSI Z370 Tomahawk. DDR4 16G. SSD 500G M.2. MSI RTX2080 DUKE 8G