May 11, 201610 yr Hello All, Sadly P3d has started crashing on me. It looks to me like it's the NTDLL? From the CTD guide it seems like that could be linked to MyTraffic or the Nvidia update i did recently. I might try disabling/rolling back drivers, but first I thought I'd post here to see if anyone had any other advice. Version=1 EventType=APPCRASH EventTime=131074395467533782 ReportType=2 Consent=1 UploadTime=131074395468054510 ReportIdentifier=1aa28ab5-176b-11e6-9de0-086266c7335c IntegratorReportIdentifier=3873a94d-13f7-4459-b0c4-a981dcaf79db WOW64=1 NsAppName=Prepar3D.exe Response.BucketId=0d18a56bcac57202ecfb218dd3f8b434 Response.BucketTable=1 Response.LegacyBucketId=108152535621 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=Prepar3D.exe Sig[1].Name=Application Version Sig[1].Value=3.2.3.16769 Sig[2].Name=Application Timestamp Sig[2].Value=56df48ce Sig[3].Name=Fault Module Name Sig[3].Value=StackHash_06da Sig[4].Name=Fault Module Version Sig[4].Value=10.0.10586.306 Sig[5].Name=Fault Module Timestamp Sig[5].Value=571afb7f Sig[6].Name=Exception Code Sig[6].Value=c0000374 Sig[7].Name=Exception Offset Sig[7].Value=PCH_EE_FROM_ntdll+0x0007718C DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.10586.2.0.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=06da DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=06daf0724672ff2684cf85e8c564a421 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=6363 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=6363adba2195548094aad21393c71870 UI[2]=H:\P3D\Prepar3D.exe UI[3]=Prepar3D exe has stopped working 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]=H:\P3D\Prepar3D.exe LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll LoadedModule[2]=C:\Windows\SYSTEM32\KERNEL32.DLL LoadedModule[3]=C:\Windows\SYSTEM32\KERNELBASE.dll LoadedModule[4]=C:\Windows\SYSTEM32\USER32.dll LoadedModule[5]=C:\Windows\SYSTEM32\GDI32.dll LoadedModule[6]=C:\Windows\SYSTEM32\ole32.dll LoadedModule[7]=C:\Windows\SYSTEM32\combase.dll LoadedModule[8]=C:\Windows\SYSTEM32\msvcrt.dll LoadedModule[9]=C:\Windows\SYSTEM32\RPCRT4.dll LoadedModule[10]=C:\Windows\SYSTEM32\SspiCli.dll LoadedModule[11]=C:\Windows\SYSTEM32\CRYPTBASE.dll LoadedModule[12]=C:\Windows\SYSTEM32\bcryptPrimitives.dll LoadedModule[13]=C:\Windows\SYSTEM32\sechost.dll LoadedModule[14]=H:\P3D\api.dll LoadedModule[15]=C:\Windows\SYSTEM32\MSVCP120.dll LoadedModule[16]=C:\Windows\SYSTEM32\MSVCR120.dll LoadedModule[17]=C:\Windows\SYSTEM32\MSWSOCK.dll LoadedModule[18]=C:\Windows\SYSTEM32\Cabinet.dll LoadedModule[19]=C:\Windows\SYSTEM32\IMM32.dll LoadedModule[20]=C:\Windows\SYSTEM32\WS2_32.dll LoadedModule[21]=C:\Windows\SYSTEM32\ADVAPI32.dll LoadedModule[22]=C:\Windows\SYSTEM32\SHELL32.dll LoadedModule[23]=C:\Windows\SYSTEM32\WINHTTP.dll LoadedModule[24]=C:\Windows\SYSTEM32\cfgmgr32.dll LoadedModule[25]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.10586.0_none_811bc0006c44242b\COMCTL32.dll LoadedModule[26]=C:\Windows\SYSTEM32\windows.storage.dll LoadedModule[27]=C:\Windows\SYSTEM32\WINMM.dll LoadedModule[28]=C:\Windows\SYSTEM32\VERSION.dll LoadedModule[29]=C:\Windows\SYSTEM32\shlwapi.dll LoadedModule[30]=C:\Windows\SYSTEM32\kernel.appcore.dll LoadedModule[31]=C:\Windows\SYSTEM32\shcore.dll LoadedModule[32]=C:\Windows\SYSTEM32\powrprof.dll LoadedModule[33]=C:\Windows\SYSTEM32\profapi.dll LoadedModule[34]=C:\Windows\SYSTEM32\WINMMBASE.dll LoadedModule[35]=C:\Windows\SYSTEM32\CRYPT32.dll LoadedModule[36]=C:\Windows\SYSTEM32\MSASN1.dll LoadedModule[37]=H:\P3D\acontain.dll LoadedModule[38]=H:\P3D\ai_player.dll LoadedModule[39]=H:\P3D\atc.dll LoadedModule[40]=H:\P3D\controls.dll LoadedModule[41]=H:\P3D\demo.dll LoadedModule[42]=H:\P3D\DIS.dll LoadedModule[43]=H:\P3D\facilities.dll LoadedModule[44]=H:\P3D\fe.dll LoadedModule[45]=C:\Windows\SYSTEM32\SETUPAPI.dll LoadedModule[46]=C:\Windows\SYSTEM32\OLEAUT32.dll LoadedModule[47]=H:\P3D\flight.dll LoadedModule[48]=H:\P3D\fs-traffic.dll LoadedModule[49]=H:\P3D\g2d.dll LoadedModule[50]=H:\P3D\g3d.dll LoadedModule[51]=C:\Windows\SYSTEM32\WLDAP32.dll LoadedModule[52]=H:\P3D\gps.dll LoadedModule[53]=H:\P3D\livingwater.dll LoadedModule[54]=H:\P3D\main.dll LoadedModule[55]=H:\P3D\menus.dll LoadedModule[56]=H:\P3D\multiplayer.dll LoadedModule[57]=C:\Windows\SYSTEM32\COMDLG32.dll LoadedModule[58]=C:\Windows\SYSTEM32\FirewallAPI.dll LoadedModule[59]=C:\Windows\SYSTEM32\NETAPI32.dll LoadedModule[60]=H:\P3D\pdk.dll LoadedModule[61]=H:\P3D\panels.dll LoadedModule[62]=H:\P3D\sim1.dll LoadedModule[63]=H:\P3D\simscheduler.dll LoadedModule[64]=H:\P3D\simprop.dll LoadedModule[65]=H:\P3D\sound.dll LoadedModule[66]=H:\P3D\symmap.dll LoadedModule[67]=H:\P3D\terrain.dll LoadedModule[68]=H:\P3D\util.dll LoadedModule[69]=H:\P3D\visualfx.dll LoadedModule[70]=H:\P3D\weather.dll LoadedModule[71]=H:\P3D\window.dll LoadedModule[72]=C:\Windows\SYSTEM32\HID.DLL LoadedModule[73]=C:\Windows\SYSTEM32\USERENV.dll LoadedModule[74]=C:\Windows\SYSTEM32\dxgi.dll LoadedModule[75]=C:\Windows\SYSTEM32\d3d9.dll LoadedModule[76]=C:\Windows\SYSTEM32\d3d11.dll LoadedModule[77]=C:\Windows\SYSTEM32\D3DCOMPILER_43.dll LoadedModule[78]=C:\Windows\SYSTEM32\OPENGL32.dll LoadedModule[79]=C:\Windows\SYSTEM32\GLU32.dll LoadedModule[80]=C:\Windows\SYSTEM32\d3dx9_43.dll LoadedModule[81]=C:\Windows\SYSTEM32\d3dx11_43.dll LoadedModule[82]=C:\Windows\SYSTEM32\DSOUND.dll LoadedModule[83]=H:\P3D\audiere.dll LoadedModule[84]=C:\Windows\SYSTEM32\MSACM32.dll LoadedModule[85]=C:\Windows\SYSTEM32\dwmapi.dll LoadedModule[86]=C:\Windows\SYSTEM32\DDRAW.dll LoadedModule[87]=C:\Windows\SYSTEM32\DAVHLPR.DLL LoadedModule[88]=C:\Windows\SYSTEM32\DCIMAN32.dll LoadedModule[89]=C:\Windows\SYSTEM32\fwbase.dll LoadedModule[90]=H:\P3D\language.dll LoadedModule[91]=C:\Windows\system32\uxtheme.dll LoadedModule[92]=C:\Windows\SYSTEM32\MSXML6.DLL LoadedModule[93]=C:\Windows\SYSTEM32\ntmarta.dll LoadedModule[94]=C:\Windows\SYSTEM32\PROPSYS.dll LoadedModule[95]=H:\P3D\uiInterface.dll LoadedModule[96]=C:\Windows\SYSTEM32\mscoree.dll LoadedModule[97]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll LoadedModule[98]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll LoadedModule[99]=C:\Windows\SYSTEM32\MSVCR120_CLR0400.dll LoadedModule[100]=C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\b1ea5171f48fa1865ea45dd904735573\mscorlib.ni.dll LoadedModule[101]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll LoadedModule[102]=C:\Windows\SYSTEM32\CRYPTSP.dll LoadedModule[103]=C:\Windows\system32\rsaenh.dll LoadedModule[104]=C:\Windows\SYSTEM32\bcrypt.dll LoadedModule[105]=C:\Windows\SYSTEM32\dwrite.dll LoadedModule[106]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll LoadedModule[107]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationNative_v0400.dll LoadedModule[108]=C:\Windows\SYSTEM32\iphlpapi.dll LoadedModule[109]=C:\Windows\SYSTEM32\NSI.dll LoadedModule[110]=C:\Windows\SYSTEM32\dhcpcsvc6.DLL LoadedModule[111]=C:\Windows\SYSTEM32\dhcpcsvc.DLL LoadedModule[112]=C:\Windows\SYSTEM32\ondemandconnroutehelper.dll LoadedModule[113]=C:\Windows\SYSTEM32\NETUTILS.DLL LoadedModule[114]=C:\Windows\SYSTEM32\wkscli.dll LoadedModule[115]=C:\Windows\SYSTEM32\srvcli.dll LoadedModule[116]=C:\Windows\SYSTEM32\secur32.dll LoadedModule[117]=C:\Windows\SYSTEM32\DNSAPI.dll LoadedModule[118]=C:\Windows\System32\fwpuclnt.dll LoadedModule[119]=C:\Windows\System32\rasadhlp.dll LoadedModule[120]=C:\Windows\SYSTEM32\MSCTF.dll LoadedModule[121]=C:\Windows\system32\nvapi.dll LoadedModule[122]=C:\Windows\SYSTEM32\nvwgf2um.dll LoadedModule[123]=C:\Windows\system32\nvspcap.dll LoadedModule[124]=C:\Windows\SYSTEM32\PSAPI.DLL LoadedModule[125]=C:\Windows\SYSTEM32\WTSAPI32.DLL LoadedModule[126]=C:\Windows\SYSTEM32\WINSTA.dll LoadedModule[127]=C:\Windows\SYSTEM32\clbcatq.dll LoadedModule[128]=C:\Windows\SYSTEM32\apphelp.dll LoadedModule[129]=C:\Windows\system32\ntshrui.dll LoadedModule[130]=C:\Windows\SYSTEM32\cscapi.dll LoadedModule[131]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10586.0_none_d3c2e4e965da4528\comctl32.dll LoadedModule[132]=C:\Windows\SYSTEM32\coml2.dll LoadedModule[133]=C:\Windows\SYSTEM32\LINKINFO.dll LoadedModule[134]=C:\Windows\System32\MMDevApi.dll LoadedModule[135]=C:\Windows\System32\DEVOBJ.dll LoadedModule[136]=C:\Windows\SYSTEM32\AUDIOSES.DLL LoadedModule[137]=C:\Windows\SYSTEM32\wintypes.dll LoadedModule[138]=C:\Windows\SYSTEM32\XInput9_1_0.dll LoadedModule[139]=C:\Windows\SYSTEM32\urlmon.dll LoadedModule[140]=C:\Windows\SYSTEM32\iertutil.dll LoadedModule[141]=C:\Windows\SYSTEM32\WindowsCodecs.dll LoadedModule[142]=C:\Windows\SYSTEM32\nvd3dum.dll LoadedModule[143]=C:\Windows\SYSTEM32\wdmaud.drv LoadedModule[144]=C:\Windows\SYSTEM32\ksuser.dll LoadedModule[145]=C:\Windows\SYSTEM32\AVRT.dll LoadedModule[146]=C:\Windows\SYSTEM32\msacm32.drv LoadedModule[147]=C:\Windows\SYSTEM32\midimap.dll LoadedModule[148]=H:\P3D\radar.dll LoadedModule[149]=H:\P3D\D3DCOMPILER_47.dll LoadedModule[150]=H:\P3D\Oculus.dll LoadedModule[151]=C:\Windows\SYSTEM32\dbghelp.dll LoadedModule[152]=H:\P3D\ControllableCamera.dll LoadedModule[153]=H:\P3D\Gauges\TargetInfo.dll LoadedModule[154]=H:\P3D\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll LoadedModule[155]=C:\Windows\SYSTEM32\WINSPOOL.DRV LoadedModule[156]=C:\Windows\SYSTEM32\WININET.dll LoadedModule[157]=C:\Windows\SYSTEM32\WINNSI.DLL LoadedModule[158]=H:\P3D\Modules\FSUIPC4.dll LoadedModule[159]=C:\Windows\SYSTEM32\DINPUT8.dll LoadedModule[160]=C:\Windows\SYSTEM32\SHFolder.DLL LoadedModule[161]=H:\P3D\Modules\SimConnectP3D3.dll LoadedModule[162]=C:\Windows\SYSTEM32\DINPUT.DLL LoadedModule[163]=C:\Windows\SYSTEM32\WINTRUST.dll LoadedModule[164]=H:\P3D\as_srv\as_btstrp.dll LoadedModule[165]=C:\Windows\winsxs\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[166]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9193_none_d09188224426efcd\MSVCR80.dll LoadedModule[167]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9193_none_d09188224426efcd\MSVCP80.dll LoadedModule[168]=H:\P3D\SimDirector.dll LoadedModule[169]=H:\P3D\BGLCompLib.dll LoadedModule[170]=H:\P3D\simpropext.dll LoadedModule[171]=C:\Windows\SYSTEM32\XInput1_4.dll LoadedModule[172]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[173]=C:\Windows\SYSTEM32\wbemcomn.dll LoadedModule[174]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[175]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[176]=C:\Windows\SYSTEM32\mscms.dll LoadedModule[177]=C:\Windows\SYSTEM32\WindowsCodecsExt.dll LoadedModule[178]=C:\Windows\SYSTEM32\icm32.dll LoadedModule[179]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\webengine4.dll LoadedModule[180]=C:\Windows\SYSTEM32\UIAutomationCore.dll LoadedModule[181]=C:\Windows\SYSTEM32\sxs.dll LoadedModule[182]=C:\Windows\system32\dataexchange.dll LoadedModule[183]=C:\Windows\system32\dcomp.dll LoadedModule[184]=C:\Windows\system32\twinapi.appcore.dll LoadedModule[185]=C:\Windows\system32\msctfui.dll LoadedModule[186]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.10586.20_none_22adb5eaa762c7fa\gdiplus.dll LoadedModule[187]=H:\P3D\Gauges\C18525.gau LoadedModule[188]=C:\Windows\SYSTEM32\msadp32.acm LoadedModule[189]=C:\Windows\SYSTEM32\ieframe.dll LoadedModule[190]=C:\Windows\SYSTEM32\mshtml.dll LoadedModule[191]=C:\Windows\SYSTEM32\srpapi.dll LoadedModule[192]=C:\Windows\System32\vaultcli.dll LoadedModule[193]=C:\Windows\SYSTEM32\MLANG.dll LoadedModule[194]=C:\Windows\SYSTEM32\edputil.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Prepar3D exe AppPath=H:\P3D\Prepar3D.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=9CEA1B3466F160E2F0D6777C43443EF6
May 11, 201610 yr Take the path of least resistance right now. Roll back your gpu drivers to an older version. Many people, including myself, have had success with using the 361.XX series of drivers. See if after the rollback, P3D works right. Engage, research, inform and make your posts count! -Jim Morvay Origin EON-17SLX - Under the hood: Intel Core i7 7700K at 4.2GHz (Base) 4.6GHz (overclock), nVidia GeForce GTX-1080 Pascal w/8gb vram, 32gb (2x16) Crucial 2400mhz RAM, 3840 x 2160 17.3" IPS w/G-SYNC, Samsung 950 EVO 256GB PCIe m.2 SSD (Primary), Samsung 850 EVO 500gb M.2 (Sim Drive), MS Windows 10 Professional 64-Bit
May 11, 201610 yr Start by renaming this My T 6 file: <drive:>\MyTraffic Professional\MyTraffic\Scenery\Mytrafficmil.bgl to MyTrafficmil.bgl.orig See if this stops the ntdll.dll errors. Some people have had some luck with this approach, which disables the military traffic.
May 27, 201610 yr Confirmed, removing the military traffic bgl worked This was posted on the My Traffic forum months ago.
May 27, 201610 yr I can also confirm, the mil traffic was causing me crashes as well. <p>Dassault Falcon, Lear, Embraer and Challenger and Cessna Mechanic.Broadcasting live from former Soviet Missile Silo.Rhys Legge
May 27, 201610 yr This is absolutely a strange fix for me as I have had MyTraffic6 since Day 1 and have never had a crash related to MyTraffic6's military traffic file. I have the default schedules and have never ever modified or updated them. I'm wondering if those who get this crash updated the flight plan schedules that are offered on the site. This might be the reason why the crash occurs for some but not all, like me. One of the nice things about MyTraffic6 was the ability to have military AI aircraft at military bases and flying around the world. I do not think any other AI program offered this feature. I know in the previous version (MyTrafficX), installing the 2012 or 2013 schedules caused the ntdll.dll error too. I think there was an error in one of the flight schedules where the flightplan was there but the AI aircraft was not available or installed. Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant 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
May 27, 201610 yr Jim, I've had this problem with MT6 and never changed the default traffic schedules. It has only occurred in the Los Angeles area. Earlier this week my sim repeatedly crashed with an ntdll.dll error while trying to load a flight KLAX. I added .passive to the end of the military traffic bgl and the flight loaded with no other problems. I had the same issue with My Traffic 5.4c but in that case I reverted back to version 5.4b to stop the crashes. I've also found that setting airline traffic to zero stops the crashes, but then of course you have no traffic. It is just a quick and easy thing to try for troubleshooting purposes. Ted [email protected] ghz, Noctua C12P CPU air cooler, Asus Z77, 2 x 4gb DDR3 Corsair 2200 mhz cl 9, EVGA 1080ti, Sony 55" 900E TV 3840 x 2160, Windows 7-64, FSX, P3dv3, P3dv4
May 27, 201610 yr Jim, Burkhard Renk, the developer has recommended this fix (renaming the military BGL file to .old) on the official MyT 6 forum, until a permanent solution can be found. The error is not that common, but I can reproduce it. I'm also curious about how many people that have seen the error are also using the Air Traffic Manager app. Jay
May 27, 201610 yr Jim, I've had this problem with MT6 and never changed the default traffic schedules. It has only occurred in the Los Angeles area. Earlier this week my sim repeatedly crashed with an ntdll.dll error while trying to load a flight KLAX. I added .passive to the end of the military traffic bgl and the flight loaded with no other problems. I had the same issue with My Traffic 5.4c but in that case I reverted back to version 5.4b to stop the crashes. I've also found that setting airline traffic to zero stops the crashes, but then of course you have no traffic. It is just a quick and easy thing to try for troubleshooting purposes. Ted Jim, Burkhard Renk, the developer has recommended this fix (renaming the military BGL file to .old) on the official MyT 6 forum, until a permanent solution can be found. The error is not that common, but I can reproduce it. I'm also curious about how many people that have seen the error are also using the Air Traffic Manager app. Jay Hi Ted and Jay, I understand what you are saying. Still it does not answer the question, "why doesn't it happen to little ole me" or "why isn't it happening to everyone who owns this popular AI program?" One possibility is it reduces the amount of resources being taken on a system and, when you are in an area where there are a lot of eye-candy or you have been flying for some period of time reducing the amount of VAS available. It could be happening in the same location for everyone. I do know for a fact, in the previous version (MyTrafficX), it involved an AI flight schedule as I was using the 2013 rendition with MyTrafficX (not the default) and my FSX crashed in the same location every time (in a flight between Chicago and St Louis). Got rid of the 2013 schedule and went back to the default and no crashes. I know the upgrade to 5.4c for MyTrafficX caused reproducible crashes for everyone too. Just thinking out-loud again and I'm glad to know it is a fix for many. I need to add it to the AVSIM CTD Guide as a possible solution for the ntdll.dll and StackHash errors. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant 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
May 27, 201610 yr There was an update to the 2015 MT6 schedules, some months ago, and that is when I started having the problem.
May 27, 201610 yr Hi Ted and Jay, I understand what you are saying. Still it does not answer the question, "why doesn't it happen to little ole me" or "why isn't it happening to everyone who owns this popular AI program?" One possibility is it reduces the amount of resources being taken on a system and, when you are in an area where there are a lot of eye-candy or you have been flying for some period of time reducing the amount of VAS available. It could be happening in the same location for everyone. I do know for a fact, in the previous version (MyTrafficX), it involved an AI flight schedule as I was using the 2013 rendition with MyTrafficX (not the default) and my FSX crashed in the same location every time (in a flight between Chicago and St Louis). Got rid of the 2013 schedule and went back to the default and no crashes. I know the upgrade to 5.4c for MyTrafficX caused reproducible crashes for everyone too. Just thinking out-loud again and I'm glad to know it is a fix for many. I need to add it to the AVSIM CTD Guide as a possible solution for the ntdll.dll and StackHash errors. Best regards, Do you use the Air Traffic Manager in conjunction with MyTraffic 6?
May 27, 201610 yr Do you use the Air Traffic Manager in conjunction with MyTraffic 6? Hi Jay, I do not use the Air Traffic Manager. My AI setting is set to 30% too. Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant 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
August 18, 20169 yr Sorry to tag an older thread but I can confirm the ntdll.dll crash which started happening for me when I installed MT6 in V3. I'm reticent to even install it again. Can anyone else confirm these workarounds? I have a new Windows 7/V3.3.5 clean install running perfectly and would rather leave it out than have it cause problems. James McLees
August 18, 20169 yr Reinstall MyT 6, rename the military BGL file to bgl.old. If that doesn't work to stop the error, then uninstall MyT 6.
Archived
This topic is now archived and is closed to further replies.