Microsoft Flight Simulator® has stopped working

[EagleSkinner 36]

There's no rush or panic here, I have been away from FSX and haven't yet worked my way back in to tuning and tweaking FSX. Besides, wehn reading this forum about CTDs I was rather interested to see this utility "Appcrashviewer" - question: is the link you give a safe one, because McAfee blocks the exe immediately as "infected" and also as a trojan

Anyway, I did the silly thing and turned McAfee off so that I could use appcrashviewer. I'll do a virus scan after.

 

As it turns out, I have had a dozen or so "soft" CTDs wwhere FSX just freezes and closes the program (as opposed to the full BSOD) - the error is always 0xc0000005. It's annoying, but I live with it - for now, while I recover from three+ years away from simming.

 

So for this post, here's my very latest crash report. It's all rather interesting, but I would appreciate if someone a lot wiser than me could take a look over it and tell me what I am or shoould be looking at.

I seem to remember there were a lot of possible tweaks that we could and should to to FSX to reduce these freezes, but please have patience with me, I have even forgotten the language, never mind the actions in FSX.

 

It was a clean install on a new itereation of windows. ALL FSX action files (i.e. FSX, sceneries, planes, FSUIPC type thingies) are on a completely separate SSD. Orbx sceneries all over the NW of USA, a few planes, REX, shockwave lights and A2A trees. All seemed to install correctly, give or take a couple of forgotten updates that caused Orbx sceneries to fail. Corrective actions were taken and these now all run correctly.

The only thing annoying me for now are these occasional unidentifiable freezes, so like I said, if anyone could tell me what I am looking at below, I'd be mighty greatful for the learning.

All the best, Chris Brisland aka Eagleskinner.

 

#####################################################

 

Version=1
EventType=APPCRASH
EventTime=130776629360243139
ReportType=2
Consent=1
UploadTime=130776629363173306
ReportIdentifier=07936118-089a-11e5-8218-50e549e1b2e0
IntegratorReportIdentifier=07936117-089a-11e5-8218-50e549e1b2e0
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.61637.0
Sig[2].Name=Application Timestamp
Sig[2].Value=46fadb14
Sig[3].Name=Fault Module Name
Sig[3].Value=terrain.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.61637.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=46fadb59
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0005595e
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1031
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=c405
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=c40584a475c3f8555bbaab9ef93905b4
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0ebb
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0ebb82beb257b421d80c998c7c0161e9
UI[2]=G:\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]=G:\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\syswow64\ole32.dll
LoadedModule[18]=C:\Windows\system32\apphelp.dll
LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[20]=C:\Windows\system32\UxTheme.dll
LoadedModule[21]=C:\Windows\system32\WINMM.dll
LoadedModule[22]=C:\Windows\system32\samcli.dll
LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[24]=C:\Windows\system32\MSACM32.dll
LoadedModule[25]=C:\Windows\system32\VERSION.dll
LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[27]=C:\Windows\system32\sfc.dll
LoadedModule[28]=C:\Windows\system32\sfc_os.DLL
LoadedModule[29]=C:\Windows\syswow64\USERENV.dll
LoadedModule[30]=C:\Windows\syswow64\profapi.dll
LoadedModule[31]=C:\Windows\system32\dwmapi.dll
LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[35]=C:\Windows\syswow64\urlmon.dll
LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[43]=C:\Windows\syswow64\iertutil.dll
LoadedModule[44]=C:\Windows\syswow64\WININET.dll
LoadedModule[45]=C:\Windows\system32\MPR.dll
LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dll
LoadedModule[50]=C:\Windows\system32\mscms.dll
LoadedModule[51]=C:\Windows\system32\DDRAW.dll
LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[54]=C:\Windows\syswow64\IMM32.dll
LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[57]=C:\Windows\syswow64\NSI.dll
LoadedModule[58]=C:\Windows\system32\msi.dll
LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[60]=G:\FSX\language.dll
LoadedModule[61]=G:\FSX\API.DLL
LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[63]=G:\FSX\ablscpt.dll
LoadedModule[64]=G:\FSX\flight.dll
LoadedModule[65]=G:\FSX\ai_player.dll
LoadedModule[66]=G:\FSX\acontain.dll
LoadedModule[67]=G:\FSX\controls.dll
LoadedModule[68]=C:\Windows\system32\DINPUT8.dll
LoadedModule[69]=G:\FSX\fsui.dll
LoadedModule[70]=G:\FSX\atc.dll
LoadedModule[71]=G:\FSX\facilities.dll
LoadedModule[72]=G:\FSX\demo.dll
LoadedModule[73]=G:\FSX\main.dll
LoadedModule[74]=G:\FSX\fe.dll
LoadedModule[75]=G:\FSX\util.dll
LoadedModule[76]=G:\FSX\simprop.dll
LoadedModule[77]=G:\FSX\g2d.dll
LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[80]=C:\Windows\system32\d3d9.dll
LoadedModule[81]=C:\Windows\system32\d3d8thk.dll
LoadedModule[82]=G:\FSX\g3d.dll
LoadedModule[83]=G:\FSX\panels.dll
LoadedModule[84]=G:\FSX\multiplayer.dll
LoadedModule[85]=G:\FSX\ui.dll
LoadedModule[86]=G:\FSX\sound.dll
LoadedModule[87]=G:\FSX\sim1.dll
LoadedModule[88]=G:\FSX\simscheduler.dll
LoadedModule[89]=G:\FSX\visualfx.dll
LoadedModule[90]=G:\FSX\window.dll
LoadedModule[91]=G:\FSX\terrain.dll
LoadedModule[92]=G:\FSX\weather.dll
LoadedModule[93]=C:\Windows\system32\DSOUND.dll
LoadedModule[94]=C:\Windows\system32\POWRPROF.dll
LoadedModule[95]=G:\FSX\symmap.dll
LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18834_none_72d38c5186679d48\gdiplus.dll
LoadedModule[97]=C:\Windows\system32\MSIMG32.dll
LoadedModule[98]=G:\FSX\xuipc.dll
LoadedModule[99]=G:\FSX\livingwater.dll
LoadedModule[100]=G:\FSX\fs-traffic.dll
LoadedModule[101]=G:\FSX\gps.dll
LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[104]=c:\PROGRA~2\mcafee\SITEAD~1\saHook.dll
LoadedModule[105]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[106]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[107]=C:\Windows\system32\rsaenh.dll
LoadedModule[108]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[109]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[110]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[111]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[112]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[113]=C:\Windows\system32\wbemcomn.dll
LoadedModule[114]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[115]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[116]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[117]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[118]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[119]=C:\Windows\system32\dxgi.dll
LoadedModule[120]=C:\Windows\system32\d3d11.dll
LoadedModule[121]=C:\Windows\system32\nvd3dum.dll
LoadedModule[122]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[123]=C:\Windows\system32\bcrypt.dll
LoadedModule[124]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[125]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[126]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[127]=C:\Windows\system32\d3d10_1.dll
LoadedModule[128]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[129]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[130]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[131]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[132]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[133]=C:\Windows\system32\winbrand.dll
LoadedModule[134]=C:\Windows\system32\nvapi.dll
LoadedModule[135]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[136]=C:\Windows\system32\WINSTA.dll
LoadedModule[137]=C:\Windows\system32\oleacc.dll
LoadedModule[138]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[139]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18807_none_41e554362bd82458\COMCTL32.dll
LoadedModule[140]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[141]=C:\Windows\SysWOW64\wer.dll
LoadedModule[142]=C:\Windows\System32\Wpc.dll
LoadedModule[143]=C:\Windows\System32\wevtapi.dll
LoadedModule[144]=C:\Windows\System32\msxml6.dll
LoadedModule[145]=C:\Windows\system32\SAMLIB.dll
LoadedModule[146]=C:\Windows\system32\netutils.dll
LoadedModule[147]=C:\Windows\system32\uiautomationcore.dll
LoadedModule[148]=C:\Windows\System32\MMDevApi.dll
LoadedModule[149]=C:\Windows\System32\PROPSYS.dll
LoadedModule[150]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[151]=C:\Windows\system32\RICHED20.DLL
LoadedModule[152]=C:\Windows\system32\HID.DLL
LoadedModule[153]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[154]=C:\Windows\system32\wdmaud.drv
LoadedModule[155]=C:\Windows\system32\ksuser.dll
LoadedModule[156]=C:\Windows\system32\AVRT.dll
LoadedModule[157]=C:\Windows\system32\msacm32.drv
LoadedModule[158]=C:\Windows\system32\midimap.dll
LoadedModule[159]=C:\Windows\system32\dinput.DLL
LoadedModule[160]=C:\Windows\System32\wship6.dll
LoadedModule[161]=C:\Windows\System32\wshtcpip.dll
LoadedModule[162]=G:\FSX\ORBX\FTX_NA\FTX_AA_KBVS\Scenery\Objectflow_KBVS.dll
LoadedModule[163]=C:\Windows\system32\Secur32.dll
LoadedModule[164]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[165]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[166]=C:\Windows\system32\WINNSI.DLL
LoadedModule[167]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[168]=C:\Windows\system32\DNSAPI.dll
LoadedModule[169]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[170]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL
LoadedModule[171]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[172]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
LoadedModule[173]=C:\Windows\system32\rasadhlp.dll
LoadedModule[174]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[175]=G:\FSX\ORBX\FTX_NA\FTX_AA_05S\scenery\ObjectFlow_05S.dll
LoadedModule[176]=G:\FSX\ORBX\FTX_NA\FTX_AA_11S\scenery\ObjectFlow_11S.dll
LoadedModule[177]=G:\FSX\ORBX\FTX_NA\FTX_AA_W16\scenery\ObjectFlow_W16.dll
LoadedModule[178]=G:\FSX\ORBX\FTX_NA\FTX_AA_0S9\scenery\Objectflow_0S9.dll
LoadedModule[179]=G:\FSX\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll
LoadedModule[180]=G:\AFX Demo\AFXModuleFSX.dll
LoadedModule[181]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[182]=G:\FSX\ORBX\FTX_NA\FTX_AA_7S3\Scenery\ObjectFlow_7S3.dll
LoadedModule[183]=G:\FSX\ORBX\FTX_NA\FTX_AA_PAKT\Scenery\ObjectFlow_PAKT.dll
LoadedModule[184]=G:\FSX\ORBX\FTX_NA\FTX_AA_1WA6\Scenery\ObjectFlow_1WA6.dll
LoadedModule[185]=G:\FSX\ORBX\FTX_NA\FTX_AA_2WA1\Scenery\Objectflow_2WA1.dll
LoadedModule[186]=G:\FSX\ORBX\FTX_NA\FTX_AA_CEJ4\scenery\ObjectFlow_cej4.dll
LoadedModule[187]=G:\FSX\ORBX\FTX_NA\FTX_AA_74S\Scenery\ObjectFlow_74S.dll
LoadedModule[188]=G:\FSX\Modules\FSUIPC4.dll
LoadedModule[189]=C:\Windows\syswow64\imagehlp.dll
LoadedModule[190]=C:\Windows\system32\ncrypt.dll
LoadedModule[191]=C:\Windows\system32\GPAPI.dll
LoadedModule[192]=C:\Windows\system32\cryptnet.dll
LoadedModule[193]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[194]=C:\Windows\system32\SensApi.dll
LoadedModule[195]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[196]=G:\FSX\Modules\A2A_Feel.dll
LoadedModule[197]=C:\Windows\SysWow64\XAudio2_6.dll
LoadedModule[198]=G:\FSX\Modules\AccuFeelMenu.dll
LoadedModule[199]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[200]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[201]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[202]=C:\Windows\system32\msimtf.dll
LoadedModule[203]=C:\Windows\system32\msls31.dll
LoadedModule[204]=C:\Windows\system32\d2d1.dll
LoadedModule[205]=C:\Windows\system32\DWrite.dll
LoadedModule[206]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[207]=C:\Windows\system32\MLANG.dll
LoadedModule[208]=C:\Windows\system32\ntmarta.dll
LoadedModule[209]=G:\FSX\GAUGES\A2A_Accusim.DLL
LoadedModule[210]=G:\FSX\SimObjects\Airplanes\A2A_C182\panel\C182.DLL
LoadedModule[211]=G:\FSX\SimObjects\Airplanes\A2A_C182\panel\C182_Illumination.DLL
LoadedModule[212]=C:\Windows\system32\msadp32.acm
LoadedModule[213]=C:\Windows\system32\explorerframe.dll
LoadedModule[214]=C:\Windows\system32\DUser.dll
LoadedModule[215]=C:\Windows\system32\DUI70.dll
LoadedModule[216]=C:\Users\Chris\AppData\Local\Microsoft\OneDrive\17.3.5860.0512\FileSyncShell.dll
LoadedModule[217]=C:\Users\Chris\AppData\Local\Microsoft\OneDrive\17.3.5860.0512\MSVCP110.dll
LoadedModule[218]=C:\Users\Chris\AppData\Local\Microsoft\OneDrive\17.3.5860.0512\MSVCR110.dll
LoadedModule[219]=C:\Users\Chris\AppData\Local\Microsoft\OneDrive\17.3.5860.0512\Telemetry.dll
LoadedModule[220]=C:\Users\Chris\AppData\Local\Microsoft\OneDrive\17.3.5860.0512\LoggingPlatform.DLL
LoadedModule[221]=C:\Windows\system32\WSOCK32.dll
LoadedModule[222]=C:\Windows\system32\Cabinet.dll
LoadedModule[223]=C:\Windows\system32\WINHTTP.dll
LoadedModule[224]=C:\Windows\system32\webio.dll
LoadedModule[225]=C:\Windows\system32\EhStorShell.dll
LoadedModule[226]=C:\Windows\system32\ntshrui.dll
LoadedModule[227]=C:\Windows\system32\srvcli.dll
LoadedModule[228]=C:\Windows\system32\cscapi.dll
LoadedModule[229]=C:\Windows\system32\slc.dll
LoadedModule[230]=C:\Windows\System32\shdocvw.dll
LoadedModule[231]=C:\Windows\system32\SXS.DLL
LoadedModule[232]=C:\Windows\System32\StructuredQuery.dll
LoadedModule[233]=C:\Windows\SysWOW64\actxprxy.dll
LoadedModule[234]=C:\Program Files (x86)\Internet Explorer\ieproxy.dll
LoadedModule[235]=C:\Windows\SysWOW64\thumbcache.dll
LoadedModule[236]=C:\Windows\system32\LINKINFO.dll
LoadedModule[237]=C:\Windows\system32\NetworkExplorer.dll
LoadedModule[238]=C:\Windows\System32\drprov.dll
LoadedModule[239]=C:\Windows\System32\davclnt.dll
LoadedModule[240]=C:\Windows\System32\DAVHLPR.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Flight Simulator®
AppPath=G:\FSX\fsx.exe
 

[vc10man 732]

That's a false positive from McAfee. It's safe to use.

[Jim Young 2,356]

Rick is correct. Understand your concerns about getting a virus though.

You need to disable your anti-virus program for FSX. How you do this I do not know as I've never owned an anti-virus program but that's what the experts say. You don't want to have your anti-virus program scanning fsx while you are using it.

Microsoft Visual C++ 2005 w/SP1 is installed and is up-to-date. Very good!

Microsoft Visual C++ 2008 w/SP1 did not load and that is strange as most addon's use Microsoft Visual 2008. Make sure it is installed. See page 6 of the AVSIM CTD Guide.

 

Microsoft Visual C++ 2011 loaded properly but very few programs use that.  Orbx/FTX may be using it.  Many programs use Microsoft Visual C++ 2010 but that module did not load which is possible.  I would make sure you have the 2008 and 2010 versions installed.

While looking in the guide, make sure you have Microsoft.net 2.0 through the latest installed (look in your Add/Remove Programs. See page 7 of the AVSIM CTD Guide for an explanation and links and more information.

The latest crash you had was caused by the terrain.dll. Quite common but it indicates you have your fsx settings set too high, especially Autogen.  Although not stated in the guide, if you have tweaks installed that are taking over your system in the wrong way, this could create a strain on your system. For instance, it is a well-known fact that the BufferPools tweak causes instability in most installations. One day it could work well, the next you are seeing freezes and another anomalies. The tweak is not a setting that you set that works for everyone. It only helps those using a lot of autogen. See the AVSIM FSX Configuration Guide for more information about tweaks and the proper settings for your FSX.cfg and video card if you own the Nvidia card.

 

The AVSIM CTD Guide tells you about the uiautomationcore.dll on page 8.  This fixes only one type of freeze on FSX - a menu freeze.  So, if you are clicking on the fsx menu or, while in VC mode, you are right clicking on the panel and selecting options, this could cause a freeze and a certain version of uiautomationcore.dll may fix this problem.  You have to have a least 19 menu clicks before the freezes.  Anything less and your sim will not freeze.  Some say it is the "holy grail" of fixing freezes but then many will later post that they had a crash or freeze and I'll see that the uiautomationcore.dll loaded in their crash report.  So much for being the holy grail!!!  It's always worth a try.  It's part of the Microsoft.net programs.  This is why I say you should have all of the proper Microsoft.net programs installed.  None are backward compatible.

The AVSIM CTD Guide lists several "probable" causes of crashes and is mostly very up-to-date as FSX is an old program and the crashes and types of crashes will never change. AVSIM did a Google search for you to find all of the possible causes for a terrain.dll crash and other types of crashes and put them in the guide. Very rarely will you see a fix that works for everyone. Everyone has a different computer system, overclocked and not clocked, high powered and low-powered. With a lot of addons and some with just the default stuff. So, you may have to conduct an investigation if one of the suggestions to not work. AVSIM is currently working on updating how you conduct an investigation for your crash. The guidance in draft forum is as follows:

Return to the default configuration - This is done by rebuilding your configuration; disabling add-on scenery; and disabling modules in your dll.xml or exe.xml as follows –

• Rebuild Configurations – Most CTD’s can be fixed by renaming your FSX/P3D/FSX-SE configuration with another extension, such as fsx.cfg to fsx.orig, or you can move the file to a temporary folder, restart the program and let the configuration rebuild. The respective application configurations are in hidden as follows - (C:\User\(yourusername)\AppData\Roaming\Microsoft\FSX or Lockheed Martin\ P3D). It has been said my many experts that rebuilding your configuration is about the same as uninstalling/reinstalling FSX, FS9, FSX-SE or P3D, as appropriate, as it removes tweaks or other parameters that you may have added and may be causing more harm than good.
• Disable Add-on Scenery – To quickly determine if your scenery.cfg is the problem, move your scenery.cfg to a temporary folder, restart FSX/P3D/FSX-SE, and the default scenery.cfg will be installed. The scenery.cfg is located in a hidden folder (C:\Program Data\Microsoft\FSX or LockHeed Martin\P3D). If this stops the CTD’s, then the problem is probably associated with one or more of your add-on sceneries. To find the offending scenery, you will have to return the scenery.cfg you moved to a temporary folder above back to the hidden folder to replace the default. Disable all of the add-on scenery via the Scenery Library or the Scenery Config Editor utility. You will then have to enable your add-ons 3-4 at a time until the CTD returns. AVSIM does not recommend this action unless you know for sure the problem is one of your scenery add-ons. Since an AI program is commonly the cause of CTD’s, disabling your AI program may be all you need to check.
• Disable modules in dll.xml and exe.dll– To quickly determine if your dll.xml and/or your exe.dll is the issue for your CTD’s, move the dll.xml and exe.xml to a temporary folder and restart FSX. These modules will not be rebuilt but your sim should still load (you just will not have an Add-on Menu). Sometimes a module you have installed is corrupted or is somehow duplicated in the dll.xml. If you moved the dll.xml and exe.xml to a temporary folder and the crashes stopped, move the dll.xml and exe.xml files you moved to a temporary folder back to the hidden folder. You can now check to see which module(s) caused your crashes by disabling the modules (except the first one). Change the parameter ‘False’ in the line <Disabled>False</Disabled> to True. Do this for each module until the problem is fixed. To check for possible dll.xml corruption – Click on the following dll.xml troubleshooting guide from PMDG.

 

Run Process Monitor – Another investigative tool used to pin down a situation where your application freezes, crashes, or stutters/pauses during a flight is to run a utility called Process Monitor. During your flight, this utility monitors activity such as calling textures, AI aircraft schedules, ATC, weather updates, and scenery loading.  When FSX/P3D stutters or FPS drop dramatically you simply write down the time it occurred.  This is important as thousands of entries are made every minute, every second.  Continue doing this throughout the flight.  Of course, if it freezes, you will know what was going on before the application froze.  This utility will not show you a definitive cause of your issue but it will show you what add-ons were being loaded about when you received the stutter, the long pause(s), and the freeze and you can further investigate by disabling that scenery, that aircraft, or whatever might have caused the event.  One member used this utility to determine that My Traffic X, version 5.4c was the cause of a BEX/StackHash/NTDLL.dll crash he was getting.  It was easy to disable My Traffic X in the Scenery Library and find that FSX no longer crashed.

AVSIM recommends you do not run a flight any longer than 60 minutes as the Process Monitor log becomes quite large (hopefully your application will freeze or crash by then!).  For a 60 minutes flight, expect the file to be at least as large as 8GB’s or tens of millions of captured events.  Make sure you delete the log or move it to another drive after you have finished your testing to free up HDD space.  Another recommended tip is to make sure you use system time to mark the time of each event and do not use an external clock unless they are synchronized.  Going through one minute of a process is a massive amount of data needed to be reviewed (it goes fast as thousands of entries just show a scenery being loaded).

To run this utility properly, you need to capture only FSX/P3D/FS9 events.  It would be nearly impossible to find a possible glitch or issue if Windows events or other system activities were being logged too.  AVSIM recommends opening of the Process Monitor when you are on the active runway and preparing to takeoff to save space on your HDD:

• Startup FSX/P3D/FS9, as appropriate, to the Setup Screen.
• Open Process Monitor
• Click on the Filter tab and then Filter…. 
• Click on Architecture and scroll down to Process Name
• Click on blank box and select FSX/P3D/FS9, as appropriate
• Click Ok or Apply

 

NOTE:  AVSIM recommends you click on the filter tab again and then select ‘Save filter…’ and name your Filter – FSX (or P3D/FS9).  Then, in the future, you can startup Process Monitor before opening your application and watch what is loading as your application loads to the Setup Screen.

 

You can use the utility while in Full Screen mode or Windowed Mode.  In Windowed Mode you can monitor what is happening instantly but it is best to run Process Monitor in Full Screen (unless you are seeing freezes in Windowed Mode).

 

When the flight is finished, immediately go to the Process Monitor application, click on it to bring it into focus, and hit Ctrl+E on your keyboard to capture the events (event logging will continue until you do this and make it more difficult to locate the cause of your crash).  Shutdown FSX/P3D/FS9 and begin your investigating!  You can also save the log for future investigations but remember the file will be as large as 8GB’s or more and using valuable disk space.

 

Delete/Rebuild your Facilities/Scenery Indexes and Shader Folders – These are temporary folders and should be deleted periodically (they will be rebuilt):

Facilities/Scenery Indexes are located in C:\Program Data\Microsoft\FSX\(hidden).  For P3D, instead of Microsoft\FSX, look in LockHeed Martin\Prepar3D v2 for the indexes.  Delete the Facilities and Scenery folders. They will be rebuilt.

 

Delete the Shader folders located in C:\Users\(your username)\AppData\Local/Microsoft\ FSX\Shader10 and Shader folders (hidden). The Shader 10 folder is created when you enable DX10 Preview in FSX.  The Shaders folder for DX9 will always be created. For P3D users, there is only a Shaders folder in C:\Users\(your username)\AppData\LockHeed Martin\Prepar3D v2 folder.  When you restart FSX/P3D, these folders will be rebuilt.  Deleting these temporary folders has also been known to fix some CTD’s.

 

Hope this helps! 

 

Best regards,

[EagleSkinner 36]

Well, to say I am impressed would be an understatement!Many thanks for the interpretations and explanations. I can see there is a lot still to learn about this thing called FSX!

If I don't reply in as much detail, please forgive me - I will be somewhere under the bonnet of my FSX, tinkering away with things; or I'll be flying along in Betsy Beaver through some turbulence ridden valleys in the PacNW. I might even get back to do some painting.

But your explanations are far more than I expected or had a right to. Many many thanks.

Oh, on the subject of virus scanners: I did remember about turning them off during installation and McAfee has a useful off switcch in "Total Protection" What I did forget (and I am sure many others will too at times) is that when you install other software addons (non-sx) many come with auto installers for useful little sub-apps such as virus scanners. The search bar tools in Firefox for instance, actually installs a separate isue of McAfee. So while I was installing my Orbx terrains I still had problems because a freeware version of McAfee was lurking in the wings, doing things.

[EagleSkinner 36]

First actions...

 

Here's the response I get from trying to install MVS 2008 SP1:

"A compatible version of Visual Studio 2008 was not detected on the system. This update is designed for only the Microsoft Visual Studio 2008 (ENU) product family, and is not compatible with any Express editions."



 

[EagleSkinner 36]

Well, most of that seems to have worked. The most effective results regarding the CTDs must have been turning the McAfee virus scanner. Next major result was going through the tweaks - here it was ******* Bojote's tweaker that did the best job - but mostly for performance here.

Whilst effective, the most work was involved in downloading and installing the Microsoft stuff - Visual Studio and all the sundry odds.

 

Just goes to show that Microsoft are far better at plastering over cracks than in actually getting things right first time.

Thanks for all the help in getting me back into simming!

[Jim Young 2,356]

 

 

Visual Studio and all the sundry odds.

 

You must NOT download and install Visual Studio.  The AVSIM CTD Guide refers you to Microsoft Visual C++ Redistributables, not Visual Studio.

 

Thanks for your other suggestions.

 

Best regards,