Hello, I've recently been getting random CTDs in Prepar3Dv5. In other forum posts I have seen people that say the "0xc0000005" error has something to do with an addon or prepar3d not having permission to access ram or something like that? Now I thought if it had something to do with permission, couldn't I just give Prepar3D somehow full permission to access anything on my computer if that makes sense?

Is there anything else I could do about fixing this CTD issue? It says terrain.dll here, but I also had a ntdll.dll and an api.dll crash.

And also, does it make a difference if the code is "0xc0000005" or "c0000005" ?

 

In the event viewer it usually looks like this:

Protokollname: Application
Quelle:        Application Error
Datum:         09.01.2024 16:51:06
Ereignis-ID:   1000
Aufgabenkategorie:Anwendungsabsturzereignisse
Ebene:         Fehler
Schlüsselwörter:
Benutzer:      DESKTOP-64IGT48\xxblu
Computer:      DESKTOP-64IGT48
Beschreibung:
Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 5.4.9.28482, Zeitstempel: 0x6463925f
Name des fehlerhaften Moduls: terrain.dll, Version: 5.4.9.28482, Zeitstempel: 0x646391de
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000df0bf
ID des fehlerhaften Prozesses: 0x0x4888
Startzeit der fehlerhaften Anwendung: 0x0x1DA42F6F6237EDC
Pfad der fehlerhaften Anwendung: C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Pfad des fehlerhaften Moduls: C:\Program Files\Lockheed Martin\Prepar3D v5\terrain.dll
Berichtskennung: b5463b6b-1c25-474c-8d0b-a78d9d02f607
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
    <EventID>1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2024-01-09T15:51:06.2853643Z" />
    <EventRecordID>8185</EventRecordID>
    <Correlation />
    <Execution ProcessID="26836" ThreadID="27276" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-64IGT48</Computer>
    <Security UserID="S-1-5-21-1408503863-458983153-3776648161-1001" />
  </System>
  <EventData>
    <Data Name="AppName">Prepar3D.exe</Data>
    <Data Name="AppVersion">5.4.9.28482</Data>
    <Data Name="AppTimeStamp">6463925f</Data>
    <Data Name="ModuleName">terrain.dll</Data>
    <Data Name="ModuleVersion">5.4.9.28482</Data>
    <Data Name="ModuleTimeStamp">646391de</Data>
    <Data Name="ExceptionCode">c0000005</Data>
    <Data Name="FaultingOffset">00000000000df0bf</Data>
    <Data Name="ProcessId">0x4888</Data>
    <Data Name="ProcessCreationTime">0x1da42f6f6237edc</Data>
    <Data Name="AppPath">C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe</Data>
    <Data Name="ModulePath">C:\Program Files\Lockheed Martin\Prepar3D v5\terrain.dll</Data>
    <Data Name="IntegratorReportId">b5463b6b-1c25-474c-8d0b-a78d9d02f607</Data>
    <Data Name="PackageFullName">
    </Data>
    <Data Name="PackageRelativeAppId">
    </Data>
  </EventData>
</Event>

Have you configured P3Dv5.4 to Run as Administrator?  If so, then I'd next test the memory.  MemTest86 is the preferred choice.  Use the free version, and if you've never used the app before take some time to familiarize yourself.  Also, since you note various Faulting modules you should be prepared to reinstall Windows apps like .Net Framework and Visual C++ Runtimes.  0xc0000005 errors can be... challenging.

Good luck!👍

I have exact the same problem (more than 80% of the time is ntdll.dll, I do see terrain.dll or atc.dll) and it almost always crashes at 30~60min in the first flight that day (even if the PC have been running for days without restart), and succeeding flight reloading autosave (or just start fresh) didn't have any problem 2~3 hours to land. It happens to me almost every time back in somewhere like August, but somehow now without any setting change (and I even disabled all windows update), it now didn't happen that frequent, but still creepy enough to keep me have autosave running in the background....

What now I deal with it is...keep autosave on, and.... fly x-plane most of the time...

Edited January 10, 20242 yr by C2615

I would try deleting the P3D.cfg and allowing the sim to rebuild it. The file is in this folder:
C:\Users\YourUserName\AppData\Roaming\LockheedMartin\Prepar3D
Before you do that you can export your keyboard settings and graphics settings, so that after the restart you can quickly load them back in. You will have to note down some of the other general settings (I take screenshots of the options screens) as these will get reset to default if you delete the .cfg.

You can also try clearing the P3D shader cache (ChasePlane has a handy button for this) and the Microsoft DX shader cache (you can do this via Disc Cleanup) and also delete all the temporary files in this folder:
C:\Users\YourUserName\AppData\Local\Temp

If none of the above works, there are other things to try but the above is what I would do first.

7 hours ago, VTCH said:

Pfad der fehlerhaften Anwendung: C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Pfad des fehlerhaften Moduls: C:\Program Files\Lockheed Martin\Prepar3D v5\terrain.dll
Berichtskennung: b5463b6b-1c25-474c-8d0b-a78d9d02f607
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />

Prepar3D 5.4 just needs to be started as admin. That's all. I think the error is not a matter of rights, it is a try to write to memory, where it shouldn't. That leads to a ctd. If it was just rights, probably only a popup would come up with the message, you don't have sufficient rights. 

All this indicates to me it is a corrupt scenery or AI object. There is even a GUID in the error message. I wonder if it relates to an object, scenery or dynamic scenery.

Now only you know, where you fly when this happens. Ask yourself, what scenery is there which you have installed? When flying over Frankfurt you may try to fix City and/or airport scenery there. Just a reinstall of the package. But if it happens everywhere, it's more probable AI objects flying around or boats.

Try flying without AI traffic, planes and boats and see if you can avoid CTD. If it's good without traffic, then comes the search for the bad file. There are several methods already discussed here often.

 

@blaunarwal's advice is good.

Also the first thing I always do when attempting to troubleshoot such types of issue is to delete the shader cache files and scenery index files.

This is a non-destructive method, as both will auto regenerate with new and fresh data when P3D is restarted.

Allowing those files to rebuild will often resolve issues and indeed many thousands of complied shader cache files can build up over time.

Shader Cache files are located in the user profile path e.g.

• C:\Users\YOUR-LOGIN-ACCOUNT-NAME\AppData\Local\Lockheed Martin\Prepar3D v5\Shaders\

Scenery Index files are located in the Prorgram Data path e.g.

• C:\ProgramData\Lockheed Martin\Prepar3D v5\SceneryIndexes_x64\

Also I wouldn't delete the prepar3D.cfg

Rename it as a first step, of note I've never needed to delete my prepar3D.cfg although I have renamed on occasion for troublehooting purposes prior to rolling back to my origional Prepar3D.cfg after troubleshooting. I always keep my Prepar3D.cfg as it is heavily customised and tuned to my usage.

Cheers

I've had a terrain.dll CTD on a flight from Manchester to Schiphol over Lincolnshire. Having a moving map on a separate computer allows me to see the precise place it occurred.

Since then I'm flown 8 legs around Europe and all have been clean. The only addon software I have close to the CTD is Pilots FSGlobal mesh. Plus UK2000 Manchester 70 miles behind me and UK2000 Stansted a similar distance to the south. Both unlikely to be the cause.

When I next fly EGCC-EHAM I'll check if a get a CTD in the same area. If I do it's definitely addon related. If I don't then it's a random thing and probably unrelated to any particular package.

And this is with 5.3HF2 so not version related.

On 1/10/2024 at 9:35 AM, blaunarwal said:

Prepar3D 5.4 just needs to be started as admin. That's all. I think the error is not a matter of rights, it is a try to write to memory, where it shouldn't. That leads to a ctd. If it was just rights, probably only a popup would come up with the message, you don't have sufficient rights. 

All this indicates to me it is a corrupt scenery or AI object. There is even a GUID in the error message. I wonder if it relates to an object, scenery or dynamic scenery.

Now only you know, where you fly when this happens. Ask yourself, what scenery is there which you have installed? When flying over Frankfurt you may try to fix City and/or airport scenery there. Just a reinstall of the package. But if it happens everywhere, it's more probable AI objects flying around or boats.

Try flying without AI traffic, planes and boats and see if you can avoid CTD. If it's good without traffic, then comes the search for the bad file. There are several methods already discussed here often.

 

Thanks, I reinstalled my Ai traffic and verified some ORBX regions, hadn't had a CTD yet. It always seemed to happen over England. For now my sim is running!

Thanks everyone for the replies. Right now I don't have the CTDs. I verified some ORBX regions and reinstalled my Ai traffic. Hopefully it stays that way. 

Meanwhile I'm catching up with the sun on the way to Toronto Pearson https://imgur.com/a/TdmMyJt

Edited January 11, 20242 yr by VTCH

Got it again *sigh*

 

Protokollname: Application
Quelle:        Application Error
Datum:         13.01.2024 21:18:19
Ereignis-ID:   1000
Aufgabenkategorie:Anwendungsabsturzereignisse
Ebene:         Fehler
Schlüsselwörter:
Benutzer:      DESKTOP-64IGT48\xxblu
Computer:      DESKTOP-64IGT48
Beschreibung:
Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 5.4.9.28482, Zeitstempel: 0x6463925f
Name des fehlerhaften Moduls: terrain.dll, Version: 5.4.9.28482, Zeitstempel: 0x646391de
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000df0bf
ID des fehlerhaften Prozesses: 0x0x14E8
Startzeit der fehlerhaften Anwendung: 0x0x1DA46421ECFDF22
Pfad der fehlerhaften Anwendung: C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Pfad des fehlerhaften Moduls: C:\Program Files\Lockheed Martin\Prepar3D v5\terrain.dll
Berichtskennung: fbb7e36b-e15b-4d68-9012-da1e12702a7d
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
    <EventID>1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2024-01-13T20:18:19.5404727Z" />
    <EventRecordID>10155</EventRecordID>
    <Correlation />
    <Execution ProcessID="38032" ThreadID="31268" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-64IGT48</Computer>
    <Security UserID="S-1-5-21-1408503863-458983153-3776648161-1001" />
  </System>
  <EventData>
    <Data Name="AppName">Prepar3D.exe</Data>
    <Data Name="AppVersion">5.4.9.28482</Data>
    <Data Name="AppTimeStamp">6463925f</Data>
    <Data Name="ModuleName">terrain.dll</Data>
    <Data Name="ModuleVersion">5.4.9.28482</Data>
    <Data Name="ModuleTimeStamp">646391de</Data>
    <Data Name="ExceptionCode">c0000005</Data>
    <Data Name="FaultingOffset">00000000000df0bf</Data>
    <Data Name="ProcessId">0x14e8</Data>
    <Data Name="ProcessCreationTime">0x1da46421ecfdf22</Data>
    <Data Name="AppPath">C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe</Data>
    <Data Name="ModulePath">C:\Program Files\Lockheed Martin\Prepar3D v5\terrain.dll</Data>
    <Data Name="IntegratorReportId">fbb7e36b-e15b-4d68-9012-da1e12702a7d</Data>
    <Data Name="PackageFullName">
    </Data>
    <Data Name="PackageRelativeAppId">
    </Data>
  </EventData>
</Event>

The C0000005 error code just means the program tried to access memory outside its allocated address space, and that can be caused by many different kinds of problems, both software and hardware.  It's the computer analog to running a fever--lots of unrelated problems can cause it, so it's not going to offer up much of a clue as to its origin on its own.

The fact that the offset (DF0BF) is the same in terrain.dll on both of these failures suggests to me that you probably do have something unhappy going on in your scenery config--a bad scenery texture or BGL, or perhaps a boogered-up terrain.cfg file.  Something like an unstable overclock wouldn't likely throw the same error at the same place.

 

2 minutes ago, Bob Scott said:

The C0000005 error code just means the program tried to access memory outside its allocated address space, and that can be caused by many different kinds of problems, both software and hardware.  It's the computer analog to running a fever--lots of unrelated problems can cause it, so it's not going to offer up much of a clue as to its origin on its own.

The fact that the offset (DF0BF) is the same in terrain.dll on both of these failures suggests to me that you probably do have something unhappy going on in your scenery config--a bad scenery texture or BGL, or perhaps a boogered-up terrain.cfg file. 

 

I'll try to find out what is happening, thanks for the hint

Hello, have you found a solution? I have the exact same error. Occurs completely randomly. Sometimes after an hour, sometimes after 6 hours, sometimes directly after the loading screen, but sometimes not at all. I have already tried several possible solutions and checked the compatibility of all add-ons. The error is completely independent of the weather or the location. Here is also the extract from the Windows event log: 

Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 5.4.9.28482, Zeitstempel: 0x6463925f
Name des fehlerhaften Moduls: terrain.dll, Version: 5.4.9.28482, Zeitstempel: 0x646391de
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000df0bf
ID des fehlerhaften Prozesses: 0xab8
Startzeit der fehlerhaften Anwendung: 0x01da5476073da713
Pfad der fehlerhaften Anwendung: L:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Pfad des fehlerhaften Moduls: L:\Program Files\Lockheed Martin\Prepar3D v5\terrain.dll
Berichtskennung: d72994fb-4396-4779-a08b-59f00a5f87ff
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

Edited February 1, 20242 yr by AirWolf21294

9 hours ago, gd212erb said:

Hello, have you found a solution? I have the exact same error. Occurs completely randomly. Sometimes after an hour, sometimes after 6 hours, sometimes directly after the loading screen, but sometimes not at all. I have already tried several possible solutions and checked the compatibility of all add-ons. The error is completely independent of the weather or the location. Here is also the extract from the Windows event log: 

Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 5.4.9.28482, Zeitstempel: 0x6463925f
Name des fehlerhaften Moduls: terrain.dll, Version: 5.4.9.28482, Zeitstempel: 0x646391de
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000df0bf
ID des fehlerhaften Prozesses: 0xab8
Startzeit der fehlerhaften Anwendung: 0x01da5476073da713
Pfad der fehlerhaften Anwendung: L:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Pfad des fehlerhaften Moduls: L:\Program Files\Lockheed Martin\Prepar3D v5\terrain.dll
Berichtskennung: d72994fb-4396-4779-a08b-59f00a5f87ff
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

Daniel,

Did you already try the advice listed above regarding deleting Shaders and Scenery Indexes??

10 hours ago, 787flyer said:

Daniel,

Did you already try the advice listed above regarding deleting Shaders and Scenery Indexes??

Yes, I've already tried that. I've even reinstalled P3D. 

After the two latest CTD events last night, I might suspect the AI traffic injected by vPilot as the culprit. 

I was flying from LPFR to EDFH with a Boeing 737 (NGXu) yesterday. The first CTD occurred at 20:59z over Nantes at waypoint BAKUL. I reinstalled the NVIDIA driver and tried the exactly same flight again. This time I made it just over Spain. Same error, but at waypoint BARDI at 22:34z. I created a map with the help of Simbrief. There are no addons installed in this entire area between LPFR and ELLX, except ORBX Global and ORBX Freeware Airports. So my troubleshooting continues. There are 453NM between BARDI and BAKUL. The time between the CTD's is 1:35h. So I assume that some AI Traffic with a groundspeed of ~287 kts came towards to me, which is not compatible with P3D v5. 

https://imgur.com/a/6YDxKrw

The flight from LPFR to EDFH completed offline without any problems. Unfortunately, I have no idea how to verify this assumption. How can I find out if a certain AI aircraft is not compatible?