CPU multiplier dropped significantly after wakeup from standby

  • Thread starter Thread starter mofliwsb
  • Start date Start date
M

mofliwsb

Hi,

My system has a AMD Athlon 64 X2 4800+ CPU with ECS NFORCE6M-A mother
board.
It has Windows XP sp2 installed.

I got a weird problem that when I put my system into standby then wake
the system up,
the CPU multiplier drops from 12.5 to 5, the bus speed does not change
(which is 200.9M).

I did a search online, and found out that the "cool n quiet" feature
may cause this problem.
However, after I disable the "cool n quiet" feature in BIOS, the
problem still exists.

Can anyone help me figure out what causes this problem exactly?
Thanks a lot!

Sam
 
Hi,

My system has a AMD Athlon 64 X2 4800+ CPU with ECS NFORCE6M-A mother
board.
It has Windows XP sp2 installed.

I got a weird problem that when I put my system into standby then wake
the system up,
the CPU multiplier drops from 12.5 to 5, the bus speed does not change
(which is 200.9M).

I did a search online, and found out that the "cool n quiet" feature
may cause this problem.
However, after I disable the "cool n quiet" feature in BIOS, the
problem still exists.

Can anyone help me figure out what causes this problem exactly?
Thanks a lot!

Sam
Click to expand...

I don't know the answer to this, but consider the instructions
you had to follow, to get CNQ to work in the first place.

1) BIOS - Advanced:CPU Configuration:Cool N Quiet: [Enabled]
2) BIOS - Power Menu, ACPI 2.0 Support [Enabled]
3) Windows - Control Panels - in mine, "Power Options", set to
"Minimal Power Management"
4) Install CNQ driver. Optionally, install some utility for
viewing the current setting for FID and VID (core freq and
Vcore voltage setting).

Now, one of the enablers of changing the multiplier, is ACPI.
ACPI affords a handle that the ACPI subsystem in Windows can
use to adjust the core speed. The CNQ driver is going to be
using that, to change FID and VID on the fly.

But there is another possibility. The Windows Power Management
scheme has a say in it as well. If it was still set to
"Minimal Power Management", perhaps the core speed was
set by that policy, or by a bug (return from standby bug)
in forgetting to bump the speed up to "normal".

You could try changing the power policy, from
"Minimal Power Management" to "Always On". Maybe
that would fix it.

I wouldn't try disabling ACPI in the BIOS, because that could
cause Windows a bit of indigestion.

If you run out of things to try, programs like RMClock or
CrystalCPUID, may be able to change the multiplier while
you are in Windows. But this is intrusive, in the sense that
you need the program to set things right.

http://cpu.rightmark.org/pic/rmclock5.png
http://cpu.rightmark.org/download.shtml (new version RMClock 2.30.1)
http://cpu.rightmark.org/products/rmclock.shtml (more info)

I wasn't able to find anything else relevant - the BIOS notes
don't mention a problem matching your description.

Paul
 
Back
Top