Sign in to follow this  
jabloomf1230

FSX Steam Edition terrain.dll crash

Recommended Posts

See details below. It only seems to happen with DX10 and the DX10Fixer.

Faulting application name: fsx.exe, version: 10.0.62607.0, time stamp: 0x548b7186
Faulting module name: terrain.dll, version: 10.0.62607.0, time stamp: 0x548b71c0
Exception code: 0xc0000005
Fault offset: 0x0008fb36
Faulting process id: 0xa84
Faulting application start time: 0x01d01c8abfcffc81
Faulting application path: D:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Program Files (x86)\Steam\steamapps\common\FSX\terrain.dll
Report Id: fe93ac73-887e-11e4-81db-001fbc02953f
Faulting package full name: 
Faulting package-relative application ID: 

The crash happens with default aircraft at random times during a flight. I have ORBX Global, ORBX Vector and FS2010 Global Mesh installed under Win 8.1. All are the most recent versions. FSX SE in DX9 is fine. The FSX CD version is not installed.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

According to my research, the terrain.dll CTD usually indicates high scenery/terrain setting, especially Autogen in FSX/P3D. In your case, the DX10 Fixer may not be completely compatible with SE as it has to modify the general10.fx (used for DX10 only). In FSX, many had this issue when trying to modify the general10.fx. I think it has something to do with sharing. At least you have it narrowed down to DX10.

 

Best regards,

Share this post


Link to post
Share on other sites

Thanks Jim. It doesn't happen all the time, so I'll try turning down some of the IQ settings.

Share this post


Link to post
Share on other sites

Now get this:If it takes a long time to select the alternative aircraft, when I am eventually returned to the Free Flight screen, I exit FSX. Then I re-start FSX and select a different aircraft it is loaded within seconds and I get back to my Free Flight screen. I then click on the Fly Now button and VOILA a trouble free flight of many hours - to date 3 hours without BSOD. Since adopting this procedure I have yet to experience the problem.Additional Notes:I do not access the in flight menu options during my flight - I don't know if this is significant, i don't do it just in case. Besides, it makes the flying experience more realistic as there is no menu in a real aircraft!I have had to sacrifice my dual screen set up as that seemed to cause the problem in spite of my 'cure'.I have not backed-off any of my sliders. I don't know if this helps anyone out there, but it costs nothing to try. I would be interested to know why this might have cured my problems.

 

Well, this old post regarding FSX seems to point out a way around it and it works for me for FSX-SE, for the same unknown reason. Even with this, I'm not confident that the bug won't return.

 

Hasnt ORBX stated their libraries need to be updated to work reliably with FSX:SE?

It's very possible, but I thought that ObjectFlow was the only thing not working in FSX-SE.

Share this post


Link to post
Share on other sites

So you are confirming that you are getting the same error? Do you have any ORBX add-ons installed? 

Share this post


Link to post
Share on other sites

I have the same problem, crashing of FSX SE, after certain time. I have only installed ORBX Global. 

Share this post


Link to post
Share on other sites

Good morning from Germany.. I have the same problem with CTD related to terrain.dll. And also i habe FTX GLobal, Vector and Open LC installed. Hope it´s a problem with OrbX(Libs) and it will fixed soon.

Share this post


Link to post
Share on other sites

Yeaahh .. ^ i have global , vector and openLC too ... It could be the problem ...

 

FYI : I was getting terrain.dll error too -__-

Share this post


Link to post
Share on other sites

I am having the exact same issue with a completely stock install of the Steam version. I have not added a single aircraft or addon to it yet, but still get this terrain.dll crash. Oddly for me the last time it done it the aircraft was in the middle of the Atlantic so not much in the way of scenery to load.

Share this post


Link to post
Share on other sites

Hmmm. And I thought it was only me. It appears to be something inherent in FSX-SE. Others in this thread are getting the same error without DX10 and also without ORBX products installed.

Share this post


Link to post
Share on other sites

Some people on Steam are reporting that the error is disappearing once they run the cfg through Bojote's cfg tool!

Share this post


Link to post
Share on other sites

That sounds like someone had a bad tweak in the file and ran the bojote tweaks and it fixed one or more parameter. It's just hard for me to believe that a tweak made for older computer systems is fixing a problem in modern computer systems. If you have a system before the i7 CPU, then those tweaks might work effectively but one has to be very careful. If you do not know that the tweak does, then you shouldn't be putting the parameter into your configuration. Thanks to Bojote several years ago for helping us to get the most out of our old systems.

 

Best regards,

Share this post


Link to post
Share on other sites

I've done all of above and still getting crashes, did the tweak with Bojote's, brought the autogen sliders back to normal, and still getting crashes with terrain.dll. On my honest opinion, its gotta have to do with the fsx software, that dll, is definitely corrupt...

Share this post


Link to post
Share on other sites

I can confirm i was getting the same terrain.dll errors with fresh install of windows 7, fresh install of FSX SE, FTX GLobal, FTXVector and FSGlobal Ultimate. I have since re-installed FSX SE and FSGlobal Ultimate and have been flying for almost a week without errors. 

Share this post


Link to post
Share on other sites

It's apparently a bug. I can't use FSX-SE anymore with all these CTDs, so I'm thinking of uninstalling it and going back to FSX Gold. I will keep watching this thread, though.

Share this post


Link to post
Share on other sites

Jabloomf1230,

 

Do you get an objectflow.dll error as well when starting FSX:SE? I'm thinking there may be small incompatibilities between Orbx and FSX:SE that will have to get patched up.

Share this post


Link to post
Share on other sites

I was going to move this over to the FSX Forum in hopes more people will see it and offer a fix but I moved a similar post this morning and you should watch that one on the FSX Forum for solutions.

 

I think one of the things you have to look at is, did this happen when you first installed FSX-SE and ran it in the default configuration? Most likely, the answer is no as there are only a few of you that are having this problem (there's another topic about this too in the FSX Forum). That's the way I look at things. If it happens in the default configuration, then I agree, there is a bug in the product but, if you have a lot of addons, tweaks, and high settings, then, you are moving a long way from having a default configuration and it could be anyone of those things you did after you first installed the product.

 

The AVSIM CTD Guide has suggestion for bringing your configuration back to the default, just to test to see if it is the basic product that is causing the problem. Rebuilding the config has been known for fixing a multitude of problems mainly because people throw tweaks into the config that are just not working. Tweaks might improve performance but I have yet to see any except those that give the user a placebo effect.

 

You can also try running Process Monitor with only FSX-SE and FSX-SE addons loading in the monitor. This is explained on page 4 of the AVSIM CTD Guide. All you would have to do is start up FSX-SE to the startup screen, then startup Process Monitor then configure it as explained in the guide. Once configured, you'll only see what is loading in the FSX-SE. As soon as you get an error, you need to write down the time. Then, you can go back and look at the Process Monitor log and see what was loading just before the crash. It will not solve your problem but it will give you a clue as to the product(s) that are possibly the culprits. Disable those and try again.

 

Hope this helps.

 

Best regards,

Share this post


Link to post
Share on other sites

I do not own that product so cannot advise. Seems like I have seen a lot of "issues" though.

 

Best regards,

Share this post


Link to post
Share on other sites

Terrain.dll appcrash here as well.  What a shame.  I was trying to test the VAS usage with the PMDG 777-300ER on a DFW-HKG flight.  It happened about 4 hours into the flight in northern CAN.  I have FTX Global and Vector installed.  Objectflow.dll had been removed from my DLL.XML file due to errors. I have autogen and scenery complexity set to Dense.

Share this post


Link to post
Share on other sites

you could verify the integrity of game cache via  steam  local  in game property ,  it did not mess with anything in my case , but  back up  just in case.

fix a lot  of  bug after miss manipulating  different  files

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