Mr. Midnight

2600k @4.2 , w7 64 , 285 gtx vid card, 2 tera Hello folks seem my sim is locking up again , and im wondering where its not working right. I had to reload FSX again , and did all the updates and tips and tricks. itsna hit and miss when it locks up. here is a log as soon as it locked up. Im suspecting a vid card problem , just added a extra vid card to the system , that may be a problem but not for sure. Thanks Robert Version=1 EventType=APPCRASH EventTime=130118358110510725 ReportType=2 Consent=1 ReportIdentifier=4f9688dc-b1e8-11e2-a14d-1c6f65d549d0 IntegratorReportIdentifier=4f9688db-b1e8-11e2-a14d-1c6f65d549d0 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=nvwgf2um.dll Sig[4].Name=Fault Module Version Sig[4].Value=9.18.13.1422 Sig[5].Name=Fault Module Timestamp Sig[5].Value=51427a06 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=001dec12 DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.1.7601.2.1.0.256.1 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 UI[2]=D:\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]=D:\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.762_none_0c178a139ee2a7ed\MFC80.DLL LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\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.17514_none_ec83dffa859149af\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.762_none_43efccf17831d131\MFC80ENU.DLL LoadedModule[60]=D:\FSX\language.dll LoadedModule[61]=D:\FSX\API.DLL LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\MSVCP80.dll LoadedModule[63]=D:\FSX\ablscpt.dll LoadedModule[64]=D:\FSX\flight.dll LoadedModule[65]=D:\FSX\ai_player.dll LoadedModule[66]=D:\FSX\acontain.dll LoadedModule[67]=D:\FSX\controls.dll LoadedModule[68]=C:\Windows\system32\DINPUT8.dll LoadedModule[69]=D:\FSX\fsui.dll LoadedModule[70]=D:\FSX\atc.dll LoadedModule[71]=D:\FSX\facilities.dll LoadedModule[72]=D:\FSX\demo.dll LoadedModule[73]=D:\FSX\main.dll LoadedModule[74]=D:\FSX\fe.dll LoadedModule[75]=D:\FSX\util.dll LoadedModule[76]=D:\FSX\simprop.dll LoadedModule[77]=D:\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]=D:\FSX\g3d.dll LoadedModule[83]=D:\FSX\panels.dll LoadedModule[84]=D:\FSX\multiplayer.dll LoadedModule[85]=D:\FSX\ui.dll LoadedModule[86]=D:\FSX\sound.dll LoadedModule[87]=D:\FSX\sim1.dll LoadedModule[88]=D:\FSX\simscheduler.dll LoadedModule[89]=D:\FSX\visualfx.dll LoadedModule[90]=D:\FSX\window.dll LoadedModule[91]=D:\FSX\terrain.dll LoadedModule[92]=D:\FSX\weather.dll LoadedModule[93]=C:\Windows\system32\DSOUND.dll LoadedModule[94]=C:\Windows\system32\POWRPROF.dll LoadedModule[95]=D:\FSX\symmap.dll LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll LoadedModule[97]=C:\Windows\system32\MSIMG32.dll LoadedModule[98]=D:\FSX\xuipc.dll LoadedModule[99]=D:\FSX\livingwater.dll LoadedModule[100]=D:\FSX\fs-traffic.dll LoadedModule[101]=D:\FSX\gps.dll LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll LoadedModule[104]=C:\Program Files (x86)\Matrox Graphics\PowerDesk\Matrox.PDesk.Hooks.dll LoadedModule[105]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[106]=C:\Windows\system32\WTSAPI32.dll LoadedModule[107]=C:\Windows\system32\newdev.dll LoadedModule[108]=C:\Windows\system32\devrtl.DLL LoadedModule[109]=C:\Windows\system32\CRYPTSP.dll LoadedModule[110]=C:\Windows\system32\rsaenh.dll LoadedModule[111]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[112]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[113]=C:\Windows\syswow64\MSASN1.dll LoadedModule[114]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[115]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[116]=C:\Windows\system32\wbemcomn.dll LoadedModule[117]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[118]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[119]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[120]=C:\Windows\system32\NTDSAPI.dll LoadedModule[121]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[122]=C:\Windows\system32\dxgi.dll LoadedModule[123]=C:\Windows\system32\d3d10.dll LoadedModule[124]=C:\Windows\system32\d3d10core.dll LoadedModule[125]=C:\Windows\system32\d3d11.dll LoadedModule[126]=C:\Windows\system32\nvd3dum.dll LoadedModule[127]=C:\Windows\system32\nvwgf2um.dll LoadedModule[128]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[129]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[130]=C:\Windows\system32\d3d10_1.dll LoadedModule[131]=C:\Windows\system32\d3d10_1core.dll LoadedModule[132]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.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]=D:\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]=D:\FSX\WidevieW\wideview.dll LoadedModule[160]=C:\Windows\system32\WSOCK32.dll LoadedModule[161]=D:\FSX\wideview\simconnect.dll LoadedModule[162]=D:\FSX\Widetraffic\widetraffic.dll LoadedModule[163]=D:\FSX\widetraffic\simconnect.dll LoadedModule[164]=D:\FSX\Modules\FSUIPC4.dll LoadedModule[165]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[166]=C:\Windows\system32\WINNSI.DLL LoadedModule[167]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[168]=C:\Windows\syswow64\imagehlp.dll LoadedModule[169]=C:\Windows\system32\ncrypt.dll LoadedModule[170]=C:\Windows\system32\bcrypt.dll LoadedModule[171]=C:\Windows\SysWOW64\bcryptprimitives.dll LoadedModule[172]=C:\Windows\system32\GPAPI.dll LoadedModule[173]=C:\Windows\system32\cryptnet.dll LoadedModule[174]=C:\Windows\syswow64\WLDAP32.dll LoadedModule[175]=C:\Windows\system32\SensApi.dll LoadedModule[176]=D:\FSX\Modules\A2A_Feel.dll LoadedModule[177]=C:\Windows\SysWow64\XAudio2_6.dll LoadedModule[178]=D:\FSX\Modules\AccuFeelMenu.dll LoadedModule[179]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll LoadedModule[180]=D:\FSX\Modules\LVLD.dll LoadedModule[181]=D:\FSX\Level-D Simulations\B767-300\leveld.dll LoadedModule[182]=C:\Windows\SysWOW64\ieframe.dll LoadedModule[183]=C:\Windows\SysWOW64\api-ms-win-downlevel-shlwapi-l2-1-0.dll LoadedModule[184]=C:\Windows\SysWOW64\api-ms-win-downlevel-advapi32-l2-1-0.dll LoadedModule[185]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll LoadedModule[186]=C:\Windows\system32\Secur32.dll LoadedModule[187]=C:\Windows\SysWOW64\mshtml.dll LoadedModule[188]=D:\FSX\GAUGES\LVLD\B767oh.GAU LoadedModule[189]=D:\FSX\GAUGES\LVLD\B767main.GAU LoadedModule[190]=D:\FSX\GAUGES\LVLD\B767Afds.GAU LoadedModule[191]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SimConnect.dll LoadedModule[192]=D:\FSX\GAUGES\LVLD\B767at.GAU LoadedModule[193]=D:\FSX\TCAS2v7.dll LoadedModule[194]=D:\FSX\GAUGES\LVLD\B767FMC.GAU LoadedModule[195]=D:\FSX\gauges\LVLD\fmcxml.gau LoadedModule[196]=D:\FSX\GAUGES\LVLD\B767ehsi.GAU LoadedModule[197]=D:\FSX\GAUGES\LVLD\B767eadi.GAU LoadedModule[198]=D:\FSX\GAUGES\LVLD\B767eicas.GAU LoadedModule[199]=D:\FSX\GAUGES\LVLD\B767leicas.GAU LoadedModule[200]=D:\FSX\GAUGES\LVLD\B767Overhead.GAU LoadedModule[201]=D:\FSX\GAUGES\LVLD\B767pedestal.GAU LoadedModule[202]=D:\FSX\GAUGES\LVLD\B767Radios.GAU LoadedModule[203]=D:\FSX\GAUGES\RCB_Groundhandling5_Sound.DLL LoadedModule[204]=C:\Windows\system32\msimtf.dll LoadedModule[205]=C:\Windows\system32\msls31.dll LoadedModule[206]=C:\Windows\system32\d2d1.dll LoadedModule[207]=C:\Windows\system32\DWrite.dll LoadedModule[208]=C:\Windows\system32\D3D10Warp.dll LoadedModule[209]=C:\Windows\system32\MLANG.dll LoadedModule[210]=C:\Windows\system32\ntmarta.dll LoadedModule[211]=C:\Windows\SysWOW64\uiautomationcore.dll LoadedModule[212]=C:\Windows\system32\msadp32.acm Sec[0].Key=LCID Sec[0].Value=1033 FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Microsoft® Flight Simulator X AppPath=D:\FSX\fsx.exe

My friend i did as you ask by updating microsoft visual and i have flown three flights without a hint of problems , just got done with a 9 hour flight . i did not even know a ctd even was a forum , Just to let you know all is well for now , its flying real smooth now . Thanks....................Again.................Robert

Cannot enjoy my sim due to this on going problem , i have done it all from moving this to that and from here to there. been dealing with this for sometime . Done all the tweeks that can be done from nick to byote and more. im out of fixes. Thanks Robert Version=1 EventType=APPCRASH EventTime=130100205679164000 ReportType=2 Consent=1 ReportIdentifier=de5c1e11-a165-11e2-af31-1c6f65d549d0 IntegratorReportIdentifier=de5c1e10-a165-11e2-af31-1c6f65d549d0 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.17725 Sig[5].Name=Fault Module Timestamp Sig[5].Value=4ec49b8f 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.256.1 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 UI[2]=D:\FSX-2013\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]=D:\FSX-2013\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.42_none_d6c3e7af9bae13a2\MFC80.DLL LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\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.17514_none_ec83dffa859149af\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.42_none_0e9c2a8d74fd3ce6\MFC80ENU.DLL LoadedModule[60]=D:\FSX-2013\language.dll LoadedModule[61]=D:\FSX-2013\API.DLL LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\MSVCP80.dll LoadedModule[63]=D:\FSX-2013\ablscpt.dll LoadedModule[64]=D:\FSX-2013\flight.dll LoadedModule[65]=D:\FSX-2013\ai_player.dll LoadedModule[66]=D:\FSX-2013\acontain.dll LoadedModule[67]=D:\FSX-2013\controls.dll LoadedModule[68]=C:\Windows\system32\DINPUT8.dll LoadedModule[69]=D:\FSX-2013\fsui.dll LoadedModule[70]=D:\FSX-2013\atc.dll LoadedModule[71]=D:\FSX-2013\facilities.dll LoadedModule[72]=D:\FSX-2013\demo.dll LoadedModule[73]=D:\FSX-2013\main.dll LoadedModule[74]=D:\FSX-2013\fe.dll LoadedModule[75]=D:\FSX-2013\util.dll LoadedModule[76]=D:\FSX-2013\simprop.dll LoadedModule[77]=D:\FSX-2013\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]=D:\FSX-2013\g3d.dll LoadedModule[83]=D:\FSX-2013\panels.dll LoadedModule[84]=D:\FSX-2013\multiplayer.dll LoadedModule[85]=D:\FSX-2013\ui.dll LoadedModule[86]=D:\FSX-2013\sound.dll LoadedModule[87]=D:\FSX-2013\sim1.dll LoadedModule[88]=D:\FSX-2013\simscheduler.dll LoadedModule[89]=D:\FSX-2013\visualfx.dll LoadedModule[90]=D:\FSX-2013\window.dll LoadedModule[91]=D:\FSX-2013\terrain.dll LoadedModule[92]=D:\FSX-2013\weather.dll LoadedModule[93]=C:\Windows\system32\DSOUND.dll LoadedModule[94]=C:\Windows\system32\POWRPROF.dll LoadedModule[95]=D:\FSX-2013\symmap.dll LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll LoadedModule[97]=C:\Windows\system32\MSIMG32.dll LoadedModule[98]=D:\FSX-2013\xuipc.dll LoadedModule[99]=D:\FSX-2013\livingwater.dll LoadedModule[100]=D:\FSX-2013\fs-traffic.dll LoadedModule[101]=D:\FSX-2013\gps.dll LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll LoadedModule[104]=C:\Windows\system32\CRYPTSP.dll LoadedModule[105]=C:\Windows\system32\rsaenh.dll LoadedModule[106]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[107]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[108]=C:\Windows\syswow64\MSASN1.dll LoadedModule[109]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[110]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[111]=C:\Windows\system32\wbemcomn.dll LoadedModule[112]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[113]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[114]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[115]=C:\Windows\system32\NTDSAPI.dll LoadedModule[116]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[117]=C:\Windows\system32\nvd3dum.dll LoadedModule[118]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[119]=C:\Windows\SysWOW64\dxgi.dll LoadedModule[120]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[121]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[122]=C:\Windows\SysWOW64\d3d11.dll LoadedModule[123]=C:\Windows\SysWOW64\d3d10_1.dll LoadedModule[124]=C:\Windows\SysWOW64\d3d10_1core.dll LoadedModule[125]=C:\Windows\system32\winbrand.dll LoadedModule[126]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[127]=C:\Windows\system32\WINSTA.dll LoadedModule[128]=C:\Windows\SysWOW64\gameux.dll LoadedModule[129]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[130]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[131]=C:\Windows\SysWOW64\wer.dll LoadedModule[132]=C:\Windows\System32\Wpc.dll LoadedModule[133]=C:\Windows\System32\wevtapi.dll LoadedModule[134]=C:\Windows\System32\msxml6.dll LoadedModule[135]=C:\Windows\system32\SAMLIB.dll LoadedModule[136]=C:\Windows\system32\netutils.dll LoadedModule[137]=C:\Windows\System32\MMDevApi.dll LoadedModule[138]=C:\Windows\System32\PROPSYS.dll LoadedModule[139]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[140]=C:\Windows\system32\RICHED20.DLL LoadedModule[141]=C:\Windows\system32\HID.DLL LoadedModule[142]=C:\Windows\system32\XInput9_1_0.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]=C:\Windows\system32\dinput.DLL LoadedModule[149]=C:\Windows\System32\wship6.dll LoadedModule[150]=C:\Windows\System32\wshtcpip.dll LoadedModule[151]=D:\FSX-2013\Widetraffic\widetraffic.dll LoadedModule[152]=C:\Windows\system32\WSOCK32.dll LoadedModule[153]=D:\FSX-2013\widetraffic\simconnect.dll LoadedModule[154]=D:\FSX-2013\AEMODULE.dll LoadedModule[155]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[156]=D:\FSX-2013\WidevieW\wideview.dll LoadedModule[157]=D:\FSX-2013\wideview\simconnect.dll LoadedModule[158]=D:\FSX-2013\Modules\LVLD.dll LoadedModule[159]=D:\FSX-2013\Level-D Simulations\B767-300\leveld.dll LoadedModule[160]=D:\FSX-2013\Modules\A2A_Feel.dll LoadedModule[161]=C:\Windows\SysWow64\XAudio2_6.dll LoadedModule[162]=D:\FSX-2013\Modules\AccuFeelMenu.dll LoadedModule[163]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll LoadedModule[164]=D:\FSX-2013\Modules\FSUIPC4.dll LoadedModule[165]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[166]=C:\Windows\system32\WINNSI.DLL LoadedModule[167]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[168]=C:\Windows\syswow64\imagehlp.dll LoadedModule[169]=C:\Windows\system32\ncrypt.dll LoadedModule[170]=C:\Windows\system32\bcrypt.dll LoadedModule[171]=C:\Windows\SysWOW64\bcryptprimitives.dll LoadedModule[172]=C:\Windows\system32\GPAPI.dll LoadedModule[173]=C:\Windows\system32\cryptnet.dll LoadedModule[174]=C:\Windows\syswow64\WLDAP32.dll LoadedModule[175]=C:\Windows\system32\SensApi.dll LoadedModule[176]=C:\Windows\SysWOW64\ieframe.dll LoadedModule[177]=C:\Windows\SysWOW64\api-ms-win-downlevel-shlwapi-l2-1-0.dll LoadedModule[178]=C:\Windows\SysWOW64\api-ms-win-downlevel-advapi32-l2-1-0.dll LoadedModule[179]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll LoadedModule[180]=C:\Windows\system32\Secur32.dll LoadedModule[181]=C:\Windows\SysWOW64\mshtml.dll LoadedModule[182]=D:\FSX-2013\GAUGES\LVLD\B767oh.GAU LoadedModule[183]=D:\FSX-2013\GAUGES\LVLD\B767main.GAU LoadedModule[184]=D:\FSX-2013\GAUGES\LVLD\B767Afds.GAU LoadedModule[185]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SimConnect.dll LoadedModule[186]=D:\FSX-2013\GAUGES\LVLD\B767at.GAU LoadedModule[187]=D:\FSX-2013\TCAS2v7.dll LoadedModule[188]=D:\FSX-2013\GAUGES\LVLD\B767FMC.GAU LoadedModule[189]=D:\FSX-2013\gauges\LVLD\fmcxml.gau LoadedModule[190]=D:\FSX-2013\GAUGES\LVLD\B767ehsi.GAU LoadedModule[191]=D:\FSX-2013\GAUGES\LVLD\B767eadi.GAU LoadedModule[192]=D:\FSX-2013\GAUGES\LVLD\B767eicas.GAU LoadedModule[193]=D:\FSX-2013\GAUGES\LVLD\B767leicas.GAU LoadedModule[194]=D:\FSX-2013\GAUGES\LVLD\B767Overhead.GAU LoadedModule[195]=D:\FSX-2013\GAUGES\LVLD\B767pedestal.GAU LoadedModule[196]=D:\FSX-2013\GAUGES\LVLD\B767Radios.GAU LoadedModule[197]=D:\FSX-2013\GAUGES\RCB_Groundhandling5_Sound.DLL LoadedModule[198]=C:\Windows\system32\msimtf.dll LoadedModule[199]=C:\Windows\system32\msls31.dll LoadedModule[200]=C:\Windows\system32\d2d1.dll LoadedModule[201]=C:\Windows\system32\DWrite.dll LoadedModule[202]=C:\Windows\system32\D3D10Warp.dll LoadedModule[203]=C:\Windows\system32\MLANG.dll LoadedModule[204]=C:\Windows\system32\ntmarta.dll LoadedModule[205]=C:\Windows\system32\msadp32.acm LoadedModule[206]=D:\FSX-2013\GoFlight\GFDEV.DLL LoadedModule[207]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[208]=C:\Windows\SysWOW64\msxml4.dll Sec[0].Key=LCID Sec[0].Value=1033 FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Microsoft® Flight Simulator X AppPath=D:\FSX-2013\fsx.exe

hello folks im having trouble loading a simroutes flight plan into level d.i generated a routes and loaded the plan into the level d folder navdata\ flightplans in vista , but the fsx fmc will not reconize.sim routes says to load the rte file into fms by clicking the route button on the fms and then click the third button on the right which is the co routes. and then hit the exec button.not happening.im sure im in the right directory in vista.program files \ microsoft\ fsx\level d\navdata\flightplans in vista.what am i doing wrong , perhaps the wrong folder.thanks........Robert

im not for sure yet , but i have been looking at the cessna 182 skylane 11 rg.so if i buy that plane i will not need peter dowson software.thanks.............Robert

i want to add a cessna 182 will i need ,FSUIPC FROM PETER DOWSON.it been awhile for me.im surprized that the Gold addition does not come with one.thanks..............Robert

Thanks for the reply , are you saying that i have to overclocked the chip, and 3.4 is not enough, wow. never thought id have to do that for this chip i thought was powerful enough as it is.Well i guess im in the overclocking busness now with FSX.I will give it a try and thanks..............................................................Robert

Mike -t im highly impressed on your set up , more than you know.i have a 2600k cooled by the new H-60gigabyte ud38 gig of patriot 1600 mem pny 285 GTX 10241 terra hd1 320 hdantec 1200 PSi ran all test cpu runs 29c 60c maxedi loaded w7 on the terra drive.i have a brand new copy of FSX gold addition.what do i do next to get even half of what your getting.so far after loading i did not get even to 40 fps, so im positive i did somthing wrong.so right now im looking at a com ready to load fsx.i need help Mike T.Thanks.....................Robert

Well once again i have been flying sims and this one for about four years , i pesonally dont believe you folks with your slyders all the way up, if you are you are flying judt default planes.im sorry if i make some of you folks mad , ive done it all, maybe im missing somthing here , maybe im just doing it all wrong for 16 -17 years.i have been flying these sims for a very long time and fsx is the worst of them , as a good product.i must be expexting to much out of this sim, i thought you just load the sim and run , you know just like every other piece of software.i did not know that after you buy there product you were suppose to go out and get all new equiptment to run it.i did not know you were suppose to tweak it to death just to get normal fps.i did not know that after 5 years with this software , and going out again to get a better com , and still deal with this problem.you folks are the best in the world then ,my experiance over the years mean nothing to this software.im sorry folks i have searhed high and low and there is no one out there that can tell me why this frickin software on todays fast super overcloced , mega ram holding supercharged computers run like a piece of the worst made sim software in my humble opinion.so fo you guys making the claim that you have your slyders all the way up , including bloom ,means that you are running mostly default.there is no way you can run what i put on my sim and get what you good folks claim.if you are running level -d , radar contac, flightsim commander, fuipc, ASX, genx, EB flight bag, i have several cities software, (and im sure i forgot a few all these and more to enchanc the game.)if new generation chips that are much faster than before , you are telling me that i have to accept the best i can get is this.i have done it all , now im being told not to do the tweeks, and now i have to make dummy folders for this software.there is no software that i know of that takes this much crap to run it. i have spent several thousands of dollars with little resultsand this new ******* tweek oh that one is real funny , to get his 30 % i have to give up my 5 monitors , and other things.everybody once to let microsoft off of the hook, they made a bad product and im sick and tired of tring to figure out how to get it to run normal.and for those making that claim that your fsx is maxed out , im sorry i dont believe you , unless you are running default planes.if you can run all this software and have all slyders up , i need to know the exact spects of your com , so that i can go out and get the parts.if fs9 could do all that, 20004, 2002, why not FSX , we certanly have the power, just bad program writers.i truly hope that flight is a better made software than fsx , in fact im sure that flight is the answer to FSX as W7 was the answer to vista.I have flown x-plane back in the day , but it was no comparison to FS9 and all the stuff i added to it.im thinking of going back to X-plane and use my great set up , and put on the shelf for now all of my FSX add-onns and wait for flight , perhaps X-plane has become a better product.at least X-plane will treat my system with respect and i wont have to tweek it to death just to have fun.Thanks..................................Robert

i feel your pain and i congradulate you folks on having your set up with your slyders all the way up with your several hunders dollar video cards and super cpu,s.im not mocking no one here , im just saying i feel the guys pain , for me fsx has been a bear, i guess my problem is that i was expacting better computer to software ratio.with fs9 i could turn every thing up and add a ton a nd i mean a ton of software , networked or on the main com.even during that day i was paying 400+ for a video card and that made everything better.Not with fsx , vid cards meant nothing to this Sim , it wanted raw power few had at the time.so everybody upgraded to whatever they deemed nessacery.and guess what that even was not enough. at least for me it wasnt.i cannot use FSX just out of the box , i must use it if not all of the third party software (radar contact, ASX, level d 767 etc. )to run it.multi monitors and all the fixins.You know if you folks out there are running it the way you want it to run , i say hats off to you , and i really mean that honestly.but to me after five years and you now have chips going so fast and video cards , and still right out of thr box , vanilla using default planes the frame rate should be off the chain , and i mean like over a hundred and upwards .i have heard of some of you good folks getting that or so i heard .my new set up.W7 64 ultimatei7 2600k with a corsair watercooled H-60 , temps are the best i have ever had 28c to 59c max full load.patriot 16 gig 1600 PNY gtx 285 vid card ....there is no need to upgrade any further on vid cards until i master what i have , every card i have ever owned and still do cost me over 400+ dollars.if fact i put the gtx 9800 card in first to set up every thing on the sim , the results were with all slyders up including boom i got around 35 fps with a default 172 cessna. i then change to a more powerful card the pny gtx 285 and the fps were about the same , maybe 5 frames or less than the other card.Im using a gigabyte board new and fresh out the box, everything is new , even the tecnology is new, to me the sim should just about jump off the screen with so much power under the hood. i have been at this for twnty plus years Fsx has been the hardest to tame for me.Once again im speaking only for myself and perhaps one or two more:).i have tweeked , and then tweeked and then when i was done i did the super tweeks from all the top guns in tweeking and now im about to do what the now famed ******* tweeks , as we speak , once again FSX is making me jump thru the hoops just for a couple of frames or more .i love the sim though for it is so real when you have every thing up and runnig , i cannot go back to just one screen or just flying staight out of the box. i have been at this simming for about twenty years . i go way back when X - plane was just and x on the screen :).98. 2000, 2002, 2004, FSX . So for you folks outthere that are running it with great specs i hope to get those sams results soon after i tackle this next super tweek.So my friend i feel your pain , and once again i love this sim , it has become a love and hate relationship with this software.You know what i like to see is with the system i have now i want to see 50 + fps with all the extra software loaded , the whole nine yards.if i could get with fs9 45+ or more , and with my last system e8500 , running FSX i was only getting with all the fixins 16 to 24 fps depending on where you were.with what i got now i should see 50+ fps if not close to a hundred. im not impressed at all with these chips , even the thousand dollar one , you mean i have to go out and buy that to get my 50+ or more fully loaded. All i want is the right system to run FSX after five years or so with all slyders up and with all the fixins , if there is not a system outhere that can , does that mean that it was not written well, or if there is a machine that can blow it away with no trouble please let me know.if what i have is not enough , then what is.w7 ultimate 64i72600kcorsair H-60PNY 285 GTX 102416 gig corsair 1600 mem1.5 terra HD1200 antec PWsony Blu-ray playerHit dvd playerThank you Good Folks For Listening............Robert

The last post is most correct , if you do not load the sp updates and follow the rules on the fsx version you have you are in for a big headache, no matter what system you have.your new system is raw and needs to be tweeked , and all updates need to be loaded.Motherboard, video card, etc.get rid of all extra garbage you dont need on your new system.once your convinced your system is ready and tuned to go.start loading fsx and all of the update sp,s in the correct order, restart each time.once loaded i run fsx and start my set up , but first i run fsx with a default plane , and you will notice with your fast vid card your frame rate is real high.you will be happy for a short while until your com regulates all the sytems and then it will start to lower to a happy medium.say a good 65 fps under defaut planes .but when you start loading add,ons that number lowers.you have a great system , but you first need to attend to your engine and tune it up and prepare it for fsx , some new systems do well on start up , but most dont.there are several websites that can help you , in not at my main com to give you any , but im sure there are some folks in here that can help.Good luck..............Robert

On the TRAKE EIGHT ARRIVAL chart above, ATC has issued you clearance to "Descend at pilots discretion to cross KAYLA at One-One Thousand (11,000 FT MSL)". You are flying at FL290 (29,000 FT MSL), your aircraft has an approximate groundspeed of 300 nautical miles per hour and your aircraft has a standard descent rate of 2,000 FT per minute.Approximately how many nautical miles away from KAYLA would be the minimum distance that you should start your "Top of Descent" to cross KAYLA at 11,000 FT MSL and how many minutes will this take?also i have to be at 250 kts when i arrive at kaylaA: 30 Nautical Miles and 6 Minutes.B: 45 Nautical Miles and 9 Minutes.C: 60 Nautical Miles and 12 Minutes.D: 75 Nautical Miles and 15 Minutes.hello folks im trying to take a open book test and the answer to the question i gave was c .that was the wrong answer .any help thanks...................Robert

your station database files cannot be updated.please make sure sharing is properly setup if using a networked configuration.im not for where else to go here i have turned on everything as far as sharing and mappiing.what are these data files they refer to.thanks.......................Robert

hello folks out there , i have just loaded ASE on another com and i ave done all of the networking and mapping.everything seems to be fine but now i get a : your database files could not be updated.i have all the files shared and mapped.what am i missing.Thanks....Robert

Hello folks out there i want to say that i have been at this simming for agreat while about 15 years.and i have built a lot of computers for myself and a few for otherrs mostly for myself.when i started simming i can remember my stumbling upon microsoft 98 , before that i remember alittle about X plane.the first thing i remember was that i had problems from freezing up and that was my first time attemps at vedio cards, putting in newer and better vids cards.youi know all those cards that we thought was the first kid on the block to get , and you could boast 20 30 fps.and when you got a better card you could get even more fps and turn most of if not all sliders up, because you get the latest and greatest.in fact dont you remember the great art work on the boxes.i could remember when microsoft came out with there latest simm and i would go out and update my cpu and vid casd and you were good to go.this pattern remained in practice for several years until fsx came out, fsx has caused me more headaches then any software i have cealt with.i have never had a bit of software that has had me go out and buy everything possible to get this software to work like software.i understand upgrading your com to a certain point , but this has become crazy, im still reading post and blogs and forums that still have problems with fsx.im taliking computers that will run the space shuttle , but when you load fsx , you might get lucky if it works right with out crashing.there are days when it will run good then there are days that you cannot even fly.im even hearing folks with super computers that will not run well.i have tweaked , repaired , uploaded , down loaded, bought, more ram , bigger HD, the best vid cards , prayed even and fsx still does what it wants to do.if you go on the forums now you will see folks wanting to know what rig will run FSX, and you will get a load of systems that claim to run FSX.i even see folks with the same set up with deferrent results.with these sims it has always been a vid problem not allways a cpu problem with me.now it is the other way around a cpu problem and not a vid problem, and im tired of the tweaking and not flying.i know there are folks out there that are flying with no problems , so they say, all i see is what i see in the forums.i believe it has been three years now and i still see people hating FSX, because of the hog that it is.as a long time user of simms i have a right to my opinion and FSX is like vista , overloaded with crap that demands attenion from everything on your computer.you gonna tell me that vid cards today cant run fsx well or cpu,s.im beginning to see why the ace teams is no more , because if i was there boss i would want to know why you developed a software that above average computers cant run.im at a stand still right now on what to do , i could stay with xp pro 64 and deal with 9 10 or 6 or 7 fps, depends on what town im in or the weather is like.or go with w7 64 and tweak from here until ******* comes back .w7 i cant even get to first base with FSX .im sure there are folks out there now wanting to know what is going on with mny system, and im thankful , but im at the point where im tired of all the hoops i have to jump through to just fly.i have been told that there is no computer that can run FSX with all sliders to max and that includes bloom.i say that that the softwhere folks ( ace team) needs to explain why that is so, why is it that even after three years there is not one com that i know of that can tell FSX that im the Boss not you.oh im sure you will have folks make that claim , oh im sure you will find those folks that will say my com will do it. and what you will have there are super tweakers, im tired of tweaking , im tired of hoping this cpu or vid card will work.So this is my last time that i will spend time on FSX.im going out and buy the best cpu out there , and im going to max out ram. the fastest hartd drive, the best MB on the market, this com will be the best and the most money ever spent on this next system.if FSX will not max out or at least go to 90 plus im through with FSX.IM going to spend my time With Mister Austin and his X plane , he may not be the best but he is consistent.I was playing with X plane first i guess i will go back.i know im going to get a lot of flax but im sorry if i offened anyone.To me FSX is Like Vista over Bloaded and a Computer Hog.im hoping that there is a company out there as we speak that is developing a good flightsim that runs like regular software is suppose to do.this is my opinion only.as i said im going to get cussed out for saying what i said.you folks have a good day.a fifteen year simmer ............Robert

Well you good folks out there I have a problem with w7 and fsx.I have been running fsx on xp pro 64 for about a couple of years and it has done well concidering with all of the add ons.I like many decided to upgrade to the new and latest system w7, and I heard good results.I went out and got the w7 64 ultimate, and loaded it with little effort, and then loaded fsx and loaded all of the latest sp1, sp2, and I loaded them in the correct way.This graphics card does not meet minimumrequirements for shader support. This product requires a geForce3/Radeon8500class or better graphics card. Flight Simulator will now exit."Also with sp1 I was able to get into fsx and choose setting and adjust a few sections, I also was able to choose a default 172, my frame rate (57 fps) was never that high before with xp (32 fps) with all the fixings.Then within a minute the sim would freeze and act sluggish and respond slowly and the counter is frozen at 52 fps.I will have to exit or three fingers it and restart the computer.I then would load sp2 and then restart the computer and then it gives me this ridiculous errorI have used cleaners to get old vid drivers out and the whole clean install process.And for some reason I cannot get fsx to play on my system, I have tried every thing possible to get it to work.My system = Intel e8500 dual core, 4 gigs ddr3, 280 HD, gtx.285 vid card.I know this machine can handle fsx, I know of systems with the same chip and vid card with great success.So I guess the question is fsx compatible to what I got , I do remember that when W7 was in its beta stage I tested fsx on w7 32 bit and it worked great, also tried it in the beta 64 bit and it worked but I did not have enough support drivers so I stayed with w732.But for some reason I cannot get it to work right on a boxed version of w7 64.Are there proper procedures that im missing?I have reloaded and formatted my drive several times.So I need some real technical assistance on what and why it won

thanks for the reply, i have done just that i never upgrade i get the full install versions.ive had w7 for about a month now and it is great , but as for getting my deluxe fsx to work is a challenge.its a hit and miss problem, some times it will load and some times it will just look at you and say what:).i have re loaded w7 so many times and formatted my drive , (the same with fsx ) that i do it with my eyes closed.it should not be this diffucult for me , my system is not that bad, it ran pretty good on xp pro 64 if , if not for the constant freesing it will run great in w7.so at this point im thinking that there is perhaps a step here im missing.as a matter of a fact im reloading w7 and formatting my hd as im posting here.as soon as itis finished i will then get all of the microsoft updates and load them.i even let the updater update my vid cards.after i get all updates for w7.i then put in disk 1 of the deluxe fsx load it until it ask for disk 2 i then load.when it is done i will start the sim and go to the default 172 . ( it is at this time that i will see if it will freeze , and it does after about 30 seconds or maybe 2 minutes.the frame rate is an astonishing 41 to 59 fps ( never seen that before ) then bam it will freeze at maybe 43 fps and i will be stuck and will have to exit the sim.i then go to nvidia and download the latest drivers and now its telling me , my card is not good enough.the things im going through to fly a sim.so as far as me loading and unloading im all ears on what to do to enjoy the sim like you folks on w7 64 .Thanks...........Robert

well know that i finally get fsx to half way work , as soon as i start the sim and go to a airport the sim freezes up.i thought maybe i needed updated drivers for my gtx 285, downloaded them and now of all things i get and error saying video card is not the right hardward and i need a card with shader.how can that be.i also put the fsx files in it own folder not in program files and i was able to get fsx to finally work a little.now i have a vid problem.help.............Robert

well folks im not for sure where to go from here, im frustrated on the performance of fsx and w7.my system is a e8500, 4 gig, 280 hd, vid gtx285.i did not like the frame rate in xp pr0 64 so i went out and got w7 64 ult.i like it but it does like fsx.i loaded the deluxe cd 1 of fsx, went through the loading process and then it ask for disk two , went thorugh that process and started the sim for the first time before i installed the first sp1 before i restart computer.when i started the sim, i opened it up and started the default plane.it opened up at a frame rate of 42 fps and then it froze up , nothing happened i would hit a key and it would react 15 seconds later or so.i exited out of the sim and loaded sp2 and restarted the computer.same thing happened again slow response of the sim and sometimes the sim would not even load, it would just sit there.now here is the funny part of this.i then go to start , all progarms to find fsx anf it is not there, in fact it is not even in the uninstall software area of the control panel.the only place i can find fsx on my computer is in c/, program files, microsoftgames, fsx, and that is the only area that shows that fsx is even on the computer.no desktop shortcuts or nothing. its not in all programs.on xp pro 64 it loade without a hitch and all folders showed up.i did a dump and load several times and i get the same results. i even reloaded w7 and the same thing over and over again.fsx will not run on my system with w7.intel dual core 2 e8500, 4 gigs ram, 280 hd, gtx nvid 285 1028 mem vid card.my system is not that bad and all i have is no shows with fsx and w7, as i said i do not know where to go from here other than going back to xp pro 64 and deal with 12 fps or lest with all of the add ons that i have .and besides i feel that upgrading to w7 to operate a sim that they made should work flawwlessly.so at this point i need some good advice on what to do , is there any one else out there with similar specs.oh and i have done all of the nicks tweaks over and over again.xp was good but i thought that w7 would be great fsx.w7 as a hold is great until i want to sim .Thanks..................................Robert

hhhmmm ive done that before and i can tell when it gives you the widerange view , but with the analog version of th2go it still looks strange.i will load w764 again and see if th2go will work better , im positive i have changed the false to true in the fsx.cfg files i just cant remember doing it in w7, so i will give it a try and let you know.Thanks.Robert

im not for i sure i follow you on that , what do you mean the fsx.cfg files what can you do to that file .are you saying i can run w764bit and th2go analog not digital and run fsx without that longated look to it.that would be nice.thanks....Robert

hello folks i have tried w7 and th2go and it looks great , but the only problem is that my th2go is analog and there are no drivers from matrox that will solve the fsx problem.with xp pro 64 bit they had software for wide screen viewing in the game with out the stretched look.w7 runs fsx preetry darn good but i will have to go back to xp pro 64 until i russell up three hundred for a digital th2go.unless someone can direct me to somewhere that might have drivers for a analog thh2go to work with w764.has any one gotten it to work with w7Thanks......Robert

Hello my friend i did as you recomended and that did the trick, i have nevr had to do it that way but its working flawlessly now very stable with the new drivers.thanks.........again......Robert

Hello i have been trying to get my go flight modules to work every since i downloaded the new software i cannot get it to work with the new 1.90.in fact all i have ever used was the 1.70 series and those drivers worked well for me.i also had trouble with the 1.80 series and went back to the 1.70.the go flight site is down and im wanting to put the older drivers back on , and i cannot seem to find then.and also why dont the new drivers 1.90 work for my system.xp 64 bit pro/ e8500/4 gig/260 goig hd.i have removed all older drivers and reloaded the new 1.90 and still nothing.on the config it will show the mods connected and i can program the keys and rotories to the level d plane and then save it .normally i will get a permission to load go flight in the fsx sim , but it does not happen this time.what am i doing wrong my good simmers.........Robert

Hello folks out there i have a problem with well everything at this point so i will deal wiith one prob at a time.me myself i enjoy fying my sim more than anything , it is a great passion to me to do this.i get frustrated when i spend more time tweaking than flying, but i guess that is the beast.what i need to know is that i just bought the w7 ul 64 b and i know that there are some great tweaks on how to get the most out of it.nicks tweaks i have a question on, is his tweaks for xp and vista and can i use his tweaks for w764.im sitting here all ready to go with a night of headaches to get my system up and running so that i can enjoy fsx.i have nicks tweaks but is it for w7.if not is there one out there that can get me the most to run fsx .i decided to go for it to stay up with the latest.right now im running xp64 and its all right if you can handle 9 to 10 fps with level d and all of the fixins.my main com i have xp64 running fsx,traffix x, gex, rex,leveld and various other addon planes.on the second com i network widfs, radar contac, asa, fscommander.like i said if you can deal with about 9 ,10 , maybe 11 or 12 fps on the ground and when im high up in the air well i will get and impressive 16 to 20 fps and at night it will get a whopping 19 , 20 fps.my system e8500 cpu, 4 gigs , 270hd,liton drive,ativa dvd drive.so im asking for some good ways to get it done right .Thanks......a long time simmer......Robert