View Single Post
  #4  
Old November 26th 11, 07:14 AM posted to alt.comp.hardware.overclocking.amd
Yousuf Khan[_2_]
external usenet poster
 
Posts: 1,296
Default Using the AMD Overdrive utility

On 26/11/2011 12:21 AM, Paul wrote:
Well, I can't say what will happen in your case, but when you use
things like CNQ, they use ACPI schema, and the multipler values
for idle and full blast, are stored in there. The question then is,
depending on how you're overclocking, does CNQ do the right thing,
or does it use the defaults for the processor ?


Well, I'm using the AOD Windows utility to do the overclocking, and it
probably takes care of bypassing ACPI limits, so I do see the top speeds
changing properly. I verify it with a couple of other utilities like
Core Temp and CPU-Z.

I don't know if I were to use the BIOS to overclock it instead, would I
run into this problem? I may try overclocking through the BIOS at some
point and I'll let you know. But I somehow doubt I'd have any such
problems in BIOS either, as it is BIOS own settings that let you
overclock, and ACPI is part of BIOS, so the BIOS can probably modify
ACPI tables properly.

One reason I used that tool, is it includes an "Idle Loop" task.
Back when I was using Win2K, I bought a one year subscription to
Kaspersky. Several months after installing it, I happened to make
a power measurement on my CPU (ammeter on +12V), and noticed the
consumption was too high. What was happening, is Kaspersky eliminated
the idle loop in Win2K, as some sort of protection. It meant, when the
system was idle, it wasn't using HALT instructions (an interrupt, like the
clock tick interrupt, brings the CPU out of HALT). So the processor would
wait for the next scheduled task, while sitting in some kind of loop
instead.

Ticking the box in RMClock for that, causes RMClock to run it's own
low priority task (one per core). When the system is idle, that task
runs, and the RightMark designers put HALT in their version. Basically,
it allowed overriding what the Kaspersky designers did. And it returned
my idle performance, back to where it belonged. Otherwise, I might
have not had occasion to use it that much.


I don't think it's absolute necessary in my case, I'm not using
Kaspersky, and the C1E state is what takes over for the HALT
instruction. I find that when idling, the processor is throttled to
800MHz and its temperature is in the sub-30C range, usually around 26C.
The idle speed is the same even when overclocked, so it stays just as
cool as when it isn't overclocked. Highest temperatures when overclocked
has been 48C, but only 32C when at stock settings.


Yousuf Khan