Cpu-z 1.78.1 I've been using this software for a while, and I know it's free, but there seems to be a bug on the core speed ticks. It's never fully accurate. Let's say you overclock your CPU or you don't at all. You change your clock ratio to 40 and put your base clock to 100.00 MHz. Save your settings then windows loads up to the desktop. You launch CPU-Z and the core speed is not reflecting what you set in the bios. Even the bus speed is off. The ticks on both the core speed and bus speed drops below of what you set it to at longer intervals than the actual speed (this latest version is even worse than previous ones). Also when you first launch the program sometimes the core speed is much higher for a quick second, which is strange. What I think should happen is whatever you set it to in the bios CPU-Z should just auto detect the ratio and display that speed no matter what, because that's what it is in the bios. I'm not sure where it is getting the core speed from if not the bios. I've sent an email to the dev and never got a reply. Does anyone know why it's not accurate? Thanks
Hi. I usually keep it on 0 because when it's on 1 it never ticks and the default speed it sets is inaccurate.
Try HWiNFO and compare the results. http://www.guru3d.com/files-details/hwinfo64-download.html http://www.hwinfo.com/download64.html < X64 http://www.hwinfo.com/download32.html < X86 http://www.softpedia.com/get/System/System-Info/HWiNFO64.shtml < X64 http://www.softpedia.com/get/System/System-Info/HWiNFO.shtml < X86
Thanks. I've tried it out and it's a little better than CPU-Z; the ticks, though are similar with the core speed to CPU-Z, but better. I wonder what these programs are doing to get the system info. It's definitely not from the bios
Not sure if you know this but CPU multipliers are dynamic and will change as the CPU load increases and decreases.
Yes, but only if you don't change the default settings. If you set everything properly in the bios and set High performance on the Power Options window it will stay at the speed you set it to. However the multiplier isn't what's changing, it's the core speed which ticks below for longer intervals than what it's set at. With this new version the ticks are worse now.
HwInfo launches its own kernel mode driver so it can get info either from OS kernel itself, or from Win API, or from special ETW provider(s). But what do you call 'ticks'? If you did not disable Turbo mode then at performance power plan CPU can switch from P-state P0 (default maximum) to turbo state and back.
Okay, I've made a side by side comparison video of 1.78. and 1.74.0. Look at the core speed and bus speed areas. why is it ticking lower so much when I've set everything in the bios properly? It shouldn't even be ticking down. As you'll see the latest 1.78.1 is even worse: here is the video so you can see it in motion: http://www41.zippyshare.com/v/s3vLEExF/file.html
Is that all? Relax. It is called measurement (and/or calculation) error. If application gets these values from ACPI subsystem (sensors or counters or whatever) they probably have weird scale form like 'tens of ticks per nanosecond' so that application should convert them to a human friendly form. And probably Core speed value is calculated by multiplying Bus speed to multyplier. So when Bus speed is measured (or calculated) as not 100MHz you see not 3900MHz.
Yes that's it. I don't know why it had to end up being this way. It's so annoying to see it do that, but I guess I'll have to ignore it. T_T
If you really want to look into this further, I would go to CPU-Z forums and post the question there. The ticks you are referring to would better be described as the CPU frequency wandering from it's set value. It's probably within the programs error of margin but you might want to point it out to them incase an issue has surfaced in their latest version. https://www.hwinfo.com/forum/
Hi, thanks. It had to do with CPU-Z, though. I am just going to use HWiNFO instead now. Thanks. Merry Christmas
Yes you are right. I can't take it with CPU-Z, it's much worse now. Not even Microsoft themselves seem to care, which is saddening because it's much worse on the task manager. It shows the speed at 3.85 GHz and goes to 3.88 GHz for a slight second sometimes. The developers just don't care much to fix it