miniZ v1.9z4 is out!

Hi everyone,

A new miniZ version v1.9z4 is out with many new improvements and features.

Performance improvements for 125,4 – FLUX – mining! Up to 20%! Also, we managed to improve 150,5 algo.

Added ubqhash support, progpow (and variants) support for AMDs, fan control for AMDs, fan/temperature control option…check complete changelog below.

Please find miniZ version v1.9z4 Download page.

miniZ version v1.9z4 is out!



  • Major performance improvements for 125,4 on all gpus. Up to 20%.
  • Performance improvements for 150,5 on all gpus.
  • Added ubqhash algorithm for Ubiq (UBQ) mining.
  • Added AMD support for all progpow algos.
  • Added fan/target temperature control option --fantemp.1
  • Changed AMD GPU order to PCI order.
  • Added AMD fan control.
  • Added support for NVIDIA RTX 40XX GPUs.
  • Fixed issue with Telemetry.
  • Fixed Ampere modes that were not launching well on Aion mining.
  • Fixed 96,5 support.
  • Added reset value to power option. --power=1 will reset to stock value. (0 to ignore)
  • Power option shows range when trying to set different value.

1 Requires sudo (Linux)/administator privileges (Windows)
Works with:
Linux: AMDs; and NVIDAs w/ driver >515
Windows: Polaris AMDs; and NVIDIAs w/ driver >515
On exit --fantemp resets to auto on AMDs, and to 50% fan on NVIDIAs.
When using --fanspeed conjointly with --fantemp, the fan % defined with --fanspeed works as minimum fan speed.


*** Thank you all for the feedback! ***

Remember to try --oc1/--oc2/--ocX options for optimum performance. (NVIDIA only)

For additional information check our Usage or FAQ pages.

*** Download miniZ latest version here. ***

Engage, feedback and support

Because your feedback is very important, miniZ kindly encourages you to use the comment box below for general questions and feedback.

Certainly we will strive to help you with any doubt and provide a solution to any problem you may encounter. In case you need to reach us, please check the Support page.

Follow us
On Twitter
Our thread on

We wish you a fast and friendly mining experience!



Recent Posts



  1. Tswift says:

    Thank you for adding ubqhash and great work on the Flux improvements. Equihash 210,9 (AION) still not working properly with CMP 170HX cards. Mini Z miner will only run them at about 30-40 watts and only 8-9 kSol/s for some reason. Any chance you can fix this?

    • Tswift says:

      Sorry, apparently my Hive update command didn’t work properly, so it was still using the old version of miniZ. Will test again later after it updates properly and report back again.

  2. LazloMo says:

    Increased Power usage by 8-10% on my 3060Ti s3-6% higher temp.crashes on my previous oc settings needs more CV and Lower CC.compared to V1.8y3_win

    • miniZ says:

      Hi LazloMo,
      Could you share your values? OCs and PL, on each version?
      The latest version is more optimised, miniZ boosted a bit the performance (usually power follows performance) so it can be that the OCs need to be adjusted.
      We’ll have a look. Thank you for the feedback.

  3. Issue with Linux download ... says:

    There seems to be an issue with the download link on HiveOS/Ubunt, but download works on local Win desktop…

  4. Issue with download server site says:

    root@rig5:/tmp# wget
    [2] 10505
    Redirecting output to ‘wget-log’.

    [2]- Exit 8 wget
    root@rig5:/tmp# cat wget-log
    –2022-10-23 18:35:38–
    Resolving (…, 2606:4700:130:436c:6f75:6466:6c61:7265
    Connecting to (||:443… connected.
    HTTP request sent, awaiting response… 500 Internal Server Error
    2022-10-23 18:35:39 ERROR 500: Internal Server Error.

  5. Issue with Linux download ... says:

    HTTP request sent, awaiting response… 500 Internal Server Error2022-10-23 20:43:55 ERROR 500: Internal Server Error.

    • miniZ says:

      Hi Issue with Linux download …,
      Try this instead:
      wget '' -O miniz.tar.gz
      When you have characters such as ? or &…you need to use the ‘ ‘.
      Let us know how it goes.

  6. Getting CUDA error when running with ethash ….[FATAL ] CUDA Driver API error = 0001 from line 1100.”>

    • CUDA error when running with ethash says:

      Found the issue… –OCX is not friendly to Ethash Algo…

      • miniZ says:

        Hi CUDA error when running with ethash,
        It can happen, but we’ll have a look. Could you give us some information?
        Which GPU is having this issue? Also, could you share your OCs and command line?
        And the output of running miniZ.exe -ci?

  7. dennis says:

    is it possible to add KHeavyHash?

  8. Bazs says:


    miniz equihas very good performance for AMD cards. But i have a problem. 144,5 algo 12 6800xt cards. The GPU 0,1 make only 4-8 sol. Another make 80-90 sol. Another algo under flux 125,4 working all GPU perfect 50-60 sol. What is the problem? All oc is Same hiveos

    • miniZ says:

      Hi Bazs,
      Thank you for your words, and feedback.
      We made improvements for the 144,5 algo, in the new release, maybe it will fix this issue.

      Do you have any screen attached? Or are you using the GPU for any other purpose, other than mining?

      You can also try to adjust the OCs a little, for the 2 GPUs. You may need to reboot your system too, just in case they crashed.

      Let us know how it goes. We should publish the new release very soon.

  9. Wayland says:

    Fantastic performance improvements across all of my NVIDIA GPUs. Is –oc1 and –oc2 mutually exclusive? Can they be combined with –ocx?

    • miniZ says:

      Hi Wayland,
      Thank you for your kind words.
      --ocX will run all kernels available for the GPU, identifies the best and runs it.
      --oc1/--oc2 (nvidia only) will run the kernel that was predefined for that option.
      If you add all of them to the command line, it will only apply the one appearing last.

      • Wayland says:

        I am using –ocX with my NCIDIA cards. What is taking place when I read the following line? (If there is documentation please pass on the link so I can read it to answer my own questions.) GPU[10]: Optimisation temperature not stable *T=64+-2.2C* How does this relate to my overclocks, if at all? My rigs are in a shed without cooling, other than pulling in the outside air into the shed to cool the cards. Generally at night I set more aggressive overclocks and then back them off in the morning when the heat starts to rise. Should I restart my workers to have MiniZ account for the temperature change of the air being brought into the shed?

        • miniZ says:

          Hi Wayland,
          This message is related to the --ocX option. Since temperature affects hashrate, to make better comparison of all kernels, miniZ ‘looks’ at temperature and waits a bit until it becomes stable (reasonably stable).
          If you change OCs at night, it is best to restart miniZ with --ocX again. 🙂

  10. Noël says:

    Hello, so i have 3070, 2060S, 2070S and 2080TI. i have problems overclocking my 2x 2070S as one of them just crashes. i had to go -100mhz core delta – but now, the 2070S get only 50sol/s and take 125w. the rest of the gpus are working fine. could miniZ do a new sheet with updated overclocks?

    • miniZ says:

      Hi Noël,
      Could you let us know what algorithm are you mining? We’ll update the tables soon, however our values are just a reference. You may need to adjust the OCs a bit. There is always some variability, since systems are different (Power supply, MB…). Are you on Windows or Linux?
      What OCs are you using? Have you tried something like -260 offset for memory clock (-130 memclock if you’re on Windows) +240 offset for core clock?

  11. Dash says:

    please add minimum/maximum settings for autofan and indication of fan speed (and GPU/memory frequency) in telemetry web interface.

  12. alex says:

    is there an option to write the timestamp to the log file?

    • miniZ says:

      Hi alex,
      Try --localtime=13, is this what you’re looking for?

      Option --localtime=[n]
      [0-4] will show runtime or formatted local time.
      [11-14] will show both runtime and formatted local time.


  13. Mike says:

    using hive os. your core clock and memory clock work on 30series gpus, but on 20 series gpus the memory lock clock doesnt work but the core clock does.

    • Mike says:

      locked core clock and locked memory clock –gpuclock
      –memclock forgot to add to original message

      • miniZ says:

        Hi Mike,
        Thank you for your message.
        Currently, you might not be able to use it. This is driver related.
        In the next release you’ll be able to use the --memoffset/--gpuoffset options.

  14. alex says:

    What about watchdog by hasrate?

  15. Mike says:

    Have 4 rigs. 3 of them work well.

    All the same drivers and version of miniZ

    One of the rigs keeps getting

    cuda error 73 an illegal instruction was encountered on line 305

    It is a mixed rig, with 1660 supers and 30 series card.

    Tried lowering oc but the errors still. Pop up every few hours.

    Rig is stable on 1.83 but not 1.94

    Driver 512.15.

    One of my other rigs also contains 1660 super with 512.15 and 1.94 and is still with the original oc as 1.83

    Any ideas?


    • miniZ says:

      Hi Mike,

      Are you still having this issue with latest version? Version v1.95b should run more stable, includes a few fixes.
      Also corrects a nasty bug.

      What algo are you mining? Recent versions include improvements and may require OC adjustment.

      If the rig keeps crashing, could you paste here a bit of miner log?


  16. XKKK says:

    [ERROR ] GPU[00] cannot adjust fan, this driver version does not allow changing fan speed! Windows OS, driver nvidia 512.15

  17. Zas says:


    I am getting a core dump on rig running the latest Hiveos, composed of with 5 1660 Super and a 3060 V1. The log entry is this:

    [31221.712020] miniZ[2955]: segfault at 1 ip 00007fd3f2b121b7 sp 00007fd35effb3b0 error 4 in[7fd3f2a7b000+1e7000]
    [31221.712027] Code: 64 48 8b 4d 00 48 85 c9 0f 84 f1 fe ff ff 0f 1f 44 00 00 48 8d 34 c1 48 8b 56 40 48 85 d2 0f 84 db fe ff ff 48 83 f8 3f 77 21 <48> 8b 3a 48 89 7e 40 80 2c 01 01 48 c7 42 08 00 00 00 00 48 83 c4

    Any ideas?

    • miniZ says:

      Hi Zas,
      Thank you for the feedback.
      How long had miniZ been running?

      • Zas says:

        Hi,Usually the error comes within a 2-3 hours. But it is not always the same.Now it has been like 18 hours with no error. Went down from 1485 locked core to 1410, on the Supers.Thank you,

        • miniZ says:

          Hi Zas,
          Thank you for the feedback.

          Have you updated the version to v1.9z5b?
          This issue should be fixed with the lastest version.

          Let us know how it goes.

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    I accept the Privacy Policy