the same ones who guess at things, make recommendations about hardware and make far fetched statements with no background knowledge and find it ok to offer advice about things which you do not possess working knowlege about

You're the one guessing things. Or do you have a SB to bench? do you even own a Nehalem to compare them both? sorry but at this point I'm not sure I believe anything you said in the past at all. You keep boasting about your awesome knowledge and working background...

things which you do not possess working knowlege about

what makes you think that just because we don't mention our jobs in every single single post then it must be that we're all pizza boys or something? I'm a software analist/developer myself, I justr don't need to remind you all the time to prove a point, actually it's completely irrelevant

The points made in that reply were and are simply true and accurate based on fact and daily experience as a dev and a professional with access to almost unlimited resourses regarding FS/software and hardware.Instead of arguing with you which I said I wouldn’t do the post was backed up from outside sources from all over..But instead of acknowledging anything or thanking me for providing you with good info you choose to now to inaccurately say I was negative –Way to man up!

You're the one who's wrong about the tripple channel looking at my testsYou're the one who's wrong about the uncore looking at my testsYou're the one who's wrong about the qpi speed looking at my tests You're the one who's wrong about the limited overclockability of the BCLK in SB being a problem with OC sacalability looking at my tests You're the one who's wrong about the SB not better clock for clock looking at my tests...Where are your TOP SECRET tests done thanks to unlimited access to such great resources? You have none to back up your statements do you? You can't simply say that the memory subsystem blah blah... and then say that SB with it's MUCH improved memory controller will only see a benefit clock for clock in apps that are compiled to use AVX instructions. You make no sense at all and all you do when you run out of arguments is remind us how knowledgeable you are and how we lack background when you don't know anything about us

I have asked the mods to del my account as I'll have no part in this.

freebird has flown the coop."one cockoo flew over the rest" (just wait... i think i have got that book title wrong. something like that anyway. it's been a while).great thread folks -- despite the casualties. i for one am interested, and appreciative of the cut, thrust and parry.

What vcore and settings did it take to get there?

1.37V but was not tested for stability, just wanted to see how this chip scaled with overclock

1.37V but was not tested for stability, just wanted to see how this chip scaled with overclock

Dario,what are you seeing for temps?I have seen max for a short touch, 59c but pretty much [email protected] 1.33v OCCT 1-hour.

Hi David,I envy you! It is so much fun building computers that I am ready to do another one again, or this one over again!

Looks like Intel has given all of us the oportunity to do it over again. :Nail Biting: Stephen, you don't work at Intel by chance do you? :Shame On You:

Haha, I'm actually looking forward to it myself. Maybe my new board will be a little more capable of memory overclocking. Hopefully Intel and the mobo manufacturers take this opportunity to make any other tweaks or changes that became apparent only after a month of the hardware being in customers hands.

Looks like Intel has given all of us the oportunity to do it over again. :Nail Biting: Stephen, you don't work at Intel by chance do you? :Shame On You:

Under the circumstances I am very glad I don't work for Intel. One of my G.Skill Pheonix Pro 120g SSDs with all of FSX installed on it just packed it in. Can't get it to be seen in BIOS or Windows no matter what I do with cables, power or ports. It is only 4 months old so I will RMA it back to G.Skill. Perhaps I will reload FSX onto my empty WD 640 Black Caviar (64 cache) mechanical drive and run the simulator from that until the SSD is repaired or replaced. It seems to me that if I call it "D" and run only FSX on it, but when the SSD gets back I change the name to say "K" and then hook up the SSD and call it D, everything should be able to copy back over to the SSD without having to reinstall the software. What do you think? The idea of reloading everything twice or not flying for however long it takes for G.Skill to fully respond and return a working drive is not a pleasant one.By the way the failure of the drive probably has nothing to do with the 3g P67 problem, as it was connected through one of the Intel 6g/s ports. I tested it in other ports to no avail however the other drives worked in the same ports that the SSD wouldn't. The remaining identical SSD has the operating system on it, and so far, seems fine. I think that it is coincidental that these things happen when there is already the well known P67 motherboard issue. It's a bit disconcerting that when I wrote the G.Skill RMA department the autoreply system responded back that they had been given time off for the Chinese New Year. In addition, they say nothing on their website whatsoever that might indicate how long it might take for an RMA to be fully processed. Next thing I suppose will be ASUS wanting my motherboard back before they send me a new one. Hope nothing else breaks, fingers crossed!Perhaps I won't see everything as it should be with FSX until about the time Ivy Bridge is released! :Nail Biting: Well at least its only my flight sim :Cry: and not some other thing more important. However if things come in 3s, and the first is the P67 recall, the second the SSD failure, what will be next? Ahhh hogwash! I'm not superstitious, knock on wood.Kind regards,

... I have asked the mods to del my account as I'll have no part in this.

Thank you.

Sorry to see one more go out from here, remembering NickN, when he quit..I'm a noob, and I ask silly, stupid questions, and I agree with your observations, this place is only for a select few with the right "positive attitude" - nothing wrong with that, but it seems that everybody with a different view is considered bad, very, very bad, unholy maybe?

One can disagree, present the reasons, facts and supporting references while still maintaining common politeness and respect. If one cannot do that then one should not be here. And of course this is just my opinion.

.... It seems to me that if I call it "D" and run only FSX on it, but when the SSD gets back I change the name to say "K" and then hook up the SSD and call it D, everything should be able to copy back over to the SSD without having to reinstall the software. What do you think? The idea of reloading everything twice or not flying for however long it takes for G.Skill to fully respond and return a working drive is not a pleasant one....Perhaps I won't see everything as it should be with FSX until about the time Ivy Bridge is released! Well at least its only my flight sim :Cry: and not some other thing more important. However if things come in 3s, and the first is the P67 recall, the second the SSD failure, what will be next? Ahhh hogwash! I'm not superstitious, knock on wood.Kind regards,

Hi SpritFlyer, I performed the exact sequence which you described and all was fine when I installed my dedicated FSX SSD. However, I found that periodically it is a good thing to "start fresh". What I did the last round was prepare a extremely detailed word doc that describes the entire process of loading win7-64 and FSX plus all addons, tweaks, etc. I did screen captures, specified web sites links, user accounts, passwords, keyboards mappings, EZdok settings, cameras, trackIR settings/profiles, visio drawings to show yoke assignments etc etc. Basically it captures every source, tweak and mod I made to bring my FSX system to life. It takes a long time to do this but it is amazing just how many steps and details there are at the end of the day! Now, a complete fresh install will be much less painful and it will definately be much quicker.I have been following your SB build story. Thanks to you and Dario for sharing the experience. I planned on sitting out the 5xx and SB round since I like "larger" incremental gains but seeing the results you guys are getting is making it a bit more tempting!!! :P

Ok, I have some solid OC results now. I struggled with the W7 SP1 installation, and had to do a fresh W7 install for it to work. I use it just for overclocking purposes but I'll be reinstalling everything from scratch as soon as the SP1 is officially released.Anyway: 4.8GHz 1600 6-8-7-24 1.368V (peak) HT off4.7GHz 1600 6-8-7-24 1.360V (peak) HT onLinpack is a joke without AVX enabled and stresses the CPU a lot more than Prime with AVX installed: Prime only needs 1.344V compared to the 1.368V of Linx + AVXWhat I'm trying to say is that whenever you decide to install W7 SP1, be warned: your Vcore might not be enough if running some app that supports AVX instructions, and if you run Ultra High or Extreme LLC, your Vcore might go much higher than expected

Went from a 980x@4500MHz to the new 2600k@5000MHz with Gigabyte P67A-UD5. The difference (without reinstalling anything) is just great. Much smoother and crispier so far. Have to use new fsx.cfg tweaks as the old one don't work the same way. BP=0 is a must now.Sandy Bridge is great for FSX! Although not the holy grale, but close. :Batting Eyelashes:Kind RegardsPatrick

Went from a 980x@4500MHz to the new 2600k@5000MHz with Gigabyte P67A-UD5. The difference (without reinstalling anything) is just great. Much smoother and crispier so far. Have to use new fsx.cfg tweaks as the old one don't work the same way. BP=0 is a must now.Sandy Bridge is great for FSX! Although not the holy grale, but close. :Batting Eyelashes:Kind RegardsPatrick

Hi Patrick,Can you expand that a bit? I want to confirm that you regard the 2600K as a better FSX engine at 5GHz than a 980X at 4.5GHz? This will be quite a blow for those that have staked a lot on the opposite being true. I only had an i7-930 OCed to 4.3 and saw a significant improvement, but thought perhaps the 980X at maximum overclock would be at least equal if not superior in FSX to the 2600K at 5g.Kind Regards,

Linpack is a joke without AVX enabled and stresses the CPU a lot more than Prime with AVX installed: Prime only needs 1.344V compared to the 1.368V of Linx + AVX

Sorry, what means AVX?

Hi StephenHave some more testing to do, as the tweaks works not the same way as it was the case with my 980x.BUT! One thing is for sure! With the 2600k my flight experience is much smoother than it was with 980x. Although FSX runs at equal FPS now. I have made a standard "benchmark" flight, so I can compare directly. The textures (cockpit, airports, AI, ...) loads much faster then before.As I wrote. I get only a view (1-4) FPS more now, but even in low 20's it feels much smoother with the new 2600k. At the moment I have also "only" 4GB of Mem. (it was 6GB with 980x). I'm also able to use more AI and car traffic now.I only changed the Mainboard and CPU. It makes even more fun to fly within FSX. I have to do an youtube vid. so others can see what I mean.But even SB is not able to run FSX (completely smooth) at max. settings with all the shiny addons out there and at the biggest hot-spots. But hey we getting close to it Patrick

Sorry, what means AVX?

From Wikipedia: Advanced Vector Extensions (AVX) is an extension to the x86 instruction set architecture for microprocessors from Intel and AMD proposed by Intel in March 2008.More: http://en.wikipedia....ctor_ExtensionsYou need Windows 7 SP1 to use AVX.