@ uncle: what is the latest release? can you give me a stable link where i can always get the latest version?
however i need to know what do the 'clock modulation' feature o the 3.00 version ... :) Thanks ;)
Printable View
@ uncle: what is the latest release? can you give me a stable link where i can always get the latest version?
however i need to know what do the 'clock modulation' feature o the 3.00 version ... :) Thanks ;)
The latest beta is always available here:
http://www.fileden.com/files/2008/3/...alTempBeta.zip
Version 3.00 is the last official version and it is available at TechPowerUp.
http://www.techpowerup.com/realtemp
Clock Modulation is an Intel term. It was designed by Intel to give a user a way to reduce the temperature of their CPU while at full load. When enabled, internally your CPU will do less work and will run cooler at full load.
Here's the official Intel explanation if you're interested:
13.5 THERMAL MONITORING AND PROTECTION
http://download.intel.com/design/pro...als/253668.pdf
If you had a CPU running at 3000 MHz and you set the Clock Modulation to 50% then it would run the CPU at half power or at the equivalent of about a 1500 MHz CPU. The 87.5%, 75%, 62.5%, etc. are Intel approximations. The RealTemp load meter will show you a more accurate % for how hard your CPU is really working when modulated. Run Prime 95 Small FFTs and play around with the Clock Modulation settings.
So far only one user has told me he uses this feature. He had a laptop and when watching a movie he sets it to 87.5% which saves some power and allows his movie to play fine without his laptop burning through his lap.
I thought it might be useful when testing an overclock. If your 3000 MHz CPU runs Prime stable at 4000 MHz most days but seems to crash on hot days, you could try running at 87.5% or 75% to keep the heat down and try to isolate your problem. Technically speaking, it's still running at 4000 MHz but will be ignoring some of the internal clock pulses so it won't be working as hard or creating as much heat internally.
This might also be handy for those that like to fake screen shots. You could run LinX on your Core i7 and CPU-Z could report your super high MHz while Core Temp or RealTemp was reporting a nice and low core temperature. The load meter in RealTemp would show that something isn't quite right but traditional load meters would show your CPU working at 100% even though it is not working that hard internally when Clock Modulation is going on. Here's Prime 95 Small FFTs on all 4 cores. My air cooled Quad runs super cool when fully modulated. :)
http://img15.imageshack.us/img15/3276/loads.png
You can also try running some Super PI 1M benches at different Clock Mod settings. Performance will definitely take a hit.
Thank you :up:
http://www.fileden.com/files/2008/3/...alTempBeta.zip
One user running XP x64 had trouble with RealTemp starting up so I got rid of the check for thermal sensors which didn't seem to be working properly on his computer. I went back to my previous start-up code which seemed to work.
Other than that, same old stuff. I noticed one user on XS has a new Core 2 Quad processor that isn't being properly detected. I saved a screen shot of it somewhere but I can't remember where the hell I put it at the moment. :) Edit: Found it! radaja on the UTP35 thread has a flaky bios which caused this issue.
If you see any screen shots with the model number missing, post them here so I can have a look.
Pardon me if this has been answered before or if it's a stupid question but what does Real Temp do when the CPU enters PROCHOT? Does Real Temp actually query the register (is it even a register?) or does it just go by the distance to TjMax?
thanks Uncle :)
Uncle, when I exit the latest beta Windows Vista 64 tells me "realtemp has stopped working". Any idea why this is?
What version number is displayed in the About... box of RealTemp?
Version 3.20 RC3 is available here if you don't have it already:
http://www.fileden.com/files/2008/3/...alTempBeta.zip
If RC3 has this issue then I'll try sending you some test versions to see if I can find out exactly what the issue is.
I thought this bug was fixed but with XS down for a couple of weeks, maybe I just didn't hear about it.
Hi uncle :) Thanks for updates, :cool:
test-run RealTemp 3.20 RC3
Vista Home Prem. 32bit/ sp1 - Get this close (error?) message(s) -
1-st(first) popup says : RealTemp stopped working , Windows is checking solution ..
2-nd : 'a problem caused the program to stop working correctly,
windows will close the program and notify .. solutions ... bla , bla
:shrug:
---------
Xp-Pro32bit/ Sp3 - NO Problem :) NO messages :up:
----------
// W7 - Not Tested //
thanks for the update
Here's what makes programming fun. I'm using Vista Ultimate x86 (32 bit) as well as Windows 7 (64 bit) and have never once had an issue closing RealTemp.
i43: Hopefully you have some time to help with finding this bug. I almost had this solved about the time XS went on holidays. When RealTemp closes, it tries to be OS friendly by freeing up memory and resources but it seems to be freeing up something that it shouldn't be in Vista.
I'll try writing a version that goes through the closing procedure step by step to hopefully figure out the exact line of code causing the issue. Ever since I started trying to do things by the book, I've been creating obscure bugs and issues. Writing code randomly off the top of my head seemed to work much better. :)
Realtemp 3.20 RC3 Works fine with XPSP3.
but in Windows 7 Build 7068 it didn't show up. you can only see it in taskbar.
http://img411.imageshack.us/img411/8...ghzthorsha.png
thanks for the hardwork uncle! :up: :worship:
Time to plug in my Win 7 drive for some testing.
uncle what's the tjmax for i7 920 D0?
thanks! :)
http://img528.imageshack.us/img528/6730/win7rc3.png
Using Windows 7 (x64) Build 7000, I downloaded RealTemp 3.20 RC3, unzipped it into a new folder and started it up and it popped up in the middle of the screen like it should.
DJSUB: Could you try downloading RC3 again? Either that or go into the RealTemp.ini file and delete the entry for WindowXY. If this value gets screwed up it's possible that RealTemp might disappear somewhere when you open it so it will appear in the Task Bar area and in the System Tray but you won't be able to see it on your screen. This is somewhere between an obscure feature and a RealTemp bug. Let me know if you get this figured out. I don't have Build 7068 to do any testing with.
As for TJMax, that information is stored within the CPU in Core i7 processors and RealTemp or Core Temp should be able to read that value correctly. In the RealTemp Settings Window you should be able to click on Defaults and it will set TJMax to the appropriate default value. All of the C0 CPUs that I've seen are set to TJMax = 100C by Intel but I've seen a couple of D0 CPUs that were TJMax = 92C or 93C. I think those were both ES engineering sample processors though. So far, the retail CPU screen shots I've seen for the new D0, have all been TJMax = 100C. I added some code to RealTemp a while ago so if you switch CPUs, it should automatically check to see if TJMax has changed.
When comparing temperature programs I like to use Prime 95 Small FFTs. It puts a consistent load on the cores so all programs should report pretty much the same thing. If the APIC ID is not sequential in the Settings window then it's possible that RealTemp will report core temperatures in different positions than the competition does but that's a feature, not a bug. :)
Yes it's RC3 Uncle.Quote:
Originally Posted by unclewebb
Hi, I have a similar problem to i43
I'm running Windows 7 7077 x64. RealTemp (3.20 RC3) opens correctly and displays temps. But when exiting, i get a popup "RealTemp has stopped working"
http://img147.imageshack.us/img147/1830/25098907.jpg
Hey Unclewebb !
keep your new RT builds coming :) currently have such equipment, 3 separate machines i have access and ready to test new versions
-1- Quad qx9650 - ( multi boot ) 1) Xp-Pro 32bit (sp3) / 2)Vista Home Premium sp1 32bit / 3)W7-b7000 64bit
-2- Dual E8400 - 1) Xp-Pro 32bit(sp3)
-3- (Dual) T5500 - 1) Vista Home Premium Sp1 32bit /laptop/(fujitsu simens Amilo)
:)
+edit adding /
booted quad from W7 64bit (b7000)
RT 3.20 RC3 - all seems working ok but on close[x] getting same error as PyrO
http://img26.imageshack.us/img26/539...rc3test.th.jpg
//direct link: http://img26.imageshack.us/my.php?im...320rc3test.jpg //
http://www.fileden.com/files/2008/3/...alTempBeta.zip
I think I found the bug that was causing a crash when closing RealTemp.
If you had problems before then try RC4 and see if your problems go away.
RealTemp 3.20 RC4 - seems like all OK ! working :up:
anyway ..so far did not notice any problems on these ...
-1- Quad qx9650 - ( multi boot )
---A) Xp-Pro 32bit (sp3) / (ATI 4870x2 ..ccc9.4
---B)Vista Home Premium sp1 32bit / (ATI 4870x2 ccc9.4)
---C)W7-b7000 64bit / (ATI 4870x2 - default driver
-2- Dual E8400 - 1) Xp-Pro 32bit(sp3) nVidia 9600GT Fw 182.50 xp
-3- (Dual) T5500 - 1) Vista Home Premium Sp1 32bit /laptop/(fujitsu simens Amilo) - (Mobile intel(R) 945 Chipset Family)
-----
CY :)
Thanks for your help testing this i43. I went through RealTemp trying to make it more efficient by freeing up any unused resources. I hate memory leaks.
When using an ATI video card, RealTemp RC3 was freeing up the same block of memory twice, once during initialization and again after clicking on the exit button. In programming, freeing up the same block of memory twice is definitely not a good thing. RC4 should be all better now.
I added a new System Tray menu item so it moves RealTemp up to the upper right corner and out of the way. That's where I like it so it doesn't get in the way when it's not minimized.
exiting works without error now. thank you unclewebb :up:
tested on the sys in sig, using win7 7100 x64
[edit] liking the new option to put the window in the top corner too :)
Just to congratulate you on some kickass software.
And tremendous work keeping it bug free. ;)
thanks for the 3.20 RC4 uncle! :)
it works fine now with 7068 windows 7 :up:
keep up the good work uncle! :worship:
No errors at all with win7100 x64.
ty sir.