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
Printable View
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.
you got a good coolingQuote:
Originally Posted by Richard Dower
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.Quote:
Originally Posted by PcCI2iminal
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
Yeah, you might be overvolting it right nowQuote:
Originally Posted by dinos22
3.2 should only require about 1.4 or even less.
Save that 1.55 for a 3.6!
Quote:
Originally Posted by dinos22
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?
that's just heat relatedQuote:
Originally Posted by Richard Dower
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?