On 9/11/2017 at 11:06 AM, IAhawkeyeDDS said:

I was having a similar problem as you were.  I have a similar rig and have similar add-ons.  Two hours into transatlantic --> CTD --> again, again, and again.   I fly the PMDG T7 and 737ngx.  Then one flight I used the 737ngx --> I didn't load any flightplan into AS4D or P3D --> flew for 6 hours straight and no CTD.  I thought I might be on to something --> so in the T7 I turned off upload flight plan to AS4D/P3D and voila --> 10 hour flight without CTD.  So for me I was able to alleviate the CTD by doing all flight-planning on the FMC and not allowing the flight plan to be uploaded into AS4D/P3d. Only annoying thing is the AS4D keeps asking for flight plan to be loaded via the green message bar.

 

Give it a try.. might work for you too.

This is a bit late to the rodeo but I just had a 9 hour flight with 20 mins to go...CTD with PMDG T7 and ChasePlane on view change...seems this is still not fixed. Not sure who the culprit was but between the two it is almost $200 USD....this is just nuts. 

After 9 hours of running a benchmark program to test the stability of your computer system with or without an overclocked computer, you could have the same issue.  How come you can fly for 9 hours with the PMDG T7, ChasePlane, ASP4, and other scenery/AI program and not have a crash until 9 hours later.  If it was one of the programs you mentioned, wouldn't you think it would have crashed sooner?  So I suggest it is your hardware like your CPU or GPU causing the problem.

I have monitored my system during flights and have seen the temp on the CPU slowly rise over time getting close to 70C (which is well within parameters).  It stays like that most of the time but sometimes I have seen it between 80-90C depending on the situation.  It just takes an overheated CPU, GPU, MB, or SIMM to suddenly crash your system and, after nine hours, that makes sense it is crashing especially if your P3D settings are high.  This may be a reason why it is happening to only you and a few others but not to everyone.

But then, you read many of the other nearby topics and people are not getting crashes when you turn off ASP4.  Turn it on and you get crashes and they say it's because their simconnect and program needs to be loaded with Administrative Privileges.  Now, this is not their problem but that of Windows 10.

Hope you can get it sorted.

Best regards,

Jim

 

 

On 9/8/2017 at 8:22 PM, Jim Young said:

The exception code - 0xc0000374 indicates Heap Corruption.  You can lower your overclock or return the OC to the optimal default and that fixes most ntdll.dll errors.  MyTrafficX also causes the ntdll.dll error as trafficmil.bgl is not compatible with P3DV4.  You did not indicate you had that installed though.  Just mentioning in case you have it installed.  If you are flying near the incompatible aircraft, it may cause your sim to crash.

The AVSIM CTD Guide provides suggestions I found across the internet for NTDLL.dll errors.  Look in the rear of the guide.

Best regards,

Jim

 

Hi I have the same exception code - 0xc0000374 and I believe is only bc of the heap corruption. I did a full reinstall of my computer and I install clean P3D V4, both 737 and 700 base and expansion, and still I got this error "ntdll.dll". I haven't tried to lower the OC or to retorn to the optimal default. Can you help me how to do this ? 

 

Best regards,

Pedro Cassoma

34 minutes ago, pedro_cassoma said:

I haven't tried to lower the OC or to retorn to the optimal default. Can you help me how to do this ? 

 

In my BIOS, I have the ability to go to the ASUS Overclocking Profile and save my overclock to a USB drive (one of those flash drives).  You can then exit the BIOS and you will then see the option to load the Optimized Default settings.  This will result in an overclock too but it was optimized (at least with the ASUS Boards).  If you do not have an ASUS board, then you will have to Google something like how to set optimized defaults for Gigabit motherboard, etc.

Heap corruption is common and caused by Windows, not P3D.  P3D just happened to be running when it happens.

Best regards,