max/min are simply the highest and lowest recorded temps during the time realtemp is running. I think 71c intel limit is tcase max which is quite different than actual core temperature.
Printable View
max/min are simply the highest and lowest recorded temps during the time realtemp is running. I think 71c intel limit is tcase max which is quite different than actual core temperature.
loonym: You could try running CPU-Z and in the cpuz.ini file set
SENSOR=OFF
to see if CPU-Z reports the same VID as RealTemp.
During testing, RealTemp and CPU-Z always reported the same thing for VID. To be honest, the Intel docs I read were not clear when it came to the correct way to read VID. I assumed that CPU-Z was getting this right and tried to follow along. You might also want to try CoreTemp which I think recently changed its VID calculation for the 45nm chips.
I don't know if these CPUs have a VID number stored in the chip that is totally independent of the motherboard it is installed on. If anyone finds in the Intel documentation how to read VID information then post it here and I will compare that to what I'm doing to see if I screwed up.
I know on my wife's Dell laptop, T7200, that RealTemp and CPU-Z report two different voltages for VID depending on whether it is in CxE power saving mode or not.
CERO: My choice of TjMax=95C for a Q6600 - G0 was based on testing of my Q6600 with an IR thermometer.
The previous assumption by every other program that TjMax=100C seems to be based on that is what Intel TAT uses even though TAT was specifically designed for testing mobile core processors and was never updated or designed for use with Core desktop processors.
If you trust TAT more than you trust my testing then it is easy enough to go into RealTemp and set TjMax=100C.
Edit: Here's some info from my original test:
http://www.xtremesystems.org/forums/...&postcount=568
It was a brand new processor that I was unfamiliar with so I didn't do a thorough test but hopefully I will have some time later this week to re-test my Q6600. After using this processor for a couple of months, the temperature sensors on core0 and core1 seem to be the most reliable and give consistent / balanced results.
@ loonym
@ Uncle
heres short description of a situation of different VID value within the SAME SYSTEM , Same components, even same run (b00t)
only software side interaction (Asus Ai Suite, Ai Gear3 with EPU driver) is causing this delta - 0.1000v (vid-value) Maximus Extreme /QX9650 /
just check both screens
(sorry these NOTES, screens are 1.5 months old (or somthing ..), So RealTemp was not used to monitor VID, ( sorry )
http://img218.imageshack.us/img218/7...end3pf9.th.png
http://img169.imageshack.us/img169/9...wer3ku8.th.png
--
clean XP setup / AiGear 3 installed / fresh drivers from asus site
more explanation .. coming .. just need to review other saved bench-screens and recall my actions from this period
--------------
Now, i have already un installed all this' Asus Ai ''CRAP' '' from that machine,
so currently can't REPLAY this situation,
anyway those ''Green Things'' made more troubles than use of it,
so returned back to my manual 24/7 settings @3600 with C1E/ speedstep enabled,
i didn't mean to prove or complain anything, what so ever,
just tried to describe the situation, i saw then..
-----------
loonym: I just remembered something. When VID got moved off of the main page of RealTemp, I also changed it so its value is no longer being updated in real time. My thinking was that I didn't want users inputting new settings and having things get screwed up by constant updates to the Settings page so the VID reported doesn't change. It's now read every time you open the settings page and if you were in C1E mode, the act of opening the page might or might not switch it to the higher value. The design of the motherboard could also effect what shows up.
It's possible that your chip has two VID settings built into it like the mobile chips. My E8400 only seems to have one VID but that might be because of the older Asus P5B I have it on.
You could try running v2.5 which is still available from the TechPowerUp site to see if that's the problem. I had planned to move VID back to the main page so it's updated along with temps on a regular basis. Thanks for reminding me of this bug / limitation and giving me some motivation to get VID back on the main page.
Thanks for the suggestions, I'll give it go. Not really a huge deal anyway, just one of those things that makes you go hmmmm....
I really don't think it is anything to do with realtemp or any other app. After trying the same cpu in a couple different boards I'm quite sure it's the gigabyte bios. Maybe I'll flash a different version and have a look at that.
Where are you Grandpa?
I need a beta tester that has problems with RealTemp reporting the wrong MHz when the CPU MHz option is enabled in the bios. That option is supposed to make RealTemp compatible with SetFSB but it has a problem on some motherboards where the MHz that RealTemp reports is too high.
I put some new code to calculate CPU Frequency into a separate utility for testing purposes. My board always reports the MHz the same as CPU-Z so I have a hard time seeing if I've made any progress.
http://www.fileden.com/files/2008/3/...07/MHzCalc.zip
MHzCalc should show your maximum MHz based on your present FSB times your maximum multiplier. When using the highest multi, if this app reports the CPU MHz higher than CPU-Z then do me a favor and post a screen shot of both programs so I can have a look. Thanks.
http://images30.fotosik.pl/224/62e66621d7f7d0f1.jpg
Whats is real temp ? ;) e2140 @ wc
As long as I check the CPU MHz option box in realtemp it keeps up fine on the few setups I've tried it on. Neat little applet, that MHzCalc though unc.
edit: MHzCalc shows the large swing the board makes when using setfsb in real time. I like it.
Arni: TjMax=100C is a myth for the L2 processors and all desktop processors that I know of. Intel TAT assumes TjMax=100C because it is a mobile / laptop testing tool. It was never designed for desktop processors but most programmers accept anything that TAT says as true because it has that nice little Intel logo on it.
Read the RealTemp docs and try doing the calibration test and post your results.
http://www.techpowerup.com/realtemp/docs.php
loonym: I would need to add support for the multipliers to make it a useful stand alone app. I'm just hoping that it calculates the MHz properly on all boards when using SetFSB. You have to write a lot of ugly code and formulas to try and get some accurate timing out of a Windows based computer when using SetFSB. Other than CPU-Z, there isn't any choice that I know of for accurate MHz when overclocking from within Windows. If I get some positive feedback from Grandpa or another user that has a board with this problem then I will add this new MHz code to RealTemp.
Quote:
Originally Posted by unclewebb
So what temp i should set in tjMax ?Sensors movement 10 and 9 "Test Sensor" ...
:shrug:
If you are using RealTemp you shouldn't touch the default TjMax setting for your L2 processor.
85C is correct, 100C is wrong.
ok thx . No calibrate also ?
Many L2 processors need a 1.0 or 2.0 calibration adjustment but the sensors on every processor are different. It's best to read the documentation about Calibration. Just ask if you are not sure about anything.
Uncie...throw up a new beta, go on...you know you want to!
I Have it set to 460Mhz
ok i set for cores 3.0 and temp now in idle 33* / 32* looks real [in room 20-23*] Nice soft rly! One sugestion in next version plz give option for minimalize to watch and "start with widows" :D
Cya and again thx
Grandpa: Looks like I'm making things worse! I might have to concede 100% compatible with SetFSB to CPU-Z but I really hate to give up.
Arni: Here's the easy way in XP to make RealTemp start with Windows.
http://img74.imageshack.us/img74/620...windowstz7.png
Click on the Start button, go to All Programs and drag RealTemp into the Startup folder.
I don't like any program that tries to add stuff into my Startup area so I like doing it manually. RealTemp already has a Start Minimized feature in the Settings window.
One user with Vista x64 SP1 says version 2.60 doesn't minimize to the System Tray anymore like version 2.5 did. I think he just had the Task Bar option selected. If there are any bugs like this then let me know.
Richard: You know me too well! I'd love to release a beta, like yesterday. I'm debating whether to scrap SetFSB compatibility. Most users run CPU-Z anyhow when posting screen shots so this would simplify things and help keep RealTemp nice and lean so it doesn't stress Vista too much!
Is there anyway to make real temp, show highest cpu temp (on quad core) when minimized on tray?
I'd like to know what motherboard Grandpa is using!Quote:
Originally Posted by unclewebb
Version 2.60 does start minimized with the proper options set in both Vista x32 and x64.Quote:
Originally Posted by unclewebb
@unclewebb i know that Autostarts option ;) but could be nice that options in same progam [one marking and no more "drag and drop"]
About tray yea i don't had marked showing * in tray, so "Tray bar" was autodisabled ...now is great :)
If you have all 4 cores being shown in the System Tray then you can go into the System Tray menu and select Maximum and it will show you the highest temps for each core.Quote:
Originally Posted by Massive
Would you like to see the highest temp of all 4 cores in one system tray icon instead? I would need to add another option for that.
I kind of thought so. Thanks for the feedback. There haven't been too many complaints with the latest release but I try to track down and fix anything that is brought to my attention, either here or by direct e-mails. The timer on Grandpa's motherboard and many other boards is different than the one on my motherboard. It's simple to get accurate MHz out of my motherboard no matter what code I write but on other motherboards you have to write additional code to correct for errors in timing. CPU-Z is about the only program I know that gets this right on all motherboards. RealTemp still needs work.Quote:
Version 2.60 does start minimized with the proper options set in both Vista x32 and x64.
I sent you a PM Grandpa so you can try and provide me with some additional info. Thanks.
Yes, it would be nice to see the highest temp of all 4 cores on the system tray, so we can have a secure measurement of the proc temp.Quote:
Originally Posted by unclewebb
Or Is there anyhow I can make it show with the 2.6 version ? because so far I only see option to show a specific core number temp.
In 2.60 you can show the highest temp of each individual core in the System Tray but there is no way to show the temp of only the one highest core. I'll try to add a new feature for that.
Anyone that has problems with the CPU MHz option NOT showing the correct MHz can try running this testing app and post their results alongside what CPU-Z is saying.
http://www.fileden.com/files/2008/3/...z%20Tester.zip
I need some more data to try and get things sorted out.
http://img149.imageshack.us/img149/8...testingml1.png
My board is too consistent so it makes troubleshooting impossible.
I ran the RT MHZ tester, does it support multipliers that are not the default multi? I have a Q6600, with 8x multi and C1E/SS enabled. It got the FSB of 450 correct, but it used a 9x instead of the 8x that I use. This is on a DFI P35-T2R. I can post a SS later, I'm using RDC to connect to my PC to test it.