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?

?!!!!!
Haven't tried the one AM bundled with in recent releases, but it might be the same, I was using the precompiled one b4 the official tpruvot 2.2.5 came out, as not much information was given, you should try out various ccminer forks for X16r and see if they all behave the same.
MPH and MD aren't yiimp pools, if you are using Online Services instead of command line options, this wouldn't be a problem at all as you have a dedicated field to put password parameter for each online services individually and in bulk.
again, use online services unless you are using custom pools, this will eliminate miner command line parameter conflicts.