Topic: TT-Miner 2022.4.1 KAWPOW, PROGPOW, ETHASH, ETCHASH, EPIC, SHA512256D, GHOSTRIDER - page 34. (Read 132207 times)
April 28, 2019, 08:02:18 PM
TrailingStop, what about statistic for shares at console - accepted\rejected etc, per device and summary?
April 28, 2019, 05:11:40 PM
Can you add some "switches" that can be pressed while miner is running to change for example intensity on go or gridsize or some other things?
To don't have to restart miner..
just asking ..
To don't have to restart miner..
just asking ..
Yes, it is already on my list and will come in one of the next releases - some other user already suggested that.
On easy thing that you can do to improve you hashrate quite a lot is to improve the cooling of the GPUs. This can easily bring you additional 5-10% - maybe you already noticed that a cold GPU performs much better than a hot one.
Great!
my cards running relaxed on 50 degrees, so dont think the temperature is problem in my case..
April 28, 2019, 04:17:40 PM
Can you add some "switches" that can be pressed while miner is running to change for example intensity on go or gridsize or some other things?
To don't have to restart miner..
just asking ..
To don't have to restart miner..
just asking ..
Yes, it is already on my list and will come in one of the next releases - some other user already suggested that.
On easy thing that you can do to improve you hashrate quite a lot is to improve the cooling of the GPUs. This can easily bring you additional 5-10% - maybe you already noticed that a cold GPU performs much better than a hot one.
Don't think I've actually seen any performance degradation from a few degrees difference while one's cruising under 70 (where most undervolted Pascal cards should sit quite comfortably).
April 28, 2019, 01:59:11 PM
Can you add some "switches" that can be pressed while miner is running to change for example intensity on go or gridsize or some other things?
To don't have to restart miner..
just asking ..
To don't have to restart miner..
just asking ..
Yes, it is already on my list and will come in one of the next releases - some other user already suggested that.
On easy thing that you can do to improve you hashrate quite a lot is to improve the cooling of the GPUs. This can easily bring you additional 5-10% - maybe you already noticed that a cold GPU performs much better than a hot one.
April 28, 2019, 01:28:45 PM
Can you add some "switches" that can be pressed while miner is running to change for example intensity on go or gridsize or some other things?
To don't have to restart miner..
just asking ..
To don't have to restart miner..
just asking ..
April 28, 2019, 11:28:41 AM
The message to change the difficulty is just an information for you. The pool changes the diff and TT-Miner show it to you - so it is changed by the pool - not the miner.
I would first try to change intensity and find a good value for your rig. then I would OC - as the last thing.
Thank you, will try and update later
April 28, 2019, 10:51:04 AM
not sure what you think by last sentence sir.. I run it on +200/+200 and with MTP in config as posted above:
Code:
-A MTP-100 -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:[email protected]: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:
Code:
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
Code:
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
Code:
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 ?
Hi,
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???
Thank you for reply. I had to relocate my rig to other place, where internet pretty sucks. So that's most probably the reason for my rejected shares
. Didn't think about it before. The pool has these options (I dont understand them well):
Code:
Start Difficulty
Setting the starting difficulty will allow your miner to start mining quicker by setting the initial VarDiff difficulty closer to the optimal difficulty of your miner.
The best way to determine an optimal starting difficulty is to allow the VarDiff to run normally and see what difficulty it settles on after 30 minutes to an hour.
-p fYbWmE,sd=3.5
Minimum/Start Difficulty
This option sets both the minimum difficulty and the starting difficulty to the same value. The starting difficulty is the initial difficulty the VarDiff will start at and the minimum difficulty is the difficulty that the VarDiff will not go below.
-p fYbWmE,d=3.5
I remember I had similar settings on other miner before, I will try them and will see if it helps:
Code:
TT-Miner.exe -log -A MTP -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:x,d=4096,[email protected]:3000 --api-bind 127.0.0.1:4033
Code:
17:38:38.537 ****************** GPU information
17:38:38.537 Nvidia GeForce Driver-Version: 430.39
17:38:38.537 CUDA devices: 4
17:38:38.537 * #0 PCI 0:1 ASUS GeForce GTX 1070 Ti (6.1) CoreClk 139 MHz | MemClk 405 MHz | 8192 MB | SM: 19
17:38:38.537 * #1 PCI 0:2 ASUS GeForce GTX 1070 Ti (6.1) CoreClk 139 MHz | MemClk 405 MHz | 8192 MB | SM: 19
17:38:38.538 * #2 PCI 0:4 ASUS GeForce GTX 1070 Ti (6.1) CoreClk 139 MHz | MemClk 405 MHz | 8192 MB | SM: 19
17:38:38.538 * #3 PCI 0:5 ASUS GeForce GTX 1070 Ti (6.1) CoreClk 139 MHz | MemClk 405 MHz | 8192 MB | SM: 19
17:38:38.538 ****************** Mining-Pool information
17:38:38.538 ID:0 - Primary pool: zcoin-eu.mintpond.com:3000
17:38:38.538 Wallet: abcdefghasjdhaklsdjallkajdl
17:38:38.538 Worker: worker:x
17:38:38.538 No backup pool defined
17:38:38.538 ****************** Algo information
17:38:38.538 Algo/Cuda detection: Auto detect
17:38:38.538 Algo/Cuda loaded: MTP for CUDA 10.10
17:38:38.539 ****************** Apply settings
17:38:38.539 Set process priority: default
17:38:38.539 Avg. performance timeframe: 2 minutes
17:38:38.539 Performance summary(seconds): 15 seconds
17:38:38.539 Performance summary(shares): disabled
17:38:38.539 Report Hashrate to pool: disabled
17:38:38.539 Use intensity: -
17:38:38.540 Use gridsize: -
17:38:38.540 API-Interface enabled. Listening on 1
17:38:38.542 ****************** Start mining
17:38:38.578 POOL: Connecting to zcoin-eu.mintpond.com:3000 - PoolID: 0
17:38:38.608 POOL: Connected to: zcoin-eu.mintpond.com:3000 - IP4: 51.68.181.133:3000, Protocol Stratum
17:38:38.639 POOL: Subscribed to zcoin-eu.mintpond.com:3000 - detected protocol: Stratum
17:38:38.671 POOL: Worker authorized: c0mrade
17:38:38.672 POOL: Message - Suggested min-difficulty accepted: 4096
17:38:38.672 POOL: Message - Strict mode enabled
17:38:38.685 POOL: Received new job#: 1f53
17:38:45.036 GPU[0]: 0.000 H/s CClk:1.607 GHz MClk:157.03 MHz 43C 50% 37W 0.000 H/W [A0:R0 0.0%] LastShare: -
17:38:45.037 GPU[1]: 0.000 H/s CClk:1.607 GHz MClk:157.03 MHz 43C 50% 35W 0.000 H/W [A0:R0 0.0%] LastShare: -
17:38:45.037 GPU[2]: 0.000 H/s CClk:1.607 GHz MClk:157.03 MHz 40C 50% 35W 0.000 H/W [A0:R0 0.0%] LastShare: -
17:38:45.038 GPU[3]: 0.000 H/s CClk:1.607 GHz MClk:157.03 MHz 43C 50% 36W 0.000 H/W [A0:R0 0.0%] LastShare: -
17:38:45.039 Rig-Speed[2 min]: 0.000 H/s 143W 0.000 H/W [A0:R0 0.0%] Uptime: 00:00:06 LastShare: -
17:38:46.124 Miner: GPU[0] use default intensity 14, Gridsize: 2432
17:38:46.125 Miner: GPU[1] use default intensity 14, Gridsize: 2432
17:38:46.126 Miner: GPU[2] use default intensity 14, Gridsize: 2432
17:38:46.126 Miner: GPU[3] use default intensity 14, Gridsize: 2432
17:38:46.127 POOL: difficulty up from 0.000 H to 268.44 MH
why is it trying to find difficulty if I set it before and it accepted it?
And want to ask you about intensity. Isnt it bad idea try to OC and change intensity at same time? Im thinking that intensity is kind of OC in fact. Maybe I should first try to change intensity, and try OC just after.. ?
The message to change the difficulty is just an information for you. The pool changes the diff and TT-Miner show it to you - so it is changed by the pool - not the miner.
I would first try to change intensity and find a good value for your rig. then I would OC - as the last thing.
April 28, 2019, 10:44:39 AM
not sure what you think by last sentence sir.. I run it on +200/+200 and with MTP in config as posted above:
Code:
-A MTP-100 -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:[email protected]: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:
Code:
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
Code:
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
Code:
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 ?
Hi,
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???
Thank you for reply. I had to relocate my rig to other place, where internet pretty sucks. So that's most probably the reason for my rejected shares
. Didn't think about it before. The pool has these options (I dont understand them well):
Code:
Start Difficulty
Setting the starting difficulty will allow your miner to start mining quicker by setting the initial VarDiff difficulty closer to the optimal difficulty of your miner.
The best way to determine an optimal starting difficulty is to allow the VarDiff to run normally and see what difficulty it settles on after 30 minutes to an hour.
-p fYbWmE,sd=3.5
Minimum/Start Difficulty
This option sets both the minimum difficulty and the starting difficulty to the same value. The starting difficulty is the initial difficulty the VarDiff will start at and the minimum difficulty is the difficulty that the VarDiff will not go below.
-p fYbWmE,d=3.5
I remember I had similar settings on other miner before, I will try them and will see if it helps:
Code:
TT-Miner.exe -log -A MTP -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:x,d=4096,[email protected]:3000 --api-bind 127.0.0.1:4033
Code:
17:38:38.537 ****************** GPU information
17:38:38.537 Nvidia GeForce Driver-Version: 430.39
17:38:38.537 CUDA devices: 4
17:38:38.537 * #0 PCI 0:1 ASUS GeForce GTX 1070 Ti (6.1) CoreClk 139 MHz | MemClk 405 MHz | 8192 MB | SM: 19
17:38:38.537 * #1 PCI 0:2 ASUS GeForce GTX 1070 Ti (6.1) CoreClk 139 MHz | MemClk 405 MHz | 8192 MB | SM: 19
17:38:38.538 * #2 PCI 0:4 ASUS GeForce GTX 1070 Ti (6.1) CoreClk 139 MHz | MemClk 405 MHz | 8192 MB | SM: 19
17:38:38.538 * #3 PCI 0:5 ASUS GeForce GTX 1070 Ti (6.1) CoreClk 139 MHz | MemClk 405 MHz | 8192 MB | SM: 19
17:38:38.538 ****************** Mining-Pool information
17:38:38.538 ID:0 - Primary pool: zcoin-eu.mintpond.com:3000
17:38:38.538 Wallet: abcdefghasjdhaklsdjallkajdl
17:38:38.538 Worker: worker:x
17:38:38.538 No backup pool defined
17:38:38.538 ****************** Algo information
17:38:38.538 Algo/Cuda detection: Auto detect
17:38:38.538 Algo/Cuda loaded: MTP for CUDA 10.10
17:38:38.539 ****************** Apply settings
17:38:38.539 Set process priority: default
17:38:38.539 Avg. performance timeframe: 2 minutes
17:38:38.539 Performance summary(seconds): 15 seconds
17:38:38.539 Performance summary(shares): disabled
17:38:38.539 Report Hashrate to pool: disabled
17:38:38.539 Use intensity: -
17:38:38.540 Use gridsize: -
17:38:38.540 API-Interface enabled. Listening on 1
17:38:38.542 ****************** Start mining
17:38:38.578 POOL: Connecting to zcoin-eu.mintpond.com:3000 - PoolID: 0
17:38:38.608 POOL: Connected to: zcoin-eu.mintpond.com:3000 - IP4: 51.68.181.133:3000, Protocol Stratum
17:38:38.639 POOL: Subscribed to zcoin-eu.mintpond.com:3000 - detected protocol: Stratum
17:38:38.671 POOL: Worker authorized: c0mrade
17:38:38.672 POOL: Message - Suggested min-difficulty accepted: 4096
17:38:38.672 POOL: Message - Strict mode enabled
17:38:38.685 POOL: Received new job#: 1f53
17:38:45.036 GPU[0]: 0.000 H/s CClk:1.607 GHz MClk:157.03 MHz 43C 50% 37W 0.000 H/W [A0:R0 0.0%] LastShare: -
17:38:45.037 GPU[1]: 0.000 H/s CClk:1.607 GHz MClk:157.03 MHz 43C 50% 35W 0.000 H/W [A0:R0 0.0%] LastShare: -
17:38:45.037 GPU[2]: 0.000 H/s CClk:1.607 GHz MClk:157.03 MHz 40C 50% 35W 0.000 H/W [A0:R0 0.0%] LastShare: -
17:38:45.038 GPU[3]: 0.000 H/s CClk:1.607 GHz MClk:157.03 MHz 43C 50% 36W 0.000 H/W [A0:R0 0.0%] LastShare: -
17:38:45.039 Rig-Speed[2 min]: 0.000 H/s 143W 0.000 H/W [A0:R0 0.0%] Uptime: 00:00:06 LastShare: -
17:38:46.124 Miner: GPU[0] use default intensity 14, Gridsize: 2432
17:38:46.125 Miner: GPU[1] use default intensity 14, Gridsize: 2432
17:38:46.126 Miner: GPU[2] use default intensity 14, Gridsize: 2432
17:38:46.126 Miner: GPU[3] use default intensity 14, Gridsize: 2432
17:38:46.127 POOL: difficulty up from 0.000 H to 268.44 MH
why is it trying to find difficulty if I set it before and it accepted it?
And want to ask you about intensity. Isnt it bad idea try to OC and change intensity at same time? Im thinking that intensity is kind of OC in fact. Maybe I should first try to change intensity, and try OC just after.. ?
April 28, 2019, 10:27:58 AM
not sure what you think by last sentence sir.. I run it on +200/+200 and with MTP in config as posted above:
Code:
-A MTP-100 -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:[email protected]: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:
Code:
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
Code:
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
Code:
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 ?
Hi,
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???
April 28, 2019, 10:16:24 AM
not sure what you think by last sentence sir.. I run it on +200/+200 and with MTP in config as posted above:
Code:
-A MTP-100 -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:[email protected]: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 5822 shares, 7 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:
Code:
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
Code:
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
Code:
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 ?
April 28, 2019, 01:01:47 AM
TrailingStop, looks like you've missed the question I asked
One bug yet: miner don't report if one of the card had crashed. It continue to work with others but failed one is absent. And didn't notice anything about situation at console.
So every time I have to manually check how many cards are working at the moment.That is fixed in the next version.
April 27, 2019, 05:24:30 PM
TrailingStop, looks like you've missed the question I asked
One bug yet: miner don't report if one of the card had crashed. It continue to work with others but failed one is absent. And didn't notice anything about situation at console.
So every time I have to manually check how many cards are working at the moment. April 27, 2019, 03:54:41 PM
Order is always 0-1-2-3-4-5, and in my case gpu with too much OC was 5...
April 27, 2019, 01:12:51 PM
Hi,
what do you mean in detail with card crashes detecting? In the about sample TT detects the cards that crashes, first GPU 0 crashes, then 2, 3 and 4. In the coming release it will continue to report crashed and/or not working cards - is it that what you mean?
Hi, I mean your miner won't say what card has caused the crash. It's always "0-1-2-3-4-5-6-etc out of memory" when it crashes and it doesn't mean that 0 card has caused it. In all miners first goes crashed card, eg. 2-0-1-3 (when card #2 causes the crash) or something like that or it will solely list crashed card only - nothing like that in TT miner, so we have to guess and figure it out.
OK- got it. I never look at the order, but if my memory servers me right if saw sometimes a different order. I do not change the order errors are forwarded from the driver to the miner. So if you see GPU as the first one, it is also the first one the driver reported to thew miner. I do not have a subroutine that sorts the gpu errors.
Anyway, I will take a closer look into this and check if I see something that might change the order I print the errors.
April 27, 2019, 01:09:36 PM
not sure what you think by last sentence sir.. I run it on +200/+200 and with MTP in config as posted above:
Code:
-A MTP-100 -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:[email protected]: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.
April 27, 2019, 01:01:11 PM
Hi,
what do you mean in detail with card crashes detecting? In the about sample TT detects the cards that crashes, first GPU 0 crashes, then 2, 3 and 4. In the coming release it will continue to report crashed and/or not working cards - is it that what you mean?
Hi, I mean your miner won't say what card has caused the crash. It's always "0-1-2-3-4-5-6-etc out of memory" when it crashes and it doesn't mean that 0 card has caused it. In all miners first goes crashed card, eg. 2-0-1-3 (when card #2 causes the crash) or something like that or it will solely list crashed card only - nothing like that in TT miner, so we have to guess and figure it out.
April 27, 2019, 12:22:23 PM
not sure what you think by last sentence sir.. I run it on +200/+200 and with MTP in config as posted above:
Code:
-A MTP-100 -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:[email protected]: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
April 27, 2019, 11:41:20 AM
not sure what you think by last sentence sir.. I run it on +200/+200 and with MTP in config as posted above:
Code:
-A MTP-100 -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:[email protected]: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.
April 27, 2019, 11:20:51 AM
Hello, Im getting randomly these error:
16:43:00.036 GPU[0]: 2.427 MH/s CClk:1.607 GHz MClk:3.999 GHz 37C 50% 32W 75.834 kH/W [A49:R2 3.9%] LastShare: 00:03:09
16:43:00.037 GPU[1]: 2.437 MH/s CClk:1.607 GHz MClk:3.999 GHz 38C 50% 31W 78.623 kH/W [A44:R1 2.2%] LastShare: 00:01:57
16:43:00.037 GPU[2]: 2.320 MH/s CClk:1.607 GHz MClk:3.999 GHz 36C 50% 31W 74.837 kH/W [A37:R0 0.0%] LastShare: 00:04:05
16:43:00.038 GPU[3]: 2.332 MH/s CClk:1.607 GHz MClk:3.999 GHz 38C 50% 31W 75.218 kH/W [A47:R0 0.0%] LastShare: 00:04:06
16:43:00.038 Rig-Speed[2 min]: 9.516 MH/s 125W 76.126 kH/W [A177:R3 1.7%] Uptime: 00:52:33 LastShare: 00:01:57
16:43:12.082 POOL: Received new job#: 169c
16:43:12.084 Miner: Error ******** GPU[0] CudaError: 702
16:43:12.085 Miner: Error ******** GPU[0] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.087 Miner: Error ******** GPU[0] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.088 Miner: Error ******** GPU[0] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.089 Miner: Error ******** GPU[1] CudaError: 702
16:43:12.090 Miner: Error ******** GPU[1] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.091 Miner: Error ******** GPU[1] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.092 Miner: Error ******** GPU[1] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.099 Miner: Error ******** GPU[2] CudaError: 702
16:43:12.099 Miner: Error ******** GPU[2] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.103 Miner: Error ******** GPU[2] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.106 Miner: Error ******** GPU[2] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.108 Miner: Error ******** GPU[3] CudaError: 702
16:43:12.111 Miner: Error ******** GPU[3] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.114 Miner: Error ******** GPU[3] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.115 Miner: Error ******** GPU[3] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.116 Miner: Error ******** All GPUs are disabled. TT-Miner cannot continue and will exit now
16:43:12.125 POOL: Lost connection to zcoin-eu.mintpond.com:3000
16:43:12.126 POOL: Mining temporary stopped
Happening after 10, 30 , 60 minutes. randomly.. any clue ?
This is my config:
-A MTP-100 -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:[email protected]:3000 --api-bind 127.0.0.1:4033
I tried different intensity or grids..
gtx 1070 ti
using latest NVIDIA drivers
8 GB RAM, 32 GB virtual memory, Celeron CPU
PS: what OC is best for gtx 1070 ti ? increase core? mem ?
16:43:00.036 GPU[0]: 2.427 MH/s CClk:1.607 GHz MClk:3.999 GHz 37C 50% 32W 75.834 kH/W [A49:R2 3.9%] LastShare: 00:03:09
16:43:00.037 GPU[1]: 2.437 MH/s CClk:1.607 GHz MClk:3.999 GHz 38C 50% 31W 78.623 kH/W [A44:R1 2.2%] LastShare: 00:01:57
16:43:00.037 GPU[2]: 2.320 MH/s CClk:1.607 GHz MClk:3.999 GHz 36C 50% 31W 74.837 kH/W [A37:R0 0.0%] LastShare: 00:04:05
16:43:00.038 GPU[3]: 2.332 MH/s CClk:1.607 GHz MClk:3.999 GHz 38C 50% 31W 75.218 kH/W [A47:R0 0.0%] LastShare: 00:04:06
16:43:00.038 Rig-Speed[2 min]: 9.516 MH/s 125W 76.126 kH/W [A177:R3 1.7%] Uptime: 00:52:33 LastShare: 00:01:57
16:43:12.082 POOL: Received new job#: 169c
16:43:12.084 Miner: Error ******** GPU[0] CudaError: 702
16:43:12.085 Miner: Error ******** GPU[0] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.087 Miner: Error ******** GPU[0] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.088 Miner: Error ******** GPU[0] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.089 Miner: Error ******** GPU[1] CudaError: 702
16:43:12.090 Miner: Error ******** GPU[1] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.091 Miner: Error ******** GPU[1] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.092 Miner: Error ******** GPU[1] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.099 Miner: Error ******** GPU[2] CudaError: 702
16:43:12.099 Miner: Error ******** GPU[2] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.103 Miner: Error ******** GPU[2] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.106 Miner: Error ******** GPU[2] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.108 Miner: Error ******** GPU[3] CudaError: 702
16:43:12.111 Miner: Error ******** GPU[3] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.114 Miner: Error ******** GPU[3] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.115 Miner: Error ******** GPU[3] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.116 Miner: Error ******** All GPUs are disabled. TT-Miner cannot continue and will exit now
16:43:12.125 POOL: Lost connection to zcoin-eu.mintpond.com:3000
16:43:12.126 POOL: Mining temporary stopped
Happening after 10, 30 , 60 minutes. randomly.. any clue ?
This is my config:
-A MTP-100 -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:[email protected]:3000 --api-bind 127.0.0.1:4033
I tried different intensity or grids..
gtx 1070 ti
using latest NVIDIA drivers
8 GB RAM, 32 GB virtual memory, Celeron CPU
PS: what OC is best for gtx 1070 ti ? increase core? mem ?
Hi,
the error 702 indicates a cuda-timeout. It takes too long until the kernel finishes and the driver terminates it. Please try to use intensities/grid sizes below 10240. For MTP I would start without any OC. Please try to get a stable configuration first.
You can make you command line somewhat simpler - so TT will find the best CUDA version for your installed driver/interface:
-A MTP -P abcdefghasjdhaklsdjallkajdl.worker:[email protected]:3000 --api-bind 127.0.0.1:4033
RAM and Virtual RAM looks OK - Celeron is fine as well.
I would guess you have a OC problem with GPU 0 and maybe GPU 1 - they show rejected shares (but I'm only guessing!).
Please let me know if removing OC helps?
thank you for reply TrailingStop
I tried different configs, memory +200 core +200, also tried MTP-100 and MTP-101
also tried -i auto 1024 10240 256
it finds best grid etc but still randomly crashing.
was using other miner before with +200/+200 and had no issues..
those rejected shares appeared on any of cards randomly..
PS: using Awesome miner and it adds the "stratum+tcp://" by default, do you think that can be problem?
if its not that, what you mean by your suggested config, cant see any difference ?
Will try to remove all OC
stratum+tcp is no problem. My config is almost identical to your. Since I develop the miner on these cards I do not try to get the last hashrate out of the GPU. I use defaults for most settings and no OC so that I can be sure to see crashes because of bad development, not because of bad OC settings.
Do you also use MTP if you run your cards with +200/+200?
not sure what you think by last sentence sir.. I run it on +200/+200 and with MTP in config as posted above:
Code:
-A MTP-100 -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:[email protected]:3000 --api-bind 127.0.0.1:4033
April 27, 2019, 11:13:40 AM
Hello, Im getting randomly these error:
16:43:00.036 GPU[0]: 2.427 MH/s CClk:1.607 GHz MClk:3.999 GHz 37C 50% 32W 75.834 kH/W [A49:R2 3.9%] LastShare: 00:03:09
16:43:00.037 GPU[1]: 2.437 MH/s CClk:1.607 GHz MClk:3.999 GHz 38C 50% 31W 78.623 kH/W [A44:R1 2.2%] LastShare: 00:01:57
16:43:00.037 GPU[2]: 2.320 MH/s CClk:1.607 GHz MClk:3.999 GHz 36C 50% 31W 74.837 kH/W [A37:R0 0.0%] LastShare: 00:04:05
16:43:00.038 GPU[3]: 2.332 MH/s CClk:1.607 GHz MClk:3.999 GHz 38C 50% 31W 75.218 kH/W [A47:R0 0.0%] LastShare: 00:04:06
16:43:00.038 Rig-Speed[2 min]: 9.516 MH/s 125W 76.126 kH/W [A177:R3 1.7%] Uptime: 00:52:33 LastShare: 00:01:57
16:43:12.082 POOL: Received new job#: 169c
16:43:12.084 Miner: Error ******** GPU[0] CudaError: 702
16:43:12.085 Miner: Error ******** GPU[0] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.087 Miner: Error ******** GPU[0] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.088 Miner: Error ******** GPU[0] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.089 Miner: Error ******** GPU[1] CudaError: 702
16:43:12.090 Miner: Error ******** GPU[1] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.091 Miner: Error ******** GPU[1] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.092 Miner: Error ******** GPU[1] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.099 Miner: Error ******** GPU[2] CudaError: 702
16:43:12.099 Miner: Error ******** GPU[2] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.103 Miner: Error ******** GPU[2] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.106 Miner: Error ******** GPU[2] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.108 Miner: Error ******** GPU[3] CudaError: 702
16:43:12.111 Miner: Error ******** GPU[3] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.114 Miner: Error ******** GPU[3] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.115 Miner: Error ******** GPU[3] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.116 Miner: Error ******** All GPUs are disabled. TT-Miner cannot continue and will exit now
16:43:12.125 POOL: Lost connection to zcoin-eu.mintpond.com:3000
16:43:12.126 POOL: Mining temporary stopped
Happening after 10, 30 , 60 minutes. randomly.. any clue ?
This is my config:
-A MTP-100 -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:[email protected]:3000 --api-bind 127.0.0.1:4033
I tried different intensity or grids..
gtx 1070 ti
using latest NVIDIA drivers
8 GB RAM, 32 GB virtual memory, Celeron CPU
PS: what OC is best for gtx 1070 ti ? increase core? mem ?
16:43:00.036 GPU[0]: 2.427 MH/s CClk:1.607 GHz MClk:3.999 GHz 37C 50% 32W 75.834 kH/W [A49:R2 3.9%] LastShare: 00:03:09
16:43:00.037 GPU[1]: 2.437 MH/s CClk:1.607 GHz MClk:3.999 GHz 38C 50% 31W 78.623 kH/W [A44:R1 2.2%] LastShare: 00:01:57
16:43:00.037 GPU[2]: 2.320 MH/s CClk:1.607 GHz MClk:3.999 GHz 36C 50% 31W 74.837 kH/W [A37:R0 0.0%] LastShare: 00:04:05
16:43:00.038 GPU[3]: 2.332 MH/s CClk:1.607 GHz MClk:3.999 GHz 38C 50% 31W 75.218 kH/W [A47:R0 0.0%] LastShare: 00:04:06
16:43:00.038 Rig-Speed[2 min]: 9.516 MH/s 125W 76.126 kH/W [A177:R3 1.7%] Uptime: 00:52:33 LastShare: 00:01:57
16:43:12.082 POOL: Received new job#: 169c
16:43:12.084 Miner: Error ******** GPU[0] CudaError: 702
16:43:12.085 Miner: Error ******** GPU[0] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.087 Miner: Error ******** GPU[0] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.088 Miner: Error ******** GPU[0] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.089 Miner: Error ******** GPU[1] CudaError: 702
16:43:12.090 Miner: Error ******** GPU[1] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.091 Miner: Error ******** GPU[1] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.092 Miner: Error ******** GPU[1] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.099 Miner: Error ******** GPU[2] CudaError: 702
16:43:12.099 Miner: Error ******** GPU[2] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.103 Miner: Error ******** GPU[2] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.106 Miner: Error ******** GPU[2] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.108 Miner: Error ******** GPU[3] CudaError: 702
16:43:12.111 Miner: Error ******** GPU[3] Not enough memory to run algo. GPU disabled.(0/1)
16:43:12.114 Miner: Error ******** GPU[3] Please check if your Virtual Memory setting is OK. You can also try to
16:43:12.115 Miner: Error ******** GPU[3] reduce the intensity/grid-size command line value to fix this problem.
16:43:12.116 Miner: Error ******** All GPUs are disabled. TT-Miner cannot continue and will exit now
16:43:12.125 POOL: Lost connection to zcoin-eu.mintpond.com:3000
16:43:12.126 POOL: Mining temporary stopped
Happening after 10, 30 , 60 minutes. randomly.. any clue ?
This is my config:
-A MTP-100 -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:[email protected]:3000 --api-bind 127.0.0.1:4033
I tried different intensity or grids..
gtx 1070 ti
using latest NVIDIA drivers
8 GB RAM, 32 GB virtual memory, Celeron CPU
PS: what OC is best for gtx 1070 ti ? increase core? mem ?
Hi,
the error 702 indicates a cuda-timeout. It takes too long until the kernel finishes and the driver terminates it. Please try to use intensities/grid sizes below 10240. For MTP I would start without any OC. Please try to get a stable configuration first.
You can make you command line somewhat simpler - so TT will find the best CUDA version for your installed driver/interface:
-A MTP -P abcdefghasjdhaklsdjallkajdl.worker:[email protected]:3000 --api-bind 127.0.0.1:4033
RAM and Virtual RAM looks OK - Celeron is fine as well.
I would guess you have a OC problem with GPU 0 and maybe GPU 1 - they show rejected shares (but I'm only guessing!).
Please let me know if removing OC helps?
thank you for reply TrailingStop
I tried different configs, memory +200 core +200, also tried MTP-100 and MTP-101
also tried -i auto 1024 10240 256
it finds best grid etc but still randomly crashing.
was using other miner before with +200/+200 and had no issues..
those rejected shares appeared on any of cards randomly..
PS: using Awesome miner and it adds the "stratum+tcp://" by default, do you think that can be problem?
if its not that, what you mean by your suggested config, cant see any difference ?
Will try to remove all OC
stratum+tcp is no problem. My config is almost identical to your. Since I develop the miner on these cards I do not try to get the last hashrate out of the GPU. I use defaults for most settings and no OC so that I can be sure to see crashes because of bad development, not because of bad OC settings.
Do you also use MTP if you run your cards with +200/+200?
Jump to: