How to lower processor frequency?

  • Thread starter Thread starter Stegozor
  • Start date Start date
S

Stegozor

Hi,

I need to lower my computer's processor frequency, 3 or 4 hundred
megahertz less would be OK. The bios offers two choices, and the lowest
frequency is still too high. A freeware or open source software able to
control the processor speed is what I need. For Linux, it seems that
cpudyn does that, but I couldn't find anything similar for Windows XP.

Could someone provide a link ?

TIA.

PS: My µp: AMD Athlon XP 2000+ running on 1.2 Ghz (bios setting), my
motherboard: Asus A7V333

Crosspost on follow-up to (fu2)
 
Hi,

I need to lower my computer's processor frequency, 3 or 4 hundred
megahertz less would be OK. The bios offers two choices, and the lowest
frequency is still too high. A freeware or open source software able to
control the processor speed is what I need. For Linux, it seems that
cpudyn does that, but I couldn't find anything similar for Windows XP.

Could someone provide a link ?

TIA.

so, what multipliers and clock speeds does it have?
 
Hi,

I need to lower my computer's processor frequency, 3 or 4 hundred
megahertz less would be OK. The bios offers two choices, and the lowest
frequency is still too high. A freeware or open source software able to
control the processor speed is what I need. For Linux, it seems that
cpudyn does that, but I couldn't find anything similar for Windows XP.

Could someone provide a link ?

TIA.

PS: My µp: AMD Athlon XP 2000+ running on 1.2 Ghz (bios setting), my
motherboard: Asus A7V333
I believe that wcpuid will do it for windows.
 
Hi,

I need to lower my computer's processor frequency, 3 or 4 hundred
megahertz less would be OK. The bios offers two choices, and the lowest
frequency is still too high. A freeware or open source software able to
control the processor speed is what I need. For Linux, it seems that
cpudyn does that, but I couldn't find anything similar for Windows XP.

Could someone provide a link ?

TIA.

PS: My µp: AMD Athlon XP 2000+ running on 1.2 Ghz (bios setting), my
motherboard: Asus A7V333

Your CPU has 12X multiplier and default 133MHz FSB. Perhaps
obvious to you but to other readers it saves time to mention
it.

So far you've only reduced the FSB to 100, presumably.
I write presumably because at the FSB reduction but default
multiplier, it should've been at 1.25GHz, which rounded off
would be 1.3GHz, not 1.2GHz.


Is your CPU multiplier-locked such that when you change the
multiplier in the bios, that change is ignored? If not,
just lower the multipler from 12.5X to (whatever you want).
A7V333 does support this. If you plan on leaving it
runnning so slow you could probably use the jumpers above
the CPU socket to significantly lower the voltage too,
which'll cut the heat production and power consumption by a
lot. With that specific board you should not have to
manipulate the CPU voltage bridges at all, IIRC.

If the multipler is locked the remaining solution is
wire-wrapping pins or using conductive paint to connect
bridges on the CPU, or using a low-voltage (like a battery)
to burn through the bridges. Google for "changing Athlon XP
multiplier paint wire" (or search for slightly different
phrase without "paint" or "wire" together) for more info on
doing that.

You dont' mention the purpose of this nor whether you want
it to be permanent so you'll have to take it from there.
 
f/fgeorge said:
I believe that wcpuid will do it for windows.

Unfortunately it seems that wcpuid only shows information but does not
allow to modify the configuration. I'll keep it anyway, it's pretty
interesting, thanks for your suggestion.
 
kony said:
Your CPU has 12X multiplier and default 133MHz FSB. Perhaps
obvious to you but to other readers it saves time to mention
it.

Er, I'm rather an eternal newbie as for hardware issues. Sorry for not
having mentioned this information.
So far you've only reduced the FSB to 100, presumably.
I write presumably because at the FSB reduction but default
multiplier, it should've been at 1.25GHz, which rounded off
would be 1.3GHz, not 1.2GHz.

Indeed, you're right. wcpuid shows 1261,23 Mhz. The purpose of this BIOS
setting was to prevent Boinc/seti@home from overheating the system and
shutting it down repeatedly, and that just works fine. As I mentioned
below, the purpose of my current question is slightly different.
Is your CPU multiplier-locked such that when you change the
multiplier in the bios, that change is ignored? If not,
just lower the multipler from 12.5X to (whatever you want).
A7V333 does support this. If you plan on leaving it

I just did that: after saving changes and exiting the bios, the screen
enters sleep mode, and I have to turn off and then on the computer to
restart, even the reset button doesn't help.
(Changes I tried were 8.5; 9.0 and 1.0X, I didn't modify anything else
as I didn't know what to do)
runnning so slow you could probably use the jumpers above
the CPU socket to significantly lower the voltage too,
which'll cut the heat production and power consumption by a
lot. With that specific board you should not have to
manipulate the CPU voltage bridges at all, IIRC.

Oops, jumpers are not good news to me. I'd like these changes to be
modified at will, if possible. And I'd rather avoid advanced manipulation.
You dont' mention the purpose of this nor whether you want
it to be permanent so you'll have to take it from there.

The reason why I didn't mention the purpose is probably because it's
almost silly: a friend wants to play a game with me on a LAN, and I'd
like to lower my computer below the minimum requirements in order to say
him "oh sh**, what a pity, I just can't run Dungeon Lords". I admit
that's not really fair :)
Lowering CPU speed also helps for some old games, and I'm curious, too.
 
Er, I'm rather an eternal newbie as for hardware issues. Sorry for not
having mentioned this information.

Well I may be wrong too, on second thought it may have 12.5X
multiplier, not 12X... but the point was to determine what
you'd been changing to achieve the 1.2GHz, since there are
two variables, FSB & multiplier.

Indeed, you're right. wcpuid shows 1261,23 Mhz. The purpose of this BIOS
setting was to prevent Boinc/seti@home from overheating the system and
shutting it down repeatedly, and that just works fine. As I mentioned
below, the purpose of my current question is slightly different.

If the system is meant to perform good at such tasks, the
best (overall system power used) vs performance would be to
keep the CPU running nearer it's spec'd speed- remembering
that the CPU power is only a fraction of the total system
powrer used. Essentially it would seem you need a better
heatsink and chassis cooling... but to keep costs low you
might just do some stability testing of lower voltages.

IN other words, cutting the voltage down some is the most
significant reduction in power & temps, then lower the
clockspeed as-needed to keep stability at the lower CPU
speed. For example, if the CPU started out using 1.65V, try
lowering it to 1.4V-1.5V, and the highest CPU frequency that
remains stable (in testing with that app, SETI or F@H or
Prime95, etc).

In general, you will get better performance from leaving the
FSB as high as possible, a sync'd memory bus, and ONLY
lowering the muliplier to achive the target CPU frequency.


I just did that: after saving changes and exiting the bios, the screen
enters sleep mode, and I have to turn off and then on the computer to
restart, even the reset button doesn't help.
(Changes I tried were 8.5; 9.0 and 1.0X, I didn't modify anything else
as I didn't know what to do)

I'd try others first, a smaller change like 10X. If you
take the numbers from your CPU's label, you may be able to
Google search for info on whether it is muliplier locked or
not. Some older CPUs did need their bridges connected to
allow changing the mutiplier, but I dont' recall which
specific models/families did.

Oops, jumpers are not good news to me. I'd like these changes to be
modified at will, if possible. And I'd rather avoid advanced manipulation.


What does "modified at will" mean? If you have the will to
change jumpers, you do, or don't. Advanced manipulation is
exactly what you're doing when you choose to not run at
stock speed. Lowering only the clock FSB speed is the worst
possible way to underclock a CPU because it has the least
impact on heat and the worst impact on performance.

Essentially, your (power & heat) vs (performance) is now
significantly lower than it was previously.

The reason why I didn't mention the purpose is probably because it's
almost silly: a friend wants to play a game with me on a LAN, and I'd
like to lower my computer below the minimum requirements in order to say
him "oh sh**, what a pity, I just can't run Dungeon Lords". I admit
that's not really fair :)
Lowering CPU speed also helps for some old games, and I'm curious, too.

It's your system, if you can justify (something) that's your
call to make. Getting the CPU speed lower than 1.25GHz will
require lowering the mulitplier. As mentioned above you
need to determine exactly what CPU you have by the markings
on it's label- which when input into a search engine will
provide the needed information on it's limitations- whether
multiplier locked or whether the bridges need painted (or
other wire mods). The same guides to overclocking by these
methods still apply, you'd simply choose a lower mutipler
based on the info in the guides - which some overclockers do
so that they can increase the FSB more, while you would
instead, not be raising the FSB.
 
Indeed, you're right. wcpuid shows 1261,23 Mhz. The purpose of this BIOS
setting was to prevent Boinc/seti@home from overheating the system and
shutting it down repeatedly, and that just works fine. As I mentioned
below, the purpose of my current question is slightly different.

i'd suggest that you forget that, then learn how you went wrong when you
put the heatsink on your processor. running seti@home should not cause
heat related shutdowns. so, what are your idle and full load temps? if
you have an app that shuts the system down during overheat, do you have it
set with too low a trigger? did you use the original tape that came with
a retail heatsink, be aware that most formulations include a rather large
percentage of paraffin wax, which will in time leak out from under the
sink.
the speed of the processor may not be the problem, under full load it
should reach then maintain a temperature, if the cooling is innadequate
you will need to address that problem, not the speed. a can of air to
blow dust out, better thermal interface, better cpu fan(which may be
failing if it's old), better case fans, and don't forget to blow out the
power supply, bacause it may not be a cpu heat issue at all.
 
jim said:
i'd suggest that you forget that, then learn how you went wrong when
you put the heatsink on your processor. running seti@home should not

Oh, everything is possible, as almost all parts of my computer are gifts
or old devices I got from friends who were upgrading their machines.
cause heat related shutdowns. so, what are your idle and full load

At 1668 Mhz, here's what SpeedFan 4.24 tells :
idle : full load : (100%, E@h)

Fan 1: 3013 RPM Temp 1: 33 °C Fan 1: 3027 RPM Temp 1: 33 °C
Fan 2: 3571 RPM Temp 2: 68 °C Fan 2: 3629 RPM Temp 2: 82 °C
Fan 3: 0 RPM Temp 3: 16 °C Fan 3: 0 RPM Temp 3: 16 °C
Temp 4: 65 °C (no 3rd Fan) Temp 4: 84 °C
Temp: 16 °C Temp: 15 °C
Temp: 68 °C Temp: 82 °C

temps? if you have an app that shuts the system down during overheat,
do you have it set with too low a trigger? did you use the original

The Bios shuts down the computer if the temperature is too high. In
fact, beep codes and vocal POST messages indicated temperature problems.
As for the overheat trigger value, I'm just keeping default options, the
motherboard (Asus A7V333) manages it automatically. Prudence...
tape that came with a retail heatsink, be aware that most formulations
include a rather large percentage of paraffin wax, which will in time
leak out from under the sink.
the speed of the processor may not be the problem, under full load
it should reach then maintain a temperature, if the cooling is
innadequate you will need to address that problem, not the speed. a

I guess you're right. But I simply chose in the Bios to lower the
frequency to 1.26 Mhz from 1.6 Mhz (during a very hot summer here, in
France), and never had a problem after that.
Seti@home is still running, now managed by Boinc, and shares CPU time
with Einstein@home.
Also, a question: I've heard that cooling a CPU would lengthen its "life
expectation", is that true?
 
Also, a question: I've heard that cooling a CPU would lengthen its "life
expectation", is that true?

absolutely, if it's kept at the lower part of the operating temperature
range it could survive quite long. a really good fan would do nicely, i'm
using an 80mm vantec thermoflow mounted to suck, it changes speed with
temperature, and has a response range that's not too bad for a processor,
top speed at about 50c.

from the list i can see the case temp is relatively stable, though you
could probably do with a little more airflow, the somewhat high case temp
may be what's allowing the cpu temp to rise, but it might not, 33 ain't
that bad. in a lot of cases the fans blow in from front and out the back,
your case may be the kind that performs best like that, or worst, the case
i'm using now has two fans blowing in from the back, none in front, i get
the best temps that way.
 
Back
Top