OMG!! - i've reached 360FSB!

Printable View

Show 100 post(s) from this thread on one page

09-12-2006, 12:01 AM
dinos22

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
09-12-2006, 12:18 AM
BiOvOrE

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.
09-12-2006, 03:37 AM
dinos22

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
09-12-2006, 04:00 AM
MrDeeds

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.
09-12-2006, 04:07 AM
dinos22

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
09-12-2006, 04:22 AM
BiOvOrE

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.
09-12-2006, 04:26 AM
Richard Dower

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.
09-12-2006, 04:30 AM
dinos22

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
09-12-2006, 04:37 AM
BiOvOrE

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 :) .
09-12-2006, 04:49 AM
dinos22

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:
09-12-2006, 04:57 AM
BiOvOrE

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.
09-12-2006, 05:01 AM
dinos22

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
09-12-2006, 05:09 AM
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.
09-12-2006, 05:12 AM
dinos22

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
09-12-2006, 05:17 AM
BiOvOrE

What for? 3.7+ seems like a good result to me, I'm not overly concerned with how I got there :) .
09-12-2006, 05:23 AM
dinos22

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 :)
09-12-2006, 06:17 AM
mascaras

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
09-12-2006, 07:19 AM
Richard Dower

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.
09-12-2006, 07:23 AM
dinos22

i would say that wall is probably something to do with your rig as most go past 3Ghz with much ease
09-12-2006, 07:26 AM
Richard Dower

Then it's the CPU.

Show 100 post(s) from this thread on one page

All times are GMT -8. The time now is 02:41 PM.

XtremeSystems