• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

No cpu clock change with FSB change - why?

craftech

Senior member
Give us a CPUz screenshot of the upped FSB overclock. I see three possible things going on here.

#1. The FSB isn't really changing.
#2. The Program your using isn't telling you the true clockspeed.
#3. CPU multiplier is being lowered.
 
Give us a CPUz screenshot of the upped FSB overclock. I see three possible things going on here.

#1. The FSB isn't really changing.
#2. The Program your using isn't telling you the true clockspeed.
#3. CPU multiplier is being lowered.

I can put up a screenshot of CPUz, but what it is showing is that the FSB isn't really changing. Even in the BIOS, when I change the FSB it stays at what I put it, but the BIOS PC Health status still shows the same clock speed no matter what the FSB setting says.

The multiplier (in CPUz) ranges from 6 (from throttling at idle) to 13 (under load) so it hasn't been lowered.

John

EDIT: The Foxconn Windows based Utility (Fox One) allows me to overclock the CPU, but there appears to be no independent way to lower the resulting increase in Memory frequency. They are tied together. No adjustment in Fox One for memory to FSB ratio. It is 2:1 so increasing the FSB in Fox One from 200 to 230 results in a memory frequency of 920 with no apparent way to lower it to 800.
 
Last edited:
Check your motherboard manual if there is a jumper for a "safe" setting.

I had an issue with an Athlon XP2200 recently that stayed stuck at 100 mhz fsb. There was a jumper on the mobo that was set to safe, meaning the FSB was set to 100 mhz no matter what the bios setting was.

There is a chance this is also the case for you.

Reset the bios to something safe before changing that jumper setting to insure you do not try a huge overclock in one go.
 
Back
Top