KE san...amacam e6850 on WC??? going further???

never try.. now using e2160 only =D

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

if i not mistaken it is 1.35v .. neway what mobo r u using?

and whats ur e6850 stepping?

Stepping B
Asus P5n32e mobo

VT-Ten,seems like ur mobo need to feed a lot of vcore to proc?

my friend's using e6850 stock 1.35vcore can go 3.6GHz

may i know how high u can go with ur previous proc?

sorry, what i meant is the week.. sthing like L72..... u can find it stated on ur box..

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

aikk!!! test la the E6850 on water....so any luck on E2160??? 100% oc???

same like mine.. ermm

hehe e2160 3.65ghz sesenang jek.. tp nak push 3.66ghz takley langsung.. dah max haha

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

what is the problem u facing?

come come pass me the e6850...i'll put in on my cascade see how high it can push. Shows a lot promise with its cool temps.

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

might the display driver infinite loop error....coz the error report states nv4_disp

Try re-install your display driver see if it works. Else, windows is corrupted maybe due to mutiple times of unstable system booting into Windows.

@VT-Ten

It is most likely due to your GC overheated. Did you OC it ?

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

VT-Ten, 4000 x 9 is dammmmmn high leh... 36.0ghz wor... sumore @ 1.38 vcore only sure bsod lar...

irenic, ur e2160 wanna sell off??? pm me if u do, me looking for 1 for secondary rig... tq...