Count me in too. :)
http://i48.tinypic.com/2nleikx.jpg
I only change my GTX260 with an HD5850 and a couple of days ago Seven x64 made some updates.
Printable View
Count me in too. :)
http://i48.tinypic.com/2nleikx.jpg
I only change my GTX260 with an HD5850 and a couple of days ago Seven x64 made some updates.
Compatibility mode to Vista worked, thanks for that solution, atleast for now =)
Any support for Caspian Processor and Mobility Radeon 4200?
Thanks
RealTemp 3.56
http://www.fileden.com/files/2008/3/...alTempBeta.zip
Finally got around to fixing a few bugs like the half multiplier bug in 3.50RC6.
The ATI GPU monitoring code is now optional since it seemed to be causing too many problems for too many users. It's always worked fine for me.
Here's how my Sapphire Vapor-X 5770 card looks.
http://img251.imageshack.us/img251/4017/realtemp356.png
You will need to add GPU=2 to the RealTemp.ini file to see if this code works for your ATI GPU. The default is GPU=1 for Nvidia cards. GPU=0 can be set if you don't have either type of card or if this code causes any problems.
GPU=3 can be used if you have one of each type of card such as if you are using an ATI card plus an Nvidia card for Physx. Click on the GPU button twice to see if it can read both of your cards.
I don't yet have access to a second ATI GPU so CrossFire support is still in the future.
I just updated Windows 7 x64 with all of the latest and greatest recommended patches from Microsoft but I haven't been able to duplicate any crashes that users have reported. I'm hoping that separating the ATI code might help isolate some of these issues. Thanks randomizer for finding a quick work around to this issue.
I haven't tried installing this optional update yet. It looked dangerous. :)
http://img9.imageshack.us/img9/1893/puke.png
Sorry jcmarfilph, there's no planned AMD support.
It appears as though that's the first one Windows installed for me (in October). So it can't be related, since the issue only started recently. I'll have to look at other updates to see if they may be involved.
If you're having crashes, I recommend updating. It fixed the problem I was having, even though I didn't have it initially.
I have a 4670 or two 4890's for short term loan if that would help you out. Lemme know and I'll take a drive out there.Quote:
I don't yet have access to a second ATI GPU so CrossFire support is still in the future.
Ol'Baditude: Thanks for the offer. I'll send you a PM to discuss further.
Added the line and these are my results:
GPU1: 48
GPU2: 48 -don't know why RT sees that as GPU3.
Which is not correct. One of my GPU's is hotter and Afterburner shows the correct temp as 51. Bottom right corner.
If you click on that GPU3 what do you see?
Those two temps of 48 degrees are minimum and maximum, not gpu1 and gpu2. Click bottom right button which says gpu3 (same as RT) and you'll see other gpu's temp.Quote:
Originally Posted by Wishmaker
EDIT: @burebista: you were quicker! :clap:
The temps are identical. This is not my first BBQ lads and Afterburner does not agree with the temps ;).
***removed attachments because it was making a nasty layout :(.
Thanks Wishmaker. I think part of the problem is that RealTemp is trying to be too friendly. With two GPUs at the Desktop, the ATI driver tries to put one of the two cores to sleep to reduce power consumption. The driver blocks RealTemp from reading the core temperature of each core when this happens. Originally I didn't want to keep waking a sleeping core up to sample its temperature since I thought that was kind of pointless and would defeat ATI's power saving mode.
I might try to come up with a user option to do this for those that want to see the temperature of each core in 2D mode and don't give a crap about saving a couple of watts. I'll see what I can figure out this week.
If you have the time can you go and play a 3D game that uses CrossFire and then go back to the desktop and see what RealTemp says for both GPU cores. Maybe reduce the Read Sensor Interval down to 1 so it will have a better chance of reading the maximum temperature correctly. It would be interesting to see how that compares to Afterburner.
Quote:
Originally Posted by unclewebb
As instructed, captain :ROTF: :
At startup :
http://i266.photobucket.com/albums/i...lTemp/th_1.jpg
After a few minutes of Mass Effect 2 (everything on max, 1600x1050+ forced max AA in Catalyst Control Center), best game out there if I do say so myself :)
http://i266.photobucket.com/albums/i...lTemp/th_2.jpg
I think it reads the same sensor on both GPUs. It does not differentiate between the two. I always have a hotter one because it is a bit choked :). As you can see, one of them is dead accurate. We will let that 1 degree delta slip because it can be the margin of error but the second registers the same :(.
P.S: I am using Catalyst 10.2 which on my setup does not shutdown the second graphics card. I hate that feature because it locks the fan at 19% and the temps go up to 70 degrees idle. So I avoid drivers that have that feature. Both cards are using the same power at idle there is not uber crossfire power saving mode. Both downclock to 240 ;)
You've motivated me to look into this issue some more. I must be doing something wrong.
Maybe my local store has one more Vapor-X 5770 card in stock. Don't tell my wife. :D
My lips are sealed. Tell her a friend gave it to you ;). This seems to be the most common excuse when it comes to buying stuff behind 'her' back :rofl:.Quote:
Originally Posted by unclewebb
http://img706.imageshack.us/img706/457/atioverdrive.png
I don't feel so bad now. A friend lent me his 5770, ;) and when in Crossfire mode, Catalyst Control Center doesn't report anything for MHz or temperature for the second card. The first card is reported fine.
RealTemp uses the CCC libraries to get temperature information so I'll see if I can find a way to get data from both GPUs even when one core is having a snooze. CrossFire support is a work in progress.
Quote:
Originally Posted by unclewebb
What Catalyst are you using? 10.2? Its that damn power saving feature :down:. There was a registry edit for that ....but can't find it now :(.
Catalyst 10.2
I think different catalyst versions play different tricks with different GPUs. At least with some hardware to play with I might be able to figure this out.
I'll keep my eyes open for a registry fix.
Cool! GPU support works for my Sapphire Radeon HD 4850x2 card now... albeit just for the first GPU on the card, but that's great! Using Catalyst 10.2 on Win7 x64 by the way.
Uncle,
I found the fix on the guru3d forums. See if this works ...
http://forums.guru3d.com/showthread.php?t=307309
http://www.fileden.com/files/2008/3/...alTempBeta.zip
http://img707.imageshack.us/img707/1641/realtemp358.png
This version has improved ATI CrossFire support. I added a few more details like Clock and Memory speed, etc.
On my 5770 cards it's able to read the temperatures and details for each individual card.
If you have an ATI card or cards then you can try this new code by adding this to the RealTemp.ini configuration file.
GPU=2
I haven't heard back from any testers yet so give it a try and let me know if it works on your system or if you have any problems.
Wishmaker: Thanks for that tip. I found the easiest thing to do was to search through the Registry for EnableUlps and I changed each value to 0 to disable or to 1 to enable this feature and then did a reboot after that.
http://img14.imageshack.us/img14/9752/enableulps.png
RealTemp respects whatever setting you choose. If you don't like having access to the GPU 2 data blocked by the driver then set EnableUlps to 0 to get rid of that power saving mode. With a Kill-a-Watt meter I measured a savings at idle of 3 or 4 watts so it doesn't make a huge difference.
When both GPUs are reporting temperature data, RealTemp should display the highest current GPU temperature on the main screen and in the system tray.
If you don't have access to both GPUs then I found just starting Furmark was enough for the second GPU to wake up. You don't need to click on the GO button and start Furmark rendering, just having the GUI visible or minimized is enough to keep the second GPU awake for testing purposes. When EnableUlps is enabled, about 30 seconds after you close Furmark, if nothing else is using GPU 2 then it will stop reporting temperature and MHz data.
You the man uncle ;).
http://i266.photobucket.com/albums/i...byte/th_RT.jpg
Where do I send the beer? :up::up:
P.S: Finally the thumbnail option works on XS. For some reason I could not hotlink pics like this :(.
P.P.S: You won't have optimum CFX performance uncle :(. Your second card is hooked in a x4 slot not a x8/x16 :(.
That's great news. Thanks for the feedback.
I was hoping no one would notice that. I'm using an antique board with the P965 chipset. It overclocks Core 2 Duo CPUs like a beast but its CrossFire support is crap. All you get is x16/x4 which obviously doesn't let you take full advantage of CrossFire.Quote:
Your second card is hooked in a x4 slot not a x8/x16. :(
What do I need now? An X58 board so I can go x16/x16? I haven't explained either 5770 card yet so I think I better wait a bit before the next round of upgrades. I still have to beat my wife to the mail box so I can get the X25-M that's on its way. It's nice and quiet. She'll never know once that's hiding inside the case. :D
Quote:
Originally Posted by unclewebb
Thanks for taking the time to add this. You pointed out that you added more features, including info about the video setup, so don't blame me :rofl:. That SSD will make a lovely addition to your system and about the mailman, you are on your own. Hell hath no fury ... :rofl::rofl:
Works great with my quadfire, every GPU is listed!
awesome job unclewebb!
Greetings unclewebb. First, I just want to say thank you for an awesome program. I've been running a Gulftown for a while and I notice running RealTempGT only gives info on one GPU, unlike RealTemp will give info on 4 GPU's. I don't know if I missed something :confused:
This one is small, with RealTemp 3.58. I can't change the font color for core #4. I can change it, but when I restart RealTemp it does stick. All other cores are fine, maybe it's just me. RealTemp 3.56 worked. Sorry to PIA.
I'm running EVGA 762 & 759 with Dual 295's (Dual PCB). Thank you :)
(These temps are not correct. Something is wrong with CPU senors)
http://littlekitty.smugmug.com/Other...7_gUmbD-X3.jpg
CKY2K: I always appreciate hearing about bugs. There was one recent bug with colors not being saved correctly for the system tray which I fixed for the GPU but I'll have another look at that to make sure colors for all of the CPU cores are being saved correctly.
RealTemp GT was a quick one off special for Gulftown users but there hasn't been much feedback so I haven't got around to updating it with the more recent Nvidia or ATI code. I'll look into updating that in the near future.
21 & 35 C,not so good :shakes:
(max 24-43 C :down:)
Thanks for the quick reply unclewebb :)
(I don't mean to go off topic)
stasio: :yepp: yeah for the fist week the temps looked about right and then after that, they were way off. I'm not sure what happened. I just posted that screen shot so unclewebb could see what I was talking about (the GPU's), as you can tell I'm not to good at explaining things.
Intel's new 35nm temperature sensors seem to have a lot of error at idle and many of them read way too low.
Intel writes TJ Target information into each core of each CPU but TJ Target isn't always equal to TJMax. Actual TJMax might be 10C or more higher from one core to the next even though they all have the same rating of 105C for this CPU. With undocumented sensors like these, accurate temperatures aren't possible. The 45nm Core i7-920 sensors were some of Intel's best, very consistent. These new sensors are at the other end of the spectrum. The new Core i3 32nm CPUs have similar issues.
Edit: Another problem is that these CPUs are designed to turn individual cores off at idle or when lightly loaded. This can also lead to a lot of temperature variation from core to core.
Thanks you for info unclewebb :).
does anyone have or know the max temps for the i3-530-540's are?
i cant find this info anywhere.ive seen people go above 70c but im still
to much of a chicken to let it go above 65c.please help bak bak bah
Have a look in the Settings window at what RealTemp shows for TJMax. That information is read directly from the CPU and I think for most of the new Dual Cores it is 105C. This number can vary from one CPU to the next. A core temperature of 70C isn't going to hurt anything. When it hits 100C, give me a call. :)
Here's what I found last night when reading the docs:
Intel® Core™ i7-900 Mobile Processor Extreme Edition Series,
Intel® Core™ i7-800 and i7-700 Mobile Processor Series Datasheet
Volume 1
6.8 Error and Thermal Protection
http://www.intel.com/products/proces...e/techdocs.htm
http://img684.imageshack.us/img684/5931/thermtrip.png
Thermal shut down doesn't happen until 130C on these new chips. Lots of head room so don't be afraid to use it. PROCHOT# is triggered when the Distance to TJMax number in RealTemp counts down to zero and then typically 25C hotter than that is when THERMTRIP# is set and the CPU will quickly shut down your computer.
awesome thanks for the info and reassurance's unclewebb
I think I hit jackpot with TIM application this time ;). I broke a Venomous X but that is not important at the moment :p. Almost identical temps on all cores ;). I've never had them so close to one another. Guess that Chillfactor 2 is good for something ;).
http://i266.photobucket.com/albums/i...abyte/RT-1.jpg
where's 3.58 version? nm , found it....uncle doing great job !
It's a BETA versión. You can get it here:Quote:
Originally Posted by TEDY
http://www.majorgeeks.com/download6098.html?2009-10-16
They're all beta versions. Some are just less beta than others. :DQuote:
Originally Posted by rhpsystems
No major complaints with 3.58 so maybe I will call it 3.60 in the near future.
:D Good explanation unclewebb. I'll wait for next "less beta" versions :up:Quote:
Originally Posted by unclewebb
I have dumb question to ask! Does setting of the TJMax vaule have an effect on the temp readings reported by RealTemp?
Yes
Reported Temperature = TJMax - Digital Thermal Sensor Reading
Any software can read the sensor accurately but many monitoring programs can't agree on what TJMax really is so they end up reporting different temperatures.
Intel doesn't use a sensor that reports the core temperature directly. It's a sensor that works the opposite of a thermometer. As the CPU gets hotter, the DTS counts down towards zero. When it reaches zero, your CPU will be at its maximum safe operating temperature and will start to thermal throttle and slow down to protect itself from damage. The temperature this happens at is called the maximum junction temperature or TJMax for short. If you know core temperature of the CPU when it starts to thermal throttle then you can work backwards and with the above formula you can get an approximation of the core temperature when you are at temperatures less than TJMax.
Intel doesn't have any exact numbers for TJMax since it can vary somewhat from one CPU to the next and even from core to core on the same CPU. At one time they released some data and they called it TJ target. TJMax is somewhere in the general neighborhood of TJ Target but Intel left out details like the amount of error in this number, etc.
The newer Core i CPUs have TJ Target written into each core of the CPU but the same problem arises. If Intel does not say how much error is in this number then it's a bit meaningless but better than nothing and better than Core 2 based CPUs where software could only guess.
For a QX9770, actual TJMax might be anywhere from 95C to 110C on individual cores. At full load running Prime95 Small FFTs, if you notice that your core temps are all over the place, that's generally the reason why. Life would have been much simpler if Intel used a traditional thermometer like GPU manufacturers use.
I just wanted to report that the latest version doesn't recognize the gpu temp of a Gigabyte 5870 Ultra Durable.
http://www.pctunerup.com/up/results/...20153714_b.jpg
Did you do this?
Quote:
If you have an ATI card or cards then you can try this new code by adding this to the RealTemp.ini configuration file.
GPU=2
Thanks a lot, it worked. :up:Quote:
Originally Posted by burebista
Thanks UncleWeb, great program. TBH, I rarely used it since my CPU temps were always under control with a modest OC. But since I found it has an alarm function for GPU temps, its became a necessity. I've had issues with autofan control with some drivers and MSI afterburner and this comes in handy when temps go out of control.
Any way we can choose fonts for the tray icon? The default font looks a bit scraggly. Thanks.
You're welcome aamar. RealTemp offers a couple of system tray font choices in the Settings window but I agree that it is limited. The problem is that the system tray is only 16 x 16 pixels wide so it is very difficult to find a font that looks good and fits in that limited area. The other problem is that RealTemp's system tray fonts are not anti-aliased so they look a little rough and blocky. I might look into this again someday but with a limited number of pixels, there's not a lot you can do.
Uncle wouldn't be useful to write in the first thread how to start RT with Windows 7?
That sounds like a good idea. I wrote a nice tutorial a while ago about doing this by using the Task Scheduler so I might as well post this link on the first page so users can actually find it.Quote:
Originally Posted by Razer(x)
http://www.xtremesystems.org/forums/...postcount=3657
Edit: I just noticed. The link to that tutorial is already in the first post of this thread.
iddqd: Maybe everyone can go to their local store and ask them, "What is TJMax?" and drive them nuts instead of me. :rofl:
Hahaha! :rofl: :clap:Quote:
Originally Posted by iddqd
Thanks Uncle for a sweet program. Didn't know if you were aware that on version 3.58 at least on mine that I have one core that will not retain the color setting on my task bar.
Each time I have to go into setings and redo. No big issue but wanted to let you know.
I thought I fixed that but I guess not. I'll have to have another look. Thanks for the bug report.
Hey uncle,Quote:
Originally Posted by unclewebb
Sorry to pester you but I also noticed something odd. I tell windows 7 not to hide my icons ...yet one core seems to disappear :(. All of them are set on always show. If I delete RT, extract it again, things return to normal ... for a while :shrug:
Thanks for the feedback Wishmaker. The funny thing is that I haven't changed anything to do with the system tray icons in a long, long time. Last time I looked at this problem, it seemed to be a Windows 7 bug. If I set W7 to show all icons then it works 100% correctly but if I try to use W7 to only show some of the icons then it seems to be unable to remember my choices for what icons I want displayed and will hide one of the RealTemp icons. I don't think there is anything I can do to solve this W7 related issue. It's also impossible to organize the cores in W7 like RealTemp is able to do in Vista or XP. :(
I complained to Microsoft during W7 beta testing about some of the changes they made to their new and improved "Notification Area" but they must be saving some fixes for SP1 or SP2. W7 assumes that a program should only place one icon in this area so where it gets inserted isn't important and if a program tries to insert multiple icons; if W7 displays 3 out of 4 or 4 out of 5 then it considers that to be good enough. Try switching to "Always show all icons" in the Notification Area and see if that fixes RealTemp.
http://img213.imageshack.us/img213/3273/w7bug.png
There seems to be some sort of feature in W7 that when this box is not checked, icons can disappear randomly and their status changes from "Show icon and notifications" to "Only show notifications". If you don't check this box then every time this happens, you need to click on the little triangle and grab the icon it just hid and drag it back onto the system tray where it belongs. I prefer to check the box.
in w7 you can manually drag and rearrange systray icons just like you are able to with the taskbar icons. that may help but it's just a workaround.
Cheers for the replies guys. I will try your workarounds ;).
Hey,
By any chance is there a update in the works so real temp reads the 980x correctly?
I've tried a few different versions with no luck. Currently it only seems to read 3 cores. core 0,1,2.
The temps though are pretty much spot on for the 3 cores its reading. These are pretty cool running chips I gotta say... :cool:
Have you tried using RealTempGT? I believe that this is the version for the GulfTown chips.Quote:
Originally Posted by zillaoc
P.S. It should be in the same folder as RealTemp, if you have a near current version. Uncle distributes them in the same download.
/slaps head...Quote:
Originally Posted by Raptor-X
Works perfectly...
Here's a quick screenie after running prime/smallFFT's for a minute.
The chip/mobo/ram/video card are brand new, I'm letting the paste cure on the mobo n chip b4 clocking it.
p.s sorry for the wide pic...
http://vizmu.com/static/cool2.jpg
You cool it with frozen water? You live into an igloo? :D
Looking good. Glad it worked out for you. Enjoy.
The entire rig minus the hd's and pump is inside this thing. That is a old ss though. Its been modded a ton since...Quote:
Originally Posted by burebista
http://www.xtremesystems.org/forums/...50#post2898350
:worship:
Hehe, I wasn't too far in my assumption. :D
Hey unclewebb,
thought I'd check back in here to see how you are doing :)
Sorry I haven't been giving any feedback lately, I remember when you made RealtempGT just for me back in Autumn 09 :D :up:
I have been using an old 3,30 Beta ever since, and it worked fine. Now I do have a few new chips, so I thought I'd update and see what has changed.
Does the attached screen look right to you? I kinow sensors 4 and 5 are kinda broken, but I think the rest is spot-on. Running fully-loaded on chilled water (14-17C water).
As always, thanks for the great program!
My best guess is that TJMax is not consistent across all of your cores. With the cores numbered from Core 0 to Core 5, I'd bump up TJMax on Core 3 by about 10C or 11C and I'd bump Core 4 by about 6C. That should make all 6 of them line up pretty good. They might even be more accurate too. :)
Prime95 Small FFTs is still the best program for equally loading each core. When you do that, most of the difference you see from one core to the next is error in how Intel sets TJMax.
A TJ target number is written into each core so in theory Intel could use a unique TJ Max value for each core but they don't bother. They just write a consistent value into all 6 cores even though actual TJMax varies a little from one core to the next.
I'll try to get RealTemp GT updated someday in the near future with better CPU name recognition and some of the newer GPU code but other than that, it looks like it still works.
Unclewebb,Quote:
Originally Posted by unclewebb
thank you for your suggestions, but too late - I already swapped the CPU for the other X5680 (it's a pair, waiting on the DP evga board) :D
This CPU is way better, but two sensors are also off the mark - different ones this time.
In this shot I am running prime SmallFFT, and your latest RealTemp version. Also, I set TJmax manually to 105C because Dave said that's what he got as a number from Intel.
So, what should I adjust here, if anything?
Thanks :)
http://database.he-computer.de/Bilder/temp/RT3.jpg
TJMax is written into each core by Intel so I'd trust that as a starting point. Hitting the Defaults button in the RealTemp Settings window should reset it to the default TJMax. RealTemp reads that value OK.
The slope error in these new sensors is much greater than the slope error in the 45nm Core i7 series. You would need to get your core temperature up to about 70C before slope error becomes a non issue. Most of the difference from core to core at that point is error in TJMax.
The easy thing to do is to run Small FFTs until the temps stabilize and then add on a few degrees to the center cores until the temps across all 6 cores are fairly well balanced. It will make things look nice if nothing else.
It's too bad that Intel has taken a step backward with these latest sensors. With 6 cores and 12 threads at 4.5GHz+, there probably won't be too many complaints. :)
Hello Uncle( Jeez that sounds strange!:DQuote:
Originally Posted by unclewebb
Running RealTemp GT 3.40 on my dual Westmere SR2 rig and defaults show a TMax of 101C.. I thought it was 105C..
Now how do I monitor all 12 cores as the app just shows 6 ?
Am I a clueless n00b?
Thanks for a great app.:up:
If I may... Try this http://www.xtremesystems.org/forums/...trail&page=105 until unclewebb answers you. It is meant for skulltrail, but it might work.Quote:
Originally Posted by Movieman
Err.. I discussed that very issue with unclewebb some time ago. We got it to work by copying the realtemp folder, changing a setting in each folder's config file (something like "CPU=0" for one and "CPU=1" for the other IIRC).
So you basically start up two instances of RealtempGT, with one displaying CPU 0 and the other CPU 1.
What's up doc? :)
I'm using Real Temp GT3.40 with X5650, and the TJ Max is 96 by default. Do I have to change this? I hope not, I'm very happy with the low temp.
Monstru: The Atoms don't use the same high performance timers that other Intel CPUs use. Try adding MSRMulti=1 to the RealTemp.ini file and it might show you a multiplier using the old method and report your correct MHz.
The load meter probably doesn't work either. You can check off TM Load in the Settings window and it will try to use a load meter based on the task manager load meter. Same problem as above. No high performance timers in these CPUs.
I just checked the Intel docs and it says the D510 has a thermal spec of 100C so you would need to change that in the Settings window too. Your temps might be a little closer to reality but probably still a little out to lunch unless you've moved way up North. I'll blame that on crappy sensors.
Can you tell I'm not a netbook fan and I have absolutely no love for the Atom line of CPUs? :)
Sam_oslo: RealTemp is reading the 96 value from the CPU but there's no guarantee that it is 100% accurate. Intel calls the number within the CPU that RealTemp reads a TJ Target number and actual TJ Max may be higher. They've never said how much higher so actual TJMax might be 100 or 105 like many other Intel CPUs. By writing information into the TJ Target register, Intel is in complete control of what your CPU reports for temperatures. If they write a low ball TJ Target number in that register then all software will report that you have a cool running CPU.
My apologies to the 12 core Westmere guys. Send me some hardware and I'll get to work on a 12 core version of RealTemp GT.
Yes boss, but this is not a notebook, and this is a dual-core Atom with hyper-threading (hooray) :D
RealTemp 3.58.2
http://www.fileden.com/files/2008/3/...alTempBeta.zip
It might not be a netbook but I still don't like it. :)
I'd rather have a Core 2 Duo and if I wanted to have a low power C2D, I'd just under volt and under clock it, preferably using my new ThrottleStop tool.
I gave RealTemp a tweak or two to try and better support the Atom family.
What's your room temperature? I'm curious to see how far out your core temperature is even with the Intel specified TJ value. At idle in an open case I think the actual peak core temperature should still be about 5C over the air temperature.
25 oC room ambient, the sensors are way off. I'll try the new RT version and report at the beginning of the next week, I will be away for a few days.
Regarding C2D vs Atom, well, C2D has huge performance compared to this little guy, but you have to give it to the little guy... only 50W drawn from the wall in full load, for the whole system. It doesn't get much "greener" then that :)
RealTemp 3.58.3.....(?)
http://www.fileden.com/files/2008/3/...alTempBeta.zip
3.58.3 contains a tiny fix to support Xeon Dual Core CPUs when you are running two of these on the same board.
The Skull=3 INI option handles this combo.
thx! 3.58.3 works grate :up:
the only thing that RealTemp is missing, imho, is a feature that allows one to see max temperature between all cores displayed in a single tray icon; adding this would simplify day to day use of this app :yepp:
my 2 cents: safe stress-testing with RealTemp
i use this simple code in a .bat file to stop active stress-testing if it exceeds my criteria for maximum cpu allowable temps.Code:@echo off
taskkill /F /IM prime95.exe
taskkill /F /IM linpack_xeon64.exe
taskkill /F /IM linpack_xeon32.exe
taskkill /F /IM linx.exe
echo %date% %time%
echo PROCESSOR HIT 85c! STRESSTEST STOPPED..
pause
note that you may be using other stress-testing software: for that matter, just copy the name, of the process that consumes 100% of CPU resources in your windows task manager, to the "taskkill /F /IM" line: you will be able to stop it when it reaches the alarm temperature set in RT.
to make this work you just need to:
1) copy the above code to a .txt file (create it in the RealTemp folder for easier handling) and rename it with a .bat extension.
2) open RealTemp, click on settings, then tick the "Alarm Temperatures" check box.
3) set the maximum allowable temperature that matches your criteria for safe stress-testing.
4) Click on the "Alarm EXE" button and in the "Open File to Run on Alarm" box change "Files of type:" to "BAT Files (*.bat)".
5) If you put the file in the RealTemp directory u will have to hit the F5 key to refresh, and then select the script you created in step 1.
test it before you run a real stress test: just set a lower temperature in the "CPU" "Alarm Temperatures" section :cool:
hope you find this helpful, i made this for myself, which is why i don't intend to get credit for this; just trying to be helpful to RT and the community.
What are the different exes for? RealTemp.exe, RealTempGT.exe, i7Turbo.exe... Can't find anything explaining what they do
You could always do something wild and crazy like try to run them and see what happens. :)
RealTemp GT is a separate version of RealTemp for the new 6 core Gulftown processors. It was the fastest way for me to create something for the 6 core guys.
RealTemp.exe is the main one for everyone else.
i7 Turbo is a separate program I wrote to give you a very accurate look at what each thread in your CPU is really up to. It's the most accurate tool to check for things like turbo throttling and can spot a problem before any other software will tell you about it. There is a separate thread for i7 Turbo somewhere on XS but I haven't been there recently.
http://www.xtremesystems.org/forums/...d.php?t=225450
vodka3dg: Excellent suggestion. :up:
lol yeah but GT and non-GT looked pretty much the same so I was like ?? and i7Turbe wasn't reporting any Min/Max values so was wondering if I actually need an i7 for it (have i5 750)
Hey Uncle, thanks for keeping this great util going :)
I have the parts for my new Gainestown dual Xeon in transit, will the standard version handle all 8/16 cores?
I will let you know how it works in a few weeks time!
i7 Turbo should work fine on most Core 2 Duos and the newer Core i7/i5/i3. When info doesn't show up in the Min/Max boxes it is because you have the Load Filter set too high. Set that to 0% and all info should show up immediately in the Min/Max boxes.
For Dual Quad Core systems, you should be able to use the RealTemp.ini options CPU=1 and CPU=2 to read each CPU. You will have to set up two separate RealTemp folders for this to work.
I need to add a similar option to RealTemp GT so the Gulftown guys can read both of their CPUs. Maybe someday.
BANNED until accomplised..:rofl:Quote:
Originally Posted by unclewebb
I think in the next month your going to see a lot of dual 6 core SR2 machines here my friend..;)
Any idea when the AMD Hex Cores will be supported?
RealTemp Beta 3.58.3 will not run using a 1090T in a Crosshair 4 890 FX Chipset.
I highly doubt that you'll ever see an AMD CPU monitored with RealTemp.Quote:
Originally Posted by unclewebb
You got buggy Core Temp 0.99.6 :(Quote:
Originally Posted by St4vr0s
Those new AMD Hex Core CPUs look very interesting and are at more of an enthusiast price point compared to the Core i7-980X.Quote:
Originally Posted by St4vr0s
Unfortunately, I haven't owned any AMD hardware in years and even if I had the hardware, I don't have the time for any new temperature monitoring projects. There's no money to be made writing free software and supporting the million and one Intel CPUs keeps me busy enough.
I've got a problem here, the gpu temp doesn't work
http://img191.imageshack.us/img191/6964/provap.jpg
Uploaded with ImageShack.us
Gotta change something?
Remove that semicolon in front of GPU=2.
Thx, i should know that :shakes:Quote:
Originally Posted by burebista
How about an option to have it start and run at different priority levels (high/low/normal/above/below/realtime)? :D
(I've tried doing "start /high C:\....realtemp.exe" from the command line and it still runs at normal :()
Tell me why you need to change the RealTemp priority and I'll see what I can do. I had to raise it above normal a long time ago because some programs like LinX were fully loading the CPU and preventing RealTemp from monitoring correctly. Anything less than its present default setting could cause a problem. There was also a bug in the Task Scheduler that lowered the priority of RealTemp to less than normal which wasn't a good idea.
I could come up with an INI file option to give you some more control of this. Just send me a PM and tell me what you need.
Hey, unclewebb, just to report, no problem reading GTX480 :up: ...but you probably knew that.
I'm always the last to know so thanks for the report.Quote:
Originally Posted by donmarkoni
Unclewebb, just wanted to let you know I'm still having issues with the font color with one icon on the task bar. It is always core 4 on my I7 980x. I'm using Real Temp 3.58.3 if that helps. Thank you for a wonderful program
and as always great support.
colt1911: The regular version of RealTemp looks fine but I finally found this bug in the RealTemp GT version. I'll get this taken care of in the next release of RealTemp GT.
In the mean time, you can go in to the RealTemp.ini file and edit this key:
IconTextColor4=0xFFFFFF
This keeps track of the system tray icon colors and is in a blue / green / red format. FF in hexadecimal is equivalent to 255 which means all that color.
0xFF0000 is a blue icon
0x00FF00 is a green icon
0x0000FF is a red icon
Save a color for the first icon using RealTemp and then just copy that value to all of the other IconTextColor values and maybe it will work.
Hopefully sometime this week I will get this fixed up along with a couple of other updates for RealTemp GT. It's been a while.
This seems to work okay but I also tried the GT version and it shows 6 cores (of my 8 real cores). The realtempGT.ini seems to have values for 8 cores ??Quote:
Originally Posted by unclewebb
Maybe next version :)