what about if lower mulitplier, eg. 8x

yup can do...8x500 easily..9x500 also can do..but my vmch on this mobo not high enough to stable it...

4.5Ghz validation

ok guy can't do any oc anymore..my ballistix suddenly dead...i never push it over 2.2v...last nite it wont boot anymore...tested on other pc...same... hav to send RMA...later on will test the mobo if it got problem or not...my sales is on hold...

This post has been edited by flatfinger: Feb 4 2008, 09:47 AM

current issue with E8400..

the FSB termination voltage
When i go lower than Vcore there is a input/ouput thingy that reduces any overshots by the proc according to intel spec.
hence lower vcore was easy..

problem..
NB .. needs higher FSB termination voltage.... and with the proc having so low vcore.. errr..


hmmm.
500fsb 1:1 mem .. still not stable..

Btw, anyone has E8200 here? Please post some results

yeah...if got E8500 also...pls post ur result...

ok confirm my mobo also gone..i think the mobo make my ballistix dead... ...guess i dont have pc temporary ..sending RMA...

This post has been edited by flatfinger: Feb 4 2008, 07:21 PM

Good but no time to push it.3.2(400x8) can do 14.3's spi.

i still have my E8200 in the box... lazy to open... motherboard haven't arrive yet...

if anyone offer me RM700.... i will sell it off
wakakka

Some results of E8400 on Gigabyte P35 DS3 F12.


Vcore bios : 1.425v
Vcore load : 1.344v
Vmch : +0.1v
Vfsb : stock
Vpci-e : stock
Vdimm : 2.0V

This post has been edited by uzairi: Feb 5 2008, 03:30 AM


Attached thumbnail(s)

nice result...4.1Ghz@1.35v....try to push it more

Hey, you've got a new baby for folding ka?

Will do so, now assraep-ing the proc with folding to check stability..

since u r on wc, why not push more higher? but why core temp so high even on wc? is that reading correct?

The reading is wrong, its not hot at all fyi.

Btw i did notice about the small fft test at orthos. It should be Min fft - 8k and Max fft 64k, not 8k for both.

The setting might go berserk after a while, weird but i noticed the changes of the values while orthos.

a few ppl been asking me whats the difference with OCCT and Orthos
basically this is OCCT

run Orthos priority 7/8 with memtest windows 256mb on 25 minutes..
1st minute for temp monitor.. last 4 minutes for cool down..

pass this and u pass OCCT 30 minutes guaranteed

better to do this way as u will know whether ure it was ure mem or proc that failed u.

example of brute force overclocking aka plug and play.

[attachmentid=394884]

based on the above u will also know if u can pass OCCT 1 hour.. samething but on 55 minutes.

best way to test if ure like surfing and stressing
if not heck do memtest 1024 would do.

* note.. theres 3 versions of OCCT... some uses 256mb and some uses 512mb..
personally feel 256mb on long periods reserved to a program for stressing is enough..
and dont advice to run d9's too long..

This post has been edited by cstkl1: Feb 7 2008, 01:06 PM

@cstkl
I believe that OCCT does a lot of stressing aye. priority 7 is qiuite high i mean for me, and to run memtest at 256MB, i do the 512Mb test * 2 for 3 hours normally, for stability.

Good guide there cstkl1.

higher priority

its just means it uses most of the unused cycles thats all..
most of the time no program runs on priority 7/8 other than ure OS.
but which OS stresses the core that much .. highest was vista.. around 75-80 percent.

Aik!!! last time u said pity to me selling my E8400...y u selling it too???

cause getting a e8500... well thats the aim.?? and a e2140( curious actually on this proc)

ures i said pity cause true potential unknown..

my E8400 same batch as urs....already buy ka E8500???

@cstkl1
dont bother about the e2140s now bro, most ppl are having problems posting after 410, 420Mhz. I dont know why, even with M0 stepping. I know one user who got 4.3Ghz on an e2140 with LN2, thats crazy.