a8v and 3500+ multiplier problems

Hi,

I have a problem with my new amd64 3500+ and asus a8v deluxe motherboard.
In the BIOS it detects the cpu as 2200Mhz, which is correct, but when I load
windows, it says the chip is running at 1Ghz.
I've run cpu-z, and instead of this
http://www.xbitlabs.com/images/cpu/a...800/cpuz-2.png
I get Multiplier = x5, Core Speed = 1000Mhz.

Does anyone know how to fix this? I dont have any multiplier options in the
BIOS, as I assume it is locked.

Thanks,
Matt Hook

In article , "Matt Hook"
wrote:

Hi,

I have a problem with my new amd64 3500+ and asus a8v deluxe motherboard.
In the BIOS it detects the cpu as 2200Mhz, which is correct, but when I load
windows, it says the chip is running at 1Ghz.
I've run cpu-z, and instead of this
http://www.xbitlabs.com/images/cpu/a...800/cpuz-2.png
I get Multiplier = x5, Core Speed = 1000Mhz.

Does anyone know how to fix this? I dont have any multiplier options in the
BIOS, as I assume it is locked.

Thanks,
Matt Hook

Is this something to do with "Cool N¹ Quiet" being enabled in
the BIOS ? The multiplier is dynamic and is adjusted according
to computing load by a driver you install in the OS. I think
disabling this should stop it.

Paul

"Paul" wrote in message
...
In article , "Matt Hook"
wrote:

Hi,

I have a problem with my new amd64 3500+ and asus a8v deluxe
motherboard.
In the BIOS it detects the cpu as 2200Mhz, which is correct, but when I
load
windows, it says the chip is running at 1Ghz.
I've run cpu-z, and instead of this
http://www.xbitlabs.com/images/cpu/a...800/cpuz-2.png
I get Multiplier = x5, Core Speed = 1000Mhz.

Does anyone know how to fix this? I dont have any multiplier options in
the
BIOS, as I assume it is locked.

Thanks,
Matt Hook

Is this something to do with "Cool N¹ Quiet" being enabled in
the BIOS ? The multiplier is dynamic and is adjusted according
to computing load by a driver you install in the OS. I think
disabling this should stop it.

Paul
aha, it could well be. I ran some benchmarks, and it came out at the right
speed, so it looks like it is ok after all.
I'll try disabling that to see whether if fixes the detection, it'll be
interesting to know, thanks.

Matt