miniZv2.4d Equihash144,5 125,4 210,9 150,5 192,7 Beam ProgPoW Ethash CFX KLS PYI

[miniZ]

should --mode set the first digit here?

if so then it's not working for P104-100s. the log above is miniZ launched with --mode=4. I don't really know what it means, you did not describe this option, but P104-100s always use the digit "7" there, no matter what mode value I set.

hope it helps

Hi darkneorus,
Thanks. This helps!
Mode can be used to tune the best solver for the card. It looks like there was only one (and not the best) solver for your card (P104).
Which OS are you using? Maybe we can build a beta version for you to try?
Cheers

[darkneorus]

should --mode set the first digit here?

if so then it's not working for P104-100s. the log above is miniZ launched with --mode=4. I don't really know what it means, you did not describe this option, but P104-100s always use the digit "7" there, no matter what mode value I set.

hope it helps

Hi darkneorus,
Thanks. This helps!
Mode can be used to tune the best solver for the card. It looks like there was only one (and not the best) solver for your card (P104).
Which OS are you using? Maybe we can build a beta version for you to try?
Cheers

Windows 10, CUDA 10. would be happy to test it

[miniZ]

Hi 2h4u,
thanks for the feedback.
We will keep working on this.
Do you have any improvemement with the segmentation faults?

Yep looks like they have gone.

Hi 2h4u,
that is nice.

I say it would be great if miniZ does it itself. 5 mins without OC, 5 mins on OC1, next 5 mins on OC2, then check the difference, set best and report to user.
You said that I/s'es stabilize kinda quick, didn't you?

We also thought about it and will see if there is a way.
Cheers

[miniZ]

Windows 10, CUDA 10. would be happy to test it

Hi darkneorus,
You can download the beta file @ https://miniz.ch/download/

Test it with --oc1, it will load mode 3.

Do you see any improvement?

Thanks for your collaboration.
Cheers

[darkneorus]

also, forgot to mention that for some reason GPUs 0, 1 and 2 performance is even lower that the others, and it was like this in previous builds too.
there are no similar issues when miniZ is mining other algos.

the driver version is 416.34.

without any parameters

Code:

[ 0d 0h 3m00s] 203(202.6)Sol/s 1199(1234.3)W
 0>P104-100     ` 100% [45°C/80%]* 9.22 I/s 18.3(18.3)Sol/s 128(141.0)W clk=1885MHz mclk=5005MHz Sol/W=0.13
 1>P104-100     ` 100% [47°C/84%]  7.59 I/s 14.9(14.9)Sol/s 101(106.0)W clk=1847MHz mclk=5005MHz Sol/W=0.14
 2>P104-100     ` 100% [46°C/82%]  9.20 I/s 17.9(17.9)Sol/s 120(134.3)W clk=1898MHz mclk=5005MHz Sol/W=0.13
 3>P104-100     ` 100% [57°C/100%]*14.01 I/s 29.3(29.3)Sol/s 150(157.6)W clk=1847MHz mclk=5005MHz Sol/W=0.19
 4>P106-100     ` 100% [56°C/100%]*10.21 I/s 19.7(19.7)Sol/s 117(107.8)W clk=1847MHz mclk=4006MHz Sol/W=0.18
 5>P104-100     ` 100% [60°C/100%] 13.96 I/s 27.8(27.8)Sol/s 155(164.5)W clk=1847MHz mclk=5005MHz Sol/W=0.17
 6>P106-100     ` 100% [56°C/100%]*10.43 I/s 21.0(21.0)Sol/s  99(105.7)W clk=1860MHz mclk=4006MHz Sol/W=0.20
 7>P104-100     ` 100% [51°C/94%] 14.06 I/s 27.9(27.9)Sol/s 149(154.3)W clk=1860MHz mclk=5005MHz Sol/W=0.18
 8>P104-100     ` 100% [59°C/100%]*14.13 I/s 27.4(27.4)Sol/s 180(163.1)W clk=1860MHz mclk=5005MHz Sol/W=0.17

--mode=3 --oc1

Code:

[ 0d 0h 3m09s] 197(197.3)Sol/s 1213(1193.5)W
 0>P104-100     ` 100% [45°C/80%]  9.22 I/s 18.5(18.5)Sol/s 115(130.8)W clk=1898MHz mclk=5005MHz Sol/W=0.14
 1>P104-100     ` 100% [47°C/84%]  7.75 I/s 14.8(14.8)Sol/s 140(113.9)W clk=1873MHz mclk=5005MHz Sol/W=0.13
 2>P104-100     ` 100% [46°C/82%]  9.22 I/s 18.3(18.3)Sol/s 129(130.9)W clk=1911MHz mclk=5005MHz Sol/W=0.14
 3>P104-100     ` 100% [57°C/100%] 13.76 I/s 27.2(27.2)Sol/s 155(155.9)W clk=1860MHz mclk=5005MHz Sol/W=0.17
 4>P106-100     ` 100% [54°C/98%]  9.03 I/s 18.3(18.3)Sol/s  95( 96.6)W clk=1873MHz mclk=4006MHz Sol/W=0.19
 5>P104-100     ` 100% [61°C/100%] 13.68 I/s 26.7(26.7)Sol/s 144(149.1)W clk=1784MHz mclk=5005MHz Sol/W=0.18
 6>P106-100     ` 100% [54°C/98%]  9.06 I/s 18.3(18.3)Sol/s 109(100.4)W clk=1898MHz mclk=4006MHz Sol/W=0.18
 7>P104-100     ` 100% [51°C/90%] 13.78 I/s 27.5(27.5)Sol/s 170(155.5)W clk=1822MHz mclk=5005MHz Sol/W=0.18
 8>P104-100     ` 100% [60°C/100%]*13.80 I/s 27.5(27.5)Sol/s 156(160.5)W clk=1847MHz mclk=5005MHz Sol/W=0.17

--mode=3 --oc2

Code:

[ 0d 0h 3m09s] 196(195.9)Sol/s 1228(1202.5)W
 0>P104-100     ` 100% [44°C/77%]  9.22 I/s 18.6(18.6)Sol/s 111(121.1)W clk=1873MHz mclk=5005MHz Sol/W=0.15
 1>P104-100     ` 100% [46°C/82%]  7.73 I/s 15.3(15.3)Sol/s 107(114.0)W clk=1885MHz mclk=5005MHz Sol/W=0.13
 2>P104-100     ` 100% [45°C/77%]  9.20 I/s 17.5(17.5)Sol/s 164(134.3)W clk=1885MHz mclk=5005MHz Sol/W=0.13
 3>P104-100     ` 100% [56°C/100%] 13.79 I/s 27.7(27.7)Sol/s 151(152.4)W clk=1822MHz mclk=5005MHz Sol/W=0.18
 4>P106-100     ` 100% [54°C/96%]  9.04 I/s 17.9(17.9)Sol/s 106(101.7)W clk=1873MHz mclk=4006MHz Sol/W=0.18
 5>P104-100     ` 100% [60°C/100%]*13.72 I/s 26.6(26.6)Sol/s 169(168.3)W clk=1860MHz mclk=5005MHz Sol/W=0.16
 6>P106-100     ` 100% [53°C/98%]  9.07 I/s 18.1(18.1)Sol/s  96( 98.7)W clk=1898MHz mclk=4006MHz Sol/W=0.18
 7>P104-100     ` 100% [49°C/88%]*13.77 I/s 26.9(26.9)Sol/s 159(150.5)W clk=1835MHz mclk=5005MHz Sol/W=0.18
 8>P104-100     ` 100% [58°C/100%] 13.81 I/s 27.7(27.7)Sol/s 163(161.5)W clk=1885MHz mclk=5005MHz Sol/W=0.17

--oc2

Code:

[ 0d 0h 3m00s] 204(203.7)Sol/s 1233(1231.7)W
 0>P104-100     ` 100% [46°C/80%]  9.22 I/s 17.3(17.3)Sol/s 150(137.2)W clk=1911MHz mclk=5005MHz Sol/W=0.13
 1>P104-100     ` 100% [48°C/86%]  7.62 I/s 14.9(14.9)Sol/s 112(121.2)W clk=1873MHz mclk=5005MHz Sol/W=0.12
 2>P104-100     ` 100% [47°C/84%]  9.19 I/s 18.0(18.0)Sol/s 143(130.7)W clk=1898MHz mclk=5005MHz Sol/W=0.14
 3>P104-100     ` 100% [58°C/100%] 14.01 I/s 28.2(28.2)Sol/s 150(162.3)W clk=1797MHz mclk=5005MHz Sol/W=0.17
 4>P106-100     ` 100% [56°C/100%] 10.16 I/s 20.1(20.1)Sol/s  93(101.8)W clk=1860MHz mclk=4006MHz Sol/W=0.20
 5>P104-100     ` 100% [61°C/100%] 13.92 I/s 28.1(28.1)Sol/s 168(152.8)W clk=1784MHz mclk=5005MHz Sol/W=0.18
 6>P106-100     ` 100% [56°C/100%] 10.30 I/s 20.1(20.1)Sol/s 107(109.8)W clk=1873MHz mclk=4006MHz Sol/W=0.18
 7>P104-100     ` 100% [53°C/96%]*14.05 I/s 28.3(28.3)Sol/s 154(157.3)W clk=1809MHz mclk=5005MHz Sol/W=0.18
 8>P104-100     ` 100% [60°C/100%] 14.09 I/s 28.4(28.4)Sol/s 156(158.5)W clk=1822MHz mclk=5005MHz Sol/W=0.18

with exactly the same OC settings GMiner performs 25 H/s on P106-100s and 41 H/s on P104-100s.

[miniZ]

also, forgot to mention that for some reason GPUs 0, 1 and 2 performance is even lower that the others, and it was like this in previous builds too.
there are no similar issues when miniZ is mining other algos.

the driver version is 416.34.

Hi darkneorus,
Ok. This is a bit unexpected, but good to know. P106 does not look good as well.

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

We also noticed that you have quite range of performances (and power) on your rig.

We need to think about these GPUs for a while.
Thanks a lot for your help!
Cheers

[darkneorus]

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

yup

Code:

Optimisation:   oc1[0 1 2 3 4 5 6 7 8]
Temp. limit:    [90°C]
miniZ<150,5,3>[3:1:00:5998]: Selecting GPU#6[6] P106-100
miniZ<150,5,3>[3:1:00:3933]: Selecting GPU#7[7] P104-100
miniZ<150,5,3>[3:1:00:3933]: Selecting GPU#2[2] P104-100
miniZ<150,5,3>[3:1:00:3933]: Selecting GPU#8[8] P104-100
miniZ<150,5,3>[3:1:00:3933]: Selecting GPU#3[3] P104-100
miniZ<150,5,3>[3:1:00:5998]: Selecting GPU#4[4] P106-100
miniZ<150,5,3>[3:1:00:3933]: Selecting GPU#0[0] P104-100
miniZ<150,5,3>[3:1:00:3933]: Selecting GPU#1[1] P104-100
miniZ<150,5,3>[3:1:00:3933]: Selecting GPU#5[5] P104-100

GPU Bus load, reported by GPU-Z, also varies from 7 to 16%, with worst performing GPUs using less bus bandwidth.

[MineOrDie]

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+

pill does nothing for P104-100 GPUs. it's useful only for 1080 series.
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.

Use --oc2.

[darkneorus]

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+

pill does nothing for P104-100 GPUs. it's useful only for 1080 series.
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.

Use --oc2.

take your time and read the above messages carefully before posting.

[91to]

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!

[windoom]

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

[miniZ]

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

yup
GPU Bus load, reported by GPU-Z, also varies from 7 to 16%, with worst performing GPUs using less bus bandwidth.

Hi darkneorus,
thanks for the information.
We will do our best to solve this.
Cheers

[miniZ]

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

[miniZ]

In windows 7, the program window looks like this

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

[BigHarryArmsi]

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.

[DanGB]

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.

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.

[BigHarryArmsi]

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.

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..

[miniZ]

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.

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..

Hi BigHarryArmsi,
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

[BigHarryArmsi]

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

[miniZ]

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,
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