Is it possible to activate RX 6700 XT fast timings settings from Radeon Software using Phoenix miner command? I found radeon software usually set default settings instead of my presets.
update: "-mt 2" works well with RX 6700 XT

Yesterday my Radeon VII ETH hashrate was dropped from 91MH to 86MH and still keep low on nicehash. Eth become more hungry for GPU performance than before?

Hi Patrike

1) Several versions ago I could reset the ignored pools from the right click >> view details.
Today I had Internet loss for 10 hours and after become online my rig could not connect the pool (there was an error message about "there are no available pools for mining" or something similar), but this time I could not reset ignored pools as before. Please, add this function back.

2) Several pools have the servers in different countries (Europe, USA, others). Can you make selected country as primary pool and the other countries as secondary for the cases when the primary pool fails?

3) Can you add an option to ban the pool from the "online services" tab? For example "disable for 30 min/1 hour/or selected time interval"? Sometimes pool owners asks for some time to repair the problems with their pools and this function can help not to do useless switches.

It seems 460.79 is not good driver:
https://www.nicehash.com/blog/post/psa-do-not-update-to-nvidia-geforce-460-79-drivers

Did you try command-line instead of PowerShell?

It is strange... For me it was never working well without "-amd" option. After you add this option miner does not try to find cuda devices and will not print the error message about cuda devices.

You need to add "-amd" start option, for example:

PhoenixMiner, I want to ask you to improve miner window and log.
I have 9 cards installed and sometimes it is not convenient to catch the situation when hashrate of one of them becomes 0 MH/s. Please, use red color for marking abnormal hashrates - it will make more simple to see the problem.
The other problem is log. After miner fails my PC reboots (watchdog). To find the problem card I need to open log and find the text with problems (zero hashrate or "not responding" messages). But sometimes log file does not contain useful info, because it stops earlier than problem occur. I mean the problem appears in the miner window, but it does not appear in log file because of log file update delay (PC reboots earlier).
This will be useful during batch undervolting/overclocking to find which card to change settings.

Version 5.2c still has low hashrate on my Radeon VII rig. 80MH/s instead of 91MH/s for several tasks on nicehash (sometimes 91MH/s sometimes 80MH/s).

Patrike, need the miner command to ban the current pool for the rules section. At present there are no such command there yet. Ban with the time option.

Patrike, I see the problem with autostart after power fail. Awesome miner did not start while it was set to start automatically with windows. It always works well, but not after power fail. 2 rigs - same problem. There is something wrong with this in version 6.

UPD: I saw Awesome Miner starts with Windows, but it closes itself after several seconds without any error message...

UPD2: I created a task to start awesome miner if it is not running. This task makes awesome miner to start, but it also closes with no reason after several seconds... If start it manually by mouse click it works without closing.

Any thoughts?

Hello, Patrike
I want to ask you to add more deep options for profit statistics.
There are many situations when the profit value displayed in pool API is too high to be the truth (even for 24H average) and the miner switches to that pool and loose the time for mining nothing. I believe it is very simple to detect such high volatility situations reported by pool (not the real coins) and prevent switching miner to that pool.
To make Awesome Miner software the best of the best it will be perfect to add more deep statistics collection for a long time periods:
- collect absolutely all pool statistics for the selected algos every time during profit values requests: TTF, Block found log, current, esimate and average profit values (all together)
- give users full control how to display these info on the graph
- add more deep rules where user can write his own formulas using many different statistics values and make miner to ban the pool for some time
- volatility value display for each pool algo (based on awesome miner collected statistics)
- ban high volatility pool algos till the volatility becomes normal or other user defined changes will happen

High volatility coins and algos are the biggest problem when using BTC for payout. You will never have that profit, because the waiting time before exchange is too long for high volatility algo. So, the only way to control it is to ban unstable profit pool algos.

Patrike, dasboard need to add an option to change graph limits for each miner hashrate and power usage independently (yes, need to add power usage). Usually the area near zero is not useful. If your miner hasrate changes from 120 to 160 MH/s it is better to cut the 0-100 MH/s area and see the more detailed statistics for 100-180 MH/s area. If 1st miner speed is H/s and the second miner speed is MH/s the dashboard screen becomes fully useless for the first miner. That's why need independent limits for each miner. Sometimes you can not understand the real power usage without seeing statistics.

Hello, Patrike
After analyze the statistics I came to understanding important thing: the hashrate of the same algo can be different for different pools. I saw at least 3% difference based on connection ping, pool load and pool mining settings such as difficulty or other things.
Please, make independent hashrate profile values for different pools for the "save hashrate..." function to make profit switching work correctly.

Suggestions for AM

The function "Ignore pools with no accepted shares in (minutes)" can be set to maximum of 10 minutes. It is not enough for CPU mining (cryptonight, cryptonightv7, yescrypt, yescryptr16). Please, increase the maximum value to at least 15-20 minutes or make this option different for every miner.

Another suggestion. Please, learn AM to catch the problems from the miner window and switch to next online pool according to online services tab profit value. If change the pool after "connection refused" or any other error messages it can help to save the time and money.

Please, add average bitrate calculation since the beginning of mining process, it will help to see the correct average hashrate for the variable hashrate algorhytms like x16 and similar.

Yes, bitcore actual profit turned to zero. Thanks for your attention. AM has no problem.
But Awesome miner has another problem after update. Bitcore, HSR, Keccakc and X16r were added, but I already had them in awesome miner before. After deleting my manual settings of these algos I have several problems with zpool algos:
https://yadi.sk/i/oZXRSgSU3TmAXj
Patrike, Do you have any ideas how to repair this? Thanks.

Patrike,
The latest AM update has the bug with bitcore.

It worked well on 5 rigs before. I tried to delete my bitcore settings and keep only yours, also tried to restart the software, restart the rigs, tried to disable/enable bitcore algo with no effect. Ahashpool and Zpool bitcore profit looks ok. the problem is exist only with bitcore profit for Hasrefinery and Zergpool.

Please, make fix