not sure what you think by last sentence sir.. I run it on +200/+200 and with MTP in config as posted above:
-A MTP-100 -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:x@zcoin-eu.mintpond.com:3000 --api-bind 127.0.0.1:4033
Just want to know if you mine with MTP algo when your OC settings worked. You already answer my question. Thanks. Let me know if TT works without OC.
Will let you know later, going to change it.
Wanted know if overclocking, increasing/decreasing of core/memory can affect the mining on this algo. Like when mining ETH +mem helps to increase speed or +core on equihash. I was thinking you as the dev would know about it something

unfortunately I do have not made a lot of test with OC. I noticed that PC does not have that impact on the hashrate for MTP as it shown on other algos. MTP is more core sensitive than mem - so you might want to play with core and leave mem untouched or even in the negative area. In the end you have to find the best settings for your system yourself since RIGs are very different and hard to compare - even if they run the same GPU.
You were right with the OC. Since I left it on default (no OC) rig runs smoothly. No crashing at all for 21 hours already. Got 4300 shares, 5 rejected only.
I'm just sorry that can't get higher hashrate, with OC I could get 10% more of it..
PS: when I got rejected share, its always gpu 1 or 3 (coincidence??) , with message:
23:29:23.452 POOL: Received new job#: 10cf
23:29:27.212 POOL: Error - Low difficulty. 0.00001859978871878651/1542(23)
23:29:27.231 GPU[3]: Rejected 441 ms. zcoin-eu.mintpond.com:3000 [51.68.181.133]
or
21:17:50.575 POOL: Received new job#: eef
21:17:50.591 POOL: difficulty down from 163.71 MH to 120.00 MH
21:17:59.139 POOL: Error - Low difficulty. 0.00001746934035415034/1831(23)
21:17:59.139 GPU[1]: Rejected 1593 ms. zcoin-eu.mintpond.com:3000 [51.68.181.133]
or
16:30:18.400 POOL: Error - MTP verify failed(20)
16:30:18.400 GPU[1]: Rejected 843 ms. zcoin-eu.mintpond.com:3000 [51.68.181.133]
Does the miner set different difficulty for each GPU? Or those cards were just unlucky because pool was changing difficulty at that time ?
happy that your rig is stable now. Now is the correct time to start OC. Start with core - if you found the sweet point, switch over to mem (also try negative numbers for mem). You may also want to find the best value for the grid size/intensity, just try to add -i 15 or -i 16 and check if that gives you some more hashes.
Miner do not set difficulty - that is up to the pool you use. MintPond support vardiff, 2miners only a high static diff.
Rg the rejections you are right - if the Miner receives a new job or new (higher) diff when a new solution is found chances are high that this solutions gets rejected - I also noticed that your connection shows values for a full turn of the solution of 500 to 1500 ms. Maybe you can connect to a closer pool - or maybe your connection is not very fast???