04-10-2015 01:30 AM - last edited 3 weeks ago by ROGBot
04-10-2015 01:59 AM
04-10-2015 02:17 AM
elesde wrote:
Just to let you know the same thing happens on my ASUS board. Granted it is not ROG and an AMD model but the base clock behaves in the same manner no matter what i do in BIOS.
At this point I am not even sure if it is the BCLK that is unstable or just the readout in Windows.
As for the PCIe frequency, afaik that is a separate clock not coupled to the BCLK. The bandwidth displayed in HWiNFIO is fine btw., it idles at PCIe x16@1.1 speeds and clocks up to x16@2.0 under load.
04-10-2015 02:58 AM
04-10-2015 03:23 AM
elesde wrote:
Oh yea looks like the BCLK & PCIe frequencies are linked on socket 1155 😞 , last Intel CPU I overclocked was an i7 920^^
By looking at the specs of your motherboard I would seriously consider replacing it with something a little more "high end" especially in the VRM department when overclocking.
The ROG Maximus might be a bit too high priced but there surely are other nice boards out there in the 100-150$ range.
04-10-2015 02:55 PM
04-10-2015 04:33 PM
unclewebb wrote:
HWiNFO is not accurate when reporting the BCLK. The variation it shows is usually not happening. The BCLK on most motherboards is very stable these days and if you were monitoring with an oscilloscope, you wouldn't see even +/- 0.001 MHz variation. Varying BCLK is mostly monitoring error that you are seeing. Try using CPU-Z 1.72 and RealTemp 3.70.
The monitoring timers within Intel CPUs are a shared resource. This means that if 2 different programs are running at the same time and trying to use the same timers, they can interfere with each other. For best results, only use 1 monitoring program at a time.
If your computer has a BSOD when lightly loaded or idle, that usually means the CPU is not getting enough voltage. Are you using offset voltage? Are you using the core C States or the package C States or both.
If you need to know what C States your CPU is using then try using this.
RealTemp T|I Edition
https://www.sendspace.com/file/55yvry
04-10-2015 05:59 PM
04-10-2015 06:46 PM
unclewebb wrote:
Are you sure that the AUTO setting in the bios is disabling all of your C States? You can use ThrottleStop to look at your C States. Make sure ThrottleStop shows all 0.0 if you want these all disabled. Most monitoring programs ignore if C1E is enabled or disabled. If all of your C States are disabled, the multiplier reported by ThrottleStop should be very steady when the CPU is idle.
RealTemp and ThrottleStop use a different method and a different timer to determine the BCLK. Every time you click on the BCLK button in ThrottleStop, it will measure your BCLK. I am curious. Does ThrottleStop show these BCLK changes? You have to keep clicking on the BCLK button. It only updates when you manually click on this button.
On most motherboards, ThrottleStop rarely reports a change of more than +/- 0.001 MHz.
If you are still having problems, there is a way to change what timers Windows uses. Windows has a few bugs when trying to measure time accurately.
Here is a program to test your Windows timers.
WinTimerTester
https://www.sendspace.com/file/xadvhe
Let the program run for about 100 seconds. It compares two different Windows timers and over the long run, they should both be showing the same thing.
I switched my Windows timer to a fixed frequency of 14.31818 MHz. You might get better results with this timer.
04-10-2015 07:55 PM