AMD 4000+ Brisbane Overclock

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
At an idle state you CPU multiplier will be lower like 5 and at 10.5 during full load. This is AMDs cool n quiet feature that they have conveniently for you to save on your energy bill.
Dont worry about anything. As long as your CPU jumps back up to 10.5 during full load you are good!
Also you can always disable it... I dont see why you would because it only does it at idle. Makes no difference performance wise.
 
Ok... Run prime95 test (doesn't matter which test put use blend for this purpose). Whilst prime is running do you still run into this same problem at 66 or above??

It just really still sounds like the cool n quite kicking in. Maybe disable that feature in the bios and see if it still does it. Cool n quiet is designed to whenever windows issues an idle command to drop down to a lower multiplier and also drop voltages in some cases. So that's what this might be considering it's happening on both computers.

Bottom line if it's happening during prime stress test than it's definitely a problem. Unless for some weird reason you have a feature that whenever the temps reach a certain degree it reduces multiplier conciquently reduceing the frequency and in turn reducing the heat.

I don't know. All this is to me is speculation and my tech assuming side. I have done no research into the matter so cant give you any very "technical" advice. All I can say so far is to do what I've said and then we'll work from there. Hopefully I'm not the only techru that will respond to this thread as there are a lot of people on here that know more than I do. The question is where are they?
 
It does it whenever the temperature reaches 66C. I have tried with the hairdryer too. Cool&Quiet is disabled.

We are talking two computers, both with same motherboard (MSI K9N-Neo-V3) and two different CPUs (X2 4000+ and X2 6000+). Settings to default, no messing about in the BIOS.

So my guesses are:

(1) rogue driver in Windows - I have lately installed (and de-installed) ATITool, NVidia tune, speedfan, cpu-z, gpu, riva tuner, ati catalyst - any of these can be responsible. I have de-installed whatever I could.
(2) In-built CPU function to protect itself when it reaches 66C
(3) Nvidia chipset 560 function
(4) Motherboard/BIOS function (I have left a question with MSI)

 
Not sure why some guys here say 3.0GHz should be easy to hit, my 4000+ Brisbane barely hit 2.8GHz on a nV570 SLI board, now clocked down to 2.65 on a AMD 690G board... I am an experienced OC'er too so you gotta realize that some chipsare better than others, that's for sure!