Share some knowledge with the rookies
I don't want to be real specific so other people will benefit from this.
There are a ton of directions to go when beggining to learn about overclocking. What tutorials should I read and what info is necessary to research the process for your personal application?
What is a reasonable expectation for performance increase, is it a set number or a percentage of stock?
Is there a performance increase ratio that should be targeted that will balance the risk with the performance gain?
I'll read up the suggested material before I ask anymore questions.
thanks,
There are a ton of directions to go when beggining to learn about overclocking. What tutorials should I read and what info is necessary to research the process for your personal application?
What is a reasonable expectation for performance increase, is it a set number or a percentage of stock?
Is there a performance increase ratio that should be targeted that will balance the risk with the performance gain?
I'll read up the suggested material before I ask anymore questions.
thanks,
0
Comments
I know, for example, that I can get about 2.4-2.6GHz out of a Winchester Athlon 64. I know that a JIUHB Athlon XP or a mobile Barton/Thorton will do about 2.3-2.6GHz with ease. I know that modules based on Samsung's TCCD chips can easily hit 250MHz on light voltage increases.
When I know these things, I immediately set my overclocking target for the lowest of the typical range.. Then it's a matter of finessing the CPU/RAM/Video Card up from there with fiddly combinations of voltages, multipliers and frequencies. The performance increase as a result is directly correlated with the quality and overclockability of your components; some components are more likely to give you a linear percentage increase though -- For example, the Athlon 64 is very good at delivering a performance increase equal to the percentage points in your overclock; from 2000MHz to 2200MHz is a 10% overclock, and the Athlon 64 will return a 9-10% performance increase as a result. Memory is a less exact science, as increasing the FSB from 210 to 220 might not give you the same result (It might be slower, actually) than if you increased it from 210 to 219; it's very much guess and check.
Video cards are so damn random in their overclocking that the best way to go is to start upping core/memory by 10MHz increments until you get little sparklies on 3d rendering. Then start backing it down by 2MHz until they go away; when they go away, you've overclocked your video card as far as it will go without cooling increases.
Risk/performance gain is a trickier question; generally speaking, if the computer boots up and runs and passes all your stress tests, then you're not at the damage point. Where this could go wrong is with memory, which will absorb a lot of voltage and still run, but might it might be damaging in the process. Always use the lowest voltage your memory will take to hit your target FSB speed - if you have to go above 3v, it's a good idea to get some airflow on it with an 80mm fan mounted in any crazy manner you can think of.
When overclocking memory, you have to balance timings with speed. The best thing to do is lower your CPU multiplier until it hits rock bottom, then at the loosest timings possible (3/4/4) see how fast the memory can go on stock voltages. Then up it .1v and see how fast it can go, then up it another .1v, then another until about 3v where you have to add cooling. Then once you've got your maximum speed, benchmark it and right the numbers down.. Then try to tighten up the timings, 3/3/4, then 3/3/3, then 2.5/4/4, then 2.5/3/4, then 2.5/3/3. Benchmark each set, and record the numbers each time. If you hit a certain timing combination that doesn't work at the frequency you've selected, try lowering the frequency and seeing if your tighter timings produce better results than the higher frequency with looser timings.. Only your computer, and you, can decide which combination will work best for you. Similarly, when overclocking your FSB, you have to find out eventually what your CPU will take (Particularly with the Athlon 64, where FSB overclocking stresses the memory controller) -- both in terms of the FSB and the core speed. Once you've gotten a target speed on your memory, slowly bump the multiplier up until the computer won't boot - then increase the voltages slightly (Generally a max of +.3v for any given chip, but this is not a set rule) until the CPU requires additional cooling or has hit its clock ceiling.
Once you fiddle with computers a lot, and read messageboards, you begin to derive an intuitive sense about components; you know what chips overclock well, what ones don't. You know which motherboards are good overclockers, and which ones aren't. You know where to buy certain components from because they're the most likely to ship you the newest version of that component, and so on.
It's 90% foreknowledge, 5% guessing, 5% luck.
Athlon 64 chips can only have their multiplier adjusted downwards.
Athlon FX chips can have their multiplier adjusted in any direction.
Both platforms can reliably hit 250MHz.
The Athlon XP generally doesn't top 230Mz FSB without voltage modifications to the motherboard itself. With a mobile chip and an nForce2, the multiplier can be adjusted in any direction. Tight timings matter more on an Athlon XP than any other chip; timings don't much matter at all on the A64/FX/P4.
1) What you're OCing
2) Cooling setup (Stock aka "what came with it" often won't allow much headroom)
3) Other components (It's one big system)
4) Electrical modifications (very advanced)
Once you know these, there's generally some max speed you can achieve, and it's a matter of "simply" finding it. This takes experience with the parts and/or software to do in a reasonable amount of time; you might substitute a lot of reading on the Internet for hands-on experience if you want to do a lot of research before buying stuff.
Final notes... The easiest component to OC is the video card. You can do it from within Windows. And be careful, but not fearful... very rarely does anything break while you're trying incremental OCs.
Oh, as for literature on overclocking in general, I'm not aware of anywhere towards which to point you. Usually you try to look up someone's experience on the same project as yours.
You might get extremely lucky and find someone selling an "ES" chip which is an engineering sample that is unlocked but they are rarer than hen's teeth but as to the OC darlings of the Intel crowd you'll find that the 2.4C and the 2.6C are the ones to look into, they get very good OC's with the proper board and ram, I'd suggest an Abit IC7-G MaxII board or the DFI Lan Party 875Pro B as both of these boards offer pretty decent OC options.
Since you're basically stuck boosting the FSB on an Intel rig you will want to look into the fastest DDR you can find (unless you decide to go the LGA 775 route and those boards use DDR2 mainly) which is PC4400 at the outside, Corsair and I believe OCZ sell lower latency versions now that are capable of 2.5-4-4-7or8 which really don't make much difference in all reality but can give you a marginal boost in bandwidth.
The overall advice that Thrax imparted upon you about the stratagey of OC'ing does apply though, follow his advice, shoot for the middle ground of the range that your particular combo is capable of to start with and go from there.
I personally set my ram to 2.8v and just leave it there and lock the AGP/PCI bus at 66/33 and turn the juice up on the vCORE by .1v when I begin OC'ing, I will usually go up 5-10mhz on the FSB at a time, 10 the first time and 5 the second and third until it begins to freak loading windows or hang altogether. Then I bump the vCORe up another .05v and continue on but you might want to make sure you've got killer cooling before trying that method as a stock cooler might fail you really fast.
I think if you ask 50 different people for recomendations on how to OC you'll get 50 different answers, some people take a conservative approach, some go balls out and some take the middle ground, I prefer the latter.
Good luck on you endeavors and may you never fry your CPU.
CPU multiplier, CPU Vcore voltage, CPU frequency stepless control, AGP/PCI Freq. control.
Which of these adjustments would be involved when running Intel as opposed to AMD if any.
What literature should I read to address my obvious ignorance about all of this?
It would be better to have a general understanding before rolling off blind questions.
for reference I am attempting this with
P4 2.4c prescott 800mhz
ASRock pv488 - VIA pt880
2*256 kingmax 3200
aopen fx5500 128mb
A P4C is not a Presscott...that would be a P4E and as far as I know you won't be finding very many 2.4E's out there, I've only seen them offered by one site and that was like late last year/early this year, I'm not certain which.
With the PC3200 you have you'll most likely have to use a divider to get a decent OC because value ram usually doesn't like being pushed very hard, at 250FSB with a 5/4 divider the ram will be at it's default speed of 200mhz, leave the cas settings at "by SPD" to begin with and set the divider at 5/4 and begin bumping the FSB up a bit at a time, I won't try to tell you what to expect with that particular chipset as it's still a dark horse to me.
I have the 2.4C as well, I'm hitting 270fsb (when my pc works) and it's very stable at that.
For cooling my Northwoods, I use either the SLK947-U or SLK948-U heatsinks made by Thermalright along with either the Thermaltake SmartFan2 or the Delta FFB0812SHE focused flow fan on a Vantec Nexxus fan controller, so that I can control the fan speeds. Even the Northwood procs emit a lot of heat and are actually a bit harder to cool than AMD procs, but it's not unmanageable though.
As for max vcore voltage on Northwoods, even with good cooling I try to keep it at 1.65v or less; anything much over than that and you stand a good chance of your Northwood suffering from SNDS (sudden Northwood Death Syndrome) where it just dies on you for no reason(other than just too much vcore). This has happened with very well cooled procs too, so it's really just heat related. I will say though that both my 2.4C and my 2.6C could both get to 3000 MHz with stock vcore.
There is a bunch of great overclocking advice here in this thread so when you get the urge to overclock, reread these posts and give it a try.
mudd
row precharge time = 2
Ras pulse width = 6
Ras to Cas delay = 2
thats the lowest my mobo let me go
and my cas latency is at 1.5 its all working awesome. I overclocked my cpu like a year ago but i didnt see a peromance increase so ti wasnt worth it and same with video card there wasnt any like epromance incrase so i dont bother.
go into your bios
then go to like where it says ur cpu speed and ****
go to front side bus for cpu
and bring it up like ummm 5 or something the higher kind fof ram u have also determines how much u can overclockin like pc-3200 will allow u to overclock more then pc-2100
now to find out what ur speed is after u over clock u take the multiplier and MULTIPLY it by the FSB
Now go test it out and see if its stable i tend not to use stablity programs and just use my comp as normal and see if any crashes occur
NOW if they do then your gonna either want to down clock it a ltitel and see if it works then OR raise ur V core my the smallest increment u can on mine its .050
now Vcore is what raises temps not raising the FSB so keep an eye on those temps and dont overclock to high or it wont post and u gotta clear CMOS.
now as for cas latency put it to 2 if thats lowest it can go mine can go down to 1.5 and keep stable but u want it as low as it can go but keep it stable. and u want
Send a message via MSN to Bone
Re: Share some knowledge with the rookies
well ive done my memory timings i have em at lowest and its all stable and i havent had to increase voltage which is awesome its 2-6-2 or however u say it like
row precharge time = lowest
Ras pulse width = lowest UNLESS YOU HAVE AN NFORCE 2!!
Ras to Cas dela = lowest
now go see if its all stable if not change ut cas latency. HAVE FUN OVERCLOCKING!!!! and keep an eye on those temps and you know any smoke pouring out of your machine :-P jk
it does not hurt memory. what i said bout memory is like if u do memory timings like i said and its like not stable like the computer then loosen em up meaning like if u have it at 2 then make it 2.5 etc. and what divider do u speak of? and yeah im pretty sure thats fsb then the best way to check is to raise it and then go get zpu-z go do search on google and download it and it will tell u what ur current Mhz on cpu is so u cant ell if its overclocked :-P
My MB manuals explain nothing, they're horrible and the website dos'nt help much either.
CPU freq or FSB at 233
multiplier obviously locked at 12
spread spectrum (??) disabled (other option enabled)
I have my sticks of ddr400 set to ddr333 on fsb to act as the divider.
Flexibilty option? no idea what that is... on or off?
Latency on 2.5 (2.0 or 3.0 are choices)
I have the dram voltage on normal (other option is high)
AGP voltage on high (other is normal)
dram command rate? (either 1t command or 2t command)
not able to change vcore (running at approx 1.54)
any suggestions besides an intel chipset?
Maybe I can OC this thing, anybody know how to oc an sx33 cpu with 16megs memory? maybe i should upgrade to the dx2-66 thats a screamer!
Thrax, your scaring me with the "drastic leap" what would be safe? When I OC ddr400 should I change the mb settings to 166mhz instead of 200? Would'nt that act like a divider? And could you explain the divider thing to me as well? Is it to seperate cpu and memory when oc'ing? how does it work?
My new memory is :
Manufacturer: Geil
Speed: DDR400(PC3200)
Type: 184 Pin DDR SDRAM
Error Checking: Non-ECC
Registered/Unbuffered: Unbuffered
Cas Latency: 2.5 7-4-4
Support Voltage: 2.55V-2.95V
Bandwidth: 3.2GB/s
Organization: two 32M x 64 -Bit
Special Features: Optimized SPD for Dual Channel DDR motherboards
Warranty: Lifetime