Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 39. (Read 60004 times)
August 29, 2019, 12:51:17 PM
Pool is 2miners.com, I'm using latest version of miner, but this happened on every version I used before. So why would miner drop connection anyway? Or why it waits for minutes to reconnect rather do it right away?
August 29, 2019, 12:47:14 PM
Hi, MiniZ! Could you plz explain what's happening here: cards will periodically start idling for 1-2 mins until I\s and h\r start dropping and then "come back to live". Why doesn't miner show any error or something and why I\s h\r holding for 1-2 minutes when cards are idling??
Hi Divinity666,this may happen if the miner loses connection to the mining pool at some point.
For example, if there were no shares submitted for some time the connection can drop. And it restarts mining when connection is possible.
We are having a look in any case. Could you let us know what miniZ version are you using? And pool?
You use Windows 10 right? Mining Beam?
Thanks.
Cheers
August 29, 2019, 07:20:13 AM
Hi, MiniZ! Could you plz explain what's happening here: cards will periodically start idling for 1-2 mins until I\s and h\r start dropping and then "come back to live". Why doesn't miner show any error or something and why I\s h\r holding for 1-2 minutes when cards are idling??
Quote
[ 2d 2h10m00s|15:11:42 29/08/2019] 134(133.8)Sol/s 275(271.6)W
0>GTX 1080 ` 100% [54шC/29%] 33.45 I/s 66.5(66.5)Sol/s 137(133.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [54шC/34%] 33.78 I/s 67.7(67.2)Sol/s 138(134.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h10m11s|15:11:52 29/08/2019] 135(133.8)Sol/s 274(271.7)W
0>GTX 1080 ` 100% [54шC/29%] 33.45 I/s 67.0(66.5)Sol/s 135(133.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [54шC/32%] 33.78 I/s 67.9(67.3)Sol/s 139(134.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h10m21s|15:12:02 29/08/2019] 135(133.8)Sol/s 271(271.6)W
0>GTX 1080 ` 100% [54шC/30%] 33.45 I/s 66.9(66.5)Sol/s 135(133.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [54шC/33%] 33.78 I/s 68.1(67.3)Sol/s 137(134.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h10m31s|15:12:12 29/08/2019] 135(133.8)Sol/s 179(268.6)W
0>GTX 1080 ` 100% [49шC/22%] 33.45 I/s 66.9(66.5)Sol/s 89(132.9)W clk=1607MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [50шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 90(134.6)W clk=1670MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h10m41s|15:12:22 29/08/2019] 135(133.8)Sol/s 97(264.4)W
0>GTX 1080 ` 100% [48шC/10%] 33.45 I/s 66.9(66.5)Sol/s 48(132.8)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [48шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 49(134.5)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h10m51s|15:12:32 29/08/2019] 135(133.8)Sol/s 56(260.2)W
0>GTX 1080 ` 100% [46шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 28(132.7)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [46шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 28(134.5)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m01s|15:12:42 29/08/2019] 135(133.8)Sol/s 36(256.2)W
0>GTX 1080 ` 100% [45шC/16%] 33.45 I/s 66.9(66.5)Sol/s 18(132.7)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [45шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 18(134.4)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m11s|15:12:52 29/08/2019] 135(133.8)Sol/s 27(252.3)W
0>GTX 1080 ` 100% [44шC/21%] 33.45 I/s 66.9(66.5)Sol/s 12(132.6)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [43шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 15(134.3)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m21s|15:13:02 29/08/2019] 135(133.8)Sol/s 23(248.4)W
0>GTX 1080 ` 100% [43шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 10(132.5)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [42шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 13(134.2)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m31s|15:13:12 29/08/2019] 135(133.8)Sol/s 18(244.5)W
0>GTX 1080 ` 100% [42шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 8(132.4)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [41шC/25%] 33.78 I/s 68.1(67.3)Sol/s 10(134.1)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m41s|15:13:22 29/08/2019] 135(133.8)Sol/s 16(240.7)W
0>GTX 1080 ` 100% [42шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 8(132.3)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [40шC/27%] 33.78 I/s 68.1(67.3)Sol/s 9(134.0)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m51s|15:13:32 29/08/2019] 135(133.8)Sol/s 16(237.0)W
0>GTX 1080 ` 100% [41шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 7(132.2)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [39шC/11%] 33.78 I/s 68.1(67.3)Sol/s 9(133.9)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h12m01s|15:13:42 29/08/2019] 135(133.8)Sol/s 15(233.3)W
0>GTX 1080 ` 100% [40шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 7(132.1)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [38шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 8(133.8)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h12m11s|15:13:52 29/08/2019] 135(133.8)Sol/s 15(229.7)W
0>GTX 1080 ` 100% [39шC/20%] 33.45 I/s 66.9(66.5)Sol/s 7(132.0)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [37шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 8(133.8)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h12m21s|15:14:02 29/08/2019] 123(133.6)Sol/s 14(226.1)W
0>GTX 1080 ` 100% [38шC/22%] 30.47 I/s 61.0(66.4)Sol/s 7(132.0)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [36шC/ 0%] 30.72 I/s 61.9(67.2)Sol/s 7(133.7)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h12m31s|15:14:12 29/08/2019] 125(133.6)Sol/s 139(226.7)W
0>GTX 1080 ` 100% [44шC/ 0%] 30.76 I/s 61.9(66.4)Sol/s 69(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [41шC/ 0%] 31.02 I/s 62.5(67.2)Sol/s 70(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h12m41s|15:14:22 29/08/2019] 125(133.6)Sol/s 205(227.5)W
0>GTX 1080 ` 100% [46шC/ 0%] 31.02 I/s 61.9(66.4)Sol/s 100(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [42шC/ 0%] 31.29 I/s 63.0(67.2)Sol/s 105(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h12m51s|15:14:32 29/08/2019] 126(133.6)Sol/s 237(228.2)W
0>GTX 1080 ` 100% [47шC/ 0%] 31.25 I/s 62.7(66.4)Sol/s 119(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [44шC/ 0%] 31.54 I/s 63.4(67.2)Sol/s 118(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h13m01s|15:14:42 29/08/2019] 127(133.6)Sol/s 254(228.9)W
0>GTX 1080 ` 100% [49шC/23%] 31.47 I/s 63.2(66.4)Sol/s 129(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [45шC/25%] 31.76 I/s 63.7(67.2)Sol/s 125(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h13m11s|15:14:52 29/08/2019] 127(133.6)Sol/s 264(229.6)W
0>GTX 1080 ` 100% [51шC/11%] 31.66 I/s 63.3(66.4)Sol/s 132(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [47шC/25%] 31.96 I/s 64.2(67.2)Sol/s 132(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h13m21s|15:15:03 29/08/2019] 128(133.6)Sol/s 268(230.3)W
0>GTX 1080 ` 100% [52шC/19%] 31.83 I/s 63.0(66.4)Sol/s 133(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [48шC/26%] 32.14 I/s 64.7(67.2)Sol/s 135(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
0>GTX 1080 ` 100% [54шC/29%] 33.45 I/s 66.5(66.5)Sol/s 137(133.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [54шC/34%] 33.78 I/s 67.7(67.2)Sol/s 138(134.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h10m11s|15:11:52 29/08/2019] 135(133.8)Sol/s 274(271.7)W
0>GTX 1080 ` 100% [54шC/29%] 33.45 I/s 67.0(66.5)Sol/s 135(133.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [54шC/32%] 33.78 I/s 67.9(67.3)Sol/s 139(134.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h10m21s|15:12:02 29/08/2019] 135(133.8)Sol/s 271(271.6)W
0>GTX 1080 ` 100% [54шC/30%] 33.45 I/s 66.9(66.5)Sol/s 135(133.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [54шC/33%] 33.78 I/s 68.1(67.3)Sol/s 137(134.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h10m31s|15:12:12 29/08/2019] 135(133.8)Sol/s 179(268.6)W
0>GTX 1080 ` 100% [49шC/22%] 33.45 I/s 66.9(66.5)Sol/s 89(132.9)W clk=1607MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [50шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 90(134.6)W clk=1670MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h10m41s|15:12:22 29/08/2019] 135(133.8)Sol/s 97(264.4)W
0>GTX 1080 ` 100% [48шC/10%] 33.45 I/s 66.9(66.5)Sol/s 48(132.8)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [48шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 49(134.5)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h10m51s|15:12:32 29/08/2019] 135(133.8)Sol/s 56(260.2)W
0>GTX 1080 ` 100% [46шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 28(132.7)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [46шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 28(134.5)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m01s|15:12:42 29/08/2019] 135(133.8)Sol/s 36(256.2)W
0>GTX 1080 ` 100% [45шC/16%] 33.45 I/s 66.9(66.5)Sol/s 18(132.7)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [45шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 18(134.4)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m11s|15:12:52 29/08/2019] 135(133.8)Sol/s 27(252.3)W
0>GTX 1080 ` 100% [44шC/21%] 33.45 I/s 66.9(66.5)Sol/s 12(132.6)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [43шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 15(134.3)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m21s|15:13:02 29/08/2019] 135(133.8)Sol/s 23(248.4)W
0>GTX 1080 ` 100% [43шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 10(132.5)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [42шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 13(134.2)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m31s|15:13:12 29/08/2019] 135(133.8)Sol/s 18(244.5)W
0>GTX 1080 ` 100% [42шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 8(132.4)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [41шC/25%] 33.78 I/s 68.1(67.3)Sol/s 10(134.1)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m41s|15:13:22 29/08/2019] 135(133.8)Sol/s 16(240.7)W
0>GTX 1080 ` 100% [42шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 8(132.3)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [40шC/27%] 33.78 I/s 68.1(67.3)Sol/s 9(134.0)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h11m51s|15:13:32 29/08/2019] 135(133.8)Sol/s 16(237.0)W
0>GTX 1080 ` 100% [41шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 7(132.2)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [39шC/11%] 33.78 I/s 68.1(67.3)Sol/s 9(133.9)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h12m01s|15:13:42 29/08/2019] 135(133.8)Sol/s 15(233.3)W
0>GTX 1080 ` 100% [40шC/ 0%] 33.45 I/s 66.9(66.5)Sol/s 7(132.1)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [38шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 8(133.8)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h12m11s|15:13:52 29/08/2019] 135(133.8)Sol/s 15(229.7)W
0>GTX 1080 ` 100% [39шC/20%] 33.45 I/s 66.9(66.5)Sol/s 7(132.0)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [37шC/ 0%] 33.78 I/s 68.1(67.3)Sol/s 8(133.8)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h12m21s|15:14:02 29/08/2019] 123(133.6)Sol/s 14(226.1)W
0>GTX 1080 ` 100% [38шC/22%] 30.47 I/s 61.0(66.4)Sol/s 7(132.0)W clk=139MHz mclk=405MHz Sol/W=0.50
1>GTX 1080 ` 100% [36шC/ 0%] 30.72 I/s 61.9(67.2)Sol/s 7(133.7)W clk=139MHz mclk=405MHz Sol/W=0.50
[ 2d 2h12m31s|15:14:12 29/08/2019] 125(133.6)Sol/s 139(226.7)W
0>GTX 1080 ` 100% [44шC/ 0%] 30.76 I/s 61.9(66.4)Sol/s 69(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [41шC/ 0%] 31.02 I/s 62.5(67.2)Sol/s 70(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h12m41s|15:14:22 29/08/2019] 125(133.6)Sol/s 205(227.5)W
0>GTX 1080 ` 100% [46шC/ 0%] 31.02 I/s 61.9(66.4)Sol/s 100(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [42шC/ 0%] 31.29 I/s 63.0(67.2)Sol/s 105(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h12m51s|15:14:32 29/08/2019] 126(133.6)Sol/s 237(228.2)W
0>GTX 1080 ` 100% [47шC/ 0%] 31.25 I/s 62.7(66.4)Sol/s 119(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [44шC/ 0%] 31.54 I/s 63.4(67.2)Sol/s 118(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h13m01s|15:14:42 29/08/2019] 127(133.6)Sol/s 254(228.9)W
0>GTX 1080 ` 100% [49шC/23%] 31.47 I/s 63.2(66.4)Sol/s 129(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [45шC/25%] 31.76 I/s 63.7(67.2)Sol/s 125(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h13m11s|15:14:52 29/08/2019] 127(133.6)Sol/s 264(229.6)W
0>GTX 1080 ` 100% [51шC/11%] 31.66 I/s 63.3(66.4)Sol/s 132(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [47шC/25%] 31.96 I/s 64.2(67.2)Sol/s 132(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
[ 2d 2h13m21s|15:15:03 29/08/2019] 128(133.6)Sol/s 268(230.3)W
0>GTX 1080 ` 100% [52шC/19%] 31.83 I/s 63.0(66.4)Sol/s 133(132.0)W clk=1746MHz mclk=5499MHz Sol/W=0.50
1>GTX 1080 ` 100% [48шC/26%] 32.14 I/s 64.7(67.2)Sol/s 135(133.7)W clk=1746MHz mclk=5499MHz Sol/W=0.50
August 29, 2019, 12:32:34 AM
Thanks for all the help!
[/quote]
Hi BigHarryArmsi,
the oc1 may get you a performance improvement, but this depends on your settings. It is good to try it and check which is best for your configuration.
You can add to the command line --oc1, or in your case bat file:
Regarding the red percentages, it seems that you had a few invalid shares and likely in the beginning. Did the red percentage turned green? Or at least is the percentage converging to 100?
This can happen, but it should be sporadic. Do let us know if it happens often.
Cheers
[/quote]
Both oc1 and oc2 slowed my hashing. OC1 especially, so I am running without either.
5)6gb MSI 1060s 65%-140-400 are ~20, MSI 1080 70%-135-350 is ~40
146 Sols at ~530w
And yes, the red %s are going away after a couple of hours, first going to dark pink then orange then to green. Expecting them all to go green before long. I had never seen reds before with miniZ on 144_5 so it was unnerving to see a sea of red!
Thanks again for the help. Will be tuning up another rig tomorrow!
[/quote]
Hi BigHarryArmsi,
the oc1 may get you a performance improvement, but this depends on your settings. It is good to try it and check which is best for your configuration.
You can add to the command line --oc1, or in your case bat file:
Code:
:loop
.\miniZ.exe --url=ssl://1442d0fab48a6d76dee30643ff01d9b7e83790df46f6b7e69a72e891c028202f.1060s@beam.sunpool.top:3334 --oc1
timeout /t 5
goto loop
Regarding the red percentages, it seems that you had a few invalid shares and likely in the beginning. Did the red percentage turned green? Or at least is the percentage converging to 100?
This can happen, but it should be sporadic. Do let us know if it happens often.
Cheers
[/quote]
Both oc1 and oc2 slowed my hashing. OC1 especially, so I am running without either.
5)6gb MSI 1060s 65%-140-400 are ~20, MSI 1080 70%-135-350 is ~40
146 Sols at ~530w
And yes, the red %s are going away after a couple of hours, first going to dark pink then orange then to green. Expecting them all to go green before long. I had never seen reds before with miniZ on 144_5 so it was unnerving to see a sea of red!
Thanks again for the help. Will be tuning up another rig tomorrow!
August 28, 2019, 08:06:32 PM
Hi, miniZ
I see a lot of chatter about OC settings. (OC1 and OC2) Where do I put that setting. In my bat file? Kinda slow here, I'm thinking I'm missing something. Then a bunch of red percentages after a couple of minutes!
6gb MSI 1060s ~20 Sols pwr 75% 100 and 200 clocks
MSI 1080 ~35 Sols 75% 100 and 200 clocks
Running Win10 Driver version 430
Thanks for all the help!
Hi BigHarryArmsi,I see a lot of chatter about OC settings. (OC1 and OC2) Where do I put that setting. In my bat file? Kinda slow here, I'm thinking I'm missing something. Then a bunch of red percentages after a couple of minutes!
6gb MSI 1060s ~20 Sols pwr 75% 100 and 200 clocks
MSI 1080 ~35 Sols 75% 100 and 200 clocks
Running Win10 Driver version 430
Thanks for all the help!
the oc1 may get you a performance improvement, but this depends on your settings. It is good to try it and check which is best for your configuration.
You can add to the command line --oc1, or in your case bat file:
Code:
:loop
.\miniZ.exe --url=ssl://1442d0fab48a6d76dee30643ff01d9b7e83790df46f6b7e69a72e891c028202f.1060s@beam.sunpool.top:3334 --oc1
timeout /t 5
goto loop
Regarding the red percentages, it seems that you had a few invalid shares and likely in the beginning. Did the red percentage turned green? Or at least is the percentage converging to 100?
This can happen, but it should be sporadic. Do let us know if it happens often.
Cheers
August 28, 2019, 07:00:32 PM
Hi, miniZ
I see a lot of chatter about OC settings. (OC1 and OC2) Where do I put that setting. In my bat file? Kinda slow here, I'm thinking I'm missing something. Then a bunch of red percentages after a couple of minutes!
6gb MSI 1060s ~20 Sols pwr 75% 100 and 200 clocks
MSI 1080 ~35 Sols 75% 100 and 200 clocks
Running Win10 Driver version 430
Thanks for all the help!
I see a lot of chatter about OC settings. (OC1 and OC2) Where do I put that setting. In my bat file? Kinda slow here, I'm thinking I'm missing something. Then a bunch of red percentages after a couple of minutes!
6gb MSI 1060s ~20 Sols pwr 75% 100 and 200 clocks
MSI 1080 ~35 Sols 75% 100 and 200 clocks
Running Win10 Driver version 430
Thanks for all the help!
August 28, 2019, 06:15:33 PM
update!
Here we go! Lost one of the files from the folder so after reopening the zip got all 5 files and Rock and Roll!
Thanks again miniZ, now let get some coinage!
Hi BigHarryArmsi,Here we go! Lost one of the files from the folder so after reopening the zip got all 5 files and Rock and Roll!
Thanks again miniZ, now let get some coinage!
great that you managed to find miniZ again
Thanks for the feedback! Happy mining!
Cheers
August 28, 2019, 05:42:03 PM
Thanks for the help miniZ and DanGB
I managed to exclude and d/l new miner
Please forgive my ignorance, this command isn't working for me.
:loop
.\miniZ.exe --url= 1442d0fab48a6d76dee30643ff01d9b7e83790df46f6b7e69a72e891c028202f.1060s@beam.sunpool.top:3334
timeout /t 5
goto loop
'.\miniZ.exe' not recognized as an internal or external,
operable program or batch file
Thanks again in advance
Hi BigHarryArmsi,I managed to exclude and d/l new miner
Please forgive my ignorance, this command isn't working for me.
:loop
.\miniZ.exe --url= 1442d0fab48a6d76dee30643ff01d9b7e83790df46f6b7e69a72e891c028202f.1060s@beam.sunpool.top:3334
timeout /t 5
goto loop
'.\miniZ.exe' not recognized as an internal or external,
operable program or batch file
Thanks again in advance
that error indicates that miniZ.exe cannot be found. Could you check that you have the bat file in the same folder as miniZ.exe file?
If this error disappears, you might get a different error message.
You will need to correct a couple of things in your bat file: there is a space after the --url=, also you are trying to mine to an ssl port so you need to add ssl://.
Like this:
Code:
:loop
.\miniZ.exe --url=ssl://1442d0fab48a6d76dee30643ff01d9b7e83790df46f6b7e69a72e891c028202f.1060s@beam.sunpool.top:3334
timeout /t 5
goto loop
Let us know how it goes.
Cheers
Not certain I understand. I have this command in both the miniz_mine file and the miniZ_gui file and both are in the same folder as the 2 .exe files
Thanks again!
update!
Here we go! Lost one of the files from the folder so after reopening the zip got all 5 files and Rock and Roll!
Thanks again miniZ, now let get some coinage!
August 28, 2019, 05:09:18 PM
Thanks for the help miniZ and DanGB
I managed to exclude and d/l new miner
Please forgive my ignorance, this command isn't working for me.
:loop
.\miniZ.exe --url= 1442d0fab48a6d76dee30643ff01d9b7e83790df46f6b7e69a72e891c028202f.1060s@beam.sunpool.top:3334
timeout /t 5
goto loop
'.\miniZ.exe' not recognized as an internal or external,
operable program or batch file
Thanks again in advance
Hi BigHarryArmsi,I managed to exclude and d/l new miner
Please forgive my ignorance, this command isn't working for me.
:loop
.\miniZ.exe --url= 1442d0fab48a6d76dee30643ff01d9b7e83790df46f6b7e69a72e891c028202f.1060s@beam.sunpool.top:3334
timeout /t 5
goto loop
'.\miniZ.exe' not recognized as an internal or external,
operable program or batch file
Thanks again in advance
that error indicates that miniZ.exe cannot be found. Could you check that you have the bat file in the same folder as miniZ.exe file?
If this error disappears, you might get a different error message.
You will need to correct a couple of things in your bat file: there is a space after the --url=, also you are trying to mine to an ssl port so you need to add ssl://.
Like this:
Code:
:loop
.\miniZ.exe --url=ssl://1442d0fab48a6d76dee30643ff01d9b7e83790df46f6b7e69a72e891c028202f.1060s@beam.sunpool.top:3334
timeout /t 5
goto loop
Let us know how it goes.
Cheers
August 28, 2019, 04:42:35 PM
Thanks for the help miniZ and DanGB
I managed to exclude and d/l new miner
Please forgive my ignorance, this command isn't working for me.
:loop
.\miniZ.exe --url=1442d0fab48a6d76dee30643ff01d9b7e83790df46f6b7e69a72e891c028202f.1060s@beam.sunpool.top:3334 --par=150,5,3 --pers=Beam-PoW
timeout /t 5
goto loop
'.\miniZ.exe' not recognized as an internal or external,
operable program or batch file
Thanks again in advance
I managed to exclude and d/l new miner
Please forgive my ignorance, this command isn't working for me.
:loop
.\miniZ.exe --url=1442d0fab48a6d76dee30643ff01d9b7e83790df46f6b7e69a72e891c028202f.1060s@beam.sunpool.top:3334 --par=150,5,3 --pers=Beam-PoW
timeout /t 5
goto loop
'.\miniZ.exe' not recognized as an internal or external,
operable program or batch file
Thanks again in advance
August 28, 2019, 03:07:43 PM
Good day miniZ
Trying to download v1.5q2_cuda10_win and I keep getting trojan/virus alert from Defender. Is this just defender being difficult? Do I need to exclude v1.5q2 before unzipping? I'm running 144_5 now and changing to Beam. Anyone have a suggestion on a pool? Looking at Leafpool, now
Thanks in advance for the help.
Trying to download v1.5q2_cuda10_win and I keep getting trojan/virus alert from Defender. Is this just defender being difficult? Do I need to exclude v1.5q2 before unzipping? I'm running 144_5 now and changing to Beam. Anyone have a suggestion on a pool? Looking at Leafpool, now
Thanks in advance for the help.
BigHarryArmsi,
Yes, you will have to exclude it from antivirus. Also, give the Sunpool.top pool a try. I have been mining there since the end of January. Great pool, no complaints. You can use a different address for each payout if you like. Just read and understand the first page and record in a safe place the private and public keys. The pool op is very active in the Beam Discord.
Thanks for the help, DanGB
Mayhaps you can lend a hand here, also? When I first d/l this new version of miniZ I got 2 Trojans. Defender repeatedly quarantined then deleted them but one is still here and will not remove?
Trojan:Win32?CoinMiner.C!.** I didn't complete it accurately here as I dunno it may cause trouble but the ? should be a / and the ** should read cl Anyone have a clue how to rid this thing? Apparently I can't update miniZ till this is gone. Win10 Defender says it is running but when I click on "actions" to "remove" nothing happens.
Thanks again for any help and Good day to all of you..
we checked miniZ.exe file and it seems fine. Only miniZ_gui.exe seems to be wrongly marked as infected, however we checked the file and it looks OK.
We made new Windows packages with a new miniZ_gui file. Maybe you can try the new ones and check if Defender complains less.
In any case, always confirm that the files SHA256 are the ones indicated on the website.
To exclude a file from Defender, you need to open the windows security window.
Then go to "Virus and threat protection settings" under the "Virus & threat protection" tab. And in "Exclusions" you can add or remove exclusions.
Let us know if you managed to solve the issue.
Thanks for the feedback!
Cheers
August 28, 2019, 10:39:58 AM
Good day miniZ
Trying to download v1.5q2_cuda10_win and I keep getting trojan/virus alert from Defender. Is this just defender being difficult? Do I need to exclude v1.5q2 before unzipping? I'm running 144_5 now and changing to Beam. Anyone have a suggestion on a pool? Looking at Leafpool, now
Thanks in advance for the help.
Trying to download v1.5q2_cuda10_win and I keep getting trojan/virus alert from Defender. Is this just defender being difficult? Do I need to exclude v1.5q2 before unzipping? I'm running 144_5 now and changing to Beam. Anyone have a suggestion on a pool? Looking at Leafpool, now
Thanks in advance for the help.
BigHarryArmsi,
Yes, you will have to exclude it from antivirus. Also, give the Sunpool.top pool a try. I have been mining there since the end of January. Great pool, no complaints. You can use a different address for each payout if you like. Just read and understand the first page and record in a safe place the private and public keys. The pool op is very active in the Beam Discord.
Thanks for the help, DanGB
Mayhaps you can lend a hand here, also? When I first d/l this new version of miniZ I got 2 Trojans. Defender repeatedly quarantined then deleted them but one is still here and will not remove?
Trojan:Win32?CoinMiner.C!.** I didn't complete it accurately here as I dunno it may cause trouble but the ? should be a / and the ** should read cl Anyone have a clue how to rid this thing? Apparently I can't update miniZ till this is gone. Win10 Defender says it is running but when I click on "actions" to "remove" nothing happens.
Thanks again for any help and Good day to all of you..
August 27, 2019, 06:05:59 PM
Good day miniZ
Trying to download v1.5q2_cuda10_win and I keep getting trojan/virus alert from Defender. Is this just defender being difficult? Do I need to exclude v1.5q2 before unzipping? I'm running 144_5 now and changing to Beam. Anyone have a suggestion on a pool? Looking at Leafpool, now
Thanks in advance for the help.
Trying to download v1.5q2_cuda10_win and I keep getting trojan/virus alert from Defender. Is this just defender being difficult? Do I need to exclude v1.5q2 before unzipping? I'm running 144_5 now and changing to Beam. Anyone have a suggestion on a pool? Looking at Leafpool, now
Thanks in advance for the help.
BigHarryArmsi,
Yes, you will have to exclude it from antivirus. Also, give the Sunpool.top pool a try. I have been mining there since the end of January. Great pool, no complaints. You can use a different address for each payout if you like. Just read and understand the first page and record in a safe place the private and public keys. The pool op is very active in the Beam Discord.
August 27, 2019, 05:09:05 PM
Good day miniZ
Trying to download v1.5q2_cuda10_win and I keep getting trojan/virus alert from Defender. Is this just defender being difficult? Do I need to exclude v1.5q2 before unzipping? I'm running 144_5 now and changing to Beam. Anyone have a suggestion on a pool? Looking at Leafpool, now
Thanks in advance for the help.
Trying to download v1.5q2_cuda10_win and I keep getting trojan/virus alert from Defender. Is this just defender being difficult? Do I need to exclude v1.5q2 before unzipping? I'm running 144_5 now and changing to Beam. Anyone have a suggestion on a pool? Looking at Leafpool, now
Thanks in advance for the help.
August 26, 2019, 06:06:58 PM
In windows 7, the program window looks like this
does anyone know why? In windows 10 there is no problem
does anyone know why? In windows 10 there is no problem
Hi windoom,
if you are not using Windows 10, it is likely that the console output gets all cluttered and unreadable.
Please read on miniZ website the FAQ "I am using Windows and my console output is a mess." which contains some tips on how to manage this issue.
In summary:
The easiest solution is to use the --nocolor, it will help clean up the console. With this you get rid of colors.
If you like to have a more colorful output, you could install another console on Windows.
Hope it helps!
Cheers
August 26, 2019, 06:00:15 PM
Hi miniZ! first, thanks for your miner! Question: What your most performance miner version for mining 144.5 algorithm (bitcoin gold). Thanks! And one more question: What most performance system? windows, ubuntu or linux? Thank you very much!
Hi 91to,thank you for your interest!
Check 144,5 performances at our website. https://miniz.ch/
Performances should be similar for Windows and Linux.
There is only one exception: the 2GB GPUs should perform better on Linux (also maybe 3GB).
This happens because they have less memory, and Windows (especially Win10) always alloc some memory on the card, leaving less memory available for miniZ to run.
Hope this helps.
Cheers
August 26, 2019, 05:57:45 PM
Could you just confirm that mode 3 was selected? Should appear something like this in the beginning of output:
miniZ<150,5,3>[3:1:00:3933]: Selecting GPU#0[0] P104-100
GPU Bus load, reported by GPU-Z, also varies from 7 to 16%, with worst performing GPUs using less bus bandwidth.
thanks for the information.
We will do our best to solve this.
Cheers
August 26, 2019, 01:01:18 PM
In windows 7, the program window looks like this
https://i86.fastpic.ru/big/2019/0826/a9/363e6c8545329e26af728184bfb8c3a9.jpg
does anyone know why? In windows 10 there is no problem
https://i86.fastpic.ru/big/2019/0826/a9/363e6c8545329e26af728184bfb8c3a9.jpg
does anyone know why? In windows 10 there is no problem
August 26, 2019, 07:29:18 AM
Hi miniZ! first, thanks for your miner! Question: What your most performance miner version for mining 144.5 algorithm (bitcoin gold). Thanks! And one more question: What most performance system? windows, ubuntu or linux? Thank you very much!
August 26, 2019, 05:36:58 AM
something is broken with 150,5,3 on P104-100 GPUs. the hashrate is low, 20-30 Sol/s max, expected 40+.
Feel free to add +500 for memory, use the pill and enjoy 40+ GMiner shows 40-42 H/s with mem at stock clock.
something is clearly wrong with 150,5,3 implementation.
on 150,5 algo GMiner and miniZ hashrates were about equal, on 150,5,3 miniZ is far behind.
Jump to: