Jump to content
Sign in to follow this  
Followers 0
davidjpowell1974

p3d v3.1 CTD

By davidjpowell1974, in Crash To Desktop (CTD) Forum

Recommended Posts

davidjpowell1974    4

davidjpowell1974
Posted

Am now struggling.  Happens most flights.

 

error message is

 

Log Name:      Application
Source:        Application Error
Date:          23/01/2016 21:05:10
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-LN01DML
Description:
Faulting application name: Prepar3D.exe, version: 3.1.2.15831, time stamp: 0x5672b60a
Faulting module name: ntdll.dll, version: 10.0.10240.16603, time stamp: 0x565531ee
Exception code: 0xc0000374
Fault offset: 0x000d5aac
Faulting process ID: 0x1c44
Faulting application start time: 0x01d1561a56492eb2
Faulting application path: D:\p3d\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: d29441de-d8b5-44d3-9734-ccc5eff02336
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-01-23T21:05:10.000000000Z" />
    <EventRecordID>1245</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-LN01DML</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>3.1.2.15831</Data>
    <Data>5672b60a</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.10240.16603</Data>
    <Data>565531ee</Data>
    <Data>c0000374</Data>
    <Data>000d5aac</Data>
    <Data>1c44</Data>
    <Data>01d1561a56492eb2</Data>
    <Data>D:\p3d\Prepar3D.exe</Data>
    <Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
    <Data>d29441de-d8b5-44d3-9734-ccc5eff02336</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>
 
contents of dll file...
 
<?xml version="1.0" encoding="WINDOWS-1252"?>
 
-<SimBase.Document version="1,0" Type="Launch">
 
<Descr>Launch</Descr>
 
<Filename>dll.xml</Filename>
 
<Disabled>False</Disabled>
 
<Launch.ManualLoad>False</Launch.ManualLoad>
 
 
-<Launch.Addon>
 
<Name>PMDG Interface</Name>
 
<Disabled>False</Disabled>
 
<Path>PMDG\DLLs\PMDG_Interface.dll</Path>
 
<DllStartName>module_init</DllStartName>
 
<DllStopName>module_deinit</DllStopName>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>RAASPRO</Name>
 
<Disabled>False</Disabled>
 
<Path>.\RAASPRO\RAASPRO.dll</Path>
 
<DllStartName>module_init</DllStartName>
 
<DllStopName>module_deinit</DllStopName>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>VAInterface</Name>
 
<Disabled>False</Disabled>
 
<Path>Modules\VAInterface.dll</Path>
 
<DllStartName>module_init</DllStartName>
 
<DllStopName>module_deinit</DllStopName>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>FSCaptain</Name>
 
<Disabled>False</Disabled>
 
<ManualLoad>False</ManualLoad>
 
<Path>FSCaptain\bin\FSCaptain.dll</Path>
 
</Launch.Addon>
 
 
-<Launch.Addon>
 
<Name>as_connect</Name>
 
<Disabled>False</Disabled>
 
<Path>as_srv\as_btstrp.dll</Path>
 
</Launch.Addon>
 
</SimBase.Document>
 
Grateful for any trips.......
 
thanks David

Share this post

Link to post
Share on other sites

Jim Young    2,356

Jim Young
Posted

If your sim did not start up, then you should suspect the dll.xml but, if it started up okay and you had the crash while flying, then it is most likely something else.  If there's something wrong with a module loading in the dll.xml, it will tell you right away (most of the time). 

 

Your crash was caused by the infamous ntdll.dll and there are so many possibilities associated with this crash.  The Exception Code 0374 indicates heap corruption which is also common, especially with P3D/FSX/and FSX-SE.

 

Here's what the AVSIM CTD Guide says on probable causes for the ntdll.dll:

 

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.
  • 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.
  • 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).

Another possibility could be very high P3D settings.  That causes a lot of resources to be placed on your system and it pushes a bad setting, say in the BIOS or an overclock, to cause the crash.  When there is no demand for more resources, then the system and your application works properly.  So, this also includes bad tweaks.  For instance, if you employed the AffinityMask or BufferPool tweak in your P3D config with wrong parameters for YOUR computer system or setup, it could place more demands on your system.  This is why we also recommend in the CTD Guide (see link in my signature) to bring your system back to the default settings and that's done by moving your p3d.cfg, dll.xml, and scenery.cfg to a temporary folder.  Your p3d.cfg and scenery.cfg will be rebuilt back to the default settings.  If no more crashes, then move the dll.xml you had moved previously to a temporary directory back to it's folder (same folder as where the p3d.dll is located).  Now you can use such things as ASN and your other addons that are really harsh on your system if the settings are set too high.  If you still have no problems, then move the scenery.cfg you had before back into its proper folder.  If still no problems, then the ntdll.dll error was probably caused by your p3d.cfg (a bad tweak and/or high settings).

 

My ntdll crashes were always caused by a too high or too low CPU voltage setting in my BIOS that I used when I overclocked it.  I returned the overclock to the optimized default settings and the ntdll.dll went away.  Once I had two identical PMDG entries in my dll.xml, removed one of them, and the ntdll.dll errors went away.  I don't see any duplicate entries in your dll.xml.  Just saying to show you how such a simple thing as duplicate entries in the dll.xml could cause an ntdll.dll crash.  This is another reason why people fix this problem when they reinstall Windows and then P3D (which I have done but will not in the future as I'm a bit smarter now).  They say that moving your p3d.cfg to a temporary folder and restarting p3d and letting the config rebuild is equal to a reinstall of P3D.  People start messing around with the parameters, adding tweaks, raising settings, and things go bad.

 

Hope this helps.

 

Best regards,

Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post

Link to post
Share on other sites

Bobsk8    12,679

Bobsk8
Posted

I haven't had any crashes of P3D, until the last couple of weeks, where I have had 4. Never had a crash of Version 2.5 or Version 3, only 3.1.    Today I have had 2 consecutive flights crash from about 45 minutes to 1 1/2 hours. haven't changed anything in my system.  here is the error log I got.  Nothing overclocked, Windows 7, P3D settings all on medium, and have not been changed in months. Any ideas, anyone. 

 

Version=1
EventType=APPCRASH
EventTime=130980726647562041
ReportType=2
Consent=1
UploadTime=130980726649932176
ReportIdentifier=21dab81f-c23a-11e5-88c2-d4bed9ce7bcd
IntegratorReportIdentifier=21dab81e-c23a-11e5-88c2-d4bed9ce7bcd
WOW64=1
Response.BucketId=534810104
Response.BucketTable=25
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=3.1.2.15831
Sig[2].Name=Application Timestamp
Sig[2].Value=5672b60a
Sig[3].Name=Fault Module Name
Sig[3].Value=ntdll.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7601.18933
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=55a69e20
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0003447e
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
UI[3]=A fatal error occurred.
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\WRusr.dll
LoadedModule[5]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[6]=C:\Windows\syswow64\USER32.dll
LoadedModule[7]=C:\Windows\syswow64\GDI32.dll
LoadedModule[8]=C:\Windows\syswow64\LPK.dll
LoadedModule[9]=C:\Windows\syswow64\USP10.dll
LoadedModule[10]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[11]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[12]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[13]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[14]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[15]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[17]=C:\Windows\syswow64\ole32.dll
LoadedModule[18]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[19]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[20]=C:\Windows\syswow64\NSI.dll
LoadedModule[21]=C:\Windows\syswow64\urlmon.dll
LoadedModule[22]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[23]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[24]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[25]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[26]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[27]=C:\Windows\system32\version.DLL
LoadedModule[28]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[29]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[30]=C:\Windows\syswow64\iertutil.dll
LoadedModule[31]=C:\Windows\syswow64\WININET.dll
LoadedModule[32]=C:\Windows\syswow64\USERENV.dll
LoadedModule[33]=C:\Windows\syswow64\profapi.dll
LoadedModule[34]=C:\Windows\system32\OLEACC.dll
LoadedModule[35]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[36]=C:\Windows\system32\Secur32.dll
LoadedModule[37]=C:\Windows\system32\MSIMG32.dll
LoadedModule[38]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\api.dll
LoadedModule[39]=C:\Windows\system32\Cabinet.dll
LoadedModule[40]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[41]=C:\Windows\system32\WINHTTP.dll
LoadedModule[42]=C:\Windows\system32\webio.dll
LoadedModule[43]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18837_none_ec86b8d6858ec0bc\COMCTL32.dll
LoadedModule[44]=C:\Windows\system32\WINMM.dll
LoadedModule[45]=C:\Windows\syswow64\IMM32.dll
LoadedModule[46]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[47]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\acontain.dll
LoadedModule[48]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\ai_player.dll
LoadedModule[49]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\atc.dll
LoadedModule[50]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\demo.dll
LoadedModule[51]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\controls.dll
LoadedModule[52]=C:\Windows\system32\HID.DLL
LoadedModule[53]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[54]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[55]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[56]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\flight.dll
LoadedModule[57]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\facilities.dll
LoadedModule[58]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\fe.dll
LoadedModule[59]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\main.dll
LoadedModule[60]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[61]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\fs-traffic.dll
LoadedModule[62]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\g3d.dll
LoadedModule[63]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\g2d.dll
LoadedModule[64]=C:\Windows\system32\dxgi.dll
LoadedModule[65]=C:\Windows\system32\dwmapi.dll
LoadedModule[66]=C:\Windows\system32\d3d9.dll
LoadedModule[67]=C:\Windows\system32\d3d8thk.dll
LoadedModule[68]=C:\Windows\system32\d3d11.dll
LoadedModule[69]=C:\Windows\system32\D3DCOMPILER_43.dll
LoadedModule[70]=C:\Windows\system32\OPENGL32.dll
LoadedModule[71]=C:\Windows\system32\GLU32.dll
LoadedModule[72]=C:\Windows\system32\DDRAW.dll
LoadedModule[73]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[74]=C:\Windows\system32\d3dx9_43.dll
LoadedModule[75]=C:\Windows\system32\d3dx11_43.dll
LoadedModule[76]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[77]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\pdk.dll
LoadedModule[78]=C:\Windows\system32\MSVCR120.dll
LoadedModule[79]=C:\Windows\system32\MSVCP120.dll
LoadedModule[80]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\simscheduler.dll
LoadedModule[81]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\simprop.dll
LoadedModule[82]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\util.dll
LoadedModule[83]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\weather.dll
LoadedModule[84]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\sim1.dll
LoadedModule[85]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\multiplayer.dll
LoadedModule[86]=C:\Windows\system32\DSOUND.dll
LoadedModule[87]=C:\Windows\system32\POWRPROF.dll
LoadedModule[88]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\panels.dll
LoadedModule[89]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\sound.dll
LoadedModule[90]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\audiere.dll
LoadedModule[91]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\window.dll
LoadedModule[92]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\terrain.dll
LoadedModule[93]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\visualfx.dll
LoadedModule[94]=C:\Windows\system32\MSACM32.dll
LoadedModule[95]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\menus.dll
LoadedModule[96]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\livingwater.dll
LoadedModule[97]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\gps.dll
LoadedModule[98]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\symmap.dll
LoadedModule[99]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[100]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[101]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\language.dll
LoadedModule[102]=C:\Windows\system32\bcrypt.dll
LoadedModule[103]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[104]=C:\Windows\system32\uxtheme.dll
LoadedModule[105]=C:\Windows\system32\MSXML6.DLL
LoadedModule[106]=C:\Windows\system32\ntmarta.dll
LoadedModule[107]=C:\Windows\system32\PROPSYS.dll
LoadedModule[108]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\uiInterface.dll
LoadedModule[109]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[110]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\DIS.dll
LoadedModule[111]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[112]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
LoadedModule[113]=C:\Windows\system32\MSVCR120_CLR0400.dll
LoadedModule[114]=C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\225759bb87c854c0fff27b1d84858c21\mscorlib.ni.dll
LoadedModule[115]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
LoadedModule[116]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System\52cca48930e580e3189eac47158c20be\System.ni.dll
LoadedModule[117]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Core\55560c2014611e9119f99923c9ebdeef\System.Core.ni.dll
LoadedModule[118]=C:\Windows\assembly\NativeImages_v4.0.30319_32\WindowsBase\32512bd09e2231f6eebb15fc17e3ad79\WindowsBase.ni.dll
LoadedModule[119]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[120]=C:\Windows\system32\rsaenh.dll
LoadedModule[121]=C:\Windows\assembly\NativeImages_v4.0.30319_32\PresentationCore\416ba33cb980d07643e82c4c45bd5786\PresentationCore.ni.dll
LoadedModule[122]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Presentatio5ae0f00f#\da36abbea6ef456f432434d4d8d835c1\PresentationFramework.ni.dll
LoadedModule[123]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Xaml\6d09f865a22e2f903b74476769e1b76a\System.Xaml.ni.dll
LoadedModule[124]=C:\Windows\system32\dwrite.dll
LoadedModule[125]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[126]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[127]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\nlssorting.dll
LoadedModule[128]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[129]=C:\Windows\system32\iphlpapi.dll
LoadedModule[130]=C:\Windows\system32\WINNSI.DLL
LoadedModule[131]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[132]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[133]=C:\Windows\system32\credssp.dll
LoadedModule[134]=C:\Windows\system32\DNSAPI.dll
LoadedModule[135]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
LoadedModule[136]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[137]=C:\Windows\system32\rasadhlp.dll
LoadedModule[138]=C:\Windows\System32\wship6.dll
LoadedModule[139]=C:\Windows\System32\wshtcpip.dll
LoadedModule[140]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[141]=C:\Windows\system32\nvwgf2um.dll
LoadedModule[142]=C:\Windows\system32\nvspcap.dll
LoadedModule[143]=C:\Windows\system32\nvapi.dll
LoadedModule[144]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[145]=C:\Windows\system32\WINSTA.dll
LoadedModule[146]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\comctl32.dll
LoadedModule[147]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[148]=C:\Windows\system32\apphelp.dll
LoadedModule[149]=C:\Windows\system32\ntshrui.dll
LoadedModule[150]=C:\Windows\system32\srvcli.dll
LoadedModule[151]=C:\Windows\system32\cscapi.dll
LoadedModule[152]=C:\Windows\system32\slc.dll
LoadedModule[153]=C:\Windows\system32\netutils.dll
LoadedModule[154]=C:\Windows\system32\mssprxy.dll
LoadedModule[155]=C:\Windows\System32\MMDevApi.dll
LoadedModule[156]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[157]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[158]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Presentatio1c9175f8#\1d34aa9a1a9cacd0301097d55cd6e658\PresentationFramework.Aero.ni.dll
LoadedModule[159]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[160]=C:\Windows\system32\nvd3dum.dll
LoadedModule[161]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Drawing\646b4b01cb29986f8e076aa65c9e9753\System.Drawing.ni.dll
LoadedModule[162]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\5aac750b35b27770dccb1a43f83cced7\System.Windows.Forms.ni.dll
LoadedModule[163]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Gauges\TargetInfo.dll
LoadedModule[164]=C:\Windows\system32\wdmaud.drv
LoadedModule[165]=C:\Windows\system32\ksuser.dll
LoadedModule[166]=C:\Windows\system32\AVRT.dll
LoadedModule[167]=C:\Windows\system32\msacm32.drv
LoadedModule[168]=C:\Windows\system32\midimap.dll
LoadedModule[169]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\radar.dll
LoadedModule[170]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\D3DCOMPILER_47.dll
LoadedModule[171]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Oculus.dll
LoadedModule[172]=C:\Windows\system32\dbghelp.dll
LoadedModule[173]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\ControllableCamera.dll
LoadedModule[174]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Aerosoft\Flight Recorder\AS-FlightRecorder.dll
LoadedModule[175]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[176]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[177]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[178]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[179]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\bglmanx.dll
LoadedModule[180]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\RAASPRO\RAASPRO.dll
LoadedModule[181]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[182]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[183]=C:\Windows\System32\netprofm.dll
LoadedModule[184]=C:\Windows\System32\nlaapi.dll
LoadedModule[185]=C:\Windows\System32\npmproxy.dll
LoadedModule[186]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SimConnect.dll
LoadedModule[187]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll
LoadedModule[188]=C:\Windows\system32\MSDART.DLL
LoadedModule[189]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll
LoadedModule[190]=C:\Program Files (x86)\Common Files\System\Ole DB\OLEDB32R.DLL
LoadedModule[191]=C:\Windows\system32\comsvcs.dll
LoadedModule[192]=C:\Windows\system32\ATL.DLL
LoadedModule[193]=C:\Windows\SysWOW64\msjetoledb40.dll
LoadedModule[194]=C:\Windows\SysWOW64\msjet40.dll
LoadedModule[195]=C:\Windows\SysWOW64\mswstr10.dll
LoadedModule[196]=C:\Windows\SysWOW64\msjter40.dll
LoadedModule[197]=C:\Windows\SysWOW64\MSJINT40.DLL
LoadedModule[198]=C:\Windows\SysWOW64\mstext40.dll
LoadedModule[199]=C:\Windows\system32\mlang.dll
LoadedModule[200]=C:\Windows\system32\RAASAUDIO32.DLL
LoadedModule[201]=C:\Windows\system32\X3DAudio1_6.dll
LoadedModule[202]=C:\Windows\SysWow64\xactengine3_4.dll
LoadedModule[203]=C:\Windows\SysWow64\XAudio2_4.dll
LoadedModule[204]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\PMDG\DLLs\PMDG_HUD_interface.dll
LoadedModule[205]=C:\Windows\system32\MSVCR100.dll
LoadedModule[206]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.dll
LoadedModule[207]=C:\Windows\system32\DINPUT8.dll
LoadedModule[208]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll
LoadedModule[209]=C:\Windows\system32\MSVCP100.dll
LoadedModule[210]=C:\Windows\system32\DINPUT.DLL
LoadedModule[211]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\as_srv\as_btstrp.dll
LoadedModule[212]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\SimDirector.dll
LoadedModule[213]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\BGLCompLib.dll
LoadedModule[214]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\simpropext.dll
LoadedModule[215]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[216]=C:\Windows\system32\wbemcomn.dll
LoadedModule[217]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[218]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[219]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[220]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18946_none_72d45ee78666ea32\gdiplus.dll
LoadedModule[221]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\46957030830964165644b52b0696c5d9\System.Configuration.ni.dll
LoadedModule[222]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Xml\d86b080a37c60a872c82b912a2a63dac\System.Xml.ni.dll
LoadedModule[223]=C:\Windows\assembly\NativeImages_v4.0.30319_32\PresentationUI\8fbd1dea7ca316116350b759a16b34e8\PresentationUI.ni.dll
LoadedModule[224]=C:\Windows\system32\mscms.dll
LoadedModule[225]=C:\Windows\system32\WindowsCodecsExt.dll
LoadedModule[226]=C:\Windows\system32\icm32.dll
LoadedModule[227]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Web\14da86a7ddbf09bd27b30061ff9a4f5e\System.Web.ni.dll
LoadedModule[228]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\webengine4.dll
LoadedModule[229]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Presentatio49d6fefe#\33d15f16d20849f7c46d19b7bc7f4273\PresentationFramework-SystemXml.ni.dll
LoadedModule[230]=C:\Windows\assembly\NativeImages_v4.0.30319_32\UIAutomationTypes\7e77d1835b49fa80598b5c47eaedccfc\UIAutomationTypes.ni.dll
LoadedModule[231]=C:\Windows\system32\UIAutomationCore.dll
LoadedModule[232]=C:\Windows\system32\msctfui.dll
LoadedModule[233]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Runteb92aa12#\c56771a9cfb87e660d60453e232abe27\System.Runtime.Serialization.ni.dll
LoadedModule[234]=C:\Windows\assembly\NativeImages_v4.0.30319_32\SMDiagnostics\4a2a848ea1fea1a74d5aa2f1c21c5ce8\SMDiagnostics.ni.dll
LoadedModule[235]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Servd1dec626#\52e9ac689c75dd011f0f7e827551e985\System.ServiceModel.Internals.ni.dll
LoadedModule[236]=C:\Windows\assembly\NativeImages_v4.0.30319_32\UIAutomationProvider\419dd31edfefd1c8923b38e8c9ce3e89\UIAutomationProvider.ni.dll
LoadedModule[237]=C:\Windows\system32\SXS.DLL
LoadedModule[238]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Accessibility\44a4ab91e8e11c7cb95343e2d9ffe621\Accessibility.ni.dll
LoadedModule[239]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Presentatio84a6349c#\f0a755350257889ec7e0559c4dbfc30a\PresentationFramework-SystemCore.ni.dll
LoadedModule[240]=C:\Program Files (x86)\EZCA\ezcacontrol.dll
LoadedModule[241]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Gauges\PMDG_737NGX.dll
LoadedModule[242]=C:\Windows\system32\NETAPI32.dll
LoadedModule[243]=C:\Windows\system32\wkscli.dll
LoadedModule[244]=C:\Windows\system32\WSOCK32.dll
LoadedModule[245]=C:\Windows\SysWow64\XAudio2_7.dll
LoadedModule[246]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Gauges\FSFX\737\fsfx_RealEffects_1.dll
LoadedModule[247]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Gauges\PMDG_737NGX_2.dll
LoadedModule[248]=C:\Windows\system32\snmpapi.dll
LoadedModule[249]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[250]=C:\Windows\system32\napinsp.dll
LoadedModule[251]=C:\Windows\system32\pnrpnsp.dll
LoadedModule[252]=C:\Windows\System32\winrnr.dll
LoadedModule[253]=C:\Windows\system32\icmp.Dll
LoadedModule[254]=C:\Windows\system32\msadp32.acm
LoadedModule[255]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[256]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[257]=C:\Windows\SysWOW64\mshtml.dll
Sec[0].Key=LCID
Sec[0].Value=1033
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=534810104/nBucketTable=25/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Lockheed Martin® Prepar3D®
AppPath=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe

 

BOBSK8             MSFS 2020 ,    ,PMDG 737-600-800 ,  FSLTL , TrackIR ,  Avliasoft EFB2  ,  ATC  by PF3  ,

A Pilots LIfe V2 ,  CLX PC , Auto FPS, ACTIVE Sky FS,  PMDG DC6 , A2A Comanche, Fenix A320, Milviz C 310

 

Share this post

Link to post
Share on other sites

Jim Young    2,356

Jim Young
Posted

 

 


I haven't had any crashes of P3D, until the last couple of weeks, where I have had 4. Never had a crash of Version 2.5 or Version 3, only 3.1. Today I have had 2 consecutive flights crash from about 45 minutes to 1 1/2 hours. haven't changed anything in my system. here is the error log I got. Nothing overclocked, Windows 7, P3D settings all on medium, and have not been changed in months. Any ideas, anyone.

 

LOL!  Thanks for reading my suggestions for fixing this problem.  I'm sorry I set you off with my suggestions to the OP above.  When you get a crash like the ntdll.dll, it is very frustrating as I have experienced them many times in the past (but not any this year - knock on wood). An ntdll.dll crash is sometimes followed with a StackHash and then back to the ntdll.dll error.  You cover all  of my suggestions except you forgot to say you rebuilt your P3D config, moved your dll.xml and scenery.cfg to a temporary folder and the ntdll.dll crashes still occur.  When you first install FSX or P3D or FSX-SE, it runs well without any addons or eye-candy, then you add the addons and everything goes to heck after that.  You also forgot to state you don't have any products installed that were not made for P3Dv3 and you used the EMT and/or jerry rigged the "compatible" products into P3Dv3. I can see where a couple of the products that loaded in your report were not made fully compatible with the latest version of P3Dv3.1 and you had to manually install them.  You have to remove those products first as LM does not support many old addons.  Even if you only had products that are considered fully compatible by LM for installation in their product, like the PMDG aircraft, FSDT/Flightbeam airports, etc., it does not mean there are not bugs in those products which are triggering the ntdll.dll error.  That's why I recommend in the CTD Guide that you move your p3d.cfg, dll.xml, exe.xml (if you have one), and the scenery.cfg to a temporary folder and see if this fixes your problem and this basically brings P3D installation back to the default.  There is no known solution to the ntdll.dll error.  There are just too many possibilities and each individual has to investigate their own "crime scene".  If it was all because of, say, the bufferpools tweak, that would be too easy.  Not even Microsoft techs or the greatest computer expert in the Universe can explain exactly why you got your crash(es).  They have to be investigated.  It could be permissions, a bad config, your Windows installation... well, almost anything.

 

To further explain some of my comments above, did you know that P3Dv3 is a complete update from P3Dv2?  It's like going from FS9 to FSX or FS2K2 to FS2K4 (FS9).  It has some new coding to make it perform better.  That's why a lot of members are staying with the old P3D simulator (v2.5) just like those who own FS9 and not upgrading to FSX/FSX-SE.  In two years they will have another P3Dv4 and two years down the road from that a version 5 and even more things we own today will not work in those versions.  Microsoft was doing the same thing with their flight simulator program by releasing FS2000, then FS2002, then FS2004, and then FSX.  If the Microsoft team had stayed in existence, one wonders what the next version of FSX would have been called but I expect whatever the name, it would have been similar to the special coding in P3D (that is still based off the old FSX coding).  Expect to see the same types of updates with P3D with each major version update costing the same as version 1, 2, or version 3 (maybe even higher).

 

Hope you can diagnose and find the solution to your problem.  I provided some recommendations for troubleshooting in the AVSIM CTD Guide, you just need to explore those suggestions to fix your problem.

 

Best regards,

Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post

Link to post
Share on other sites

Bobsk8    12,679

Bobsk8
Posted

LOL!  Thanks for reading my suggestions for fixing this problem.  I'm sorry I set you off with my suggestions to the OP above.  When you get a crash like the ntdll.dll, it is very frustrating as I have experienced them many times in the past (but not any this year - knock on wood). An ntdll.dll crash is sometimes followed with a StackHash and then back to the ntdll.dll error.  You cover all  of my suggestions except you forgot to say you rebuilt your P3D config, moved your dll.xml and scenery.cfg to a temporary folder and the ntdll.dll crashes still occur.  When you first install FSX or P3D or FSX-SE, it runs well without any addons or eye-candy, then you add the addons and everything goes to heck after that.  You also forgot to state you don't have any products installed that were not made for P3Dv3 and you used the EMT and/or jerry rigged the "compatible" products into P3Dv3. I can see where a couple of the products that loaded in your report were not made fully compatible with the latest version of P3Dv3.1 and you had to manually install them.  You have to remove those products first as LM does not support many old addons.  Even if you only had products that are considered fully compatible by LM for installation in their product, like the PMDG aircraft, FSDT/Flightbeam airports, etc., it does not mean there are not bugs in those products which are triggering the ntdll.dll error.  That's why I recommend in the CTD Guide that you move your p3d.cfg, dll.xml, exe.xml (if you have one), and the scenery.cfg to a temporary folder and see if this fixes your problem and this basically brings P3D installation back to the default.  There is no known solution to the ntdll.dll error.  There are just too many possibilities and each individual has to investigate their own "crime scene".  If it was all because of, say, the bufferpools tweak, that would be too easy.  Not even Microsoft techs or the greatest computer expert in the Universe can explain exactly why you got your crash(es).  They have to be investigated.  It could be permissions, a bad config, your Windows installation... well, almost anything.

 

To further explain some of my comments above, did you know that P3Dv3 is a complete update from P3Dv2?  It's like going from FS9 to FSX or FS2K2 to FS2K4 (FS9).  It has some new coding to make it perform better.  That's why a lot of members are staying with the old P3D simulator (v2.5) just like those who own FS9 and not upgrading to FSX/FSX-SE.  In two years they will have another P3Dv4 and two years down the road from that a version 5 and even more things we own today will not work in those versions.  Microsoft was doing the same thing with their flight simulator program by releasing FS2000, then FS2002, then FS2004, and then FSX.  If the Microsoft team had stayed in existence, one wonders what the next version of FSX would have been called but I expect whatever the name, it would have been similar to the special coding in P3D (that is still based off the old FSX coding).  Expect to see the same types of updates with P3D with each major version update costing the same as version 1, 2, or version 3 (maybe even higher).

 

Hope you can diagnose and find the solution to your problem.  I provided some recommendations for troubleshooting in the AVSIM CTD Guide, you just need to explore those suggestions to fix your problem.

 

Best regards,

 

Hi Jim,

 

First, thanks for the detailed response. I have had version 3.1 since about 1 week after it was released, just installing the client. The only add ons I have installed in V3 and V3.1 are add ons that had a regular P3D V3 installers, other than Ezdok. No migration tool installs, or non P3D V3 content. As I said, I had 2 of these crashes yesterday, and one other a few days ago, and that was it. Probably have 70 or more flights on 3.1 with zero problems.  The only thing I did differently in the last couple of days , was I started using the engine anti ice settings on the PMDG 737 ( which is the only thing I am flying now for a VA). I did not turn the anti ice on today, and completed a two hour flight with no problems. I am wondering if something as simple as that could have caused this problem. Will experiment some more with it.. 

 

BOBSK8             MSFS 2020 ,    ,PMDG 737-600-800 ,  FSLTL , TrackIR ,  Avliasoft EFB2  ,  ATC  by PF3  ,

A Pilots LIfe V2 ,  CLX PC , Auto FPS, ACTIVE Sky FS,  PMDG DC6 , A2A Comanche, Fenix A320, Milviz C 310

 

Share this post

Link to post
Share on other sites

Jim Young    2,356

Jim Young
Posted

 

 


I did not turn the anti ice on today, and completed a two hour flight with no problems. I am wondering if something as simple as that could have caused this problem. Will experiment some more with it..

 

I think that's likely Bob.  I have been reading that version 3.1 has a lot of "bugs" (not really but the coding was changed in some areas to make a function work better) and these "bugs" are popping up.  Still not LM's problem but the developer of the addon to update his product to the new code.  Someone told me the other day that PMDG may delay the release of the 747 as they found more "bugs" in the latest version of P3D.  It will be good for us if the developers of our addons discover these new functions or changes in functions and update their respective products.

 

Best regards,

Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post

Link to post
Share on other sites

Bobsk8    12,679

Bobsk8
Posted

I think that's likely Bob.  I have been reading that version 3.1 has a lot of "bugs" (not really but the coding was changed in some areas to make a function work better) and these "bugs" are popping up.  Still not LM's problem but the developer of the addon to update his product to the new code.  Someone told me the other day that PMDG may delay the release of the 747 as they found more "bugs" in the latest version of P3D.  It will be good for us if the developers of our addons discover these new functions or changes in functions and update their respective products.

 

Best regards,

 

Well I have completed three flights after not setting anti ice, and everything seems to be working perfectly again.   Go figure...... :fool:

 

BOBSK8             MSFS 2020 ,    ,PMDG 737-600-800 ,  FSLTL , TrackIR ,  Avliasoft EFB2  ,  ATC  by PF3  ,

A Pilots LIfe V2 ,  CLX PC , Auto FPS, ACTIVE Sky FS,  PMDG DC6 , A2A Comanche, Fenix A320, Milviz C 310

 

Share this post

Link to post
Share on other sites

Jim Young    2,356

Jim Young
Posted

That's great!  I wonder if that's a gauge that needs permission?  In any case, your fix may help many others and is appreciated.

 

Best regards,

  • Upvote 1

Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post

Link to post
Share on other sites

Bobsk8    12,679

Bobsk8
Posted

Been doing a great deal of research on this issue of CTD's with P3D. There are many complaints on the P3D Facebook page, and the P3D forum,  of users experiencing CTDs, most of them mid flight. This is a recent complaint regarding P3D. One of the reasons I was attracted to P3D was its stability which was unlike what I had experienced with MSFS for years, which finally convinced me to give up sim flying altogether for about 6 years. Now with the latest version of P3D, version 3.1, it looks like they fixed what wasn't broken, and broke it. 

 

I spent my entire working career training techs how to troubleshoot complex electronic gear, so trying to solve an  issue like this is something that I have done before. In reading the different posts on Facebook and two forums, I was looking for a common denominator in these crashes. I mentioned on Facebook about my engine de ice theory with the NGX, and two people say they never use the engine de ice but get CTDs. Some folks have suggested a recent update of My Traffic as a cause, but several other people say that they don't use My Traffic. Another theory is GSX and FS2 Crew could be causing the problem, but not everyone seems to use those add ons either.  The common denominator that I have come up with in every instance  is P3D V3.1 and PMDG products, almost always mentioned and the NGX in particular. Two users have had so many CTDs mid flight  that they have stopped flying P3D altogether. Everyone that seems to be experiencing this CTD mid flight, some with this NTDll. Dll error pointed out, are using V3.1 and the NGX. I am wondering if something that they did with V3.1 caused a problem with the NGX, which is causing these CTDs and since it is so intermittent, PMDG didn't spot it when testing with V3.1.  This issue has just started to surface in the last couple of weeks, which timing coincides with the release of V 3.1. 

 

BOBSK8             MSFS 2020 ,    ,PMDG 737-600-800 ,  FSLTL , TrackIR ,  Avliasoft EFB2  ,  ATC  by PF3  ,

A Pilots LIfe V2 ,  CLX PC , Auto FPS, ACTIVE Sky FS,  PMDG DC6 , A2A Comanche, Fenix A320, Milviz C 310

 

Share this post

Link to post
Share on other sites

newtie    533

newtie
Posted

Hi Bob-

 

I too have had successive CTDs in the last two weeks after a long time of no problems at all.

 

Here's what has stopped it, at least for the four or five flights I've done after doing this.

 

Go here and follow the directions. I was missing CR and LF characters.

 

Then, go here and run this. I had several corrupted system files, some fixed by the app, others it could not.

 

I know correlation does not equal causation, but this seems to be working, at least for the time being.

 

Cheers,

Mark

Share this post

Link to post
Share on other sites

Swe_Richard    1,172

Swe_Richard
Posted

Hmm.. I seem to be becoming a regular nowadays in this ntdll.dll club as well. I've had three crashes the last couple of weeks. I fail to see a pattern in it. I think the first two were when I was using the CS l1011 and the latest was when using the Majestic Q400 Pro. I'm always using ASN. 

 

This is highly annoying.

Richard

7950x3d   |   32Gb 6000mHz RAM   |   8Tb NVme   |   RTX 4090    |    MSFS    |    P3D    |      XP12  

Share this post

Link to post
Share on other sites

SteveW    1,792

SteveW
Posted

Well I have completed three flights after not setting anti ice, and everything seems to be working perfectly again.   Go figure...... :fool:

Ice = weather = metars. Have you tried another weather system Bob? If not you could try a weather theme with anti-ice.

Steve Waite: Engineer at codelegend.com

Share this post

Link to post
Share on other sites

Guest JustanotherPilot   

Guest JustanotherPilot
Posted

Been doing a great deal of research on this issue of CTD's with P3D. There are many complaints on the P3D Facebook page, and the P3D forum,  of users experiencing CTDs, most of them mid flight. This is a recent complaint regarding P3D. One of the reasons I was attracted to P3D was its stability which was unlike what I had experienced with MSFS for years, which finally convinced me to give up sim flying altogether for about 6 years. Now with the latest version of P3D, version 3.1, it looks like they fixed what wasn't broken, and broke it. 

 

I spent my entire working career training techs how to troubleshoot complex electronic gear, so trying to solve an  issue like this is something that I have done before. In reading the different posts on Facebook and two forums, I was looking for a common denominator in these crashes. I mentioned on Facebook about my engine de ice theory with the NGX, and two people say they never use the engine de ice but get CTDs. Some folks have suggested a recent update of My Traffic as a cause, but several other people say that they don't use My Traffic. Another theory is GSX and FS2 Crew could be causing the problem, but not everyone seems to use those add ons either.  The common denominator that I have come up with in every instance  is P3D V3.1 and PMDG products, almost always mentioned and the NGX in particular. Two users have had so many CTDs mid flight  that they have stopped flying P3D altogether. Everyone that seems to be experiencing this CTD mid flight, some with this NTDll. Dll error pointed out, are using V3.1 and the NGX. I am wondering if something that they did with V3.1 caused a problem with the NGX, which is causing these CTDs and since it is so intermittent, PMDG didn't spot it when testing with V3.1.  This issue has just started to surface in the last couple of weeks, which timing coincides with the release of V 3.1.

 

Bob,

 

Agree with what you say but I get the CTD using As Airbus and Majestic Q400. I found that I can sometimes complete a flight of an hour duration in the AS A320 if I turn off HDR. Very disappointed with 3.1. It promised bells and whistles but delivered smoke and mirrors.

Share this post

Link to post
Share on other sites

Bobsk8    12,679

Bobsk8
Posted

Bob,

 

Agree with what you say but I get the CTD using As Airbus and Majestic Q400. I found that I can sometimes complete a flight of an hour duration in the AS A320 if I turn off HDR. Very disappointed with 3.1. It promised bells and whistles but delivered smoke and mirrors.

 

I think that P3D has put a bug in 3.1 that they do not want to admit. There are several posting on their forum regarding this issue, and they have not addressed any of them. Also there are many people on the P3D Facebook groups that are reporting the same mid flight crash problem of V 3.1. This all started a couple of weeks ago,. 

 

BOBSK8             MSFS 2020 ,    ,PMDG 737-600-800 ,  FSLTL , TrackIR ,  Avliasoft EFB2  ,  ATC  by PF3  ,

A Pilots LIfe V2 ,  CLX PC , Auto FPS, ACTIVE Sky FS,  PMDG DC6 , A2A Comanche, Fenix A320, Milviz C 310

 

Share this post

Link to post
Share on other sites

jeff974cd    9

jeff974cd
Posted

i ve also been experiencing several mid flight CTD with P3D V3.1. don't remember having any of this with 2.3 >>2.5

Hope it will be fixed in a patch.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0
Go To Topic Listing

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...