January 23, 201313 yr Hi everybody, My computer was running very well but since about a month, i have many "fatal errors" and FPS has dropped considerably . Need advise please. Thank you and best regards. Here is my rig: CPU: i7 2700 3.5GHz 8MB:, MO ASUS Maximus 4 Extreme-Z,: Memory Corsair 8G DDR3 1866MHz, GPU: ASUS GTX580 1536MB, Cooling: Corsair H80, HD: HD 480GB SSD OCz, HDD Seagate 1T 7200RPM 32MB, Power Supply: Thermaltake 1000W, Windows 7 Pro 64bits. Real Deraps
January 23, 201313 yr Have you made any changes to your configuration (both hardware and software—new add-ons, computer components, etc.)? Otherwise, have you tried applying stability tweaks? Two essential stability tweaks many people recommend are: HIGHMEMFIX=1 in FSX.cfg, which largely eliminates aircraft graphics rendering (“skeleton”) issues. UIAutomationCore.dll in the FSX main folder, which largely eliminates memory insufficiency/usage errors (e.g., after long periods of flight, using menus too frequently, etc.). For specific instructions, please reference the appropriate sections of Word Not Allowed's Guide (use Find in your browser).
January 23, 201313 yr Author Thanks for replying Owen, Well, i've changed the SSD HD (from 240Gb to 480Gb) (made a "ghost") instead of a complete reinstallation. Also install FSDT Vancouver (CYVR), FT Montreal (CYUL). I can't remember if i've installed somethings else. (update for ORBX England). That's it i think. In my FSX.cfg, HIGHMEMFIX is set to 1 and i have the UIAutomationCore.dll in main FSX folder. I'm reading the Word Not Allowed's guide and try to see if i can change somethings. Thanks again. Real Deraps
January 23, 201313 yr This is an automatic message. This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons. The most likely reason is that the post was off topic. The topic could also have contained images or a video that were not appropriate to the original forum it was posted in. The images might not have been "illustrative" or "explanatory" in nature. The topic could have been moved because we deemed it to be more appropriately placed elsewhere. Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated. Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
January 23, 201313 yr You should download and run AppCrashView - http://www.nirsoft.net/utils/app_crash_view.html so we can see the latest CTD. You can copy and paste the report here. The uiautomationcore.dll in your main FSX folder only fixes Menu crashes (i.e., several clicks opening/closing the menu bar. If this is not happening, then the uiautomationcore.dll is not doing anything and you should remove it as it could be conflicting with other software. I'm not sure what you did in regards to moving something over to your new SSD (made a Ghost). What was moved? Everything on the old SSD including FSX and your OS? I ask this because FSX and FSX addons need certain versions of Microsoft Visual C++ Redistributable (2005 and 2005 w/SP1) and Versions 1.1, 2.0, and 3.5 of Microsoft.net in order for your applications to run properly. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
January 23, 201313 yr Author Thank you Jim. Everything on the old SSD including FSX and my OS was moved to the new SSD. I have downloaded and run the Appcrashview. Which report i have to copy here. Is it the text at the button of the page.? Anyways here is the text: ersion=1 EventType=APPCRASH EventTime=130033757025594269 ReportType=2 Consent=1 UploadTime=130033757026404315 ReportIdentifier=95f81d6f-64f6-11e2-940e-5404a6359278 IntegratorReportIdentifier=95f81d6e-64f6-11e2-940e-5404a6359278 WOW64=1 Response.type=4 Sig[0].Name=Nom de l’application Sig[0].Value=fsx.exe Sig[1].Name=Version de l’application Sig[1].Value=10.0.61637.0 Sig[2].Name=Horodatage de l’application Sig[2].Value=46fadb14 Sig[3].Name=Nom du module par défaut Sig[3].Value=atc.dll Sig[4].Name=Version du module par défaut Sig[4].Value=10.0.61637.0 Sig[5].Name=Horodateur du module par défaut Sig[5].Value=46fadb59 Sig[6].Name=Code de l’exception Sig[6].Value=c0000005 Sig[7].Name=Décalage de l’erreur Sig[7].Value=00024165 DynamicSig[1].Name=Version du système DynamicSig[1].Value=6.1.7601.2.1.0.256.48 DynamicSig[2].Name=Identificateur de paramètres régionaux DynamicSig[2].Value=3084 UI[2]=C:\FSX\fsx.exe UI[3]=A fatal error occurred. UI[4]=Windows peut rechercher une solution au problème en ligne et essayer de redémarrer le programme. UI[5]=Rechercher une solution en ligne et redémarrer le programme UI[6]=Rechercher ultérieurement une solution en ligne et fermer le programme UI[7]=Fermer le programme LoadedModule[0]=C:\FSX\fsx.exe LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll LoadedModule[2]=C:\Program Files\AVAST Software\Avast\snxhk.dll LoadedModule[3]=C:\Windows\syswow64\KERNEL32.dll LoadedModule[4]=C:\Windows\syswow64\KERNELBASE.dll LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL LoadedModule[6]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll LoadedModule[7]=C:\Windows\syswow64\msvcrt.dll LoadedModule[8]=C:\Windows\syswow64\GDI32.dll LoadedModule[9]=C:\Windows\syswow64\USER32.dll LoadedModule[10]=C:\Windows\syswow64\ADVAPI32.dll LoadedModule[11]=C:\Windows\SysWOW64\sechost.dll LoadedModule[12]=C:\Windows\syswow64\RPCRT4.dll LoadedModule[13]=C:\Windows\syswow64\SspiCli.dll LoadedModule[14]=C:\Windows\syswow64\CRYPTBASE.dll LoadedModule[15]=C:\Windows\syswow64\LPK.dll LoadedModule[16]=C:\Windows\syswow64\USP10.dll LoadedModule[17]=C:\Windows\syswow64\SHLWAPI.dll LoadedModule[18]=C:\Windows\syswow64\ole32.dll LoadedModule[19]=C:\Windows\system32\apphelp.dll LoadedModule[20]=C:\Windows\AppPatch\AcGenral.DLL LoadedModule[21]=C:\Windows\system32\UxTheme.dll LoadedModule[22]=C:\Windows\system32\WINMM.dll LoadedModule[23]=C:\Windows\system32\samcli.dll LoadedModule[24]=C:\Windows\syswow64\OLEAUT32.dll LoadedModule[25]=C:\Windows\system32\MSACM32.dll LoadedModule[26]=C:\Windows\system32\VERSION.dll LoadedModule[27]=C:\Windows\syswow64\SHELL32.dll LoadedModule[28]=C:\Windows\system32\sfc.dll LoadedModule[29]=C:\Windows\system32\sfc_os.DLL LoadedModule[30]=C:\Windows\system32\USERENV.dll LoadedModule[31]=C:\Windows\system32\profapi.dll LoadedModule[32]=C:\Windows\system32\dwmapi.dll LoadedModule[33]=C:\Windows\syswow64\SETUPAPI.dll LoadedModule[34]=C:\Windows\syswow64\CFGMGR32.dll LoadedModule[35]=C:\Windows\syswow64\DEVOBJ.dll LoadedModule[36]=C:\Windows\syswow64\urlmon.dll LoadedModule[37]=C:\Windows\syswow64\iertutil.dll LoadedModule[38]=C:\Windows\syswow64\WININET.dll LoadedModule[39]=C:\Windows\syswow64\Normaliz.dll LoadedModule[40]=C:\Windows\system32\MPR.dll LoadedModule[41]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[42]=C:\Windows\system32\WINSPOOL.DRV LoadedModule[43]=C:\Windows\AppPatch\AcSpecfc.DLL LoadedModule[44]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll LoadedModule[45]=C:\Windows\system32\mscms.dll LoadedModule[46]=C:\Windows\system32\DDRAW.dll LoadedModule[47]=C:\Windows\system32\DCIMAN32.dll LoadedModule[48]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[49]=C:\Windows\syswow64\IMM32.dll LoadedModule[50]=C:\Windows\syswow64\MSCTF.dll LoadedModule[51]=C:\Windows\syswow64\WS2_32.dll LoadedModule[52]=C:\Windows\syswow64\NSI.dll LoadedModule[53]=C:\Windows\system32\msi.dll LoadedModule[54]=C:\Windows\SysWOW64\nvinit.dll LoadedModule[55]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80FRA.DLL LoadedModule[56]=C:\FSX\language.dll LoadedModule[57]=C:\FSX\API.DLL LoadedModule[58]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[59]=C:\FSX\ablscpt.dll LoadedModule[60]=C:\FSX\flight.dll LoadedModule[61]=C:\FSX\ai_player.dll LoadedModule[62]=C:\FSX\acontain.dll LoadedModule[63]=C:\FSX\controls.dll LoadedModule[64]=C:\Windows\system32\DINPUT8.dll LoadedModule[65]=C:\FSX\fsui.dll LoadedModule[66]=C:\FSX\atc.dll LoadedModule[67]=C:\FSX\facilities.dll LoadedModule[68]=C:\FSX\demo.dll LoadedModule[69]=C:\FSX\main.dll LoadedModule[70]=C:\FSX\fe.dll LoadedModule[71]=C:\FSX\util.dll LoadedModule[72]=C:\FSX\simprop.dll LoadedModule[73]=C:\FSX\g2d.dll LoadedModule[74]=C:\Windows\system32\d3dx9_34.dll LoadedModule[75]=C:\Windows\system32\d3dx10_34.dll LoadedModule[76]=C:\Windows\system32\d3d9.dll LoadedModule[77]=C:\Windows\system32\d3d8thk.dll LoadedModule[78]=C:\FSX\g3d.dll LoadedModule[79]=C:\FSX\panels.dll LoadedModule[80]=C:\FSX\multiplayer.dll LoadedModule[81]=C:\FSX\ui.dll LoadedModule[82]=C:\FSX\sound.dll LoadedModule[83]=C:\FSX\sim1.dll LoadedModule[84]=C:\FSX\simscheduler.dll LoadedModule[85]=C:\FSX\visualfx.dll LoadedModule[86]=C:\FSX\window.dll LoadedModule[87]=C:\FSX\terrain.dll LoadedModule[88]=C:\FSX\weather.dll LoadedModule[89]=C:\Windows\system32\DSOUND.dll LoadedModule[90]=C:\Windows\system32\POWRPROF.dll LoadedModule[91]=C:\FSX\symmap.dll LoadedModule[92]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll LoadedModule[93]=C:\Windows\system32\MSIMG32.dll LoadedModule[94]=C:\FSX\xuipc.dll LoadedModule[95]=C:\FSX\livingwater.dll LoadedModule[96]=C:\FSX\fs-traffic.dll LoadedModule[97]=C:\FSX\gps.dll LoadedModule[98]=C:\Windows\system32\MSWSOCK.dll LoadedModule[99]=C:\Windows\system32\SHFOLDER.dll LoadedModule[100]=C:\Program Files (x86)\Common Files\Spigot\Search Settings\wth156.dll LoadedModule[101]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[102]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll LoadedModule[103]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.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\dxgi.dll LoadedModule[118]=C:\Windows\system32\nvd3dum.dll LoadedModule[119]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[120]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[121]=C:\Windows\system32\d3d10_1.dll LoadedModule[122]=C:\Windows\system32\d3d10_1core.dll LoadedModule[123]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[124]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[125]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[126]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[127]=C:\Windows\SysWOW64\d3d11.dll LoadedModule[128]=C:\Windows\system32\winbrand.dll LoadedModule[129]=C:\Windows\system32\nvapi.dll LoadedModule[130]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[131]=C:\Windows\system32\WINSTA.dll LoadedModule[132]=C:\Windows\SysWOW64\gameux.dll LoadedModule[133]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[134]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[135]=C:\Windows\SysWOW64\wer.dll LoadedModule[136]=C:\Windows\System32\Wpc.dll LoadedModule[137]=C:\Windows\System32\wevtapi.dll LoadedModule[138]=C:\Windows\System32\msxml6.dll LoadedModule[139]=C:\Windows\system32\SAMLIB.dll LoadedModule[140]=C:\Windows\system32\netutils.dll LoadedModule[141]=C:\FSX\uiautomationcore.dll LoadedModule[142]=C:\Windows\system32\OLEACC.dll LoadedModule[143]=C:\Windows\System32\MMDevApi.dll LoadedModule[144]=C:\Windows\System32\PROPSYS.dll LoadedModule[145]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[146]=C:\Windows\system32\RICHED20.DLL LoadedModule[147]=C:\Windows\system32\HID.DLL LoadedModule[148]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[149]=C:\Windows\system32\wdmaud.drv LoadedModule[150]=C:\Windows\system32\ksuser.dll LoadedModule[151]=C:\Windows\system32\AVRT.dll LoadedModule[152]=C:\Windows\system32\msacm32.drv LoadedModule[153]=C:\Windows\system32\midimap.dll LoadedModule[154]=C:\Windows\system32\dinput.DLL LoadedModule[155]=C:\Windows\System32\wship6.dll LoadedModule[156]=C:\Windows\System32\wshtcpip.dll LoadedModule[157]=C:\FSX\bglmanx.dll LoadedModule[158]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[159]=C:\Windows\system32\inetmib1.dll LoadedModule[160]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[161]=C:\Windows\system32\WINNSI.DLL LoadedModule[162]=C:\Windows\system32\snmpapi.dll LoadedModule[163]=C:\FSX\ORBX\FTX_NA\FTX_AA_CYBD\Scenery\ObjectFlow_CYBD.dll LoadedModule[164]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll LoadedModule[165]=C:\FSX\ORBX\FTX_NA\FTX_AA_KCMW\Scenery\ObjectFlow_KCMW.dll LoadedModule[166]=C:\FSX\ORBX\FTX_NA\FTX_AA_KBVS\Scenery\Objectflow_KBVS.dll LoadedModule[167]=C:\FSX\ORBX\FTX_NA\FTX_AA_PAKT\Scenery\ObjectFlow_PAKT.dll LoadedModule[168]=C:\FSX\ORBX\FTX_AU\FTXAA_YBCS\scenery\ObjectFlow_YBCS.dll LoadedModule[169]=C:\FSX\ORBX\FTX_AU\FTXAA_YMML\Scenery\ObjectFlow_YMML.dll LoadedModule[170]=C:\FSX\ORBX\FTX_AU\FTXAA_YBAS\Scenery\ObjectFlow_YBAS.dll LoadedModule[171]=C:\FSX\ORBX\FTX_NA\FTX_AA_CZST\Scenery\ObjectFlow_CZST.dll LoadedModule[172]=C:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll LoadedModule[173]=C:\Windows\system32\MSVCR100.dll LoadedModule[174]=C:\FSX\FeelThere\E170\EJetH.dll LoadedModule[175]=C:\FSX\VistaMare\ViMaCoreX.dll LoadedModule[176]=C:\FSX\VistaMare\bin\VMCX_AP.dll LoadedModule[177]=C:\FSX\VistaMare\bin\ViMaNET_AP.dll LoadedModule[178]=C:\FSX\Aerosoft\Flight Recorder\AS-FlightRecorder.dll LoadedModule[179]=C:\FSX\RAASPRO\RAASPRO.dll LoadedModule[180]=C:\Windows\system32\Secur32.dll LoadedModule[181]=C:\Windows\system32\dnsapi.DLL LoadedModule[182]=C:\Windows\system32\RASAPI32.dll LoadedModule[183]=C:\Windows\system32\rasman.dll LoadedModule[184]=C:\Windows\system32\rtutils.dll LoadedModule[185]=C:\Windows\system32\sensapi.dll LoadedModule[186]=C:\Windows\system32\NLAapi.dll LoadedModule[187]=C:\Windows\system32\rasadhlp.dll LoadedModule[188]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL LoadedModule[189]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll LoadedModule[190]=C:\Windows\System32\fwpuclnt.dll LoadedModule[191]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SimConnect.dll LoadedModule[192]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll LoadedModule[193]=C:\Windows\system32\MSDART.DLL LoadedModule[194]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll LoadedModule[195]=C:\Windows\system32\bcrypt.dll LoadedModule[196]=C:\Program Files (x86)\Common Files\System\Ole DB\OLEDB32R.DLL LoadedModule[197]=C:\Windows\system32\comsvcs.dll LoadedModule[198]=C:\Windows\system32\ATL.DLL LoadedModule[199]=C:\Windows\SysWOW64\bcryptprimitives.dll LoadedModule[200]=C:\Windows\SysWOW64\msjetoledb40.dll LoadedModule[201]=C:\Windows\SysWOW64\msjet40.dll LoadedModule[202]=C:\Windows\SysWOW64\mswstr10.dll LoadedModule[203]=C:\Windows\SysWOW64\msjter40.dll LoadedModule[204]=C:\Windows\SysWOW64\MSJINT40.DLL LoadedModule[205]=C:\Windows\SysWOW64\mstext40.dll LoadedModule[206]=C:\Windows\system32\mlang.dll LoadedModule[207]=C:\Windows\system32\RAASAUDIO32.DLL LoadedModule[208]=C:\Windows\system32\X3DAudio1_6.dll LoadedModule[209]=C:\Windows\SysWow64\xactengine3_4.dll LoadedModule[210]=C:\Windows\SysWow64\XAudio2_4.dll LoadedModule[211]=C:\Windows\SysWOW64\ieframe.dll LoadedModule[212]=C:\Windows\SysWOW64\mshtml.dll LoadedModule[213]=C:\Windows\system32\ntmarta.dll LoadedModule[214]=C:\Windows\syswow64\WLDAP32.dll LoadedModule[215]=C:\Windows\system32\msimtf.dll LoadedModule[216]=C:\Windows\system32\msls31.dll LoadedModule[217]=C:\Windows\system32\d2d1.dll LoadedModule[218]=C:\Windows\system32\DWrite.dll LoadedModule[219]=C:\Windows\system32\D3D10Warp.dll LoadedModule[220]=C:\FSX\VistaMare\bin\ViMaIScnX_AP.dll LoadedModule[221]=C:\Windows\system32\explorerframe.dll LoadedModule[222]=C:\Windows\system32\DUser.dll LoadedModule[223]=C:\Windows\system32\DUI70.dll LoadedModule[224]=C:\Windows\system32\EhStorShell.dll LoadedModule[225]=C:\Windows\system32\ntshrui.dll LoadedModule[226]=C:\Windows\system32\srvcli.dll LoadedModule[227]=C:\Windows\system32\cscapi.dll LoadedModule[228]=C:\Windows\system32\slc.dll LoadedModule[229]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll LoadedModule[230]=C:\Windows\System32\StructuredQuery.dll LoadedModule[231]=C:\Windows\SysWOW64\actxprxy.dll LoadedModule[232]=C:\Program Files (x86)\Internet Explorer\ieproxy.dll LoadedModule[233]=C:\Windows\SysWOW64\thumbcache.dll LoadedModule[234]=C:\Windows\system32\SHDOCVW.dll LoadedModule[235]=C:\Windows\system32\SearchFolder.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\ntlanman.dll LoadedModule[240]=C:\Windows\System32\davclnt.dll LoadedModule[241]=C:\Windows\System32\DAVHLPR.dll LoadedModule[242]=C:\Windows\system32\wkscli.dll LoadedModule[243]=C:\Windows\system32\PortableDeviceApi.dll LoadedModule[244]=C:\Windows\system32\EhStorAPI.dll LoadedModule[245]=C:\Windows\system32\twext.dll LoadedModule[246]=C:\Windows\system32\msadp32.acm LoadedModule[247]=C:\FSX\GAUGES\PMDG_737NGX.DLL LoadedModule[248]=C:\Windows\system32\NETAPI32.dll LoadedModule[249]=C:\Windows\system32\WSOCK32.dll LoadedModule[250]=C:\Windows\system32\MSVCP100.dll LoadedModule[251]=C:\Windows\SysWow64\XAudio2_7.dll LoadedModule[252]=C:\FSX\FS2Crew2010\Versions\PMDG737NGX\Gauges\FS2CrewNGXButton.GAU LoadedModule[253]=C:\FSX\libcurl.dll LoadedModule[254]=C:\Windows\system32\FS2AUDIO.dll LoadedModule[255]=C:\FSX\GAUGES\PMDG_737NGX_3.DLL LoadedModule[256]=C:\FSX\Gauges\PMDG_737NGX_2.dll LoadedModule[257]=C:\Windows\system32\napinsp.dll LoadedModule[258]=C:\Windows\system32\pnrpnsp.dll LoadedModule[259]=C:\Windows\System32\winrnr.dll LoadedModule[260]=C:\Windows\system32\icmp.Dll Sec[0].Key=LCID Sec[0].Value=3084 FriendlyEventName=Fonctionnement arrêté ConsentKey=APPCRASH AppName=Microsoft® Flight Simulator X AppPath=C:\FSX\fsx.exe Best regards Real Deraps
January 23, 201313 yr Everything on the old SSD including FSX and my OS was moved to the new SSD. Thanks for the crash report. You provided exactly what was needed. Glad to hear you moved everything over to the new SSD. The AVAST anti-virus program has been known to cause problems while running FSX but I see no indications in your crash report where it was the fault. Just letting you know some people have had problems with it. The ATC.dll, located in your main FSX directory was the faulting module. It is integrated with the fsx graphics and there have been problems when individuals had too many Windows open while running FSX. You had the Memory_Access_Violation (005) which is common with most crashes but it happens when FSX is trying to call a function, like a texture, a gauge, and cannot find it so FSX crashes. It could have happened too if your system was not overclocked correctly, your system is overheating, and, I think the most probable cause - your installed RAM are not properly configured. You might want to look at the CTD Guide here in this forum for more information and suggestions for fixing this crash - http://forum.avsim.net/topic/395603-a-guide-to-ctd-and-why-they-happen/. It provides more information about this dll and common causes. Make sure your memory is properly configured in your BIOS. If set to Auto, you should manually set the configuration as I read that ASUS (and I think other MB developers) have trouble reading and configuring memory properly. To find the proper configuration, startup CPU-Z (Google it if you do not have it installed). Look on the memory tab and look at the current configuration on your MB. On the SPD tab, there will be for columns showing the possible configurations for your memory. I highly recommend the X.M.P. Profile which uses the most out of your memory. You would just need to go into your BIOS and make those settings (if not done already). The SPD information is also located in your BIOS on the Tools page so you really don't need CPU-Z as it's all right there in the ASUS bios. It does not look like you are overclocked but with your locked 2700 CPU, you could overclock up to 4.2GHz but that is the max. Leaving it at 3.5 GHz is fine too or you could use ASUS's own program to have them overclock your system. Just make sure after the overclock is complete to check the memory settings. If they returned them to Auto, reset them to the exact timings (believe you cannot use the X.M.P. profile when ASUS does the overclocking) so you'll have to make sure the frequency is correct for the frequency and timings in the third column (second best memory settings). Hope this helps. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
January 23, 201313 yr Author Your help is really appreciated Jim. Thank you very much and i'll see what can i do. By the way, i've printed the CDT guide this morning. I'll have a look at it and try to find a solution. Best regards. Real Deraps
January 26, 201313 yr I'll have a look at it and try to find a solution. Hi Real, Did you ever get your issue fixed? Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
January 26, 201313 yr Author No not yet Jim. Yesterday evening, i started a flight from Vancouver to Bowerman US and i got a CTD only after 7 mins. On thursday i've had a 1H30mins flight over another region and got no CTD but what ever regions i'm flying over, FSX isn't smooth as it was before. With the Majestic Dash 8 400 and the PMDG B777 coming soon it's not a good new. Best regards Real Deraps
January 26, 201313 yr Do you have the FSDT version of Vancouver? They issued a fix for that product. Is Bowerman from FTX/Orbx or is it the default? You might need to rule a scenery issue and you can do this by disabling FTX/Orbx (through FTX Central) then unchecking all the addon scenery installed in your FSX directory (don't disable any default). Now run those flights. Does the problem continue? Is FSX smoother? If so, then it is an issue with one of the sceneries. Enable 2-3 sceneries at a time until you start seeing the problem again. It might be easier to disable scenery by using the Scenery Config Editor 1.1.1 (freeware) - http://www.softpedia.com/get/Others/Miscellaneous/Scenery-Config-Editor.shtml. If you have Orbx/FTX scenery, you should disable that only through their FTX Central program. I'm wondering how you are able to fly the Dash 8 400. As far as I know it hasn't been released yet. I do know Majestic made an excellent Q300 for FS9. You must be the developer huh? That product could be an issue as I remember the FS9 version had some FPS issues as it was very detailed. Maybe that's the problem. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
January 26, 201313 yr Author Do you have the FSDT version of Vancouver? They issued a fix for that product. Is Bowerman from FTX/Orbx or is it the default? You might need to rule a scenery issue and you can do this by disabling FTX/Orbx (through FTX Central) then unchecking all the addon scenery installed in your FSX directory (don't disable any default). Now run those flights. Does the problem continue? Is FSX smoother? If so, then it is an issue with one of the sceneries. Enable 2-3 sceneries at a time until you start seeing the problem again. It might be easier to disable scenery by using the Scenery Config Editor 1.1.1 (freeware) - http://www.softpedia...ig-Editor.shtml. If you have Orbx/FTX scenery, you should disable that only through their FTX Central program. I'm wondering how you are able to fly the Dash 8 400. As far as I know it hasn't been released yet. I do know Majestic made an excellent Q300 for FS9. You must be the developer huh? That product could be an issue as I remember the FS9 version had some FPS issues as it was very detailed. Maybe that's the problem. Best regards, Jim Yes i have FSDT Vancouver (version 1.1), ORBX Bowerman with all ORBX regions and many ORBX airports. And about the Majestic Dash-8-Q-400, i said "coming soon". haha!. Don't have it yet. Well i'll try with the default sceneries to see what happens. Just wondering even though i don't fly over an ORBX region could it run to CDT? I'll be back on monday with the results. (maybe tomorrow if i have time) Best regards Real Deraps
January 28, 201313 yr Author Jim I've had time today to make two flights from Vancouver to Bowerman with the Carenado B200. (CTD after only 7 minutes yesterday) First flight FTX was disable and used default FSX weather. No CTD. Second flight th FTX still disable but with Active Sky 2012 running. Still no CTD. Tomorrow i'll try a flight from Montreal (CYUL) to Caya Coco with PMDG 737. I'll keep FTX disable to see if i'll get a CTD. My computer is really smoother since FTX is disable. I'll give you report tomorrow evening. Best regards. Real Deraps
January 28, 201313 yr Hey! Some progress! Your keen investigating technique seems to be working. I am puzzled though if there is a problem with FTX scenery. If you enable it again in the future, make sure the product is completely up-to-date, including the latest Library. Thanks for posting your progress. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
January 28, 201313 yr Hi since you got the fsdt airport cyvr and all of the orbox pnw etc people had been getting ctds when flying with in the cyvr airport etc, what fixed their problem was removing any cyvr bgl files from the orbox pnw folders etc there are 3 of them i only found 2 of them in mine i removed them and it solved my problem and the others as well. its mentioned in the fsdt team forum as well I7-8700k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,, gtx 1080ti Card, RM850 power supply Peter kelberg
Create an account or sign in to comment