Quote from: moppidoo on April 06, 2018, 11:58:27 AM

Quote from: textb0ok on April 06, 2018, 11:52:11 AM

Quote from: patrike on April 06, 2018, 10:54:44 AM

Quote from: textb0ok on April 06, 2018, 10:30:26 AM

There seems to be a real problem with X16r.

Every morning I wake up and my most profitable rig is not mining anything at all, because it was mining X16r and then it just stopped overnight and did not start mining anything else.

I am losing a lot of profit because of this.

PLEASE FIX...

Has the mining software crashed multiple times? If crashed, it will be noted on the Notifications tab and you will see what mining software, algorithm and pool that was active then the crash happend. By default Awesome Miner will restart a crashed mining process, but if it fails too many times within a few minutes, Awesome Miner will give up. You can configure how many times Awesome Miner should try to restart a miner with frequent crashes in the Options dialog, Advanced section: "Restart attemps on process crash".

Yes I know and I love that part of Awesome Miner, but it doesn't appear to be working at all. It actually just happened to me while it was mining.

X16r seems to start and stop a lot, but there are no fails. If you mean the "Notes" tab it is completely empty.

It looks like it just stops and never restarts unless you manually start it. Honestly I would just disable X16r but it shows as the most profitable for this rig.

This is the only algo that causes this issue. Huh

Which miner are you using with X16r? Has it successfully mined at all or it simply crashed on every startup of the X16r miner of your choice. What is the GPU you are using?

Awesome Miner is using raven miner and there are no problems with the actual mining. There are no rejected shares or anything like that. It is not crashing in any way..... It just starts mining, and after a little while, it stops mining and does not start again.

Raven miner while it is mining will stop mining at random and then start itself back up again, all the time..... BUT... after a while, it just stops mining and does not start again.

I am having this problem on 3 different rigs.

EDIT: Is there a way to make zergpool, ahashpool, hashrefinery, and zpool use C=LTC, without affecting mining pool hub and mining dutch?

Right now if I right click on the managed miner and I add -p C=LTC to the command line properties.... That will make zergpool, ahashpool, hashrefinery, and zpool use c=LTC, but it causes problems with mining dutch and I suspect it may cause issues with mining pool hub.

EDIT 2: For one of my rigs adding -p C=LTC the the managed profit miner command line properties does not even work, it shows as x in the extra column of any pool. THIS SOFTWARE IS SO INCONSISTENT! I am using windows 10 LTSB on a samsung EVO 840 SSD for all 3 rigs and it is a very basic rig.... how is there so much INCONSISTENCY? Huh

?!!!!!