Realtemp reports 100% CPU usage all the time??

Ok i have tried what you suggested vashiro, i changed the min cpu clock speed to 60% and the max to 90% but the clock speed in CPU-Z didnt change at all. I recorded it on my crappy mobile camera....

http://youtu.be/C9sRRDC4JhM

Notice how realtemp clock speed and usgae doesnt change either?, and how different the clock speeds are between Realtemp and CPU-Z

PS. sorry about the quality
 
The Balanced profile on your Windows install is broken so don't use it. You are not missing out on anything. Modern Core i CPUs are designed to significantly reduce power consumption internally when idle regardless of what power profile you are using. People that continue to promote the Wiindows Balanced profile have never done any hands on power consumption testing. The difference in power consumption between this profile and the High Performance profile is minimal or non-existent.

Your High Performance profile appears to be working correctly so set the Minimum and Maximum to 100%. On a Core i CPU, this does not force your CPU into a high power consumption state when idle. The reported MHz when a Core i CPU is using one of its C Sleep states is not important.

Your motherboard does not allow you to use C3/C6 when overclocking so all you have to decide is whether you want to use C1 or C1E. With C3/C6 disabled, when RealTemp reports a low value for Load when idle, that confirms that the C1 sleep state must be working. You can choose C1E in the bios if you would prefer to use that sleep state all the time. If you only want to use C1E some of the time then use RealTemp to enable or disable C1E when you are in Windows.

Reinstalling Windows and installing hundreds of Windows updates and all your software 1 by 1 would be a huge waste of time. Beyond satisfying ones curiosity, it wouldn't accomplish anything because for maximum performance and minimum power consumption, you are still left to choose from the above options.

CPU-Z is designed to be a MHz validation tool. What it tells you about your CPU when it is idle and using various C sleep states is not always a good indication of what your CPU is really doing internally. CPU-Z chooses to ignore some of these sleep states so it can provide users with consistent MHz when doing a validation.
 
Last edited:
unclewebb said:
Your motherboard does not allow you to use C3/C6 when overclocking so all you have to decide is whether you want to use C1 or C1E. With C3/C6 disabled, when RealTemp reports a low value for Load when idle, that confirms that the C1 sleep state must be working. You can choose C1E in the bios if you would prefer to use that sleep state all the time. If you only want to use C1E some of the time then use RealTemp to enable or disable C1E when you are in Windows.
Click to expand...

So the GIGABYTE EX58-UD5 mobo doesnt use C3/C6 states just C7 when overclocked? Whats the difference between C1E and C1 state, and should i only have one or the other enabled in the BIOS?

yashiro said:
Did you try removing that Gigabyte Easytune nonsense?
Click to expand...

I had this problem before i installed ET6, so i dont think the 2are related.


A bit more info i have noticed in msconfig under the services tab there is something listed as,

Intel(R) Integrated Clock Controller Service - Intel(R) ICCS

which at the moment has the status set to 'Stopped' what is this and is it linked to the problem im having??
 
Nope. Not sure why you have that installed on a UD5 anyway.

If your aim is to have your CPU go into low power states while overclocking on a UD5 then having EIST and C1E enabled achieves that. The other C-states are best left disabled.

A UD5 with an overclocked i920 will downclock just fine. So it's probably something you keep repeating/installing that is breaking this functionality.
 
Just did some quick checks for you as this was bugging me.

v1.62 of CPU-Z is broken on the UD5 (reports max multiplier is active 100% of the time). Every other tool reports the CPU speed correctly except CPU-Z. Perhaps Realtemp is also incorrect with regards to the Load?

55 degrees is hot for totally idle though. Idle means straight after boot, nothing supposedly running. No Firefox, no flash in the background etc.

Try using v 1.61 of CPU-Z. That's the last version that works correctly for me.
 
Last edited:
I don't know if this has been covered already, but have you tried closing down real temp and using core temp? I was reading an article last night about real temp having some interesting capabilities, for example it can throttle your cpu. I suspect it could also make it run 100% too. Just a thought.
 
yahiro: You have got it all wrong. CPU-Z versions before 1.62 are the ones that are broken. The old versions used to tell people that their CPU was nice and stable at idle using the 16 multiplier when internally, the multiplier could be rapidly cycling much higher. CPU-Z 1.61 used to ignore this. CPU-Z 1.62 decided that if the multiplier is not at the lowest value then it must be at the highest value. This is still wrong but at least it is getting closer to the truth.

Depending on how you have Windows setup and depending on what C States you have enabled, a lightly loaded CPU can have the multiplier changing hundreds of times a second. Software that reports a steady single multiplier when this is happening is misleading.

For years, almost all monitoring software has followed CPU-Z. What CPU-Z reported was assumed to be 100% accurate so software that showed anything different was assumed to be wrong. Now that CPU-Z 1.62 has started trying to be more accurate, users don't know what to believe.

Keep in mind that the programmer of CPU-Z creates methods for consistent validation purposes and that's fine if that is what you are interested in seeing. RealTemp was interested in accuracy so decided to tell it like it is. It has been using the same proven method since the first Core i was introduced in 2008. RealTemp uses high performance timers within the CPU and a method recommended by Intel to accurately determine what the multiplier is really doing. RealTemp is also one of the very few utilities that can show the percent of time that a CPU is spending in the C0 state. It also does this by following a monitoring method recommended by Intel.

If you are interested in learning what your CPU is really doing, turn off all versions of CPU-Z. A lightly loaded Core i CPU might not be sitting at a nice fixed multiplier so using software that tells you this should be avoided.

55 degrees is hot for totally idle though.
Click to expand...

You are not understanding what is going on. A CPU can be idle and it can be spending its idle time in the C0 state or it can be spending its idle time in the C1 state. When idle in the C0 state, it will be running at a much higher core temperature compared to when it is idle in the C1 state. In both situations, the CPU is still considered to be idle. The Task Manager simplifies things. It tells you that your CPU is idle but it is not smart enough to know what idle state the CPU is in.

lettuce's CPU is idle. The Task Manager confirms that. The broken Balanced Profile is forcing his idle CPU into the C0 state, 100% of the time. Switching to High Performance allows his idle CPU to drop down into the low power C1 state. The immediate change in his core temperature when switching profiles and the immediate change in the RealTemp C0 based Load percentage confirms this.
 
I wasn't aware of this change within CPU-Z. I'll check it out.

I don't have the same issue here though despite having a similar setup. So something is broken in software or being misreported. With all the power saving gubbins enabled on a UD5 (f13) the machine should be functioning as expected.
 
You're right that something is broken. This CPU gets stuck in the C0 state when using the Balanced Profile. RealTemp is not misreporting anything. It follows the Intel recommended monitoring methods and is one of the few utilities that is capable of accurately reporting exactly what is going on.

As for CPU-Z, what version do you want to believe? Here's an example:

http://img338.imageshack.us/img338/6682/cpuzoldnew.png

Neither version is correct.

RealTemp accurately tracks the average multiplier and in this situation, it shows the multiplier randomly going up and down depending on the CPU load. As cores wake up to process background tasks, the multiplier will increase and as cores go back to sleep, the multiplier will decrease. When a CPU is lightly loaded like this, cores can be rapidly transitioning between various C States (C0, C1, C3, C6) hundreds of times a second.

In this example, reporting a steady 16 multiplier or reporting a 40 multiplier does not accurately represent what the multiplier is really doing in this lightly loaded Core i CPU. A few people in the forums have noticed the change in how CPU-Z is reporting this but most seem to think that it must have been a Windows update or something like that.

Anyway, it's possible that the bios is not setting up all 4 cores consistently which can screw up Windows when it is trying to determine what C states are available. Intel wrote a DOS based program called the BIOS Implementation Test Suite (BITS) that lets you run various tests to make sure that all 4 of your cores have been set up the same. You need to burn BITS to a bootable CD and then you can test your bios for any issues without needing to run Windows.

http://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=19763
 
You must log in or register to reply here.
Back
Top Bottom