TT-Miner 2024.1.2 BLAKE3, KAWPOW, ETHASH, ETCHASH, EPIC, SHA512256D, SHA3D, ETI

[TrailingStop]

Guys! who can explain me how it work?)) i have 3 rigs 1080ti (6 card each). use new build 2.2.0, each rig ~22 mh (66total). mining on 2miners XZC, my result very different http://joxi.ru/DmBZLBaHw0xp0m it's after 6h work. max what i saw 60mh current hashrate) what happened?)) i new on this coin, all other coin what i mined before - results coincided

Thank you for your help with my idiot question)

Hi,

there are no idiot questions . only idiot answers. What you see is the 3 hours average. If you check that from time to time you will see this value going up and down. You can see that in the chart 2miners provide. You can also try mintpond to verify - I think they use a fast average. You will also see the average fluctuating up and down. If you use -lick as command line option the miner shows you a session luck value. If that is @ 100 % the miner finds as much shares as expected for the printed hashrate. This can become lower if you have rejected shares, which have more impact on pools with higher diff than it have on pools with a lower diff.

Please let me know if that helps - or if you have more questions.

[1715365499]

1715365499

[1715365499]

1715365499

[1715365499]

1715365499

[1715365499]

1715365499

[dkmontague]

Any way to add a CPU priority setting 1-5 like crypto dredge? Would be great.  Thanks for your hard work on this!  Love the miner.

Thanks - happy if you like the miner.
So what is the effect you are locking for? Do you want to mine while doing other work on you PC?

Thanks for the reply!  No I actually want to prioritize the miner above other system processes.  I found that on cryptodredge this was helpful, as setting the miner's CPU priority at max level actually made the hash rate a little better as well as resulted in less rejected shares.  Probably just from less switching between processes for CPU.  Would be awesome if it helped the same way here.  If it's relatively easy to implement, it would definitely add value!!  Let us know if you think its possible

Ah - got it. I hope your rejected rate with TT is not that high? Anyway I can add a switch to set the miner to a higher priority in the next release.

Thanks.

Yeah rejected shares are not high at all but thought it was worth a try to see if hashrate improves a little bit.  Saw you added it to the new release.  I'll give it a go and report back!  Thx again bro!

[impynick]

hash rate definitely higher with 2.20. Using intensity 16/17 im seeing higher lows on pool side and an overall bump in shares from .11 per block to .12

great work thank you 

[Teranaft]

Hello
There was such a mistake and only in this miner.
Win 8.1 x64
https://i109.fastpic.ru/big/2019/0326/b6/cc4f6ddc1b4c63bcc934100b633417b6.png
https://i110.fastpic.ru/big/2019/0326/2b/c17ddbcd85d3573b73eeab1ad375882b.png

[dgeo]

Win7 x64
https://i110.fastpic.ru/big/2019/0326/42/726f4092773945c2e43959e282c65842.jpg

[TrailingStop]

Win7 x64
https://i110.fastpic.ru/big/2019/0326/42/726f4092773945c2e43959e282c65842.jpg

Any idea what that mean??? Some people reported only 50% hashrate using Windows 7!

[abudfv2008]

TralingStop
What does MTP intensity setting depends on?
I have a rig with 5*1060 and can run even i21 without problems (but I think there is no sence of it), while I have 26Gb swap only.
On rigs with 8*1060 and 9*1060 and having 50-75Gb swap files I can't run MTP even on i16. (it starts but then cuda error)

[TrailingStop]

TralingStop
What does MTP intensity setting depends on?
I have a rig with 5*1060 and can run even i21 without problems (but I think there is no sence of it), while I have 26Gb swap only.
On rigs with 8*1060 and 9*1060 and having 50-75Gb swap files I can't run MTP even on i16. (it starts but then cuda error)

Intensity depends on number of cores (SM) on the GPU, maximal thread-count and memory. So if you have 1060/6GB only the intensity should be all the same - it changes only if one or more of the parameters changes. Memory-requirements is in first line coming from the driver (as a result of the block / grid size). Do you have the same driver-version installed on each rig? Also OS might be an issue, but I haven't verified that. So if you have one 1060 that works with 21, all of them should work with 231 as long as the driver and OS is the same (and the virtual memory settings). a cuda error is not always a memory issue. I print this text because in most cases the virtual memory settings are really too low - but this is not alwys true. Can you send me a screenshot with the error-message. I have some information in the message (the numbers) that tells me at which point in the program the problem happened.

Thanks.

[abudfv2008]

Intensity depends on number of cores (SM) on the GPU, maximal thread-count and memory. So if you have 1060/6GB only the intensity should be all the same - it changes only if one or more of the parameters changes. Memory-requirements is in first line coming from the driver (as a result of the block / grid size). Do you have the same driver-version installed on each rig? Also OS might be an issue, but I haven't verified that. So if you have one 1060 that works with 21, all of them should work with 231 as long as the driver and OS is the same (and the virtual memory settings). a cuda error is not always a memory issue. I print this text because in most cases the virtual memory settings are really too low - but this is not alwys true. Can you send me a screenshot with the error-message. I have some information in the message (the numbers) that tells me at which point in the program the problem happened.

Thanks.

Yes. Same driver 417.1 on all rigs.
Rig with 5GPU has 4Gb and  Win10 1709
Rig win 8/9 has 8Gb Win10 1803

So actual difference is only 1709vs1803.

14:51:04 Miner: GPU[7] use intensity 17, Gridsize: 10240
14:51:04 POOL: difficulty up from 0.000 H to 536.88 MH
14:51:12 Miner: Error ******** GPU[3] CudaError: 719
14:51:12 Miner: Error ******** GPU[3] Not enough memory to run algo. GPU disabled.(1/2)
14:51:12 Miner: Error ******** GPU[3] Please check if your Virtual Memory setting is OK. You can also try to
14:51:12 Miner: Error ******** GPU[3] reduce the intensity/grid-size command line value to fix this problem.
14:51:12 Miner: Error ******** GPU[0] CudaError: 719
14:51:12 Miner: Error ******** GPU[0] Not enough memory to run algo. GPU disabled.(1/1)
14:51:12 Miner: Error ******** GPU[0] Please check if your Virtual Memory setting is OK. You can also try to
14:51:12 Miner: Error ******** GPU[0] reduce the intensity/grid-size command line value to fix this problem.
14:51:12 Miner: Error ******** GPU[4] CudaError: 719
14:51:12 Miner: Error ******** GPU[4] Not enough memory to run algo. GPU disabled.(1/1)
14:51:12 Miner: Error ******** GPU[4] Please check if your Virtual Memory setting is OK. You can also try to
14:51:12 Miner: Error ******** GPU[4] reduce the intensity/grid-size command line value to fix this problem.
14:51:12 Miner: Error ******** GPU[2] CudaError: 719
14:51:12 Miner: Error ******** GPU[2] Not enough memory to run algo. GPU disabled.(1/1)
14:51:12 Miner: Error ******** GPU[2] Please check if your Virtual Memory setting is OK. You can also try to
14:51:12 Miner: Error ******** GPU[2] reduce the intensity/grid-size command line value to fix this problem.
14:51:12 Miner: Error ******** GPU[6] CudaError: 719
14:51:12 Miner: Error ******** GPU[6] Not enough memory to run algo. GPU disabled.(1/1)
14:51:12 Miner: Error ******** GPU[6] Please check if your Virtual Memory setting is OK. You can also try to
14:51:12 Miner: Error ******** GPU[6] reduce the intensity/grid-size command line value to fix this problem.
14:51:12 Miner: Error ******** GPU[5] CudaError: 719
14:51:12 Miner: Error ******** GPU[5] Not enough memory to run algo. GPU disabled.(1/1)
14:51:12 Miner: Error ******** GPU[5] Please check if your Virtual Memory setting is OK. You can also try to
14:51:12 Miner: Error ******** GPU[5] reduce the intensity/grid-size command line value to fix this problem.
14:51:12 POOL: Error - Low difficulty share(23)
14:51:12 GPU[-1]: Rejected 0 ms. xzc.2miners.com:8080 [54.36.109.3]
14:51:15 GPU[1]: 2.626 MH/s  CClk:1.561 GHz MClk:4.189 GHz 49C 60% [A0:R0 0.0%]  LastShare: -
14:51:15 GPU[7]: 873.82 kH/s  CClk:1.561 GHz MClk:4.189 GHz 44C 60% [A0:R0 0.0%]  LastShare: 00:00:02
14:51:15 Rig-Speed[2 min]: 3.500 MH/s [A0:R1 0.0%] Uptime: 00:00:27  LastShare: 00:00:02

[TrailingStop]

Intensity depends on number of cores (SM) on the GPU, maximal thread-count and memory. So if you have 1060/6GB only the intensity should be all the same - it changes only if one or more of the parameters changes. Memory-requirements is in first line coming from the driver (as a result of the block / grid size). Do you have the same driver-version installed on each rig? Also OS might be an issue, but I haven't verified that. So if you have one 1060 that works with 21, all of them should work with 231 as long as the driver and OS is the same (and the virtual memory settings). a cuda error is not always a memory issue. I print this text because in most cases the virtual memory settings are really too low - but this is not alwys true. Can you send me a screenshot with the error-message. I have some information in the message (the numbers) that tells me at which point in the program the problem happened.

Thanks.

Yes. Same driver 417.1 on all rigs.
Rig with 5GPU has 4Gb and  Win10 1709
Rig win 8/9 has 8Gb Win10 1803

So actual difference is only 1709vs1803.

14:51:04 Miner: GPU[7] use intensity 17, Gridsize: 10240
14:51:04 POOL: difficulty up from 0.000 H to 536.88 MH
14:51:12 Miner: Error ******** GPU[3] CudaError: 719
14:51:12 Miner: Error ******** GPU[3] Not enough memory to run algo. GPU disabled.(1/2)
14:51:12 Miner: Error ******** GPU[3] Please check if your Virtual Memory setting is OK. You can also try to
14:51:12 Miner: Error ******** GPU[3] reduce the intensity/grid-size command line value to fix this problem.
14:51:12 Miner: Error ******** GPU[0] CudaError: 719
14:51:12 Miner: Error ******** GPU[0] Not enough memory to run algo. GPU disabled.(1/1)
14:51:12 Miner: Error ******** GPU[0] Please check if your Virtual Memory setting is OK. You can also try to
14:51:12 Miner: Error ******** GPU[0] reduce the intensity/grid-size command line value to fix this problem.
14:51:12 Miner: Error ******** GPU[4] CudaError: 719
14:51:12 Miner: Error ******** GPU[4] Not enough memory to run algo. GPU disabled.(1/1)
14:51:12 Miner: Error ******** GPU[4] Please check if your Virtual Memory setting is OK. You can also try to
14:51:12 Miner: Error ******** GPU[4] reduce the intensity/grid-size command line value to fix this problem.
14:51:12 Miner: Error ******** GPU[2] CudaError: 719
14:51:12 Miner: Error ******** GPU[2] Not enough memory to run algo. GPU disabled.(1/1)
14:51:12 Miner: Error ******** GPU[2] Please check if your Virtual Memory setting is OK. You can also try to
14:51:12 Miner: Error ******** GPU[2] reduce the intensity/grid-size command line value to fix this problem.
14:51:12 Miner: Error ******** GPU[6] CudaError: 719
14:51:12 Miner: Error ******** GPU[6] Not enough memory to run algo. GPU disabled.(1/1)
14:51:12 Miner: Error ******** GPU[6] Please check if your Virtual Memory setting is OK. You can also try to
14:51:12 Miner: Error ******** GPU[6] reduce the intensity/grid-size command line value to fix this problem.
14:51:12 Miner: Error ******** GPU[5] CudaError: 719
14:51:12 Miner: Error ******** GPU[5] Not enough memory to run algo. GPU disabled.(1/1)
14:51:12 Miner: Error ******** GPU[5] Please check if your Virtual Memory setting is OK. You can also try to
14:51:12 Miner: Error ******** GPU[5] reduce the intensity/grid-size command line value to fix this problem.
14:51:12 POOL: Error - Low difficulty share(23)
14:51:12 GPU[-1]: Rejected 0 ms. xzc.2miners.com:8080 [54.36.109.3]
14:51:15 GPU[1]: 2.626 MH/s  CClk:1.561 GHz MClk:4.189 GHz 49C 60% [A0:R0 0.0%]  LastShare: -
14:51:15 GPU[7]: 873.82 kH/s  CClk:1.561 GHz MClk:4.189 GHz 44C 60% [A0:R0 0.0%]  LastShare: 00:00:02
14:51:15 Rig-Speed[2 min]: 3.500 MH/s [A0:R1 0.0%] Uptime: 00:00:27  LastShare: 00:00:02

Hi,

I looked into the code. The problem happened when I try to copy data from host to gpu. So it is not an 'out of memory' error. Do you  OC these gpus? Can you try without please? If that didn't work it may be the size of shared memory. This is a 1660?

[dgeo]

Hello
There was such a mistake and only in this miner.
Win 8.1 x64
https://i109.fastpic.ru/big/2019/0326/b6/cc4f6ddc1b4c63bcc934100b633417b6.png
https://i110.fastpic.ru/big/2019/0326/2b/c17ddbcd85d3573b73eeab1ad375882b.png

msvcp140d.dll is debug version

Win7 x64
https://i110.fastpic.ru/big/2019/0326/42/726f4092773945c2e43959e282c65842.jpg

Any idea what that mean??? Some people reported only 50% hashrate using Windows 7!

try to compile without debug versions dll's

[TrailingStop]

Hello
There was such a mistake and only in this miner.
Win 8.1 x64

msvcp140d.dll is debug version

Win7 x64
https://i110.fastpic.ru/big/2019/0326/42/726f4092773945c2e43959e282c65842.jpg

Any idea what that mean??? Some people reported only 50% hashrate using Windows 7!

try to compile without debug versions dll's

Yes my bad. Please delete NeoScrypt.dll from the algo folder.
Sorry - forgot to delete it.

[dgeo]

Yes my bad. Please delete NeoScrypt.dll from the algo folder.
Sorry - forgot to delete it.

Yes, now working fine!

[Alexios777]

with new version I get 0 Hashrate...any ideas? (everything works with previous version on MTP, 1080Ti, win10, Mintpond)

[cirlama]

Hi,
1080ti, single gpu pc, MTP win 10 cuda 10, anything above -i 15 doesn't work on v2.2.0, is it normal? (-gs 8192  or 11000 works also)
above no error message but gpu doesn't hash and cools....

[cirlama]

with new version I get 0 Hashrate...any ideas? (everything works with previous version on MTP, 1080Ti, win10, Mintpond)

seems like me, try -i 15 max

[Bozz77]

Hi

Work fine  

1080ti, 8 gpu pc, MTP win 10 cuda 10 -i 17 Hashrate 30,8

[crsminer]

Hi! No linux version?
Thx

[cirlama]

oki, I understand a  bit better:

on win10 MTP, it's required to update to latest driver & cuda 10.1 to allow intensity to go over -i 15

[omskunreal]

3h ago miner (2.2.0 10 MTP)  reconnected to pool (2miners) and after reconnect don't get share, just work, show hashrate without shares, so I did not immediately notice that it was not working