help with 4 ctd in one night

[alphabetagaga 0]

hi guys looking for some help here. only had fsx installed for 3 weeks. the alienware 14 laptop is 2 months old. had a couple of ctd 3 weeks ago then nothing until last night. last night i got 4 :( 

 

fsx.exe    Stopped working    27/10/2013 22:56:31    Stuart    0xc0000005    0x0002e41b    ntdll.dll    6.1.7601.18247    C:\FSX\fsx.exe    22,870    C:\Users\Stuart\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_525c3e8fdacff77b679864762b91887b39c5e5ca_0a4faa83\Report.wer    

 

fsx.exe    Stopped working    27/10/2013 20:41:01    Stuart    0xc0000005    0x000172ef    MSVCR80.dll    8.0.50727.6195    C:\FSX\fsx.exe    25,602    C:\Users\Stuart\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_b7290e017f943e1672c612aa366b314c1b_1567dc69\Report.wer    

 

fsx.exe    Stopped working    27/10/2013 20:30:51    Stuart    0xc0000005    0x000172ef    MSVCR80.dll    8.0.50727.6195    C:\FSX\fsx.exe    25,602    C:\Users\Stuart\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_b7290e017f943e1672c612aa366b314c1b_17967197\Report.wer    

 

fsx.exe    Stopped working    27/10/2013 19:59:09    Stuart    0xc0000005    0x0002e41b    ntdll.dll    6.1.7601.18247    C:\FSX\fsx.exe    26,074    C:\Users\Stuart\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_525c3e8fdacff77b679864762b91887b39c5e5ca_0e5de070\Report.wer    
 

and here is the log from appcrashview for the last crash timed at 22:56:31

 

Version=1
EventType=APPCRASH
EventTime=130273881913573122
ReportType=2
Consent=1
ReportIdentifier=049c4e03-3f5b-11e3-b38b-0c84dcbafe4e
IntegratorReportIdentifier=049c4e02-3f5b-11e3-b38b-0c84dcbafe4e
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=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=0002e41b
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
UI[2]=C:\FSX\fsx.exe
UI[3]=A fatal error occurred.
UI[4]=Windows can check online for a solution to the problem and try to restart the program.
UI[5]=Check online for a solution and restart the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\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\system32\USERENV.dll
LoadedModule[30]=C:\Windows\system32\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\SysWOW64\nvinit.dll
LoadedModule[60]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[61]=C:\FSX\language.dll
LoadedModule[62]=C:\FSX\API.DLL
LoadedModule[63]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[64]=C:\FSX\ablscpt.dll
LoadedModule[65]=C:\FSX\flight.dll
LoadedModule[66]=C:\FSX\ai_player.dll
LoadedModule[67]=C:\FSX\acontain.dll
LoadedModule[68]=C:\FSX\controls.dll
LoadedModule[69]=C:\Windows\system32\DINPUT8.dll
LoadedModule[70]=C:\FSX\fsui.dll
LoadedModule[71]=C:\FSX\atc.dll
LoadedModule[72]=C:\FSX\facilities.dll
LoadedModule[73]=C:\FSX\demo.dll
LoadedModule[74]=C:\FSX\main.dll
LoadedModule[75]=C:\FSX\fe.dll
LoadedModule[76]=C:\FSX\util.dll
LoadedModule[77]=C:\FSX\simprop.dll
LoadedModule[78]=C:\FSX\g2d.dll
LoadedModule[79]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[80]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[81]=C:\Windows\system32\d3d9.dll
LoadedModule[82]=C:\Windows\system32\d3d8thk.dll
LoadedModule[83]=C:\FSX\g3d.dll
LoadedModule[84]=C:\FSX\panels.dll
LoadedModule[85]=C:\FSX\multiplayer.dll
LoadedModule[86]=C:\FSX\ui.dll
LoadedModule[87]=C:\FSX\sound.dll
LoadedModule[88]=C:\FSX\sim1.dll
LoadedModule[89]=C:\FSX\simscheduler.dll
LoadedModule[90]=C:\FSX\visualfx.dll
LoadedModule[91]=C:\FSX\window.dll
LoadedModule[92]=C:\FSX\terrain.dll
LoadedModule[93]=C:\FSX\weather.dll
LoadedModule[94]=C:\Windows\system32\DSOUND.dll
LoadedModule[95]=C:\Windows\system32\POWRPROF.dll
LoadedModule[96]=C:\FSX\symmap.dll
LoadedModule[97]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dll
LoadedModule[98]=C:\Windows\system32\MSIMG32.dll
LoadedModule[99]=C:\FSX\xuipc.dll
LoadedModule[100]=C:\FSX\livingwater.dll
LoadedModule[101]=C:\FSX\fs-traffic.dll
LoadedModule[102]=C:\FSX\gps.dll
LoadedModule[103]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[104]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[105]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[106]=C:\Windows\system32\rsaenh.dll
LoadedModule[107]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[108]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[109]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[110]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[111]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[112]=C:\Windows\system32\wbemcomn.dll
LoadedModule[113]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[114]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[115]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[116]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[117]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[118]=C:\Windows\system32\dxgi.dll
LoadedModule[119]=C:\Windows\system32\d3d11.dll
LoadedModule[120]=C:\Windows\system32\nvd3dum.dll
LoadedModule[121]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[122]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[123]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[124]=C:\Windows\system32\d3d10_1.dll
LoadedModule[125]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[126]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[127]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[128]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[129]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[130]=C:\Windows\system32\winbrand.dll
LoadedModule[131]=C:\Windows\system32\nvapi.dll
LoadedModule[132]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[133]=C:\Windows\system32\WINSTA.dll
LoadedModule[134]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[135]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
LoadedModule[136]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[137]=C:\Windows\SysWOW64\wer.dll
LoadedModule[138]=C:\Windows\System32\Wpc.dll
LoadedModule[139]=C:\Windows\System32\wevtapi.dll
LoadedModule[140]=C:\Windows\System32\msxml6.dll
LoadedModule[141]=C:\Windows\system32\SAMLIB.dll
LoadedModule[142]=C:\Windows\system32\netutils.dll
LoadedModule[143]=C:\FSX\uiautomationcore.dll
LoadedModule[144]=C:\Windows\system32\OLEACC.dll
LoadedModule[145]=C:\Windows\System32\MMDevApi.dll
LoadedModule[146]=C:\Windows\System32\PROPSYS.dll
LoadedModule[147]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[148]=C:\Windows\system32\RICHED20.DLL
LoadedModule[149]=C:\Windows\system32\HID.DLL
LoadedModule[150]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[151]=C:\Windows\system32\wdmaud.drv
LoadedModule[152]=C:\Windows\system32\ksuser.dll
LoadedModule[153]=C:\Windows\system32\AVRT.dll
LoadedModule[154]=C:\Windows\system32\msacm32.drv
LoadedModule[155]=C:\Windows\system32\midimap.dll
LoadedModule[156]=C:\Windows\system32\dinput.DLL
LoadedModule[157]=C:\Windows\System32\wship6.dll
LoadedModule[158]=C:\Windows\System32\wshtcpip.dll
LoadedModule[159]=C:\FSX\Addons\AIRound\AIRound.dll
LoadedModule[160]=C:\FSX\Modules\FSUIPC4.dll
LoadedModule[161]=C:\Windows\system32\iphlpapi.dll
LoadedModule[162]=C:\Windows\system32\WINNSI.DLL
LoadedModule[163]=C:\Windows\syswow64\imagehlp.dll
LoadedModule[164]=C:\Windows\system32\ncrypt.dll
LoadedModule[165]=C:\Windows\system32\bcrypt.dll
LoadedModule[166]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[167]=C:\Windows\system32\GPAPI.dll
LoadedModule[168]=C:\Windows\system32\cryptnet.dll
LoadedModule[169]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[170]=C:\Windows\system32\SensApi.dll
LoadedModule[171]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[172]=C:\Windows\system32\msadp32.acm
LoadedModule[173]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[174]=C:\Windows\SysWOW64\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[175]=C:\Windows\SysWOW64\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[176]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[177]=C:\Windows\system32\Secur32.dll
LoadedModule[178]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[179]=C:\Windows\system32\msimtf.dll
LoadedModule[180]=C:\Windows\system32\msls31.dll
LoadedModule[181]=C:\Windows\system32\d2d1.dll
LoadedModule[182]=C:\Windows\system32\DWrite.dll
LoadedModule[183]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[184]=C:\Windows\system32\MLANG.dll
LoadedModule[185]=C:\Windows\system32\ntmarta.dll
LoadedModule[186]=C:\Windows\SysWOW64\uiautomationcore.dll
LoadedModule[187]=C:\Fraps\FRAPS32.DLL
LoadedModule[188]=C:\Windows\system32\windowscodecsext.dll
LoadedModule[189]=C:\Windows\SysWOW64\jscript9.dll
LoadedModule[190]=C:\Windows\system32\d3dx9_31.dll
Sec[0].Key=LCID
Sec[0].Value=2057
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft® Flight Simulator X
AppPath=C:\FSX\fsx.exe
 

not sure if this helps, i only have a few add-ons - gex europe, utx europe, rex, aismooth and just one plane the a2a 172. last night i was running without rex and just using the default mooney.

 

any ideas? would be very grateful for any help.

[Jim Young 2,356]

The MSVCR80.dll (cause of a couple of your crashes) is part of the Microsoft Visual C++ 2005 package which was installed with FSX and FSX Acceleration.  You have the latest version of the 2005 package installed.  It is used by developers to make sure your applications are installed properly in the manner they intended. It works with Microsoft.net packages.....

 

Microsoft.net - you should check to make sure you have the proper versions of Microsoft.net. These are installed when you install FSX or a fsx addon but they could be corrupted or missing. You need versions 1.1 thru the latest installed. You can see quickly what versions are installed on your computer by looking in C:\Windows\Microsoft.net\framework\then the versions (must be the 32 bit versions). To verify they are installed properly you can go to the following link and use the verification tool there - http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx. Microsoft.net is used by developers to make sure their product works as intended including managing memory for the application.

 

NTDLL.DLL (faulting module for your latest crash) - I was getting this error as the faulting module every time I loaded FSX with a flight from KIAD to KCLT (Wash to Charlotte). I have no tweaks but my LOD_Radius was set to 6.5. Lowered it to 5.5 and still got a crash. I checked my dll.xml and had two entries for PMDG and several entries for software I had uninstalled. I removed those entries and the duplicate PMDG entry. Tried the flight again and no CTD.

 

On another occasion, after opening AS2012 and then starting up FSX for a flight from KIAD to KORD, I loaded the PMDG777. All went well in pouring rain and I took off on runway 30. Soon after that I got the mouse pointer indicating something was running then a crash. A look at the AppCrashView indicated the faulting module was ntdll.dll. I accidentally discovered I again had the uiautomationcore.dll in my main fsx folder. I never installed this module and some unknown software program installed it. I deleted the module. Ran AS2012 and FSX with the same scenario as above (same time, same location, same flightplan, same weather from AS2012). This time I had no crash and was able to complete the flight to Chicago. The FSUIPC log indicated I had an average of 36 fps throughout the flight.

 

Fault Tolerant Heap and NTDLL.dll. 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.

 

The NTDLL faulting module is related to memory so there is a setting(s) that are set too high.  REX could be the culprit if you set the textures to 4096 (HD) instead of 2048 (HD).  GEX Europe only replaces your default textures so it is impossible for that program to be the fault of any crash (unless it was installed improperly and that's extremely remote).  Same goes with UTX Europe.  The A2A 172 might have not been installed properly but I've never heard of it causing a crash.  The fact that you were using the default Mooney at the time of your CTD indicates it is a high setting or the dll.xml corruption or the uiautomationcore.dll.  Of course, a bad tweak in the Fsx.cfg will also cause an NTDLL.dll crash if the tweak uses up more resources (like the Bufferpool or that other resource taking tweak known as the Fiber_Frame_Time_Fraction).  If your Fsx.cfg is tweaked, then you should rename the Fsx.cfg to fsx.orig, restart FSX and let the fsx.cfg rebuild.  This way you will know whether it is one of the tweaks or not that's causing your problems.  If the CTD's continue, just delete the Fsx.cfg and rename the fsx.orig back to fsx.cfg.

 

Hope this helps.

 

Best regards,

Jim

 

[alphabetagaga 0]

thanks very much for taking the time to submit such a detailed reply. i ran the .net verification tool and all 6 installs passed ok. i've not gone into the fsx.cfg file and done any manual editing myself, last time i did that i ended up having to do a clean fsx install :unsure:. re the settings i have attached a few screengrabs of my current settings inc rex.

 

note 1) i have a switchable graphics card and always run with the nvidia when using fsx so ignore the intel entry you see.

 

note 2) i didn't have rex running when the 4 ctd occured so could that be ruled out?

 

 

 

 

 

 

 

 

 

 

 

are any settings too high in your opinion? i don't have any fps issues that i notice. sometimes use fraps and that always seems to avg around the 28fps mark.

[alphabetagaga 0]

forgot to say that i did have uiautomationcore.dll in my main fsx folder, so have removed that to see if that helps. i also had microsoft security essentials installed when setting up my new laptop but have uninstalled that for now. bit of a memory hog by all accounts.

[Jim Young 2,356]

Screen 1.  You have your resolution set at 16 bit.  Have you tried 32 bit resolution?  (your desktop has to be set at 32 bit too).  Perhaps it was at 32 bit since you did not change over to the installed video card?  Filtering should be Ansiotrophic not Trilinear.

 

Screen 2.  Your Scenery settings are horrible.  I would suspect even the default settings (the one's when you first installed fsx) are higher.  Dense autogen means fsx will crash on most systems.  Even on my high powered system, dense is too high.

 

Screen 3.  This one is a major problem.  Clouds are a major fps killer.  They also destroy system memory.  Your cloud draw distance should be no higher than 60 miles.

 

So no problems with the rest of the FSX settings.

 

REX screen:  I see no problems with the settings except:

 

Cirrus Cloud resolution should be 1024.  Water too.  And wave animation should be 32 bit.

 

Fraps is a memory hog too and you are lucky to see 28 fps. 

 

I don't know your system specs.  You have a laptop so that means you probably don't have anything really powerful for this game.  However, computers have gotten much better since when FSX was first released in 2006 and are at least 2-3 times more powerful.  I would run fsx with mainly the default fsx settings.  The only thingy that Microsoft messed up on when they figured out default settings for a computer was the resolution.  It is usually not set at the highest resolution available for your computer (or what your desktop is set at) so you need to adjust that.  Max settings does not mean you'll see the best graphics.  In fact, it could result in the worst graphics.

 

Once you get your CTD figured out, I would recommend you post your screenies in the FSX forum and ask for suggestions.  In our Hardware Forum there are many different system configurations and settings that you might want to take a look at.  Remember, no one can help you if you do not provide your system specs (see my system specs in the sidebar under My PC).  You can set those up in your profile.

 

Hope this helps.

 

Best regards,

Jim

[alphabetagaga 0]

thanks again jim. i'll work through your reply, adjust as necessary and report back. for now i've simply uninstalled microsoft security essentials and deleted uiautomationcore.dll from the main fsx folder. after getting rid of those 2 things, i only had time left for a short flight last night in the stock 172 and happy to say i did not get a ctd.

 

i've also posted in the hardware thread to see what others say.