You will need at least Visual C++ 2005 for x64. Either that or mess with VS2003 and Platform SDK which always includes latest x86 and x64 compiler and libraries. However, I would recommend VS2005 because I am not sure if MFC version in VS2003 is x64 compatible.Originally Posted by unclewebb
Realtemp 2.0 reports 100C and 100C cores and 100C tmax for my Merom T7100. I ran the sensor test and it says, "Cannot perform test on mobile processors due to extreme heat."
e8200
33c and 22c.
4ghz 1.72vcore.
watercooling.
vista 32b sp1.
4670k 4.6ghz 1.22v watercooled CPU/GPU - Asus Z87-A - 290 1155mhz/1250mhz - Kingston Hyper Blu 8gb -crucial 128gb ssd - EyeFunity 5040x1050 120hz - CM atcs840 - Corsair 750w -sennheiser hd600 headphones - Asus essence stx - G400 and steelseries 6v2 -windows 8 Pro 64bit Best OS used - - 9500p 3dmark11(one of the 26% that isnt confused on xtreme forums)
Gigabyte Z68AP-D3i2500k@4.50 1.35+Thermalright Ultra 120-4x2GB G.SKILL@1600- Sapphire 5870 Vapor-x-TT Element G- Corsair Force 3 120 ssd+ 1 Tb samsung - Copperhead Mouse- LG 32 lcd+TT Toughpower 750W (Boinc id:kadireren team id:xtremesystems)
Q6600 @ 8x333 gives a tjmax of 85c.. I read your post here but don't understand why you'd give a b3 stepping a tjmax of 85?
Room temp is 16.1 °C for this screenshot (I drop the heat down to 61 °F at night in my house).
I found out that if I clicked on the "TjMax=85" it switched to 0x6F7 which according to processorfinder.intel.com is right for my chip.
Update: I figured it out... you're using two different TjMax values - one of which is incorrect. The one used to calculate the "core temp" is wrong @ 85:
...but the one used to calculate the "distance from TjMax" is correct:
![]()
Last edited by graysky; 03-05-2008 at 12:30 AM.
can somebody please drop a proper link to ver 2.0
just have downloaded from different posts above, i still get
( \RealTemp_1.1 - ZIP archive, unpacked size 122 302 bytes ) ?
and on load - it does not show v2.0 on its window (top) bar
/ like i can see (mr. graysky ) upper screens /
Thanks![]()
Maximus Extreme / Air // E8400 // Noctua NH-C12P
Asus 8800 ULTRA /Stock Air/
G.SKILL F3-10600CL8D-2GBHK
Tagan TG700-BZ // Antec P182 B
Rampage Extreme / Air // QX9650 // True120 Black
A-Data DDR3-1600G 3x2gb kit (using 2 modules 2x2b)
((CellShock (MSC CS3222580) ) dead
Sapphire HD 4870x2 (single) stock Air
Be Quiet! Dark Power Pro 1KW // HAF'932
@unclewebb: just out of curiousity, what now if the sensor in 1 core is stuck, does that warrant for RMA?
any chance of supporting pent "D"'s ???
anyways great work unclewebb and your efforts are apperciated
[SIGPIC][/SIGPIC]
PENT E8400 batch #814A014 ...4.3 at 1.34v~4.7 at 1.45v
FOXCONN MARS
COOLIT Eliminator 7*c idle~27~38*c load $95bucks !
BUFFALO FireStix's ddr2-800 do 1200 eazy at 2.1v
OCZ 2x2 kit pc2 8500 - 1066 @1069 atm
Quattro 1000W
Radeon 2-4850's in crossfire
OCZ Vertex SSD thanks Tony!
ALL PIPED INTO HOUSE AIRCOND ;}
*QUANTUM FORCE* saaya & sham rocks !
*REAL TEMP*
At least you've got some Xtreme software now for working in Xtreme situations! "Unclewebb" rocks !
*MEMSET* Felix rocks !
*SUPER TEC MAN* UncleJimbo rocks !
OVERCLOCKERS MAG..http://www.xtremesystems.org/forums/...d.php?t=197660
Both me and my friend(both of us got our e8400's from the same batch) get 0 sensor movement.
Any idea why?
Here, I've uploaded the realtemp 2.0
http://www.sendspace.com/file/368t2k
The zip file was just named 1.1, but the files inside were 2.0. That's how he could keep the link in the first post (and with all the other websites) without changing it.
my Q746A446 also showed 0-sensor movement...but in core1 onlywhat gives? what does it mean?
![]()
{2012 27imac-3.4i7-680mx-32gb ram-768SSD+External TB Samsung840pro ssd + TB velociraptors-Moto828mkIII/Marantz/Amphion Sound-HPzR30w 2nd monitor}
http://www.fileden.com/files/2008/3/...7/RealTemp.zip
The link in post#1 is working fine for downloading version 2.0
Now the question is how many people are having problems with their temperature being reported as DTS=0 or full temperature with version 2.0 as lasershock shows above?
Edit: I think problems were caused by the driver not getting initialized properly and my program not properly checking if it was initialized or not. In Vista you will need to run RealTemp as an Administrator to get it to work properly. Version 2.1 now does proper driver testing and will exit if it can't be found.
lasershock: Did previous versions work fine for you?
graysky: There are two versions of the Q6600, the early B3 and the later G0. I believe that the B3 like yours has a TjMax = 85C and the G0 has a TjMax = 95C. Just because CoreTemp has chosen a TjMax = 100C doesn't make it necessarily true. He has no documentation from Intel to back that up.
With my B2 E6400 I need an Idle Temp Calibration setting of ++ to get proper idle temperatures. If you set your B3 to this setting then do that low temp test again. Your idle temperatures will look very believable. Until someone points an IR gun at a B3 to confirm or deny things, I'm sticking to my TjMax=85C theory.
The Distance to TjMax number is just the raw DTS data read from the processor. How a program chooses to interpret that data will result in different reported absolute temperatures.
Absolute Temperature = TjMax - DTS
RealTemp and CoreTemp choosing TjMax that is 15C different is what causes your temps to be displayed 15C different by these two programs.
emoners: Intel will not do anything about a sensor getting stuck at low temperatures. They don't approve any software that tries to do anything with the data coming from this sensor. The DTS sensor is designed to control thermal throttling so as long as your processor doesn't catch on fire then it is working within the Intel spec and doesn't need to be replaced. If you are unhappy with a stuck sensor then your own recourse is EBay and then you can try and buy another one and see if that is any better.
HDCHOPPER: Unfortunately your 820 processor doesn't have a DTS sensor in it that any program can read the data from. I still think that the 65nm Pentium 4 has a DTS sensor but I haven't got any feedback yet to confirm this.
jaredpace: I disabled the sensor test on mobile processors because they don't have the kind of cooling a desktop processor has. This test is designed for desktop processors only. Did you try previous versions of RealTemp? Were they reading your temperatures correctly on your T7100? Can you post a screen shot? If previous versions worked then I will have to shoot the driver I switched to and bury it.
Are the problems only on Vista or does anyone with XP not have proper temperatures anymore?
Last edited by unclewebb; 03-05-2008 at 03:11 PM.
Thank You unclewebb !![]()
got new ver now , just run tests, heres screens if ya like to anlyze ..
MBO: Maximus Extrem / Bios v. 1001 / Air cooling / (No water on NB)
CPU: QX9650 [ Fpo: 742A758 ] (vCore 1.2375v manual in Bios) / Air cooling / TRUE120 / Skytce Minebea 120mm /1600rpm
RAM: CellShock (MSC CS3222580) Air cooling / OCZ XTC Ram cooler)
/ case : Antec P182 / side panel open
opsys : Win XP Pro Sp2
Idle ................... Load ........................ Sensor Check - seems like mine are stuck also![]()
![]()
![]()
![]()
Maximus Extreme / Air // E8400 // Noctua NH-C12P
Asus 8800 ULTRA /Stock Air/
G.SKILL F3-10600CL8D-2GBHK
Tagan TG700-BZ // Antec P182 B
Rampage Extreme / Air // QX9650 // True120 Black
A-Data DDR3-1600G 3x2gb kit (using 2 modules 2x2b)
((CellShock (MSC CS3222580) ) dead
Sapphire HD 4870x2 (single) stock Air
Be Quiet! Dark Power Pro 1KW // HAF'932
That looks perfect. Sticking DTS sensors was not an issue with the previous 65nm generation of chips. It is only the new 45nm E8x00 processors that seem to be having issues.
Both sensors moving 6 during that test is right in the middle of the normal range. You're probably using some decent cooling as well. With lots of core voltage and a poor cooler you can go over 10 in this test.
Dom7184: Have you ever tried doing the low temp test where you run at about 1600 MHz and 1.10 volts and check your idle temps. I have a B2 E6400 just like yours and I found that my computer would report below ambient idle temperatures during this test. The ++ idle temp correction adjusts my idle temperatures on that processor back up to reality.
Sorry for the dumb question: is this adjustement permenent and seen by any program or only done in your RealTemp?
I wish I can adjust the idle temp separately for any core as my E8400 has core0 lower 20 C° than core1 at idle![]()
Thanks anyway for this program that allows a new approach in DTS temps measurement.
Last edited by Brama; 03-05-2008 at 09:12 AM.
The idle adjustment only applies to RealTemp reported temperatures. If your idle temps are different between your two cores by 20C then that is a big red flag that core1 is stuck. What does the Test Sensor test show? There is no way to compensate for dysfunctional sensors.
Any user having problems with v2.0 reporting 100C temperatures, just send me a PM and I'll work with you so we can try and find out what is causing the problem. The earlier version of the open source driver might work better.
That's exactly what RealTemp is all about.Thanks anyway for this program that allows a new approach in DTS temps measurement.
Last edited by unclewebb; 03-05-2008 at 10:49 AM.
I had a look at things and the only thing that I noticed that might be causing problems for users is if the driver is not being loaded properly then the program won't be able to read your temperatures and will display 100C. I added some code to prevent the program from starting up if it has any issues with loading the driver.
The driver might not load in Vista if you are in a limited account.
This is my best guess. Version 2.1 is now available if anyone having problems wants to try these theories.
http://www.fileden.com/files/2008/3/...7/RealTemp.zip
Bookmarks