Thanks JohnZS. All programs are reading the same info from the same sensors so I'm not sure what OCCT is reporting or why. The competition thinks their interpretation of the data coming from these sensors is right and obviously I think my interpretation is right. Good to hear that RT is working for you.

The PROCHOT# reading at the bottom of RealTemp shows you if a core is overheating. That's Intel speak for Processor Hot which is a signal from the processor that it is too hot and thermal throttling has begun to keep the temperature from getting any hotter. This data is separate from the DTS temperature data but is likely coming from the same sensors. Intel individually calibrates these processors so I'm assuming that PROCHOT# is working correctly even on CPUs with dodgy sensors. If the PROCHOT# boxes are clear in RealTemp then the CPU isn't throttling and it should be running happily at full speed.

I'm working with RejZoR at the moment trying to find out why RealTemp doesn't start minimized for some users. He has it in the Task Scheduler and found that he needs to set a time delay for it to minimize properly on start up. I tried to make RealTemp start up as quickly as possible but it looks like I might have to build in a delay option for Vista users. Whatever it takes to keep everyone happy.

In XP you can drag programs into the All Programs -> Startup folder. Does Vista have this option or do you have to use Task Scheduler?

If you have this problem with Vista then try setting a delay and see if that works. I'm not a fan of Registry mods but I might have to add that option so users can add it to their Start Up area that way.