BC,
:shock: :shock: :shock: :shock: :shock: :shock: :shock:
I'm in shock. You have nice and great setups.
Printable View
BC,
:shock: :shock: :shock: :shock: :shock: :shock: :shock:
I'm in shock. You have nice and great setups.
Well,
I'm single, live modestly within my means, and this is what I do with my 'mad money'. I also build machines for friends to kill my idle time when i'm not busy going somewhere or doing something.
It's obvious I'm a geek at heart.... true ROFL!!!
Here's the funny part... This ALL started as the result of 2 things...
1) my ham radio licence at age 12.
2) seeing an HP-35 calculator (now a dinosaur) and being obsessed
with how it works.
BC
Keith75,
Take a look at this page:
AMD64 Device Driver Support for Windows® and Linux.
Thanks for the link em.
BC,
I have overclocked alot of machines and have had mostly good but a few bad experiences, 1800 and a 2200 that would overclock worth a damn. I would suggest you overclock it one processor speed. So your 3000 would be a 3200 or your 3200 a 3400 and be happy that you saved the money not buying that faster chip. Now on the other hand if you are just doing it to have fun then I am kinda new to the A64 and what voltages it can safely take. Visit the link below though as it may give you some useful info.
Keith
http://forums.pcper.com/showthread.php?t=299229
Keith,
Thanks. It's been my experience, and moreso now with the smaller fab process .13 and upcoming .065 that the limits will be leakage current and junction current/temp. the juctions are getting awefully small and hence wont tolerate much over design.
So far, the most I have tried is 1.55v and 2.31 Ghz (FSB 230) on both the 3200 Claw and NewCastle. The Claw was stable, but i felt i was pushing it for no good reason.
The NewCastle jumped rigt up to its cap of 2400 (2.37) without flinching. Too bad i can't unlock that... my unlocker / reclocker can't undo burned junctions to limit speed... lol. I bet the NewCastle (unlocked) will go up to 2.6 / 2.8 without much trouble.
NC
When you talk about overclocking it seems to me like chinese talk. I don't understand nothing at all.
pepe,
Think of overclocking as this...
Your car's engine was designed to run at a normal speed and a 'red line' speed. What we are doing is figuring out how to safely go PAST the red line without destroying the engine.
Example: Volvo engines are designed for 8000 RPM of 100% use, they are limited to 7000 by the onboard electronics to extend the life of the engine. Most people drivethem in the 3000- 5000 RPM range.
What we want to do is run that same engine at 8000 normal and be able to safely go to 10,000 RPM when we want with a limit of 12,000. Some folks want to run at 10,000 all the time. AND... we still want it to last just as long and be just as reliable.
Does that help?
BC
I second that. I'm using one machine running 2 nodes. I get about 220 a day if there's no hang up's. (ex. stupid yahoo dsl...) anyways, 220 a day is as fast as this thing will go. I tried running 3 nodes but experienced nothing but slow system performance. I'm sorry I don't have 10 computers running 24/7 like Chaz... :D If I had that I wouldn't have to use the heater in the winter. :cool: Someday I hope to have a home network of at least 10 pc's. But for right now I have to be content with 220 WU's, Candidates, Conformer's or whatever else they may be called. Does anyone have any tips on how to speed it up any? :help:Quote:
Originally Posted by em99010pepe
DSPY is an excellent tool. I highly recommend it if you don't have it. :thumbup:
I recently discovered something with the A64's that may or may not help.... It's probably good advice overall and for you serious over-clockers, probably common knowledge.
What I did was get the best memory I could (Corsair XMS512-3200LL).
It's 2-2-2-5 and stable WELL past what the A64 3200+ can run so far.
It runs great bank interleaved and all.
I locked the Memclock/CPU clock to 1:1.... so there was no problem there,
and then simply incremented the FSB in steps of 5 (AMD prefers multiples of 10, but 5's are ok for some reason) until I lost stability at 235. I do not know if it was a lack of CPU voltage (current = 1.55, full range of manual voltage choices there up +/- .3 volts in .025 steps) or DDR voltage (current = manual 2.7, not 2.75 as recommended by Corsair'. My options are 2.6,2.7, 2.8 or auto for mem) or some other sync problem.
My Clawhammer... rated at 2.0 Ghz, is running nice and cool at 2.25. I can push it easily to 2.3 (FSB = 230)... After that, I lose the processor. Perhaps I need to increase the voltage past the auto-set 1.55 (normal is 1.5 at 2.0G). The CPU multiplier for Claw is 10:1. At 2.25G, under 100% CPU load, I have MB of 31C, Processor of 40C. Power supply is Antec 550TruePower (VERY tight regulation).
The NewCastle... Rated at 2.2G... will go all the way to 2.37 (aka 2400 Mhz) which is the AMD imposed cap. The CPU multiplier for NewCastle is 11:1. I used the same techniques and settings as defined above.
Hope that helps you....
Can anyone tell me what to do with what I have or am I at the max?
Thanks in advance,
BC
Can anyone translate that into english???