Quote from: sir_blacks on February 02, 2018, 07:57:48 PM

because usual i like to find a fix to a problem, after reading more about https://github.com/nicehash/excavator/tree/master/api i was say hey let try to use "device.set.power_limit" setting my be i will make Excavator to be stable & work nice agen!!! so i set 86W limit (this is my target set already in Afterburner) to be sure it will never exceed that value & GPU Clock it will never goo more that 1860 Mhz. SURPRISE Excavator FAIL to obey / fallow his OWN fraking setting ending crashing GPU clock (2088 - 2216) => ending crashing himself !!! Way ?!?!? i will like to undestend but that's dev job to look in code & see way is out of control, way he can't fallow his own setting ... way can't be stable

Setting extra add in json:

Code:

{"time":5,"commands":[
{"id":1,"method":"device.set.power_limit","params":["0","86"]}
]},

i make a image to show working stable miner & unstable one on crash moment see below
... img removed see orginal post ...

Your mistake is to believe that power_limit is an absolute power value. It's a ratio like in MSI afterburner : a value of 100 is equivalent to the max "official" TDP of your card.
Try with a value of 72 like the one you are using in MSI Afterburner and you shall be in line to compare.

Edit : didn't watched this API before nor using this miner, then saw there was a tdp method.
Did you try to read the value before applying a value (device.get.power_limit) ?