tried tighten the ram timings, but dont see much improvement.
set the timing to 4-4-4-12 2T and got 1M Pi @ 13.671

decrease the command rate to 4-4-4-12 1T and improve just a couple tens of a second.

didnt further to tighten the timing, no free time to rum memtest yet.

This post has been edited by VT-Ten: Jul 9 2007, 11:51 PM


Attached thumbnail(s)

just came back from LYP and got myself an e6850. got it cheaper than above (member price).

if time permits, will test it out tonite and upload the results.

---

Added on July 20, 2007, 5:00 pmmine too got very slight improvement when tightening up the ram timings. can we conclude that super pi doesnt take advantage of ram timings?

This post has been edited by VT-Ten: Jul 20 2007, 05:00 PM

my e6850 is up. but doesnt seem to respond well to overclocking

temp is cool. lowest (non oc) 27C core0 and 21C core1

4000x9 @ 1.38 vcore BSOD. 444x9 @ 1.55vcore also BSOD. still messing with it now....

@irenic
what is the stock vcore for this chip?

This post has been edited by VT-Ten: Jul 21 2007, 06:28 PM

Stepping B
Asus P5n32e mobo

last time e6600 pumped max 3.8Ghz no problem. but somehow im sufferin with this one.

---

Added on July 21, 2007, 7:37 pmL720A740. and yours?

This post has been edited by VT-Ten: Jul 21 2007, 07:37 PM

this is really troubling me. my e6850 doesnt even seem to run stable at stock speed.

set to 1.48vcore and everything else to stock. orthos gromac stress for abt 2 hours no problem. ran some games (CoH and TR anniversary) and the rig will hang when playing half way.

any idea what could it be?

...and guess what. my rig hung again right after i posted the above message. left it alone for a minute and blue screen came out with the message below;

***STOP: 0x0000008E (0xC0000005, 0xBFAA9E10, 0x9A7CA550, 0x00000000)
*** nv4_disp.dll - Address BFAA9E10 base at BFA16000, DateStamp 45df38b5

No hardware and/or driver changes other than the proc and PSU.



mmm... theres no hardware and/or driver changes other than the proc and PSU.


any idea what's causing it?

This post has been edited by VT-Ten: Jul 21 2007, 10:27 PM

yeap, core clock was too high. heh.... paiseh paiseh

The BSOD im experiencing are not entirely from the graphics oc. defaulted the gc clocks still experiencing OC errors (BSOD, frozen screen, post fail etc)....

so far managed to pump to 3.825Ghz @ 1.55vcore. need kinda high vcore if you ask me. tried to push further, even pumped to 1.6vcore, but will get screen lockups and POST fail.

hmm... even my previous e6600 can push to 3.844 with similiar settings, but my e6850 cant?




Attached thumbnail(s)

ram volts running at 2.225v. prolly different boards will be differently by speedfan.

ram speed was left stock at 400mhz.
as for the 12v readin, not sure if asus probe is readin it correctly or not...

this is my current setup;

400x9 @ 1.52vcore
NB 1.4v
Sb 1.4v
1.2VHT 1.45v
VTT 1.5v
vdimm 2.225v
timing 5-5-5-18 2T @ 400mhz

proc idle temp 29C core0 and 23C core1. readings are identical using asus probe, speedfan, coretemp, rivatuner & everest. load at 48C & 46C on the respective cores.

pc hung after orthos for 2 hrs using the above setup.

This post has been edited by VT-Ten: Jul 23 2007, 01:25 AM

you bet! got hammered by my wife when i told her that i spent a couple of hundred to top up for a proc that (currently still) couldnt outperform my previous proc

This post has been edited by VT-Ten: Jul 23 2007, 01:58 AM

orthos ran for 6+ hours with everything stock without errors... check out the temp at load, dun you just LOVE IT!?


Attached thumbnail(s)