I heard this was bad but who knows. I just got done reinstalling my OS and FSX and did it at default BIOS settings along with all the "major" FSX addons, the base infrastructure if you will. I am now back up to my stable 4.6Ghz and was wondering with little stuff like airports and things like with an auto installer that if it is ok to install with the OC going.

 

Thanks

Yes, it's fine.

 

Personally I overclock first, and get the darn thing stable - you know, do the IntelBurnTest - Prime95 thing, and some normal usage first, and then, when I know she's solid - then I install the sim. The last thing I need is to install the whole sim, add the addons, tweak, setup Inspector, and then get one (or more) bluescreens as I'm overclocking.

 

4.6 is good at 1.385.

Thanks, Yea 1.375 was stale for tons of IBT and after about 100 hours of FSX I got a bluescreen. So 1.385 had been good so far. FSX is a better stability tes than anything out there. More fun than sitting there watching IBT or Prime 95 as well.

Yeah, for sure!

 

Don't be worried about the vCore: it'll take 1.4 for months on end. I'm still sitting at 1.385 and running 4.9 gig. Here's my 4.6 & 4.8 if you want someone else's for a samples.

 

https://dl.dropbox.com/u/52676345/4.6%20settings.pdf

https://dl.dropbox.com/u/52676345/4.8%20settings.pdf

Denver, i've always been using the though by NickN that on a new system build or new OS install that its best to install FSX and or any addons that you may already own, on the stock clock settings to be on the safe side, then proceed with the overclock.

 

This isnt to say that you could overclock first then install FSX, but doing so on stock settings takes away any possibility of installling the base FSX progran that isnt completely stable.

 

Having said that, I can understand due to the fact that when I did my first oc, then tested FSX at one stage, even though I had passed the normal oc tests, FSX encountered some errors and would load correctly and also displayed some .dll errors.

 

Of course, if you install FSX and some addons first, then OC and its stable for long time, there shouldnt be any reason to underclock before installing any new addons after you are certain to have a stable oc.

 

I always leave nothing to chance when it comes to a new setup and installing FSX on a bone stock CPU clock, then overclocking seems to be the safest way to go and would leave some degree of install errors out of the equation.

 

Although as you have probably read in these forums, pretty much any idea is up for debate with any number of people arguing that one way is better than the other, so it just leaves you up to decide with opinion seems to make the most sense form a logical stand point. If you think about it logically, installing FXX on a non oc'ed system can eliminate more possibilities of error rather than the possibilities of doing it on an oc'ed system that could have hidden stability problems and could mess up your base installing that could cause problems further down the line. Also consider the fact that doing it either way will still end up in the same amount of work, just in a different order.

Sorry, Jim, but FSX will run perfectly fine on a stock system. Why wouldn't it? It's only when it's stressed that it has problems, and the problems FSX has are largely due to an fsx.cfg parameter which is missing - like HIGHMEMFIX=1, or wrongly set up - like BufferPools=0, or it's a Win7-64-bit, and FSX freezes after 20 minutes, in which case we put UIAutomationCore.dll, version 6.0.5840.16386 in the root of FSX. Freezing gone.

There are not too many other errors that are of any significance. Most here on the forum are the above, or overly aggressive Inspector settings, and or other FSX settings within the sim. When you set FSX up on a stock pc - you have to tweak your guts out to get anywhere close to a decent experience. The new post-i7 960, i.e. 2nd gen, the Sandy Bridge K series - will OC so easily on stock cooling it's a no-brainer. Why spend a ton of time tweaking when we know for absolute certainty - that the way to happiness is core speed. Likewise - if you've spend three weeks setting FSX up on the new PC, and it's running fine, but stuttering or blurring, or slow loading (what else is new?) and then you overclock - and she bluescreens..... guess what just happened inside that harddrive?Now you have corruption. Don't you? Try fixing that one.

These are not Pentium 3's, 4,s or Core2Duo's - the 2nd-gen i7's are a new breed of darned fine processors that cry out to be safely overclocked. Do it first, get it out of the way. Then load up FSX, OrbX, REX, FlyTampa, FSDT KORD, etc..

Everyone has an opinion, but just because someone says "I've always done it this way", or "xxx says to do it this way" - doesn't mean they're always right. Times and circumstances change the way things are done. Some folks have lots of training, but most here are hobby-ists. And some folks are just plain wrong...... but sometimes they're right...

Anyway - enough of that - For me - BSoD's should be got rid of before you install FSX. Do it once. I don't like reinstalling FSX or - even worse - the operating system.

 

Cheers

Well, there you go Denver, two different people with two different ideas. Is one more right than the other, not really, just two different ways of doing the same thing.

 

Btw Paul, is the talk to the hand thing really necessary, like what I said is wrong. Same goes for the way you started with "Sorry Jim", as if everything I stated was false and your idea is,right, and never did I say that FSX couldnt run on a stock system.

 

FWIW, I have used Michael and he preaches or used to preach when I used him, that you setup up FSX and everything on a stock clock, then procede with the OC and tune from there.

 

Anyway, I was just expressing an idea, so sorry if I feel I stepped on your toes so to speak, but I dont need any condescending "talk to the hand" symbols or sorry remarks.