Unable to open Avsim CTD Guide

[STUART_H 12]

I have downloaded the CTD Guide but Adobe won't open the file saying it is an invalid file type.

Please investigate and advise.

 

Thanks Stuart

[Jim Young 2,356]

Please investigate and advise.

I am not having any problems opening it Stuart. I click on download and it say where do you want to save it and I instead select open with Adobe PDF and it opens it up immediately. I can then save it to my HHD if I want.

 

Best regards,

[STUART_H 12]

OK, I had downloaded to my Nexas android device and was trying to open it there using several PDF readers, including Adobe, but none were successful. I'll have to wait and try to open it on my PC. Perhaps it is because of the version of PDF when it was created.

 

Just that I am suddenly getting a fatal error every time I start FSX and try to load a flight. Event viewer says that ntdll.DLL failed but it could be another issue causing it to fail.

 

Need some help in investigating, as I have tried everything from removing entries in DLL.XML to deleting and reinstalling FSX Steam.

 

I am getting very frustrated not being able to load a flight in FSX.

 

Stuart

[Jim Young 2,356]

ust that I am suddenly getting a fatal error every time I start FSX and try to load a flight.

Sounds like the infamous MyTrafficX issue. If you have it installed, you can easily check by disabling MyTrafficX in the Scenery.cfg. Here's what it states in the CTD Guide regarding 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).

 

Best regards,

[STUART_H 12]

Thanks Jim, hopefully will help.

I don't use MyTrafficX. Only AI installed is WOAI.

I think the only thing that I haven't looked at is the first one relating to 'heap tolerant service'. I'll check whether the Security Centre service is turned on.

I'll have to investigate increasing the heap limitation too, once I get the CTD guide opened.

Will have to wait until next week though as am away for the weekend tomorrow.

 

Thanks again,

Stuart

[Jim Young 2,356]

Someone else who had WOAI installed had the same problem you had. FSX would not start up. He removed WOAI and the problems went away. His post his is very recent.

 

EDIT: Here's the topic - http://forum.avsim.net/topic/463679-fsx-ctd-while-loading/. It didn't show ntdll.dll as the faulting module though.

 

Best regards,

[STUART_H 12]

Jim,

Step 1

Just checked the Security Centre Service is running and I applied the Increase Heap fix from Microsoft.

Started FSX Steam, Free Flight screen appeared, but when clicking on [Change Aircraft] I received the fatal error, which Event Viewer attributes to NTDLL.DLL.  FSX never got to loading the flight stage at all !

I ran AppCrashViewer and this is the result below.

How does one glean something from this data as to what might be causing the crash?  Seems last DLL in the list being loaded was:

LoadedModule[205]=C:\Windows\SysWOW64\uiautomationcore.dll

LoadedModule[206]=C:\Windows\SysWOW64\jscript9.dll

Not sure if this is relevent?

 

Can you tell something from this report?  Any help would be appreciated.  Am off for the weekend now so will pick up any suggestions next week.

 

Thanks,

Stuart

 

Version=1

EventType=APPCRASH

EventTime=130701125136762697

ReportType=2

Consent=1

UploadTime=130701125140562914

ReportIdentifier=550b9493-c3ee-11e4-bf63-00241d2dac36

IntegratorReportIdentifier=550b9492-c3ee-11e4-bf63-00241d2dac36

WOW64=1

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=fsx.exe

Sig[1].Name=Application Version

Sig[1].Value=10.0.62608.0

Sig[2].Name=Application Timestamp

Sig[2].Value=54abe5b4

Sig[3].Name=Fault Module Name

Sig[3].Value=ntdll.dll

Sig[4].Name=Fault Module Version

Sig[4].Value=6.1.7601.18247

Sig[5].Name=Fault Module Timestamp

Sig[5].Value=521ea8e7

Sig[6].Name=Exception Code

Sig[6].Value=c0000005

Sig[7].Name=Exception Offset

Sig[7].Value=000332cd

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.1.7601.2.1.0.768.3

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=2057

DynamicSig[22].Name=Additional Information 1

DynamicSig[22].Value=0a9e

DynamicSig[23].Name=Additional Information 2

DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789

DynamicSig[24].Name=Additional Information 3

DynamicSig[24].Value=0a9e

DynamicSig[25].Name=Additional Information 4

DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789

UI[2]=C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe

UI[3]=Microsoft Flight Simulator® 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]=C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.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\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL

LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll

LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll

LoadedModule[7]=C:\Windows\syswow64\GDI32.dll

LoadedModule[8]=C:\Windows\syswow64\USER32.dll

LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll

LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll

LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll

LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll

LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll

LoadedModule[14]=C:\Windows\syswow64\LPK.dll

LoadedModule[15]=C:\Windows\syswow64\USP10.dll

LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll

LoadedModule[17]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll

LoadedModule[18]=C:\Program Files (x86)\Steam\steamapps\common\FSX\steam_api.dll

LoadedModule[19]=C:\Windows\syswow64\SHELL32.dll

LoadedModule[20]=C:\Windows\syswow64\ole32.dll

LoadedModule[21]=C:\Windows\system32\apphelp.dll

LoadedModule[22]=C:\Windows\AppPatch\AcGenral.DLL

LoadedModule[23]=C:\Windows\system32\UxTheme.dll

LoadedModule[24]=C:\Windows\system32\WINMM.dll

LoadedModule[25]=C:\Windows\system32\samcli.dll

LoadedModule[26]=C:\Windows\syswow64\OLEAUT32.dll

LoadedModule[27]=C:\Windows\system32\MSACM32.dll

LoadedModule[28]=C:\Windows\system32\VERSION.dll

LoadedModule[29]=C:\Windows\system32\sfc.dll

LoadedModule[30]=C:\Windows\system32\sfc_os.DLL

LoadedModule[31]=C:\Windows\syswow64\USERENV.dll

LoadedModule[32]=C:\Windows\syswow64\profapi.dll

LoadedModule[33]=C:\Windows\system32\dwmapi.dll

LoadedModule[34]=C:\Windows\syswow64\SETUPAPI.dll

LoadedModule[35]=C:\Windows\syswow64\CFGMGR32.dll

LoadedModule[36]=C:\Windows\syswow64\DEVOBJ.dll

LoadedModule[37]=C:\Windows\syswow64\urlmon.dll

LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll

LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll

LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll

LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll

LoadedModule[42]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll

LoadedModule[43]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll

LoadedModule[44]=C:\Windows\syswow64\normaliz.DLL

LoadedModule[45]=C:\Windows\syswow64\iertutil.dll

LoadedModule[46]=C:\Windows\syswow64\WININET.dll

LoadedModule[47]=C:\Windows\system32\MPR.dll

LoadedModule[48]=C:\Windows\AppPatch\AcLayers.DLL

LoadedModule[49]=C:\Windows\system32\WINSPOOL.DRV

LoadedModule[50]=C:\Windows\AppPatch\AcSpecfc.DLL

LoadedModule[51]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dll

LoadedModule[52]=C:\Windows\system32\mscms.dll

LoadedModule[53]=C:\Windows\system32\DDRAW.dll

LoadedModule[54]=C:\Windows\system32\DCIMAN32.dll

LoadedModule[55]=C:\Windows\syswow64\COMDLG32.dll

LoadedModule[56]=C:\Windows\syswow64\IMM32.dll

LoadedModule[57]=C:\Windows\syswow64\MSCTF.dll

LoadedModule[58]=C:\Windows\syswow64\WS2_32.dll

LoadedModule[59]=C:\Windows\syswow64\NSI.dll

LoadedModule[60]=C:\Windows\system32\msi.dll

LoadedModule[61]=C:\Windows\AppPatch\AcXtrnal.DLL

LoadedModule[62]=C:\Windows\system32\SHUNIMPL.DLL

LoadedModule[63]=C:\Windows\system32\SortWindows6Compat.dll

LoadedModule[64]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL

LoadedModule[65]=C:\Program Files (x86)\Steam\gameoverlayrenderer.dll

LoadedModule[66]=C:\Windows\syswow64\psapi.dll

LoadedModule[67]=C:\Program Files (x86)\Steam\steamapps\common\FSX\language.dll

LoadedModule[68]=C:\Program Files (x86)\Steam\steamclient.dll

LoadedModule[69]=C:\Windows\syswow64\CRYPT32.dll

LoadedModule[70]=C:\Windows\syswow64\MSASN1.dll

LoadedModule[71]=C:\Windows\system32\IPHLPAPI.DLL

LoadedModule[72]=C:\Windows\system32\WINNSI.DLL

LoadedModule[73]=C:\Windows\syswow64\imagehlp.dll

LoadedModule[74]=C:\Program Files (x86)\Steam\tier0_s.dll

LoadedModule[75]=C:\Program Files (x86)\Steam\vstdlib_s.dll

LoadedModule[76]=C:\Windows\system32\Secur32.dll

LoadedModule[77]=C:\Program Files (x86)\Steam\steam.dll

LoadedModule[78]=C:\Program Files (x86)\Steam\Steam2.dll

LoadedModule[79]=C:\Program Files (x86)\Steam\DbgHelp.dll

LoadedModule[80]=C:\Program Files (x86)\Steam\CSERHelper.dll

LoadedModule[81]=C:\Program Files (x86)\Steam\steamapps\common\FSX\API.DLL

LoadedModule[82]=C:\Program Files (x86)\Steam\steamapps\common\FSX\ablscpt.dll

LoadedModule[83]=C:\Program Files (x86)\Steam\steamapps\common\FSX\flight.dll

LoadedModule[84]=C:\Program Files (x86)\Steam\steamapps\common\FSX\ai_player.dll

LoadedModule[85]=C:\Program Files (x86)\Steam\steamapps\common\FSX\acontain.dll

LoadedModule[86]=C:\Program Files (x86)\Steam\steamapps\common\FSX\controls.dll

LoadedModule[87]=C:\Windows\system32\DINPUT8.dll

LoadedModule[88]=C:\Program Files (x86)\Steam\steamapps\common\FSX\fsui.dll

LoadedModule[89]=C:\Program Files (x86)\Steam\steamapps\common\FSX\atc.dll

LoadedModule[90]=C:\Program Files (x86)\Steam\steamapps\common\FSX\facilities.dll

LoadedModule[91]=C:\Program Files (x86)\Steam\steamapps\common\FSX\demo.dll

LoadedModule[92]=C:\Program Files (x86)\Steam\steamapps\common\FSX\main.dll

LoadedModule[93]=C:\Program Files (x86)\Steam\steamapps\common\FSX\fe.dll

LoadedModule[94]=C:\Program Files (x86)\Steam\steamapps\common\FSX\util.dll

LoadedModule[95]=C:\Program Files (x86)\Steam\steamapps\common\FSX\simprop.dll

LoadedModule[96]=C:\Program Files (x86)\Steam\steamapps\common\FSX\g2d.dll

LoadedModule[97]=C:\Windows\system32\d3dx9_34.dll

LoadedModule[98]=C:\Program Files (x86)\Steam\steamapps\common\FSX\d3dx10_34.dll

LoadedModule[99]=C:\Windows\system32\MSVCR100.dll

LoadedModule[100]=C:\Program Files (x86)\Steam\steamapps\common\FSX\reald3dx10_34.DLL

LoadedModule[101]=C:\Program Files (x86)\Steam\steamapps\common\FSX\dx10fixerlib.DLL

LoadedModule[102]=C:\Windows\system32\d3d9.dll

LoadedModule[103]=C:\Windows\system32\d3d8thk.dll

LoadedModule[104]=C:\Program Files (x86)\Steam\steamapps\common\FSX\g3d.dll

LoadedModule[105]=C:\Program Files (x86)\Steam\steamapps\common\FSX\panels.dll

LoadedModule[106]=C:\Program Files (x86)\Steam\steamapps\common\FSX\multiplayer.dll

LoadedModule[107]=C:\Program Files (x86)\Steam\steamapps\common\FSX\sdkencryptedappticket.dll

LoadedModule[108]=C:\Program Files (x86)\Steam\steamapps\common\FSX\ui.dll

LoadedModule[109]=C:\Program Files (x86)\Steam\steamapps\common\FSX\sound.dll

LoadedModule[110]=C:\Program Files (x86)\Steam\steamapps\common\FSX\sim1.dll

LoadedModule[111]=C:\Program Files (x86)\Steam\steamapps\common\FSX\simscheduler.dll

LoadedModule[112]=C:\Program Files (x86)\Steam\steamapps\common\FSX\visualfx.dll

LoadedModule[113]=C:\Program Files (x86)\Steam\steamapps\common\FSX\window.dll

LoadedModule[114]=C:\Program Files (x86)\Steam\steamapps\common\FSX\terrain.dll

LoadedModule[115]=C:\Program Files (x86)\Steam\steamapps\common\FSX\weather.dll

LoadedModule[116]=C:\Windows\system32\DSOUND.dll

LoadedModule[117]=C:\Windows\system32\POWRPROF.dll

LoadedModule[118]=C:\Program Files (x86)\Steam\steamapps\common\FSX\symmap.dll

LoadedModule[119]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll

LoadedModule[120]=C:\Windows\system32\MSIMG32.dll

LoadedModule[121]=C:\Program Files (x86)\Steam\steamapps\common\FSX\xuipc.dll

LoadedModule[122]=C:\Program Files (x86)\Steam\steamapps\common\FSX\livingwater.dll

LoadedModule[123]=C:\Program Files (x86)\Steam\steamapps\common\FSX\fs-traffic.dll

LoadedModule[124]=C:\Program Files (x86)\Steam\steamapps\common\FSX\gps.dll

LoadedModule[125]=C:\Windows\system32\MSWSOCK.dll

LoadedModule[126]=C:\Windows\system32\SHFOLDER.dll

LoadedModule[127]=C:\Windows\system32\CRYPTSP.dll

LoadedModule[128]=C:\Windows\system32\rsaenh.dll

LoadedModule[129]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL

LoadedModule[130]=C:\Windows\system32\dxgi.dll

LoadedModule[131]=C:\Windows\system32\d3d11.dll

LoadedModule[132]=C:\Windows\syswow64\WINTRUST.dll

LoadedModule[133]=C:\Windows\system32\nvd3dum.dll

LoadedModule[134]=C:\Windows\system32\bcrypt.dll

LoadedModule[135]=C:\Windows\system32\D3DCompiler_34.dll

LoadedModule[136]=C:\Windows\SysWOW64\bcryptprimitives.dll

LoadedModule[137]=C:\Windows\system32\WindowsCodecs.dll

LoadedModule[138]=C:\Windows\system32\d3d10_1.dll

LoadedModule[139]=C:\Windows\system32\d3d10_1core.dll

LoadedModule[140]=C:\Windows\syswow64\CLBCatQ.DLL

LoadedModule[141]=C:\Windows\SysWOW64\dxdiagn.dll

LoadedModule[142]=C:\Windows\SysWOW64\d3d10.dll

LoadedModule[143]=C:\Windows\SysWOW64\d3d10core.dll

LoadedModule[144]=C:\Windows\system32\wbem\wbemprox.dll

LoadedModule[145]=C:\Windows\system32\wbemcomn.dll

LoadedModule[146]=C:\Windows\system32\RpcRtRemote.dll

LoadedModule[147]=C:\Windows\system32\wbem\wbemsvc.dll

LoadedModule[148]=C:\Windows\system32\wbem\fastprox.dll

LoadedModule[149]=C:\Windows\system32\NTDSAPI.dll

LoadedModule[150]=C:\Windows\system32\winbrand.dll

LoadedModule[151]=C:\Windows\system32\WTSAPI32.DLL

LoadedModule[152]=C:\Windows\system32\WINSTA.dll

LoadedModule[153]=C:\Windows\SysWOW64\gameux.dll

LoadedModule[154]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll

LoadedModule[155]=C:\Windows\SysWOW64\XmlLite.dll

LoadedModule[156]=C:\Windows\SysWOW64\wer.dll

LoadedModule[157]=C:\Windows\System32\Wpc.dll

LoadedModule[158]=C:\Windows\System32\wevtapi.dll

LoadedModule[159]=C:\Windows\System32\msxml6.dll

LoadedModule[160]=C:\Windows\system32\SAMLIB.dll

LoadedModule[161]=C:\Windows\system32\netutils.dll

LoadedModule[162]=C:\Program Files (x86)\Steam\steamapps\common\FSX\uiautomationcore.dll

LoadedModule[163]=C:\Windows\system32\OLEACC.dll

LoadedModule[164]=C:\Windows\System32\MMDevApi.dll

LoadedModule[165]=C:\Windows\System32\PROPSYS.dll

LoadedModule[166]=C:\Windows\system32\AUDIOSES.DLL

LoadedModule[167]=C:\Windows\system32\RICHED20.DLL

LoadedModule[168]=C:\Windows\system32\HID.DLL

LoadedModule[169]=C:\Windows\system32\XInput9_1_0.dll

LoadedModule[170]=C:\Windows\system32\wdmaud.drv

LoadedModule[171]=C:\Windows\system32\ksuser.dll

LoadedModule[172]=C:\Windows\system32\AVRT.dll

LoadedModule[173]=C:\Windows\system32\msacm32.drv

LoadedModule[174]=C:\Windows\system32\midimap.dll

LoadedModule[175]=C:\Windows\system32\dinput.DLL

LoadedModule[176]=C:\Windows\System32\wship6.dll

LoadedModule[177]=C:\Windows\System32\wshtcpip.dll

LoadedModule[178]=C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\iFly737NG.dll

LoadedModule[179]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll

LoadedModule[180]=C:\Program Files (x86)\Steam\steamapps\common\FSX\bglmanx.dll

LoadedModule[181]=C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\A2A_Feel.dll

LoadedModule[182]=C:\Windows\SysWow64\XAudio2_6.dll

LoadedModule[183]=C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\AccuFeelMenu.dll

LoadedModule[184]=C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.dll

LoadedModule[185]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_1ed9da73c880e429_10.0.62608.0_none_6994c60660d9a3f3\SimConnect.dll

LoadedModule[186]=C:\Program Files (x86)\Steam\steamapps\common\FSX\fsInsider.dll

LoadedModule[187]=C:\Windows\system32\msadp32.acm

LoadedModule[188]=C:\Windows\SysWOW64\ieframe.dll

LoadedModule[189]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll

LoadedModule[190]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll

LoadedModule[191]=C:\Windows\system32\ntmarta.dll

LoadedModule[192]=C:\Windows\syswow64\WLDAP32.dll

LoadedModule[193]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll

LoadedModule[194]=C:\Windows\SysWOW64\mshtml.dll

LoadedModule[195]=c:\program files (x86)\steam\steamapps\common\fsx\simobjects\airplanes\Fly UK DHC8-Q400 (New Union Spirit) v6.0.x\panel.dh84x\DH83.GAU

LoadedModule[196]=C:\Windows\system32\MSVCR70.dll

LoadedModule[197]=c:\program files (x86)\steam\steamapps\common\fsx\simobjects\airplanes\Fly UK DHC8-Q400 (New Union Spirit) v6.0.x\panel.dh84x\RKG_buttons.GAU

LoadedModule[198]=c:\program files (x86)\steam\steamapps\common\fsx\simobjects\airplanes\Fly UK DHC8-Q400 (New Union Spirit) v6.0.x\panel.dh84x\RCB_Groundhandling5_Sound.DLL

LoadedModule[199]=C:\Windows\system32\d2d1.dll

LoadedModule[200]=C:\Windows\system32\DWrite.dll

LoadedModule[201]=C:\Windows\system32\D3D10Warp.dll

LoadedModule[202]=C:\Windows\system32\msimtf.dll

LoadedModule[203]=C:\Windows\system32\msls31.dll

LoadedModule[204]=C:\Windows\system32\MLANG.dll

LoadedModule[205]=C:\Windows\SysWOW64\uiautomationcore.dll

LoadedModule[206]=C:\Windows\SysWOW64\jscript9.dll

FriendlyEventName=Stopped working

ConsentKey=APPCRASH

AppName=Microsoft Flight Simulator®

AppPath=C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe

[Jim Young 2,356]

Can you tell something from this report? Any help would be appreciated. Am off for the weekend now so will pick up any suggestions next week.

The only solutions I know of are the ones in the AVSIM CTD Guide. We did extensive research across the Internet using various search engines looking for causes of this type of crash. We then took that information and put it in the AVSIM CTD Guide. There are absolutely no other solutions other than those indicated in the AVSIM CTD Guide and there was only one known solution (the rest were probable fixes).

 

You are running FSX-SE which has some different configurations but the solutions and probable solutions are still considered valid. You have several addons that were not made for FSX-SE like the A2A_Feel, the Q400, etc., etc. When you have addons like this, then all bets are called off as to what caused the crash. To explain, ALL addons (and FSX-SE) need the proper Microsoft Visual installed to make sure their product was installed properly. I see you have Microsoft Visual C++ 2005 properly installed but no indications Microsoft Visual C++ 2008 installed. Some of these older addons you installed to FSX-SE were developed with Microsoft Visual C++ 2008 w/SP1. Not with the 2005, 2010, or 2013 versions. So, when a product like this is running, it is looking in your registry for certain entries that tells them with the FSX sound is located or other modules. With FSX-SE, they are not located where they should be located as FSX-SE has a completely different file structure which has caused problems even for some of the latest developers like PMDG. They had to come up with some type of installer to enter the appropriate entries into the registry so that FSX-SE could "see" the product properly and not crash.

 

What else is needed to successfully run an application in Windows? Microsoft.net's (dotnets). FSX and many FSX addons needed dotnets 2.0 and 3.0. Some of the later applications are using later dotnets, like version 4.0 or 4.5. Dotnets, for the most part, are not backward compatible. Dotnets are used by developers to make sure their application runs properly in the manner they intended, including memory management. One of the modules that comes with the dotnet packages is the uiautomationcore.dll. Dovetail threw in an older version and you will see that it successfully loaded first and then later on in the FSX-SE loading process, the latest version of uiautomationcore.dll located in the Windows system folders loaded successfully. I cannot determine whether this caused your crash but I doubt it as they both loaded. It might have been a contributing factor.

 

MSVCR70.dll loaded and this belongs to a really, really old Microsoft Visual C++ 2002 (way before FSX was even thought of).  It will usually cause a crash because it needs Microsoft.net 1.0 (developed way before FSX) in order to run properly.  So, if dotnet 1.0 is missing or not registered, then you will have issues.  Microsoft.net's and Microsoft Visuals are installed by a developer of a product if the programs are not installed on your computer.  So, if you installed an old program made of FS2000/2002, the installer will install MSVCR70.dll and the appropriate dotnet 1.0.  So, you need to look into your add/remove programs and see if those programs are installed.  Bottom line:  what worked in FSX, FS2000, or 2002 will not necessarily work in FSX-SE unless the program's installer is updated to use the latest Microsoft Visual and dotnet or with the very different configuration of FSX-SE in mind.

The ntdll.dll is related to memory, memory management, CPU and DRAM voltages. If anything is out of line, an ntdll.dll will result.

 

The jscript9.dll belongs to Internet Explorer 11 (hopefully it was not running in the background while you were running FSX-SE). There was a security update for jscript9 on 15 Feb 2015 so maybe this update messed up Internet Explorer 11. IE11's security updates are known to cause fsx crashes so it could have happened in this case too but I think I'm grasping for straws. I think the only possible solutions are still those shown in the AVSIM CTD Guide.

 

Best regards,

[STUART_H 12]

Jim thanks very much for the comphensive analysis.

It would seem that my system has become very clogged with 'stuff' since I originally had the machine in 2002!!

I will have a look at the CTD Guide when I get home after the weekend, but from all the things you identified, I think it may be time to consider a new PC. My current machine (phenom II 2.6 MHz CPU and GTX 260 graphics card) is beginning to feel the strain.

 

BTW, I don't run Internet Explorer 11, but could it run in the background without my knowledge?

 

Thanks again,

Stuart

[Jim Young 2,356]

 

 

BTW, I don't run Internet Explorer 11, but could it run in the background without my knowledge?

 

Obviously a wrong guess on my part.  The module is in previous versions of Internet Explorer too.  When I did a search though, the first think that I got hit with was the problem with Internet Explorer 11 and I have seen previous problems with IE11 updates.

 

Best regards,

[STUART_H 12]

Jim,

I finally managed to read the CTD guide. I seem to have already tried many of the suggestions it contains, without success.

I seem now to consistently get the ntdll crash when I click the [Change Aircraft] from the initial screen. The aircraft list appears and then when selecting even a default aircraft, the error / crash occurs.

 

Does this suggest anything specific to look for?

Thanks

Stuart

[Jim Young 2,356]

Everything that is in my brain, my research, etc., is in the AVSIM CTD Guide. I have no other solutions. Again, the ntdll.dll is a system module and is related to management of memory for your system. Some people throw in that uiautomationcore.dll thinking that's the holy grail of fixing all crashes and that's what Dovetail did. I think it is a major mistake on their part because there is absolutely no proof whatsoever that the placement of an older Vista version of this module placed in the FSX or FSX-SE folder will magically fix crashes in FSX or FSX-SE. You see? You are having one. I have never seen so many crashes here in this forum caused by the uiautomationcore.dll. It really boggles my mind. Oh well! Like NickN, I'm going to take a deep breath and move on.

 

Best regards,

[STUART_H 12]

Jim,

I may have resolved my ntdll error issue. Not sure what resolved it but I downloaded and reinstalled the FSDT Addon Manager.

I also found that all the default scenery entries in the scenery.cfg were reflecting an error in Scenery Configurator(SC), as they were pointing to just "scenery\....". After pointing them to the full FSX Steam path the error in SC disappeared and FSX loads much better.

I still did get one ntdll error, but think this may be related to the old Premier Dash Q 8-400 aircraft.

I shall try a flight on Friday (next free day) and see if I still get the error.

 

Thanks for all your assistance.

Stuart