Jump to content
Sign in to follow this  
Followers 0
Bjoern

FSXSE terrain/g3d.dll related crashes

By Bjoern, in Crash To Desktop (CTD) Forum

Recommended Posts

Bjoern    1,157

Bjoern
Posted

Nice! Glad you're figuring these things out quickly.

 

To be fair, I was very lucky in that the crash was easily reproducible.

 

It might have taken a bit (much) longer, had it I gotten the crash in-flight.

7950X3D + 6900 XT + 64 GB + Linux | 4800H + RTX2060 + 32 GB + Linux
My add-ons from my FS9/FSX days

Share this post

Link to post
Share on other sites

AviatorMoser    353

AviatorMoser
Posted

I'm having some luck with Bojote's tweaks. I usually get crashes halfway through a long haul (8 hr flights), but after the tweaks, the crash frequency has dropped remarkably. I've only gotten that one crash over northern Canada with Bojote's tweaks.

Share this post

Link to post
Share on other sites

hadoken    1

hadoken
Posted

Unfortunately even after my recommendations that I posted, I started getting g3d.dll errors again. So to I investigated the issue a little more. I read somewhere that these errors can also occur if your scenery files did not install correctly, or are missing. I'm sorry I can't remember the source, but if you search Google something to this effect should turn up.

 

To eliminate all possible variables, I completely uninstalled FSX-SE and all add-ons. I re-downloaded FSX-SE from the Steam servers and installed Global, Vector, OpenLC and then FS Global 2010 as indicated in the guide that I referenced in my recommendations post.

 

This time I decided not to reinstall any of the Orbx free or payware scenery, or Orbx Libraries. Just to rule out the chance of any non FSX-SE compatible installer corrupting the fresh installation. I only installed the Orbx products that I referenced in the previous paragraph.

 

I then installed all my payware scenery.

 

Next I installed all payware aircraft. I decided not to re-install the Level D 767 since it has not been confirmed to have a installer specifically compatiable for FSX-SE. I did install other payware aircraft that is confirmed FSX-SE compatible such as, PMDG 777, Aerosoft Airbus etc.

 

After reinstallation of FSX-SE, I have not seen any g3d.dll or terrain.dll errors. I have completed several hours of flight time, short and long range and still no issues. Something that was not possible in my first installation.

 

So I can only conclude, at least in my case that something in my first installation had corrupted some of the scenery files. I have downloaded many games from the Steam servers in the past with no issues. Maybe one of the non confirmed compatible products I listed above overwrote critical files. I can't say for sure. However reinstalling, and eliminating the above factors have fixed this issue for me. It's a lot of work to reinstall everything, but if you have tried everything else, and nothing has worked then you can give this option a try.

Share this post

Link to post
Share on other sites

spesimen    135

spesimen
Posted

i posted this to another thread but will add here because it's relevant.

 

found another 100% reproducible g3d.dll crash, this time it's easy to repro and only takes a few minutes

 

pmdg 777, takeoff from EGLL runway 27L compton 3g departure. will crash within a couple minutes every time. same offset, same g3d.dll.

 

it goes away if you use ftx global, but happens with hybrid or europe region enabled. (talking about ftx england pack here although i have all the british isles ones installed). i also was unable to repro it with the default cessna although it doesn't seem like a VAS issue as my monitor showed at near 1.5Gb free every time. EDIT: confirmed also occurs with dash8-Q400. i wonder if the cessna one didn't occur since i just flew direct cdt instead of flying the sid. weird.

 

things i tried- clean fsx.cfg, venetubo tweaks, bufferpools usepools=0 or not, affinitymask 14 and 84 or no entry, various levels of scenery complexity (still crashed with extremley dense, very dense, and dense) didn't try lower yet cause it was getting boring crashing over and over...

 

fun times! at least it seems to jibe with other people's experience of removing ftx england to solve it although this is less than ideal of course

 

Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4
Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd
Exception code: 0xc0000005
Fault offset: 0x000c7c0a
Faulting process id: 0x2844
Faulting application start time: 0x01d039bfc7bde7ea
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Steam\steamapps\common\FSX\g3d.dll
Report Id: badeb191-a5b4-11e4-889f-e0cb4e2c4e6f
 
 
cheers
-andy crosby

Share this post

Link to post
Share on other sites

sidhantsv    1

sidhantsv
Posted

egc1a0.png

 

 

I'm constantly getting CTD's during Ultra Long Hauls and Long Hauls . APPCRASHVIEW says its a terrain.dll error *exhales* again!

 

 

Any hope for me  :P  :unsure: ?

 

I don't have any terrain mesh addons nor many Scenery Airport addons !

 

( Happened to me while flying from LSZH Zurich to WSSS changi approx 2hrs in to the flight )

PMDG 777 btw.

 

heres the APPCRASHVIEW entry--

 

Version=1
EventType=APPCRASH
EventTime=130670693637617895
ReportType=2
Consent=1
UploadTime=130670693640189723
ReportIdentifier=f24fc931-a840-11e4-beeb-94de80a54a51
IntegratorReportIdentifier=f24fc930-a840-11e4-beeb-94de80a54a51
WOW64=1
NsAppName=fsx.exe
Response.BucketId=e0e61976f37ccfc9444036541416fd08
Response.BucketTable=1
Response.LegacyBucketId=73798284701
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.62608.0
Sig[2].Name=Application Timestamp
Sig[2].Value=54abe5b4
Sig[3].Name=Fault Module Name
Sig[3].Value=terrain.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.62608.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=54abe5e1
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00059be8
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=16393
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=f304
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=f304717eeed43189b7c0d7c053f4a949
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=7ebc
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=7ebcf995f7a3c4bc1c9043de621f745a
UI[2]=E:\FSX\steamapps\common\FSX\fsx.exe
UI[3]=Microsoft Flight Simulator® has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=E:\FSX\steamapps\common\FSX\fsx.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\Program Files\Bitdefender\Bitdefender\Active virus Control\Avc3_00291_034\avcuf32.dll
LoadedModule[5]=C:\WINDOWS\system32\apphelp.dll
LoadedModule[6]=C:\WINDOWS\AppPatch\AcLayers.DLL
LoadedModule[7]=C:\WINDOWS\SYSTEM32\msvcrt.dll
LoadedModule[8]=C:\WINDOWS\SYSTEM32\USER32.dll
LoadedModule[9]=C:\WINDOWS\SYSTEM32\GDI32.dll
LoadedModule[10]=C:\WINDOWS\SYSTEM32\SHELL32.dll
LoadedModule[11]=C:\WINDOWS\SYSTEM32\SHLWAPI.dll
LoadedModule[12]=C:\WINDOWS\SYSTEM32\OLEAUT32.dll
LoadedModule[13]=C:\WINDOWS\SYSTEM32\MPR.dll
LoadedModule[14]=C:\WINDOWS\SYSTEM32\SETUPAPI.dll
LoadedModule[15]=C:\WINDOWS\SYSTEM32\sfc.dll
LoadedModule[16]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
LoadedModule[17]=C:\WINDOWS\SYSTEM32\RPCRT4.dll
LoadedModule[18]=C:\WINDOWS\SYSTEM32\combase.dll
LoadedModule[19]=C:\WINDOWS\SYSTEM32\CFGMGR32.dll
LoadedModule[20]=C:\WINDOWS\SYSTEM32\SspiCli.dll
LoadedModule[21]=C:\WINDOWS\SYSTEM32\sfc_os.DLL
LoadedModule[22]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[23]=C:\WINDOWS\SYSTEM32\sechost.dll
LoadedModule[24]=C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll
LoadedModule[25]=C:\WINDOWS\AppPatch\AcSpecfc.DLL
LoadedModule[26]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.17415_none_7c5769eaaa0aa358\COMCTL32.dll
LoadedModule[27]=C:\WINDOWS\SYSTEM32\mscms.dll
LoadedModule[28]=C:\WINDOWS\SYSTEM32\ADVAPI32.dll
LoadedModule[29]=C:\WINDOWS\SYSTEM32\ole32.dll
LoadedModule[30]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[31]=C:\WINDOWS\SYSTEM32\DDRAW.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\COMDLG32.dll
LoadedModule[34]=C:\WINDOWS\SYSTEM32\IMM32.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\WS2_32.dll
LoadedModule[36]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\msi.dll
LoadedModule[38]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[39]=C:\WINDOWS\SYSTEM32\DCIMAN32.dll
LoadedModule[40]=C:\WINDOWS\SYSTEM32\profapi.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\SHCORE.DLL
LoadedModule[42]=C:\WINDOWS\SYSTEM32\MSCTF.dll
LoadedModule[43]=C:\WINDOWS\SYSTEM32\NSI.dll
LoadedModule[44]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll
LoadedModule[45]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[46]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCR80.dll
LoadedModule[47]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCP80.dll
LoadedModule[48]=E:\FSX\steamapps\common\FSX\steam_api.dll
LoadedModule[49]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[50]=E:\FSX\steamapps\common\FSX\language.dll
LoadedModule[51]=C:\Program Files (x86)\Steam\steamclient.dll
LoadedModule[52]=C:\WINDOWS\SYSTEM32\CRYPT32.dll
LoadedModule[53]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule[54]=C:\WINDOWS\SYSTEM32\imagehlp.dll
LoadedModule[55]=C:\WINDOWS\SYSTEM32\PSAPI.DLL
LoadedModule[56]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[57]=C:\Program Files (x86)\Steam\tier0_s.dll
LoadedModule[58]=C:\Program Files (x86)\Steam\vstdlib_s.dll
LoadedModule[59]=C:\WINDOWS\SYSTEM32\Secur32.dll
LoadedModule[60]=C:\WINDOWS\SYSTEM32\MSASN1.dll
LoadedModule[61]=C:\WINDOWS\SYSTEM32\WINNSI.DLL
LoadedModule[62]=C:\Program Files (x86)\Steam\steam.dll
LoadedModule[63]=C:\Program Files (x86)\Steam\Steam2.dll
LoadedModule[64]=C:\WINDOWS\SYSTEM32\DbgHelp.dll
LoadedModule[65]=C:\Program Files (x86)\Steam\CSERHelper.dll
LoadedModule[66]=C:\Program Files (x86)\Steam\gameoverlayrenderer.dll
LoadedModule[67]=E:\FSX\steamapps\common\FSX\API.DLL
LoadedModule[68]=E:\FSX\steamapps\common\FSX\ablscpt.dll
LoadedModule[69]=E:\FSX\steamapps\common\FSX\acontain.dll
LoadedModule[70]=E:\FSX\steamapps\common\FSX\ai_player.dll
LoadedModule[71]=E:\FSX\steamapps\common\FSX\atc.dll
LoadedModule[72]=E:\FSX\steamapps\common\FSX\controls.dll
LoadedModule[73]=E:\FSX\steamapps\common\FSX\demo.dll
LoadedModule[74]=E:\FSX\steamapps\common\FSX\facilities.dll
LoadedModule[75]=E:\FSX\steamapps\common\FSX\fe.dll
LoadedModule[76]=E:\FSX\steamapps\common\FSX\flight.dll
LoadedModule[77]=E:\FSX\steamapps\common\FSX\fsui.dll
LoadedModule[78]=E:\FSX\steamapps\common\FSX\g2d.dll
LoadedModule[79]=E:\FSX\steamapps\common\FSX\g3d.dll
LoadedModule[80]=E:\FSX\steamapps\common\FSX\gps.dll
LoadedModule[81]=E:\FSX\steamapps\common\FSX\livingwater.dll
LoadedModule[82]=E:\FSX\steamapps\common\FSX\main.dll
LoadedModule[83]=E:\FSX\steamapps\common\FSX\multiplayer.dll
LoadedModule[84]=E:\FSX\steamapps\common\FSX\panels.dll
LoadedModule[85]=E:\FSX\steamapps\common\FSX\sim1.dll
LoadedModule[86]=E:\FSX\steamapps\common\FSX\simprop.dll
LoadedModule[87]=E:\FSX\steamapps\common\FSX\simscheduler.dll
LoadedModule[88]=E:\FSX\steamapps\common\FSX\sound.dll
LoadedModule[89]=E:\FSX\steamapps\common\FSX\symmap.dll
LoadedModule[90]=E:\FSX\steamapps\common\FSX\terrain.dll
LoadedModule[91]=E:\FSX\steamapps\common\FSX\fs-traffic.dll
LoadedModule[92]=E:\FSX\steamapps\common\FSX\ui.dll
LoadedModule[93]=E:\FSX\steamapps\common\FSX\util.dll
LoadedModule[94]=E:\FSX\steamapps\common\FSX\visualfx.dll
LoadedModule[95]=E:\FSX\steamapps\common\FSX\weather.dll
LoadedModule[96]=E:\FSX\steamapps\common\FSX\window.dll
LoadedModule[97]=E:\FSX\steamapps\common\FSX\xuipc.dll
LoadedModule[98]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll
LoadedModule[99]=C:\WINDOWS\SYSTEM32\SHFOLDER.dll
LoadedModule[100]=C:\WINDOWS\SYSTEM32\POWRPROF.dll
LoadedModule[101]=C:\WINDOWS\SYSTEM32\DINPUT8.dll
LoadedModule[102]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.17415_none_dad8722c5bcc2d8f\gdiplus.dll
LoadedModule[103]=C:\WINDOWS\SYSTEM32\d3dx9_34.dll
LoadedModule[104]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[105]=C:\WINDOWS\SYSTEM32\d3dx10_34.dll
LoadedModule[106]=C:\WINDOWS\SYSTEM32\d3d9.dll
LoadedModule[107]=E:\FSX\steamapps\common\FSX\sdkencryptedappticket.dll
LoadedModule[108]=C:\WINDOWS\SYSTEM32\DSOUND.dll
LoadedModule[109]=C:\WINDOWS\SYSTEM32\MSACM32.dll
LoadedModule[110]=C:\WINDOWS\SYSTEM32\MSIMG32.dll
LoadedModule[111]=C:\WINDOWS\SYSTEM32\iertutil.dll
LoadedModule[112]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[113]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[114]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[115]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[116]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[117]=C:\WINDOWS\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL
LoadedModule[118]=C:\WINDOWS\SYSTEM32\clbcatq.dll
LoadedModule[119]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[120]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[121]=C:\WINDOWS\SYSTEM32\d3d11.dll
LoadedModule[122]=C:\WINDOWS\SYSTEM32\nvd3dum.dll
LoadedModule[123]=C:\WINDOWS\system32\nvspcap.dll
LoadedModule[124]=C:\WINDOWS\SYSTEM32\D3DCompiler_34.dll
LoadedModule[125]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
LoadedModule[126]=C:\WINDOWS\SYSTEM32\d3d10_1.dll
LoadedModule[127]=C:\WINDOWS\SYSTEM32\d3d10_1core.dll
LoadedModule[128]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[129]=C:\Windows\SYSTEM32\dxdiagn.dll
LoadedModule[130]=C:\WINDOWS\system32\wbem\wbemprox.dll
LoadedModule[131]=C:\WINDOWS\SYSTEM32\wbemcomn.dll
LoadedModule[132]=C:\WINDOWS\system32\wbem\wbemsvc.dll
LoadedModule[133]=C:\WINDOWS\system32\wbem\fastprox.dll
LoadedModule[134]=C:\WINDOWS\system32\winbrand.dll
LoadedModule[135]=C:\WINDOWS\SYSTEM32\WINTRUST.dll
LoadedModule[136]=C:\WINDOWS\system32\nvapi.dll
LoadedModule[137]=C:\WINDOWS\SYSTEM32\WTSAPI32.DLL
LoadedModule[138]=C:\WINDOWS\SYSTEM32\WINSTA.dll
LoadedModule[139]=C:\Windows\SYSTEM32\gameux.dll
LoadedModule[140]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17415_none_a9ed7f470139b3c1\COMCTL32.dll
LoadedModule[141]=C:\Windows\SYSTEM32\XmlLite.dll
LoadedModule[142]=C:\Windows\SYSTEM32\msxml6.dll
LoadedModule[143]=C:\WINDOWS\System32\Wpc.dll
LoadedModule[144]=C:\WINDOWS\System32\NETAPI32.dll
LoadedModule[145]=C:\WINDOWS\SYSTEM32\Normaliz.dll
LoadedModule[146]=C:\WINDOWS\System32\wevtapi.dll
LoadedModule[147]=C:\WINDOWS\System32\netutils.dll
LoadedModule[148]=C:\WINDOWS\System32\srvcli.dll
LoadedModule[149]=C:\WINDOWS\System32\wkscli.dll
LoadedModule[150]=C:\WINDOWS\System32\SAMCLI.DLL
LoadedModule[151]=C:\Windows\System32\Windows.Globalization.dll
LoadedModule[152]=C:\Windows\System32\Bcp47Langs.dll
LoadedModule[153]=C:\Windows\System32\Windows.Web.dll
LoadedModule[154]=E:\FSX\steamapps\common\FSX\uiautomationcore.dll
LoadedModule[155]=C:\WINDOWS\SYSTEM32\OLEACC.dll
LoadedModule[156]=C:\WINDOWS\System32\MMDevApi.dll
LoadedModule[157]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL
LoadedModule[158]=C:\WINDOWS\SYSTEM32\RICHED20.DLL
LoadedModule[159]=C:\WINDOWS\SYSTEM32\USP10.dll
LoadedModule[160]=C:\WINDOWS\SYSTEM32\msls31.dll
LoadedModule[161]=C:\WINDOWS\SYSTEM32\HID.DLL
LoadedModule[162]=C:\WINDOWS\SYSTEM32\XInput9_1_0.dll
LoadedModule[163]=C:\WINDOWS\SYSTEM32\wdmaud.drv
LoadedModule[164]=C:\WINDOWS\SYSTEM32\ksuser.dll
LoadedModule[165]=C:\WINDOWS\SYSTEM32\AVRT.dll
LoadedModule[166]=C:\WINDOWS\SYSTEM32\msacm32.drv
LoadedModule[167]=C:\WINDOWS\SYSTEM32\midimap.dll
LoadedModule[168]=C:\WINDOWS\SYSTEM32\dinput.DLL
LoadedModule[169]=C:\WINDOWS\SYSTEM32\XInput1_4.dll
LoadedModule[170]=E:\FSX\steamapps\common\FSX\PMDG\DLLs\PMDG_Interface.dll
LoadedModule[171]=C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[172]=E:\FSX\steamapps\common\FSX\RAASPRO\RAASPRO.dll
LoadedModule[173]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll
LoadedModule[174]=C:\WINDOWS\SYSTEM32\winhttp.dll
LoadedModule[175]=C:\WINDOWS\SYSTEM32\DNSAPI.dll
LoadedModule[176]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
LoadedModule[177]=C:\Windows\System32\rasadhlp.dll
LoadedModule[178]=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule[179]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll
LoadedModule[180]=C:\WINDOWS\SYSTEM32\MSDART.DLL
LoadedModule[181]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll
LoadedModule[182]=C:\Windows\SYSTEM32\comsvcs.dll
LoadedModule[183]=C:\Windows\SYSTEM32\msjetoledb40.dll
LoadedModule[184]=C:\Windows\SYSTEM32\msjet40.dll
LoadedModule[185]=C:\Windows\SYSTEM32\msjter40.dll
LoadedModule[186]=C:\Windows\SYSTEM32\mswstr10.dll
LoadedModule[187]=C:\Windows\SYSTEM32\MSJINT40.DLL
LoadedModule[188]=C:\WINDOWS\SYSTEM32\DPAPI.DLL
LoadedModule[189]=C:\Windows\SYSTEM32\mstext40.dll
LoadedModule[190]=C:\WINDOWS\SYSTEM32\mlang.dll
LoadedModule[191]=C:\WINDOWS\SYSTEM32\RAASAUDIO32.DLL
LoadedModule[192]=C:\WINDOWS\SYSTEM32\X3DAudio1_6.dll
LoadedModule[193]=C:\WINDOWS\SYSTEM32\xactengine3_4.dll
LoadedModule[194]=C:\WINDOWS\SYSTEM32\XAudio2_4.dll
LoadedModule[195]=E:\FSX\steamapps\common\FSX\Aerosoft\Flight Recorder\AS-FlightRecorder.dll
LoadedModule[196]=E:\FSX\steamapps\common\FSX\VistaMare\ViMaCoreX.dll
LoadedModule[197]=E:\FSX\steamapps\common\FSX\Modules\FSUIPC4.dll
LoadedModule[198]=C:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dll
LoadedModule[199]=C:\WINDOWS\SYSTEM32\mfc100.dll
LoadedModule[200]=C:\WINDOWS\SYSTEM32\MSVCR100.dll
LoadedModule[201]=C:\WINDOWS\SYSTEM32\MSVCP100.dll
LoadedModule[202]=C:\WINDOWS\SYSTEM32\MFC100ENU.DLL
LoadedModule[203]=C:\WINDOWS\system32\propsys.dll
LoadedModule[204]=C:\Windows\SYSTEM32\ieframe.dll
LoadedModule[205]=C:\Windows\SYSTEM32\mshtml.dll
LoadedModule[206]=C:\WINDOWS\system32\msimtf.dll
LoadedModule[207]=C:\WINDOWS\SYSTEM32\d2d1.dll
LoadedModule[208]=C:\WINDOWS\SYSTEM32\DWrite.dll
LoadedModule[209]=C:\WINDOWS\SYSTEM32\d3d10warp.dll
LoadedModule[210]=C:\Windows\SYSTEM32\uiautomationcore.dll
LoadedModule[211]=e:\fsx\steamapps\common\fsx\GAUGES\PMDG_777X.DLL
LoadedModule[212]=C:\WINDOWS\SYSTEM32\WSOCK32.dll
LoadedModule[213]=C:\WINDOWS\SYSTEM32\XAudio2_7.dll
LoadedModule[214]=E:\FSX\steamapps\common\FSX\Gauges\PMDG_777X_2.dll
LoadedModule[215]=C:\WINDOWS\SYSTEM32\snmpapi.dll
LoadedModule[216]=C:\WINDOWS\system32\napinsp.dll
LoadedModule[217]=C:\WINDOWS\system32\pnrpnsp.dll
LoadedModule[218]=C:\WINDOWS\system32\NLAapi.dll
LoadedModule[219]=C:\WINDOWS\System32\winrnr.dll
LoadedModule[220]=C:\WINDOWS\SYSTEM32\icmp.Dll
LoadedModule[221]=C:\Windows\SYSTEM32\msjtes40.dll
LoadedModule[222]=C:\WINDOWS\SYSTEM32\VBAJET32.DLL
LoadedModule[223]=C:\WINDOWS\SYSTEM32\expsrv.dll
LoadedModule[224]=C:\Program Files (x86)\Common Files\System\ado\msadrh15.dll
LoadedModule[225]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[226]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Flight Simulator®
AppPath=E:\FSX\steamapps\common\FSX\fsx.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=7912059C691EC53D52465B2D04ABD1E8
 
 
AMAZINGLY This happened 3 hrs before my FSX Crashed (Or maybe I'm interpreting it wrong )

 

I don't fly offline , I fly on IVAO so I don't think AI might be a problem....

 

 

 

 

 

 

Intel i7 4770K , NVidia GTX 660ti , 8GB DDR3 Ram, 1TB Seagate SSD.

Share this post

Link to post
Share on other sites

FLAPS15    8

FLAPS15
Posted

Wow!

 

My FSX SE is still sitting in the download stage I have not installed as ASN is still not compatible..but after reading all the crashes I am now very reluctant to even think about porting over to SE...

 

Which is a shame given the reports on how well it runs in other areas....do hope DTG are reading these forum user notes and taking note to produce a fix if at all possible..

 

Will have to watch and wait ..sorry to see some of you having these issues very annoying..

So very frustrating when well into a flight which use to happen in the early days of FSX..

 

Come on DTG got any fixes lines up!

 

All the best

Share this post

Link to post
Share on other sites

sidhantsv    1

sidhantsv
Posted

Wow!

 

My FSX SE is still sitting in the download stage I have not installed as ASN is still not compatible..but after reading all the crashes I am now very reluctant to even think about porting over to SE...

 

Which is a shame given the reports on how well it runs in other areas....do hope DTG are reading these forum user notes and taking note to produce a fix if at all possible..

 

Will have to watch and wait ..sorry to see some of you having these issues very annoying..

So very frustrating when well into a flight which use to happen in the early days of FSX..

 

Come on DTG got any fixes lines up!

 

All the best

I would've never ported to FSX:SE but the fact that I owned WIN8.1 (where the boxed version crashed a lot!) 

I had to buy it!..

 

Hope DTG fix these annoying bugs :)

Share this post

Link to post
Share on other sites

Jim Young    2,356

Jim Young
Posted

 

 


MAZINGLY This happened 3 hrs before my FSX Crashed (Or maybe I'm interpreting it wrong )

 

You have the uiautomationcore.dll in the main FSX-SE folder.  It is not allowed there.  The uiautomationcore.dll is part of the Microsoft.net packages.  It only fixes one type of crash for FSX and FSX only:  The Menu Crash (where you right click inside of FSX and select a menu item at least 19 times).  Only a certain version works for FSX installation only.  It is not the holy grail of fixes for FSX crashes/freezes.  Remove it from your SE installation and go fly.  At one time the uiautomationcore.dll version placed in FSX only caused a memory leak in Windows 8.1.  This has since been fixed by Microsoft and we no longer have this warning in the CTD Guide. 

 

Again, lower your FSX-SE settings to the default (go to the scenery tab and click on reset to default).  You need to make sure you do not have high display driver settings too.

 

Best regards,

Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important 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 

 

Share this post

Link to post
Share on other sites

blueridgeflyer    1

blueridgeflyer
Posted

Wow!

 

My FSX SE is still sitting in the download stage I have not installed as ASN is still not compatible..but after reading all the crashes I am now very reluctant to even think about porting over to SE...

 

Which is a shame given the reports on how well it runs in other areas....do hope DTG are reading these forum user notes and taking note to produce a fix if at all possible..

 

Will have to watch and wait ..sorry to see some of you having these issues very annoying..

So very frustrating when well into a flight which use to happen in the early days of FSX..

 

Come on DTG got any fixes lines up!

 

All the best

I'm a long time FSX user and something is fundamentally flawed that is causing these terrain.dll errors for long haulers. FWIW my settings (autogen, complexity and mesh) are reasonable. I made the switch to FSX-SE to avoid the OOM errors. To that end it has been a success. But I don't recall witnessing many terrain.dll errors in FSX acceleration. In FSX-SE they are consistently reproduced at about 4 hrs of flight time. I'm looking for suggestions to keep the ball rolling on this "entertainment" platform. But from all accounts I will be making the leap over to P3D 2.5 in the future. I only hope that it is stable with the PMDG product line and leading scenery enhancements. Ill keep checking these forums on a daily basis for a solution to the SE terrain.dll problem. Good luck to all.

Ryan Kelly

Share this post

Link to post
Share on other sites

JRBarrett    3,070

JRBarrett
Posted

There seem to be many G3D crashes in STEAM, though I have not (as yet) experienced one. Then there is the stand-alone terrain.dll crash (with a specific fault code offset of 00059be8) which always seems to occur at just about 4 hours into a flight.

 

The 4-hour (approximate) time from beginning a flight to the crash has got me to wondering if this possibly could have something to do with the fact that FSX-SE has to be launched from within the main STEAM interface - and that there needs to be an active internet connection to log into the Steam servers (at least at first) before launching FSX. 

 

Could it possibly be that the parent STEAM application is doing something after being open for 4 hours that could be causing the terrain.dll crash? Some kind of lease renewal of the connection between the desktop app and the Steam server? Or some other internal process that runs after 4 hours, (give or take)  which interferes with the FSX process?

 

I may be barking up the wrong tree here, but there is something about the fact that this one particular terrain.dll crash (00059be8) only seems to happen after running the program for several hours is bugging me... what is it about the elapsed time that might be causing this?

Jim Barrett

Licensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.

Share this post

Link to post
Share on other sites

AviatorMoser    353

AviatorMoser
Posted

I may be barking up the wrong tree here, but there is something about the fact that this one particular terrain.dll crash (00059be8) only seems to happen after running the program for several hours is bugging me... what is it about the elapsed time that might be causing this?

 

Bugging me too! It's always around fours of elapsed sim-time.

Share this post

Link to post
Share on other sites

Jim Young    2,356

Jim Young
Posted

In the FSX-SE Forum you read about many who are having absolutely no problems and SE is running better than anything else.  I think you have to look now at what scenery you installed that maybe was not ready for installation as it did not make all the required entries.  For instance, I heard the FTX/Orbx stuff wasn't ready for proper installation.

 

Best regards,

Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important 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 

 

Share this post

Link to post
Share on other sites

AviatorMoser    353

AviatorMoser
Posted

In the FSX-SE Forum you read about many who are having absolutely no problems and SE is running better than anything else.  I think you have to look now at what scenery you installed that maybe was not ready for installation as it did not make all the required entries.  For instance, I heard the FTX/Orbx stuff wasn't ready for proper installation.

 

Best regards,

 

Yeah, FSX-SE does run great without problems during the first four hours, Jim, but it crashes usually where the scenery is sparse.

 

Greenland, the Black Sea, South China Sea. Usually halfway through an eight hour flight over water or near the coast. If it was scenery related, I'd figure the crashes would be more random, but they all seem to be consistently around the four hour mark. Which is bewildering to me.

Share this post

Link to post
Share on other sites

Jim Young    2,356

Jim Young
Posted

 

 


they seem to be consistently around the four hour mark.

 

Have you check the amount of Virtual Address Space (VAS) left?  In FSX, after two hours of flight over photoscenery or GEX, FSX will start running out of VAS (Memory).  When there's only about 400 MB's of VAS left or less then things start slowing down until FSX freezes or crashes.  You only get 4 GB's for any application.  I have rarely seen the terrain.dll error though.  That module is changed whenever you add or remove scenery programs and it really is a rare faulting module in FSX and P3D.

 

Best regards,

Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important 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 

 

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0
Go To Topic Listing

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...