Real Temp - New temp program for Intel Core processors

[randomizer]

Thought I might chip in something else here. Nothing new, but this thread must get a shot of caffeine every now and then. I'm so dedicated I haven't even got video drivers installed yet



I've finished making sure that CPU is working unclewebb. The motherboard's VRM simply can't handle the quad overclocked and overvolted so even 3GHz caused reboots. Strangely it passed several hours of Far Cry 2 but rebooted while surfing the net the next day. I'm glad to be rid of that board now I'll ship out the E6600 on Monday unless the post office is open on Saturdays, which I don't think it is.

[OC Nub]

unclewebb, I have the Gigabyte UD3P board. I booted at 506x8.5 but changed the FSB in windows using ET6 to 512x8.5, Real Temp is still reading the speed at 4.3ghz. CPUZ reads 4.35ghz and also shows the voltage increase. Is it still reading what was originally set in bios or am I still running 4.3ghz ? I was trying to do some tweaking without constantly rebooting. Thanks
http://img5.imageshack.us/img5/1903/512o.png

[SimpleTECH]

unclewebb, I have the Gigabyte UD3P board. I booted at 506x8.5 but changed the FSB in windows using ET6 to 512x8.5, core temp is still reading the speed at 4.3ghz. CPUZ reads 4.35ghz and also shows the voltage increase. Is it still reading what was originally set in bios or am I still running 4.3ghz ? I was trying to do some tweaking without constantly rebooting. Thanks
http://img5.imageshack.us/img5/1903/512o.png

You may want to try one of his later builds, just in case.

[unclewebb]

There was a change in Windows 7 that screwed up RealTemp's ability to update the FSB reading when overclocking from within Windows. Check out the latest beta version of RealTemp and let me know if this bug has been fixed for you. It worked last time I tried on my E8400 and rge said it's working OK on his Core i7-950.

http://www.fileden.com/files/2008/3/...alTempBeta.zip

[OC Nub]

Yes, works great now. Thank you!

[unclewebb]

http://www.fileden.com/files/2008/3/...alTempBeta.zip

To keep the XS guys happy, I put an option in the Settings window so you can look at real time VID info on the main screen instead of the timer. It might drop down to a lower value at idle depending on your motherboard and bios settings like EIST and C1E. On a mobile CPU, you might also see some intermediate values somewhere between VID Min and VID Max during an EIST transition.

[OC Nub]

That's a great feature, Thanks

[Mehmet_Ali]

nice one thanx

[Brama]

I set VidInfo=1 in .ini file but I have always the time displayed.
Using Asus R2E with BIOS 1406.

Just a cosmetic note: if you enable in the .ini file the customization of degrees symbol, it is changed correctly everywhere except in the "Temperature (°C)" string, under the load info.

[burebista]

I set VidInfo=1 in .ini file but I have always the time displayed.

I'm pretty happy this way

[unclewebb]

http://www.fileden.com/files/2008/3/...alTempBeta.zip

Just a quick update to fix a few minor issues.

There's an INI option,

DegreeSymbolString=""

that lets you change what the degree symbol looks like. Brama says it didn't get used in the Temperature Heading and he was right. I originally didn't know how to change those but now I do so the degree symbol should be consistent throughout the program.

While fixing that I discovered that it really wouldn't be that hard at all to add a Fahrenheit option. Personally, I hate Fahrenheit but a few users have requested it during the last year so I finally caved in. Just use this INI option.

Fahrenheit=1

There is not enough room in the System Tray to display 3 digits when using Fahrenheit so 125 degrees will be displayed as 25. I won't be fixing this.
First person to post a 200 degree screen shot will win a prize.

All Fahrenheit does for me is make my CPU look like it's hot as hell.



The RealTemp Load meter has always been based on the percentage of time that the CPU spends in the C0 state. This method is designed for the Core i7 and seemed to work OK for Core 2. On mobile processors though, this can cause an issue at idle. As a mobile CPU idles down, depending on EIST/C1E and a few other settings, the percentage of time that it spends in the C0 state can start going up. As the MHz goes down and as the second core gets turned off to save power, the remaining core must work harder and harder to get the background tasks done at idle. If you've ever seen the RealTemp load meter go up while your CPU idles down, that's probably why.

If the RealTemp C0 state based load meter is not for you then you can go into the Settings window and select TMLoad and RealTemp will use the traditional Windows based function similar to what the Task Manager uses. It might provide you with more usable information on a mobile CPU though the other meter is useful too as long as you understand what it's telling you at idle. Take you pick.

Brama: VID information does not apply to Core i7. Intel says that VID can't be read from their Core i7 CPUs so no software reports this.

[WaterFlex]

Thanks, Uncle! Working great on I7 64bit build 7600 RTM

[Brama]

Thanks, Uncle! Working great on I7 64bit build 7600 RTM

Just a note.
Microsoft declared that build 7600 of Win7 that we can found in these days, is not RTM.

True lies?

[SimpleTECH]

unclewebb, I'm not sure what's happening but with RC12 I am not getting it to show all of my core temperatures correctly. It just shows the 4th core.

RC11 works though.

[unclewebb]

unclewebb, I'm not sure what's happening but with RC12 I am not getting it to show all of my core temperatures correctly. It just shows the 4th core.

RC11 works though.

RealTemp is like an apple cart. Whenever I throw on a couple of more apples / features, the whole damn thing falls apart.

Can you post a screen shot and a few details like what OS you're using. These bugs are mostly bugs in the 10+ year old C++ compiler I'm using. I'll try to find a work around for this issue and send you a version or two you can test if you want to help with project RealTemp.

[SimpleTECH]

Hmm. Just tried it again, but under Windows 7, and it seems to be working.

I'll try it with Windows XP.

[SimpleTECH]

Yeah it seems like XP doesn't like it.

RC11 (left) / RC12 (right)

[unclewebb]

Thanks for posting that. The APIC ID number shows that it is only finding your last thread. In RC11 it shows that it is finding all 8 of your threads, 02461357. That will help me try and find the issue. It's always fun programming in Windows when code that works 100% in one OS falls on its face in another OS. The Windows API function to count cores is buggy. If I was a smarter guy I'd write my own code for this and save myself a lot of headaches. This isn't the first time this issue has surfaced. In a day or two I'll send you a version that tries to work around this issue.

[SimpleTECH]

Okay, thanks unclewebb.

Honestly I couldn't do worth a damn of coding (when I had taken a few CS classes couple of years ago). So don't feel bad.

[jobol]

Latest beta only detects 1 core on my 920

[stasio]

Me same

[unclewebb]

Me same.

It works fine in Vista but only shows the last core on my wife's XP laptop and within a minute usually crashes.
Time for a RealTemp overhaul. This might take a day or three.

Edit: RC12 has been shot and buried.

RC11 is back at the main fileden download area.
http://www.fileden.com/files/2008/3/...alTempBeta.zip

Now I can spend more time testing RC12 to see where I screwed up. I mean, find out why XP is so screwed up.

[jobol]

Me same.

It works fine in Vista but only shows the last core on my wife's XP laptop and within a minute usually crashes.
Time for a RealTemp overhaul. This might take a day or three.

Edit: RC12 has been shot and buried.

RC11 is back at the main fileden download area.
http://www.fileden.com/files/2008/3/...alTempBeta.zip

Now I can spend more time testing RC12 to see where I screwed up. I mean, find out why XP is so screwed up.

Hey uncle,

Yes, RC11 worked for me. Can I throw a quick suggestion?

Could you please add the option of displaying "Highest core temp" under "system tray settings"?

That way instead of always displaying the temp of a given core, it can display the highest current temperature in the system tray, regardless of the core. It might even add the core to the temp in the tray. ex: 72|Core2 (means that right now, the highest temp is 72C and is veing reported by Core #2)

[unclewebb]

jobol: I've thought about this feature and I'll probably add it someday. If you only want to monitor a single core then monitor core 0.

It is usually the most accurate and almost always the highest. On a Core 2 Dual or Quad Core, it should be exactly the same as core 1 as both cores are attached. Even if you have Prime running on one of these cores and nothing running on the other, both cores are still going to be at almost the same temperature because they are physically joined together. On a Core 2 Quad, core 0/1 pretty much always report higher than core 2/3.

On a Core i7 CPU, screen shot after screen shot that I've seen has core 0 as the hottest core. All 4 of them are joined together so it's hard for one to get too much hotter than any of the other ones.

[radaja]

Me same

good to know its not just mine.i tried the last three and all did the same with my E8400 and XP.but now i dont need to report it,because you guys already are on it