Not as clumsy or random as a GUI. Elegant mining hardware control, from a more civilized age.
MS Windows command line overclock / underclock, temperature observe and GPU data logging tool for AMD Radeon HD graphic cards.Features
- Change core clock from very low values up to BIOS limit = CCC limit (e.g. stock Sapphire HD5850 Xtreme: 159-900Mhz*). Benefit: Increased Hashrate. It is NOT possible to overclock or overvolt higher than with catalyst control center!
- Change memory clock from very low value up to BIOS limit (e.g. stock Sapphire HD5850 Xtreme: 159-1250Mhz*). Benefit: Lower power dissipation, thus lower temperatures in turn allowing significantly higher core clock.
- Reduce core voltage**. Benefit: Lower power dissipation.
- Will preserve your warranty unlike modifying the BIOS which may void it.
- Works with multiple cards.
- Fan control.
- PowerTune support
- Data logging
- JSON output
- Temperature limit and idle watching.
* Depending on core voltage and hardware limits.
** May only work in big steps at the moment, depending on your card. (e.g. stock Sapphire HD5850 Xtreme: 950mV, 1038mV, 1088mV)New in v0.9.2b
: small fix for undervolting allowing idle voltage levels for mining --> very low power consumption
My four Sapphire HD 5850s can run at 870Mhz instead of 725Mhz at stock 1088mV. Because they get very hot in this configuration I run them at 807/269Mhz, 1088mV. Another possible configuration is 699/233Mhz, 1038mV, saving ~40W per card.Latest Version: 0.9.2b - Download at http://blockchained.com/stuff/clocktweak_installer_v0.9.2b.exe
As a precaution check without load (=without miners) if everything works as intendend with your system. Also test if the limits work as you expect. This program can destroy your system by overheating etc. - be careful and closely monitor your system temperatures and wattage
. Especially on 6xxx and 7xxx systems memory downclocking might be limited. Clocks and voltages can jump back to stock values if you go lower than a certain limit without driver readings (=clocktweak readings) reflecting it.
Note: Adapter / GPU order may be different from your mining software!If you do not know what a command line is and how to use it this is NOT the right tool for you.
ClockTweak is based on Netxshare's pyADL AMDOverdriveCtrl (Radeon overclocking for Linux).Support
Read through the FAQ below. Search this thread. Please do not PM unless I ask you to but post in this thread. Newbies go here
===============================================================================Tested Card Types
ClockTweak v0.9.2b - bitcoinX.com/clocktweak/
usage: clocktweak.exe [-h] [-a [ADAPTER]] [-f] [-r] [-ds [VERBOSITY]] [-n]
[-y] [-c CORECLOCK] [-m MEMCLOCK] [-v VOLTAGE]
[-s FANSPEED] [-p [PERCENT]] [-o [SECONDS]]
[-dw [VERBOSITY]] [-tl CELSIUS] [-th CELSIUS]
[-i [LOAD]] [-time [thSECONDS]] [-w [CYCLES]]
[-j TARGET] [-x]
-h, --help show this help message and exit
-a [ADAPTER], --adapter [ADAPTER]
Choose adapter(s). Without an adapter number given:
list valid adapters. A keyword "all" is available.
Examples: -a all, -a 0, -a 2 -a 4
-f, --force -a, -s: Force adapter choice or low fan speeds. Use
-r, --readonly Read current information. Default is all adapters.
-ds [VERBOSITY], -l [VERBOSITY], --detailscreen [VERBOSITY]
-r: Screen output detail. 1: single line, 2: default,
-n, --naked -r: Suppress header.
-y, --yes By setting this flag you acknowledge that you know
exactly what you are doing and that you read the
readme.txt and the following: The author of this
program will not be responsible for anything it does
to your computer system or your graphic cards. To make
any changes it is necessary to set this flag.
-c CORECLOCK, --core CORECLOCK
Set core clock for level 2 [MHz]. Example: -c 720
-m MEMCLOCK, --memory MEMCLOCK
Set memory clock for level 2 [MHz]. Example: -m 240
-v VOLTAGE, --voltage VOLTAGE
Set voltage for level 2 [mV]. Example: -v 1050
-s FANSPEED, --speed FANSPEED
Set fan speed in percent. Keyword "auto" sets to
automatic (=default). Examples: -s 100, -s 90, -s auto
-p [PERCENT], --powertune [PERCENT]
6xxx cards only. Without value get powertune value.
Set powertune value to PERCENT (-20 to +20).
Experimental, use separately.
-o [SECONDS], --observe [SECONDS]
Start observe mode. Cyclically print -r to screen.
-dw [VERBOSITY], --detailwrite [VERBOSITY]
-o: Log output detail. 1: single line, 2: default, 3:
-tl CELSIUS, --temperaturelow CELSIUS
-o: Exit with errorlevel 10 if highest temperature is
lower than CELSIUS for longer than thSECONDS if
2*thSECONDS after startup.
-th CELSIUS, --temperaturehigh CELSIUS
-o: Exit with errorlevel 11 if any temperature is
higher than CELSIUS.
-i [LOAD], --idle [LOAD]
-o: Exit with errorlevel 12 if lowest GPU load is
below LOAD for longer than thSECONDS.
-time [thSECONDS] -o, -tl, -th, -i: Set approximate time horizon for
observed limits (default: 300).
-w [CYCLES], --write [CYCLES]
-o: Write to logfile every CYCLES observe-cycles (if
disk space > 100MB at start). Default: 10
-j TARGET, --json TARGET
-r, -o, -w: Switch output to json format. Valid
targets are "screen", "file","extrafile" and
"singleentryfile". Examples: -j screen, -j screen -j
-x, --explore Explore adapters for debugging purposes.
HD5670 - tested (RaTTuS); fan control?
HD5750 - tested (SteveFL); fan control?
HD5770 - tested; no fan control (Raigekisai)
HD5830 - tested (grue)
HD5850 - tested (phelix)
HD5870 - tested (Beremat)
HD5970 - tested (jabba)
HD6770 - tested, no fan control (MegaBux); probably limited memclock underclocking*
HD6790 - tested (hawks5999); probably limited memclock underclocking*
HD6850 - tested (ujin); probably limited memclock underclocking*
HD6870 - tested, (mike85123, OCedHrt); probably limited memclock underclocking*
HD6950 - tested (coznefx); probably limited memclock underclocking*
HD6970 - tested (Jazkal); probably limited memclock underclocking*
HD6990 - tested (proudhon - thanks a lot for your support!); probably limited memclock underclocking*
HD7970 - does not always work; probably limited memclock underclocking**On some (all?) 6xxx and 7xxx systems underclocking memory seems to be limited to coreclock - 125Mhz. In these cases the driver and thus ClockTweak do not reflect these limits so you will not even notice. Use a wattmeter or compare temperatures after five minutes of mining to verify.
Asus DirectCU TOP - tested (KiLeRrosS)
Club 3d -
Gigabyte - tested (coznefx)
HIS Reference Implementation - tested (gamecom)
MSI - tested (Raigekisai)
Sapphire - tested (phelix)
XFX - tested (Raigekisai)
This is only an overview as there is a huge number of different combinations of card types and manufactureres out there. You might want to search this thread for your particular card to find more information on what works and what does not.
crossfire - tested (Raigekisai)
4 Cards - tested (phelix)
more than 4 cards - tested (jabba with 5 cards)
Two monitors attached - tested (cdb000)
Two different cards - tested (Beremat)
Windows OS version
XP - tested (phelix)
Vista - tested (RaTTuS)
Server 2008 - tested (Lexiko)
7 - tested (KiLeRrosS)
64bit - tested (RaTTuS); there may be problems
Big thanks to everyone for posting test results!Scripts using on clocktweakLexiko's Auto temperature control .bat scriptFAQ
Q: Why does ClockTweak give me an error if I try to set the core clock / voltage above xxx?
A: You run into the BIOS limit. Either go along with lower values, try another tool or use RBE to modify your BIOS. Some people can beyond BIOS limits with driver version 11.6 / 11.7 / 11.8.
Q: Why does ClockTweak give me an error if I try to set the memory clock below xxx?
A: You run into the BIOS limit. Either go along with higher values, try another tool or use RBE to modify your BIOS. Some people can beyond BIOS limits with driver version 11.6 / 11.7 / 11.8.
Q: How can I reset my card to default mem clock speeds also for level 0 (2D)?
A: There is no comfort function for this yet. Either reboot or ask me for procedure using hidden options explained in the readme.
Q: Why is the reported fan speed different from the speed I set?
A: The reported fan speed is the measured rpm in proportion to the theoretical maximum rpm. A difference of 20% or so is still normal. If the air stream is blocked or the fan is broken the reported fan speed will decrease.