I don't see how stating "no double posts here" is going to add to this topic. Secondly, the OP clearly stated "GIGABYTE BOARD".

And also, double posts DO NOT happen on every motherboard, but on ALL manufacturers. But not every board.

Well just as long as its not something to worry about. It doesn't really bother me, just a bit concerned.

Lower your overclock for three or four days and see if it happen again.....OC probably not stable (even if it does seems to be after testing)...Lower your overclock for three or four days and see if it happen again.....OC probably not stable (even if it does seems to be after testing)... Dam!! double post......

Its still occasional, not happening ever time.

Its still occasional, not happening ever time.

It still happen after lowering your OC? It does not mean it will happen everytime with high OC.....like I said try lowering your OC and see....if it does not happen after lowering your OC you know where the problem is......if it does still happen with a lower OC test your memory..

Lower your overclock for three or four days and see if it happen again.....OC probably not stable (even if it does seems to be after testing)... Lower your overclock for three or four days and see if it happen again.....OC probably not stable (even if it does seems to be after testing)... Dam!! double post......

I see what you did there lol One thing I noticed was when I first got my computer built before I had even overclocked I had changed the memory to 1600 as its rated at that and I got a double boot then I changed it back to 1333 and no double boot occurred. But I am not sure if its a memory issue completely.

Well I lowered the OC and did one boot and it booted fine. Thats is not conclusive for me though cos I was getting fine boots at 4.7GHz as well. So I will run it at 3.3GHz for a while and see what. If it is fine I might ask for some overclocking help. But I was running at 4.7GHz prior to my BIOS update which I had to re enter the settings. So maybe I missed something.

I remember reading in the gigabyte forums that the double boot is normal for an overclocked system. First boot scans the bios for setting issues, second boot is normal if no issues found. Apparently its a feature to stop corruption of the the operating system during a failed boot. Now to find that post.

I remember reading in the gigabyte forums that the double boot is normal for an overclocked system. First boot scans the bios for setting issues, second boot is normal if no issues found. Apparently its a feature to stop corruption of the the operating system during a failed boot. Now to find that post.

How come it doesn't do it all the time then? Is than an Intel feature because it happens on my Asus board as well.

No Clue, I was trying to find answers myself. Still doesnt make sense to me either

Here is something interesting, I just went onto CPU-Z cos I have loaded the fail-safe defaults which should put the multiplier at 33x, right? It has it at 34x in windows but the multiplier in the Touch BIOS (no, i dont use it for OCing, just monitoring) is still at 33x.

I had double booting before and in my case it was always releated to my overclocking, I had to add a little more voltage on the memory and that took care of it. That's why I asked for Andrew to lower is overclock and try it for awile just to see if it will happen again, if it does not happen again you know where to start looking. Stress testing is a good indication of the stability of a rig BUT as you all know you can be stress test stable and crash in FSX, to run FSX stable you may need to raise your core voltage just a tad over your stable voltage after stress testing, the same apply to memory, mine is rated at 1.68v but because of my high overclock and the tight timing I have to run them at 1.74v, anything below that and FSX crash on me, triple chanel memory (on paper) can go up to 1.8v but you won't see that in intel spec. sheet.

I don't think anyone else in this thread other than yourself is talking about the first generation i7 processors, we are all talking about the 2*00k range and it's chipset. My ASUS i7 9*0 series first gen Maximus Extreme board was rock solid, the same cannot be said even for the Z68 chipset. Running 1.65 volt triple channel memory in an i7 2*00k range processor @ 1.75 volts will kill the CPU pretty quickly, they should be using dual channel memory at 1.5 volts.

I don't think anyone else in this thread other than yourself is talking about the first generation i7 processors, we are all talking about the 2*00k range and it's chipset. My ASUS i7 9*0 series first gen Maximus Extreme board was rock solid, the same cannot be said even for the Z68 chipset. Running 1.65 volt triple channel memory in an i7 2*00k range processor @ 1.75 volts will kill the CPU pretty quickly, they should be using dual channel memory at 1.5 volts.

You misunderstood my post, my system and voltage as nothing to do with the 2600K (do not use my numbers on your rig.) what I'm saying is that no matter what system you have it is possible that you will have to raise the voltage a little on the mem. or the CPU because of FSX or double booting, I'm talking about my own experience with double booting, raising the voltage on my memory one notch took care of it so if your memory run at 1.5v and you have a high overclock you may need to raise the voltage one notch not to get double boot AFTER you know you do not get double boot at lower OC. Testing your rig at lower OC is just to make sure you won't get double boot, if you still get double boot after that you know your problem has nothing to do with your OC, you need to start looking somewhere else before one can say that the problem is caused by the mobo, the mobo may be A OK, only after eliminating all other options can you look at the mobo for the source of the problem. Futher more, a stable OC (high one) may not be stable anymore after 6 month + because of degradation and you may need to add more voltage to it just to keep it at the same GHz as when you started.