I'm running P3Dv2 2.5.12945 (one update version back) with KFLL v1.5.4 (d/l on 29 Jun 15) and addon manager v3.0.0.5 (d/l/ 7 Jul 15) without issue so far here.  Using a single 980 with 353.30 driver.

 

Just a thought...don't NVidia drivers use .net?

 

Regards

Quick update.

 

Hasn't done nothing since last night.

 

1. Started P3D at 09:58am ET with default (!!!) KTPA airport and got the same error message around 10:03 am. At least I was totally satisfied with consistency of the error :-)

2. Uninstalled GSX with and also approved full uninstall of both bglman and coatl.exe. Neither FSDT nor FB sceneries were uninstalled with a purpose to test my theory regarding corrupted modules.

3. With the above-mentioned software uninstalled, ran P3D at 10;33am. loaded F22 at T2G KMCO and did a couple of crazy flying in this area through 10:42AM, then without exiting the sim, loaded F22 at T2G KSEA and flew the same crazy patterns through 10:51AM. No errors or whatsover for almost 19 minutes!!!

 

Going to install GSX again in about an hour and repeat the same approach. Stay tuned

Bob,

 

I have P3D XXX46 hotfix. You still run XXX45.

 

 

I'm running P3Dv2 2.5.12945 (one update version back) with KFLL v1.5.4 (d/l on 29 Jun 15) and addon manager v3.0.0.5 (d/l/ 7 Jul 15) without issue so far here.  Using a single 980 with 353.30 driver.

 

Bob,

 

I have P3D XXX46 hotfix. You still run XXX45.

 

 

Just a thought...don't NVidia drivers use .net?

 

Yes it does, but normally all the CTD related to video are marked as ntdll, g3d.dll or g2d.dll. In our case with Rob, the module to blame is marked as "unknown"

I purchased KFLL myself and have zero problems running it.   Flew into the other night and she looked beautiful.   A strange error you are getting no doubt but I don't think it has anything to do the airport itself.   I can't think of what it might be.

...2nd update.

 

1. Installed GSX with NAV off

 

2. Executed exactly the same test for 20 minutes as described above. No errors, no crashes.

 

At this point I'm 75% convinced that it's KFLL installer that caused the problem and perhaps this individual installer's modules were not correctly updated for recent hotfixes from P3D. That's why some people have no problems running FLL in their sims as they installed it a while ago and others, especially those who downloaded the installer in recent week like myself and Rob, do.

 

Im' not going to try and install FLL again (especially taking into consideration the fact that the scenery is heavily outdated in terms of runways configuration) until I receive 100% green light from FSDT and others. What really worries me is that I'm planning to add JFKv2, CYVR and KIAH to my collection in a next month and honestly speaking I don't want to run into the same issues again as efforts for resolving issues like these are pretty much time consuming.

 

Thanks to all who helped and participate.

 

Rob - you input would be much appreciated as well. 

I don't get the error if I disable MT6 (set GA and Commerical traffic = 0).  

 

I also don't get the error at every parking spot even with AI traffic enabled.  

 

I consistently get the error at Parking 102 RAMP GA SMALL when I have AI traffic enabled but not when disabled.

 

I'll keep digging but super busy so probably will not be able to look more into this until weekend.

 

Cheers, Rob.

At this point I'm 75% convinced that it's KFLL installer that caused the problem

Rob's last message about disabling AI, instead, finally confirmed the problem is NOT the scenery.

 

perhaps this individual installer's modules were not correctly updated for recent hotfixes from P3D.

All FSDT installers *DOWNLOAD* the very latest version of the modules, from the same place so, unless your antivirus is blocking the download, it's not possible you would get a outdated version by mistake.

 

And, if you HAD an outdated version by mistake, one that doesn't support the latest Hotfix, the Addon Manager WILL give you a clear message about the simulator version not supported.

 

And if the problem were the modules, you would should have crashes everywhere NOT just at KFLL.

 

That's why some people have no problems running FLL in their sims as they installed it a while ago and others, especially those who downloaded the installer in recent week like myself and Rob, do.

Again, Rob latest test finally confirmed KFLL doesn't have anything to do with this.

 

It's either some kind of AI traffic tool that runs with .NET, or it's a missing/corrupted AI texture, for an AI that only appears if FSDT KFLL is installed, because due to the different AFCAD assignments, the one with the problem doesn't appear on the default scenery.

 

A crash after some minutes, is perfectly compatible with a problem with an AI, because it takes some time for FSX to generate all the traffic in the "reality bubble" around (about 100 NM) an airport.

I tend agree with Umberto's initial premise ... my hunch is on FSDT AFD interaction with MT6.  I've heard conflicting information that AFD can't conflict because it's priority based but in the same token I've heard AFD can conflict regardless of priority.

 

I've been using this tool: http://www.scruffyduck.org/simple-airport-scanner/4584282795 to help identify conflicts (supports P3D also).

 

I install FSDT KFLL, when prompted to download the AFCAD, I hit "Yes".  My expectation was to see a conflict and sure enough the "Airport Scanner Tool" did indeed report a conflict, so I disabled the MT6 BR2_KFLL.BGL (set to .OFF or move to another disable folder) leaving the FSDT AFD intact (note: that's the ONLY *KFLL*.* file MT6 has).

 

My hunch, and that's all it is at this point is that MT6 does NOT like FSDT KFLL AFD.

 

I'll dig more into this tonight if I get time.

 

Cheers, Rob.

 

EDIT: And/Or an MT6 AI model that happens to come to life with the FSDT AFD ... of course, how the heck can we know which AI model is the source of the problem if that is indeed the case?

Just ran a couple test flights with the configuration I specified above.  Started with the RealAir Duke at KFLL Parking 102 as Rob mentioned, with stock MT6 aircraft and traffic schedule and traffic levels set at 30% commercial and 40% GA.  Let it sit for 10 minutes, started, and flew around the pattern.  I did this profile several times.  No problems.  Date and time were 6/24/15 at 12:00 local at KFLL.

 

The BR2_KFLL.bgl AFCAD in the MyTraffic Professional scenery folder is disabled (renamed to BR2_KFLL.xxx)

 

I did experience a CTD while loading P3D one time during this test, before I even got to the scenario setup screen, with couatl.exe identified as the faulting module.  Haven't seen this before or since.

 

couatl.exe
   3.0.0.3088
   55940ba4
   unknown
   0.0.0.0
   00000000
   c0000005
   7ebd0055
   135c
   01d0ba81d842ad26
   X:\P3D\fsdreamteam\couatl\couatl.exe
   unknown
   16f8f363-2675-11e5-8775-10c37b96291d
 

I'm also running FSUIPC 4.939u with WideFS active.  ASN and ATM were not running during the tests.

 

Regards

1. Bad Traffic Textures usually calls for g2d.dll or ntdll (very rare) crashes.

2. Bad AFD itself (even duplicate AFD) is not prerequisite for CTD, especially NET-related. 

Rob's last message about disabling AI, instead, finally confirmed the problem is NOT the scenery.


 

Actually it did't at all as I DO NOT use MT or UT. My AI-traffic is hand-picked and checked with all *dds textures verified on multiple AI validators such as AIFP and ACA2015. Your KLAX worked fine, your KDFW worked fine, your KLAS worked fine....until I installed KFLL.

I remove the EMT.dll from my dll.xml. It isn't compatible with Ezdok. 

My AI-traffic is hand-picked and checked with all *dds textures verified on multiple AI validators such as AIFP and ACA2015.

 

I'd be interested to see what happens in your environment if you disable AI traffic (0% both GA and Commercial) ... do you still get any errors?

 

In summary what has been positively ruled out by fact of not used and/or installed:

 

1. MT6

2. UT2

3. EMT

4. EzDok

5. ASN

 

Cheers, Rob.

Actually it did't at all as I DO NOT use MT or UT. My AI-traffic is hand-picked and checked with all *dds textures verified on multiple AI validators such as AIFP and ACA2015.

Yes, it confirmed it entirely.

 

Also, it's funny that, BEFORE Rob's findings, you took his own experience with the same crash as yours, as being a supporting evidence of the scenery being a problem, but now that he finally found the issue was NOT the scenery, you are not interested anymore in his own opinion ? What's happened to Rob's reliability as P3D tester, etc, etc, etc ?

 

Fact is, now that Rob has clearly proven the problem is NOT the scenery, you are the only one left with it. And if you continue losing your time insisting the scenery must have some problem, you are not going to find the REAL cause.

 

Your KLAX worked fine, your KDFW worked fine, your KLAS worked fine....until I installed KFLL.

Could you please stop repeating this ?

 

It has been already explained, several times, that a problem happening ON an specific airport, doesn't HAVE to be a problem IN that airport, but simply a problem that happens *there*, because of other issues.

 

Case in point (but this is just ONE example), a missing AI texture for an airline that will only be called if the FSDT AFCAD is active (because it's different than default), will manifest exactly this way: everything working fine before installing the scenery, and issue after installing it, so you can be mislead thinking "it's the scenery", when clearly it's not.

 

And no, missing AI textures are not the only possible source of crashes, that was just something to check, but according to Rob's findings, it's surely something AI-related and .NET related. Like a traffic utility, a radar utility, an ATC utility, ANYTHING that, for some reason, needs to read the AI in the area.

 

Of course, after Rob's findings the crash happens only at Parking 102 GA, I immediately tried it, with 100% density (commercial, GA and airport vehicles), and left the airplane sitting at that parking for about 1 hour. And of course, no problems whatsoever.

 

Which further confirm:

 

- The scenery is NOT the problem (this was already obvious from Rob's findings)

 

- The problem doesn't happen with default AI traffic.

UPDATE:

 

I tried doing the AFD shuffle - tried with just MT6 AFCAD (with AI enabled), still CTD.  Tried just FSDT AFCAD, still CTD.   Moved FSDT KFLL up and down in the scenery library to see if that would have any impact, still CTD.

 

Uninstalled FSDT KFLL and NO CTD's (tested for over 1 hour)

 

Solutions for me so far is:

1.  Disable AI Traffic with FSDT KFLL installed

2.  Uninstall FSDT KFLL

 

But just to clarify, the errors - two of them reported at the same time, one is Prepar3d.exe error the other is .NET framework error (most likely one triggered the other).

 

Log Name:      Application

Source:        Application Error

Date:          7/9/2015 11:47:05 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      Rob-5960X-PC

Description:

Faulting application name: Prepar3D.exe, version: 2.5.12946.0, time stamp: 0x555f1dfa

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0xffaf00a7

Faulting process id: 0x10e0

Faulting application start time: 0x01d0badac7c23cd8

Faulting application path: D:\Lockheed Martin\Prepar3D v2\Prepar3D.exe

Faulting module path: unknown

Report Id: 797fdb09-26cf-11e5-ba34-54a050d5785d

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2015-07-10T06:47:05.000000000Z" />

    <EventRecordID>19220</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Rob-5960X-PC</Computer>

    <Security />

  </System>

  <EventData>

    <Data>Prepar3D.exe</Data>

    <Data>2.5.12946.0</Data>

    <Data>555f1dfa</Data>

    <Data>unknown</Data>

    <Data>0.0.0.0</Data>

    <Data>00000000</Data>

    <Data>c0000005</Data>

    <Data>ffaf00a7</Data>

    <Data>10e0</Data>

    <Data>01d0badac7c23cd8</Data>

    <Data>D:\Lockheed Martin\Prepar3D v2\Prepar3D.exe</Data>

    <Data>unknown</Data>

    <Data>797fdb09-26cf-11e5-ba34-54a050d5785d</Data>

  </EventData>

</Event>

 

.NET Framework error:

 

Log Name:      Application

Source:        .NET Runtime

Date:          7/9/2015 11:47:05 PM

Event ID:      1026

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      Rob-5960X-PC

Description:

Application: Prepar3D.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: exception code c0000005, exception address FFAF00A7

 

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name=".NET Runtime" />

    <EventID Qualifiers="0">1026</EventID>

    <Level>2</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2015-07-10T06:47:05.000000000Z" />

    <EventRecordID>19219</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Rob-5960X-PC</Computer>

    <Security />

  </System>

  <EventData>

    <Data>Application: Prepar3D.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: exception code c0000005, exception address FFAF00A7

</Data>

  </EventData>

</Event>

 

As you can see from above, exception code c0000005 is access violation (not necessarily anything to do with security) ... it means an attempt was made to reference memory that is not valid.  Many code issues can cause this error ... from removing pointers in a collection while navigating thru the collection to trying to access elements outside of the allocated size of a collection ... to trying to reference a structure that is either not instantiated or has been removed by the CG ... just some examples.

 

Cheers, Rob.

 

EDIT: I did run a .NET validation tool and all version I have on my system verified correctly. 

I'm not really interested in blame at all ... I'm just trying to find solutions to a problem.  The two solutions I have above are obviously not "optimal" and have NOT positively identified the issue (and we may never identify it).  Others don't seem to have any issues with FSDT KFLL and AI Traffic products, so there is some other environment issue at play that I haven't identified.

 

Although removing FSDT KFLL does make the problem go away, it still doesn't mean I've identified the problem ... it just means FSDT KFLL was a trigger for the problem.  Because other's aren't having a problem, it's most likely some combination of products that is triggering the issue (in my case MT6 and FSDT KFLL) ... what exact combination I don't know ... and may never know.

 

Cheers, Rob.

Rob,

 

Not only you have to uninstalled KFLL, you'd need to remove modules as well (at least uninstall of KFLL alone did not work initially in my case). I did the following.

 

1. Removed KFLL and modules

2. Removed GSX and then re-installed again with all the modules.

 

Made a lovely flight yesterday from FB KIAD to T2G KMCO with NGX, ASN, REX, PRO ATC.  No CTDs, no crashes, no other bad stuff...life is back to normal :-)

Case in point (but this is just ONE example), a missing AI texture for an airline that will only be called if the FSDT AFCAD is active (because it's different than default), will manifest exactly this way: everything working fine before installing the scenery, and issue after installing it, so you can be mislead thinking "it's the scenery", when clearly it's not.

 

 

As I said before - my AI are clean, my AFDs are clean as well as I always use "Fault Finder" with AFD 1.65

Honestly I don't even want to talk further about this because your problem is that you cannot (or you don't want to) read or hear what other people say. Normal response from any commercial developer, regardless whose fault it is (at least here in the US) - 'Yes, we will investigate and let you know". Your typical "defense" - is blaming your paying customers immediately. Personally I find this unethical at least.  In the meantime I have a stable and well-running sim after I got rid of KFLL. Next week I'm planning to purchase FSDT KIAH and KJFKv2 and I have a bad feeling that we would return to this discussion again. So let' s save our emotions for next week :-)

 

Have a nice weekend. 

 

Thanks for the help

 

 

I'd be interested to see what happens in your environment if you disable AI traffic (0% both GA and Commercial) ... do you still get any errors?

 

Not only I disabled AI traffic, I also parked F22 at default KTPA and got the same string of CTDs (P3d unknown "module" + NET violation). In my case, KFLL installer affected not only KFLL area, but the entire sim.  

 

 

Not only I disabled AI traffic, I also parked F22 at default KTPA and got the same string of CTDs (P3d unknown "module" + NET violation). In my case, KFLL installer affected not only KFLL area, but the entire sim.

 

Hmmmm ... did you get the error even with Virtuali entries disabled in DLL.XML and EXE.XML?

 

Cheers, Rob.