Automatic Temperature regulation

Message boards : Questions and problems : Automatic Temperature regulation
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3 · 4 · 5 . . . 12 · Next

AuthorMessage
Fred - efmer.com
Avatar

Send message
Joined: 8 Aug 08
Posts: 570
Netherlands
Message 23285 - Posted: 24 Feb 2009, 19:58:20 UTC - in response to Message 23283.  

Hi Fred,

Gave 1.51 a spin and after 4 hours, the Firefox app with 3 longer writings, not yet saved, disappeared off screen. Trying to relaunch gave the same relaunch error... Quota all used, free resources... Again when ending TThrottle, the temp icon (coretemp), went from 100, which I think is the junction point, to the regular op temp.
Thanks
Could be a number of things. Did you disable the virus scanner from the boinc data directory? Are there any other program communicating with BOINC a FireFox app?
ID: 23285 · Report as offensive
SekeRob

Send message
Joined: 25 Aug 06
Posts: 1596
Message 23286 - Posted: 24 Feb 2009, 20:45:33 UTC - in response to Message 23285.  

I've got BOINCview running, but that's not running on the other device where BV is not. Yes AV is excluded and rules are set for free passage, but given that killing the throttle provides instantaneous stability restore, it's hard to not consider it's not releasing something... memory leak?

At the time of freeze, coretemp showed 100C and immediately returned to regular temperature showing when the throttle was closed. I saw in the TT interface this junction value, thus considered that possibly something kicks to have the TT think it is 100C? BOINC continues as normal and the CPU usage monitor (Process Explorer) continues to show processes running on.

I use Firefox add-on ScribeFire to write posts. Too often lost stuff when a website or forum goes down, but as it is since FFX is my most used writing interface, it's the one to first get hit by system issues.

ATM I'm only running WCG, Nutritious Ricve, Help Cure Cancer and Human Proteome Folding. Occasionally FightAIDS@Home and Clean Energy and Some Dengue... all WCG, but it happened when all cores were doing Rice, which is very very small memory footprint and barely raising temps.

I'll post the log when I'll resume testing in a PM.
Coelum Non Animum Mutant, Qui Trans Mare Currunt
ID: 23286 · Report as offensive
Fred - efmer.com
Avatar

Send message
Joined: 8 Aug 08
Posts: 570
Netherlands
Message 23335 - Posted: 27 Feb 2009, 9:48:02 UTC - in response to Message 23286.  
Last modified: 27 Feb 2009, 10:41:54 UTC

I get reports back that the memory problem is solved in V 1.54. There is a V 1.55 for testing with some improvements in the GPU throttle for laptops.
Thanks to Sekerob, Mikael and Alain for the testing.
ID: 23335 · Report as offensive
SekeRob

Send message
Joined: 25 Aug 06
Posts: 1596
Message 23394 - Posted: 2 Mar 2009, 10:50:51 UTC - in response to Message 23335.  

Hi Fred,

1.53 is still doing fine. On Vista Quad it has trouble reading the system data only showing 1 core temp and 1 gpu temp, and not doing anything, certainly not graphing, trying all sorts for version 1.54 and 1.55. Tried both admin and user lever installs.

cheers
Coelum Non Animum Mutant, Qui Trans Mare Currunt
ID: 23394 · Report as offensive
Fred - efmer.com
Avatar

Send message
Joined: 8 Aug 08
Posts: 570
Netherlands
Message 23412 - Posted: 2 Mar 2009, 20:45:33 UTC - in response to Message 23394.  

Hi Fred, 1.53 is still doing fine. On Vista Quad it has trouble reading the system data only showing 1 core temp and 1 gpu temp, and not doing anything, certainly not graphing, trying all sorts for version 1.54 and 1.55. Tried both admin and user lever installs.cheers
PM me the log data so I can see what is going on.
ID: 23412 · Report as offensive
Fred - efmer.com
Avatar

Send message
Joined: 8 Aug 08
Posts: 570
Netherlands
Message 24849 - Posted: 13 May 2009, 13:29:33 UTC - in response to Message 23412.  

A new Version 1.56 is released.

A lot of user request are in this new release.
For AMD users the 0x10 Family problems seems to be solved thanks to Thierry, who send met the log file.

For the upcoming version: a French and Dutch release is planned.
I'm still looking for other languages, please sign on.
And if there is an native English reader, who can check my English for style errors etc.
ID: 24849 · Report as offensive
SekeRob

Send message
Joined: 25 Aug 06
Posts: 1596
Message 24850 - Posted: 13 May 2009, 18:23:43 UTC - in response to Message 24849.  
Last modified: 13 May 2009, 18:24:25 UTC

On the Programs Tab there is twice runnning with 3 n ;>0
Coelum Non Animum Mutant, Qui Trans Mare Currunt
ID: 24850 · Report as offensive
Fred - efmer.com
Avatar

Send message
Joined: 8 Aug 08
Posts: 570
Netherlands
Message 24851 - Posted: 13 May 2009, 18:33:53 UTC - in response to Message 24850.  

On the Programs Tab there is twice runnning with 3 n ;>0

??? a copy of the programs Tab please.
ID: 24851 · Report as offensive
benDan
Avatar

Send message
Joined: 9 Feb 09
Posts: 22
United States
Message 24956 - Posted: 20 May 2009, 19:32:09 UTC

Has anyone been able to run Tthrottle under Win7 RC1 with anything other than the F8 method of driver signing?

If so, please let me know what you did.

Thanks
--
benDan
ID: 24956 · Report as offensive
Fred - efmer.com
Avatar

Send message
Joined: 8 Aug 08
Posts: 570
Netherlands
Message 24959 - Posted: 20 May 2009, 19:42:09 UTC - in response to Message 24956.  

Has anyone been able to run Tthrottle under Win7 RC1 with anything other than the F8 method of driver signing?
If so, please let me know what you did.
Thanks

I ordered a CodeSigning For Microsoft Authenticode for the driver signing, so hopefully before the end of May. Signed drivers should work.
Will have a testing machine for Windows 7 64 soon, that way I can do some thorough testing.
ID: 24959 · Report as offensive
benDan
Avatar

Send message
Joined: 9 Feb 09
Posts: 22
United States
Message 24993 - Posted: 21 May 2009, 20:10:43 UTC

Win7 RC1 64 bit
Tthrottle V1.57
Using F8 ... driver loaded
Running 2 copies of minirosetta_1.67_windows_x86_64.exe.

No BOINC detection!
Number of matching Programs (Processes): 0


Added minirosetta_1.67_windows_x86_64.exe to the program list.

TThrottle shows 1 of them (pid 2520) but not the other (pid 2286)

Number of matching Programs (Processes): 1
Cpu: minirosetta_1.67_windows_x86_64.exe, PID: 2520, Threads: 4



However ... both seem to be controlled. Process Lasso shows both CPU %s are changed.




--
benDan
ID: 24993 · Report as offensive
Fred - efmer.com
Avatar

Send message
Joined: 8 Aug 08
Posts: 570
Netherlands
Message 24995 - Posted: 21 May 2009, 20:30:53 UTC - in response to Message 24993.  

Win7 RC1 64 bit

Strange..no BOINC detection, but as it seems to work... When I'm able to test it on Win7 I will look into it.
At the moment I'm looking in the registry: localmachine Software\Wow6432Node\Space Sciences Laboratory, U.C. Berkeley\BOINC Setup\DATADIR for the directory.
But in Win7 they probably changed that.
ID: 24995 · Report as offensive
benDan
Avatar

Send message
Joined: 9 Feb 09
Posts: 22
United States
Message 25007 - Posted: 22 May 2009, 23:57:09 UTC

My bad!
TThrottle works fine.

I just copied the BOINC folder from my Vista partition to my Win7 part.

I went back and installed it and now TThrottle works.

Your comment about the registry clued me.

Install sets up the reg entry.
but boinc/seti ran OK without the reg.

strange
--
benDan
ID: 25007 · Report as offensive
Fred - efmer.com
Avatar

Send message
Joined: 8 Aug 08
Posts: 570
Netherlands
Message 25014 - Posted: 23 May 2009, 12:23:23 UTC - in response to Message 25007.  

There is now a signed driver for Vista / Win 7 X64.
Look here for: signed drivers
Makes installation on Windows 64 a lot easier.
ID: 25014 · Report as offensive
Jave Ivanovski
Avatar

Send message
Joined: 23 May 09
Posts: 35
Australia
Message 25020 - Posted: 23 May 2009, 22:31:05 UTC

Wow... I'm impressed. Currently running 1.57 on a Dual AMD Opteron 275 system (ie four cores in total) with Vista 32 as the OS and all seems well. This will definitely come in handy during summer here in Australia. :) (It's currently late autumn now.)
ID: 25020 · Report as offensive
MikeJ

Send message
Joined: 18 Jun 09
Posts: 3
United States
Message 25534 - Posted: 18 Jun 2009, 20:06:57 UTC

I just downloaded version 1.60 a week or so ago and wanted to put a couple of comments here. First off, great program, it really does seem to do its job quite well (with a couple exceptions noted below):

On the Programs tab, setting the "Min Cpu %" to less than 5% has no effect. Even when the temperatures are still above your threshold amount, TThrottle will not throttle back any lower than 5%. Perhaps this is as intended, but I wasn't able to find any such indication that it was intended in the documentation.

The temperature that is being reported from my CPU cores seem to be off by a considerable amount (15°C to 20°C). I actually noticed this by accident. I installed TThrottle and immediately noticed that when BOINC was running at 100% I had temperatures being reported in TThrottle at about 77°C to 78°C. Much too warm!

After opening up my case and doing a thorough cleanout of the fan and all of the cooling elements, I was able to drop those temperatures about 10°C. Better, but still not what I wanted to see.

The next step was to see if I could get the CPU fan in my Dell OptiPlex 745 to speed up a little bit, rather than stay at its lowest speed which is all it has ever done regardless of the temperature inside the case.

So I installed Speed Fan. I was hoping this little program would allow me to increase the fan speed on the CPU and give me some add additional cooling. Unfortunately, it is unable to control the fan on my motherboard. All was not lost, however, because another thing that Speed Fan does is report the core temperatures of the CPU. The odd thing was that the temperatures that Speed Fan was reporting were 15°C or more LOWER than what TThrottle was reporting!

I didn't really think too much of this, because I figured that two different applications could simply process the temperature sensor signals differently and simply not agree on what temperatures were being reported. Furthermore, the instructions with Speed Fan indicate that you could adjust any of the settings being reported by Speed Fan if needed, so this indicated that there was probably some room for inaccuracy with respect to Speed fan at the least.

Nonetheless, I decided to see if there was another application I could install which would report the CPU core temperatures, to kind of break the tie so to speak. So I went out and downloaded CoreTemp. The temperatures being reported by CoreTemp completely agree with the temperatures being reported by Speed Fan. The documentation that comes along with CoreTemp also seems to indicate that it is taking the temperatures directly off the digital sensor on the core themselves, not the computer case, so it should be pretty darn accurate.

Am I the only one experiencing this?
ID: 25534 · Report as offensive
Fred - efmer.com
Avatar

Send message
Joined: 8 Aug 08
Posts: 570
Netherlands
Message 25541 - Posted: 19 Jun 2009, 7:01:22 UTC - in response to Message 25534.  

I just downloaded version 1.60 a week or so ago and wanted to put a couple of comments here. First off, great program, it really does seem to do its job quite well (with a couple exceptions noted below):


TThrottle is limited to 5%, otherwise programs may freeze and even crash.
The 1.60 does have a small bug, that will be corrected in 1.62 that will come out this week. It doesn't throttle back far enough.

Some processors are off. That's why there is a correction option in the expert tab. Normal Junction temperatures are 100C or 85C.
But I need more log reports from users, so if you can send me yours with the temperature you thing it should be. There is very little documentation about this from Intel or AMD. So seeing is knowing.... thats the only way.

TThrottle does it exactly the same way as CoreTemp so try setting the Tjunction to 85C and send me the log.
And I wouldn't go as far as darn accurate, it mostly seems to be accurate. But on some processors it may be off be a lot.
ID: 25541 · Report as offensive
SekeRob

Send message
Joined: 25 Aug 06
Posts: 1596
Message 25553 - Posted: 19 Jun 2009, 14:50:00 UTC - in response to Message 25541.  
Last modified: 19 Jun 2009, 14:52:31 UTC

On all the systems I run TThrottle, the temps match exactly with CoreTemp 0.95.4 and SpeedFan 4.38, so don't know what the issue is.

A minimum of 5% is good. Indeed it's known that BOINC's own CPU control of on and off to achieve a mean computing time to get temps down can lead to crashes of tasks.

1.60 works so far flawless, just updated from 1.57 which ran for weeks without issue and nicely keeping the laptop in particular in a state of not turning into a groin scorcher.
Coelum Non Animum Mutant, Qui Trans Mare Currunt
ID: 25553 · Report as offensive
MikeJ

Send message
Joined: 18 Jun 09
Posts: 3
United States
Message 25556 - Posted: 20 Jun 2009, 0:29:37 UTC - in response to Message 25541.  

TThrottle is limited to 5%, otherwise programs may freeze and even crash.
The 1.60 does have a small bug, that will be corrected in 1.62 that will come out this week. It doesn't throttle back far enough.


That makes sense. Even when my core temperatures were above my set temperature, TThrottle could not back the number crunching off enough to allow the processor to cool. I had to manually suspend BOINC to allow the processors to cool.

Some processors are off. That's why there is a correction option in the expert tab. Normal Junction temperatures are 100C or 85C.
But I need more log reports from users, so if you can send me yours with the temperature you thing it should be. There is very little documentation about this from Intel or AMD. So seeing is knowing.... thats the only way.


I just set my "normal junction temperature" to 85°C and the temperatures now being reported are exactly in alignment with those of Core Temp. Since I have no idea what a "normal junction temperature" is, my opinion on what I think it should be probably would not be terribly useful. :-)

TThrottle does it exactly the same way as CoreTemp so try setting the Tjunction to 85C and send me the log.
And I wouldn't go as far as darn accurate, it mostly seems to be accurate. But on some processors it may be off be a lot.


After resetting my normal junction temperature to 85°C I immediately sent you my log in a personal message on this forum. Please let me know if you would like me to send it to you some other way. Also, please let me know if I misunderstood your log request and you wanted me to actually let the program run for a while at the new setting before sending you the log. I am happy to send it to you again at some other point in the future. Actually, I can send it to you regularly if that would help as well.

I'm happy to do what small part I can in helping to improve this fabulous piece of software!
ID: 25556 · Report as offensive
Fred - efmer.com
Avatar

Send message
Joined: 8 Aug 08
Posts: 570
Netherlands
Message 25558 - Posted: 20 Jun 2009, 4:51:04 UTC - in response to Message 25556.  


After resetting my normal junction temperature to 85°C I immediately sent you my log in a personal message on this forum. Please let me know if you would like me to send it to you some other way. Also, please let me know if I misunderstood your log request and you wanted me to actually let the program run for a while at the new setting before sending you the log. I am happy to send it to you again at some other point in the future. Actually, I can send it to you regularly if that would help as well.

I'm happy to do what small part I can in helping to improve this fabulous piece of software!

Thanks I will add this one to the 85C list, so others don't have the same problem.
The new version will have an emergency throttle that start throttling all running programs when the normal throttling doesn't help enough.
ID: 25558 · Report as offensive
Previous · 1 · 2 · 3 · 4 · 5 . . . 12 · Next

Message boards : Questions and problems : Automatic Temperature regulation

Copyright © 2022 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.