As I had installed several UK2000 airports prior to v4.1, and was getting this very irritating ntdll.dll CTD, I uninstalled every UK2000, and then re-installed all again. But, just a P3Dv4.1 is loading up after asking to add-on these airports, it goes CTD with that error.

Is anyone else experiencing the same?

do you have the v4 installers ?? 

Are you installing the new way or old way?  

ntdll.dll errors can be cause by a ton of things.  Usually has to do with your nvidia drivers.  sometimes rolling back or updating them works.  

18 hours ago, tooting said:

do you have the v4 installers ?? 

Yes, all of them.

6 minutes ago, jason99vmi said:

Are you installing the new way or old way?  

ntdll.dll errors can be cause by a ton of things.  Usually has to do with your nvidia drivers.  sometimes rolling back or updating them works.  

New way, if you mean letting the installers do their job. Oddly enough, soon after posting, I re-booted, and re-started 4.1 and was able to take off from EGPK in my new FSL A320.

Nvidia drivers are the latest stable ones, then rolled back. This particular .dll has been like a leech causing so many CTDs that I have seen here, in P3D more than I ever experienced it in FSX-SE.

1 hour ago, jason99vmi said:

Are you installing the new way or old way?  

ntdll.dll errors can be cause by a ton of things.  Usually has to do with your nvidia drivers.  sometimes rolling back or updating them works.  

Absolute rubbish.  the drivers don't cause ntdll.dll ctds.  theres a million things that can cause ntdll.dll ctds.  Bad ai models,  bad overclocks, fsrealtime to name a few.  It's not the drivers 

1 hour ago, tooting said:

Absolute rubbish.  the drivers don't cause ntdll.dll ctds.  theres a million things that can cause ntdll.dll ctds.  Bad ai models,  bad overclocks, fsrealtime to name a few.  It's not the drivers 

Well then super genius feel free to tell Jim Young his AVSIM CTD guide is worthless.  

And no need to be rude guys. Stay classy :-)

Big culprit of ntdll.dll errors is bad memory management. Just one hiccup in P3Dv4 memory management process (and think of all the things behind the scenes that are communicating with P3D via simconnect) and you get the CTD. Whole it used to drivers causing this it is usually not that anymore. And just because Jim has not updated his CTD guide, remember he is just 1 person with 1 opinion on what is causing that CTD. In other words just because Jim has that in that guide does not mean that is the ONLY answer. 

I will say with v4 this ntdll.dll error is way more prevalent than in v3. LM IMO needs to do more to improve the core sim memory management processes. 

Yeah that is why my first sentence said the error can be caused by a ton of things.  But its worth noting past steps in the guide to start to rule stuff out.  

17 minutes ago, jason99vmi said:

Yeah that is why my first sentence said the error can be caused by a ton of things.  But its worth noting past steps in the guide to start to rule stuff out.  

Agreed, start with the easy stuff to rule out. With v4 though I think this ntdll.dll CTD fix is not with us but with LM.