Quick question for the WCG guys: Conroe / Allendale...

[[XC] DragonOrta]

STEvil, I'll let you know how that board clocks with an e6400 tomorrow. I just got my case, a HDD, and the e6400 in for the Dual-VSTA board I got a month or so ago.

[rob725]

@meshmesh:

The S3 is definitly promising; a few great results for $100 mobo. Was watching the action in that thread and the info just kinda stopped. Like to hear more about peoples experience with it. If you go that way, please let us know how it goes.

[STEvil]

VIA PT800 chipset iirc.. could be wrong. Trying to find the PLL at the moment.

EDIT

PT880 Pro/Ultra. Lots of info here: http://72.14.205.104/search?q=cache:...a&ct=clnk&cd=1

Voltage mods: http://www.xtremesystems.org/forums/...ad.php?t=95250

PLL's possibly: http://72.14.205.104/search?q=cache:...a&ct=clnk&cd=2

III) FSB clockgen // cpucool fsb
conroe865pe has pll winbond :
conroe865pe should have, according to systools site, http://www.techpowerup.com/wiki/doku...sd_unsupported
as clock_generator:
W83194BG-SD
winbond website:
The winbond website:
W83194BG-SD
Step-less Frequency INTEL 865™ series chipset Clock Gen., Pb-free
SSOP 48
http://www.winbond-usa.com/products/...3194BG-SDc.pdf

I mailed clockgen guy and he replied (thx to Franck from cpuz) he has beta that supports similar winbond pll
W83195BG: he thinks it is close to the used pll.

Cpucool responded that it has support for W83194BR-SD and this pll (comparing data sheets) is equal to W83194BG-SD

[rob725]

For me, if I was trying to save the money, I would save the money on the chip and put it towards the p5b;

I'm not sure I agree with myself. You said right off the bat to remember you were new to overclocking, and less has to go right to get 350-360 x 9 than for 400 x 8, where for instance you will need RAM capable of running reliably at 800mhz.

[RSmura]

Please excuse the noob question, but aren't all the C2D, except the EXTREME, locked multiplier?

[Got Chow]

RSmura,

Yes and no. Yes, they are locked so that you cannot go to a higher multiplier. But, kind of like the A64s, you can take the multiplier lower, DEPENDING on whether the motherboard allows for that or not. So far, most (if not all) 965 chipsets allow for this. There is a new P5W DH beta BIOS that allows this, but it is not finalized yet.

I believe it should function in the way that you cannot go up in multi unless it's the extreme edition, but you should be able to go down in multi so you can max that FSB.

[[XC] DragonOrta]

Well, the 775Dual-VSTA will have to wait until next week, because the BIOS I have doesn't support Conroe. I've ordered a cel-D from from Newegg to flash it, which will hopefully get here soon.

EDIT: And C2D is definately the best cruncher available. I love looking through my results in WCG and seeing that my completion time is at least 1/2, sometimes 1/3-1/4 of what the rest of them are.

[STEvil]

what bios are you using? I've got 1.3 on mine for now, but no C2D for it yet.

The Celeron is benching at 4.1ghz with less than (1.28v) stock volts (1.4v) on stock air ! Prime stable somewhere around 4.0 ish probably.

Latest bios avail is 1.7 I think, should find a modding tool for it.

[[XC] DragonOrta]

I have the 1.10 BIOS. I have 1.80 loaded on a floppy and all ready for flashing once my cel-d gets here.

[rob725]

For those considering e6400: Looking at the thread below, it seems like e6400s may be somewhat more stubborn about being coaxed into higher clock speeds. Obviously, this is a generalization and there are plenty of exceptions and may be a passed issue (there seems to be a growing feeling for c2ds that later-week processors are improving in oc ability), but I notice that many have had no success moving passed 3.2ghz.

I have had the chance to play a little more with my wife's rig and can also say that it does not seem to like going above 3.2. There are still many things I haven't tried (I am am not overly motivated to figure this out as a 3.2 c2d is still a smoking machine which she is very happy with) and it may not be the chip, but I can say that that both the e6300 and e6700 rigs would run 3.2 with less coaxing and went beyond it very easily.

Again, not much of a test sample, but I pick up somewhat of a pattern in this thread. Food for thought anyway.

e6400 overclocking thread

[meshmesh]

i assume you are aware of this thread and this external post as well.

in a nut shell, the boards hate to be booted at default CPU multi between 370-399, but happy below 365 and 400 and above.

So yes, the 6700 (10*320) and the E6300 (7*457) are OK.
The 6400 is also OK (8*400) but not between 8*370 to 8*399. it will boot beyond 8*400 with no problem if your memeory allows it (but only up to ~415*8 using clockgen though). This is all explained in the threads.

[rob725]

Aware of those. Mine is even fine between 370-399. It doesn't like 405 or 410. Again, may not be chip related, but in looking through 6400 thread there seemed to be a fair number of people getting stuck at lower clocks and a couple observing that 6400's did not seem to clock as easy as 6300's. Just wanted to be sure anyone thinking about 6400 caught this thread.

Thanks.

[meshmesh]

Aware of those. Mine is even fine between 370-399. It doesn't like 405 or 410. Again, may not be chip related, but in looking through 6400 thread there seemed to be a fair number of people getting stuck at lower clocks and a couple observing that 6400's did not seem to clock as easy as 6300's. Just wanted to be sure anyone thinking about 6400 caught this thread.

Thanks.

Thanks Rob for the heads up. Been checking the thread now. Yes, some poeple have problems as you posted! One may initially think the E6300 are marginal E6400. This whole intel thing flies in the face of logic and has more to it than it appears on the surface. The next period is going to be an education period, me guess.

They are actually comparing production week! It might end up being total indiviual luck at the end. Maybe just get along with it and accept what one gets. And if say 400*8 is attainable, at good temperatures easy as you said, so be it and settle at that for 24/7 and be done.

BTW, to add to the confusion, just saw a thread on the new (cheap?) P5B-E.

[rob725]

It's ok only cuz it my wife's!

Otherwise I would be working to figure out if its the chip, mobo, ram, vmch, vfsb...I went through this stuff with the 6300 to get it to 500 fsb and managed to do dual 32m super-pi, but no prime. I also had to work a little to get the 6700 to run prime stable at 3.6 and to super-pi at 3.8. But neither of those rigs took any effort to run at 3.2 and very little voltage increase. The 6400 did not really take much work for 3.2, but it seemed to need a little more voltage.

Also, the 6300 and 6700 do not seem to mind running hot under load, whereas the 6400 past 400 wants to crap out before coretemps reach 60. ( Have had 6700 priming near 80.)

Maybe there is something to the weeks. My 6400 is wk 25, while 6300 is 27.

[meshmesh]

It's ok only cuz it my wife's!

And as long as the wife is happy, let it be. Mine is lucky to have a user account

Also, the 6300 and 6700 do not seem to mind running hot under load, whereas the 6400 past 400 wants to crap out before coretemps reach 60....

Not many reported for week 25 though. The individual chips vary considerably. For week 25:
3.30Ghz 1.50Vcore
3.36Ghz 1.50Vcore
3.44Ghz 1.36Vcore
3.58Ghz 1.40Vcore

Some guys are really unlucky:
3.4Ghz 1.5875v (north bridge at 1.45V though)

I guess the lucky ones had an E6800 with a bad cache while the unlucky ones may had a perfectly good cache but with a single weak transistor in the core logic itself. No way to find out before hand.

maybe Intel downgraded some chips to E6300 at week 27 to accomodate demand if the yeilds are good. They have done it before.

There are really many variables in this thing. Even a poorly applied TIM under the MCH may prevent OC. Maybe a 50mm fan would help. Who knows.

....( Have had 6700 priming near 80.)

Don't know about Intel, but my AMD shuts down at 61C. The 80C would be BBQ time! Not even worth it IMO.

[rob725]

Yep, that's why I'm not running at 3.6. That's also in-die coretemp. Asus probe would about 13 degrees cooler. At 3.5, I use 1.4375v and running wcg, coretemps stay around 55, probe at 42-43. For 3.6, i have to increase vcore to 1.55 and I just don't like those temps for 24/7. I am considering lapping the cpu to see if I can't run 3.6 a little cooler. The cpu was pretty concave on the other two, so I ended up lapping them. Not sure I will though as it is running so well at 3.5, I hate to mess with it just to get another 100mhz I prolly won't even notice in actual use.

The funny thing about the c2ds is how easily it is to get spoiled by them. They're faster per clock than any thing out there and we complain when we "only" get a 1ghz overclock. lol