uzairi..
not sure whether u know this
this procs like to undershoot and overshoot the ref termination voltage..

geeee kindda hard leh.. just now was looking for gtl 85.3.. kekeke.. couldnt..
this is y depesrate need of the UT mobo or any mobo that has that bios.


This post has been edited by cstkl1: Feb 14 2008, 11:59 AM

stress ure rams via memtest86
not orthos.

or memtest windows.. watch those temps on nb rocket up..

unless ure lucky

geee got somebody in lyn whos q6600 can do 3ghz at 1.1v.. kekeke

off ure PAE..
no point..

dont u think ure overvolting that proc of ures..

and 533 bus.. the prob is not the vcore.. is the NB voltage

thats y ure 500x6 had problems

technically depends.. games i would go for 500x6

overall performance would be ure 400x8. at the lowest trd CL3.


but pretty sure u could have gone to 9x400 at less than 1.2v



This post has been edited by cstkl1: Feb 17 2008, 11:07 PM

trial and error
definitely more than 1.5v on NB
and ure fsb termination voltage cannot go more than ure vcore.

fsb termination voltage aka cpu vtt voltage aka ht-link voltage.

all boards has this

checking ure manual now.. find it weird that ure mobo doesnt has this.

P35 DS3L
http://america.giga-byte.com/FileList/Manu...d)s3l_2.0_e.pdf

Page 47
FSB Overvoltage



This post has been edited by cstkl1: Feb 18 2008, 03:29 PM

hence y i say keep it lower than ure vcore.. so most of the time dont even have to raise it.

auto.. bad idea..

simple.. not even talking about gtl in the reference to advice to last screenshot.


This post has been edited by cstkl1: Feb 18 2008, 05:05 PM

no idea bout gigabyte p35DS3 and to be more specific..

but on asus x38, Evga 680, Asus Striker Extreme ( One of the earlier boards,, fried two rams and one proc.. degrade actually), Foxconn P35 Mars, Gigabyte N680 DQ6 (Fried Rams for breakfast), EVGA 680 SLI( Rmaed twice and now dead still have it if u want to prove the fsb termination theory) P35 DQ6
all of this boards its a NO NO.


ure fsb termination voltages is the one that overheats the proc and kills the proc

its the link between the core to the NB.

google it. quite a no of ppl killed either their proc or mobo by doing that for a long period of time.

to make it plain .. keep it lower than vcore.. thats all i am saying.. not trying to debate..


This post has been edited by cstkl1: Feb 18 2008, 05:27 PM

Dude lets make this thread actually worth while to troubleshoot overclocking settings.

1.CPUZ screen shot of first CPU tab Either 450x8 or 424x8.5 or 400x9 - Download Here
2.Orthos one Large FFT for one hour - Download Here
3.Orthos Small FFT for one hour.
4.Memset - Download Here



Reason for posting.. i am very confident that at 3.6ghz all penryn can do less than 1.2v.
so just wanna see whether this is true or not. Cause so far i have tried quite a number of batches and they all can do less than 1.2 which is y i find it weird that ppl are doing 1.4v for 4ghz.

This post has been edited by cstkl1: Feb 25 2008, 05:42 PM

dude can post a screenshot ure gigabyte voltage program or everest voltages
try the exact voltages but maybe higher vcore as my screenshot..

the VTT,NB etc..

a few of my friends also has e8400/e8200 batches ranging from fpo 42 to 48 and all of them can do less than 1.2v for 3.6ghz mainly on asus/dfi/abit mobos. heck one of them even on Neo2... so just wondering on the gigabyte.


even better if u can post like the template above..

easier to see..

This post has been edited by cstkl1: Feb 25 2008, 03:16 PM

updated to 4 hours 30 minutes.

not enough info..

is it possible to show a everest ultimate OSD with the voltages..
ty

want to see what ure running at..

3 voltages in paticular
NB/VTT(FSB termination) and ure PLL.
oh yeah and to get the full voltages sensors
please enable ACPi table especially ACPI 2.0 support

---

Added on February 25, 2008, 5:47 pmhmm still incomplete dude..
so many voltages reading missing.

i wonder y. dfi UT can read ..
gaygaybyte ACPI table is not a 1.1 or 2.0 prehaps??

hmm that case dude dunno whats ure fsb termination /nb on load.


This post has been edited by cstkl1: Feb 25 2008, 05:48 PM

i know this is leceh
but can u check at ure bios at the monitoring page to check whats the actual voltage for ure FSB, NB and PLL.

in the bios??

damn man
u guys should sue gaygaybyte..

or get a voltmeter.

didnt try e8200..

no..
core temp has a error of 0.1v.
so its 1.1375..

try it at stock with ure mobo.. the voltage u get at stock timing is ure vid..
also note certain mobo like DFI and FOXconn MARS gives inaccurate VID readings.
especially when EIST is enabled..
the problem is the ACPI table reading which core temp takes the reading from.


This post has been edited by cstkl1: Feb 26 2008, 10:26 AM

eh no dude..
warranted up to ure box stated max

hmm wait retract that back..

reason is cause last time thats what happened when i rmaed my p4. they knew i overclocked it and said it was warranted according to the box stated max..


This post has been edited by cstkl1: Feb 26 2008, 05:56 PM

hmmm dunno leh

but this is what happened when i rma my P4 like 2 years ago.
i send it to them and it was a few voltages above the box stated max.
and then they replied that it is void since i went above the box stated max.

good question

but this was debate a few times.. but afaik it is true during the p4 days that intel has a way to find out what vcore u were running last before the proc kaputs.