OMG!! - i've reached 360FSB!

http://valid.x86-secret.com/show_oc?id=120510

Ooh what JOY! :banana: :woot: :toast:

Uisng a DQ6 with the new beta F5d.....i'm in Windows at 360FSB!!!
Haven't Orthos or tested yet...just booting is enoguh for me right now as with all previos bios i could NOT get the FSB past 340MHz without zero POST.

I have the (G)MCH at 0.4V and the FSB at 0.2V...i gave it juice just to see if i could at least boot, i'll start to drop the voltage to see where i am most stable.

Now all i need to do is find where and what settings are nesscary for 400FSB with a 6x mulit.

:D

360 is not so impressive. A DQ6 will run 400+ Without any more chipset voltage.

Show us 500FSB + :woot:

Well, for ME it's impressive...considering all bios i;ve used thus far could not allow over 340FSB.

But since F5d bios.....look:

http://valid.x86-secret.com/show_oc?id=120533

personally richard... id be calling gigabyte and demanding an RMA..
that board you have is a real lemon.
unless ther eis something in the bios your still havent changed or you have crap ram or crap psu

you really have something in your hardware be it th eboard or whatever that is giving you issues.

Quote:

---

Originally Posted by The_Hardstylez

360 is not so impressive. A DQ6 will run 400+ Without any more chipset voltage.

Show us 500FSB + :woot:

---

:D :D :D


regards

400FSB is good, my RAM is G.SKILL HZ 0627 which good upto 1000Mhz, my PSU is on OCZ 700W Gamxtreme and rails have been tested using a multimeter.

Everything in my rig is high end, it's the bios that is holding the board back.
F5c...340FSB max, now F5d i'm at 400FSB.

And i have lowered the (G)MCH and FSB voltage to 0.1V on both...so it is bios related, and i've yet to try past 400FSB, it may go much higher.

Quote:

---

Originally Posted by Lestat

personally richard... id be calling gigabyte and demanding an RMA..

---

Agreed. My cheap P5B that no one liked because of his limited overclock is doing 9x400Mhz without too much problem.

Quote:

---

Originally Posted by Richard Dower

400FSB is good, my RAM is G.SKILL HZ 0627 which good upto 1000Mhz, my PSU is on OCZ 700W Gamxtreme and rails have been tested using a multimeter.

Everything in my rig is high end, it's the bios that is holding the board back.
F5c...340FSB max, now F5d i'm at 400FSB.

And i have lowered the (G)MCH and FSB voltage to 0.1V on both...so it is bios related, and i've yet to try past 400FSB, it may go much higher.

---

show us 9 x 400 and some benching :D

Pish, let's not debate which brand is best...i'm just glad Gigabyte are moving in the right direction.

Quote:

---

Originally Posted by Richard Dower

400FSB is good, my RAM is G.SKILL HZ 0627 which good upto 1000Mhz, my PSU is on OCZ 700W Gamxtreme and rails have been tested using a multimeter.

Everything in my rig is high end, it's the bios that is holding the board back.
F5c...340FSB max, now F5d i'm at 400FSB.

And i have lowered the (G)MCH and FSB voltage to 0.1V on both...so it is bios related, and i've yet to try past 400FSB, it may go much higher.

---

have you set the memory divisor anything else than AUTO???


with gigabyte Ds3 if you let memry divisor in AUTO you cant overclok more than +- 360 FSB, you have to set divisor 2.0 or other but no AUTO


regards

I don't think my CPU will go 3.6Ghz...without serious voltage, i will try 400x8 and see what voltage is nesscary.

I'm not gonna run 1.55V through a CPU no matter what, at €400 it cost to purchase it's not worth it for the MHz increase.

Devider is 2:2 in bios.

Quote:

---

Originally Posted by Richard Dower

I don't think my CPU will go 3.6Ghz...without serious voltage, i will try 400x8 and see what voltage is nesscary.

I'm not gonna run 1.55V through a CPU no matter what, at €400 it cost to purchase it's not worth it for the MHz increase.

---

cooling?

I think you don't need more than 1.5v for a screen

Ultra-90 using AS5 + two 92mm Evercool PWM fans in push/pull.

415FSB

http://valid.x86-secret.com/show_oc?id=120552

1.4000Vcore...no stability testing though.

G.SKILL HZ 0627??
2GBHZ is it?? what does that 0627 mean?? r u talking about the batch for ur CPU?? the L627??

Yes 2GB kit, HZ..0627 refers to 2006 week 27, which means the memory is using Micron D9's which are great overclockers. People have been getting between 1000-1100Mhz from 2.2-2.4V.

my 0652 are hitting 1000 fsb no problem, i think all of them are d9gmh... week doesnt matter

Quote:

---

Originally Posted by Richard Dower

415FSB

http://valid.x86-secret.com/show_oc?id=120552

1.4000Vcore...no stability testing though.

---

1.40v for 3Ghz ??? cant you run 3Ghz@vcore default???



BTW: my 2x1GB Teamgroup PC5300 CL3-4-4-8 are also 0627 :D


regards

Quote:

---

Originally Posted by mascaras

1.40v for 3Ghz ??? cant you run 3Ghz@vcore default???



BTW: my 2x1GB Teamgroup PC5300 CL3-4-4-8 are also 0627 :D


regards

---

3Ghz default Vcore...you joking???

Anyways here is where i'm at right now:

http://valid.x86-secret.com/show_oc?id=120597

Congrats Richard! Hmmm, maybe I should try that BIOS and hit 8x400...or more. :D

I'm using 1.344 vCore (as set in the BIOS - 1.36V as reported by EasyTune 5 and 1.318V as reported by CPU-Z) on my DQ6 to get 8x375 FSB = 3 Ghz right now on my E6400. Dual Prime stable 16 hours I think.

Richard - Ive had exactly the same situation as you except Ive been running on a DS4.
Up until this BIOS I had tried EVERYTHING to get it above 340FSB and nothing.
New BIOS and im now Orthos testing at 410 (400x7 passed 1/2 an hr easy).
No voltage adjustments at all other than RAM up .3!
I HIGHLY recommend this BIOS (F5C) to anyone that is OCing their DS4 with an E6600 (same probably applies to E6700).

I booted at 420FSB...but no stability testing conducted.

Richard, see if you can run dual-Prime (or Orthos) stable for 12 hours.

Quote:

---

Originally Posted by LordShadow

Richard - Ive had exactly the same situation as you except Ive been running on a DS4.
Up until this BIOS I had tried EVERYTHING to get it above 340FSB and nothing.
New BIOS and im now Orthos testing at 410 (400x7 passed 1/2 an hr easy).
No voltage adjustments at all other than RAM up .3!
I HIGHLY recommend this BIOS (F5C) to anyone that is OCing their DS4 with an E6600 (same probably applies to E6700).

---

including the DS3, DS4 and DQ6. All are now able to get above 400Mhz with the E6600 and E6700! Tomorrow you will be seeing 3.4Ghz from me (or 430x8 RAM will be roughly 860Mhz), and then I'll go for the big 400x9 (ram at 1000Mhz). And there I shall stay! :D
I'll start orthos at current settings of 410x8 (3.28Ghz) 1.4V (I just added volts because my cpu doesn't seem to care how many volts I put through it... temps are never more than 63oC on coretemp except when I put above 1.6v - I won't do that again lol)

I Orthos dual primed for 3 hours 20 mins with the 414FSB settings.

Now booted into Windows at 430FSB, default (G)MCH+FSB:

http://valid.x86-secret.com/show_oc?id=120647

Link to new bios Please.......

And why aren't you running a higher speed?

Say 400X9 3.6ghz? See how much voltage that needs. Less than 1.5 and you have a good mobo / chip. 1.55V or more and you have nothing special!

445FSB!!!

http://valid.x86-secret.com/show_oc?id=120653

Default volts again on thr GMCH + FSB...the X-FI issue is back, Windows dosen't detect the PCI soundcard.

lol@ you Richard, I'm currently at 416 x 8... http://valid.x86-secret.com/show_oc?id=120655
er... why does my RAM show as PC5300 :S... ah well :D

I doubt my CPU can reach 3.2-3.6GHz without huge voltage, even then it might not.

Click on the "about" tab on CPU-Z....you'll see "Validation", new tab opens, click on save validation file. Tehn click on the validation ID's page web link.

It appears to crap ot at 450FSB, no boot even with 0.3V on the (G)MCH and 0.2V on the FSB.

Quote:

---

Originally Posted by Richard Dower

I Orthos dual primed for 3 hours 20 mins with the 414FSB settings.

Now booted into Windows at 430FSB, default (G)MCH+FSB:

http://valid.x86-secret.com/show_oc?id=120647

---

you got a good cooling
can you try 1.5v + 9 x max boot stable FSB and clockgen it?

keep pushing :)

Quote:

---

Originally Posted by PcCI2iminal

you got a good cooling
can you try 1.5v + 9 x max boot stable FSB and clockgen it?

keep pushing :)

---

I personally don't like using tools like clockgen to increase my speeds... It just doesn't seem right, I'd prefer to get my boot settings and stick with them :D.

I will up the CPU in time, i'm just trying to find the highest and stable FSB.

Lestat...HZ @ 1000MHz, 2.2V

http://valid.x86-secret.com/show_oc?id=120660

you have the DQ6 the HZ has alwyas been ok at 1000+ on the DQ6

the DS3 is fux'd it wont work and i doubt it ever will.


are you still on auto vcore richard ?

if so then go to 8x400 it might work.... maybe... if you have an early 6600 then i wont they took like 1.5v to go to 3.2 just really crappy conroes. well some did atleast.

http://valid.x86-secret.com/show_oc?id=120670

3.2Ghz...1.550V...but no testing done, just seeing if i could POST and boot in Windows.

you must be doing something wrong as 1.55v is way too much for 3.2GHz man unless you have the worst E6600 around here

Quote:

---

Originally Posted by dinos22

you must be doing something wrong as 1.55v is way too much for 3.2GHz man unless you have the worst E6600 around here

---

Yeah, you might be overvolting it right now

3.2 should only require about 1.4 or even less.

Save that 1.55 for a 3.6!

Quote:

---

Originally Posted by dinos22

you must be doing something wrong as 1.55v is way too much for 3.2GHz man unless you have the worst E6600 around here

---

not really Dino i have seen several people with early first release conroes that are having a hell of a time at 3.2ghz with anything less than 1.55v.
they are really crappy.

the ES chips do 3.3 and 3.4(like mine) at default.
the 0627's will do it also
but if he has one of the early chips.. they are crappy like that.
atleast some batches were. it was like the last chips in the die before they changed out hardware for new pieces in the manufacturing plant,, know what i mean.

I have a week 24 and it failed Orthos after a minute with 1.55V, unless a bios setting is holding it back, should i disable CPU Enhanced Halt CE1?, what about Virtualisation Technology?

Quote:

---

Originally Posted by Richard Dower

I have a week 24 and it failed Orthos after a minute with 1.55V.

---

that's just heat related

drob the vcore down and see what happens

I dropped it to 1.5V...it wouldn't boot, just restarted.

oh man doesn't look good.......well drop the Mhz back that's all you can do

i didn't realise chips needed that much vcore to be stable...........thinks my default vcore ~3.5GHz on E6300ES is better than i thought LOL

from what i have established, i need 1.36250V for 2.8Ghz, 1.41250V for 2.9Ghz.

I could hit 3.4Ghz no probs on stock vcore, but then I needed to go to at least 1.675v to go even 100mhz higher with my week 24. It needed a massive vcore jump to go any higher for some reason.

Lucky you, I can bench at up to 280MHz (can only boot up to 266MHz - but most of the time won't boot at that). Only stable up to 240MHz though...:( Shoddy DFI crap.

Congrats man, personal bests are still #1 (for you hahah).

Richard are you considering vdroop when you post your voltage settings?

Quote:

---

Originally Posted by BiOvOrE

I could hit 3.4Ghz no probs on stock vcore, but then I needed to go to at least 1.675v to go even 100mhz higher with my week 24. It needed a massive vcore jump to go any higher for some reason.

---

i don't think you were actually setting the vcore manually there

good to see OCAU guys here heheh

Quote:

---

Originally Posted by dinos22

i don't think you were actually setting the vcore manually there

---

Let me clarify. With vcore on Auto, I could get to 3.4. To get only 100Mhz higher, I had to manually set the vcore to 1.675 to get my system to even POST. Still using 1.675v now at 3.8ish. Temps of 52-54C under load.

Quote:

---

Originally Posted by BiOvOrE

Let me clarify. With vcore on Auto, I could get to 3.4. To get only 100Mhz higher, I had to manually set the vcore to 1.675 to get my system to even POST. Still using 1.675v now at 3.8ish. Temps of 52-54C under load.

---

ok now i know what the deal was

AUTO vcore automatically adjusts the vcore to compensate for the overclock hence you were not really on default vcore on 3.4GHz >> far from it actually. You were most likely around 1.6V actual vcore

Quote:

---

Originally Posted by dinos22

ok now i know what the deal was

AUTO vcore automatically adjusts the vcore to compensate for the overclock hence you were not really on default vcore on 3.4GHz >> far from it actually. You were most likely around 1.6V actual vcore

---

The only way he would know was if he checking in windows. My old asus board used to do that but there would be a variation on the volts every couple reboots. 1.6 to 1.55 and then back up again or that could just be the droop. I dont really trust the auto vcore. I feel more comfortable setting it myself.

Quote:

---

Originally Posted by MrDeeds

The only way he would know was if he checking in windows. My old asus board used to do that but there would be a variation on the volts every couple reboots. 1.6 to 1.55 and then back up again or that could just be the droop. I dont really trust the auto vcore. I feel more comfortable setting it myself.

---

somewhat >>>> for a reliable measure you should really pull out the old DMM and it will tell you exactly where you're at

actually PCProbe is on the money for vcore reporting for me

Quote:

---

Originally Posted by dinos22

ok now i know what the deal was

AUTO vcore automatically adjusts the vcore to compensate for the overclock hence you were not really on default vcore on 3.4GHz >> far from it actually. You were most likely around 1.6V actual vcore

---

Yeah, I'm aware of this. It was actually around 1.475ish at 3.4, but this board tends to undervolt by around 0.025, so about 1.45.

When set at 1.475 manually, I could hit 3.4 easily with no changes to the MCH, FSB, PCIe or vdimm voltages from their default values. But no higher till I gave it 1.675.

Quote:

---

Originally Posted by eXceededgoku

Richard are you considering vdroop when you post your voltage settings?

---

No i didn't factor in Vdroop into the manual setting of 1.550V.

Quote:

---

Originally Posted by BiOvOrE

Yeah, I'm aware of this. It was actually around 1.475ish at 3.4, but this board tends to undervolt by around 0.025, so about 1.45.

---

ok so you are saying that from 3.4GHz to 3.5GHz you had to raise vcore from 1.475 to 1.675. If that's the case there is something else other than vcore that's making the system unstable. You should not need more than 0.05v for every 100MHz increase in OC unless heat or other factors come into play

Quote:

---

Originally Posted by dinos22

ok so you are saying that from 3.4GHz to 3.5GHz you had to raise vcore from 1.475 to 1.675. If that's the case there is something else other than vcore that's making the system unstable. You should not need more than 0.05v for every 100MHz increase in OC unless heat or other factors come into play

---

Yep, that's how my setup is working. Tried all combinations of FSB, PCIe, MCH and RAM volatages but none of them helped at all. In fact any more than the default voltage on the HZ seemed to hinder any overclocking.

Not that I'm complaining, I'm Orthos stable at 3.7, and working on my 3.8 stability now :) .

Quote:

---

Originally Posted by BiOvOrE

Yep, that's how my setup is working. Tried all combinations of FSB, PCIe, MCH and RAM volatages but none of them helped at all. In fact any more than the default voltage on the HZ seemed to hinder any overclocking.

Not that I'm complaining, I'm Orthos stable at 3.7, and working on my 3.8 stability now :) .

---

3.7 at what vcore........your bios max is 1.7 :confused:

1.675 in BIOS. 12 hour Orthos stable. Which was my original point - 1.45ish to get to 3.4, but anywhere between 100 and 400 Mhz more needed a jump straight to 1.675.

Quote:

---

Originally Posted by BiOvOrE

1.675 in BIOS. 12 hour Orthos stable.

---

so you vcore did not gradually increase but straight to 1.675 right

if so you should definately make sure with a DMM that the voltage regulation isn't just glitching between 1.475-1.675

Yeah mate, it could well be a glitch with the board. I don't claim to be any kind of expert, I just know what works for me.

Auto wouldn't let me go any higher than 3.4 and neither would any manual setting below 1.675. And at this point I don't mind giving it 1.675, the temps are fine and it's rock-solid stable.

Quote:

---

Originally Posted by BiOvOrE

Yeah mate, it could well be a glitch with the board. I don't claim to be any kind of expert, I just know what works for me.

Auto wouldn't let me go any higher than 3.4 and neither would any manual setting below 1.675. And at this point I don't mind giving it 1.675, the temps are fine and it's rock-solid stable.

---

1.675v on water...........LOL PLEASE check the vcore via DMM

What for? 3.7+ seems like a good result to me, I'm not overly concerned with how I got there :) .

Quote:

---

Originally Posted by BiOvOrE

What for? 3.7+ seems like a good result to me, I'm not overly concerned with how I got there :) .

---

it's mainly my pure curiousity....i understand if it's too difficult :)

Quote:

---

Originally Posted by Richard Dower

3Ghz default Vcore...you joking???

---

joking , why?????



my friend is runing E6600 L624A761 @3250mhz @ Vcore default:








http://img239.imageshack.us/img239/6337/1yz7.jpg



regards

Well good luck to him, not all CPU's are the same. Personally i think it's a bios issue. I think there is some problem or wall being encountered with a CPU speed past 3Ghz. At least for me and my mobo/CPU.

Considering the new F5d increased my FSB from 340 to 445 i think there is also a bios issue with the Vcore. Thus hopefully in time this will get solved.

If not then i'll wait until November and buy a new E6600, i'll be more likely to get a week 27 or later.

i would say that wall is probably something to do with your rig as most go past 3Ghz with much ease

Then it's the CPU.