• Overclocking, whats the bieffect?
    38 replies, posted
[QUOTE=bohb;32422489]Voltage is constant, amperage is not. When electrical devices draw more power (watts), the amperage goes up, not the voltage. Increasing or decreasing the voltage on a device not designed to do so will have catastrophic results. The easiest way to think about volts and amps is by using a water pipe. The voltage would be the diameter of the pipe, in this case 1.3". The Amperage would be the amount of water current flowing through the pipes. That's called vDroop, and it's not normal; But can't be eliminated entirely unless you want to spend some substantial coin in a massively overbuilt power regulation system. Any time you apply a load on a power source, the voltage is going to drop, but the rate at which it will drop is highly dependent on the power regulation (IE. if the power regulators (FETs in this case) on the motherboard or in the PSU are shit, then Vcc can fluctuate a bunch.) But just because Vcore drops under load doesn't mean it's drawing less power, it means the regulation system is having a hard time keeping up with demand.[/QUOTE]I know, I didn't say it was supposed to happen, just that it did
Thanks for the info. Any examples from personal experience (or otherwise) though would be great. I don't know whether to increment by .1 or .25 each time. I have a Phenom II X3 2.8 GHz and if the default voltage is 1.25 (I think) V, would it be a good idea to bump it up to 1.35 or 1.45 if overclocking to 3.2 or 3.4? Any suggestions would be great. I don't mind buying a new CPU soon anyways so it won't be the end of the world if it fries, but I'd rather wait before buying a X6 or quad right now. I just want a huger clock right now so my video encoding will be faster (for stuff like remotely streaming cogent to my iPhone, it uses the CPU apparently and I'd love less delays/higher rates.
[QUOTE=rodent-man;32427386]Thanks for the info. Any examples from personal experience (or otherwise) though would be great. I don't know whether to increment by .1 or .25 each time. I have a Phenom II X3 2.8 GHz and if the default voltage is 1.25 (I think) V, would it be a good idea to bump it up to 1.35 or 1.45 if overclocking to 3.2 or 3.4? Any suggestions would be great. I don't mind buying a new CPU soon anyways so it won't be the end of the world if it fries, but I'd rather wait before buying a X6 or quad right now. I just want a huger clock right now so my video encoding will be faster (for stuff like remotely streaming cogent to my iPhone, it uses the CPU apparently and I'd love less delays/higher rates.[/QUOTE] You shouldn't be changing the voltage until you reach instability, in my opinion. And since you're doing base clock overclocking (I think? it's an X3) you should be watching your RAM frequencies, since instability could be the RAM as well.
[QUOTE=Shadaez;32427463]You shouldn't be changing the voltage until you reach instability, in my opinion. And since you're doing base clock overclocking (I think? it's an X3) you should be watching your RAM frequencies, since instability could be the RAM as well.[/QUOTE] I actually overclOcked both in the past, haha. I OC'ed the RAM from 1333 (forgot the units that's in) to 1600 and the CPU cloak from 2.8 GHz to 3.2 GHz and remember getting BSOD's after some time in Battlefield Bad Company 2. It seems more like an issue of cheap RAM IMO but I think the first time I overclocked and the BSOD'S occured, it was just a CPU OC. The error was a string stuck in some loop, but I don't know if that's particular to the CPU or RAM, or if it's just a vague "Hey! You crashed!". Anyways, assuming it's not the RAM, would the increments in voltage I mentioned be a good start? What should I aim for as a target clock speed? A friend of mine told me AMD processors don't clock as well as Intel CPUs, so would 3.5 or 3.8 GHz be absurd? I'd imagine 3.3-3.4 is good enough for my needs. [editline]22nd September 2011[/editline] Sorry if that's all gibberish. I'm typing during a short break in a lecture.
you'll probably get up to 3.6 or so keep pushing the clock until you get some instability which is best tested by Prime95 w/large FFTs after that, push the voltage up .05V and retest, once it's stable push it some more; also, what is the model of your CPU? just google the maximum voltage for it and do NOT go past it
You were right about the 3.6. That was the general answer I could find online for the model (which is the 720 black edition). Thanks for the tip about the maximum voltage; that's the kind of knowledge I wanted to know. How long do you guys test test-clocks for before figuring it's "stable"?
1:Increase clock by 0.1 2:Check if stable If yes goto 1 Else increase voltage 1 step and goto 2.
[QUOTE=rodent-man;32432486]You were right about the 3.6. That was the general answer I could find online for the model (which is the 720 black edition). Thanks for the tip about the maximum voltage; that's the kind of knowledge I wanted to know. How long do you guys test test-clocks for before figuring it's "stable"?[/QUOTE] maybe an hour, once you get up to where it won't be stable anymore no matter what you do you want to test it for 10-12 hours and if any errors occur in any of the cores you should step it down about 50 MHz and then leave it
[QUOTE=rodent-man;32432486]You were right about the 3.6. That was the general answer I could find online for the model (which is the 720 black edition). Thanks for the tip about the maximum voltage; that's the kind of knowledge I wanted to know. How long do you guys test test-clocks for before figuring it's "stable"?[/QUOTE] A good resource is to check what voltages other people have had to use to get their overclock on the same processor type. This won't give you the exact amount you'll need as it varies from each one but it gives a rough idea of where to aim. As said look up the max voltage/temp of your processor, although most modern processors should have a shut off limit for the latter and might have safety procedures for the former (but don't risk that anyway).
Sorry, you need to Log In to post a reply to this thread.