CPU frequency/voltage always read at maximum (1.0 RC5, RC6)

[The_Assimilator]

CPU: Core i5-2500K (Sandy Bridge) @ 4.5GHz/1.392V
Motherboard: ASRock Z77 Extreme6

My CPU is overclocked but EIST is enabled in the BIOS to allow it to throttle down to its minimum clocks/voltages (1.6GHz/1.024V) when idle. CPU-Z and various other hardware identification applications correctly track the CPU's throttling up and down, but Core Temp does not - it's always stuck displaying the maximum reading, 4.5GHz/1.392V. Obviously this negates much of the usefulness of Core Temp.

I first noticed this issue in Core Temp 1.0 RC5 and had hoped it would be fixed by RC6 but unfortunately not.

If you require any additional information please advise, I will happily provide it if possible. Also willing to test debug builds if that helps to isolate the issue.

[The Coolest]

Try to open the System Info screen under tools and see what happens to the frequency/vid values there.
Also what Windows are you running on your system?

[The_Assimilator]

Since I made this post I swapped out my CPU for an i5-3570K running at 4.7GHz, problem still persists. My OS is Windows 7 Professional x64.

I opened the System Information window like you suggested. All 4 cores were pegged at 4.7GHz, but the VID was fluctuating between 1.1809 and 1.1859 volts. Then I closed System Information (without pressing the refresh button) and suddenly Core Temp started reading the frequencies/VID correctly!

Let me try a few more tests, will post again later.

[The Coolest]

What is the power plan select in Power Options? Try setting it to Balanced (or to power saver if it is already on balanced) and see if this affects Core Temp's readings.

[The_Assimilator]

What is the power plan select in Power Options? Try setting it to Balanced (or to power saver if it is already on balanced) and see if this affects Core Temp's readings.

It's set to Balanced, been set on that since I installed the OS. Things are still weird, here's what I did:

1. Shut down the PC.
2. Booted up again, I have Core Temp set to load with Windows, so it launched. At that stage it was correctly displaying the idle/turbo frequencies/voltages as the machine switched between them.
3. Put the computer into Sleep mode. When I woke it, Core Temp was stuck on the turbo freq/volts. Opening System Information and clicking "Refresh" did not change anything.
4. Restarted Core Temp, it was still stuck on the turbo freq/volts. Opened System Information and watched it, after about a minute the freq/volts started updating correctly without me touching anything, after that Core Temp works as expected.

So I have a workaround now: restart Core Temp after waking the computer from Sleep - which isn't ideal, but I won't lose any sleep over it.

The super weird part is that when I made this post, Core Temp was always reading the freq/volts at turbo levels - regardless of what I did (although I have to say I never opened the System Information window before today). I also haven't updated BIOS/drivers - literally the only thing that's changed is that I swapped out the CPU - perhaps a Windows update changed something?

Last thing to note - in the BIOS settings for my board, I have disabled C-state related options as they can interfere with an overclock - however EIST is still enabled. Could this be confusing Core Temp?