Hi everyone,
Thank you for your feedback and support!
You can find new miniZ v1.5p here.
miniZ has released a new version v1.5p that supports 150,5,3 – BeamHashII.
For more information on Beam mining check How to mine Beam? on our FAQ page.
* Added support for 150,5,3 (BeamHashII).
* Added autoswitch for Beam fork at block 321321.
* Fixed ZEL mining on 3GB GPU, on Windows 10. (Testing)
* Improved support for 210,9 (Aion).
* Added --stat-int option to customize statistics interval.
* Added --nonvml option to disable GPU health stats.
* Improved cpu load.
* Minor bug fixes.
Equihash 150,5,3 (BeamHashII):
* GTX 1050 Ti 4GB ~11.9 Sol/s
* GTX 1060 3GB ~20.1 Sol/s
* GTX 1070 Ti 8GB ~40.1 Sol/s
* GTX 1080 8GB ~41.0 Sol/s
* GTX 1080 Ti 11GB ~53.8 Sol/s
* RTX 2070 8GB ~46.9 Sol/s
Download here.
For additional information check our Usage or FAQ pages.
Hive OS support here.
Happy mining!
Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 45. (Read 59781 times)
August 13, 2019, 07:22:39 PM
August 13, 2019, 07:03:36 PM
Does the program support Beam Hard Fork 15 aug?
Hi Galat,Yes!
We have just released miniZ v1.5p that supports Beam new algo (150,5,3).
Cheers
August 13, 2019, 07:02:51 PM
Good day.
Why, after starting the miner, the use of is not available PhysX.
Hi Ziv1,Why, after starting the miner, the use of is not available PhysX.
the miner uses all GPU resources. Are you trying to run some other software simultaneously?
Cheers
August 13, 2019, 07:02:28 PM
Code:
Error: recieve has been 2284
[INFO ]stratum.icemining.ca Disconnecting
[INFO ]stratum.icemining.ca Stopping miner
[INFO ]stratum.icemining.ca Disconnecting
[INFO ]stratum.icemining.ca Stopping miner
got this error couple times. Sometimes the number is different
we fixed this error in the new release, miniZ v1.5p.
Thanks!
Cheers
August 13, 2019, 04:48:12 AM
Does the program support Beam Hard Fork 15 aug?
August 13, 2019, 03:31:36 AM
Good day.
Why, after starting the miner, the use of is not available PhysX.
Why, after starting the miner, the use of is not available PhysX.
August 12, 2019, 09:31:40 AM
Code:
Error: recieve has been 2284
[INFO ]stratum.icemining.ca Disconnecting
[INFO ]stratum.icemining.ca Stopping miner
[INFO ]stratum.icemining.ca Disconnecting
[INFO ]stratum.icemining.ca Stopping miner
got this error couple times. Sometimes the number is different
August 11, 2019, 02:29:08 PM
for me miniZ have less CPU utilisation on 12x1070 CPU3930 4Gb ubuntu 16 cuda 9.2
thank you for letting us know.
Which nvidia driver version are you using?
Cheers
August 11, 2019, 02:28:09 PM
Your miner gets gradually slow on systems with many GPUs. It starts off with higher hashrate for the first few minutes and then slowly drops by up to 30% in speed. This is a sign of too much driver comms, keeping the CPU swamped with irq requests (Gminer had the same problem a few months ago but they fixed it).
You should find a way to drop CPU utilization and driver usage. You should also add an option to disable nvml polling of temperature, fans, power etc.
13x gtx1070, i3-7100, 8 GB ram, Ubuntu x64, nvidia 415.27, cuda 10.0
Gminer 150,5: 280-290 H/s, steady. CPU utilization is 40-50%. I can communicate with the GPUs while it's mining as usual.
miniZ 150,5: starts at ~250 H/s for a about 1 minute, then gradually drops to ~180 H/s within ~2 minutes. CPU is kept at 100% at all times and any GPU command issued hangs (e.g. nvidia-smi hangs entirely). The nvidia driver is totally hogged.
I tried lowering --intensity and the CPU utilization drops, but the hashrate drops significantly too, even if I use --intensity 99. Max I can get is about ~195 H/s.
I also tried --oc1 and --oc2. Also tried --telemetry 0 (doesn't disable nvml polling). Nothing made any difference (even though I have them overclocked and at lower power limits).
I'm willing to test a beta if you're willing to work on this. PM me. I manage a small farm.
EDIT: Retested Gminer on 150,5. Gets 280-290 H/s steady, with 40-50% CPU utilization.
Hi cryptoyes,You should find a way to drop CPU utilization and driver usage. You should also add an option to disable nvml polling of temperature, fans, power etc.
13x gtx1070, i3-7100, 8 GB ram, Ubuntu x64, nvidia 415.27, cuda 10.0
Gminer 150,5: 280-290 H/s, steady. CPU utilization is 40-50%. I can communicate with the GPUs while it's mining as usual.
miniZ 150,5: starts at ~250 H/s for a about 1 minute, then gradually drops to ~180 H/s within ~2 minutes. CPU is kept at 100% at all times and any GPU command issued hangs (e.g. nvidia-smi hangs entirely). The nvidia driver is totally hogged.
I tried lowering --intensity and the CPU utilization drops, but the hashrate drops significantly too, even if I use --intensity 99. Max I can get is about ~195 H/s.
I also tried --oc1 and --oc2. Also tried --telemetry 0 (doesn't disable nvml polling). Nothing made any difference (even though I have them overclocked and at lower power limits).
I'm willing to test a beta if you're willing to work on this. PM me. I manage a small farm.
EDIT: Retested Gminer on 150,5. Gets 280-290 H/s steady, with 40-50% CPU utilization.
thank you so much for your availability.
We have been unable to reproduce this problem. However, we made a few changes when introducing the new Beam algo, for the next release.
Maybe you can try it and let us know if you see a difference in cpu usage. It should be out within ~24h.
We also introduce an option to disable nvml.
Cheers
August 11, 2019, 02:27:00 PM
why does miniZ sometimes popup a dialog box when it crashes? this results in the program stopping until I press a button and bat file loop restarts miniz and continues mining. this dialog box presents a productivity issue as I may not notice this box popup for some amount of time while the miner is doing 0 work. how can I disable this dialog box from appearing?
also: when there is a problem with a GPU it spams errors on all the GPUs so I cant identify which GPU actually caused the crash.
Hi fistsofgod,also: when there is a problem with a GPU it spams errors on all the GPUs so I cant identify which GPU actually caused the crash.
we did a fix for the next release that may disable the popup box in your case.
You can also disable this error box by changing windows settings. Check here and let us know if it helps.
Regarding the error spamming, you need to look which GPU got the error first.
Cheers
August 11, 2019, 07:24:58 AM
Your miner gets gradually slow on systems with many GPUs. It starts off with higher hashrate for the first few minutes and then slowly drops by up to 30% in speed. This is a sign of too much driver comms, keeping the CPU swamped with irq requests (Gminer had the same problem a few months ago but they fixed it).
You should find a way to drop CPU utilization and driver usage. You should also add an option to disable nvml polling of temperature, fans, power etc.
13x gtx1070, i3-7100, 8 GB ram, Ubuntu x64, nvidia 415.27, cuda 10.0
Gminer 150,5: 280-290 H/s, steady. CPU utilization is 40-50%. I can communicate with the GPUs while it's mining as usual.
miniZ 150,5: starts at ~250 H/s for a about 1 minute, then gradually drops to ~180 H/s within ~2 minutes. CPU is kept at 100% at all times and any GPU command issued hangs (e.g. nvidia-smi hangs entirely). The nvidia driver is totally hogged.
I tried lowering --intensity and the CPU utilization drops, but the hashrate drops significantly too, even if I use --intensity 99. Max I can get is about ~195 H/s.
I also tried --oc1 and --oc2. Also tried --telemetry 0 (doesn't disable nvml polling). Nothing made any difference (even though I have them overclocked and at lower power limits).
I'm willing to test a beta if you're willing to work on this. PM me. I manage a small farm.
EDIT: Retested Gminer on 150,5. Gets 280-290 H/s steady, with 40-50% CPU utilization.
for me miniZ have less CPU utilisation on 12x1070 CPU3930 4Gb ubuntu 16 cuda 9.2 You should find a way to drop CPU utilization and driver usage. You should also add an option to disable nvml polling of temperature, fans, power etc.
13x gtx1070, i3-7100, 8 GB ram, Ubuntu x64, nvidia 415.27, cuda 10.0
Gminer 150,5: 280-290 H/s, steady. CPU utilization is 40-50%. I can communicate with the GPUs while it's mining as usual.
miniZ 150,5: starts at ~250 H/s for a about 1 minute, then gradually drops to ~180 H/s within ~2 minutes. CPU is kept at 100% at all times and any GPU command issued hangs (e.g. nvidia-smi hangs entirely). The nvidia driver is totally hogged.
I tried lowering --intensity and the CPU utilization drops, but the hashrate drops significantly too, even if I use --intensity 99. Max I can get is about ~195 H/s.
I also tried --oc1 and --oc2. Also tried --telemetry 0 (doesn't disable nvml polling). Nothing made any difference (even though I have them overclocked and at lower power limits).
I'm willing to test a beta if you're willing to work on this. PM me. I manage a small farm.
EDIT: Retested Gminer on 150,5. Gets 280-290 H/s steady, with 40-50% CPU utilization.
August 09, 2019, 06:04:48 AM
Your miner gets gradually slow on systems with many GPUs. It starts off with higher hashrate for the first few minutes and then slowly drops by up to 30% in speed. This is a sign of too much driver comms, keeping the CPU swamped with irq requests (Gminer had the same problem a few months ago but they fixed it).
You should find a way to drop CPU utilization and driver usage. You should also add an option to disable nvml polling of temperature, fans, power etc.
13x gtx1070, i3-7100, 8 GB ram, Ubuntu x64, nvidia 415.27, cuda 10.0
Gminer 150,5: 280-290 H/s, steady. CPU utilization is 40-50%. I can communicate with the GPUs while it's mining as usual.
miniZ 150,5: starts at ~250 H/s for a about 1 minute, then gradually drops to ~180 H/s within ~2 minutes. CPU is kept at 100% at all times and any GPU command issued hangs (e.g. nvidia-smi hangs entirely). The nvidia driver is totally hogged.
I tried lowering --intensity and the CPU utilization drops, but the hashrate drops significantly too, even if I use --intensity 99. Max I can get is about ~195 H/s.
I also tried --oc1 and --oc2. Also tried --telemetry 0 (doesn't disable nvml polling). Nothing made any difference (even though I have them overclocked and at lower power limits).
I'm willing to test a beta if you're willing to work on this. PM me. I manage a small farm.
EDIT: Retested Gminer on 150,5. Gets 280-290 H/s steady, with 40-50% CPU utilization.
You should find a way to drop CPU utilization and driver usage. You should also add an option to disable nvml polling of temperature, fans, power etc.
13x gtx1070, i3-7100, 8 GB ram, Ubuntu x64, nvidia 415.27, cuda 10.0
Gminer 150,5: 280-290 H/s, steady. CPU utilization is 40-50%. I can communicate with the GPUs while it's mining as usual.
miniZ 150,5: starts at ~250 H/s for a about 1 minute, then gradually drops to ~180 H/s within ~2 minutes. CPU is kept at 100% at all times and any GPU command issued hangs (e.g. nvidia-smi hangs entirely). The nvidia driver is totally hogged.
I tried lowering --intensity and the CPU utilization drops, but the hashrate drops significantly too, even if I use --intensity 99. Max I can get is about ~195 H/s.
I also tried --oc1 and --oc2. Also tried --telemetry 0 (doesn't disable nvml polling). Nothing made any difference (even though I have them overclocked and at lower power limits).
I'm willing to test a beta if you're willing to work on this. PM me. I manage a small farm.
EDIT: Retested Gminer on 150,5. Gets 280-290 H/s steady, with 40-50% CPU utilization.
August 07, 2019, 08:05:17 AM
why does miniZ sometimes popup a dialog box when it crashes? this results in the program stopping until I press a button and bat file loop restarts miniz and continues mining. this dialog box presents a productivity issue as I may not notice this box popup for some amount of time while the miner is doing 0 work. how can I disable this dialog box from appearing?
also: when there is a problem with a GPU it spams errors on all the GPUs so I cant identify which GPU actually caused the crash.
also: when there is a problem with a GPU it spams errors on all the GPUs so I cant identify which GPU actually caused the crash.
August 04, 2019, 06:37:17 PM
Thanks!
Really waiting for it. I prefer miniZ over any other miner as you know.
Thanks for your preference Really waiting for it. I prefer miniZ over any other miner as you know.
Cheers
August 04, 2019, 06:36:36 PM
Hi,
some news about date for the new release ?
Hi Nairolf911,some news about date for the new release ?
We will try to get it out next Sunday.
Cheers
August 04, 2019, 06:34:51 PM
Thanks!
Really waiting for it. I prefer miniZ over any other miner as you know.
Really waiting for it. I prefer miniZ over any other miner as you know.
August 04, 2019, 06:33:16 PM
Hi,
I'm getting random rejected shares, like 60 at once in the console output (that's not normal, for sure) on Flypool mining YEC. Other miners work just fine, no rejected shares. GTX 1060 6GB, Windows 10, 431.60 drivers.
Hi MineOrDie,I'm getting random rejected shares, like 60 at once in the console output (that's not normal, for sure) on Flypool mining YEC. Other miners work just fine, no rejected shares. GTX 1060 6GB, Windows 10, 431.60 drivers.
It looks like the miner might be submiting some shares bellow target, on flypool.
This should not affect performance but we will check this further.
Thanks for reporting this.
Cheers
Also, is there something wrong with color output on Windows 8.1? GMiner works fine.
this should be fixed in the next version.
Regarding the color output, Windows 8 console does not support miniZ colors. Check here for more information.
Cheers
August 04, 2019, 05:58:34 AM
Hi,
some news about date for the new release ?
some news about date for the new release ?
August 03, 2019, 11:18:25 PM
Hi,
I'm getting random rejected shares, like 60 at once in the console output (that's not normal, for sure) on Flypool mining YEC. Other miners work just fine, no rejected shares. GTX 1060 6GB, Windows 10, 431.60 drivers.
Hi MineOrDie,I'm getting random rejected shares, like 60 at once in the console output (that's not normal, for sure) on Flypool mining YEC. Other miners work just fine, no rejected shares. GTX 1060 6GB, Windows 10, 431.60 drivers.
It looks like the miner might be submiting some shares bellow target, on flypool.
This should not affect performance but we will check this further.
Thanks for reporting this.
Cheers
Also, is there something wrong with color output on Windows 8.1? GMiner works fine.
August 03, 2019, 07:24:53 PM
Hi,
I'm getting random rejected shares, like 60 at once in the console output (that's not normal, for sure) on Flypool mining YEC. Other miners work just fine, no rejected shares. GTX 1060 6GB, Windows 10, 431.60 drivers.
Hi MineOrDie,I'm getting random rejected shares, like 60 at once in the console output (that's not normal, for sure) on Flypool mining YEC. Other miners work just fine, no rejected shares. GTX 1060 6GB, Windows 10, 431.60 drivers.
It looks like the miner might be submiting some shares bellow target, on flypool.
This should not affect performance but we will check this further.
Thanks for reporting this.
Cheers
Jump to: