For Overheating GPU's : Experimental Core Released For Large WU's

[LCB001]

This is to replace FahCore_11 only, make sure you do the change at the beginning of the WU, it will be restarted from 0%.

From this recommended reading thread: Folding Forum • View topic - Experimental core to reduce overheating for large protein WU

by friedrim » Tue Jun 16, 2009 10:26 pm
A new, experimental core, FahCore_11.exe, has been posted at http://www.stanford.edu/~friedrim This core allows you to specify the percentage of time the program will idle by setting the environment variable 'FAH_GPU_IDLE'. For example, if FAH_GPU_IDLE=10, the program will idle for approximately 10% of the time. Idle times greater than 0 should reduce problems associated with boards overheating for work units modeling larger proteins. On the downside, large idle time percentages will reduce ppd.

If you wish to test this core, stop your GPU client, rename FahCore_11.exe to something else (for a backup) and download the core into the same directory before restarting the client. This version also includes a fix that changes the way checkpoints are done. You can expect the current WU to restart from the beginning. Install the new core soon AFTER a WU finishes. (The same is true if you decide to switch back to the standard core.)

You can set environment variables via Control Panel -> System properties->Advanced->Environment Variables or
right click on 'My computer' and choose Properties -> Advanced->Environment Variables

Environment variables are case-sensitive so be sure to specify FAH_GPU_IDLE=10 because fah_gpu_idle=10 will be ignored.

According to this post:

shdbcamping » Tue Jun 23, 2009 4:19 am
I just got some info from Mark. The only core that will be affected by the throttle settings at this point is the core_11 version 1.27. All others will not even know it's there . Also short term plan is for both the 1.19 and 1.27 versions to stay available. It's up in the air on where the 1.27 will finally end up before going mainstream. Both versions can run on the same system.

Even though the change to enviromental variables effects are global they only effect the clients with the new core, so only change the ones that need it...

[Perineum]

You know, it would be kickass if the core could poll the video card it's running on and have an automatically set "high temp" based on the model of card.... then back off if hitting unacceptable temps.

There is probably a good reason why they aren't doing this...