https://www.dropbox.com/s/1f08ml9w109kygq/IMG_2298.MOV?dl=0Hello patrike, I will try to be productive. I am using my time to try to identify the problem.
You have already seen that I have had dozens of errors with lyra2z (other days is another protocol) and tried to reproduce it.
IN the video that I send, I just recorded it when it started to give problems in lyra2z in blazepool, it looks perfectly as it fails.
I created a pool, only with lyra2z in blazepool and nothing else, I add it to the same miner who failed seconds before, and I throw it. The surprise is that he does it correctly, enters blazepool in lyra2z.
There is a problem in the autoswitch, because I have already shown that it fails when there are more protocols, but when it is just not, when mino gin in lyra2z does not fail, when I do the benchmark it works fine. I have not changed the miner nor the OC, I have only put mine directly blazepool in lyra2z
These failures that I have been reporting for some time, happen randomly and in different protocols. It's a good thing that there are more people who have thought of reporting the same thing as me.
gives the feeling that somehow and sometimes when a miner launches autoswitch change the OC or throw it with incorrect parameters, because I do not understand why it only happens in autoswitch, but does not fail mining with a single protocol or currency. So I do not expect to read more than it is a bad configuration of the miner, it is demonstrated that the miner works perfectly when he is not in autoswitch.
Now it is happening in miner 2, 3 and 4, but not in 1 and 5. Why does it work well in some and poorly in others if it is the same pool and miner?
Also to say that to those miners with T-rex that fail, I have lowered the OC a lot, but as it sees it fails in autoswitch but not alone.
And I hope you have the courtesy to answer me.
I think that the important point that Patrike highlighted is that the problem is a false error report. AM doesn't shuffle on his own algorithms, compatible software and pools. The real fact is that we have a miner that crash for a reason and AM report it sometimes badly depending on the speed of crash.
As i do right now, you should first try different OC settings on your cards and see if there's a difference. Maybe stability problem come from the way AM launch mining softwares, but it may be also a bad configuration on our rigs...
Agree that it is a bad error report.
But, the problem is that it tells me that lyra2z does not work when it is in autoprofit mode, but it does when there is no autoprofit. In the video I just choose that protocol and it works perfectly, so it's not the miner's configuration, it's the problem of how the autoswtich launches the requests of some miners
In this scenario, I would really recommend you to start the miner with the Diagnostics button. That would give us both the exact command line and settings Awesome Miner uses to launch the mining software, and also any error messages from the mining software (that it cannot initialize some GPU, that it cannot connect to the pool or anything else). With this information, it's easier to see if the issue is related to the command line that Awesome Miner uses to launch the mining software or if it's simply something going wrong inside the mining software after being launched.
The fact that a miner doesn't start almost always requries the use of the Diagnostics to find out why.
There are two more points
1) As you might have seen from my previous post, I did identify the issue with the incorrect error message where it displayed the incorrect pool name. This does however not explain or cause any real mining issues as it was just a display string that was wrong in the user interface.
2) I've also added another feature that should make Awesome Miner better at recovering from these scenarios where it keeps failing with a certain mining software or pool. In the next release you will find a new setting "Ignore pools after too many failed miner restart attempts". It's very similar to the feature where no accepted shares results in that a pool i marked as failed and the profit switcher will ignore it for some time.
The result is that after a few restart attempts, where Awesome Miner eventually gives up, it will mark your Blazepool Lyra2z as failed and it will restart the miner and let the profit switcher pick the next pool in the list. In the end, you might end up with a completely different pool, mining software and algorithm, but at least the mining is still running.
Please note that this will not resolve any issues with a specific mining software, you still need to figure that out with the Diagnostics, but it helps your miner to keep running during night even if there is either a specific pool or a specific mining software that is failing all the time. Then you can see from all the Notifications that there has been some issues and you could then investigate that in more detail.
Both #1 and #2 will be part of the next development preview.
