RealTemp General Discussion

Decoman: I thought this used to work when using UAC but it doesn't seem to work anymore. Maybe there was a Windows security update that plugged up a security vulnerability or maybe I was just delusional when I originally played with this.

If you go into your non admin "user account" and right click on the Task Scheduler icon and run it with Admin privileges, you can use the following method to auto start RealTemp.

http://forum.notebookreview.com/har...es/531329-throttlestop-guide.html#post6865107

After you get that done you have to go back and edit this task to make sure RealTemp tries to start only when you are logging into your non admin account. On the General Tab in the Task Scheduler you also have to make sure that it is using your non admin account.

Even with all this, you still have to enter an Admin user account and password each and every time RealTemp starts. That's ridiculous but I can't find any way around this.

I am on a computer that is running Vista x86 at the moment but this weekend I will try again when using Windows 7. I am not very hopeful at the moment.

There was a RealTemp plugin that used to sort of work with RivaTuner but MSI Afterburner doesn't support any of the previous RivaTuner plugins so development on that project ended.

RealTemp does not have any built in graphing abilities. The only thing you could do with RealTemp is run it with the Log File option checked. You could then take that data and import it into Excel to graph it but that is not very practical.

I think the Core Temp program has a graphing option.

http://www.alcpu.com/CoreTemp/

Core Temp Grapher Beta
http://www.alcpu.com/CoreTemp/addons.html

RealTemp is for CPUs with 4 cores or less and RealTemp GT is for CPUs with 6 cores.
If you don't know how many cores your CPU has then tell me the model number or look it up here.

http://ark.intel.com/

Just physical cores. The regular version of RealTemp is designed for Quad Core processors like the old Core 2 Quad Q6600 or the newer Core i5-2500K or Core i7-2600K. RealTemp GT is designed for the 6 core processors like the Core i7-980X or the recent Core i7-3930K.

RealTemp 3.70 should be reading Ivy Bridge CPUs correctly but I don't have an Ivy CPU to confirm this and most of the people that do have Ivy CPUs are not talking.

From what I understand, the temperature data is still in the same register as previous Core 2 and Core i generations and the TJ Target or TJ Max register is also still in the same location as before so RealTemp and other monitoring applications should work as is.

There is a rumor that Ivy ES processors have TJ Target set to 91. Here is the formula that all software uses.

Reported Temperature = TJ Target - Digital Sensor Reading

All software assumes that the TJ Target value written to each CPU core is the same as actual TJ Max but the two values might not be the same. Intel has previously stated that actual TJ Max might be higher. Actual TJ Max might be 91, 98 or 100, 105 or some number in between. It might be consistent for all cores or it might be completely different from core to core. No one knows and the few people inside Intel that do know are not talking.

If there is a pile of unknown error in the TJ Target / TJ Max value and the sensors are far from 100% accurate from idle to full load then reported temperatures are more like random numbers.

I have read some forums where all sorts of conclusions are being drawn on how hot Ivy Bridge runs. That's nonsense. These conclusions are based on temperature data that can not be relied on for any of Intel's recent CPUs. Temperature data from Intel CPUs should not be compared to other CPUs in the same CPU family let alone comparisons to CPUs from different families.

RealTemp is a good program and the sensors are useful enough so that if you swap a heatsink you can see if things are better or worse but beyond that, Intel's core temperature sensors are not accurate enough or documented well enough to provide users with 100% accurate core temperatures.

I will see if I can add these features for Ivy Bridge CPUs the next time I am working on RealTemp. It might be a month or two until I get around to doing this.

Go into the Control Panel and open up the Power Options. Under Processor power management what do you have the Minimum processor state set to? Try setting that to a low number like 5%. Your CPU won't actually go down to 5% but it will allow your CPU to go as low as possible.

How much background stuff do you have running on your computer? What sort of Load Percent does RealTemp show at idle? There might be something preventing your CPU from truely idling down. CPU-Z is designed for MHz validation purposes so to keep things simple, it hides some of what your CPU is really doing internally. RealTemp tries to tell it like it is.

You might want to play around with my ThrottleStop tool as well.

http://www.techpowerup.com/downloads/2090/ThrottleStop_4.00.html

This should allow you to adjust the multiplier from within Windows. You can also watch to see what percentage of time your CPU is spending in the deeper sleep states like C3 and C6 as well as over all power consumption. The initial warning message is for owners with Extreme mobile CPUs. Some users like to overclock them to the moon with the help of ThrottleStop.

Looks fine.. But after a little more time has passed, the system starts to idle, and it down clocks to 1.6GHz
I'm not even completely sure why it's doing this with all of the power saving features turned off.. Maybe I missed one?
Anyway, after it has 'downclocked' like this, it never goes back up past the stock 3.3GHz, even under 100% load.

Click to expand...

When a Core i5-2500K gets locked to 3.3 GHz, that means the Intel Turbo Boost feature has been disabled. The above quote comes from your very first post about this problem on Overclockers.com and this was before you started using RealTemp.

I am not trying to say that RealTemp is innocent but if this problem can occur without running RealTemp then the real problem could be how your bios is setting up your CPU. It also doesn't make sense that with all of the various power saving features disabled in the bios that your CPU is still able to idle down to 1.6 GHz after booting up. Are you using the most recent bios version?

When running RealTemp, have you looked in the RealTemp Settings window to see if the Disable Turbo option is checked? Make sure that box is not checked and then put a load on your CPU and see if Turbo Boost starts working correctly for you again. That box might have accidentally got checked.