New release 2.2.1
this release contains only smaller fixes that do not have any impact on hashrates:
- fixed a file sharing bug when more than a single instance of TT-Miner is started.
- fixed a too small time-interval for update checks.
- removed an unfinished new algo from the Algo folder (debug version).
Topic: TT-Miner 2022.4.1 KAWPOW, PROGPOW, ETHASH, ETCHASH, EPIC, SHA512256D, GHOSTRIDER - page 43. (Read 132207 times)
March 26, 2019, 11:52:33 PM
March 26, 2019, 11:32:55 PM
TrailingStop
It's seems to be a driver problem. 5GPU rig that earlier easily run with -i21 after I updated to latest 419.67 now can't run even with -i15. 26Gb is too small for it.
It's seems to be a driver problem. 5GPU rig that earlier easily run with -i21 after I updated to latest 419.67 now can't run even with -i15. 26Gb is too small for it.
Oh- I didn't know that. Good investigation. Thanks a lot for sharing! Please also note that I have made a change for the intensity values from 2.1.19 to 2.2!
March 26, 2019, 11:27:40 PM
TrailingStop
It's seems to be a driver problem (or CUDA version). 5GPU rig that earlier easily run with -i21 after I updated to latest 419.67 now can't run even with -i15. 26Gb is too small for it.
It's seems to be a driver problem (or CUDA version). 5GPU rig that earlier easily run with -i21 after I updated to latest 419.67 now can't run even with -i15. 26Gb is too small for it.
March 26, 2019, 10:41:53 PM
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
Yes, sorry. I have to change the values for intensity to develop a function that works better on mixed rigs.
March 26, 2019, 10:40:52 PM
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
Hi, do you have by any chance a logfile of this? I just check here, connect to 2miners, interrupt the network-connection. The the miner first tries to connect to backup-pool, then 2miners again. If the connection is back again it connects and starts mining. Could you please try if that works for you as well?
March 26, 2019, 09:20:18 PM
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
March 26, 2019, 05:16:36 PM
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
on win10 MTP, it's required to update to latest driver & cuda 10.1 to allow intensity to go over -i 15
March 26, 2019, 04:59:43 PM
Hi! No linux version?
Thx
Thx
March 26, 2019, 03:39:44 PM
Hi
Work fine
1080ti, 8 gpu pc, MTP win 10 cuda 10 -i 17 Hashrate 30,8
Work fine
1080ti, 8 gpu pc, MTP win 10 cuda 10 -i 17 Hashrate 30,8
March 26, 2019, 02:56:25 PM
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
March 26, 2019, 02:55:38 PM
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....
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....
March 26, 2019, 02:44:54 PM
with new version I get 0 Hashrate...any ideas? (everything works with previous version on MTP, 1080Ti, win10, Mintpond)
March 26, 2019, 07:58:58 AM
Yes my bad. Please delete NeoScrypt.dll from the algo folder.
Sorry - forgot to delete it.
Sorry - forgot to delete it.
Yes, now working fine!
March 26, 2019, 07:54:39 AM
Hello
There was such a mistake and only in this miner.
Win 8.1 x64
msvcp140d.dll is debug versionThere was such a mistake and only in this miner.
Win 8.1 x64
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.
March 26, 2019, 07:41:37 AM
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 versionThere 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
Any idea what that mean??? Some people reported only 50% hashrate using Windows 7!
try to compile without debug versions dll's
March 26, 2019, 07:04:32 AM
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. Thanks.
Rig with 5GPU has 4Gb and Win10 1709
Rig win 8/9 has 8Gb Win10 1803
So actual difference is only 1709vs1803.
Quote
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
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?
March 26, 2019, 06:54:35 AM
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. Thanks.
Rig with 5GPU has 4Gb and Win10 1709
Rig win 8/9 has 8Gb Win10 1803
So actual difference is only 1709vs1803.
Quote
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
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
March 26, 2019, 05:49:30 AM
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)
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.
March 26, 2019, 05:25:41 AM
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)
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)
March 26, 2019, 03:55:13 AM
Any idea what that mean??? Some people reported only 50% hashrate using Windows 7!
Jump to: