April 15, 201313 yr Hi! I have an annoying phenomenon with my quite fresh installation of FSX on my new PC: When I boot up FSX, it asks me wether to load the FS Force dll's or not (I set that up in the FS Force options, because sometimes I use a non force feedback yoke), and thereafter it can happen, that the sim crashes to desktop immediately, without any error message. That happens not too often. More often, it happens, that the main menu of FSX shows up, the plane in the preview screen rotates for 2 or 3 seconds, stops and then the simulator crashes to desktop with various error messages. But it is always the g3d.dll that is related to the CTD. I can almost trigger that error by moving the mouse wildly after the confirmation to load the FS Force.dll's. If I do nothing at all after that, the sim starts normally most of the times. But around 30% of the time, the sim crashes when booting up. On the second attempt, everything goes well usually. Once loaded or in flight, everything is super stable. I only had 1 (!) CTD in flight, caused by not starting the sim freshly before switching add on aircraft. I use a FSX.cfg tweaked by the Boyote online tool, frames are set to unlimited in the sim and are limited to 30 in the Nvidia Inspector. Vsync is set to half refresh rate and anti aliasing is set to 8xS within the Inspector, everything else is at its default value. My system is: i5 3570K 16 GB RAM CL9 GTX 670 2GB Win 7 64 bit Home Premium Thanks in advance for your help!
April 15, 201313 yr FSX does not run well with an external fps limiter, especially the one in NVidia Inspector. I would set it internally and set the NI setting to render 3 as recommended by almost everyone. Your explanation of the crash indicates fsx is resource hungry and is having issues rendering textures in a timely manner. The g3d.dll error is related to high FSX and display driver settings. The Bojote online config tool is a good start at tweaking but sometimes his settings are way out of line. I personally do not think it does a very good job at tweaking. I would look at the Bufferpool setting in your fsx.cfg first. A wrong setting and your fsx will crash. I would look at AVSIM's Software and Hardware Guide pinned at the top of the FSX and some other forums. It provides you with the tweaks plus an explanation of the tweak. You should never tweak without knowing what the tweak will do to your system. The guide also has suggested NI settings. No matter how much ram you have, fsx will only use about 4 GB's and the rest will be used for system operating system functions. Maybe the next version will be able to use more. 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
April 15, 201313 yr FSX does not run well with an external fps limiter, especially the one in NVidia Inspector. I would set it internally and set the NI setting to render 3 as recommended by almost everyone. Your explanation of the crash indicates fsx is resource hungry and is having issues rendering textures in a timely manner. The g3d.dll error is related to high FSX and display driver settings. The Bojote online config tool is a good start at tweaking but sometimes his settings are way out of line. I personally do not think it does a very good job at tweaking. I would look at the Bufferpool setting in your fsx.cfg first. A wrong setting and your fsx will crash. I would look at AVSIM's Software and Hardware Guide pinned at the top of the FSX and some other forums. It provides you with the tweaks plus an explanation of the tweak. You should never tweak without knowing what the tweak will do to your system. The guide also has suggested NI settings. No matter how much ram you have, fsx will only use about 4 GB's and the rest will be used for system operating system functions. Maybe the next version will be able to use more. Best regards, Jim Thanks for the fast answer! Hmmm, okay. But in game, everything is runnig really nicely. I tried to limit the frames with the internal setting once, but after deactivating the frame limiter within NI, FSX didn´t boot up at all anymore... Quite strange.
April 15, 201313 yr but after deactivating the frame limiter within NI, FSX didn´t boot up at all anymore... Quite strange. Yes, that is strange. No reason it should do that. You might look in your fsx.cfg in the [Display] section and make sure upper_framerate_limit=0 is there (that's for the unlimited fps). Still, it should not affect the startup of FSX. FSX should startup to the startup screen so you can change settings. 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
April 15, 201313 yr but after deactivating the frame limiter within NI, FSX didn´t boot up at all anymore... Quite strange. Yes, that is strange. No reason it should do that. You might look in your fsx.cfg in the [Display] section and make sure upper_framerate_limit=0 is there (that's for the unlimited fps). Still, it should not affect the startup of FSX. FSX should startup to the startup screen so you can change settings. Best regards, Jim Hmmm, I got the sim booting up with NI frame limiter off and FSX internal limiter set to 30. But the sim crashes nearly on every boot up. Now, the ntdll.dll shows up too...
April 15, 201313 yr Hmmm, I got the sim booting up with NI frame limiter off and FSX internal limiter set to 30. But the sim crashes nearly on every boot up. Now, the ntdll.dll shows up too... NTDLL.dll indicates high fsx/display driver settings. I would save your current FSX.cfg to fsx.orig (in case you want to get it back) then restart FSX and let the config rebuild. If it fixes the problem, then you can begin tweaking it like your original FSX.cfg. If that doesn't work, then your dll.xml is corrupt. 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
April 16, 201313 yr NTDLL.dll indicates high fsx/display driver settings. I would save your current FSX.cfg to fsx.orig (in case you want to get it back) then restart FSX and let the config rebuild. If it fixes the problem, then you can begin tweaking it like your original FSX.cfg. If that doesn't work, then your dll.xml is corrupt. Best regards, Jim Here is one of my latest app crash reports: Version=1 EventType=APPCRASH EventTime=130105837974438797 ReportType=2 Consent=1 UploadTime=130105837974918824 ReportIdentifier=3d52b8b2-a685-11e2-a304-10bf487b383a IntegratorReportIdentifier=3d52b8b1-a685-11e2-a304-10bf487b383a WOW64=1 Response.type=4 Sig[0].Name=Anwendungsname Sig[0].Value=fsx.exe Sig[1].Name=Anwendungsversion Sig[1].Value=10.0.61637.0 Sig[2].Name=Anwendungszeitstempel Sig[2].Value=46fadb14 Sig[3].Name=Fehlermodulname Sig[3].Value=g3d.dll Sig[4].Name=Fehlermodulversion Sig[4].Value=10.0.61637.0 Sig[5].Name=Fehlermodulzeitstempel Sig[5].Value=46fadb58 Sig[6].Name=Ausnahmecode Sig[6].Value=c0000005 Sig[7].Name=Ausnahmeoffset Sig[7].Value=000ba79f DynamicSig[1].Name=Betriebsystemversion DynamicSig[1].Value=6.1.7601.2.1.0.768.3 DynamicSig[2].Name=Gebietsschema-ID DynamicSig[2].Value=1031 UI[2]=C:\FSX\fsx.exe UI[3]=Ein schwerwiegender Fehler ist aufgetreten. UI[4]=Windows kann online nach einer Lösung für das Problem suchen. UI[5]=Online nach einer Lösung suchen und das Programm schließen UI[6]=Später online nach einer Lösung suchen und das Programm schließen UI[7]=Programm schließen 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:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80DEU.DLL LoadedModule[54]=C:\FSX\language.dll LoadedModule[55]=C:\FSX\API.DLL LoadedModule[56]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[57]=C:\FSX\ablscpt.dll LoadedModule[58]=C:\FSX\flight.dll LoadedModule[59]=C:\FSX\ai_player.dll LoadedModule[60]=C:\FSX\acontain.dll LoadedModule[61]=C:\FSX\controls.dll LoadedModule[62]=C:\Windows\system32\DINPUT8.dll LoadedModule[63]=C:\FSX\fsui.dll LoadedModule[64]=C:\FSX\atc.dll LoadedModule[65]=C:\FSX\facilities.dll LoadedModule[66]=C:\FSX\demo.dll LoadedModule[67]=C:\FSX\main.dll LoadedModule[68]=C:\FSX\fe.dll LoadedModule[69]=C:\FSX\util.dll LoadedModule[70]=C:\FSX\simprop.dll LoadedModule[71]=C:\FSX\g2d.dll LoadedModule[72]=C:\Windows\system32\d3dx9_34.dll LoadedModule[73]=C:\Windows\system32\d3dx10_34.dll LoadedModule[74]=C:\Windows\system32\d3d9.dll LoadedModule[75]=C:\Windows\system32\d3d8thk.dll LoadedModule[76]=C:\FSX\g3d.dll LoadedModule[77]=C:\FSX\panels.dll LoadedModule[78]=C:\FSX\multiplayer.dll LoadedModule[79]=C:\FSX\ui.dll LoadedModule[80]=C:\FSX\sound.dll LoadedModule[81]=C:\FSX\sim1.dll LoadedModule[82]=C:\FSX\simscheduler.dll LoadedModule[83]=C:\FSX\visualfx.dll LoadedModule[84]=C:\FSX\window.dll LoadedModule[85]=C:\FSX\terrain.dll LoadedModule[86]=C:\FSX\weather.dll LoadedModule[87]=C:\Windows\system32\DSOUND.dll LoadedModule[88]=C:\Windows\system32\POWRPROF.dll LoadedModule[89]=C:\FSX\symmap.dll LoadedModule[90]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll LoadedModule[91]=C:\Windows\system32\MSIMG32.dll LoadedModule[92]=C:\FSX\xuipc.dll LoadedModule[93]=C:\FSX\livingwater.dll LoadedModule[94]=C:\FSX\fs-traffic.dll LoadedModule[95]=C:\FSX\gps.dll LoadedModule[96]=C:\Windows\system32\MSWSOCK.dll LoadedModule[97]=C:\Windows\system32\SHFOLDER.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\d3d11.dll LoadedModule[113]=C:\Windows\system32\nvd3dum.dll LoadedModule[114]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[115]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[116]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[117]=C:\Windows\system32\d3d10_1.dll LoadedModule[118]=C:\Windows\system32\d3d10_1core.dll LoadedModule[119]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[120]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[121]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[122]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[123]=C:\Windows\system32\winbrand.dll LoadedModule[124]=C:\Windows\system32\nvapi.dll LoadedModule[125]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[126]=C:\Windows\system32\WINSTA.dll LoadedModule[127]=C:\Windows\SysWOW64\gameux.dll LoadedModule[128]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[129]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[130]=C:\Windows\SysWOW64\wer.dll LoadedModule[131]=C:\Windows\System32\Wpc.dll LoadedModule[132]=C:\Windows\System32\wevtapi.dll LoadedModule[133]=C:\Windows\System32\msxml6.dll LoadedModule[134]=C:\Windows\system32\SAMLIB.dll LoadedModule[135]=C:\Windows\system32\netutils.dll LoadedModule[136]=C:\Windows\system32\uiautomationcore.dll LoadedModule[137]=C:\Windows\system32\OLEACC.dll LoadedModule[138]=C:\Windows\System32\MMDevApi.dll LoadedModule[139]=C:\Windows\System32\PROPSYS.dll LoadedModule[140]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[141]=C:\Windows\system32\RICHED20.DLL LoadedModule[142]=C:\Windows\system32\HID.DLL LoadedModule[143]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[144]=C:\Windows\system32\wdmaud.drv LoadedModule[145]=C:\Windows\system32\ksuser.dll LoadedModule[146]=C:\Windows\system32\AVRT.dll LoadedModule[147]=C:\Windows\system32\msacm32.drv LoadedModule[148]=C:\Windows\system32\midimap.dll LoadedModule[149]=C:\Windows\system32\dinput.DLL LoadedModule[150]=C:\Windows\SysWow64\WmJoyF32.dll LoadedModule[151]=C:\Program Files (x86)\Avira\AntiVir Desktop\avsda.dll LoadedModule[152]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[153]=C:\Windows\system32\WINNSI.DLL LoadedModule[154]=C:\Windows\System32\wshtcpip.dll LoadedModule[155]=C:\Windows\System32\wship6.dll LoadedModule[156]=C:\FSX\bglmanx.dll LoadedModule[157]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[158]=C:\Windows\system32\inetmib1.dll LoadedModule[159]=C:\Windows\system32\snmpapi.dll LoadedModule[160]=C:\FSX\Modules\iFly737NG.dll LoadedModule[161]=C:\FSX\ORBX\FTX_NA\FTX_AA_PAKT\Scenery\ObjectFlow_PAKT.dll LoadedModule[162]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll LoadedModule[163]=C:\FSX\ORBX\FTX_NA\FTX_AA_W52\scenery\ObjectFlow_W52.dll LoadedModule[164]=C:\FSX\ORBX\FTX_NA\FTX_AA_KCMW\Scenery\ObjectFlow_KCMW.dll LoadedModule[165]=C:\FSX\ORBX\FTX_NA\FTX_AA_CZST\Scenery\ObjectFlow_CZST.dll LoadedModule[166]=C:\FSX\ORBX\FTX_NA\FTX_AA_74S\Scenery\ObjectFlow_74S.dll LoadedModule[167]=C:\FSX\ORBX\FTX_NA\FTX_AA_1WA6\Scenery\ObjectFlow_1WA6.dll LoadedModule[168]=C:\FSX\Modules\rxpGnsDriver.dll LoadedModule[169]=C:\FSX\A2A\Shared\A2A_Service.dll LoadedModule[170]=C:\FSXVistaMare\ViMaCoreX.dll LoadedModule[171]=C:\FSXVistaMare\bin\VMCX_AP.dll LoadedModule[172]=C:\FSXVistaMare\bin\ViMaNET_AP.dll LoadedModule[173]=C:\FSX\Aerosoft\ASE_DATA\AseData.dll LoadedModule[174]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SimConnect.dll LoadedModule[175]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll LoadedModule[176]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll LoadedModule[177]=C:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll LoadedModule[178]=C:\Windows\system32\MSVCR100.dll LoadedModule[179]=C:\FSX\Modules\GPSModule.dll LoadedModule[180]=C:\FSX\Aerosoft\Ase_Data\bin\dlls\ASELoadDll.dll LoadedModule[181]=C:\FSX\Addon Modules\AirbusNewHUD.dll LoadedModule[182]=C:\FSX\FeelThere\B737 v2\PIC737XH.dll LoadedModule[183]=C:\FSX\FeelThere\E170\EJetH.dll LoadedModule[184]=C:\FSX\Aerosoft\Flight Recorder\AS-FlightRecorder.dll LoadedModule[185]=C:\FSX\RAASPRO\RAASPRO.dll LoadedModule[186]=C:\Windows\system32\Secur32.dll LoadedModule[187]=C:\Windows\system32\dnsapi.DLL LoadedModule[188]=C:\Windows\system32\RASAPI32.dll LoadedModule[189]=C:\Windows\system32\rasman.dll LoadedModule[190]=C:\Windows\system32\rtutils.dll LoadedModule[191]=C:\Windows\system32\sensapi.dll LoadedModule[192]=C:\Windows\system32\NLAapi.dll LoadedModule[193]=C:\Windows\system32\rasadhlp.dll LoadedModule[194]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL LoadedModule[195]=C:\Windows\System32\fwpuclnt.dll LoadedModule[196]=C:\Windows\system32\napinsp.dll LoadedModule[197]=C:\Windows\system32\pnrpnsp.dll LoadedModule[198]=C:\Windows\System32\winrnr.dll LoadedModule[199]=C:\Windows\system32\dhcpcsvc.DLL LoadedModule[200]=C:\Windows\system32\dhcpcsvc6.DLL LoadedModule[201]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll LoadedModule[202]=C:\Windows\system32\MSDART.DLL LoadedModule[203]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll LoadedModule[204]=C:\Windows\system32\bcrypt.dll LoadedModule[205]=C:\Program Files (x86)\Common Files\System\Ole DB\OLEDB32R.DLL LoadedModule[206]=C:\Windows\system32\comsvcs.dll LoadedModule[207]=C:\Windows\system32\ATL.DLL LoadedModule[208]=C:\Windows\SysWOW64\bcryptprimitives.dll LoadedModule[209]=C:\Windows\SysWOW64\msjetoledb40.dll LoadedModule[210]=C:\Windows\SysWOW64\msjet40.dll LoadedModule[211]=C:\Windows\SysWOW64\mswstr10.dll LoadedModule[212]=C:\Windows\SysWOW64\msjter40.dll LoadedModule[213]=C:\Windows\SysWOW64\MSJINT40.DLL LoadedModule[214]=C:\Windows\SysWOW64\mstext40.dll LoadedModule[215]=C:\Windows\system32\mlang.dll LoadedModule[216]=C:\Windows\system32\RAASAUDIO32.DLL LoadedModule[217]=C:\Windows\system32\X3DAudio1_6.dll LoadedModule[218]=C:\Windows\SysWow64\xactengine3_4.dll LoadedModule[219]=C:\Windows\SysWow64\XAudio2_4.dll LoadedModule[220]=C:\FSX\PMDG\DLLs\PMDGOptions.dll LoadedModule[221]=C:\FSX\PMDG_SimConnect_Ldr.dll LoadedModule[222]=C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90.dll LoadedModule[223]=C:\Windows\WinSxS\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_49768ef57548175e\MFC90DEU.DLL LoadedModule[224]=C:\FSX\PMDG\DLLs\PMDGEvents.dll LoadedModule[225]=C:\FSX\PMDG\DLLs\PMDGSounds.dll LoadedModule[226]=C:\FSX\WaveLib.dll LoadedModule[227]=C:\FSForce 2\FSForce.dll LoadedModule[228]=C:\FSX\Modules\FSUIPC4_Loader.dll LoadedModule[229]=C:\FSX\Modules\LVLD.dll LoadedModule[230]=C:\FSX\Modules\LVLDLanguage.dll LoadedModule[231]=C:\FSX\Level-D Simulations\B767-300\leveld.dll LoadedModule[232]=C:\Windows\system32\msadp32.acm LoadedModule[233]=C:\Windows\SysWOW64\ieframe.dll LoadedModule[234]=C:\Windows\SysWOW64\mshtml.dll LoadedModule[235]=C:\FSX\GAUGES\Cessna.DLL LoadedModule[236]=C:\FSX\GAUGES\Cessna172.DLL LoadedModule[237]=C:\FSX\GAUGES\Cessna182s.DLL LoadedModule[238]=C:\FSX\GAUGES\CessnaWAlpha.DLL LoadedModule[239]=C:\FSX\GAUGES\Bendix_King_Radio.DLL LoadedModule[240]=C:\FSX\GAUGES\Bell_206B.DLL LoadedModule[241]=C:\Windows\system32\msimtf.dll LoadedModule[242]=C:\Windows\system32\msls31.dll LoadedModule[243]=C:\Windows\system32\d2d1.dll LoadedModule[244]=C:\Windows\system32\DWrite.dll LoadedModule[245]=C:\Windows\system32\D3D10Warp.dll LoadedModule[246]=C:\Windows\system32\ntmarta.dll LoadedModule[247]=C:\Windows\syswow64\WLDAP32.dll LoadedModule[248]=C:\FSXVistaMare\bin\ViMaIScnX_AP.dll LoadedModule[249]=C:\FSX\Aerosoft\Ase_Data\bin\dlls\aeroStyle-dll.dll Sec[0].Key=LCID Sec[0].Value=1031 FriendlyEventName=Nicht mehr funktionsfähig ConsentKey=APPCRASH AppName=Microsoft® Flight Simulator X AppPath=C:\FSX\fsx.exe And here is my dll.xml: <?xml version="1.0" encoding="windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>Addon Manager</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>bglmanx.dll</Path> </Launch.Addon> <Launch.Addon> <Name>iFly Menu</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\Modules\iFly737NG.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow_PAKT.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_PAKT\Scenery\ObjectFlow_PAKT.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow_W52.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_W52\scenery\ObjectFlow_W52.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow_KCMW.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_KCMW\Scenery\ObjectFlow_KCMW.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow_CZST.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_CZST\Scenery\ObjectFlow_CZST.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow_74S.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_74S\Scenery\ObjectFlow_74S.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow_1WA6.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_1WA6\Scenery\ObjectFlow_1WA6.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Object Placement Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Traffic Toolbox</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Visual Effects Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Reality XP GNS WAAS Hardware</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\rxpGnsDriver.dll</Path> </Launch.Addon> <Launch.Addon> <Name>A2A Service</Name> <Disabled>False</Disabled> <Path>A2A\Shared\A2A_Service.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>VistaMare Core</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSXVistaMare\ViMaCoreX.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ASE-Data</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Aerosoft\ASE_DATA\AseData.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG HUD interface</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>GPS Module</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\GPSModule.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>AirbusNewHUD</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Addon Modules\AirbusNewHUD.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>FeelThere PIC737X v2 Helper</Name> <Disabled>False</Disabled> <Path>FeelThere\B737 v2\PIC737XH.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FeelThere EJetX Helper</Name> <Disabled>False</Disabled> <Path>FeelThere\E170\EJetH.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Flight Recorder</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path> </Launch.Addon> <Launch.Addon> <Name>RAASPRO</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>.\RAASPRO\RAASPRO.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>PMDG Options</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGOptions.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Events</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGEvents.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Sounds</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGSounds.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSForce DLL</Name> <Disabled>false</Disabled> <ManualLoad>true</ManualLoad> <Path>C:\FSForce 2\FSForce.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4_Loader.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Level-D Simulations</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\LVLD.dll</Path> </Launch.Addon> </SimBase.Document> This starts to get really annoying!
April 16, 201313 yr The g3d.dll and ntdll.dll are related to memory. You have the latest Microsoft Visuals C++ 2005,2008, and 2010 installed. Good. The g3d.dll and ntdll.dll successfully loaded. FSX may be trying to render a texture or object and cannot find it so crashes. You should try running fsx with the following triggers enabled: [sCENERY]// Alert for missing texturesShowMissingTextureAlert=1// Alert for missing objectsMissingLibraryAlert=1// Render Trigger areas as visible boxes//ShowTriggers=0 This one does not need to be loaded unless you want to see a box around the missing texture or object. If there is a problem with a missing texture/object, it will show details about it then you can continue your flight and your sim will not crash. But, if it sees no missing texture/object your sim will probably crash. Your dll.xml appears to be okay. You have some really old products not originally made for FSX installed and any one of them could be causing a problem. Just before your CTD, the last module loaded was the AES module. It is installed with Aerosoft scenery so you can update the product or get the product activated. You should be able to uninstall this module. It has caused problems in the past. Another thing you can do is start up FSX and, at the startup screen click on Settings then Save.... Save the current settings as My Original FSX Config. Now open up Customize and select Reset Defaults under each Tab. This will return all of your FSX settings under the various tabs to the default but leave everything else, like tweaks, enabled. Now run FSX and see if this fixes the problem. This is usually better than deleting or renaming the fsx.cfg and then restarting fsx and letting the config rebuild. If it fixes the problem, then it was high settings. If the crashes still continue, then it could also be one of your tweaks from Bojote as mentioned earlier and the only way to find out about that is to delete the fsx config and let it rebuild when fsx restarts. Let's try these options and see if it fixes the problem. If not, we'll go from there. 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
May 2, 201313 yr Sorry, it took a little time to try out all your suggetions, but this is what I came up with:-Adding the lines to the cfg for showing missing objects didn´t bring any results, everything seems to be fine-starting FSX with a completely fresh cfg lead into the same problems. The rotating plane stops rotating after a few seconds, and most of the times, the sim kept crashing after that (ntdll.dll, user32.dll...)-from time to time, I get an error message while booting up FSX that there is a problem with the LVLD.dll, and if I want to load it anyway-even if I turn down the sliders significantally, the same phenomenon persistsOn my last flight yesterday, I had to start up FSX 5 times before I could set up my flight. The sim crashed after showing the FSX main menu, but it also crashed right before showing the menu, without any error message. It really looks as if there was some corrupt file being loaded the moment the sim crashes. The LED on my computer case, indicating HDD activity, always shows much activity at that moment. (I have a SSD installed)I´d like to point out again, that once the flight is loaded, the sim is super stable, with very nice frame rates, no problems when going into FSX menus or making changes in the FS2Crew panel etc.I bought my new PC with the SSD for the improved booting and load times. This annoying problem takes this advantage more or less completely away...
May 3, 201313 yr I get an error message while booting up FSX that there is a problem with the LVLD.dll, and if I want to load it anyway You need to fix this problem don't you? It could be the problem. Regarding booting and load times, I have an SSD and it does load fast with just fsx, gex, and acceleration installed. It's when I start adding addons and stuff when things got slowed down. I was starting up fsx in 20 seconds or less with the basic, but now, with all the addons, it now takes over 5 minutes to load. An ssd is not going to give you much improvement with a lot of addons. Have you ever run Process Monitor (Google) then start up fsx. When FSX crashes, click on Process Monitor then hit Ctrl+E. This will save a lot of everything that happened from the time you started up fsx to the time it crashed. It might give you a hint as to what might be causing the crash(es). 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
June 18, 201312 yr I found the problem! Finally! Yeah, Jim, you were right, the Level-D dll was the problem! But I renamed the wrong dll, so the problem still occurred. There is a LVLD.dll and a LVLD767.dll. I just didn´t recognised that. I kept looking for solutions, tried different things, and all the time, the solution was there! Oh my... ;-) So, after renaming the LVLD.dll and therefore disabling it, my sim is super stable again, no problems at all during booting up or flying. As a nice side effect during all my searching on AVSIM and on the web, I found a thread by Word Not Allowed here on AVSIM, how to enable Vsync in windowed mode. Now, I am able to fly online again, without fearing the sim to crash or even not to start, and all that with super smooth graphics and performance in windowed mode! WOW! AVSIM really can be a great place! Thanks again for your help!
June 18, 201312 yr Glad you got it figured out. It's a frustrating process but nice when FSX starts working right again. 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