Overclock.net › Forums › Graphics Cards › AMD/ATI › ATI Drivers and Overclocking Software › WattTool: A simple tool that combines overclocking with VRM monitoring/tweaking for RX 400 series
New Posts  All Forums:Forum Nav:

WattTool: A simple tool that combines overclocking with VRM monitoring/tweaking for RX 400 series - Page 26

post #251 of 290
Coming in to report a weird bug with the software. I was fiddling with the behaviour of LLC on and off (on my card it makes a 0.019v sway and makes it hard to undervolt the IMC without getting EDC errors for some reason, as IMC voltage is really fixed and the vdroop of the card sometimes makes it unstable and gives EDC errors when undervolting the IMC at reasonable voltages of 0.9-0.95v at stock mem clocks).

Well, played BF1 just fine for the most part. Had a crash related to too low vcore and tried to fix it while the game was alt-tabbed.... all sorts of weird behaviour regarding voltage managment, low fps across the board even at P0 and seeing all this i just restarted the pc.

Well now it works all fine for the little problem that it seems that I lost all forms of power-state managment. I have all Pstates at disposal, but either BF1 or LoL wont underclock to lower pstates if the gpu usage goes low, and stay 99% of the time at P0, even if I'm fps capping at 80. On LoL on this 470 nitro I can play just fine at 300 core 300 mem, but now it stays all the time at P0, increasing power consumption by 30 watts.

Is there a way to restart this behaviour? Now even without profiles and reseting everything in either wattool and wattman doesn't solve this weird issue, do i need to reinstall the driver and start from scratch?

EDIT: Now I got it. Seems that sometime down the road the Wattool interfered with Wattman, disabling the Power Efficiency to off in Wattman. Seems like this tab does a lot more than just control the excesive PCI-E power draw on the ref design that was why it was introduced shortly after launch, and when set on ON, it makes the pstate control really go aggresive on downclocking at % usage threshhold. Good TIL honestly.
Edited by PPBottle - 3/19/17 at 2:42pm
post #252 of 290
Hi.

I have some trouble with automattion in batch files on multi GPU system.
- one adapter moves from 46 to 36 and back on system restart or power loss
- if i add both in batch files watttool stays there with an open window
- adding all ini files in the command line not always set all gpu's properly

Any ideas?
post #253 of 290
http://www.overclock.net/t/1609782/watttool-a-simple-tool-that-combines-overclocking-with-vrm-monitoring-tweaking-for-rx-400-series/90#post_25499159
just add the NoGUI Option, and no window will open.

maybe the answer to your other question is also to be found in this thread. You should post what exactly u did and what is meant by "moves from 46 to 36". Doesn't make any sense to me, maybe it's crossfire related, still..
post #254 of 290
Of course i'm using the NoGUI=1 option.

I save 7 GPU in my system. Usually they count 0, 6, 12, 18, 24, 30, 36. But sometimes 36 is missing, instead i get #46, without any hardware change, just after reboot. OK?
post #255 of 290
hm. doesn't have to be watttool.
With every driver install and every card, there is a regkey found here:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\

with only one card, and a clean install (means previous versions deinstalled), my key has the number "0000"
..as shown in watttool as "0". take a look, maybe it makes any sense.

If you just installed over and over again, there will be a lot of numbers. u can uninstall every key in the device manager uninstall option and "delete drivers" till the basic ms driver will be loaded.

or its just a bug. BromoL won't fix it. We don't know what happend to him.
Edited by hellm - 4/2/17 at 2:17pm
post #256 of 290
Watttool 0.92 doesn't appear to apply core frequency/voltage changes as of the latest Crimson driver 17.4.1. Can others confirm?
post #257 of 290
confirmed. voltage doesn't work anymore, frequency alone does.
First BromoL, now this. AMD strikes again.

PP_PhmSoftPowerPlayTable still works:
http://www.overclock.net/t/1609782/watttool-a-simple-tool-that-combines-overclocking-with-vrm-monitoring-tweaking-for-rx-400-series/240#post_25834851
Edited by hellm - 4/5/17 at 2:49pm
post #258 of 290
Issue:

GPU indices from the dropdown are changed from time to time that makes GPU identification in profiles provided via command line impossible
Need to find some other way to identify particular GPU, some device unique id?
Edited by Mightywill - 4/8/17 at 9:39am
post #259 of 290
Quote:
Originally Posted by Mightywill View Post

Issue:

GPU indices from the dropdown are changed from time to time that makes GPU identification in profiles provided via command line impossible
Need to find some other way to identify particular GPU, some device unique id?

Have the same problem, stopped using remote desktop, use only tightvnc, seems to be ok now. I gat the issue the 7th GPU changed #36 and #46.
post #260 of 290
[/quote]
Quote:
Originally Posted by SSBrain View Post

Watttool 0.92 doesn't appear to apply core frequency/voltage changes as of the latest Crimson driver 17.4.1. Can others confirm?
Quote:
Originally Posted by hellm View Post

confirmed. voltage doesn't work anymore, frequency alone does.
First BromoL, now this. AMD strikes again.

PP_PhmSoftPowerPlayTable still works:
http://www.overclock.net/t/1609782/watttool-a-simple-tool-that-combines-overclocking-with-vrm-monitoring-tweaking-for-rx-400-series/240#post_25834851

Hmm, for me both voltage and frequency still work. However button "Reset" doesn't seem to work, but it's not a big issue
New Posts  All Forums:Forum Nav:
  Return Home
Overclock.net › Forums › Graphics Cards › AMD/ATI › ATI Drivers and Overclocking Software › WattTool: A simple tool that combines overclocking with VRM monitoring/tweaking for RX 400 series