Overclocking question

BabyPCMR · August 10, 2018

So i set the multiplier for my cpu to 48, and in the task manager it's telling me 4.79 ghz is the max max speed im reaching. However, in CPU-Z and HWMonitor, both updated to latest versions, it's saying im reaching speeds of 4.95 Ghz. Are on of these inaccurate? Side note: task manager looks like it literally caps the number at 4.79, it won't go above that at all at any point. Not sure if that's important or not.

DildorTheDecent · August 10, 2018

12 minutes ago, BabyPCMR said:

So i set the multiplier for my cpu to 48, and in the task manager it's telling me 4.79 ghz is the max max speed im reaching. However, in CPU-Z and HWMonitor, both updated to latest versions, it's saying im reaching speeds of 4.95 Ghz. Are on of these inaccurate? Side note: task manager looks like it literally caps the number at 4.79, it won't go above that at all at any point. Not sure if that's important or not.

Make sure you haven't applied any BCLK.

What have you done in the BIOS exactly?

AngryBeaver · August 10, 2018

18 minutes ago, BabyPCMR said:

So i set the multiplier for my cpu to 48, and in the task manager it's telling me 4.79 ghz is the max max speed im reaching. However, in CPU-Z and HWMonitor, both updated to latest versions, it's saying im reaching speeds of 4.95 Ghz. Are on of these inaccurate? Side note: task manager looks like it literally caps the number at 4.79, it won't go above that at all at any point. Not sure if that's important or not.

Depending on your Motherboard some have a sorta floating BLCK. So in general the BLCK should be 100mhz so with your multiplier that would put you at 4.8ghz, but when enabled in the bios it allows windows to make slight increase and decreases to the BLCK... so that can result in clocks being under or over the expected values. Some times it runs your BLCK at 98 others it might run it at 103.

So 4704mhz to 4944mhz. You can disable that feature in the bios then this issue won't occur.

This isn't a bad thing, it use to be an issue because changes to BCLK also affect the FCLK. That problem has gotten a lot better though as newer bios revisions fixed most of those issues back with the 6000 series.