Can I mine Beam on gtx 1063 with Win 10?
Yes, there is no problems while mining Beam on GTX1060 with 3 Gb memory. Equihash 192 needs a little bit more memory and also perfectly working on Windows 7, 8 and 10LTSB versions. 
Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 61. (Read 60004 times)
April 27, 2019, 03:31:46 AM
April 27, 2019, 03:17:05 AM
Can I mine Beam on gtx 1063 with Win 10?
April 27, 2019, 02:47:11 AM
Good job with the 150,5 algo.
April 27, 2019, 02:36:55 AM
Hi, overnight, I had the same problem on both rigs
OS win10
OS win10
April 27, 2019, 01:59:09 AM
using miniZ on mmpOS and at some point overnight, the pool stopped accepting shares.
miner kept going and stats were showing fine in the OS but at pool, miner has stopped totally.
what might be causing this?
i have reverted to using the miner via command line, bypassing the OS UI but i don't think that is the issue as the OS still showed sol/s
mining 150_5
miner kept going and stats were showing fine in the OS but at pool, miner has stopped totally.
what might be causing this?
i have reverted to using the miner via command line, bypassing the OS UI but i don't think that is the issue as the OS still showed sol/s
mining 150_5
April 27, 2019, 01:42:05 AM
Dear miniZ, i've got some bug reports for you:
1. HiveOS custom package doesn't save logs at all. Directory /var/log/miner/miniZ exists, but is empty all the time.
2. Load average is very high, like 6-7 on G3930. 11 Pascal GPUs. Would you like to abuse NVML in less frequent manner?
p.s. It would be epic to add some auto-tune feature, ok? No any evil --oc1 --oc2 --f11 --ohmygod347, but --autotune=speed|efficiency
Hi 2h4u.1. HiveOS custom package doesn't save logs at all. Directory /var/log/miner/miniZ exists, but is empty all the time.
2. Load average is very high, like 6-7 on G3930. 11 Pascal GPUs. Would you like to abuse NVML in less frequent manner?
p.s. It would be epic to add some auto-tune feature, ok? No any evil --oc1 --oc2 --f11 --ohmygod347, but --autotune=speed|efficiency
thank you for the bug reports.
1. We will look into this. Meanwhile you can run miniZ with --log.
2. Load should not be high at all. Does it happen again if you restart miniZ? Could you tell what coin are you mining? Maybe also which pool you are using.
If you try again, could you paste here a bit of the miniZ log?
Regarding the autotune, we will think about it
Cheers
1. Ok done it. As far as I know, Hive guys already added miniZ to their miners repo and I was told they'll make it public next week.
2. It happens every run. HiveOS, 418.43 drivers, beam 150,5 on the nicehash. The rest of miners I use (gminer/t-rex/ethminer) giving me LA 2-3, tops. Log and LA as follows:
Code:
[ 0d 1h22m45s] S:742/0 150(150.4)Sol/s 1030(1040.8)W [beam.eu.nicehash.com]- 105ms (97.7%) (0.0%) (0.0%) (0.0%) (0.0%) (0.0%) (2.3%)
0>GTX 1060 3GB `S:133/0 [64°C/63%] 6.71 I/s 13.4(13.3)Sol/s 78( 82.7)W clk=1632MHz mclk=4353MHz Sol/W=0.16
1>GTX 1060 3GB `S: 70/0 [64°C/60%] 7.38 I/s 14.9(14.6)Sol/s 102(106.5)W clk=1835MHz mclk=4544MHz Sol/W=0.14
2>GTX 1060 3GB `S: 69/0 [65°C/65%] 7.33 I/s 14.5(14.5)Sol/s 96(104.8)W clk=1885MHz mclk=4437MHz Sol/W=0.14
3>GTX 1060 3GB `S: 60/0 [64°C/63%] 6.44 I/s 12.9(12.8)Sol/s 82( 79.8)W clk=1645MHz mclk=4248MHz Sol/W=0.16
4>GTX 1060 3GB `S: 72/0 [64°C/63%] 7.39 I/s 13.9(14.5)Sol/s 118(113.4)W clk=1847MHz mclk=4556MHz Sol/W=0.13
5>GTX 1060 3GB `S: 57/0 [64°C/59%] 6.93 I/s 13.8(13.8)Sol/s 96(100.3)W clk=1797MHz mclk=4117MHz Sol/W=0.14
6>GTX 1060 3GB `S: 63/0 [65°C/67%] 6.46 I/s 12.6(12.8)Sol/s 86( 84.3)W clk=1683MHz mclk=4094MHz Sol/W=0.15
7>GTX 1060 3GB `S: 55/0 [65°C/64%] 6.86 I/s 13.6(13.7)Sol/s 96( 95.5)W clk=1822MHz mclk=4233MHz Sol/W=0.14
8>GTX 1060 3GB `S: 59/0 [65°C/65%] 6.61 I/s 13.7(13.1)Sol/s 91( 89.6)W clk=1733MHz mclk=4140MHz Sol/W=0.15
9>GTX 1060 3GB `S: 61/0 [65°C/68%] 7.03 I/s 13.6(13.9)Sol/s 101(100.1)W clk=1873MHz mclk=4314MHz Sol/W=0.14
10>GTX 1060 3GB `S: 66/0 [65°C/61%] 6.77 I/s 13.1(13.4)Sol/s 84( 83.8)W clk=1721MHz mclk=4414MHz Sol/W=0.16
[ 0d 1h22m55s] S:743/0 150(150.4)Sol/s 1033(1040.7)W [beam.eu.nicehash.com]- 100ms (97.7%) (0.0%) (0.0%) (0.0%) (0.0%) (0.0%) (2.3%)
0>GTX 1060 3GB `S:133/0 [64°C/63%] 6.71 I/s 13.2(13.3)Sol/s 88( 82.8)W clk=1632MHz mclk=4353MHz Sol/W=0.16
1>GTX 1060 3GB `S: 70/0 [64°C/60%] 7.38 I/s 14.6(14.6)Sol/s 104(106.5)W clk=1847MHz mclk=4544MHz Sol/W=0.14
2>GTX 1060 3GB `S: 69/0 [65°C/65%] 7.33 I/s 14.6(14.5)Sol/s 103(104.8)W clk=1847MHz mclk=4437MHz Sol/W=0.14
3>GTX 1060 3GB `S: 60/0 [65°C/63%] 6.44 I/s 13.0(12.8)Sol/s 82( 79.8)W clk=1645MHz mclk=4248MHz Sol/W=0.16
4>GTX 1060 3GB `S: 72/0 [65°C/63%] 7.39 I/s 14.2(14.5)Sol/s 115(113.4)W clk=1822MHz mclk=4556MHz Sol/W=0.13
5>GTX 1060 3GB `S: 57/0 [65°C/59%] 6.93 I/s 13.6(13.8)Sol/s 92(100.3)W clk=1809MHz mclk=4117MHz Sol/W=0.14
6>GTX 1060 3GB `S: 63/0 [64°C/67%] 6.46 I/s 12.6(12.8)Sol/s 86( 84.3)W clk=1683MHz mclk=4094MHz Sol/W=0.15
7>GTX 1060 3GB `S: 56/0 [65°C/64%]* 6.86 I/s 13.6(13.7)Sol/s 98( 95.5)W clk=1822MHz mclk=4233MHz Sol/W=0.14
8>GTX 1060 3GB `S: 59/0 [65°C/65%] 6.61 I/s 13.6(13.1)Sol/s 86( 89.6)W clk=1733MHz mclk=4140MHz Sol/W=0.15
9>GTX 1060 3GB `S: 61/0 [65°C/68%] 7.03 I/s 13.5(13.9)Sol/s 94(100.1)W clk=1860MHz mclk=4314MHz Sol/W=0.14
10>GTX 1060 3GB `S: 66/0 [65°C/61%] 6.77 I/s 13.2(13.4)Sol/s 83( 83.7)W clk=1708MHz mclk=4414MHz Sol/W=0.16
Code:
user@c3:/hive-config# uptime
13:36:42 up 3 days, 18:57, 1 user, load average: 8.12, 8.49, 8.52
At the top of the top (pun intended) are miniZ and kworker.
April 26, 2019, 09:19:15 PM
Does this optimization work for the Beam algo? It seems to, but the FAQ say that it only works with 144.5 algo. Also, would there be any benefit to running this optimization along with an --oc optimization?
April 26, 2019, 07:59:16 PM
Could you please add Beam mining pool Sunpool to your FAQ list of pools?
https://sunpool.top/
beam.sunpool.top:3333
https://sunpool.top/
beam.sunpool.top:3333
April 26, 2019, 07:04:53 PM
The console says no rejected at all, but @NiceHash its ~15% in this tiny sample. In bigger samples you will see spikes up to 30-40% like I showed above. Hope this helps.
Driver 430.39, latest Win 10 + all patches. But same rejects also on 419.67 with RTX 2070 cards.
Hi joseph32,Driver 430.39, latest Win 10 + all patches. But same rejects also on 419.67 with RTX 2070 cards.
When you have a stale share you just get a yellow star on the miner console, the efficiency only accounts for the number of accepted and invalid shares. To see the other shares you have to look at the telemetry, it would be the middle value on the shares column.
As we said for cervajz, we can see that nicehash, after sending a new job, does not accept submissions from previous jobs. Some pools still accept it, others like nicehash do not. We've tested and managed to see that when the miner receives a new job, just before submiting a solution from a previous work, this results in a rejected share from that submission.
Can you let us know what reason for rejection does nicehash report. You can check your graphic. It can say rejected (target), rejected (stale), rejected (duplicate)...
Cheers
Highest reject reason is target, a few % is stale which is mostly splitted between stale and duplicate. Here is a screen. (Around 18:30 the miner wasnt farming, so thats why its 0).
Hi joseph32,
thank you for the log.
We believe we managed to reproduce your problem.
Try running miniZ without --pers auto, for mining BEAM. Or use --pers Beam-PoW.
Actually, when mining Beam --pers auto should not work on any pool, we are surprised you got accepted so many shares.
Let us know if this helped.
Cheers
Much better now, thanks for the tip! Also did a quick note to AwesomeMiner to change that auto
April 26, 2019, 06:45:06 PM
Sorry if this has been asked before, when is a win10 AMD friendly version been released?
Hi clousian,At the moment we are not considering to add support for AMD.
We suggest that you user another miner like lol miner that has a good AMD support.
Cheers
Okay cheers dude
April 26, 2019, 06:36:40 PM
Hi,
I get an "out of memory" error when I try to mine BEAM on Hive OS with my 1060 3GB cards. You said earlier that it's possible to mine on Linux, so am I doing something wrong?
I get an "out of memory" error when I try to mine BEAM on Hive OS with my 1060 3GB cards. You said earlier that it's possible to mine on Linux, so am I doing something wrong?
April 26, 2019, 05:07:07 PM
Hi, use last version miniz... w10, driver 430+,cpu g3930, 4GB RAM, 5x1080ti+1x1080, mine beam, speed is far better than gminer :-) good work
cpu load is 100%
Hi stzcze, cpu load is 100%
thanks for the encouragement.
CPU load shouldn't be high at all, we are looking into the problem at this moment.
Cheers
April 26, 2019, 04:10:57 PM
not stable for me, back to version v1.2m
Hi topteam,Code:
kernel: [ 678.861888] show_signal_msg: 18 callbacks suppressed
kernel: [ 678.861891] miniZ[2386]: segfault at c0 ip 0000560d8618c982 sp 00007fcc10ff2bd0 error 4 in miniZ[560d86098000+1fea000]
1775 Segmentation fault (core dumped) ~/miniZ --url [email protected]:20595 --pers BgoldPoW --par=144,5 --nocolor --telemetry 0 --gpu-line --extra --templimit 70C --tempunits C --latency --show-solratio --show-pers --shares-detail --oc2
sorry for this.
Could you post here a bit of the log just before the crash?
Thanks.
Cheers
PS crash on fee.server
thanks for the log. We just spotted the problem and it is fixed for the next release.
Cheers
April 26, 2019, 04:08:34 PM
Dear miniZ, i've got some bug reports for you:
1. HiveOS custom package doesn't save logs at all. Directory /var/log/miner/miniZ exists, but is empty all the time.
2. Load average is very high, like 6-7 on G3930. 11 Pascal GPUs. Would you like to abuse NVML in less frequent manner?
p.s. It would be epic to add some auto-tune feature, ok? No any evil --oc1 --oc2 --f11 --ohmygod347, but --autotune=speed|efficiency
Hi 2h4u.1. HiveOS custom package doesn't save logs at all. Directory /var/log/miner/miniZ exists, but is empty all the time.
2. Load average is very high, like 6-7 on G3930. 11 Pascal GPUs. Would you like to abuse NVML in less frequent manner?
p.s. It would be epic to add some auto-tune feature, ok? No any evil --oc1 --oc2 --f11 --ohmygod347, but --autotune=speed|efficiency
thank you for the bug reports.
1. We will look into this. Meanwhile you can run miniZ with --log.
2. Load should not be high at all. Does it happen again if you restart miniZ? Could you tell what coin are you mining? Maybe also which pool you are using.
If you try again, could you paste here a bit of the miniZ log?
Regarding the autotune, we will think about it
Cheers
April 26, 2019, 04:06:37 PM
The console says no rejected at all, but @NiceHash its ~15% in this tiny sample. In bigger samples you will see spikes up to 30-40% like I showed above. Hope this helps.
Driver 430.39, latest Win 10 + all patches. But same rejects also on 419.67 with RTX 2070 cards.
Hi joseph32,Driver 430.39, latest Win 10 + all patches. But same rejects also on 419.67 with RTX 2070 cards.
When you have a stale share you just get a yellow star on the miner console, the efficiency only accounts for the number of accepted and invalid shares. To see the other shares you have to look at the telemetry, it would be the middle value on the shares column.
As we said for cervajz, we can see that nicehash, after sending a new job, does not accept submissions from previous jobs. Some pools still accept it, others like nicehash do not. We've tested and managed to see that when the miner receives a new job, just before submiting a solution from a previous work, this results in a rejected share from that submission.
Can you let us know what reason for rejection does nicehash report. You can check your graphic. It can say rejected (target), rejected (stale), rejected (duplicate)...
Cheers
Highest reject reason is target, a few % is stale which is mostly splitted between stale and duplicate. Here is a screen. (Around 18:30 the miner wasnt farming, so thats why its 0).
Hi joseph32,
thank you for the log.
We believe we managed to reproduce your problem.
Try running miniZ without --pers auto, for mining BEAM. Or use --pers Beam-PoW.
Actually, when mining Beam --pers auto should not work on any pool, we are surprised you got accepted so many shares.
Let us know if this helped.
Cheers
April 26, 2019, 03:21:02 PM
Hi, use last version miniz... w10, driver 430+,cpu g3930, 4GB RAM, 5x1080ti+1x1080, mine beam, speed is far better than gminer :-) good work
cpu load is 100%
cpu load is 100%
April 26, 2019, 02:32:11 PM
not stable for me, back to version v1.2m
Hi topteam,Code:
kernel: [ 678.861888] show_signal_msg: 18 callbacks suppressed
kernel: [ 678.861891] miniZ[2386]: segfault at c0 ip 0000560d8618c982 sp 00007fcc10ff2bd0 error 4 in miniZ[560d86098000+1fea000]
1775 Segmentation fault (core dumped) ~/miniZ --url [email protected]:20595 --pers BgoldPoW --par=144,5 --nocolor --telemetry 0 --gpu-line --extra --templimit 70C --tempunits C --latency --show-solratio --show-pers --shares-detail --oc2
sorry for this.
Could you post here a bit of the log just before the crash?
Thanks.
Cheers
Code:
[ 0d 0h 5m19s] S: 31/0 744(732.4)Sol/s 1641(1589.8)W [fee.server]- 105ms (95.9%) (4.1%)
0>GTX 1070 S: 0/0 [60°C/65%] 28.91 I/s 58.4(58.2)Sol/s 141(139.8)W clk=1746MHz mclk=4452MHz Sol/W=0.42 2.00 Sol/I
1>GTX 1070 S: 0/0 [55°C/50%] 29.40 I/s 59.0(59.1)Sol/s 137(137.5)W clk=1784MHz mclk=4452MHz Sol/W=0.43 2.00 Sol/I
2>GTX 1070 S: 0/0 [56°C/50%] 29.60 I/s 58.2(58.3)Sol/s 137(136.7)W clk=1822MHz mclk=4452MHz Sol/W=0.43 1.97 Sol/I
3>GTX 1070 S: 0/0 [53°C/50%] 30.01 I/s 60.7(60.6)Sol/s 136(135.0)W clk=1835MHz mclk=4452MHz Sol/W=0.45 2.00 Sol/I
4>GTX 1070 S: 0/0 [54°C/50%] 30.07 I/s 59.4(59.4)Sol/s 135(136.4)W clk=1835MHz mclk=4452MHz Sol/W=0.44 1.98 Sol/I
5>GTX 1070 Ti S: 0/0 [48°C/50%] 34.00 I/s 66.9(67.0)Sol/s 135(129.1)W clk=1784MHz mclk=4452MHz Sol/W=0.52 1.96 Sol/I
6>GTX 1070 Ti S: 0/0 [48°C/50%] 33.95 I/s 67.2(67.3)Sol/s 138(128.3)W clk=1771MHz mclk=4452MHz Sol/W=0.52 1.99 Sol/I
7>GTX 1070 Ti S: 0/0 [56°C/50%] 33.58 I/s 67.5(67.3)Sol/s 140(136.1)W clk=1759MHz mclk=4452MHz Sol/W=0.49 2.00 Sol/I
8>GTX 1070 Ti S: 0/0 [54°C/50%] 33.74 I/s 66.1(66.1)Sol/s 138(135.4)W clk=1759MHz mclk=4452MHz Sol/W=0.49 1.97 Sol/I
9>GTX 1070 Ti S: 0/0 [55°C/50%] 34.02 I/s 68.7(68.7)Sol/s 137(118.5)W clk=1784MHz mclk=4452MHz Sol/W=0.58 2.00 Sol/I
10>GTX 1070 Ti S: 0/0 [60°C/65%] 32.93 I/s 65.9(66.0)Sol/s 134(134.6)W clk=1708MHz mclk=4452MHz Sol/W=0.49 2.00 Sol/I
11>GTX 1070 Ti S: 0/0 [53°C/50%] 33.41 I/s 66.5(66.4)Sol/s 132(122.3)W clk=1759MHz mclk=4452MHz Sol/W=0.54 1.97 Sol/I
[ 0d 0h 5m29s] S: 31/0 747(734.8)Sol/s 1615(1589.9)W [fee.server]- 105ms (95.9%) (4.1%)
0>GTX 1070 S: 0/0 [60°C/65%] 28.91 I/s 58.3(58.1)Sol/s 116(136.9)W clk=1771MHz mclk=4452MHz Sol/W=0.42 2.00 Sol/I
1>GTX 1070 S: 0/0 [55°C/50%] 29.41 I/s 59.1(59.1)Sol/s 138(137.5)W clk=1784MHz mclk=4452MHz Sol/W=0.43 2.00 Sol/I
2>GTX 1070 S: 0/0 [56°C/50%] 29.61 I/s 58.1(58.2)Sol/s 138(136.9)W clk=1809MHz mclk=4452MHz Sol/W=0.43 1.97 Sol/I
3>GTX 1070 S: 0/0 [53°C/50%] 30.02 I/s 60.6(60.5)Sol/s 137(135.2)W clk=1822MHz mclk=4452MHz Sol/W=0.45 1.99 Sol/I
4>GTX 1070 S: 0/0 [54°C/50%] 30.06 I/s 59.6(59.5)Sol/s 136(136.4)W clk=1809MHz mclk=4452MHz Sol/W=0.44 1.99 Sol/I
5>GTX 1070 Ti S: 0/0 [48°C/50%] 34.00 I/s 66.6(66.7)Sol/s 133(129.2)W clk=1784MHz mclk=4452MHz Sol/W=0.52 1.97 Sol/I
6>GTX 1070 Ti S: 0/0 [48°C/50%] 33.95 I/s 67.5(67.5)Sol/s 139(129.0)W clk=1771MHz mclk=4452MHz Sol/W=0.52 1.99 Sol/I
7>GTX 1070 Ti S: 0/0 [56°C/50%] 33.58 I/s 67.6(67.4)Sol/s 140(136.3)W clk=1759MHz mclk=4452MHz Sol/W=0.49 2.00 Sol/I
8>GTX 1070 Ti S: 0/0 [54°C/50%] 33.73 I/s 66.8(66.6)Sol/s 133(135.0)W clk=1771MHz mclk=4452MHz Sol/W=0.49 1.98 Sol/I
9>GTX 1070 Ti S: 0/0 [55°C/50%] 34.03 I/s 68.9(68.9)Sol/s 138(119.8)W clk=1784MHz mclk=4452MHz Sol/W=0.57 2.00 Sol/I
10>GTX 1070 Ti S: 0/0 [60°C/65%] 32.93 I/s 66.2(66.2)Sol/s 131(134.1)W clk=1708MHz mclk=4452MHz Sol/W=0.49 2.00 Sol/I
11>GTX 1070 Ti S: 0/0 [54°C/50%] 33.42 I/s 66.3(66.3)Sol/s 137(123.5)W clk=1759MHz mclk=4452MHz Sol/W=0.54 1.97 Sol/I
[ 0d 0h 5m39s] S: 31/0 748(736.0)Sol/s 1629(1593.0)W [fee.server]- 105ms (95.9%) (4.1%)
0>GTX 1070 S: 0/0 [60°C/65%] 28.91 I/s 58.2(58.1)Sol/s 129(137.1)W clk=1746MHz mclk=4452MHz Sol/W=0.42 2.00 Sol/I
1>GTX 1070 S: 0/0 [55°C/50%] 29.41 I/s 58.8(59.0)Sol/s 139(137.7)W clk=1784MHz mclk=4452MHz Sol/W=0.43 2.00 Sol/I
kernel: [ 678.861888] show_signal_msg: 18 callbacks suppressed
kernel: [ 678.861891] miniZ[2386]: segfault at c0 ip 0000560d8618c982 sp 00007fcc10ff2bd0 error 4 in miniZ[560d86098000+1fea000]
1775 Segmentation fault (core dumped) ~/miniZ [email protected]:20595 --pers BgoldPoW --par=144,5 --nocolor --telemetry 0 --gpu-line --extra --templimit 70C --tempunits C --latency --show-solratio --show-pers --shares-detail --oc2
April 26, 2019, 02:15:48 PM
Dear miniZ, i've got some bug reports for you:
1. HiveOS custom package doesn't save logs at all. Directory /var/log/miner/miniZ exists, but is empty all the time.
2. Load average is very high, like 6-7 on G3930. 11 Pascal GPUs. Would you like to abuse NVML in less frequent manner?
p.s. It would be epic to add some auto-tune feature, ok? No any evil --oc1 --oc2 --f11 --ohmygod347, but --autotune=speed|efficiency
1. HiveOS custom package doesn't save logs at all. Directory /var/log/miner/miniZ exists, but is empty all the time.
2. Load average is very high, like 6-7 on G3930. 11 Pascal GPUs. Would you like to abuse NVML in less frequent manner?
p.s. It would be epic to add some auto-tune feature, ok? No any evil --oc1 --oc2 --f11 --ohmygod347, but --autotune=speed|efficiency
April 26, 2019, 02:12:50 PM
The console says no rejected at all, but @NiceHash its ~15% in this tiny sample. In bigger samples you will see spikes up to 30-40% like I showed above. Hope this helps.
Driver 430.39, latest Win 10 + all patches. But same rejects also on 419.67 with RTX 2070 cards.
Hi joseph32,Driver 430.39, latest Win 10 + all patches. But same rejects also on 419.67 with RTX 2070 cards.
When you have a stale share you just get a yellow star on the miner console, the efficiency only accounts for the number of accepted and invalid shares. To see the other shares you have to look at the telemetry, it would be the middle value on the shares column.
As we said for cervajz, we can see that nicehash, after sending a new job, does not accept submissions from previous jobs. Some pools still accept it, others like nicehash do not. We've tested and managed to see that when the miner receives a new job, just before submiting a solution from a previous work, this results in a rejected share from that submission.
Can you let us know what reason for rejection does nicehash report. You can check your graphic. It can say rejected (target), rejected (stale), rejected (duplicate)...
Cheers
Highest reject reason is target, a few % is stale which is mostly splitted between stale and duplicate. Here is a screen. (Around 18:30 the miner wasnt farming, so thats why its 0).
April 26, 2019, 02:04:53 PM
not stable for me, back to version v1.2m
Hi topteam,Code:
kernel: [ 678.861888] show_signal_msg: 18 callbacks suppressed
kernel: [ 678.861891] miniZ[2386]: segfault at c0 ip 0000560d8618c982 sp 00007fcc10ff2bd0 error 4 in miniZ[560d86098000+1fea000]
1775 Segmentation fault (core dumped) ~/miniZ --url [email protected]:20595 --pers BgoldPoW --par=144,5 --nocolor --telemetry 0 --gpu-line --extra --templimit 70C --tempunits C --latency --show-solratio --show-pers --shares-detail --oc2
sorry for this.
Could you post here a bit of the log just before the crash?
Thanks.
Cheers
Jump to: