Guru3D.com Forums

Go Back   Guru3D.com Forums > Videocards > Videocards - AMD Radeon Catalyst Drivers Section
Videocards - AMD Radeon Catalyst Drivers Section In this section you can discuss everything AMD Catalyst related. Catalyst drivers are for all AMD based graphics cards and APUs.



Reply
 
Thread Tools Display Modes
ClockBlocker (profiled AMD power-management control)
Old
  (#1)
A2Razor
Master Guru
 
Videocard: ASUS R9 Fury X
Processor: Xeon E5 1650 v3
Mainboard: ASROCK X99 WS
Memory: DDR4 2133 ECC / 64GB
Soundcard: SB ZxR, Logitech Z623
PSU: EVGA SuperNova 1000 P2
Default ClockBlocker (profiled AMD power-management control) - 12-10-2015, 13:10 | posts: 330

ClockBlocker is a GPU power-management control software designed for AMD graphics cards. It started as a tool entirely designed for the Radeon R9 Fury series, yet many people have had success with the tool on a whole slew of different graphics hardware. While there may be other tools that already work on your hardware to stop downclocking, this is potentially another option available to you.

Want to read a bit more? Check out the web-documentation linked right here.
(Please be aware that the screenshots are a bit outdated at this point [more choices exist on dialogs], but the usage-guide is otherwise still valid)


Direct Download links for the current latest version (Dallas):
Installer
7zip self extractor (for non-installation)
Documentation
Archived versions

Mirrored links (Seattle):
Installer
7zip self extractor (for non-installation)
Documentation
Archived versions


Guru3D Downloads

Latest Beta:
3148104c3d1d0f3f7fdd75e6d45acbdd66650634 ./web-root/ClockBlocker/Archive/BETA/ClockBlocker 1.3.3 BETA.exe
ClockBlocker 1.3.3 BETA

Use Logitech Gaming Software?
-There's a known issue where running ClockBlocker and having ClockBlocker trigger a "block" rule will disrupt LGS' ability to detect game processes.

In the short term I've produced a workaround, which is posted about starting from here: here.
1.0 -- tested on LGS 8.x (does not support older versions)
1.1 -- tested on LGS 8.x and 5.x

** Please keep in mind that 1.1 is functionally the same and differs only in the injection method. If your hardware works with the latest LGS, then 1.0 may be best for you.

self extracting 7zip
LGS Hook 1.0.exe -- via proxy-DLL injector
LGS Hook 1.1.exe -- via external injector (launcher)

sha1 hash:
35d4ad976023ec9556c9e3b813fd7a200687788a /Archive/Logitech Gaming Software/LGS Hook 1.0.exe
200957799a296df7849a1579fc72ee8e5bcb52b3 /Archive/Logitech Gaming Software/LGS Hook 1.1.exe

The jist:
Quote:
LGS relies on Windows event hooks to detect whenever focus changes. Be that via alt-tab, a program grabbing focus, a program starting, etc.
--Unfortunately, the software assumes that any windowed process on startup will take-focus. [** This assumption is WRONG **]
^ This bug has been reported to Logitech, so presumably in later versions of their software it may be properly fixed and the workaround no longer needed.
(it'd be wise to re-check if my proxy DLL is needed with newer releases)

Want to check your download?
Code:
SHA1-hashes:
ec8ec32bdbe290d81c7fe12e8d8d07f285407b8a  /Archive/1.0/1.0-4/ClockBlocker_Setup.exe
624f56df64897e0fca06617da1db91fe132e586a  /Archive/1.0/1.0-5/ClockBlocker_Setup.exe
9625df03a9bea61e213f22cde81745d28b32e3a6  /Archive/1.0/1.0-6/ClockBlocker_Setup.exe
931241d9f3d5a8c569a942b935e90ca99258d8c1  /Archive/1.0/1.0-7/ClockBlocker_Setup.exe
a16015350ead29d709fe6e08b04e3736d260893e  /Archive/1.0/1.0-8/ClockBlocker_Setup.exe
928a7005a6883eab95ff1ef6588f3681e8921141  /Archive/1.1/1.1-2a/ClockBlocker_7zExtractor.exe
7a3bab8e2941fd92b6657065b10387f7b915a56a  /Archive/1.1/1.1-2a/ClockBlocker_Setup.exe
1231a7a88519a5a48aaec5c7494f35b335d238e5  /Archive/1.1/1.1-3/ClockBlocker_7zExtractor.exe
7096853d0bd3828a9cefb12277cf0155626f78d2  /Archive/1.1/1.1-3/ClockBlocker_Setup.exe
92c034def1558fc125fc68b0ef586cac3ec44d8f  /Archive/1.1/1.1-4/ClockBlocker_7zExtractor.exe
3f57e9f933007e6f8a2af7d82231649c282e3209  /Archive/1.1/1.1-4/ClockBlocker_Setup.exe
de08952af3ae84fcff6abca3e73604056d8476ec  /Archive/1.2/1.2-0/ClockBlocker ADL Module 1.0.zip
27ba3fba0140006681be65301dd68e86a7e135d8  /Archive/1.2/1.2-0/ClockBlocker_7zExtractor.exe
a49b96fa343e0ce3f0a15114e821b79b727d3fe4  /Archive/1.2/1.2-0/ClockBlocker_Setup.exe
ff2e638d5aa94431cb04a3e194fbdfdf3bf89ca4  /Archive/1.2/1.2-1b/ClockBlocker_7zExtractor.exe
3edd2c14592befe371e5cde74100864213749eb9  /Archive/1.2/1.2-1b/ClockBlocker_Setup.exe
2d10bfc451f03c1c240b0dfc8d178928dcaf9085  /Archive/1.2/1.2-2/ClockBlocker_7zExtractor.exe
15c256abe154770882acaadaf6851b8e63b346de  /Archive/1.2/1.2-2/ClockBlocker_Setup.exe
cfd4c41e99c9d0c876f2ab512602f572762c9e74  /Archive/1.2/1.2-3/ClockBlocker_7zExtractor.exe
8201387c7ac45912f6ee97bb8a54900457ceac75  /Archive/1.2/1.2-3/ClockBlocker_Setup.exe
cc3b2ba4a8027c826bd9d4944f6a666d3a11bd3c  /Archive/1.2/1.2-3a/ClockBlocker_7zExtractor.exe
fd7e0e2b899dd6c430639bab4f5ce53575828319  /Archive/1.2/1.2-3a/ClockBlocker_Setup.exe
3080d7573dad3dc0dc0e26bc9ed2f9410a61613c  /Archive/1.2/1.2-4/ClockBlocker_7zExtractor.exe
fa992b82754a73d2220de5a8514541e21ad7ff6a  /Archive/1.2/1.2-4/ClockBlocker_Setup.exe
80020f261122ef058dd04ada415e1d4a52d03859  /Archive/1.2/1.2-5/ClockBlocker_7zExtractor.exe
5a308ecf2284a5757e3d80f2e914add6e7472f05  /Archive/1.2/1.2-5/ClockBlocker_Setup.exe
0981e10712fc3f02ec2acea3a5459bf6cb360e51  /Archive/1.2/1.2-6.2/ClockBlocker_7zExtractor.exe
5203c582f946b4aaed41b2b37b234047f2d82ad4  /Archive/1.2/1.2-6.2/ClockBlocker_Setup.exe
68fe41ec855f14f9084b5a814213ef82141f70d8  /Archive/1.2/1.2-6.3/ClockBlocker_7zExtractor.exe
320ab22b9fee8084c3f89c99867b6f9daab405a2  /Archive/1.2/1.2-6.3/ClockBlocker_Setup.exe
428415c618cb99b9972b32b07f1e35ace1142aa4  /Archive/1.2/1.2-6.4/ClockBlocker_7zExtractor.exe
602b5940ba352987591a8e19bffa715218dba0ce  /Archive/1.2/1.2-6.4/ClockBlocker_Setup.exe
aab9c0e70ab36b4d2b936d4e060cc7dd0d8b9478  /Archive/1.2/1.2-6.5/ClockBlocker_7zExtractor.exe
88deab4014eb4d258f49ffbd45fd987f43cb9307  /Archive/1.2/1.2-6.5/ClockBlocker_Setup.exe
This tool has been posted on AMD's forums in the Fury-X corruption thread, as it was designed due to 'THAT' problem which I was having. It is probably useful for far more purposes than screen-corruption though. While this has been tested now by many more people, I definitely would like to continue hearing if you have success or issues with ClockBlocker on your rigs. I'm also of course open to suggestions on the ClockBlocker UI or any other aspects of it.


All that out of the way, brief section from the link:
Quote:
What is ClockBlocker?

ClockBlocker is a tool designed to do one thing, block GPU downclocking on AMD's latest Fiji graphics cards. Specifically, it was designed to do so on cards operating with the newest power-management scheme -- where customization of AMD's CCC profiles no longer works to lock clock speeds at the maximum. What makes the tool unique is that it does this in a very generic way through creating a near zero-load OpenCL compute workload ... this workload tricks the drivers (so to speak) in to believing that high clocks are needed, and thus prevents throttling of the card. Such a method works on many videocards and is not just limited to AMD's R9 Fury series, despite that these cards (and the increased power-management in Crimson) were the sole motivation for the tool's creation.

--It's similar in concept to running a high end game such as Crysis 3 concurrent with playing a low demanding one (such as most JRPG's), only ClockBlocker has a virtually non-existant impact on graphics performance (it doesn't produce heavy workload while achieving the same effect).

This idea has been expanded on in to a full featured profile-based power-management control, of which I am releasing for free for my fellow gamers.


Features:
*foreground window detection (blocking downclocking only when a program has focus)
*minimalistic UI with emphasis on unobstructive use:

-such as, automatic fullscreen detection as a clocking rule (both for Windowed Fullscreen and true Fullscreen modes)

*Multi-GPU ClockBlocking for you guys out there that use Crossfire
*automatic "instant" effects of clock profile changes, without restarting applications and without saving them
*attempted safe handling of cases where GPU acceleration ends (driver crashes, driver reinstallation, etc)
*best-effort config storage w/ a backup copy

--I will of course respond on these forums, and to PM's on Guru3D. You do not need to register on our site.


Knowing that the software is working:

-The 'easiest' way to test if the tool works at all. Is to after installation edit the "DEFAULT" rule to "Block", instead of "Downclock". If everything is working right, at this point your Graphics Card would clock itself up to the maximum frequency (0% load, at idle on the Windows desktop).

-I would suggest trying to do this before playing around with profiles for a starting point. Otherwise there's going to be alot of potential questions on if programs are properly being detected, the profile you've defined is actually working & detecting game processes, etc.

-As long as you're in Windowed Mode, you can see whether or not ClockBlocker thinks it should be attempting to block downclocking by looking at the System-Tray Icon. If the program's icon is YELLOW, then blocking is not being applied. If it's RED, your profile has correctly identified the application.

-A green tray-icon indicates upclock blocking.

-Currently you'll need to use another utility, such as MSI-Afterburner, TriXX, or GPU-Z to see if your clock speeds are actually being increased. (do not take my software's tray-icon as truthful until you've verified my tool works on your system)

**I will likely add AMD ADL to some future release to make this easier.


Recent:
Quote:
11/27/2016: 1.2-6.5 is released
Further continuation of 1.2-6.4's ADL sanity-check additions.

11/26/2016: 1.2-6.4 is released
ADL watchdog tweaks.

11/25/2016: 1.2-6.3 is released
This is a minor hotfix build.

11/20/2016: 1.2-6.2 is released
This is a CRITICAL regression fix between beta and release of 1.2-6.

11/20/2016: 1.2-6.1 is released
This is a minor hotfix build.

11/19/2016: 1.2-6 is released - PHEW

Thanks to everyone who tested and emailed me bug-reports during the beta testing!

Quote:
Version 1.2-6.5 (watchdog tweaks, sanity-checks):
-ADL watchdog INIT reason is now clarified in log.
(this seems to be causing some confusion, please be aware that the watchdog starting does not mean that timing events are happening)

-More safety-checks added before ADL helper takes actions.
(continuation of 1.2-6.4's changes, looking for more potentially bad-situations that technically shouldn't happen)

Version 1.2-6.4 (watchdog tweaks):
-ADL watchdog interval can now be set. (including completely disabling timing-events)
-More safety-checks have been added on watchdog actions.

Version 1.2-6.3 (hotfix):

Addressed issues:
-ADL watchdog setting STOCK clocks when a card is pre-overclocked and when custom clocks is disabled.
*Original clocks are reverted properly when the profile is dropped*

**This is an unintended behavior and was corrected, blocking is supposed to behave similar to 1.2-5 in this specific case.
[where the pre-set clocks are respected in ALL circumstances => IF custom clocks is off either by checkbox OR selected devices to manage]

-Some Windows components such as the Windows registration dialog, System Information, etc -- (and probably more), were being detected by the internal rules [fullscreen detection, 3D-detection].

**The under-the-hood (non configurable) rejection of system processes has been improved, both for the scanner and window pickers.
Make sure that you are running 64bit-builds on 64bit-Windows, else this rejection will be significantly crippled.

Version 1.2-6.2 (hotfix -- critical):
-Addresses a 'deadlock' between the Main UI-Thread and ProcessScanner.
This looks like a regression between beta and release of 1.2-6. The ordering of two CriticalSections were flipped.

Version 1.2-6.1 (hotfix):
Fixed issues:
-ProcessScanner in some circumstances did not apply profile custom-clock rule changes, until the rule is re-applied.
(aka, disabling and re-enabling it, or changing dialog focus)
-Minor memory-leak (4-bytes per time) may be noticed when disabling, deleting, undoing, and then re-enabling rules w/ custom-clocks in effect.

Version 1.2-6 (major release: dealing with stuck clocks & the latest 16.11 drivers):

Fixed issues:
-Start with Windows, in specific circumstances created the scheduler entry as 'SYSTEM'.
-Clock-States should no longer get stuck when using ADL -- be it from ClockBlocker crashes (hung helper), driver-crashes, or full OS hangs.
(If ClockBlocker detects stuck states on startup, or whenever its ADL Helper is run -- these states will be automatically corrected)

-ADL init, and thus setting of clocks sometimes did not work on the latest 16.11 releases. (where all 3 retry attempts would fail in the log)
-Compute-Method no longer reliably held clocks on the latest 16.11 releases.

New Additions:
-BugTrap:
**If the controller process crashes, a crash-dump can be saved to email to me. (please send these in if you see a crash a few times, it will help me immensely in getting the software stable for everyone)
-ADL WATCHDOG:
**ADL-Helper now has a background task that constantly monitors clock-states. If clock-states change (for any reason) your desired clocks are automatically restored.

-Explicit Clock Control (custom clocks):
**You can now set a custom Overdrive target globally, in profiles, and override the stuck-clock 'fixing' reverted clocks.
=> You also may specify which devices these target applies to. (such as if you have both an IGP and discrete cards, or multiple discrete cards in the machine concurrently)*

================================================== ====================
Note that to enable Custom clocks in profiles you need to:

-"Enable custom clocks" on Settings > General
-Choose "Use ADL-method" on Settings > General
-Move your graphics device from the left to right on Settings > "[ADL] GPU-Picker"

As always please use common sense in what clocks you apply, especially if you're adding voltage via an altered vBios or through another utility.

**Some hardware will need options such as "Extend official overclocking limits" enabled in a tool such as Afterburner (for instance for memory clock control on the R9 Fury).
As this is not an overclocking tool (more of a supplement), I have not automated this process.

-"SHIFT" may be held during startup as an emergency halt to using custom clocks.* (this will uncheck Enable custom clocks)
================================================== ====================

-Added "wait-on", "wait-for", and "wait-after" concept. (these are in the Settings > General tab)

*wait-on => Process to wait on
*wait-for => Duration of time to wait for this process
*wait-after => After wait-on process has launched, or after timeout on wait-for, waits an additional period. (to give ample time for the other program to fully start)

**These options only apply whenever ClockBlocker is started from the loader processes on startup. Normal starts after a machine is running are not delayed.
**This option has been added due to custom clock control and profiles, and to address startup race-conditions.

================================================== ====================
For a usage example with MSIAfterburner (if you use a clock profile in both tools on Windows Startup):

-Click on "Set Wait-On"
-scroll down and select MSIAfterburner.exe
-Select "File-Name", just like you would with the profile picker for a rule edit or addition.
-Click on "Set Wait-For"
-Enter in 60 or 120 seconds. (there's no realistic reason to not pick the largest delay, as wait-for ends as soon as the process launches)
-Set Wait-After to 8-10 seconds
================================================== ====================

Misc:
-Complete rewrite of Task-Scheduler interactions, and removal of account-login prompt
-Eliminated all resize-flicker on buttons (only two more GUI-elements that aren't double-buffered remaining in the program)
-Added dialog scrollbars for the Settings > General tab (if the dialog is vertically smashed, the page can be scrolled now-- it still auto sizes horizontally)
-Various 'minor' tooltip edits and GUI tweaking
-Vulkan, DX12, and Mantle should now be properly detected by the 3D-detection rule
-Improved Compute-Method (for "reliable" approach only), which should work with the latest 16.11 drivers.
NOTE: Recent drivers (at least on the Fury-X & probably also on other cards) have changed the way that Power-Management works for CL and DC workloads.

The empty kernel trick no longer reliably works (alternate method), additionally in these drivers at very-low loads a Fury-X can drop to ~1018mhz.
The effective range of the Compute approach is ~1018-1050 now. (should still keep the card over 1000mhz at all times -- still effective, but if you want locked 1050 and if a game's load is too low you may need to use ADL)

Version 1.2-5:
Fixed issues:
-When "Always Ontop" is set at startup, some systems have tooltips appear behind dialogs and out of view. (they are there, but covered until Always Ontop is cycled off & on)
-ADL blocking method does not reflect overclock settings set by official-mode in MSI-Afterburner and AMD Overdrive.

Version 1.2-4:
-New splashscreen, animation, and Guru3D co-branding theme. ComroeStudios proudly considers Guru3D a partner in bringing you ClockBlocker.
-Added 'websites' section under HELP from the tray-menu.
-Moved 'Dump to TXT' tray-menu to under Misc.

Fixed issues:
-ADL helper may be launched by dispatcher thread before action-type is fully set. (IPC race-condition)
-ADL helper may occasionally set clockspeed to max when exiting Forced-Downclock mode. (IPC race-condition)
-Two log messages may be seen with no cr/lf between them when both COMPUTE & ADL modules are active concurrently. (helper coordination issue)
-On changing focus from a program closing or alt-tabbing, a minimized program could have a rule processed. (despite not being visible)
-It was possible to crash the program by holding the tray-menu open while the splashscreen is active.

Version 1.2-3a:
-interim release -- contains all 1.2-4 bugfixes a bit sooner

Version 1.2-3:
-Added Force-Downclock rule choices. (no matter your method selection, ADL will be used on such rules)
-ADL module will now retry several times before giving up on most calls.
-ADL-method now works w/ memory overclocking on the Fury-X.
[provided that the overclock is done with MSI-Afterburner in unofficial overclocking mode & that Crimson CP Overdrive has not been enabled. (only tested on Windows 8.1 so far) ]
-Fixed a few issues that prevented tooltips from showing up in certain circumstances. (this would persist until the ClockBlocker UI was restarted completely)
-Added dump to TXT tray-menu option (log file + rules page)
-Fixed an extremely-rare crash in the 3D_PROGRAM detection.
-3D_PROGRAM detection will work for more games now.
-Major code optimizations. (up to 40% less overhead in some rule setups)

Version 1.2-2: (optimization & GUI cleanup)
-Eliminate dialog resize flicker on edit rule prompts and confirmation prompt popups
-Drop the no longer necessary delays in IPC coordination (faster behavior switching)
-Optimize module thread-init (slightly faster startup)

Version 1.2-1b: (hotfix)
-Fixed a potential SharedMem race condition -- only could occur when using both methods concurrently
-Changed one last reference to 2015

Version 1.2-1a: (hotfix)
-Combined method now working properly.
(Last second issue right after packaging the release)

Version 1.2-1: (1.2-0 ADL-test integration, cleanup, minor GUI fixes)
-Integrated ADL-method in to the GUI, as well as providing the option to mix ADL + compute methods
(this is very close to "ClockBlocker ADL Module 1.0" for 1.2-0, minus some cleanup and various other changes to glue it all together)
-Bumped SharedMem signature, no longer compatible with prior versions
-ExecuteProcess now labels which module is launched (both can be launched concurrently)
-Helper Module messages are now labeled as ADL or COMPUTE, to make it clear which module generated them
-Eliminated dialog resize flicker on general-settings tab
-Added minimum dialog size for settings page
-Changed all 2015 references to 2016 (woohoo!)
-Set "HELP > Forums" link to point to the documentation forums page, which in turn links directly to the Guru3D forums (Guru3D is considered ClockBlocker's official home)

Version 1.2-0: (major release)

-Edge added around tabbed dialogs, control, and some other UI elements (clarify control division)
-More tooltips added
-Fixed some minor control painting issues
-Tweaked helper module time keeping (should help keep things working right in certain intensive games)
-Clarified log-messages from the Helper-Module as coming from it
-Re-added old blocking method (which has slightly lower performance cost), the newer (more reliable) and older compute methods can now be chosen between
-Rules can now be disabled from the editor. (with the exception of the base "DEFAULT" rule of course, disabled rules are color-coded "gray")
-Rules can now have priority-hints set. These can be assigned individually or collectively adjusted. Higher priorities will be forcedly sorted above others in the list.
-3D-Program detection added as a base choice. (this is disabled by default in favor of fullscreen detection)
-Undo support added. (needed now that bulk actions like priority adjustment exist)
-Added choice for "fast" window fade (faster editing of rules)
-Added choice to bypass confirmation prompts (faster editing of rules)
-Sped up default fade speed slightly
-Windows minimized to the taskbar or hidden in other such ways can no longer trigger foreground detections
-Reduced fontsize in rules list (to help with long paths)
-Fixed some cases of incorrect iconic-windows showing in the window picker
-And many more under the hood changes

Please be aware that builds of 1.2-0 onward are "not" backwards compatible save-format wise. That means that 1.2 can import 1.1 and 1.0 config files, but not the other way around.

--Put another way, reverting to 1.1 after installing 1.2 will cause the loss of your rules. Upgrading to 1.2 will migrate your rules over to the new format.
New builds from 1.1 onward execute as multiple processes. If ClockBlocker's helper-container crashes, ClockBlocker will attempt to re-launch it as soon as an error message is OK'd. This may result in a chain of error messages if ClockBlocker is set to "block".
----If that happens, close ClockBlocker or disable Blocking before accepting the error prompt(s).


You can either re-download the software from here, get it via a 7zip self extractor, or use the built in Software Update function (based on the installer).
[Right Click on the Tray-Icon, Misc > Software Update]


Prior installers are still available from here, for if the new version doesn't work for you and the older versions did.



Confused on the rule system's advanced features? Here's a putting the recent new features together example:
-This may give you an idea of how you'd use all these things with the direction the software is going.

Code:
===============================================================
Settings > General
===============================================================
Start With Windows = TRUE
Check for Updates on Startup = FALSE
Always Ontop = TRUE
Show Splash = FALSE
Exclude ScreenSavers (fullscreen & 3D detection) = TRUE
Disable Editor Confirmation = TRUE
Window Fade Speed = FAST
Blocking Method = ADL


===============================================================
Settings > Rules
===============================================================
[Executable]                                                                 | [Action]                                     | [Priority] | [Enabled]
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ | ++++++++++++++++++++++++++++++++++++++++++++ | ++++++++++ | +++++++++
"*.scr"                                                                      | "[ADL] Force-Downclock"                      | "100"      | "YES"    
"C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Fallout4.exe"       | "Block"                                      | "50"       | "YES"    
"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe" | "[ADL] Force-Downclock if in the foreground" | "0"        | "YES"    
"C:\Program Files (x86)\Mozilla Firefox\firefox.exe"                         | "[ADL] Force-Downclock if in the foreground" | "0"        | "YES"    
"C:\Program Files (x86)\Steam\steamapps\common\*"                            | "Block if in the foreground"                 | "0"        | "YES"    
"FULLSCREEN_PROGRAM"                                                         | "Block"                                      | "0"        | "YES"    
"3D_PROGRAM"                                                                 | "Block"                                      | "0"        | "NO"     
"DEFAULT"                                                                    | "Downclock"                                  | "0"        | "YES"
And worded out what those rules all accomplish:

-force downclocking if a screensaver is running. (priority example)
-block downclocking if Fallout 4 is running in the foreground or the background, as long as a screensaver isn't running.
-force downclocking if we're working in Visual Studio or browsing the web in Firefox, as long as Fallout 4 isn't running.
-block downclocking if we're in any Steam game (windowed mode or fullscreen w/ current focus), as long as a screensaver isn't running.
-and finally raise the clocks if any fullscreen program has focus (non Steam), with the same constraints as above on screensavers.


There may be more cool things you can do such as with media-players or anything else to tame your card and tailor it to your usage, but hopefully this gives some ideas. -Also note that you do not have to have ADL set as the method to use "[ADL]" rule types. These will always use ADL regardless your selection.

Let's find a way to get the most out of our cards.
Cheers!

Last edited by A2Razor; 03-30-2017 at 13:52.
   
Reply With Quote
 
Old
  (#2)
Hilbert Hagedoorn
Don Vito Corleone
 
Hilbert Hagedoorn's Avatar
 
Videocard: AMD | NVIDIA
Processor: Core i7 5960K
Mainboard: X99
Memory: 16GB
Soundcard: X-Fi - GigaWorks 7.1
PSU: 1200 Watt
Default 12-10-2015, 13:20 | posts: 29,513 | Location: Guru3D testlab

Awesome little tool man, hope you get lots of good feedback.

And to the rest of you, yes I read that name wrong at first as well


Follow Guru3D on twitter - facebook and Youtube.
   
Reply With Quote
Old
  (#3)
theoneofgod
Ancient Guru
 
Videocard: AMD 7950 (CFX retired)
Processor: Intel
Mainboard:
Memory:
Soundcard:
PSU: 800w
Default 12-10-2015, 13:23 | posts: 3,945

Absolutely nothing wrong with a bit of clock blocking.

Thanks for the tool.
   
Reply With Quote
Old
  (#4)
PrMinisterGR
Ancient Guru
 
PrMinisterGR's Avatar
 
Videocard: Sapphire 7970 Quadrobake
Processor: Core i7 2600k@4.5GHz
Mainboard: Sapphire Pure Black P67
Memory: Corsair Vengeance 16GB
Soundcard: ASUS Xonar D2X
PSU: EVGA SuperNova 750 G2
Default 12-10-2015, 13:25 | posts: 6,846

Thanks for the tool! The fact that it's even necessary is telling on the state of a lot of things.
   
Reply With Quote
 
Old
  (#5)
thatguy91
Ancient Guru
 
Videocard: XFX RX 480 RS 4 GB
Processor: Ryzen 1700X
Mainboard: MSI X370Gaming Pro Carbon
Memory: DDR3-3733@3333 C15 16 GB
Soundcard: Onboard ALC1220 Nahimic 2
PSU: Enermax Platimax 750W
Default 12-10-2015, 13:48 | posts: 6,453 | Location: Australia

Quote:
Originally Posted by Hilbert Hagedoorn View Post
And to the rest of you, yes I read that name wrong at first as well
I was going to remark on that as well!
   
Reply With Quote
Old
  (#6)
JonasBeckman
Ancient Guru
 
JonasBeckman's Avatar
 
Videocard: Sapphire R9 Fury OC
Processor: i7-3930K @ 4.1Ghz
Mainboard: Asus Rampage IV Extreme
Memory: Corsair Vengeance 16GB
Soundcard: Asus ROG Phoebus
PSU: Corsair AX 1200W
Default 12-10-2015, 14:10 | posts: 13,189 | Location: Sweden

Hey I wonder if that's the screen corruption issue I get on some occasions, might try this tool then if that can be remedied.

https://community.amd.com/thread/188642
(It's rare, and just turning off the monitor and turning it on again solves it for me and it only triggers on certain websites as the clock speeds fluctuate as I understood it, hopefully it won't require a bios update to fix but it's been months now without any driver correcting the problem although only a few users get this specific problem as I understood it.)
   
Reply With Quote
Old
  (#7)
mtrai
Master Guru
 
Videocard: PowerColor RX 480 Red Dev
Processor: Skylake I5 6600K
Mainboard: ASUS Z170-A
Memory: G.Skill Ripjaw V 2x8 3200
Soundcard:
PSU: evga supernova 1050 gs
Default 12-10-2015, 14:22 | posts: 774 | Location: Panama City Beach, FL, USA

Does this tool only work with the fury or will it also work with the R9 290/290x? Anyhow I am trying it out. Set everything to block. Should my GPU clocks then be running at max speed no matter what I am doing? The icon is showing red, but not sure how to test this tool. I am on the latest Windows 10 and have 2 R9 290x crossfired.

Last edited by mtrai; 12-10-2015 at 14:24.
   
Reply With Quote
Old
  (#8)
A2Razor
Master Guru
 
Videocard: ASUS R9 Fury X
Processor: Xeon E5 1650 v3
Mainboard: ASROCK X99 WS
Memory: DDR4 2133 ECC / 64GB
Soundcard: SB ZxR, Logitech Z623
PSU: EVGA SuperNova 1000 P2
Default 12-10-2015, 14:25 | posts: 330

Quote:
Originally Posted by JonasBeckman View Post
Hey I wonder if that's the screen corruption issue I get on some occasions, might try this tool then if that can be remedied.

https://community.amd.com/thread/188642
(It's rare, and just turning off the monitor and turning it on again solves it for me and it only triggers on certain websites as the clock speeds fluctuate as I understood it, hopefully it won't require a bios update to fix but it's been months now without any driver correcting the problem although only a few users get this specific problem as I understood it.)
It seems to for me, however if you read through that forum thread you'll also see that I had success with a +36mv voltage bump to my card. I'm now down to +24mv and haven't seen it repeat, even permitting clock jitter in low GPU load games. For whatever the reason, I absolutely cannot play games like Akiba's Trip and Zestiria without numerous corruptions an hour (yes, even at stock clocks). Now that I've figured out this workaround, I have effectively two solutions. Either I can lock the clockspeed at the maximum (stops the corruption), or I can raise the voltage.


Right now I'm just locking the clockspeeds during most of the games that I play as my solution (as this yields better performance to do that, less stuttering), and then boosting voltage when otherwise using the PC for work (non gaming).


You could probably stop the corruption by setting the DEFAULT profile to block, but this would also mean eating more power than just raising the voltage. Either way, hopefully it helps you in some way.


EDIT: It's not clear to me from your link's image. But the defining trait of this type of corruption is that the screen scrunches up from the bottom, with either a "green" or "black" bar. Eg, you only get the top 70-80% of the screen that's visible, and this is overlapped through the corruption with the lower half.

As an example: Here's one of my corruptions.

Last edited by A2Razor; 12-10-2015 at 14:27.
   
Reply With Quote
Old
  (#9)
A2Razor
Master Guru
 
Videocard: ASUS R9 Fury X
Processor: Xeon E5 1650 v3
Mainboard: ASROCK X99 WS
Memory: DDR4 2133 ECC / 64GB
Soundcard: SB ZxR, Logitech Z623
PSU: EVGA SuperNova 1000 P2
Default 12-10-2015, 14:33 | posts: 330

Quote:
Originally Posted by mtrai View Post
Does this tool only work with the fury or will it also work with the R9 290/290x? Anyhow I am trying it out. Set everything to block. Should my GPU clocks then be running at max speed no matter what I am doing? The icon is showing red, but not sure how to test this tool. I am on the latest Windows 10 and have 2 R9 290x crossfired.
I don't have a 290x to test it with, but it does appear to work with some non Fury's (I've tried a 7950) and even with my Geforce 980 on the NVidia side. If everything is on block and the icon is RED, then you should (assuming it was working) be seeing max clocks right now.


---If you're not seeing max clocks, it'd be helpful to see if there's any specific error messages under "Misc > Log Viewer" on a fresh start (after the profile edit).
   
Reply With Quote
Old
  (#10)
mtrai
Master Guru
 
Videocard: PowerColor RX 480 Red Dev
Processor: Skylake I5 6600K
Mainboard: ASUS Z170-A
Memory: G.Skill Ripjaw V 2x8 3200
Soundcard:
PSU: evga supernova 1050 gs
Default 12-10-2015, 14:35 | posts: 774 | Location: Panama City Beach, FL, USA

Just tried the 64 bit version on my Windows and it errors and crashes can get you a screen shot if you need.

The reason I was asking how to test it, I cannot remember seeing a downclock issue in gaming on my system.
   
Reply With Quote
Old
  (#11)
A2Razor
Master Guru
 
Videocard: ASUS R9 Fury X
Processor: Xeon E5 1650 v3
Mainboard: ASROCK X99 WS
Memory: DDR4 2133 ECC / 64GB
Soundcard: SB ZxR, Logitech Z623
PSU: EVGA SuperNova 1000 P2
Default 12-10-2015, 14:39 | posts: 330

Quote:
Originally Posted by mtrai View Post
Just tried the 64 bit version on my Windows and it errors and crashes can get you a screen shot if you need.

The reason I was asking how to test it, I cannot remember seeing a downclock issue in gaming on my system.
Crashes instantly with errors, interesting. Sure, screenshot of the error might help seeing what's happening or at what point of startup it's hosing.


If you just wanted to test that the tool was working, you might try locking clocks on the desktop purely to see it lock your clocks at the maximum. If there's no downclocking in games, then probably you don't actually need it. --Yet I still appreciate testing it absolutely.


EDIT: Does the 32bit version start properly? Is the crash specific to the 64bit build?
   
Reply With Quote
Old
  (#12)
mtrai
Master Guru
 
Videocard: PowerColor RX 480 Red Dev
Processor: Skylake I5 6600K
Mainboard: ASUS Z170-A
Memory: G.Skill Ripjaw V 2x8 3200
Soundcard:
PSU: evga supernova 1050 gs
Default 12-10-2015, 14:43 | posts: 774 | Location: Panama City Beach, FL, USA

Quote:
Originally Posted by A2Razor View Post
Crashes instantly with errors, interesting. Sure, screenshot of the error might help seeing what's happening or at what point of startup it's hosing.


If you just wanted to test that the tool was working, you might try locking clocks on the desktop purely to see it lock your clocks at the maximum. If there's no downclocking in games, then probably you don't actually need it. --Yet I still appreciate testing it absolutely.


EDIT: Does the 32bit version start properly? Is the crash specific to the 64bit build?
Interestingly it crashes only on the first start of it in 64 bit, then starts normally. It shows the splash screen then errors. I reinstalled it and did the exact same thing.

The 32 bit start fine. Just trying to help.
   
Reply With Quote
Old
  (#13)
A2Razor
Master Guru
 
Videocard: ASUS R9 Fury X
Processor: Xeon E5 1650 v3
Mainboard: ASROCK X99 WS
Memory: DDR4 2133 ECC / 64GB
Soundcard: SB ZxR, Logitech Z623
PSU: EVGA SuperNova 1000 P2
Default 12-10-2015, 14:49 | posts: 330

Quote:
Originally Posted by mtrai View Post
Interestingly it crashes only on the first start of it in 64 bit, then starts normally.
Crashing on the first start after each installation implies something special with it being launched from that Indigo Rose installer. Do I understand correctly that the 64bit build starts fine (for each launch) after it crashes one-time from being launched by the installer?


Quote:
It shows the splash screen then errors.
-This is also pretty helpful, since OpenCL initialization doesn't happen until right after the Splash.

Quote:
Just trying to help.
-This is a huge help, very good observations. Appreciate it!
   
Reply With Quote
Old
  (#14)
Fox2232
Ancient Guru
 
Fox2232's Avatar
 
Videocard: Fury X - XL2420T(Z)@144Hz
Processor: i5-2500k@4.5GHz NH-D14
Mainboard: MSI Z68A-GD80[g3]
Memory: 4x4GB 1600MHz 9,9,8,20 1T
Soundcard: Essence ST / AKG K-701
PSU: FSP Gold series 750W
Default 12-10-2015, 14:54 | posts: 5,562 | Location: EU, CZ, Brno

I did not test your tool, yet. But I would like to point out one thing:
What about thermal throttling/TDP throttling? People testing on other than well cooled GPUs should take some precautions.
   
Reply With Quote
Old
  (#15)
mtrai
Master Guru
 
Videocard: PowerColor RX 480 Red Dev
Processor: Skylake I5 6600K
Mainboard: ASUS Z170-A
Memory: G.Skill Ripjaw V 2x8 3200
Soundcard:
PSU: evga supernova 1050 gs
Default 12-10-2015, 14:55 | posts: 774 | Location: Panama City Beach, FL, USA

Correct, after the first 64 bit launch on Win 10 64, it crashes while the load splash screen is showing. Then you can launch it and no crash. By no means will I say it is the coding, as it well may be my system.
   
Reply With Quote
Old
  (#16)
A2Razor
Master Guru
 
Videocard: ASUS R9 Fury X
Processor: Xeon E5 1650 v3
Mainboard: ASROCK X99 WS
Memory: DDR4 2133 ECC / 64GB
Soundcard: SB ZxR, Logitech Z623
PSU: EVGA SuperNova 1000 P2
Default 12-10-2015, 14:57 | posts: 330

Quote:
Originally Posted by Fox2232 View Post
I did not test your tool, yet. But I would like to point out one thing:
What about thermal throttling/TDP throttling? People testing on other than well cooled GPUs should take some precautions.

AMD's clock control is still completely active.

In the case of exceeding the thermal / TDP limits, downclocking would still happen. So it should be completely safe as this is not an absolute lock, but rather a hint to the drivers to run the card under the expectation of full load.
   
Reply With Quote
Old
  (#17)
mtrai
Master Guru
 
Videocard: PowerColor RX 480 Red Dev
Processor: Skylake I5 6600K
Mainboard: ASUS Z170-A
Memory: G.Skill Ripjaw V 2x8 3200
Soundcard:
PSU: evga supernova 1050 gs
Default 12-10-2015, 15:00 | posts: 774 | Location: Panama City Beach, FL, USA

Figured a way to test it. Yes it does work for R9 290/290x. Thought of a game I play that will downlock during loading screens and no longer downclocks.
   
Reply With Quote
Old
  (#18)
A2Razor
Master Guru
 
Videocard: ASUS R9 Fury X
Processor: Xeon E5 1650 v3
Mainboard: ASROCK X99 WS
Memory: DDR4 2133 ECC / 64GB
Soundcard: SB ZxR, Logitech Z623
PSU: EVGA SuperNova 1000 P2
Default 12-10-2015, 15:01 | posts: 330

Quote:
Originally Posted by mtrai View Post
Correct, after the first 64 bit launch on Win 10 64, it crashes while the load splash screen is showing. Then you can launch it and no crash. By no means will I say it is the coding, as it well may be my system.
Yeah, I'll still put a high priority in tracking that down.. because the self-updater downloads and launches the installer with a "-silent" argument (the way that I've designed things). The installer scans through running processes, looks for a matching Window Handle to the app, issues it a request to close itself, overwrites the files, then re-launches the program.

It doesn't happen here, but I also don't have a Windows 10 machine like I mentioned. We'll probably know soon as more people attempt to use it.


-This would be a recurring issue on every update if it's a problem with the software.
   
Reply With Quote
Old
  (#19)
A2Razor
Master Guru
 
Videocard: ASUS R9 Fury X
Processor: Xeon E5 1650 v3
Mainboard: ASROCK X99 WS
Memory: DDR4 2133 ECC / 64GB
Soundcard: SB ZxR, Logitech Z623
PSU: EVGA SuperNova 1000 P2
Default 12-10-2015, 15:06 | posts: 330

Quote:
Originally Posted by mtrai View Post
Figured a way to test it. Yes it does work for R9 290/290x. Thought of a game I play that will downlock during loading screens and no longer downclocks.
Awesome, great to know!

The more working cards, the merrier.
   
Reply With Quote
Old
  (#20)
xxela
Master Guru
 
Videocard: ASUS Radeon R9 FURY STRIX
Processor: AMD AMD Ryzen 7 1700X@3.9
Mainboard: ASUS CROSSHAIR VI
Memory: HyperX Fury Black 16GB
Soundcard:
PSU: Seasonic X-850
Default 12-10-2015, 15:38 | posts: 200

great tool it seems but in my case when I did the test it only works for couple of seconds and then it drops to 300 again. here a screenshot


Anyway, keep up the good work!
   
Reply With Quote
Old
  (#21)
GREGIX
Master Guru
 
GREGIX's Avatar
 
Videocard: Saphire Fury 3-x@2720Z
Processor: i7-5775C@4ghz
Mainboard: Asus z97 pro gamer
Memory: 2x8gb Basillix 2133 cl9
Soundcard: Creative Zx+Edifier 1700
PSU: EVGA G2 550W
Default 12-10-2015, 16:33 | posts: 331 | Location: Ireland

To be honest I didn't tested your tool, but thanks for the post.
I didn't realized that there are problems with corruptions/artefacts with those cards.
And it worries me, as I planned to buy fury card...ATM Im using only iGPU with Benqa xl2720x so upgrade is must, I want to see that 144Hz...
That case I might turn to 980, but I rather wouldn't do that.


Sry 4 english
   
Reply With Quote
Old
  (#22)
BIG_FREAK
Newbie
 
Videocard: R9 290x
Processor: Intel i7 4970k
Mainboard: Asus z97m - Plus
Memory: 16GB DDR 1600
Soundcard: Fiio e10k DAC/Amp
PSU: Seasonic 750
Default 12-10-2015, 16:48 | posts: 8 | Location: Fredericton.nb.ca

Hello,

unable to get it to clockblock (great name)

Windows 10 X64
r9 290x
Driver Crimson 15.11.1 (9.14.10.01162)

I have tested with firefox setup for the firefox.exe
I also tried it with NBA2K16.exe and also just with the gaming running full screen.

I tried setting the short cut to run under windows 8 compatibly mode with no luck.


I am using MSI afterburner 4.20 to monitor my GPU usage on my second monitor.

Thanks keep up the great work. let me know if there something else I could try.

BIG_FREAK


Last edited by BIG_FREAK; 12-10-2015 at 16:52.
   
Reply With Quote
Old
  (#23)
Shadowxaero
Master Guru
 
Videocard: R9 Fury Crossfire
Processor: Ryzen 7 1700 @ 3.9Ghz
Mainboard: Asrock x370 Taichi
Memory: 32GB Trident Z 3020Mhz
Soundcard: Sound Blaster Z
PSU: Ultra X4 1050 Watt
Default 12-10-2015, 17:55 | posts: 150

Hello, great idea for this APP. Greatly needed haha but it is not working on my end.

Trying to get it to "clockblock" AC Syndicate but my core is still bouncing all over the place.

I have the Sapphire Fury Tri-X btw
   
Reply With Quote
Old
  (#24)
Tomatone
Member Guru
 
Tomatone's Avatar
 
Videocard: PowerColor R9 270
Processor: i5-4690K@4.5GHz
Mainboard: GIGABYTE GA-Z97-D3H
Memory: Kingston 4x4GB 1866MHz
Soundcard: Onboard
PSU: SS-500ET
Default 12-10-2015, 22:24 | posts: 80 | Location: Serbia

Hi,
just to report that this tool works with my R9 270 (non-x) on Win7. I want to ask did this tool can use 3D clock/profile from AB?
http://imgur.com/DsREuek

Last edited by Tomatone; 12-10-2015 at 22:52.
   
Reply With Quote
Old
  (#25)
sammarbella
Ancient Guru
 
sammarbella's Avatar
 
Videocard: 290X Lightning CFX (H2O)
Processor: I7 3770 4.1Ghz (H2O)
Mainboard: Asrock xtreme4
Memory: G.Skill TridentX CL7 32GB
Soundcard: SB Zx sennheiser PC350SE
PSU: Lepa G1600
Default 12-11-2015, 02:05 | posts: 3,551 | Location: Imagine...

Quote:
Originally Posted by Fox2232 View Post
I did not test your tool, yet. But I would like to point out one thing:
What about thermal throttling/TDP throttling? People testing on other than well cooled GPUs should take some precautions.
Agree.

Ppl with less than optimal cooling solutions or in locations who have high ambient temp should at least use an AB fan temp customized to their local specific conditions if they want to block (lock) his GPU timings with this tool or AB profiles.

Relying only on thermal throttling to lower temp in all cases is not good at all for the GPU.

@A2Razor

Thanks to spend your time in this tool and share it with all of us.

As PR said the need of tools like this one or RadeonMod expose how little effort AMD put in giving us basic control over our GPUs and instead spend a lot of time delivering fancy graphics drivers GUI, social connectors and a worst gameplay/multimedia playback in the pursuit of lower watt usage.

I guess AMD consider his "green" crazyness a top priority for his GPUs.

I think the customers who buy these GPUs normally use them to play games and want performance to be top priority over watts spend...or at least have the option to have this performance and stability back deactivating the "green fetures" right from the fancy drivers GUI.
   
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump



Powered by vBulletin®
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
vBulletin Skin developed by: vBStyles.com
Copyright (c) 2017, All Rights Reserved. The Guru of 3D, the Hardware Guru, and 3D Guru are trademarks owned by Hilbert Hagedoorn.