Sign in to follow this  
Kosta

FSX: A holy grail of no CTDs?

Recommended Posts

Help AVSIM continue to serve you!
Please donate today!

and your point is...RhettAMD 3700+ (@2585 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2gb Corsair XMS 3-3-3-8 (1T), WD 150 gig 10000rpm Raptor, WD 250gig 7200rpm SATA2, Seagate 120gb 5400 rpm external HD, CoolerMaster Praetorian

Share this post


Link to post
Share on other sites

Ehh, nothing really, was just angry, cuz my FS9 likes to CTD sometimes (very rarely, lately even not at all), ruining my flights, and now FSX also... Thought this would be repaired, but apparently it wasn't (or it's not possible to repair).

Share this post


Link to post
Share on other sites

If you are getting CTD's in both FS9 and FSX then that's probably an indicator that something is amiss in your system...and it's most likely not FS9 or FSX.I'd look at hardware issues, driver issues, before blaming FS9 or FSX. And if you don't get CTD's in any other application, keep in mind that FS9 and FSX both run the CPU at 100% usage, and nothing pushes a computer as hard as FS does. I'll test an overclock with SuperPI but also with FS.RhettAMD 3700+ (@2585 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2gb Corsair XMS 3-3-3-8 (1T), WD 150 gig 10000rpm Raptor, WD 250gig 7200rpm SATA2, Seagate 120gb 5400 rpm external HD, CoolerMaster Praetorian

Share this post


Link to post
Share on other sites

Everytime I exit FSX I now get the 'FSX has encountered a problem and needs to close' message. All I have installed is SP1, UTX and LVD767.Everything else, including FS9 runs fine on my PC.As it only happens when I exit the sim, it's not bothering me that much.Glenn

Share this post


Link to post
Share on other sites

Glenn, I get the same message and have no add-ons, just SP1. I wonder how many others are having this issue?. It didn't bother me much either at first, but I now suspect it's why none of my settings changes are being saved across sessions because the sim won't write to the cfg file when it closes (see my post elsewhere in the forum). And I don't like living with that scenerio at all......... Regards, KendallDell 8400 3.2 GHZ H.T.3GB 533 DDR2X800XT 256MB/Catalyst driver - 7.1's6x AA/16x HQ A/FDiamond Xtreme/Logitech X-530'sDual Monitor: Dell 2405/1905CH Yoke/Pedals - Saitek Throttle

Share this post


Link to post
Share on other sites

Mace, I am completely sure it is *not* my system. What could eventually be, is hardware that doesn't play well along, although also my components are pretty good, and not the cheapest. Everything driver-wise updated and working well.No other games are crashing. And I have tested my setup with many many tools, from SuperPI, Orthos, MemTest, Prime95 and others.Also not the heat.So, it must be programming in the FS9/X.

Share this post


Link to post
Share on other sites

I believe the evidence is most likely these ctds are caused by your equipment/system.My logic: Your system components are so standard that if ctds were the result of a system like yours interacting with a software bug, that bug would have been a constant issue in the community, in fact that bug would not have made it past the beta process.Further, the one part of your system that is quite NON-standard is the watercooling, which suggests extreme overclocking. I suspect you have found the instability of your overclock that cannot be detected by superpi, othros, memtest, and prime95.My fsx is stable as a rock, no ctds. my system:core2duo e6600 with a mild overclock to 3ghz cooled by arctic7 hs/fan.intel 975bxb 4gb crucial ram (4x1gb in dual config)radeon x1900xt vidIf the ctds were inherent in the fsx, how could you explain why fsx works so well on my system?Best,Bob

Share this post


Link to post
Share on other sites

I've never had FSX crash, and I use it almost everyday since it came out. It has to do with the hardware / overclocking.

Share this post


Link to post
Share on other sites

I have been having computer crash restart problems for weeks now, about 10 minutes into the flight, but only in full screen mode - Windows mode is okay. I have tested exhaustively, done many updates but I am rapidly coming to the conclusion it is inadequate power supply. I have a 600 watt unit which delivers 18A on each of the two 12v rails. My Sapphire X1950XT 512mb calls for 30A on the 12v rail!! I notice several high end ATI cards in this string, so check the power requirements on your box.There are lots of similar problems being discussed at the Sapphire forum at: http://www.sapphiretech.com/en/forums/forumdisplay.php?f=4I have one more test to do and that is to re-install FSX, and if that does not cure the problem, I will be trying another power supply.NigelVancouverMy System:Intel Core2 Duo E6400Gigabyte GA 965G DS3 mobo Sapphire ATI Radeon X1950XT video card PCI-e 512MB2GB Transcend 800Mhz DDR2 RAMMaxtor 80GB 7200rpm hard driveMaxtor 200GB 7200rpm hard driveWestern Digital 250GB 7200rpm hard driveCreative Sound Blaster Live! with latest driversNEC FE950+ crt monitorCHProducts USB yoke and pedalsWindows XP Home edition with SP2DirectX 9.0©Cooler Master 600W power supply Five case fans

Share this post


Link to post
Share on other sites

>Well, you just haven't encountered it yet! :DI guess I haven't encountered it yet either, nor have most people, based on the lack of reporting of CTD's in this forum in the 10 months of FSX history we have accrued so far.The only time I have had a CTD with FSX was when I was massively overclocking.It has been the paragon of stability when I keep things reasonable with the overclocking.I still maintain that the cause could be any number of things, including corrupted driver, gummed-up OS, hardware problem, etc. If CTD's were a pervasive thing in FSX, there would 100's of posts here about it.The true test for you would be to wipe everything, reinstall OS + all updates + vid driver, then FSX clean. And see if you get CTD's then. If you got CTD's then, you would know that the problem was hardware, a combination of hardware.RhettAMD 3700+ (@2585 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2gb Corsair XMS 3-3-3-8 (1T), WD 150 gig 10000rpm Raptor, WD 250gig 7200rpm SATA2, Seagate 120gb 5400 rpm external HD, CoolerMaster Praetorian

Share this post


Link to post
Share on other sites

That would mean, running without OC for 6 months from now on and not getting CTD. Just for the sake of the test? Nah...sorry.

Share this post


Link to post
Share on other sites

Bogus to assert that fsx has a bug, when you're running a significant o/c and not willing to consider evaluating the impact of that o/c on your operation.Sorry Word Not Allowed, this thread is rendered meaningless given that response.

Share this post


Link to post
Share on other sites

After all the testing, and ALSO testing if O/C has an impact on FS9 CTDs, and that I did test for a long long time on the previous computer, which had completely different components, IMO, it's not a bogus assumption. And yes, without the OC on the previous setup, it had same unknown CTDs, though I must say, some where scenery-caused, which I found out the reason for. Others very rare, and without apparent reason. No any other game crashed like that. Ever. I never had unexplained restarts of the whole computer.In my opinion, it's something else. I'm not a programmer, but why can't they make the application more tolerant to some errors?

Share this post


Link to post
Share on other sites

I also had the problem of CTD's, for many weeks. Was also blaming the software but in the end it turned out to be the X45 joystick. Replaced it with the X52 and no more CTD's.

Share this post


Link to post
Share on other sites

I have the same addons as Glenn, the exact same and have never seen a CTD in FSX, so I'm thinking it may be something with your computer such as background applications. I'm not going to tell you to turn your antivirus off, but I do, infact I use smartclose. Also, I can't hardly use FS9 anymore without getting a CTD with or without an "error has occured" message, and it seems to only happen after I've set up FS pushbacked and started engine, or when I'm a few miles out on approach, very annoying.Jeff

Share this post


Link to post
Share on other sites

I reinstalled my FS9, with all its glory and addons, and since then it seems to be running A-OK. Since then I haven't seen one CTD in FS9. And also, I have barely apps running in the background. And I don't even have an antivirus.

Share this post


Link to post
Share on other sites

Hi Bob,I can already see a flaw in your logic.The fact that you do not get ctd's does not necessarily mean that the OP's machine is at fault. Do you fly in the same areas that he does? Do you use the your simulator in the exactly the same manner that he does.How long are your sessions compared to his?All I am saying is that we should not be so quick to blame hardware just because you think your installation is solid. A better way to solve the problem would be to investigate with sequence of actions lead to the CTD and THEN try that sequence on other hardware.To the OP, do the CTD's seem to occur regularly at particular point in the simulation?Kabs

Share this post


Link to post
Share on other sites

Kabs, your approach is logical. I have a problem with avoiding the most obvious likely cause however. Anytime I have a problem, I investigate the obvious first before painstaking one by oneing it. The OP has a massive overclock, imho the most obvious cause of instability, and refused to believe that fsx might be a tougher test on an o/c than prime 95 and memtest.To be unwilling to back off the overclock simply to assess that possibility leaves me shaking my head. I'd say this op is not willing to actively troubleshoot, and simply prefers to have a belief that MS has a bug.Thats not science, and if this is the OPs headspace, I can't really help.Bob

Share this post


Link to post
Share on other sites

Kendall:If it helps, I have the same Dell box, and do not get that message at all. Running a different Videocard (7600GT, most recent drivers). I just installed FSX clean on this system after a defrag, and then immediately put on SP1. Have not tweaked any graphics/AA settings yet, just running at FSX's suggestions.

Share this post


Link to post
Share on other sites

This CTD I had was a irregular one. For this one, and this was the only one in FSX, I didn't remember where it was, because it was insignificant.I know though in FS9, that in the past 4 years, I did find many scenery caused CTDs (which were mostly solvable), and yet again, there were weird ones, which I was completely unable to find (and usually happening irregularly and also sometimes on one place). I found out that a whole reinstall of the sim usually made the whole situation better, and then again, after a year or so, gets bad. Possibly through some installs...I will just make a simple compare: you know what happened to Win98 after you installed many application, uninstalled, etc? I think it's pretty similar with FS9/X.And I also do know how to keep an installation clean. But as I said before, something else is here wrong, cuz if I were the only one having CTDs, I wouldn't be here speaking about this.Bob:"To be unwilling to back off the overclock simply to assess that possibility" - been there, done that.I never refused to turn down the clock. In fact, I was running FSX clean on the non-OCed machine, and everything was OK. As it was for a long time now. As I said, this was one and only crash.As I just said, FSX was running happily until it seems that I installed couple of addons. I have FSG, ASX/G, FSForce, and couple of sceneries.Now, what it seems I forgot to say is, that FSX never crashed with FSG only.So now only remains to observe if this was a very rare one time thing, or is it like FS9, more you put in it, more often it crashes.Time will tell.But it also leaves me shaking my head, when you say that overclocking is the most obvious reason. Why would you make such a statement? Running hardware at higher speed if it can handle it, is a normal thing. And it runs stable.If we make a compare of crashes I had with non-OCed and OCed PC, I would have to say they are 1:1. Nothing changed, in any of my games. Those that were crashing, were still crashing afterwards, and the stable ones didn't.I refuse to believe that FSX is higher CPU test than all other programs running and testing hours and hours. Or should I just go against and say, prove it that it's higher CPU test. There is basically no way to check, whether both you are me are right.

Share this post


Link to post
Share on other sites

I don't really understand this thread. If you had one and only one ctd with fsx, and it never happened until you added some addons, how can you suggest fsx has a bug that must be fixed?Had I known that you really don't have a problem, I wouldn't have tried to think thru potential fixes.Of course your o/c is not the cause, because there is no problem.B

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