Hi unclewebb!
Can I have my X for extreme after i7-990? :D
Just a small bug, but it's poking my eyes, you know me. ;)
Printable View
Hi unclewebb!
Can I have my X for extreme after i7-990? :D
Just a small bug, but it's poking my eyes, you know me. ;)
Hi unclewebb
I've been using RealTemp 3.67 on my 2500K.
Most of the times I had it showing the same temperature for all 4 cores like below:
http://img.techpowerup.org/110424/PS...A2A1_70.00.jpg
Is this a bug of the software or just the normal behaviour of Sandy Bridge's sensor?
Thanks.
BTW: I saw many people have experienced this fact.
It's hard to win. If software shows a bunch of different core temperatures, everyone is suspicious of crappy sensors and if the core temperatures are all the same, everyone is suspicious of crappy software. :)
Your screen shot shows RealTemp reporting a variety of minimum and maximum temperatures. A maximum of 72C was recorded on 3 of your 4 cores but they all occurred at different times so RealTemp must be reading all 4 sensors and not just a single sensor and then copying that value.
If you want to do some testing, run a single thread of Prime95 Small FFTs and then open up the Task Manager and use Set Affinity... to limit prime95.exe to different threads within your CPU and see how the core temperatures vary. As you move the Prime95 load around, the peak core temperature within the CPU should move around too.
32nm CPUs are tiny so there might not be a huge difference in temperatures. There's not a lot of real estate between the 4 core sensors. One hot spot on a core is going to spread to the other core sensors very quickly. This also might have something to do with what you are seeing.
donmarkoni: I'll put the missing X on the things to do list.
-X-hellfire: Adjustable transparency is an interesting but I'm not sure if I'll ever get around to adding that feature.
Is there a Real Temp applet for the G15 yet?
realtemp 3.67 is only displaying 3cores i7 970 ES, i have turbogt opened and it only shows multipliers and C0 state etc
I have google searched, and have no luck.
Only thing http://www.evga.com/forums/tm.aspx?m=849875&mpage=1 i foudn was this.
Can someone please help cheers.
Under Thermal Status, I saw a "Log" instead of Ok. Does that mean it was logging my temps or something's wrong with one core? I don't remember enabling logging.
Retrolock LOG means that that core hit TJMax value and your CPU is throttling.
Check your cooler ASAP.
Sanousie use RealTempGT for your Gulftown.
@unclewebb
How much is the delta of a 2600K on stock speed above ambient temperatures with a highend air cooling?
I remember the Q6600 had about 8-10c rise.
I haven't done any temperature testing with a 2600K like I used to do in the good old days with the Core 2 CPUs.
Maybe someday.
I see, but my GUT feeling tells me it still like the Q6600 ~10c above ambient.
@unclewebb
Any chance you can get the new Max option that reports the highest temperature in the moment quickly added to the RealTempGT executable for Westmere/Gulftown chips? I really like that option in the new version of RealTemp and I know that the change has to be pretty trivial (the code just needs to compare the polled values and report the highest at any given instance in time). Please let me know :) I would really appreciate it!
:D
If anyone else needs the above, just ask. I've got an updated version of RealTemp GT but it hasn't been tested very much. dejanh is happy with it so far.
RealTemp GT 3.64
http://www.mediafire.com/?jibd769x6z7n0c8
dejanh put me to work and helped me get RealTemp GT fixed up for the 6 core users. There haven't been too many requests since Sandy Bridge arrived. :)
No more memory leak and it can report the highest core temperature in the system tray now so you don't have to look at all 6 cores anymore.
The download also includes i7 Turbo GT 1.30 which has Sandy Bridge support and the correct version number on it. Thanks stasio.
Thanks Uncle! :clap:
I'm happy to report RealTempGT 3.64 is working as expected. No more memory leak. Thanks uncle! :D
unclewebb, I've been using your Real Temp 3.60 (which BTW I really like) and I've noticed an odd occurrence which I'm hoping you can shed some light on.
When attempting to calibrate idle temperature on my HP 311(Atom N270) Real Temp disregards my changes on subsequent sessions. I used the setting control panel to make the change and checked the RealTemp.ini when the settings reverted. The entries are present but aren't reflected in operation.
I understand the idle temperature likely isn't measured accurately on my CPU and that the distance to TJmax/pref is probably accurate, still I'd like to adjust the displayed temperature to correspond with OCCT, Everest and such which are doubtless closer to reality since room temperature > reported CPU temperature. Can you reccomend a way to accomplish this short of changing idle calibration settings each session?
RealTemp 3.67
http://www.mediafire.com/?jibd769x6z7n0c8
Where have you located the RealTemp folder? It sounds like the file permissions for the RealTemp.ini file have been changed so you don't have full Read/Write access to that file anymore and your settings aren't being saved correctly. Right mouse click on the RealTemp.INI file, select Properties and then have a look at the Security tab. Windows can change the permissions if you unzip a file to one location and then move it somewhere else, especially on a different drive. I think that's what the problem is.
You can also try downloading the latest version above and unzip it somewhere like your desktop and see if you can save your settings then.
Thanks for the quick response.
I tried 364 with the same results which I'll reiterate as I believe my post was unclear.
Changes to Realtemp.ini are persistent and yet the program doesn't reflect changes to idle offset or TJmax in operation on successive starts, despite the custom values written to the .ini file.
My C: volume is write protected but since Realtemp resides on a different volume that shouldn't matter, however I'm puzzled and grasping at straws.
Edit: System tray font and color changes are persistent in operation. Perhaps Realtemp is defaulting to auto-detected or default values for TJmax and idle calibration on my platform.