This faulting module is beginning to get so aggravating. Twice, now, flights have been curtailed to CTD due to this module.Had I not had FSUIPC auto-saving my flights, I think I'd just pack up flightsimming altogether! Is this what the so-called saviour of flightsimiiming---P3Dv4.1 64-bit code---has brought us down to? Over Eastern Coast of USA heading to KMCO. PMDG 747-400, ASP4. No scenery add-ons, bang, CTD!

EDIT: After a re-boot to clear the DLLs, and discarding ASP4, yet another CTD, ntdll.dll, same place on the flight track. Only have Orbx  Global.So, am going to try uninstalling that to narrow down what is causing this really irksome CTD.

According to the AVSIM CTD Guide, the ntdll error can occur if you use the FSUIPC autosave.  Perhaps fixed in later versions of FSUIPC?

Thanks Jim, but I have the very latest FSUIPC.

Just uninstalled Orbx Global; rolled back the Nvidia drivers after a clean uninstall using DDU default scenery, 500nm from default KMCO. 4th try. Let's see what happens. I'll also turn off auto-save if it happens 5th time.

Just like the OP where this module was faulting and causing a CTD at the same point, this too, for the 5th time it has CTD'd is happening at a waypoint into KMCO called HIBAC, same waypoint three times on the trot.

Now, if we can only fix the problem put forth by the OP as this topic has been high-jacked a few times....

30 minutes ago, Jim Young said:

this topic has been high-jacked a few times...

How is that, Jim? I thought the topic was dealing with an ntdll.dll caused CTD?

Each NTDLL error is different as each person has their own addons, their own computer setup, sometimes different Windows OS's, and I believe his crash was caused by the vcruntime140.dll?  This is the OP's topic.  Any issues by others should be posted in their own topic.  I'll see if I can split your issues into a new topic.

Thanks, Jim. Appreciate that

This particular ntdll,dll CTD is repeatedly occurring at exactly the same waypoint. FSUIPC auto-save unchecked, and no add-on scenery other than the PMDG 737-400 v3.

I had a flight in FSX once from KORD to KSTL.  At the same point in the flight I kept getting a freeze or CTD.  I ran Process Monitor and saw that MTX was being loaded.  I disabled MTX and this time not CTD or freeze.  As I posted elsewhere, maybe here, I found that the MyTrafficX6 module, MyTrafficMil.bgl was causing the NTDLL and StackHash crashes I was experiencing after installing v4.1 .  I was crashing at the same spot.  It sounded like ATC was trying to run but it became garbled and the flight ended.  I have since fixed it by renaming the mytrafficmil.bgl.  Now I knew from many others that the mytrafficmil.bgl caused the ntdll.dll crash but I had removed some aircraft that were incompatible with P3DV4 as they were developed in FS9 days.  I thought the issue was fixed by doing that and I had not seen a crash for some time.  Then I decided to fly an old route I flew in V4 after I got V4.1 (KSFO to KSAN) in my PMDG747.  Nearing KSAN (where there are many military bases), I started to get the ATC chatter and it crash.  I can replicate this crash 100% of the time and removing the mytrafficmil.bgl fixed it.  If you disabled all of your add-on scenery, that means you disabled MyTrafficX so your issue might be different but most likely you have an incompatible texture in the scenery where you are getting your crashes.  It could be an airport on the ground where someone installed static aircraft that were made in FS9 and earlier.