P3D V3.4 ntdll.dll crash

[virtualflying 2]

For the past few weeks I've been getting the random ntdll.dll crash, but it would happen only if I started clicking around while P3D loaded. Now, it does it whenever I try to load in. 

-Tried using FSDT Live Update (normally fixes everything)

-Updated Drivers

-PC is not overheating, checked the temps and they looked normal.

-Tried removing dll.xml

 

I cannot figure this out for the life of me, anyone got anything that could help? Thanks so much

[virtualflying 2]

I'd also like to point out I've done everything in the CTD Guide

[BAW264 1]

I had that problem myself, got to use Affinitymask, leave the first core free, put this in your p3d.cfg

[JOBSCHEDULER]
AffinityMask=254

 

[virtualflying 2]

1 hour ago, BAW264 said:

I had that problem myself, got to use Affinitymask, leave the first core free, put this in your p3d.cfg

[JOBSCHEDULER]
AffinityMask=254

 

While that did let me run the simulator, it is still super finicky. Removing a scenery in the library caused it to crash, still due to ntdll.dll.

[jabloomf1230 2,445]

Affinity  mask is not going to rid a setup of ntdll.dll CTDs. Other than a bad OC, the vast majority  of these errors are caused by misbehaving  3rd party addons. The most common version of this error is heap corruption and the base simulators almost never show that error. Think about it. If they did, a company like LM could easily reproduce the error.

Hence, the only way to troubleshoot  this error is to to remove all addons and test them separately until the cause is isolated. This is not to say that the base simulator  is without potential blame. An add-on could be exposing a bug in the sim, but then it would be the responsibility  of the 3rd party developer  to reproduce  the CTD.

[Maarten Otto 18]

CPU power could be the issue...

Try giving it a bit more juice. Or (in my case) a bit less juice. My errors were gone since I altered the Vcore voltage.

[virtualflying 2]

I haven't touched my BIOS in a long time so I doubt thats the problem,. It's kept cool with my H75, so it has to be software.

[Jim Young 2,356]

The ntdll.dll is a system module and does not belong to any FS program or addon.  It is related to memory.  A year or two ago you could have overclocked your computer (or it was done by an expert).  If you have an outdated module, high P3D and/or display driver settings, you will get the ntdll.dll 100% of the time as your system just could not handle the process requested by your simulator.  A CPU voltage too high or too low will cause this crash.  The AffinityMask tweak has been known to cause this crash.  The BufferPools tweak has been known to cause this crash.  So there are many possibilities.  This is why the AVSIM CTD Guide recommends you bring your system back to the default on pages 9 and 10 and tells you to rename your p3d.cfg, your scenery.cfg, and the dll.xml located in the same folder as your p3d.cfg and your scenery.cfg.  If there are no crashes, then there was a problem with them and I would bring the scenery.cfg back and maybe one of the dll.xml's.  If no crashes, then bring the other dll.xml back.  If the crashes start up, you'll know it is connected with one of the modules the dll.xml loads or, if you get the ntdll.dll crash when you bring back the scenery.cfg, it is one of the sceneries (less likely).  Most causes are high settings and tweaks so I believe it is your p3d.cfg.