Greetings!

I have had several CDT's in Prepar3d v5.4 after installing the PMDG 737.  2 have been access violations according to AppCrashView and the other was "A heap has been corrupted." error.  Have been flying with Prepar3d since August of last year, never had a CDT until now.  Also, where is a good link to the version 5.0.0 CTD guide?  The link on Jim Young's thread in the CTD forum doesn't work.  Any help anyone can give me would be great.

I am running Prepar3d v5.4, ChasePlane, vPilot, ActiveSky P3D, OBS Studio for streaming and flying the PMDG 737 NGXu

System specs:

Intel Core i7 12th Gen 12700KF 2.7GHz Processor |  Microsoft Windows 11 Pro | NVIDIA GeForce RTX 3070 Ti 8GB GDDR6X | 32GB DDR4-3200 RAM | 

First crash:  terrain.dll

EventType=APPCRASH
EventTime=133560628157104566
ReportType=2
Consent=1
UploadTime=133560628164349782
ReportStatus=268435456
ReportIdentifier=a1c9c6f8-dfae-4fd1-bbc3-aef4630307fa
IntegratorReportIdentifier=f14be54e-7141-481d-b84c-22ecebf473c1
Wow64Host=34404
NsAppName=Prepar3D.exe
OriginalFilename=Prepar3D.exe
AppSessionGuid=00000798-0001-0063-7b45-854ea280da01
TargetAppId=W:0006655d1ff7f92eefd11cf6e4553533bab400000904!0000f988e384c8c0cc0c565368ad44771d3f79cedce0!Prepar3D.exe
TargetAppVer=2023//05//16:14:25:35!5408b!Prepar3D.exe
BootId=4294967295
TargetAsId=474
UserImpactVector=808465200
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=a98ac0f69c1b7812f8e2375d0f0b94de
Response.BucketTable=4
Response.LegacyBucketId=1793056474470782174
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=5.4.9.28482
Sig[2].Name=Application Timestamp
Sig[2].Value=6463925f
Sig[3].Name=Fault Module Name
Sig[3].Value=terrain.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=5.4.9.28482
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=646391de
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000df0bf
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.22631.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=dcb9
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=dcb9c269bd3fca5adf847babfdd86641
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=14ea
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=14ea69158732004e4ab6e611ea2bdc95
UI[2]=C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe

 

Second crash:  PMDG_737NGXu.dll

EventType=BEX64
EventTime=133562328031754843
ReportType=2
Consent=1
UploadTime=133562328039304181
ReportStatus=268435456
ReportIdentifier=d6878fad-5d7a-4051-9b7d-0796c99045ae
IntegratorReportIdentifier=ae7ea89e-e652-49d6-b8fa-024cf43e8c5f
Wow64Host=34404
NsAppName=Prepar3D.exe
OriginalFilename=Prepar3D.exe
AppSessionGuid=00003a44-0001-0067-0b8d-850e3282da01
TargetAppId=W:0006655d1ff7f92eefd11cf6e4553533bab400000904!0000f988e384c8c0cc0c565368ad44771d3f79cedce0!Prepar3D.exe
TargetAppVer=2023//05//16:14:25:35!5408b!Prepar3D.exe
BootId=4294967295
TargetAsId=295
UserImpactVector=808465200
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=6e7431e6bbc681c8ead117fc228a7596
Response.BucketTable=5
Response.LegacyBucketId=1932352086797350294
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=5.4.9.28482
Sig[2].Name=Application Timestamp
Sig[2].Value=6463925f
Sig[3].Name=Fault Module Name
Sig[3].Value=PMDG_737NGXu.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=1.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5fdbddbe
Sig[6].Name=Exception Offset
Sig[6].Value=000000000038faa8
Sig[7].Name=Exception Code
Sig[7].Value=c0000409
Sig[8].Name=Exception Data
Sig[8].Value=0000000000000002
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.22631.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=ee03
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=ee039fd93cbec69bfab36b1041f24bdc
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=9653
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=96530092fcc2fe4cc38607a5ab4207b8
UI[2]=C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe

Third crash:  Unknown

EventType=APPCRASH
EventTime=133562347170722123
ReportType=2
Consent=1
UploadTime=133562347176308314
ReportStatus=268435456
ReportIdentifier=42e60095-9783-43b3-aa8f-bd6434ec7bac
IntegratorReportIdentifier=49d30103-6e6b-4729-87a5-55cdbd5958e8
Wow64Host=34404
NsAppName=Prepar3D.exe
OriginalFilename=Prepar3D.exe
AppSessionGuid=000009c4-0001-0067-0052-a3ec3a82da01
TargetAppId=W:0006655d1ff7f92eefd11cf6e4553533bab400000904!0000f988e384c8c0cc0c565368ad44771d3f79cedce0!Prepar3D.exe
TargetAppVer=2023//05//16:14:25:35!5408b!Prepar3D.exe
BootId=4294967295
TargetAsId=1085
UserImpactVector=269497136
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=1a9d28c70a991a4d6c9cba337f72d8a8
Response.BucketTable=4
Response.LegacyBucketId=2061727459773175976
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=5.4.9.28482
Sig[2].Name=Application Timestamp
Sig[2].Value=6463925f
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_b8b2
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.22621.3374
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=eae8eecc
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=PCH_38_FROM_ntdll+0x000000000009FEB4
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.22631.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=b8b2
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=b8b2a13a4f5d062536816f3908e34f12
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=908a
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=908ac19fd15a2c9a1a379e7e8f6d32b1
UI[2]=C:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe

8 hours ago, AS129 - Michael Johnson said:

  Have been flying with Prepar3d since August of last year, never had a CDT until now

& since you installed PMDG's 737ngux/ng .... 🤔

One typical way to get CTDs with the PMDG is due to the PMDG writing to a user file stored in the C:\Program Files\Lockheed Martin\Prepar3D v5\ folder which is ordinarily read only. We can make it read/write by setting the "Modify" permission on the "C:\Program Files\Lockheed Martin\" folder for the "Users" group which then allows the PMDG to write to its files stored in that folder tree with authenticated permission. To set that up; right click on the C:\Program Files\Lockheed Martin\ folder, choose "Properties" from the popup menu, choose the "Security" tab, press "Edit", in the top window select the "Users" group, and in the window below check the "Modify" box in the "Allow" column, then OK, OK. From here any version of P3D installed will acquire Modify access for the Users group which contains "You" the Authenticated user. That's the proper way to administer Windows folders.

Another way is to start the simulator with "Run As Admin" but then other add-ons will have to be set to Run As Admin as well.

Another way is to install P3D into a user created folder such as "C:\FS\" and so by doing this you the user will automatically get write access to anything installed into that folder. However, you would also need to add the Modify permission for the Users group on that folder if you need to add a new Windows user to that PC to get permission to the simulator.

On 4/4/2024 at 7:52 AM, SteveW said:

One typical way to get CTDs with the PMDG is due to the PMDG writing to a user file stored in the C:\Program Files\Lockheed Martin\Prepar3D v5\ folder which is ordinarily read only. We can make it read/write by setting the "Modify" permission on the "C:\Program Files\Lockheed Martin\" folder for the "Users" group which then allows the PMDG to write to its files stored in that folder tree with authenticated permission. To set that up; right click on the C:\Program Files\Lockheed Martin\ folder, choose "Properties" from the popup menu, choose the "Security" tab, press "Edit", in the top window select the "Users" group, and in the window below check the "Modify" box in the "Allow" column, then OK, OK. From here any version of P3D installed will acquire Modify access for the Users group which contains "You" the Authenticated user. That's the proper way to administer Windows folders.

Another way is to start the simulator with "Run As Admin" but then other add-ons will have to be set to Run As Admin as well.

Another way is to install P3D into a user created folder such as "C:\FS\" and so by doing this you the user will automatically get write access to anything installed into that folder. However, you would also need to add the Modify permission for the Users group on that folder if you need to add a new Windows user to that PC to get permission to the simulator.

I changed the permissions for the folder and that seemed to do the trick.  I have done 2 livestreams and a couple of test flights offline and no more incidents of CTD!  Thanks!

Good work! I'm glad that helped.

I am going to piggy back on this, instead of starting a new topic.

I have had a very stable set up for many, many months, until about 2 or 3 months ago. Then I started to get the odd CTD. I didn't worry too much as I could just re boot and all would go well until the next time.

There seemed to be no pattern, as I was flying a different route each time.

However, this last week (and there has been a W10 update Tuesday last week) I have had two  CTDs while flying the same route . Both over North Africa en route to EGLL.

They were both the dreaded x.........05 Terrain.dll.

The only thing that has changed on my PC is the Windows update and a driver update to 552.22

My settings are very low for EGLL and have worked fine previously.

Could a Windows update affect P3D? I really don't know ?

All the usual SFC checks show nothing missing.

Any suggestions?

I am having the same issues since updating my NVDIA driver in March 2024.

I have even gone so far to re-reinstall P3d5.4, kept my scenery to a minimum and I still experience CTD after about 30 minutes of flight.

Most errors are DLL related such as terrain etc. I have deleted the P3D shader cache  and scenery index  files but still no resolution.

Done the SFC /SCANNOW, no issues.

I have also lowered all word and terrain settings.

Is this a Windows or NVDIA driver issue with p3D ?

I have no issues running MSFS or X plane 12.

Any guidance would be appreciated

 

My pc specs are RTX4090, 64GB RAM, Intel i9 14900ks.

I cannot answer for others but for me, I used to "surf" while flying and would read newspapers and watch associated YouTube videos.

It dawned on me that when I did this (on a long flight) the CTDs happened more often.

I have now flown 4 long (8 hour) flights with no or very minimal "faffing around" and the result has been, no CTDs, flights all successfully completed.

So, my theory is that on a not so modern system, perhaps also on some modern systems, P3D does not like you taking over some PC resources that it likes to use and has a tantrum.

Ian

I was getting a terrain.dll CTD over Lincolnshire, England. If anyone knows that area it's as flat as a pancake so terrain issues seemed odd.

I'm going to come to this from a completely different direction. I had to revert to 5.3HF2 because of issues with AIG Ai and some BGL plans causing freezes in 5.4. reverting to 5.3HF2 solved them.

I believe Ai have an effect in P3D and might be responsible for some issues. I used Ai Companion to clean my AIG BGL files and since doing that I've had zero CTDs including a flight this morning from EGCC to EHAM over Lincolnshire.

Use BGL Report in AIC to resolve all errors. You'll need AIFP3 to edit them to replace any NO PAINTS with an alternative aircraft.

I might be barking up the wrong tree but it might be worth trying. I haven't updated my drivers since getting this PC last October.

 

20 hours ago, Ray Proudfoot said:

I was getting a terrain.dll CTD over Lincolnshire, England. If anyone knows that area it's as flat as a pancake so terrain issues seemed odd.

I'm going to come to this from a completely different direction. I had to revert to 5.3HF2 because of issues with AIG Ai and some BGL plans causing freezes in 5.4. reverting to 5.3HF2 solved them.

I believe Ai have an effect in P3D and might be responsible for some issues. I used Ai Companion to clean my AIG BGL files and since doing that I've had zero CTDs including a flight this morning from EGCC to EHAM over Lincolnshire.

Use BGL Report in AIC to resolve all errors. You'll need AIFP3 to edit them to replace any NO PAINTS with an alternative aircraft.

I might be barking up the wrong tree but it might be worth trying. I haven't updated my drivers since getting this PC last October.

 

I don't seem to have any .bgl files in AIG at all.

52 minutes ago, IanHarrison said:

I don't seem to have any .bgl files in AIG at all.

That suggests you opted for AIGFP alternatives. Keep away from t'internet on your flights.

16 hours ago, Ray Proudfoot said:

That suggests you opted for AIGFP alternatives. Keep away from t'internet on your flights.

That's exactly what I am trying to do. On the way from KMIA to your home airport this morning.

1 hour ago, IanHarrison said:

That's exactly what I am trying to do. On the way from KMIA to your home airport this morning.

Nice weather here. Check my weather station for latest info. I’m 3 miles from EGCC.

4 hours ago, Ray Proudfoot said:

Nice weather here. Check my weather station for latest info. I’m 3 miles from EGCC.

Tried to install and run LNMap  while flying. Of course, it caused a CTD. Just confirms my theory.

I look at your weather site quite regularly. Since my machine was blown down by the gale last year, it has subsequently ceased to work.

I will try the flight again tomorrow, with no "outside" activities.

Last note on this topic, after another CTD, I found in the Windows error report an odd reference, which I traced back to a fan control module.

I removed this and yesterday did the 9 hour from Miami to Manchester with not a single problem.

So now no "surfing" is the answer to the CTD problem. Confirmed.