Still the same thing on Windows 10 and 125,4 algo.
Your solver still wants to allocate 2524MB, and my cards only got 2480 memory free.
Nothing changed from the last version.
Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 42. (Read 59781 times)
August 23, 2019, 07:22:04 PM
August 23, 2019, 07:14:07 PM
Hi everyone,
Thanks a lot for your feedback and support!
You can find new miniZ v1.5q here.
In brief:
* Adjusted oc modes for ZelHash - 125,4. Major improvements for 1080Ti (>7%).
* Adjusted oc modes for BeamHashII - 150,5,3 with improvements.
* Improvements for ZHash - 144,5, for RTX cards.
* Further attempts to support ZEL mining on 3GB GPU, on Windows 10.
* Fixed support for 144,5 for 1050 2GB, on Windows 10.
* Fixed slow start for some GPUs/rigs.
* Added --csv option for log stats in csv format.
* Added busID to -ci output.
* Fixed issue connection to sparkpool.
* Fixed invalid shares on flypool.
* Other minor bug fixes.
Check performances here. Or performances page for each algorithm.
For additional information check our Usage or FAQ pages.
Happy mining!
Thanks a lot for your feedback and support!
You can find new miniZ v1.5q here.
In brief:
* Adjusted oc modes for ZelHash - 125,4. Major improvements for 1080Ti (>7%).
* Adjusted oc modes for BeamHashII - 150,5,3 with improvements.
* Improvements for ZHash - 144,5, for RTX cards.
* Further attempts to support ZEL mining on 3GB GPU, on Windows 10.
* Fixed support for 144,5 for 1050 2GB, on Windows 10.
* Fixed slow start for some GPUs/rigs.
* Added --csv option for log stats in csv format.
* Added busID to -ci output.
* Fixed issue connection to sparkpool.
* Fixed invalid shares on flypool.
* Other minor bug fixes.
Check performances here. Or performances page for each algorithm.
For additional information check our Usage or FAQ pages.
Happy mining!
August 23, 2019, 09:07:08 AM
@miniz, what is window size for calculating averages?
I need to figure out minimal amount of time to wait before I can use your average hashrate as real average hashrate, give or take. Let's say I gonna benchmark some algo against every power level to find out a sweet spot. If that averaging window is like past 5 mins, I don't have to run miner for 10 minutes, right?
Hi 2h4u,I need to figure out minimal amount of time to wait before I can use your average hashrate as real average hashrate, give or take. Let's say I gonna benchmark some algo against every power level to find out a sweet spot. If that averaging window is like past 5 mins, I don't have to run miner for 10 minutes, right?
the Sol/s averages you read in the console output are a short 3min average, and a long 3h average (in brackets).
However, for benchmarking purposes the I/s are much more suitable than the Sol/s (we show 3min average).
I/s stabilize much faster ~3-4min, and the Sol/s ~3-4h.
We are about to make a release later in the day.
Cheers
August 23, 2019, 09:04:35 AM
Thank you for your work.
We hope you can do it.
Would be glad to start mining ZEL again on my win 10 rigs.
Thank you.
Hi Valter84,
we are about to make a new release today where we further attempt to make it work.
You should be aware that if it works in Windows 10, the performance is a bit worse than in other OS.
Cheers
August 23, 2019, 03:11:53 AM
@miniz, what is window size for calculating averages?
I need to figure out minimal amount of time to wait before I can use your average hashrate as real average hashrate, give or take. Let's say I gonna benchmark some algo against every power level to find out a sweet spot. If that averaging window is like past 5 mins, I don't have to run miner for 10 minutes, right?
I need to figure out minimal amount of time to wait before I can use your average hashrate as real average hashrate, give or take. Let's say I gonna benchmark some algo against every power level to find out a sweet spot. If that averaging window is like past 5 mins, I don't have to run miner for 10 minutes, right?
August 22, 2019, 06:19:43 AM
Hi RelaxedCrypto, MineOrDie,
Apparently our solver has not shrink enough to fit in your cards.
We keep trying to improve this for the next version.
Cheers
We hope you can do it.
Would be glad to start mining ZEL again on my win 10 rigs.
Thank you.
August 20, 2019, 06:45:25 PM
Looks like I have found the cause. This situation happens only when an additional CPU miner is working. I put it on hold, restarted miniZ and woa--there's no problem at all. Must say that gminer and cryptodredge not that touchy at all.
Hi 2h4u,Thanks for the extra information.
We managed to understand the cause.
We fixed this and it will be OK in the next version.
Cheers
August 20, 2019, 06:43:32 PM
Well, the problem with Flypool invalid shares still exists.
Hi MineOrDie,we think we may have spot the issue.
It will be fixed in the next release.
Thanks.
Cheers
August 19, 2019, 11:12:25 PM
Looks like I have found the cause. This situation happens only when an additional CPU miner is working. I put it on hold, restarted miniZ and woa--there's no problem at all. Must say that gminer and cryptodredge not that touchy at all.
August 19, 2019, 10:57:17 PM
thank you for all the information. We're looking into it.
More logs. No hashes and no nvml info for 5 mins. HiveOS.
Code:
[ 0d 0h 5m17s|10:45:28 20/08/2019] S:150/0 188(187.6)Sol/s 35( 34.9)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 101ms (93.1%) (6.9%)
0>GTX 1070 Ti `S: 40/0 [47°C/35%] 21.64 I/s 43.2(43.1)Sol/s 35( 34.9)W clk=1657MHz mclk=4536MHz Sol/W=1.23
1>P106-100 `S: 0/0 [0°C/ 0%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=-nan
2>P106-100 `S: 19/0 [0°C/ 0%]*10.54 I/s 20.8(20.9)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf
3>P106-100 `S: 0/0 [0°C/ 0%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=-nan
4>GTX 1060 6GB `S: 30/0 [0°C/ 0%]*12.84 I/s 26.0(25.9)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf
5>GTX 1060 6GB `S: 12/0 [0°C/ 0%] 13.20 I/s 25.7(25.7)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf
6>GTX 1060 6GB `S: 16/0 [0°C/ 0%] 12.56 I/s 24.8(24.7)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf
7>GTX 1060 6GB `S: 13/0 [0°C/ 0%]*11.07 I/s 21.9(21.9)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf
8>GTX 1050 Ti `S: 10/0 [0°C/ 0%] 6.19 I/s 12.2(12.2)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf
9>GTX 1050 Ti `S: 10/0 [0°C/ 0%] 6.62 I/s 13.4(13.3)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf
[ 0d 0h 5m27s|10:45:38 20/08/2019] S:151/0 188(187.8)Sol/s 725(725.4)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 100ms (93.3%) (6.7%)
0>GTX 1070 Ti `S: 40/0 [47°C/35%] 21.63 I/s 43.2(43.0)Sol/s 35( 34.9)W clk=1657MHz mclk=4536MHz Sol/W=1.23
1>P106-100 `S: 0/0 [44°C/37%] 0.01 I/s 0.0( 0.0)Sol/s 29( 29.3)W clk=1506MHz mclk=4665MHz Sol/W=0.00
2>P106-100 `S: 19/0 [67°C/46%] 10.54 I/s 20.9(20.9)Sol/s 73( 72.5)W clk=1506MHz mclk=4738MHz Sol/W=0.29
3>P106-100 `S: 0/0 [55°C/35%] 0.01 I/s 0.0( 0.0)Sol/s 67( 67.4)W clk=1480MHz mclk=4437MHz Sol/W=0.00
4>GTX 1060 6GB `S: 30/0 [67°C/55%] 12.84 I/s 26.3(26.1)Sol/s 90( 89.9)W clk=1873MHz mclk=4363MHz Sol/W=0.29
5>GTX 1060 6GB `S: 12/0 [66°C/62%] 13.20 I/s 25.8(25.8)Sol/s 104(103.5)W clk=1949MHz mclk=4437MHz Sol/W=0.25
6>GTX 1060 6GB `S: 17/0 [66°C/64%]*12.56 I/s 24.7(24.7)Sol/s 103(102.7)W clk=1835MHz mclk=4404MHz Sol/W=0.24
7>GTX 1060 6GB `S: 13/0 [67°C/56%] 11.07 I/s 21.7(21.8)Sol/s 75( 75.0)W clk=1645MHz mclk=4568MHz Sol/W=0.29
8>GTX 1050 Ti `S: 10/0 [62°C/36%] 6.20 I/s 12.4(12.3)Sol/s 75( 75.0)W clk=1835MHz mclk=4058MHz Sol/W=0.16
9>GTX 1050 Ti `S: 10/0 [55°C/35%] 6.62 I/s 13.4(13.3)Sol/s 75( 75.0)W clk=1822MHz mclk=4380MHz Sol/W=0.18
[ 0d 0h 5m37s|10:45:48 20/08/2019] S:154/0 192(190.1)Sol/s 918(825.3)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 107ms (93.5%) (6.5%)
0>GTX 1070 Ti `S: 41/0 [67°C/43%]*21.62 I/s 43.2(43.1)Sol/s 217(133.6)W clk=1759MHz mclk=4536MHz Sol/W=0.32
1>P106-100 `S: 0/0 [51°C/36%] 12.64 I/s 23.0(23.0)Sol/s 60( 32.8)W clk=1822MHz mclk=4665MHz Sol/W=0.70
2>P106-100 `S: 19/0 [68°C/47%] 10.54 I/s 20.7(20.9)Sol/s 74( 72.7)W clk=1506MHz mclk=4738MHz Sol/W=0.29
3>P106-100 `S: 0/0 [59°C/35%] 10.38 I/s 24.4(24.4)Sol/s 64( 67.0)W clk=1455MHz mclk=4437MHz Sol/W=0.36
4>GTX 1060 6GB `S: 31/0 [67°C/55%]*12.83 I/s 26.4(26.2)Sol/s 82( 89.0)W clk=1873MHz mclk=4363MHz Sol/W=0.29
5>GTX 1060 6GB `S: 12/0 [66°C/62%] 13.20 I/s 25.9(25.8)Sol/s 110(104.3)W clk=1949MHz mclk=4437MHz Sol/W=0.25
6>GTX 1060 6GB `S: 17/0 [66°C/64%] 12.55 I/s 25.0(24.8)Sol/s 102(102.6)W clk=1822MHz mclk=4404MHz Sol/W=0.24
7>GTX 1060 6GB `S: 14/0 [67°C/57%]*11.06 I/s 21.8(21.8)Sol/s 61( 73.4)W clk=1594MHz mclk=4568MHz Sol/W=0.30
8>GTX 1050 Ti `S: 10/0 [63°C/35%] 6.19 I/s 12.4(12.3)Sol/s 75( 75.0)W clk=1835MHz mclk=4058MHz Sol/W=0.16
9>GTX 1050 Ti `S: 10/0 [55°C/35%] 6.62 I/s 13.3(13.3)Sol/s 75( 75.0)W clk=1835MHz mclk=4380MHz Sol/W=0.18
[ 0d 0h 5m47s|10:45:58 20/08/2019] S:158/0 197(192.8)Sol/s 886(827.0)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 252ms (93.7%) (6.3%)
0>GTX 1070 Ti `S: 42/0 [67°C/44%]*21.61 I/s 43.2(43.1)Sol/s 180(134.2)W clk=1746MHz mclk=4536MHz Sol/W=0.32
1>P106-100 `S: 0/0 [54°C/38%] 12.64 I/s 25.8(25.8)Sol/s 77( 36.3)W clk=1822MHz mclk=4665MHz Sol/W=0.71
2>P106-100 `S: 19/0 [68°C/47%] 10.54 I/s 20.9(20.9)Sol/s 70( 72.4)W clk=1493MHz mclk=4738MHz Sol/W=0.29
3>P106-100 `S: 0/0 [61°C/38%] 10.39 I/s 22.4(22.4)Sol/s 60( 66.4)W clk=1442MHz mclk=4437MHz Sol/W=0.34
4>GTX 1060 6GB `S: 32/0 [67°C/56%]*12.83 I/s 26.5(26.2)Sol/s 96( 90.2)W clk=1860MHz mclk=4363MHz Sol/W=0.29
5>GTX 1060 6GB `S: 12/0 [66°C/62%] 13.20 I/s 25.7(25.8)Sol/s 112(104.8)W clk=1949MHz mclk=4437MHz Sol/W=0.25
6>GTX 1060 6GB `S: 17/0 [66°C/64%] 12.55 I/s 24.9(24.8)Sol/s 85(100.6)W clk=1822MHz mclk=4404MHz Sol/W=0.25
7>GTX 1060 6GB `S: 14/0 [67°C/57%] 11.06 I/s 22.1(22.0)Sol/s 55( 72.1)W clk=1594MHz mclk=4568MHz Sol/W=0.30
8>GTX 1050 Ti `S: 11/0 [62°C/37%]* 6.19 I/s 12.5(12.4)Sol/s 75( 75.0)W clk=1847MHz mclk=4058MHz Sol/W=0.16
9>GTX 1050 Ti `S: 11/0 [55°C/35%]* 6.62 I/s 13.6(13.4)Sol/s 75( 75.0)W clk=1822MHz mclk=4380MHz Sol/W=0.18
August 19, 2019, 06:20:21 PM
Well, the problem with Flypool invalid shares still exists.
August 19, 2019, 06:03:16 PM
--localtime=[11,14] - I meant --localtime=11 and --localtime=14 and its not working. I tried localtime with 11~14 everyone number from this diapason and its not working
Hi 91to,could you paste here your command line?
We tried and see no problem:
Code:
./miniZ --url 0xa074dd01441a2618296590e0d5fb69603624e8aa0251decec9f81c9f050a84c3.rig@aion-eu.luxor.tech:3366 --extra --localtime=14
************ miniZ v1.5p ************
Number of CUDA[8.0] devices found: 1
miniZ,210,9[3:1:00:1939]: Selecting GPU#1[0] GeForce GTX 1050
Algo: EQ[210,9]
Pool#0: user[0xa074dd01441a2618296590e0d5fb69603624e8aa0251decec9f81c9f050a84c3.rig1]
server[aion-eu.luxor.tech] port[3366] ssl[no] pers[AION0PoW]
Telemetry: [http://localhost:20000]
Temp. limit: [90°C]
[ 0d 0h 0m10s|Aug 20 00:40:53] S: 0/0 0>GTX 1050 ` 100% [48°C/38%] 37.57 I/s 73.3(73.3)Sol/s 75( 75.0)W clk=1746MHz mclk=3504MHz Sol/W=0.98 [aion-eu.luxor.tech] (100.0%) (0.0%)
[ 0d 0h 0m20s|Aug 20 00:41:03] S: 0/0 0>GTX 1050 ` 100% [56°C/41%] 38.26 I/s 72.9(72.9)Sol/s 75( 75.0)W clk=1746MHz mclk=3504MHz Sol/W=0.97 [aion-eu.luxor.tech] (100.0%) (0.0%)
[ 0d 0h 0m30s|Aug 20 00:41:13] S: 0/0 0>GTX 1050 ` 100% [59°C/43%] 38.45 I/s 74.4(74.4)Sol/s 75( 75.0)W clk=1733MHz mclk=3504MHz Sol/W=0.99 [aion-eu.luxor.tech] (100.0%) (0.0%)
[ 0d 0h 0m40s|Aug 20 00:41:23] S: 0/0 0>GTX 1050 ` 100% [60°C/45%] 38.52 I/s 73.1(73.1)Sol/s 75( 75.0)W clk=1733MHz mclk=3504MHz Sol/W=0.98 [aion-eu.luxor.tech] (100.0%) (0.0%)
Let us know if you managed to get it work.
Cheers
August 19, 2019, 01:41:30 PM
--localtime=[11,14] - I meant --localtime=11 and --localtime=14 and its not working. I tried localtime with 11~14 everyone number from this diapason and its not working
August 19, 2019, 11:01:29 AM
hello! How to make to show local time in miner window? --localtime=[11,14] is not working
Hi 91to,you need to specify a number, from 11 to 14, not [11,14].
Ex. if --localtime=13 you get the following format:
[ 0d 0h 0m10s|15:44:03]
Cheers
August 19, 2019, 10:59:59 AM
Good day.
miniZ v1.4o zel W7-64
fee-all
1d15h 1m19s] S:1279/0 81(81.0)Sol/s 313(318.6)W [zel.2miners.com] (98.0%) (2.0%)
0>GTX 1060 3GB 100% [62шC/63%] 10.28 I/s 20.2(20.4)Sol/s 83( 79.7)W clk=1670MHz mclk=4201MHz Sol/W=0.26
1>GTX 1060 3GB 100% [60шC/60%] 10.18 I/s 20.4(20.2)Sol/s 78( 79.0)W clk=1645MHz mclk=4201MHz Sol/W=0.26
2>GTX 1060 3GB 100% [60шC/60%] 10.27 I/s 20.2(20.4)Sol/s 77( 79.4)W clk=1670MHz mclk=4201MHz Sol/W=0.26
3>GTX 1060 3GB 100% [58шC/56%] 10.12 I/s 20.1(20.1)Sol/s 75( 79.3)W clk=1645MHz mclk=4201MHz Sol/W=0.25
[ 1d15h 1m29s] S:1279/0 81(81.0)Sol/s 314(318.5)W [fee.server] (9.0%) (0.2%)
Hi Ziv1,miniZ v1.4o zel W7-64
fee-all
1d15h 1m19s] S:1279/0 81(81.0)Sol/s 313(318.6)W [zel.2miners.com] (98.0%) (2.0%)
0>GTX 1060 3GB 100% [62шC/63%] 10.28 I/s 20.2(20.4)Sol/s 83( 79.7)W clk=1670MHz mclk=4201MHz Sol/W=0.26
1>GTX 1060 3GB 100% [60шC/60%] 10.18 I/s 20.4(20.2)Sol/s 78( 79.0)W clk=1645MHz mclk=4201MHz Sol/W=0.26
2>GTX 1060 3GB 100% [60шC/60%] 10.27 I/s 20.2(20.4)Sol/s 77( 79.4)W clk=1670MHz mclk=4201MHz Sol/W=0.26
3>GTX 1060 3GB 100% [58шC/56%] 10.12 I/s 20.1(20.1)Sol/s 75( 79.3)W clk=1645MHz mclk=4201MHz Sol/W=0.25
[ 1d15h 1m29s] S:1279/0 81(81.0)Sol/s 314(318.5)W [fee.server] (9.0%) (0.2%)
thanks for reporting. We are investigating this.
The second error, the one from April, had a different cause and it has been fixed.
There was a time/clock update which messed up the counters. This is now set up differently and it is fixed.
Cheers
August 19, 2019, 10:19:18 AM
Good day.
There was an interesting crash.
Mining time decreased by an hour and a permanent session fee.server started.
Good luck.
2>GTX 1060 3GB `99.7% [55шC/48%] 17.97 I/s 35.8(35.9)Sol/s 82( 87.3)W clk=1797MHz mclk=4404MHz Sol/W=0.41
3>GTX 1060 3GB `99.7% [55шC/48%] 17.65 I/s 35.0(35.1)Sol/s 92( 87.4)W clk=1784MHz mclk=4404MHz Sol/W=0.40
[ 0d14h38m36s] S:1167/6 143(141.8)Sol/s 353(349.8)W [btcz.2miners.com]- 76ms (98.0%) (2.0%)
0>GTX 1060 3GB `99.0% [54шC/45%] 17.57 I/s 35.7(35.1)Sol/s 88( 87.2)W clk=1771MHz mclk=4404MHz Sol/W=0.40
1>GTX 1060 3GB `99.6% [55шC/48%] 17.88 I/s 36.0(35.7)Sol/s 90( 87.7)W clk=1784MHz mclk=4404MHz Sol/W=0.41
2>GTX 1060 3GB `99.7% [55шC/48%] 17.97 I/s 36.0(35.9)Sol/s 86( 87.3)W clk=1809MHz mclk=4404MHz Sol/W=0.41
3>GTX 1060 3GB `99.7% [56шC/50%] 17.65 I/s 34.9(35.1)Sol/s 88( 87.4)W clk=1759MHz mclk=4404MHz Sol/W=0.40
[ 0d14h38m46s] S:1167/6 143(141.8)Sol/s 347(349.7)W [btcz.2miners.com]- 76ms (98.0%) (2.0%)
0>GTX 1060 3GB `99.0% [55шC/45%] 17.57 I/s 35.6(35.1)Sol/s 85( 87.2)W clk=1771MHz mclk=4404MHz Sol/W=0.40
1>GTX 1060 3GB `99.6% [55шC/48%] 17.88 I/s 36.0(35.7)Sol/s 88( 87.7)W clk=1784MHz mclk=4404MHz Sol/W=0.41
2>GTX 1060 3GB `99.7% [55шC/48%] 17.97 I/s 35.8(35.9)Sol/s 89( 87.3)W clk=1797MHz mclk=4404MHz Sol/W=0.41
3>GTX 1060 3GB `99.7% [56шC/50%] 17.65 I/s 34.9(35.1)Sol/s 86( 87.4)W clk=1784MHz mclk=4404MHz Sol/W=0.40
[ 0d14h38m56s] S:1167/6 143(141.8)Sol/s 342(349.4)W [fee.server]- 75ms (98.0%) (2.0%)
0>GTX 1060 3GB `99.0% [55шC/48%] 17.57 I/s 35.6(35.1)Sol/s 84( 87.2)W clk=1733MHz mclk=4404MHz Sol/W=0.40
1>GTX 1060 3GB `99.6% [55шC/48%] 17.88 I/s 36.0(35.7)Sol/s 84( 87.7)W clk=1784MHz mclk=4404MHz Sol/W=0.41
2>GTX 1060 3GB `99.7% [55шC/48%] 17.97 I/s 35.9(35.9)Sol/s 90( 87.3)W clk=1797MHz mclk=4404MHz Sol/W=0.41
3>GTX 1060 3GB `99.7% [55шC/48%] 17.65 I/s 35.4(35.1)Sol/s 84( 87.4)W clk=1759MHz mclk=4404MHz Sol/W=0.40
[ 0d13h39m04s] S:1169/6 144(141.8)Sol/s 345(349.4)W [fee.server]- 76ms (105.2%) (-5.2%)
0>GTX 1060 3GB `99.0% [54шC/45%] 17.57 I/s 35.5(35.1)Sol/s 85( 87.2)W clk=1746MHz mclk=4404MHz Sol/W=0.40
1>GTX 1060 3GB `99.6% [55шC/48%]*17.88 I/s 35.7(35.7)Sol/s 83( 87.7)W clk=1784MHz mclk=4404MHz Sol/W=0.41
2>GTX 1060 3GB `99.7% [55шC/48%] 17.97 I/s 36.5(35.9)Sol/s 91( 87.3)W clk=1797MHz mclk=4404MHz Sol/W=0.41
3>GTX 1060 3GB `99.7% [55шC/48%] 17.65 I/s 35.8(35.1)Sol/s 85( 87.4)W clk=1759MHz mclk=4404MHz Sol/W=0.40
[ 0d13h39m14s] S:1172/6 144(141.8)Sol/s 348(349.5)W [fee.server]- 76ms (105.2%) (-5.2%)
0>GTX 1060 3GB `99.0% [54шC/48%]*17.57 I/s 35.5(35.1)Sol/s 86( 87.2)W clk=1746MHz mclk=4404MHz Sol/W=0.40
1>GTX 1060 3GB `99.6% [55шC/48%] 17.88 I/s 36.2(35.7)Sol/s 80( 87.6)W clk=1784MHz mclk=4404MHz Sol/W=0.41
2>GTX 1060 3GB `99.7% [55шC/48%]*17.97 I/s 35.8(35.9)Sol/s 92( 87.3)W clk=1797MHz mclk=4404MHz Sol/W=0.41
3>GTX 1060 3GB `99.7% [55шC/48%] 17.65 I/s 35.9(35.1)Sol/s 90( 87.4)W clk=1784MHz mclk=4404MHz Sol/W=0.40
[ 0d13h39m24s] S:1174/6 144(141.8)Sol/s 339(349.1)W [fee.server]- 76ms (105.1%) (-5.1%)
0>GTX 1060 3GB `99.0% [54шC/45%] 17.57 I/s 35.5(35.1)Sol/s 89( 87.2)W clk=1771MHz mclk=4404MHz Sol/W=0.40
1>GTX 1060 3GB `99.6% [55шC/48%] 17.88 I/s 36.1(35.7)Sol/s 80( 87.6)W clk=1784MHz mclk=4404MHz Sol/W=0.41
2>GTX 1060 3GB `99.7% [55шC/48%]*17.97 I/s 35.8(35.9)Sol/s 85( 87.3)W clk=1784MHz mclk=4404MHz Sol/W=0.41
3>GTX 1060 3GB `99.7% [55шC/50%]*17.65 I/s 35.7(35.1)Sol/s 86( 87.4)W clk=1759MHz mclk=4404MHz Sol/W=0.40
August 19, 2019, 07:56:40 AM
hello! How to make to show local time in miner window? --localtime=[11,14] is not working
August 19, 2019, 04:51:25 AM
Good day.
miniZ v1.4o zel W7-64
fee-all
1d15h 1m19s] S:1279/0 81(81.0)Sol/s 313(318.6)W [zel.2miners.com] (98.0%) (2.0%)
0>GTX 1060 3GB 100% [62шC/63%] 10.28 I/s 20.2(20.4)Sol/s 83( 79.7)W clk=1670MHz mclk=4201MHz Sol/W=0.26
1>GTX 1060 3GB 100% [60шC/60%] 10.18 I/s 20.4(20.2)Sol/s 78( 79.0)W clk=1645MHz mclk=4201MHz Sol/W=0.26
2>GTX 1060 3GB 100% [60шC/60%] 10.27 I/s 20.2(20.4)Sol/s 77( 79.4)W clk=1670MHz mclk=4201MHz Sol/W=0.26
3>GTX 1060 3GB 100% [58шC/56%] 10.12 I/s 20.1(20.1)Sol/s 75( 79.3)W clk=1645MHz mclk=4201MHz Sol/W=0.25
[ 1d15h 1m29s] S:1279/0 81(81.0)Sol/s 314(318.5)W [fee.server] (9.0%) (0.2%)
0>GTX 1060 3GB 100% [62шC/62%] 10.28 I/s 20.2(20.4)Sol/s 81( 79.7)W clk=1683MHz mclk=4201MHz Sol/W=0.26
1>GTX 1060 3GB 100% [60шC/60%] 10.18 I/s 20.3(20.2)Sol/s 81( 79.0)W clk=1657MHz mclk=4201MHz Sol/W=0.26
2>GTX 1060 3GB 100% [60шC/60%] 10.27 I/s 20.4(20.4)Sol/s 75( 79.4)W clk=1670MHz mclk=4201MHz Sol/W=0.26
3>GTX 1060 3GB 100% [58шC/56%] 10.12 I/s 20.1(20.1)Sol/s 76( 79.3)W clk=1645MHz mclk=4201MHz Sol/W=0.25
[ 1d15h 1m39s] S:1279/0 81(81.0)Sol/s 314(318.5)W [fee.server] (9.0%) (0.2%)
0>GTX 1060 3GB 100% [62шC/62%] 10.28 I/s 20.2(20.4)Sol/s 81( 79.7)W clk=1721MHz mclk=4201MHz Sol/W=0.26
1>GTX 1060 3GB 100% [60шC/60%] 10.18 I/s 20.3(20.2)Sol/s 79( 79.0)W clk=1657MHz mclk=4201MHz Sol/W=0.26
2>GTX 1060 3GB 100% [60шC/60%] 10.26 I/s 20.7(20.4)Sol/s 75( 79.4)W clk=1670MHz mclk=4201MHz Sol/W=0.26
3>GTX 1060 3GB 100% [58шC/56%] 10.12 I/s 20.2(20.1)Sol/s 80( 79.3)W clk=1645MHz mclk=4201MHz Sol/W=0.25
[ 1d15h 1m49s] S:1279/0 81(81.0)Sol/s 312(318.3)W [fee.server] (9.0%) (0.2%)
0>GTX 1060 3GB 100% [62шC/63%] 10.28 I/s 20.1(20.4)Sol/s 80( 79.7)W clk=1670MHz mclk=4201MHz Sol/W=0.26
1>GTX 1060 3GB 100% [59шC/60%] 10.18 I/s 20.4(20.2)Sol/s 79( 79.0)W clk=1708MHz mclk=4201MHz Sol/W=0.26
2>GTX 1060 3GB 100% [60шC/60%] 10.27 I/s 20.6(20.4)Sol/s 75( 79.4)W clk=1670MHz mclk=4201MHz Sol/W=0.26
3>GTX 1060 3GB 100% [58шC/56%] 10.12 I/s 20.3(20.1)Sol/s 77( 79.3)W clk=1670MHz mclk=4201MHz Sol/W=0.25
[ 1d15h 1m59s] S:1279/0 81(81.0)Sol/s 316(318.3)W [fee.server] (9.0%) (0.2%)
0>GTX 1060 3GB 100% [62шC/63%] 10.28 I/s 20.0(20.4)Sol/s 83( 79.7)W clk=1670MHz mclk=4201MHz Sol/W=0.26
1>GTX 1060 3GB 100% [60шC/60%] 10.18 I/s 20.6(20.2)Sol/s 77( 79.0)W clk=1683MHz mclk=4201MHz Sol/W=0.26
2>GTX 1060 3GB 100% [60шC/60%] 10.27 I/s 20.7(20.4)Sol/s 80( 79.4)W clk=1670MHz mclk=4201MHz Sol/W=0.26
3>GTX 1060 3GB 100% [58шC/56%] 10.12 I/s 20.4(20.1)Sol/s 76( 79.3)W clk=1645MHz mclk=4201MHz Sol/W=0.25
[ 1d15h 2m09s] S:1279/0 82(81.1)Sol/s 321(318.5)W [fee.server] (9.0%) (0.2%)
0>GTX 1060 3GB 100% [61шC/63%] 10.28 I/s 20.0(20.4)Sol/s 80( 79.7)W clk=1721MHz mclk=4201MHz Sol/W=0.26
1>GTX 1060 3GB 100% [60шC/59%] 10.18 I/s 20.7(20.2)Sol/s 80( 79.0)W clk=1645MHz mclk=4201MHz Sol/W=0.26
2>GTX 1060 3GB 100% [60шC/60%] 10.27 I/s 20.7(20.4)Sol/s 79( 79.4)W clk=1670MHz mclk=4201MHz Sol/W=0.26
3>GTX 1060 3GB 100% [58шC/56%] 10.12 I/s 20.2(20.1)Sol/s 81( 79.3)W clk=1670MHz mclk=4201MHz Sol/W=0.25
[ 1d15h 2m19s] S:1279/0 82(81.1)Sol/s 321(318.5)W [fee.server] (9.0%) (0.2%)
miniZ v1.4o zel W7-64
fee-all
1d15h 1m19s] S:1279/0 81(81.0)Sol/s 313(318.6)W [zel.2miners.com] (98.0%) (2.0%)
0>GTX 1060 3GB 100% [62шC/63%] 10.28 I/s 20.2(20.4)Sol/s 83( 79.7)W clk=1670MHz mclk=4201MHz Sol/W=0.26
1>GTX 1060 3GB 100% [60шC/60%] 10.18 I/s 20.4(20.2)Sol/s 78( 79.0)W clk=1645MHz mclk=4201MHz Sol/W=0.26
2>GTX 1060 3GB 100% [60шC/60%] 10.27 I/s 20.2(20.4)Sol/s 77( 79.4)W clk=1670MHz mclk=4201MHz Sol/W=0.26
3>GTX 1060 3GB 100% [58шC/56%] 10.12 I/s 20.1(20.1)Sol/s 75( 79.3)W clk=1645MHz mclk=4201MHz Sol/W=0.25
[ 1d15h 1m29s] S:1279/0 81(81.0)Sol/s 314(318.5)W [fee.server] (9.0%) (0.2%)
0>GTX 1060 3GB 100% [62шC/62%] 10.28 I/s 20.2(20.4)Sol/s 81( 79.7)W clk=1683MHz mclk=4201MHz Sol/W=0.26
1>GTX 1060 3GB 100% [60шC/60%] 10.18 I/s 20.3(20.2)Sol/s 81( 79.0)W clk=1657MHz mclk=4201MHz Sol/W=0.26
2>GTX 1060 3GB 100% [60шC/60%] 10.27 I/s 20.4(20.4)Sol/s 75( 79.4)W clk=1670MHz mclk=4201MHz Sol/W=0.26
3>GTX 1060 3GB 100% [58шC/56%] 10.12 I/s 20.1(20.1)Sol/s 76( 79.3)W clk=1645MHz mclk=4201MHz Sol/W=0.25
[ 1d15h 1m39s] S:1279/0 81(81.0)Sol/s 314(318.5)W [fee.server] (9.0%) (0.2%)
0>GTX 1060 3GB 100% [62шC/62%] 10.28 I/s 20.2(20.4)Sol/s 81( 79.7)W clk=1721MHz mclk=4201MHz Sol/W=0.26
1>GTX 1060 3GB 100% [60шC/60%] 10.18 I/s 20.3(20.2)Sol/s 79( 79.0)W clk=1657MHz mclk=4201MHz Sol/W=0.26
2>GTX 1060 3GB 100% [60шC/60%] 10.26 I/s 20.7(20.4)Sol/s 75( 79.4)W clk=1670MHz mclk=4201MHz Sol/W=0.26
3>GTX 1060 3GB 100% [58шC/56%] 10.12 I/s 20.2(20.1)Sol/s 80( 79.3)W clk=1645MHz mclk=4201MHz Sol/W=0.25
[ 1d15h 1m49s] S:1279/0 81(81.0)Sol/s 312(318.3)W [fee.server] (9.0%) (0.2%)
0>GTX 1060 3GB 100% [62шC/63%] 10.28 I/s 20.1(20.4)Sol/s 80( 79.7)W clk=1670MHz mclk=4201MHz Sol/W=0.26
1>GTX 1060 3GB 100% [59шC/60%] 10.18 I/s 20.4(20.2)Sol/s 79( 79.0)W clk=1708MHz mclk=4201MHz Sol/W=0.26
2>GTX 1060 3GB 100% [60шC/60%] 10.27 I/s 20.6(20.4)Sol/s 75( 79.4)W clk=1670MHz mclk=4201MHz Sol/W=0.26
3>GTX 1060 3GB 100% [58шC/56%] 10.12 I/s 20.3(20.1)Sol/s 77( 79.3)W clk=1670MHz mclk=4201MHz Sol/W=0.25
[ 1d15h 1m59s] S:1279/0 81(81.0)Sol/s 316(318.3)W [fee.server] (9.0%) (0.2%)
0>GTX 1060 3GB 100% [62шC/63%] 10.28 I/s 20.0(20.4)Sol/s 83( 79.7)W clk=1670MHz mclk=4201MHz Sol/W=0.26
1>GTX 1060 3GB 100% [60шC/60%] 10.18 I/s 20.6(20.2)Sol/s 77( 79.0)W clk=1683MHz mclk=4201MHz Sol/W=0.26
2>GTX 1060 3GB 100% [60шC/60%] 10.27 I/s 20.7(20.4)Sol/s 80( 79.4)W clk=1670MHz mclk=4201MHz Sol/W=0.26
3>GTX 1060 3GB 100% [58шC/56%] 10.12 I/s 20.4(20.1)Sol/s 76( 79.3)W clk=1645MHz mclk=4201MHz Sol/W=0.25
[ 1d15h 2m09s] S:1279/0 82(81.1)Sol/s 321(318.5)W [fee.server] (9.0%) (0.2%)
0>GTX 1060 3GB 100% [61шC/63%] 10.28 I/s 20.0(20.4)Sol/s 80( 79.7)W clk=1721MHz mclk=4201MHz Sol/W=0.26
1>GTX 1060 3GB 100% [60шC/59%] 10.18 I/s 20.7(20.2)Sol/s 80( 79.0)W clk=1645MHz mclk=4201MHz Sol/W=0.26
2>GTX 1060 3GB 100% [60шC/60%] 10.27 I/s 20.7(20.4)Sol/s 79( 79.4)W clk=1670MHz mclk=4201MHz Sol/W=0.26
3>GTX 1060 3GB 100% [58шC/56%] 10.12 I/s 20.2(20.1)Sol/s 81( 79.3)W clk=1670MHz mclk=4201MHz Sol/W=0.25
[ 1d15h 2m19s] S:1279/0 82(81.1)Sol/s 321(318.5)W [fee.server] (9.0%) (0.2%)
August 18, 2019, 06:32:34 PM
Hi,
Can you please confirm that your miner is working correctly with Sparkpool? Because me, and few other people run into issues.
Can you please confirm that your miner is working correctly with Sparkpool? Because me, and few other people run into issues.
Same here, I can't connect to sparkpool anymore using miniz (for beam mining at least), other pools seem to work fine.
thanks a lot for reporting this.
We already fixed it. The pool changed a login message sent in the stratum, which is not the standard for Beam.
Sparkpool should work again in the next version. We will try to release it within the next couple of days.
Cheers
August 18, 2019, 06:28:41 PM
Regarding miniZ behaviour, does this happen always? Also, does it happen with all algorithms?
Could you also confirm that you are using Hive OS?
Could you also confirm that you are using Hive OS?
I have just overview all the logs and can tell this does happen like in 19 out of 20 cases. Average time before full power hashing is 3 minutes.
Didn't test other algos.
HiveOS, miniz 1.5p cuda 100. Driver version doesn't matter, I have 418.43, 430.14 and 418.56, all the same behaviour.
Oh, by the way, it's not only GPU0 and GPU1. In most cases it is, but sometimes it's another two (rarely 1 or 3) gpus. Something wrong with scheduler?
thank you for all the information. We're looking into it.
Cheers
Jump to: