September 26, 201213 yr Since a couple of days, FSX Acceleration gets stuck on loading the FreeFlight menu. It's weird because I am still able to load a mission and start flying and all add-ons load properly, even TileProxy. I tried many different solutions, including a repair from the original disc. I started tweaking the config file and that did indeed work when in a mission. As soon as I hit the FreeFlight menu, FSX crashes. In the log, there's a hint to the 'g3d.dll' file, and since then I have read many things about it here in the forum. Still, no go. I also looked for a 'pure' default version of the FSX config file, but could not find any, but maybe that's not the issue. I have everything -including FSUIPC- updated to the most recent editions. I also contacted FSPS Xtreme as the crash occurs in the same fashion when using this great add-on, but no answer so far. Any ideas on this topic would be more than welcome !
September 26, 201213 yr Hi Jermac. Welcome to the AVSIM forums. Sorry your first post has to be related to a CTD! I suspect a bad video card driver installation, especially if you recently updated video card drivers. I'm a little confused though with your description of the problem. The first paragraph states the crash starts at the FreeFlight menu. Where's that? Did you hit FlyNow and the crash occurred or did you hit the FreeFlight button and the crash occurred? Are you able to start up FSX at the location where you want your flight to begin because in your first sentence you state it crashes on loading the FreeFlight menu and the second sentence says you are able to load a mission and all addons properly (which is a completely different function from FreeFlight)? Another possibility for the crash is a wrong configuration of your memory modules in the BIOS. The timings, voltages and frequencies should match those provided by the utility CPU-Z under the SPD column (or, with an ASUS board under the Tools section in the BIOS). Bad settings will work for a while, maybe several weeks before you see a crash. It just takes a memory intensive program like FSX to trigger the crash. If you are always getting the g3d.dll crash though, it is most likely something else. Have you tried the 'uiautomationcore.dll fix'? I'm not an advocate of this 'fix' as it doesn't work for everyone, including me, but it's a fairly easy fix to accomplish. Just look in a couple of posts below yours regarding the aiautomationcore.dll and where you can download it and then drop into your main FSX folder. The aiautomationcore.dll is part of Microsoft.net and FSX installs the proper version of dotnet when you install FSX or any commercial addon. Dotnet is used to manage your software once installed, including memory management. Microsoft FSX also installs the proper Microsoft Visuals C++ Redistributables. The ones required on your system are the 2005, 2008, and 2010 versions. MSV's are used by developers to properly install a product on your system. People who have removed these from their Add/Remove Programs have received problems in the past. Next, I would download AppCrashView - http://www.nirsoft.net/utils/app_crash_view.html . It looks at all the error messages that have occurred with FSX and other software applications and looks the the WER file generated by Microsoft everytime you get that 'Microsoft has had a problem and must close' dialogs. If the Exception is 0xc0000005, that means you had a Memory_Access_Violation while the g3d.dll was being called (or any faulting module). If FSX cannot load an object or a texture, it will likely have an memory exception and then a crash. It can happen too if FSX has a conflict with an addon (like EMB.series module). If you can, please copy and paste the full text of the crash as shown in the AppCrashView or Event Viewer. 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
September 26, 201213 yr Author Hi Jim, Thank-you very much for your detailed response. It's a Mac machine running Win7 64bit on bootcamp. Most recent installation on new dedicated ATA disk with bootcamp 12 months ago. For one year everything has run fine. Suddenly this issue has started. No serious updates so far, last free flight dates from Sept 20. I have the Free Flight menu as the startup screen now, and after about 3 seconds on showing the screen FSX tells me that it has to quit. When I would start with the missions menu I am able to pick a mission and fly. I have AppCrashView in place and will cite the report below. I did try the 'uiautomationcore.dll fix' and now I have the default 'uia...' file form the installation disc in place. I used UT2 but for testing reasons it has now been deactivated. C++ Redistributables have been updated as well, before this issue started. As you understand, I try to keep FSX afloat as long as I can as I know re-installing takes a lot of time. Crash log follows. Best wishes, Jeroen Version=1 EventType=APPCRASH EventTime=129931383248179780 ReportType=2 Consent=1 UploadTime=129931383256979793 ReportIdentifier=d464d7af-07da-11e2-8be1-001e52e35075 IntegratorReportIdentifier=d464d7ae-07da-11e2-8be1-001e52e35075 WOW64=1 Response.BucketId=557972855 Response.BucketTable=1 Response.type=4 Sig[0].Name=Naam van de toepassing Sig[0].Value=fsx.exe Sig[1].Name=Versie van toepassing Sig[1].Value=10.0.61637.0 Sig[2].Name=Tijdstempel van toepassing Sig[2].Value=46fadb14 Sig[3].Name=Naam van foutmodule Sig[3].Value=g3d.dll Sig[4].Name=Versie van foutmodule Sig[4].Value=10.0.61637.0 Sig[5].Name=Tijdstempel van foutmodule Sig[5].Value=46fadb58 Sig[6].Name=Uitzonderingscode Sig[6].Value=c0000005 Sig[7].Name=Uitzonderingsmarge Sig[7].Value=000122fa DynamicSig[1].Name=Versie van besturingssysteem DynamicSig[1].Value=6.1.7601.2.1.0.768.3 DynamicSig[2].Name=Landinstelling-id DynamicSig[2].Value=1043 DynamicSig[22].Name=Aanvullende informatie 1 DynamicSig[22].Value=b80f DynamicSig[23].Name=Aanvullende informatie 2 DynamicSig[23].Value=b80fa8aa693f9630e858f5a976d06b8a DynamicSig[24].Name=Aanvullende informatie 3 DynamicSig[24].Value=2ade DynamicSig[25].Name=Aanvullende informatie 4 DynamicSig[25].Value=2adea04e810ac36f6067d59a816f636a UI[2]=C:\FSX\fsx.exe UI[3]=Microsoft Flight Simulator® werkt niet meer UI[4]=U kunt online naar een oplossing voor het probleem zoeken. UI[5]=Online naar een oplossing zoeken en dit programma sluiten UI[6]=Later online naar een oplossing zoeken en dit programma sluiten UI[7]=Het programma sluiten 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\iertutil.dll LoadedModule[37]=C:\Windows\syswow64\WININET.dll LoadedModule[38]=C:\Windows\syswow64\Normaliz.dll LoadedModule[39]=C:\Windows\system32\MPR.dll LoadedModule[40]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[41]=C:\Windows\system32\WINSPOOL.DRV LoadedModule[42]=C:\Windows\AppPatch\AcSpecfc.DLL LoadedModule[43]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll LoadedModule[44]=C:\Windows\system32\mscms.dll LoadedModule[45]=C:\Windows\system32\DDRAW.dll LoadedModule[46]=C:\Windows\system32\DCIMAN32.dll LoadedModule[47]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[48]=C:\Windows\syswow64\IMM32.dll LoadedModule[49]=C:\Windows\syswow64\MSCTF.dll LoadedModule[50]=C:\Windows\syswow64\WS2_32.dll LoadedModule[51]=C:\Windows\syswow64\NSI.dll LoadedModule[52]=C:\Windows\system32\msi.dll LoadedModule[53]=C:\FSX\language.dll LoadedModule[54]=C:\FSX\API.DLL LoadedModule[55]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[56]=C:\FSX\ablscpt.dll LoadedModule[57]=C:\FSX\flight.dll LoadedModule[58]=C:\FSX\ai_player.dll LoadedModule[59]=C:\FSX\acontain.dll LoadedModule[60]=C:\FSX\controls.dll LoadedModule[61]=C:\Windows\system32\DINPUT8.dll LoadedModule[62]=C:\FSX\fsui.dll LoadedModule[63]=C:\FSX\atc.dll LoadedModule[64]=C:\FSX\facilities.dll LoadedModule[65]=C:\FSX\demo.dll LoadedModule[66]=C:\FSX\main.dll LoadedModule[67]=C:\FSX\fe.dll LoadedModule[68]=C:\FSX\util.dll LoadedModule[69]=C:\FSX\simprop.dll LoadedModule[70]=C:\FSX\g2d.dll LoadedModule[71]=C:\Windows\system32\d3dx9_34.dll LoadedModule[72]=C:\Windows\system32\d3dx10_34.dll LoadedModule[73]=C:\Windows\system32\d3d9.dll LoadedModule[74]=C:\Windows\system32\d3d8thk.dll LoadedModule[75]=C:\FSX\g3d.dll LoadedModule[76]=C:\FSX\panels.dll LoadedModule[77]=C:\FSX\multiplayer.dll LoadedModule[78]=C:\FSX\ui.dll LoadedModule[79]=C:\FSX\sound.dll LoadedModule[80]=C:\FSX\sim1.dll LoadedModule[81]=C:\FSX\simscheduler.dll LoadedModule[82]=C:\FSX\visualfx.dll LoadedModule[83]=C:\FSX\window.dll LoadedModule[84]=C:\FSX\terrain.dll LoadedModule[85]=C:\FSX\weather.dll LoadedModule[86]=C:\Windows\system32\DSOUND.dll LoadedModule[87]=C:\Windows\system32\POWRPROF.dll LoadedModule[88]=C:\FSX\symmap.dll LoadedModule[89]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll LoadedModule[90]=C:\Windows\system32\MSIMG32.dll LoadedModule[91]=C:\FSX\xuipc.dll LoadedModule[92]=C:\FSX\livingwater.dll LoadedModule[93]=C:\FSX\fs-traffic.dll LoadedModule[94]=C:\FSX\gps.dll LoadedModule[95]=C:\Windows\system32\MSWSOCK.dll LoadedModule[96]=C:\Windows\system32\SHFOLDER.dll LoadedModule[97]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll LoadedModule[98]=C:\Windows\system32\CRYPTSP.dll LoadedModule[99]=C:\Windows\system32\rsaenh.dll LoadedModule[100]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[101]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[102]=C:\Windows\syswow64\MSASN1.dll LoadedModule[103]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[104]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[105]=C:\Windows\system32\wbemcomn.dll LoadedModule[106]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[107]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[108]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[109]=C:\Windows\system32\NTDSAPI.dll LoadedModule[110]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[111]=C:\Windows\system32\dxgi.dll LoadedModule[112]=C:\Windows\system32\aticfx32.dll LoadedModule[113]=C:\Windows\system32\atiu9pag.dll LoadedModule[114]=C:\Windows\system32\atiumdag.dll LoadedModule[115]=C:\Windows\system32\atiumdva.dll LoadedModule[116]=C:\Windows\system32\atiuxpag.dll LoadedModule[117]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[118]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[119]=C:\Windows\system32\d3d10_1.dll LoadedModule[120]=C:\Windows\system32\d3d10_1core.dll LoadedModule[121]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[122]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[123]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[124]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[125]=C:\Windows\SysWOW64\d3d11.dll LoadedModule[126]=C:\Windows\system32\winbrand.dll LoadedModule[127]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[128]=C:\Windows\system32\WINSTA.dll LoadedModule[129]=C:\Windows\system32\oleacc.dll LoadedModule[130]=C:\Windows\SysWOW64\gameux.dll LoadedModule[131]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[132]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[133]=C:\Windows\SysWOW64\wer.dll LoadedModule[134]=C:\Windows\System32\Wpc.dll LoadedModule[135]=C:\Windows\System32\wevtapi.dll LoadedModule[136]=C:\Windows\System32\msxml6.dll LoadedModule[137]=C:\Windows\system32\SAMLIB.dll LoadedModule[138]=C:\Windows\system32\netutils.dll LoadedModule[139]=C:\FSX\uiautomationcore.dll LoadedModule[140]=C:\Windows\System32\MMDevApi.dll LoadedModule[141]=C:\Windows\System32\PROPSYS.dll LoadedModule[142]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[143]=C:\Windows\system32\RICHED20.DLL LoadedModule[144]=C:\Windows\system32\HID.DLL LoadedModule[145]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[146]=C:\Windows\system32\wdmaud.drv LoadedModule[147]=C:\Windows\system32\ksuser.dll LoadedModule[148]=C:\Windows\system32\AVRT.dll LoadedModule[149]=C:\Windows\system32\msacm32.drv LoadedModule[150]=C:\Windows\system32\midimap.dll LoadedModule[151]=C:\Windows\system32\dinput.DLL LoadedModule[152]=C:\Windows\System32\wship6.dll LoadedModule[153]=C:\Windows\System32\wshtcpip.dll LoadedModule[154]=C:\FSX\ORBX\FTX_NZ\FTX_NZNI_05_SCENERY\scenery\ObjectFlow_NZNI.dll LoadedModule[155]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll LoadedModule[156]=C:\FSX\ORBX\FTX_AU\FTXAA_YBCS\scenery\ObjectFlow_YBCS.dll LoadedModule[157]=C:\FSX\VistaMare\ViMaCoreX.dll LoadedModule[158]=C:\FSX\VistaMare\bin\VMCX_AP.dll LoadedModule[159]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[160]=C:\FSX\VistaMare\bin\ViMaNET_AP.dll LoadedModule[161]=C:\FSX\Captain_Sim\Captain_Sim.b767.menu.dll LoadedModule[162]=C:\FSX\Captain_Sim\767\cs.sound.dll LoadedModule[163]=C:\FSX\Captain_Sim\Captain_Sim.b757.menu.dll LoadedModule[164]=C:\FSX\Captain_Sim\757\cs.sound.dll LoadedModule[165]=C:\FSX\FeelThere\E170\EJetH.dll LoadedModule[166]=C:\Program Files (x86)\FlyingWSimulation\SuperTrafficBoard\STBServer\STBServer.dll LoadedModule[167]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SimConnect.dll LoadedModule[168]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll LoadedModule[169]=C:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll LoadedModule[170]=C:\Windows\system32\MSVCR100.dll LoadedModule[171]=C:\FSX\Modules\FSUIPC4.dll LoadedModule[172]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[173]=C:\Windows\system32\WINNSI.DLL LoadedModule[174]=C:\Windows\syswow64\imagehlp.dll LoadedModule[175]=C:\Windows\system32\ncrypt.dll LoadedModule[176]=C:\Windows\system32\bcrypt.dll LoadedModule[177]=C:\Windows\SysWOW64\bcryptprimitives.dll LoadedModule[178]=C:\Windows\system32\GPAPI.dll LoadedModule[179]=C:\Windows\system32\cryptnet.dll LoadedModule[180]=C:\Windows\syswow64\WLDAP32.dll LoadedModule[181]=C:\Windows\system32\SensApi.dll LoadedModule[182]=C:\Windows\SysWOW64\ieframe.dll LoadedModule[183]=C:\Windows\system32\Secur32.dll LoadedModule[184]=C:\Windows\system32\dnsapi.DLL LoadedModule[185]=C:\Windows\system32\ntmarta.dll LoadedModule[186]=C:\Windows\SysWOW64\mshtml.dll LoadedModule[187]=C:\Windows\system32\msimtf.dll LoadedModule[188]=C:\Windows\system32\msls31.dll LoadedModule[189]=C:\Windows\system32\d2d1.dll LoadedModule[190]=C:\Windows\system32\DWrite.dll LoadedModule[191]=C:\Windows\system32\D3D10Warp.dll LoadedModule[192]=C:\Windows\system32\MLANG.dll LoadedModule[193]=C:\FSX\VistaMare\bin\ViMaIScnX_AP.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 State[1].Key=DataRequest State[1].Value=Bucket=557972855/nBucketTable=1/nResponse=1/n FriendlyEventName=Werkt niet meer ConsentKey=APPCRASH AppName=Microsoft Flight Simulator® AppPath=C:\FSX\fsx.exe
September 26, 201213 yr It sounds like to me you have a saved situation? I would restore the fsx.cfg to restore the default flight. One easy way to restore the original default flight is to edit your FSX.cfg file. Look for the line under the [uSERINTERFACE] label which says situation=(remove anything after this line and save the fsx.cfg). This will delete any new default setup you might have saved. FSX will now use the original default flight when you restart it. If this solves the problem -- STOP and GoFly. If not, the problem could also be a corrupted logbook.bin. This file is located in your My Documents\Flight Simulator X Files. Download 'fsxlogrecovery11.zip' from the Avsim Library. Then place fsxlog.exe in the same folder as logbook.bin and run the program. If it is corrupted, it will do a repair. Restart FSX and see if this fixes the problem. The logbook.bin saves every flight and mission you have ever done in FSX and it sometimes gets corrupted. 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
September 26, 201213 yr Author Hi Jim, After deleting the lines after 'stuation=' no improvement. Now FSX crashes at the very first splash screen, just a few seconds after the theme music has started. I then followed your second advice and to my surprise the app stated that no corruption has been found. Replacing the UIAutomation file got me past the splash screen. Missions and Lessons work, settings can be loaded without any issues. But, as soon as I hit the Free Flight mode, FSX crashes. The crash log shows the same type of errors: Sig[0].Name=Naam van de toepassing Sig[0].Value=fsx.exe Sig[1].Name=Versie van toepassing Sig[1].Value=10.0.61637.0 Sig[2].Name=Tijdstempel van toepassing Sig[2].Value=46fadb14 Sig[3].Name=Naam van foutmodule Sig[3].Value=g3d.dll Sig[4].Name=Versie van foutmodule Sig[4].Value=10.0.61637.0 Sig[5].Name=Tijdstempel van foutmodule Sig[5].Value=46fadb58 Sig[6].Name=Uitzonderingscode Sig[6].Value=c0000005 Sig[7].Name=Uitzonderingsmarge Sig[7].Value=000122fa What shall I do next ? I looked for a title in the FSX documents folder pointing to the default flight 'over puget sound' or something like that but could not find anything. Could that be the problem ? In the cfg file there is no file path listed after 'situation=', only a list of flight settings. FSX was able to find the correct path because the missions are listed and they reside in the same folder. I noticed a file entitled 'previous flight' and a connecting .wxs file with a recent date, could those be the trouble makers? Best wishes, Jeroen
September 26, 201213 yr Okay Jeroen, I checked the Internet again and it appears that others who had this error and same circumstances fixed it by uninstalling their video card drivers and reinstalling them (http://www.flightsim.com/vbfs/archive/index.php/t-230489.html). Another individual fixed the same exact problem by uninstalling Acceleration only, running FSX and the problem disappeared so he reinstalled Acceleration and all fixed. That would be easy to check out. In regards to the uiautomationcore.dll 'fix', I could not completely comprehend what happened when you tried it. Hopefully you used the right version which is located in one of the posts near this post. In regards to the default flight in the FSX documents folder, there should be no default file. In the FSX.cfg, the situation line should read SITUATION=FLIGHTS\OTHER\FLTSIM. Are you getting the Trike when you first start up with the location at Friday Harbor? If not, then you probably saved a flight for startup and that flight is corrupted as the things it has to call up to load the flight have changed (like the weather, another aircraft, or you removed a scenery location). In the FSX documents location you should have Previous Flight.FLT Previous Flight.FSSAVE and Previous Flight.WX You can delete the .wx file but nothing else. See if that makes a difference. Do not delete the .flt file. Let's see if any of the above fixes your issue. 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
September 27, 201213 yr Author Hi Jim, thanks for writing! In my case, Apple OS manages the drivers of the videocard in the background. To my knowledge, I am unable to directly interact with the card, other than tweaks in the fsx config file. I did experiment with installing drivers from AMD but that only led to errors and conflicts, so I lay this to rest. As to the UIAutomationcore, I did pick the one that was posted in this forum. But I think we hit something here. I remember I changed the default flight for another flight and left that there. Some weeks ago I recreated the Friday Harbor flight as to choosing the Trike and location and saved this as the flight that is loaded at startup. However, I never bothered to actually fly this flight. Today, in the list I noticed something irregular, concerning the 'previous flight' (dated 10-09-2012) and 'rectmflight' (I haven't got a clue what kind of flight this is, it dates back to 2010) as all other flight files come in sets of three filetypes, as you showed in your post. With these particluar files, the .FSSAVE file is missing and this would somehow explain why FSX crashes. Concerning uninstalling and re-installing Acceleration, I am worried that these actions would mess up the add-ons currently installed. Or would this leave the add-ons merely untouched ? And what about .NET editions, would it install previous versions on top of current versions ? As you know I already ran a repair session from the Acceleration disc but it did not fix this issue. Nevertheless, I am willing to try, of course. Best wishes, Jeroen
September 27, 201213 yr <br />Concerning uninstalling and re-installing Acceleration, I am worried that these actions would mess up the add-ons currently installed. Or would this leave the add-ons merely untouched ? And what about .NET editions, would it install previous versions on top of current versions ?<br /> Hi Jeroen, Uninstalling Acceleration should not affect any addon but when you uninstall it, you need to run FSX. If you do this, please select a default aircraft (like the trike) and a default location. Once that has loaded and started up and you are not getting the crash anymore, close it and then reinstall Acceleration. This is much different than a repair as you're bringing FSX back to the basic setup. A repair only repaired any missing or corrupted files. You might also rename the previous flight.flt to previous flight.old, start up fsx and see what happens. You can always rename it back to .flt if there is a problem. Not sure what the rectmflight belongs to but it's not on my system or in My Documents/FSX folder. I would move it to a temporary folder to make sure it's not needed by some other program you own. Did you the .wx or weather file? What I'm looking at is when you save a flight, you save the weather and that may be conflicting as what is required can no longer be found. Maybe a long shot but work a try. I'm running out of possible solutions. Regarding the .net editions, I have all of the editions installed from Version 1.1 to 4.5. They will make a separate folder for each version. Look in your C:/Windows/Microsoft.net/Framework/(versions). If you have a 64 bit system you should have a Framework64 too. Here's a link to the dotnet verification tool and how to run that tool - http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx. If the uiautomationcore.dll 'fix' did not work, and none of these possible solutions work, I'm afraid you'll have to uninstall FSX and reinstall. Before doing that, disable all of your addons located in the Scenery Library by removing the checkmark. This list should be all the way to Propeller Objects. Then run FSX and see if the problem is fixed. Sometimes a bad install of an addon will mess things up too. If FSX works properly, then, you'll have to enable each one by one until you find the one that's causing the issue. It's better than uninstalling! I'm not familiar with Apple computers but guessing you have Windows 7 64 bit installed? If so, you can do another check to make sure nothing is wrong with DirectX. Click on the Start button, click on All Programs, then click on Assessories>Run. Once the Run box is up, type dxdiag and hit return. You should have a diagnostics of your DirectX. See if there are any errors. If so, you may have to reinstall DirectX. You can also scan your computer for corrupted or missing system files. Just click on the Start button, click on All Programs, then click on Accessories >Command Prompt. Once the command prompt is displayed, type sfc /scannow and hit return. Hopefully we can find a solution soon. 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
September 28, 201213 yr Author Hi Jim, thank-you again for writing! For the record, my Mac machine is running Windows 7 HP SP1 64bit. Before I uninstalled Accleration I made sure to check the .NET versions and they were all there from version 1 right up to the most recent one 4.5. Then I checked the DirectX files, both 32bit and 64bit, and no errors were found. I also ran the 'sfc / scannow' command and some files were indeed repaired. I ran FSX Acceleration again but the same crash appeared. So I uninstalled 'Acceleration' by running the uninstall programme from the disc. I then defragmented the bootdisk, and started up. Same crash appeared in FSX. Then, I decided to disable all the third-party scenery in the Scenery Library, and started FSX again. To my surprise, I could now access the Free Flight mode. I performed a short flight in the trike and exited without any problem. I will now proceed and re-install Acceleration. Then I am facing the task of checking which scenery add-on is causing the crash. The prime suspect is TileProxy as it crashed several times in the days preceding the Free Flight mode crash. And, there are many files -or rather 'tiles'- involved. But, we'll see. At least now I know that file corruption can occurr in this area and in this particular fashion. I also learned a lot these days about system maintenance and working with the inner cores of FSX. This is a great relief, I must admit, as I have spent so many hours trying to find the source of the problem. And you have been such a great help in solving this matter, I deeply appreciate it, thank-you very much indeed! Best wishes, Jeroen
September 28, 201213 yr Hey Jeroen! Great news! Always enjoy reading success stories. I have a feeling you are right about TileProxy. A program in FSX is probably calling one of the tiles and it's not there or where it should be. Can't help you there though. I heard it's a great program but never bought it. I'm sticking with my FTX/Orbx stuff. There's a lot of tips for properly running TileProxy if you do a Google search. Hope you continue to have no issues after hitting that Fly Now button! 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
Create an account or sign in to comment