To give an update on this ... we've just found a third person having stability issues in the PNW area, approaching KSEA with his Carenado planes, nearly the same coordinates all the time. Go to the FTX thread for details if you like.Update again: Forth person found.

Could end up being a nVidia driver issue as I've been getting a c02 blue screen since 258.69.jja

Well, I would divide bluescreens from a crash to desktop (CTD) and I think we have some guys around with ATI cards so Nvidia is out of the front line here.Also it would surprise me if a driver causes crashes on some scenery files (remember: disabling one PNW folder and the CTDs are gone).I myself tried some driver versions, no betas of course, just in case ... no change in behavior.

ATI5870 here, 10.5 drivers, Win7-64, PNW all OrbX PNW airports, REX, ASE, GEX, UTX_USA, ASUS P6T, Intel i7-950 o/c at 4.2: Maddog, A2A Cub, Spit, Jug, Me109, SibWings BirdDog, MyTrafficX v5.3 - no crashing issues any type of aircraft or weather. Sorry... :(

Why sorry? For not crashing? That's allowed :( In fact: I hopefully pointed out that the issue is NOT a general one and we are now just 4 guys with very different systems that get PNW to crash around Seattle.I see in your aircraft list that only A2A Piper is one of the reported "bad" ones. I don't own it myself so I can't speak for its complexity.If you look at the other aircraft mentioned, you'll see that there are quite a few. Exceptions are also known as for example my nice Realair Duke doesn't crash.Strange issue, this thing, I know.

I've done a fresh install of Vashon Island and the library objects and added the alert lines to my fsx.cfg.Here's what I gotI have no idea how to interpret this stuff and of course posted it too in the FTX forums (http://orbxsystems.com/forums/index.php?topic=23872.0).These alerts caused no CTD so far ... it came later at NOLLA NDB, without alerting for something missing there. So those pictures are just taken on my way to my most liked CTD point, approaching KSEA from the NW.

The error message(s) indicate you are missing scenery components FSX is trying to call up and display on your system. This indicates to me that your scenery is not properly installed (it could be PNW, it could be something else). Not all components were installed on your system when you ran an installation program. If you had UAC enabled when you installed FTX PNW, this could have caused the bad installation as sometimes it tries to save you from bad and evil people and won't install something considered suspicious. An aggressive anti-virus program could have caused it too but the latest anti-virus programs usually do a great job handling installations. I would disable UAC and uninstall FTX PNW, then check your folders and make sure all folders belong to Orbx have been deleted. Then check the scenery.cfg and make sure all entries have been removed and the scenery.cfg is not corrupted (i.e., areas/layers are in numerical sequence). Restart FSX. Close it after restart then reinstall FTX PNW. The other 3-4 people may have UAC enabled too and have bad installs (thus the reason this is not happening to everyone). UAC is enabled by default. If this does not fix your problem you may have to reinsert your FSX disk and select repair (with UAC disabled) then do the same for SP1 and SP2 and/or Acceleration. Scenery objects not belonging to the PNW product and belonging to the default FSX scenery could also be missing. Hope this helps.Best regards,Jim

Well, I would divide bluescreens from a crash to desktop (CTD) and I think we have some guys around with ATI cards so Nvidia is out of the front line here.Also it would surprise me if a driver causes crashes on some scenery files (remember: disabling one PNW folder and the CTDs are gone).I myself tried some driver versions, no betas of course, just in case ... no change in behavior.

I only mention it because I only fly around Seattle these days with PNW and Darrington with 2048 textures. I think that I have the fan monitoring driver issue that causes jerky behavior on 285s. The BluSecreen is just thrown in for good measure but may be related.I'll probably end up sucking all the dust out of my machine as it has been really worm lately.jja

Not had the problem here, with an i7 and a 285, though certainly I find Seattle to be fps-unfriendly.Have you tried it at default clock speeds? Just wondering if the extra overhead at SeaTac is pushing an overheated chip a little too far. Certainly, trying it at default speeds should be a good guide to exclude the problem - though I suspect from your posts that you've had the nous to try that already.

Hello I have had this problem after Vashion install always flying morning hours into Vashion from darrington. I found that Vashion was updated just installed on top of current and problem ws gone. Hope this helps Steve

Hello I have had this problem after Vashion install always flying morning hours into Vashion from darrington. I found that Vashion was updated just installed on top of current and problem ws gone. Hope this helps Steve

I get the crash flying the Carenado F33 in Darrington. For some reason Concrete is fine as are some other areas.

I'm sort of glad I read these comments since I am having problems with my PNW. Whenever I start anywhere other than in the Orbx PNW area FSX loads without problems.I'll look for other threads specific to not being able to finish loading FSX, but for now Loading terrain data never gets past 17 percent. I now have 4GB of memory.Keith

. that's a very good find as repeatable cases of errors in fsx seem very rare what with how finicky it is.. (short flight, and seems repeatable!)this crash is very similar to a test case crash i found in australia with the orbx stuff.i found that with the md-11 i could easily recreate the crash 100%, but by reducing 2 settings could eliminate it.i tried your test case with ycvr->ksea and it also crashed with my control test settings but flew fine with the same changes i used... so maybe that's a good sign!?if you'd like to try it, in my case the culprit seemed to be a combination of autogen and texture max load.the only config i found was to reduce autogen to 'normal' setting and texture max load to 2048 or less. this included reinstalling rex textures at 2048 although i don't know if thats entirely necessary.for some crazy reason that eliminates every crash test case i have with the 'heavy' planes like md-11. generally i can fly with autogen set higher (i usually use 'dense') when i am doing vfr flights in smaller planes that don't have fancy systems etc. cheers,-andy crosby

Thanks again for the replies, guys.Lets see if I can answer some post or reply to tips ...As far as the installation of PNW goes. UAC was the first thing to go completely off when I installed the system - might be my type of philosophy from "it's the user that clicks, not the admin rights that harm", however, PNW was installed again, got its 1.2 patch, I've controlled the scenery library entries and the amount of files in each folder so far. Especially in erroneous one, which is "FTX_NA_PNW05_SCENERY".As for the alarms of missing stuff: I've had them turned on for some flights now (not only at PNW) and to me they seem some kind of normal. I've had them here and there, but never experienced problems or even a CTD - even at PNW they don't trigger the CTD, because they come up way before the bad location and if I don't continue to this location, there's no CTD at all.Of course, they show that something is missing but as long as I can't understand what exactly this missing part is, I'll be far away from going to reinstall, repair or other huge projects with the target to only hope that everything will be fine thereafter.Don't get me wrong, this tip was and is much appreciated and I agree that especially UAC is a source of trouble with installing software but I'm not a fan of the (in a way) blind reinstallation without knowing what went wrong in the first time. But as I said, PNW was already reinstalled.Default clock speeds: That's a good one. Although it would be strange, that only KSEA triggers errors (there are some other dense areas in FSX too), I've tried them - no success. Strange that only some complex birds seem to trigger problems there and other complex ones do not.I must admit that success here would have surprised me as I can't recall overclocking errors to be that precise. Sure, they occur in the same kind of circumstances but to be exactly at NOLLA NDB all the time and to don't occur when going to all the other spots around is unusual to my understanding.The Vashon update: Already done, version 1.1 and the new library objects too. No success so far :(Crashing at Darrington: Maybe you want to join us at the FTX thread, Geofa?Settings controlled/lowered: I'll go for this. I'm not using the max load values above 1024 as they've made no big improvement for me and only raised systems workload. Autogen is set to "dense" at PNW (running i7 at 4GHz) because the big birds demanded some power together with areas like KSEA and "dense" looked like a good value for speed and optics. So I'll go for "normal" next time and report back. I think I've tried this before but I'm not completely sure.Although I think that "dense" should (and from experience IS) suitable for a 4GHz i7, I'll go one step lower.We have a guy in the FTX thread that reports CTD problems at the AU-airports from OrbX too when approaching with the MD11 - I'll pass this one on I think.Finally I'd like to thank you guys and although some answer might seem as if I didn't like your tips, they were and are all appreciated :)

Well, what should I say, shame on me ...I tried a flight with this really low autogen setting (rest unchanged), which means "normal" and surely does not suit my CPU (i7 @ 4GHz) in case of FSX performance around PNW, but ... it was stable on my first and short flight.Even passing NOLLA NDB (my "favorite" CTD point) went fine with nice Concorde X.I will surely try some more of my mentioned complex planes on this rather (too) low autogen setting, but if it gives me stability to pass through PNW completely with every aircraft I own, I'd go for it.I don't know if you can call this a pure solution, because my thinking (and experience) is that running to high settings will give you poor frames but not CTDs eventually.Thanks for all tips so far and again: shame on me for not testing this setting as it seemed "to low to fit". Apologies therefore, gentlemen.As I've only tested this for one flight now, I'll stay away from saying that this issue is solved, but I'll copy this tip over to the other FTX guys and listen what they can tell about the CTDs then.

Maybe last update ...Second flight now with autogen to only "normal" - no CTDs. Strange "low" setting to use on that beautiful scenery but I must admit that it brought stability back when flying to KSEA (other areas weren't a problem so far, even on high settings).Thanks to all who helped, quite a few people :(