Archived

This topic is now archived and is closed to further replies.

Sesquashtoo

As other users, FED UP with CTD's using FSX.

Recommended Posts

Look at my system specs below. It cost me $3000, a DOA Motherboard from New Egg, two weeks of waiting for a new motherboard to arrive, two days of putting the system together, one week of tweaking and overclocking, two weeks of reinstalling everything from scratch and only NOW is FSX working like it was meant to be 4 years ago.It is what it is.

Share this post


Link to post
Share on other sites

Good to hear you are not throwing in the towel just yet. I usually have 1 CTD per flight, but the CTD happens while I'm in the UI, before the simulation ahs even loaded. You see, with my FSX, the UI is terribly slow. I'm convinced is due to the massive amounts of scenery I have, including lots of photoreal scenery, but other that that, I can do flights without running into trouble.True, the FPS sometimes is truly awful, and I remember times when it was better. I'm quite sure that there is a DLL somewhere in there that is causing this, but I wouldn't know which one, and in fact, I don't really feel like starting all the fidgeting, tweaking and troubleshooting again.For me, FSX is okay. I hate it and I love it at the same time.

Share this post


Link to post
Share on other sites
-----------------------------------------------------------------Wow....I just got home from work....and dropped on into the forum. I almost feel ashamed 'for throwing in the towel' due to the truly great and supportive response to my venting thread. All of your responses deserves a 'one more' effort by myself. That is for sure. Since I always make an image back-up of my entire system, it will be a no-sweat to bring everything back onboard within about 30 minutes.I really do love what FSX brings to the table, but do NOT love the instability (at least on my system and config) as per my thread.I read through all the suggestions of you great bunch of folks...and first off....will start stripping out all the TWEAKS that we have accumulated over time to squeeze a few more drops out of performance. I will keep stripping them out and keep taking that KDTW-KMYR flight as a base line of reference. The first flight (I sure HOPE I fly one....) that allows me to land from along the original flight-path...will be my signal that I have isolated (at least in my config file...) the offending TWEAK/ENTRY. I will then publish that offending tweak..and hopefully it might stop the CTD's that any other user is experiencing. If I don't end up eliminating the CTD's...at least I can say to myself that I gave it the one last ol' college try...and made it worth your collective, and great support of another's FSX misery!It looks like it might be a long night....("Hey Honey....can you just slip the food under the door......and I love you for not rolling your eyes to much!) To reload the image backup and take a flight out of FSX's KDTW..... Wish me luck! I really want to keep FSX flying on this rig...but flying...and not crashing to the desktop. I already know what the desktop looks like! (large grin).Mitch
If only CTDs were constant. I flew TNCC-TNCM when I got a MSVCR80.DLL error. The next day I re-did the flight, with the exact same flightplan and exact same aircraft.This time it did not CTD.You cannot remove a tweak then fly KDTW-KMYR without CTDs and conclude that you've removed the offending tweak. You might get CTD some days later with the same .CFG

Share this post


Link to post
Share on other sites

We really need a database that looks at all the variables and evaluates which ones/combinations among surveyed users cause CTD or other undesireable behaviors like stutters, blurred textures, etc. I know we have ideas that suggest what to look at but how cool to have a registry that can evaluate the data.

Share this post


Link to post
Share on other sites

Mitch,Once upon a while, I observed those terrible ctds (g3d.dll errors) at various places with various settings. In my case it was the sound module entry of 'audio environment' in the dll.xml. Since then ctds are nearly gone. Keeping eyes on the dll.xml might be helpful - particularly if a lot of addon modules are installed. Another point which has been discussed is the fps limiter 0.2. Don't know if you use this one. You can also find a profound discussion on the ftx forums about those g3d.dll errors (http://www.orbxsystems.com/forum/topic/33032-an-open-letter-to-orbx-re-g3ddll-errors-in-pnw/). Harry

Share this post


Link to post
Share on other sites
Me too. Whilst I would agree that the amount of people saying they have problems surely indicates that there is some sort of issue, FSX has never been unstable on my machine, even when it was first released. The only time I have ever had a problem with it was when it once refused to reinstall until I did some messing about installing a few windows bits and pieces. Apart from that, it has and does run fine on my computer, and that's in either SP2 form, or with Acceleration.I suspect some of that might be down to the fact that I run it via XP, although to be fair, I do also run it on another machine using Vista, and that seems to work fine as well. I know that does not help the OP's complaint, but it is nevertheless not true to put over the impression that everyone who uses FSX is constantly beset by problems, for if it was, I would certainly say so.Al
Al,You are right about there having to be something up, since there is a large amount of people that still seem to experience CTD. I wonder if it is just random things or are the cases narrowing down to a certin aspect of the PC or software. I'm running FSX on Windows 7 64bit with 4GB of RAM and it runs great. I always run and install all add-ons and FSX using the "Run As Administrator" option. I remember when I had Vista 32bit I did get CTDs occationally, but mainly OOM errors. I would make sure FSX was the only app running and ran tools to close all non-essential background apps. That helped for a while, but what Fixed things was going up to 3GB. Now I'm running 4GB on Win 7 64bit and I my setup is solid.Have CTD errors started to narrow down to any 1 or 2 specific causes?

Share this post


Link to post
Share on other sites

HelloIt seem that most of the issues are from folks running W764.Microsoft themselves state that this OS is incompatible with FSX but not Acceleration for some reason.They have in some reported cases refused validation after installing FSX.Now for Microsoft to adjust is stance on compatibility with W764 between two of its own products, that decision must have come from logging a lot of customer support calls and data from the built in online crash reports.Why else would they put this on their compatability site.http://www.microsoft.com/windows/compatibility/windows-7/en-us/Search.aspx?type=Software&s=flight%20simulator%20x&os=64-bit

Share this post


Link to post
Share on other sites
Guest nzch2010
HelloIt seem that most of the issues are from folks running W764.Microsoft themselves state that this OS is incompatible with FSX but not Acceleration for some reason.They have in some reported cases refused validation after installing FSX.Now for Microsoft to adjust is stance on compatibility with W764 between two of its own products, that decision must have come from logging a lot of customer support calls and data from the built in online crash reports.Why else would they put this on their compatability site.http://www.microsoft...r%20x&os=64-bit
Rubbish. I have been using FSX on a 64 bit OS since W7 was released. That compatibility statement is mostly to do with program files X86 and UAC. Even a brain dead garden gnome knows how to overcome that.Have not had a CTD yet. If your OS is set up correctly, FSX is tuned correctly and not tweaked to death, you can have a very stable flight simming experience. Too state that CTD's in FSX are caused by W7 64 is folly, it is user error, plain and simple. Even badly coded scenery addons can cause CTD. Double afcads etc. W7 64, I don't think so my friend, you have been mis informed.What do you expect from Microsoft, that tells you to "press start to shut down windows"

Share this post


Link to post
Share on other sites
By the way have you never heard of sarcacsm?Bryan.
Have you ??

Share this post


Link to post
Share on other sites
Rubbish. I have been using FSX on a 64 bit OS since W7 was released. That compatibility statement is mostly to do with program files X86 and UAC. Even a brain dead garden gnome knows how to overcome that.Have not had a CTD yet. If your OS is set up correctly, FSX is tuned correctly and not tweaked to death, you can have a very stable flight simming experience. Too state that CTD's in FSX are caused by W7 64 is folly, it is user error, plain and simple. Even badly coded scenery addons can cause CTD. Double afcads etc. W7 64, I don't think so my friend, you have been mis informed.What do you expect from Microsoft, that tells you to "press start to shut down windows"
Vista also uses UAC, though.. so I don't think that's it. Also, FSX does store user data in the proper folder (c:\users\... rather than in the installation folder).Acceleration includes SP2, but SP2 itself does not count as a separate product. That's probably why FSX (RTM) is listed as incompatible while Acceleration is supposed to be compatible (though the UIAutomationCore.dll error in Win7 affects all versions of FSX...).

Share this post


Link to post
Share on other sites
Mitch, you're not having an out of memory error are you? That was the only thing that ever presented as a CTD for me and that was prior to my current PC and OS, and was secondary to the old and well known issue of having a, pardon my aging memory, an empty texture folder inside of a scenery folder. Sorry I really don't recall what the specifics were, but as I say it was a well known issue at the time I think.Good luck Mitch I hope you get it figured out as it is a very satisfying experience when it isn't broken. I think too for me, I don't have the hottest rig on the planet, but it's stable and plenty good 'nuf for enjoying. Tweaks beyond galore, EMBSeries this and FPS_limiter that and thrown in some new shaders and before long it's truly amazing everyone isn't suffering from CTD's!
------------------------------------------------------------------------------------------------------------Hi Noel, I didn't end up having a chance to run the test bed flight up and to the point that a terrain.dll CTD took me out. What I intend to do, is start stripping out the tweaks from the config and see at what point (crossing my fingers!!!) I can complete flights and stay afloat. If I have no success that way....I will just delete the .cfg file and let FSX rebuild. I had done that once, and was amazed at how much performance (FPS) you lose if you don't have at least some of the more popular tweaks published over the years. That's why I wish to start with just deleting them as I go...(with notes) and find if one of them might be the cause of true instability.
Good to hear you are not throwing in the towel just yet. I usually have 1 CTD per flight, but the CTD happens while I'm in the UI, before the simulation ahs even loaded. You see, with my FSX, the UI is terribly slow. I'm convinced is due to the massive amounts of scenery I have, including lots of photoreal scenery, but other that that, I can do flights without running into trouble.True, the FPS sometimes is truly awful, and I remember times when it was better. I'm quite sure that there is a DLL somewhere in there that is causing this, but I wouldn't know which one, and in fact, I don't really feel like starting all the fidgeting, tweaking and troubleshooting again.For me, FSX is okay. I hate it and I love it at the same time.
----------------------------------------------------------------As I strip out my tweak entries, if I find that I can fly with no CTD's...I'll publish the last stripped out tweak entry, before I found stability, and perhaps others can match it up to their CTD or three.

Share this post


Link to post
Share on other sites

Whoohoo! Just had a new CTD (although it happened on exit) Fault Module Name: simprop.dll

Share this post


Link to post
Share on other sites
HelloIt seem that most of the issues are from folks running W764.Microsoft themselves state that this OS is incompatible with FSX but not Acceleration for some reason.They have in some reported cases refused validation after installing FSX.Now for Microsoft to adjust is stance on compatibility with W764 between two of its own products, that decision must have come from logging a lot of customer support calls and data from the built in online crash reports.Why else would they put this on their compatability site.http://www.microsoft...r%20x&os=64-bit
If you read the entire thing, you will se they say that ONLY the 64 part of Win 7 is incompatible, the 32 bit part works just fine. Since FS is a 32 bit program, it don't take a rocket scientist to come up with that conclusion. I have been running FSX in it's default location since day 1 without any issues, except for one addon plane that caused problems, and thats now gone.

Share this post


Link to post
Share on other sites
Whoohoo! Just had a new CTD (although it happened on exit) Fault Module Name: simprop.dll
HelloWhat does your brain dead garden gnome say about it, can he not help you.
If you read the entire thing, you will se they say that ONLY the 64 part of Win 7 is incompatible, the 32 bit part works just fine. Since FS is a 32 bit program, it don't take a rocket scientist to come up with that conclusion. I have been running FSX in it's default location since day 1 without any issues, except for one addon plane that caused problems, and thats now gone.
HelloTell microsoft that, at this point they do not seem to agree with you hence they will not support you.Or reactivate you by phone once your installation limit is reached.

Share this post


Link to post
Share on other sites

"HelloTell microsoft that, at this point they do not seem to agree with you hence they will not support you.Or reactivate you by phone once your installation limit is reached. "Then they should read their own site, it clearly states its compatible with the 32 bit part of Win 7 64. I wouldnt waste my time in any case trying to deal with MS, these and other forums are much better at helping users, and a heck of a lot cheaper.

Share this post


Link to post
Share on other sites
Guest nzch2010
HelloWhat does your brain dead garden gnome say about it, can he not help you.HelloTell microsoft that, at this point they do not seem to agree with you hence they will not support you.Or reactivate you by phone once your installation limit is reached.
Research is it all it takes to build up a stable system using W7 64, and there is countless forums around including this one with very knowledgable people who share there expertise at no cost to the end user. Installing FSX and addons to the windows default location and UAC turned on including windows defender is asking for trouble. The only reason some were not able to activate FSX would be due to UAC turned on. UAC might be a good thing in a internet cafe, but certainly over the top for home use.Don't take too much notice of what Squishy posts, he may one day post something intelligent. He does nothing but bag FSX on here, and is becoming rather tiresome. Speaking of garden gnomes.......Raised%20Eyebrow.gif

Share this post


Link to post
Share on other sites
Don't take too much notice of what Squishy posts, he may one day post something intelligent. He does nothing but bag FSX on here, and is becoming rather tiresome. Speaking of garden gnomes.......Raised%20Eyebrow.gif
Oh grow up. What's tiresome is that after 5 years FSX still CTDs and nobody knows how to fix it. Then people open topics "hey I fixed my CTD, my GPU was overheating, try it now". THat's tiresome. I posted here years ago with CTD problems but apparently it cannot be fixed. If you do not experience CTDs, great. Good for you, but that doesn't FSX is stable and the problem lies with someone's computer.But you're right I might've been complaining a lot recently. It's just that only this month i've completely formatted and reinstalled FSX carefully, only to get a big fat CTD in my fase on final.

Share this post


Link to post
Share on other sites
There is one option a lot of us have used, and don't get any CTD's or any other problems with FSX .... www.fs-gs.com :(
You know it's funny Jay, but I was thinking the same thing. We both had our whole system tuned and set up professionally and have no problems, CTD's, or other annoyances. To this day I don't understand how some people, especially if they have the money (Mitch), don't use FS-GS to get set properly, especially if they are dogged with problems all the time. Even funnier is that those who use FS-GS swear by it and those who don't dog it, but yet continue to waste time and engery trying to figure out how to get it working properly.Even funnier, you mention Michael and "Squishy" says "$85?? LMAAAAAOOOOOO!!!!!!!"At this point I think "Squishy" gets more satisfaction in complaining about FSX, posting about FSX dll crashes, and piling on other peoples CTD posts, than he does actually doing something about his computer/FSX issues and getting it fixed.

Share this post


Link to post
Share on other sites
----------------------------------------------------------------- Since I always make an image back-up of my entire system, it will be a no-sweat to bring everything back onboard within about 30 minutes.Mitch
IMHO, this is a mistake (not making images, but trying to re-use an image which represents a faulty install).Properly uninstall everything, run something like CCleaner, wipe the drive and start fresh. If you don't have a separate drive for FSX, get one. Your image(s) may contain the old bugbears. Other than that, your methodical approach sounds like sanity. Also, resist the urge for any tweaks and try running the sim, tweak-free, for as long as possible. As you point out, focus on flying and see what your joy/stress levels are.

Share this post


Link to post
Share on other sites
"HelloTell microsoft that, at this point they do not seem to agree with you hence they will not support you.Or reactivate you by phone once your installation limit is reached. "Then they should read their own site, it clearly states its compatible with the 32 bit part of Win 7 64. I wouldnt waste my time in any case trying to deal with MS, these and other forums are much better at helping users, and a heck of a lot cheaper.
Hellothat Pic clearly shows that it is compatible with the 32bit version of win7 NOT the 64bit version, which is a different product entirely.Hence the reason that you get both disks included in the box when you buy a retail copy of Win7.I have two disks supplied when I bought Win7, a 32bit install dvd and a 64bit dvd, it is the 32bit version that MS states is compatable.

Share this post


Link to post
Share on other sites
At this point I think "Squishy" gets more satisfaction in complaining about FSX, posting about FSX dll crashes, and piling on other peoples CTD posts, than he does actually doing something about his computer/FSX issues and getting it fixed.
Once again the FSX issues cannot be fixed, i tried over and over.Must say it's much better than before. I only get 1 CTD per 5 flights now

Share this post


Link to post
Share on other sites
Once again the FSX issues cannot be fixed, i tried over and over.Must say it's much better than before. I only get 1 CTD per 5 flights now
HelloTry running it under XP64 , I have zero issues here with both FS9 and FSX under XP64 bit.Never had a problem since going to XP64, under W764 I could not even switch between the desktop and full screen more than once without it locking up.Dropping back to the desktop to launch Radar Contact or PFE was a total crap shoot.

Share this post


Link to post
Share on other sites
Guest nzch2010
HelloTry running it under XP64 , I have zero issues here with both FS9 and FSX under XP64 bit.Never had a problem since going to XP64, under W764 I could not even switch between the desktop and full screen more than once without it locking up.Dropping back to the desktop to launch Radar Contact or PFE was a total crap shoot.
You are getting lock ups because you have not done any research. There is lots of information on how to cure the lock ups when switching from full screen to windows. Maybe you should give "Bus Simulator" a whirl, because even after explaing how FSX works in W7 64 you still are not able to comprehend. I have been invoplved in the FS community long enough to recognise someone who has trouble absorbing technical information, Let me know how you get on with your Bus.Rolling%20Eyes.gif

Share this post


Link to post
Share on other sites