okey , I 'll try it, I let you know what the result is

All settings are now at low and still crash

Try making a flight in Africa to be away from any 3rd party scenery, AI, etc.

 

It's a process of elimination.

 

 

Cheers,

Apologies for my late response

I did yesterday a flight without any add-on scenery from  EHAM Schiphol to FACT Cape Town

 

And still crash :(

Anyone have any ideas?

Here's some more ideas... also users with the NTDLL.dll issue with the PMDG 777:

 

http://www.avsim.com/topic/487660-fsx-ctd-777/

 

 

They're not using FS2Crew, but worth a shot.

Bryan,

 

Sorry, I didn't bail on this thread. I just moved and we are still unpacking. I still need to set up my computer. I'll try a flight once I get it set up and see if I get another crash. For me, it's just strange it all happened after the latest update. Before that, zero issues.

 

Thinks for the link in your most recent post. I'll need to investigate that one further.

 

Todd

Todd, I think you may have double entries in your DLL.XML and/or EXE.XML. Check programdata/lockheed Martin/P3Dv3 folder and %APP%/user/roaming/LM/P3Dv3

If using ASN, make sure it is the last entry, and FSUIPC should also be last entry. Compare both xmls in both folders.

This is the most common fix for ntdll errors in P3D. And they are random.

Todd, I think you may have double entries in your DLL.XML and/or EXE.DLL. Check programdata/lockheed Martin/P3Dv3 folder and %APP%/user/roaming/LM/P3Dv3

If using ASN, make sure it is the last entry, and FSUIPC should also be last entry. Compare both xmls in both folders.

This is the most common fix for ntdll errors in P3D. And they are random.

 

 

Thanks for sharing that.

 

In the good old days before FSX we could just drop DLLs in the module folder.  Easy peasy.

 

And then they came up with the DLL.xml idea, and a million FS developer voices cried out in terror...

Thanks for sharing that.

 

In the good old days before FSX we could just drop DLLs in the module folder.  Easy peasy.

 

And then they came up with the DLL.xml idea, and a million FS developer voices cried out in terror...

Yes Bryan, things were so much easier. Now when I install a new addon, I have to check the integrity of the xml files to ensure everything is in correct order, and no double entries, in two different locations.

 

I got caught out on this one, was having random ntdll errors, and after checking the xml's found double entries, as some older software gets confused, and so does P3D

Digging up an old thread, I know (busy life with 3 youngsters). I already know about the double entries and strictly watch those. The issue has never resolved for me until I uninstalled FS2Crew. Maybe I just can't use it on my system. Oh well...

Can you revert to the old version as a test?

I don't have the older version that was working. Probably should have kept it. Lesson learned.

I'm away from my home computer, and will be back home in a month.

 

Contact me again again and I may still have the older version on my main computer.