• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

weirdness

S

smd86

n00b
Joined
Dec 10, 2007
Messages
11
programs are showing different clock speeds for my Q9450. As you can see realtemp and CPUZ show a clock speed of 2325.3mhz with a multiplier of x6.0. on the other hand BIOS, 3dmark 06 and windows system tools app shows 3.1ghz which is what the processor should read since thats what its clocked at in BIOS. The multiplier should be showing up as x8.0. Every once in awhile CPUZ will flash the actually clock speed of 3.1ghz then quickly go back down to 2325.3mhz. Coretemp shows the correct clock speeds, too.

anyone know if this is just an error with CPUZ and real temp? BIOS shows the correct readings like I said.


I'm on an EVGA 790i ultra mobo btw.


roarcm5.jpg
 
nevermind i found the problem. there was a setting in bios that down clocked the cpu when it is in an idle state. that explains why it would switch between 3.1ghz and 2.3ghz every once in awhile. please delete or close this thread mods.



thanks:D
 
It was likely C1E that you had enabled in the bios in case anyone else notices this issue and wants to change it.

Dropping the multiplier down to 6.0 when idle doesn't save 1 watt of power for me when measured with a Kill-a-Watt meter. No power savings also means that enabling C1E doesn't make my CPU run any cooler either.

Most ASUS motherboards don't lower the core voltage when you're overclocking so the savings are basically zilch. On my board, C1E is only good in theory.

Aren't you glad that CPU-Z and RealTemp told you about what was really going on with your MHz? Looks like your core0 sensor might be stuck.
 
You must log in or register to reply here.
Back
Top