FSDreamTeam forum
Products Support => Charlotte KCLT Support FSX/P3D => Topic started by: jackieman27 on November 23, 2017, 03:08:45 am
-
Hi all,
Taking advantage of the Black Friday deal, I purchased KCLT. Its a great scenery. I installed the scenery, and then ran the Live Update tool which I believe updated the addon manager and GSX to the latest version, along with a few of my other FSDT airports.
Unfortunately, after about 1 or 2 minutes of flying even in the vicinity of the airport (no matter what aircraft), my sim crashes. This doesn't occur at any other FSDT/Addon Manager airport, let alone any airport in P3D.
Initially, I got this error:
Problem signature:
Problem Event Name: BEX64
Application Name: Prepar3D.exe
Application Version: 4.1.7.22841
Application Timestamp: 59d67e95
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.23807
Fault Module Timestamp: 5915fdce
Exception Offset: 00000000000689f2
Exception Code: c000000d
Exception Data: 0000000000000000
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: cd9f
Additional Information 2: cd9fc598e0f41d686cb569a748a59abb
Additional Information 3: 768f
Additional Information 4: 768f87cd22438cd35a29de9570821b9d
But after digging in the forums, I found the solution: to edit the registry and delete a certain entry; which I did. When I next started P3D, an FsLabs popup informed me that this entry was missing, so it automatically added it back. So, I uninstalled the FsLabs A320 and delete the registry entry again.
Should be all good right? I thought so! Well I ran the sim again and taxied around the airport for a while (this is when the crash seems to initiate the fastest) but then I get another CTD. But this time, there was no error message regarding P3D crash. Just went right to my desktop.
But, I did get this Couatl crash error:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Couatl.exe
Application Version: 3.2.0.3876
Application Timestamp: 5a12d4f3
Fault Module Name: ucrtbase.DLL
Fault Module Version: 10.0.10586.788
Fault Module Timestamp: 5879aa7b
Exception Code: 40000015
Exception Offset: 0008469a
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 73a1
Additional Information 2: 73a130e3d872c93e57e6ea24d1f17e0d
Additional Information 3: 5fb1
Additional Information 4: 5fb17ef4b2eabfc4d17517a232abb641
Now, my best guess is that the Live Update I ran screwed something up with either GSX or the airport itself which is causing something in my system (Win7 64bit) to not be happy with something recently installed. I have the latest NVidia drivers & C++ Redistributables.
Thanks for your time!
Jack D
-
But after digging in the forums, I found the solution: to edit the registry and delete a certain entry; which I did. When I next started P3D, an FsLabs popup informed me that this entry was missing, so it automatically added it back. So, I uninstalled the FsLabs A320 and delete the registry entry again.
Which registry key, exactly ?
-
But after digging in the forums, I found the solution: to edit the registry and delete a certain entry; which I did. When I next started P3D, an FsLabs popup informed me that this entry was missing, so it automatically added it back. So, I uninstalled the FsLabs A320 and delete the registry entry again.
Which registry key, exactly ?
"Remove the key related to Prepar3D.EXE or FSX.EXE in the HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers key location of REGEDIT."
-
Just crashed again, but his time I got this message. The frame rate was very bad at some points in this scenario, especially during approach. Then the sim froze for 2 seconds and gave me this
Problem signature:
Problem Event Name: APPCRASH
Application Name: Prepar3D.exe
Application Version: 4.1.7.22841
Application Timestamp: 59d67e95
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.23807
Fault Module Timestamp: 5915fdce
Exception Code: c0000005
Exception Offset: 000000000004f23c
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 4cf1
Additional Information 2: 4cf129fc8ee9a03d66b0566e5371b6b0
Additional Information 3: d6bf
Additional Information 4: d6bfae44021a599194dd1ef6ffc4206f
-
Nothing in your log indicates the problem is the scenery. Have you tried the same approach with a default airplane ?
-
Yes, i just did. This time the sim crashed when I was in the default Lear in front of a hangar..
Problem Event Name: APPCRASH
Application Name: Prepar3D.exe
Application Version: 4.1.7.22841
Application Timestamp: 59d67e95
Fault Module Name: StackHash_9d06
Fault Module Version: 6.1.7601.23807
Fault Module Timestamp: 5915fdce
Exception Code: c0000374
Exception Offset: 00000000000bf3e2
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 9d06
Additional Information 2: 9d0607b77848de9bc341b7164a9c807b
Additional Information 3: af30
Additional Information 4: af30f84df9f64fb195bc9d0a029600e5
-
Yes, i just did. This time the sim crashed when I was in the default Lear in front of a hangar
I'm sorry, but I cannot reproduce this, and nobody ever reported such instant crash so, it can only be caused by something else you have installed.
If you want, we can arrange a Teamviewer session, so I can check your system directly. PM me to arrange it.
-
Just got a SODE crash at another airport.. Might be the culprit, investigating now
-
Just got a SODE crash at another airport.. Might be the culprit, investigating now
Fairly sure it couldn't be specific to KCLT. Let me know how it goes.
-
Hello Umberto -
Just to let you know, I am experiencing the same CTD near KCLT as mentioned above. It happens when using a default aircraft and also the PMDG 737. It also happens with default scenery as well as when using Megascenery North Carolina.
Thank you,
Kevin
-
It also happens with default scenery as well as when using Megascenery North Carolina.
This further confirm it's not a problem of the airport, like the previous user that had it in another non-FSDT airport too.
-
Yes I agree with you Umberto. It is not attributed to an FSDT airport from my experience. I had another CTD over central PA last night while flying from KIAD to KBUF. I think LM has to look into this as it just started happening after installation of the latest version, 4.1. Very frustrating.
Thanks!
Kevin
-
Yes, i just did. This time the sim crashed when I was in the default Lear in front of a hangar..
Problem Event Name: APPCRASH
Application Name: Prepar3D.exe
Application Version: 4.1.7.22841
Application Timestamp: 59d67e95
Fault Module Name: StackHash_9d06
Fault Module Version: 6.1.7601.23807
Fault Module Timestamp: 5915fdce
Exception Code: c0000374
Exception Offset: 00000000000bf3e2
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 9d06
Additional Information 2: 9d0607b77848de9bc341b7164a9c807b
Additional Information 3: af30
Additional Information 4: af30f84df9f64fb195bc9d0a029600e5
Hi. I recently purchased KCLT and I get a CTD either on approach or departure from the airport. I've used different aircraft (including FSLabs A320 and Leonardo Maddog X) and approached / departed in different directions, but the same error happens. I don't get crashes at any other airports or in P3D generally, so hoping someone can shed some light. Thank you.
EventType=APPCRASH
EventTime=131706069234925947
ReportType=2
Consent=1
UploadTime=131706069235545982
ReportIdentifier=1cda35e6-55ec-11e8-8df8-1234567890ab
IntegratorReportIdentifier=1cda35e5-55ec-11e8-8df8-1234567890ab
Response.BucketId=1232259922
Response.BucketTable=349533006
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=PREPAR3D.EXE
Sig[1].Name=Application Version
Sig[1].Value=4.2.21.24048
Sig[2].Name=Application Timestamp
Sig[2].Value=5a7c832c
Sig[3].Name=Fault Module Name
Sig[3].Value=ntdll.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7601.23915
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=59b94ee4
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000000000004f2a2
-
Hi. I recently purchased KCLT and I get a CTD either on approach or departure from the airport. I've used different aircraft (including FSLabs A320 and Leonardo Maddog X) and approached / departed in different directions, but the same error happens.
Nothing in your log indicates the error is caused by the scenery. Please try with a default aircraft.
-
Hi. I recently purchased KCLT and I get a CTD either on approach or departure from the airport. I've used different aircraft (including FSLabs A320 and Leonardo Maddog X) and approached / departed in different directions, but the same error happens.
Nothing in your log indicates the error is caused by the scenery. Please try with a default aircraft.
Hi Umberto. Tried with the default F-35A and got the exact same problem. CTD about 5 nautical miles away from KCLT. See below. The only other thing I can thing of is that it's related to FTX Global openLC North America, as that's the only other thing installed in the area (though I haven't had any problems with it elsewhere). Let me know if you have any other suggestions. Thank you.
EventType=APPCRASH
EventTime=131706598923068227
ReportType=2
Consent=1
UploadTime=131706598923498251
ReportIdentifier=71003085-5667-11e8-bb98-1234567890ab
IntegratorReportIdentifier=71003084-5667-11e8-bb98-1234567890ab
Response.BucketId=1232259922
Response.BucketTable=349533006
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=PREPAR3D.EXE
Sig[1].Name=Application Version
Sig[1].Value=4.2.21.24048
Sig[2].Name=Application Timestamp
Sig[2].Value=5a7c832c
Sig[3].Name=Fault Module Name
Sig[3].Value=ntdll.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7601.23915
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=59b94ee4
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000000000004f2a2
-
CTD about 5 nautical miles away from KCLT.
Can you provide with a bit more accurate location ? The loading range for KCLT is 10 NM so, if the problem was the airport, the should have happened at 10 NM out but, if you can provide with coordinates, I can test it here.
-
CTD about 5 nautical miles away from KCLT.
Can you provide with a bit more accurate location ? The loading range for KCLT is 10 NM so, if the problem was the airport, the should have happened at 10 NM out but, if you can provide with coordinates, I can test it here.
Hi Umberto. I tried to get coordinates by doing another flight into KCLT but I disabled FTX Vector and Orbx North America LC to make sure they weren't the cause, and this time I got the CTD a lot closer to the airport ... on final approach just a couple of nautical miles away from landing. So the CTD doesn't happen at a fixed distance. But one thing I noticed is that I get a lot of microstutters the closer I get to the airport, so I'm thinking it has something to do with that? Almost like an OOM - but of course that shouldn't happen in P3Dv4. Any ideas?
I should also say that I'm able to start a flight from KCLT but in that case the CTD happens during the climb away from the airport. This is proving really hard to pinpoint. Thanks for your help.
-
But one thing I noticed is that I get a lot of microstutters the closer I get to the airport, so I'm thinking it has something to do with that? Almost like an OOM - but of course that shouldn't happen in P3Dv4. Any ideas?
There shouldn't be any microstutters and surely not an OOM with KCLT, surely not under P3D4, because we basically load the whole airport at 10NM so, your are supposed to see only a somewhat large pause at 10 NM, then nothing.
Of course, I'm assuming you haven't touched the anti pop-up slider in the Addon Manager, which by default is set at its maximum under P3D4. If it's not, the program will start to create/destroy objects more often (depending how low it is), which could introduce some stuttering, even if the fps might be a bit better, depending on the system.
this time I got the CTD a lot closer to the airport ... on final approach just a couple of nautical miles away from landing. So the CTD doesn't happen at a fixed distance.
This seems to further confirm the airport is not the problem. If it was, it should happen always at the same spot, since the airport is static. If the crash appears in different places, it might possibly related to an AI, especially one which was originally made for FS9, which are known to cause CTDs in P3D4.
Testing with 0% Traffic might be useful to verify this.
-
There shouldn't be any microstutters and surely not an OOM with KCLT, surely not under P3D4, because we basically load the whole airport at 10NM so, your are supposed to see only a somewhat large pause at 10 NM, then nothing.
Of course, I'm assuming you haven't touched the anti pop-up slider in the Addon Manager, which by default is set at its maximum under P3D4. If it's not, the program will start to create/destroy objects more often (depending how low it is), which could introduce some stuttering, even if the fps might be a bit better, depending on the system.
Yes, the anti pop-up slider is set to default / maximum.
This seems to further confirm the airport is not the problem. If it was, it should happen always at the same spot, since the airport is static. If the crash appears in different places, it might possibly related to an AI, especially one which was originally made for FS9, which are known to cause CTDs in P3D4.
Testing with 0% Traffic might be useful to verify this.
I think you have hit the nail on the head. I managed to complete a flight, landing at KCLT, with traffic set to 0. I then did a bit more research in forums and found that my AI (MyTraffic 6) does have some AI aircraft from FS9 that can cause CTDs. Given that I don't normally get CTDs, they must be aircraft that are common around KCLT. So I deleted those aircraft and was able to complete a second flight with my AI at 10 per cent. Hooray!
Thank you for all your help in getting to the bottom of this problem Umberto. It's much appreciated! And now I can appreciate your wonderful KCLT scenery properly. :)