• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

David's Learning and Rambling Thread

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.
Green setting? Sir, you are benchmarking not surfing the web, grow a pair! :p

Being serious, where are you at with Vtt, and NB voltage?
 
Haha!

Checking my scraps of notepaper, I had:

  • VCore: 1.6 V
  • CPU PLL: 1.60 V
  • Northbridge: 1.55 V
  • FSB termination: 1.5 V
  • Southbridge: 1.15 V

I didn't mess with DRAM setting as the RAM was running well within spec.
 
PLL I thought default was 1.8?

But yeah, that should be enough voltage to get you were you are at... thats for sure.
 
I'll check, but by default I'm sure the PLL was running around 1.5 V. What's the view on LLC? Yay or nay?

How high is too high for the NB? I don't care if I fry a CPU, but I'll cry like a baby if I kill the board.
 
I would imagine around there on air... Its been a while since I have been on s775 though... :(

Im learning again on e6600 and e6750. :)
 
The NB temp was pretty high so I have a fan aimed at it, which brought it back down quite a bit.
 
Got 4.347 GHz validated on 1.5175 V on the 925, but it's way too hot to bench. Trying to back off the voltage a little, I think I'm giving in and ramming up the VCore too quickly.
 
You need SetFSB, usually you can get a few MHz more fsb in windows with setfsb vs bios settings.

EDIT:
775 PLL is 1.5v stock. Over 1.6 rarely helps.
 
Last edited:
yeah I've always gotten a lot more using setfsb than trying to boot with different FSB.
 
Was hoping my 630 would have arrived, but no such luck :(

Maybe that's fate telling me to write my damn thesis.
 
Got the Celly D 336 to work last night, but it only boots after a CMOS reset. I think on subsequent boots it tries to kick the FSB up to 200 and it can't handle it, even if I set vcore to 1.6 V and bump up the NB voltage.

I can boot into Windows and use SetFSB up to around 180 MHz FSB (http://hwbot.org/submission/2245359_). We don't have any team entries for this chip so I'll probably rattle through the 2D benches to get the ca. 2 TPP (per test) they are worth.

I also acquired a P4 550 @ 3.4 GHz which might help me get a higher valid on air (or not :p). We're also lacking some scores for it.

I doubt I'll get many hwboints until I get them all under DICE, to be honest.
 
PM Massman, sometimes the the HWBot software screws up and nobody can touch it bit him and their mod people.
You did everything correctly as far as I can see.
 
I think a couple have boobed. I'll get my wPrime 1024M and Superpi 32M scores done then I'll see which I need to report.

My P4-550 arrived (fast!) but I'm holding off testing it until I get the complete set of Celly-D tests onto the 'bot. That, and I have a thesis to write :p

Mmmm... processors
 

Attachments

  • 2012-01-26 22.19.15.jpg
    2012-01-26 22.19.15.jpg
    440.9 KB · Views: 69
Struggling to keep the P4-550 stable enough to bench it. My best validation was at 4340.6 (only 190 MHz away from getting > 0.1 HW points ...) but I've had to back right down to ~4.2 to get wPrime32M to run. wPrime1024M will maybe need to go down further - Windows keeps encountering critical errors that require reboots ...

The temperatures aren't hellish (ca. 65 C running wPrime32M) and I have the Vcore at 1.6 V with LLC enabled, and NB at 1.49 V. Any higher on the Vcore appears to be unstable.

Any tips on improving stability? I'm rapidly learning to redefine stability as "long enough to run a benchmark and nab a screenshot"...
 
Back