Basically sim performance is excellent, good frame rates, no stutters but on final approach or just about to touch down sim crashes with the ntdll.dll, error at different airports by different developers. - Only have the PMDG aircraft installed.

 

Have read and checked all items on the Avsim CTD guide, reduced all settings to 1024, rebuilt the P3D.cfg, took out all entries on dll.xml and then tested the sim by adding entries one at a time, all to no avail. Not sure what else to do bar wiping the whole windows 7 64 install and starting from scratch again. Any other suggestions would be greatly appreciated.

 

Thanks

I had this issue with FSX a couple of years ago, turned out it was my nvidia drivers causing the problem.

 

I used this tool to completely wipe all traces of video card drivers, it will reboot your pc into safe mode so it can do a "deep clean" off all graphics drivers.

 

http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

 

Then I did a clean re-install of the latest nvidia geforce drivers (at the time).

 

ntdll.dll crashes went away!

That truly is annoying.  Hope you get it sorted.

Thanks for the feedback, haven't tried new drivers so I'll do that this evening. Will remove all traces of previous drivers using Driver cleaner and do a custom install. Will keep you posted.

 

Regards

Make sure you delete your shader files and let P3D rebuild them any time you change drivers or make a significant change in your video settings.

 

Regards

hate to be the one to say it, but all over forums where folks have issues with p3dv3 two main addons are in use

 

1. PMDG

2 Sometimes FTX vector, but by far mostly PMDG.

 

Honestly haven't charged folks for FSX and p3d PMDG, it will only be fare for PMDG to address atleast the VAS issue with their ac that makes them too bloated for the sim, unless you wana fly with the sim in 2d graphics.

 

To be fare, p3d in 32 bit is arguably no longer tenable today, its hard enough developing reliable complex software such as jetliner, never mind having to resort to bit fields to save memory, must be like developing in assembly language.

 

But far too many sim forums  topics all over the web with folks having issues, and addon in use is mostly always PMDG, would be nice if they announce pacht to deal with the VAS issues or even possibly memory leak in the case of PMDG.

 

On my previous p3d install only about 30% of my pmdg flights ever made it to destination, and many failed during approach landing when the terrain starts to be burden for the sim as you get lower.

 

There have been enough of these for PMDG to make official announcement about rework memory for their expensive products many cant use cause its too bloated for the 32 bit sim even WITH MODERATE SETTINGS. 

 

But glad to see pmdg adding options like only using ac interior to save VAS we need more options like that for example to cut down on systems for those not too kin on that but prefer exterior view but reduced systems simulation etc.

I loved PMDG planes on FSX, but their pricing policy has kept me away since I switched to P3D v3. A very convenient side effect is that I never had to worry about CTDs anymore. And I am very happy with my fleet (Majestic, Aerosoft, QW) as well.

 

Peter 

No issues with any PMDG planes or Orbx products here with rather extreme graphics settings, VAS usage is very good, never OOMs ... my suggestions:

 

1.  Turn OFF any overclocking (CPU and GPU) and return to defaults

2.  Download nVidia drivers from web site

3.  run DDU (boots to safe mode)

4.  Run As Administrator nVidia driver installer

5.  Don't use any replacement DXGI (i.e. SweetFx, Reshade, etc.)

6.  Don't use NI

 

Basic idea is to get it working and stable.

 

Cheers, Rob.

No issues with any PMDG planes or Orbx products here with rather extreme graphics settings, VAS usage is very good, never OOMs ... my suggestions:

 

1.  Turn OFF any overclocking (CPU and GPU) and return to defaults

And to piggyback on this, in the case of GPUs, returning to default may not be enough...many GPUs come factory overclocked right out of the box.  I have a factory overclocked eVGA 980 Hydrocopper that passes stress tests at default factory settings, but won't run FSX reliably.  I had to take it back down to GPU/memory clock speeds somewhere between nVidia's stock reference 980 settings and the factory overclock to stop regularly occurring black/gray screen and g3d.dll crashes.

 

Regards

The NTDLL.dll is an ugly crash for sure and difficult to determine the Source of the problem.  Reiterating my comments in the AVSIM CTD Guide about this crash:

 

NTDLL.dll – Several possibilities as follows:

• Quote from Microsoft Techs – “Heap metadata can become corrupted and it has been identified by Microsoft as one of the most common causes of application failures.  When an application crash shows the faulting module as ntdll.dll along with the Memory Access Violation (0xc0000005), then Windows places the application on a watch list and, if the application crashes at least four times or more in an hour, the fault tolerant heap service will configure the application to use the fault tolerant heap service in the future” (Source - Chapter 10, Memory Management, Windows Internals, Part 2: Covering Windows Server 2008 R2 and Windows 7 by Mark E. Russinovich, David A Solomon, and Alex Ionescu).  The service is part of the Security Center service so you need to make sure this service is turned on.  If the ntdll.dll is placed on the watch list, this information will be shown in the Event Viewer (Admin Events).  See also Increase Heap Limitation in the Actions to Take to Prevent Crashes section of this guide.
• MyTrafficX version 5.4c is installed. It is believed to be caused by an AI scheduling programming error. Go back to the 5.4b version or make sure no external AI program schedule is activated (i.e., the 2012 or 2013 Schedules on the developers website).  The default schedule appears to be okay for most. Check the developers support forums for updated information and possible bug fixes.
• System overheats or you have wrong timings/voltages set for your installed RAM or CPU voltage. You might be able to fix by returning your BIOS to Optimized Defaults or lowering your overclock by one point from say, 4.4GHz to 4.3GHz.
• Remove the UIAutomationcore.dll from the main FSX folder, if installed.
• Check your dll.xml for duplicate entries or any corruption.  Some have fixed the NTDLL.dll CTD by removing duplicate entries and/or old software entries where the software is no longer on your system.
• Disable User Access Controls (UAC) (see the section above for more information).
• Update hardware drivers for your computer (especially on new computer systems) (see Driver Update information in this guide).

The NTDLL.dll is a system file and you should suspect a hardware or overclock or bad voltages and not P3D (or FSX) or any addon.  We were able to pinpoint only one instance where a P3D/FSX addon caused a crash and that was with the older version of MyTrafficX as explained above.  The information and recommendations shown above came from the entire Flight Simulation Community and not just here at AVSIM.  Since you rebuilt your P3D.cfg, disabled everything in the dll.xml (you could have moved it to a temporary folder and restarted P3D to test whether there's a problem there), and lowered your settings (well, rebuilding the P3D.cfg does that), then it is most likely not a problem with P3D or any addons.  However, you can also move your scenery.cfg to a temporary folder, restart P3D and the config will be returned to the default.  If that fixes the problem, then maybe one of your scenery addons is causing the problem.

 

Hope you find the cause of your ntdll.dll crashes soon!

 

Best regards,