ClockBlocker (profiled AMD power-management control)

That was one of the problems. My costum fan profile wasn't turned on. The other problem is that the GPU did get abnormally hot at one spot in Fallout 4. It was almost like i was running furmark. One of the patches seem to have fixed this problem.

 

The new version seem to work much much better. It's still downclocking a little bit (10 - 15mhz) with FreeSync enabled, but it's much better than a 500+mhz downclock per card.

 

I do not have an affected card but well done on the tool and on the name!! Love it!

 

It's working (HD7970)!! Me and my wife are very thankful for your ClockBlock method, and the "how to" use it.

I think you might as well have saved our marriage!

Looking forward a lot of ClockBlocking next week end ! :kind: :kissin: :banana:

 

Tried new release 1.0-5 and now it works. When activated the clock stay at 1000 all the time on desktop.
Two things though:
1 It wont match the overclock frequency (in games bounce between 1000 and 1100) but this is not such a big deal.
2 When I apply an overclock profile in afterburner with 100 mv offset, on desktop the voltage raise above what I have in games with this profile. for example with 100 mv offset in load I have aprox 1.300 but on desktop with ClockBlocker active it gave me 1.337 witch is kinda high.

 

Awesome that it's working for all of you now.

I was expecting to need alot more test builds, logging, and potentially even to install Windows 10 again -- but it looks like I got it with a shot in the dark (off of assumptions and some guesswork).

xxela: Far as the voltage you're seeing, one thing to keep in mind is the likes of vdroop and compensation for it. The card is clocked up at idle, but it's also very inactive vs whenever you're playing a demanding game. I've never done testing to what degree applied voltage dips on these types of chips though (how much of a draw there is), so this is just speculation of course.


-I will see if there's something I can do about that remaining clock jitter and also test voltage a bit later on (push my card a bit higher and see if I can observe it). No promises on the clock jitter you guys are seeing of course, but I think that'll wait till another day.


On that note: Sadly I have a very low clocking Fury-X as well.

-It can't hit past 1082mhz really in Crysis 3, regardless the voltage. But, in this case it doesn't matter if I can run a game like Crysis 3 stable.. Just need it to run long enough at a clock speed in some low load game that I can test changes (eg, reproduce it and see some dips).

--Like the earlier testing in Zestiria (on old builds), my card locks at 1079mhz with no drops recorded.

 

I forgot the mention. It is only fluctuating by 10 - 15 mhz if i overclock my card. If i running both of my cards at stock speed, Clockblock works perfectely.

This is a perfect replacement for locking clocks with afterburner. The screen doesn't flicker anymore, because i don't need to switch between a 2D and 3D profile anymore.

EDIT: 'start with windows' doesn't seem to work for me.

 

Do you potentially use a Windows account that doesn't have a password? I know that the project that I ripped this code from has problems with password-less user accounts sometimes.


If you don't have a password on your account, setting one would probably fix it. But if it's the case that you do have a password and it still doesn't work, then you can create a Task Scheduler entry for "C:\Program Files (x86)\ClockBlocker\Loader_x64.exe" as a workaround for now.


Basically you'd just need to do this:

-Task Scheduler
-File > Create Task

General Tab:
-Name it whatever you want.
-Check "Run with highest privileges"

Triggers Tab:
-New (button)
-Begin the task: At log on (any user)

Actions Tab:
-New
Program: "C:\Program Files (x86)\ClockBlocker\Loader_x64.exe"
Start-in: "C:\Program Files (x86)\ClockBlocker\"
-OK

Conditions Tab:
-Uncheck "start the task only if the computer is on AC power"

 

I do indeed not use a password.

 

It work for my 390 too, nice

 

Works for me now also, though I did have to add the witcher exe to make it work, now my gameplay is flawless, thanks alot good work.

 

Default setting enable it for all fullscreen programs, i think you need to setup if you play in bordless windows fullscreen

 

nope don't play in borderless, and the default fullscreen does not work, well in THW3 anyways, haven't tried any other games yet

 

AB and ClockBlocker work together without any problem only in games clock fluctuate between AB 3D clock and GPU bios 3D clock.

 

Tool is working for me as well


Thank you and keep up the great work

STOKED!

 

Just for info on my side (windows 10 pro X64 TH1) none of the games block on the default full screen block, I have to add the exe (tried TW3 assetto corsa, project cars) though on assetto corsa it's not a problem.
But the full screen default block does work on chrome

As I said not a big problem, just giving my feedback.

 

Just disable power play in MSI AB. Prevents downclocking.

 

Personally do not like doing that. Card stays in 3d clocks all the time.

 

All feedback is pretty great, actually this one I do consider a big issue (personally). One of the most important things to have working, because it eliminates the need to make profile changes.

---I don't have any of those games to test with sadly, but I'll see what I can do.

**If you run in to a free program or some game that has a demo-version that doesn't work (or a cheap Indie title that I can buy), definitely let me know. If I can see detection not working on some software, it should be pretty easy to create a workaround.


Anyway,
-Anything special on your system like multi-monitor?
-Whenever you added rules for each game, are these working with foreground detection? (or did you need to use an all-cases background inclusive block?)

 

Set an AB profile for 2D and another for 3D then on last tab in settings (profiles) define the profile to be used in 2D and the one to be used in 3D.