My Sol/s…

You can help updating this table.

Leave your comment below with your Sol/s per GPU, and OC settings, as this might help others to tweak their configurations.

miniZ will try to update these numbers, based on your best reported values.

 

Categories

Search

Comments

  1. viktor says:

    palit game rock 1070 – rig 6x

    av. – 54 sol/s, p0, pl 75%, core +180, memory 0

    • kreem em says:

      gigabyte rtx 3080 SUPER ETHASH [ 0d 4h 2m10s] S:319/0/3 3>RTX 3080[28] `99.1% [51 C/100%]* 99.47( 99.49)MH/s 254(252.9)W clk=1170MHz mclk=10551MHz MH/W=0.39

  2. styleshifter says:

    Laptop with Geforce 940M and 2 GB RAM gets 3.5 Sol/s

  3. Crypto says:

    Dear Team,

    Please shared overclocking setting for GTX 1060 6GB GPU.

  4. ssong says:

    1080ti power limit 69% core +110clock memory -405clock 61 Celcius

    miniZ 1.0j 83~85sol/s
    EWBF v0.6 71~75sol/s

    approx. Pool amount average per day = more over 5~8% EWBF v0.6

  5. Darko says:

    Looked at your 1060 3gb OC settings …

    None of my card with Samsung mem on 60PL cann’t go upper than 110 Core and 500 mem …

    Your ECO table is not OK

    • miniZ says:

      Hi Darko,

      On the 1060GB, with PL=60W (50%), we use core = +250 and mem = -600, in Linux.
      If you are on Windows and use MSI Afterburner: core = +250 and mem = -300.
      We see that we do have a mistake on the table. https://miniz.ch/1445-2/ is correct.(we are updating the other algo pages)

      Thanks for the feedback.
      Cheers

      • Darko says:

        The miniz 1.3n and 1.3n+ have a memory alloc error on 1060 3gb …

        I supose it’s on clocks …

        Im on mmpos (linux system),will try again with +250 and -600

        • Darko says:

          It doesn’t work … Must to change the clocks to 110/500/60PL … The miner on your clocks is all time memory alloc fail …

          • miniZ says:

            Hi Darko,
            Our implementation of BEAM runs very tight on the 1060 3GB, but it works fine on our system.
            Could you show us the output of ./miniZ -ci ?
            Also try to run miniZ with --mode=0 (it will run slower… but it is good to know if it works).
            Does the miner tells you the ammount of memory it wants to allocate?

            Cheers,
            miniZ

  6. Darko says:

    It says 2924 needed to allocate …

    Aain on hive it was a invalid share period (a little bit long),when it got 88k invalid shares

    • Darko says:

      Another invalid shares on mmpos …

      • miniZ says:

        Hi Darko,
        Thanks for reporting, are you using sparkpool?
        There might some issue with this pool, we are looking into it.
        About the 3GB card, whe you have time cloud give us the output of
        ./miniZ -ci ? That would help us to understand why you do not have enough memory.
        Cheers,
        miniZ

        • Darko says:

          Don’t have the ./miniZ directory …

          Again a fail on HiveOS,yes it is with sparkpool …

          Now I cann’t start the miner again … 1.3n+ version

  7. Darko says:

    |——————————-+———————-+———————-+
    | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
    | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
    |===============================+======================+======================|
    | 0 GeForce GTX 106… On | 00000000:01:00.0 Off | N/A |
    | 60% 68C P2 78W / 90W | 2851MiB / 3019MiB | 100% Default |
    +——————————-+———————-+———————-+
    | 1 GeForce GTX 1070 On | 00000000:03:00.0 Off | N/A |
    | 60% 58C P2 99W / 100W | 3409MiB / 8119MiB | 100% Default |
    +——————————-+———————-+———————-+
    | 2 GeForce GTX 1070 On | 00000000:04:00.0 Off | N/A |
    | 60% 55C P2 111W / 100W | 3409MiB / 8119MiB | 100% Default |
    +——————————-+———————-+———————-+
    | 3 GeForce GTX 106… On | 00000000:05:00.0 Off | N/A |
    | 60% 57C P2 65W / 90W | 2851MiB / 3019MiB | 100% Default |
    +——————————-+———————-+———————-+
    | 4 GeForce GTX 106… On | 00000000:06:00.0 Off | N/A |
    | 60% 65C P2 85W / 90W | 2851MiB / 3019MiB | 100% Default |
    +——————————-+———————-+———————-+
    | 5 GeForce GTX 107… On | 00000000:07:00.0 Off | N/A |
    | 60% 61C P2 115W / 120W | 3429MiB / 8119MiB | 100% Default |
    +——————————-+———————-+———————-+

    +—————————————————————————–+
    | Processes: GPU Memory |
    | GPU PID Type Process name Usage |
    |=============================================================================|
    | 0 1979 G /usr/lib/xorg/Xorg 6MiB |
    | 0 21193 C /hive/miners/gminer/1.39/miner 2833MiB |
    | 1 1979 G /usr/lib/xorg/Xorg 6MiB |
    | 1 21193 C /hive/miners/gminer/1.39/miner 3391MiB |
    | 2 1979 G /usr/lib/xorg/Xorg 6MiB |
    | 2 21193 C /hive/miners/gminer/1.39/miner 3391MiB |
    | 3 1979 G /usr/lib/xorg/Xorg 6MiB |
    | 3 21193 C /hive/miners/gminer/1.39/miner 2833MiB |
    | 4 1979 G /usr/lib/xorg/Xorg 6MiB |
    | 4 21193 C /hive/miners/gminer/1.39/miner 2833MiB |
    | 5 1979 G /usr/lib/xorg/Xorg 6MiB |
    | 5 21193 C /hive/miners/gminer/1.39/miner 3411MiB |
    +—————————————————————————–+
    [email protected]:~#

    • Darko says:

      [email protected]:~# nvidia-smi
      Mon Apr 29 09:59:49 2019
      +—————————————————————————–+
      | NVIDIA-SMI 396.54 Driver Version: 396.54 |
      |——————————-+———————-+———————-+
      | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
      | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
      |===============================+======================+======================|
      | 0 GeForce GTX 106… On | 00000000:01:00.0 Off | N/A |
      | 60% 65C P2 77W / 80W | 3007MiB / 3019MiB | 100% Default |
      +——————————-+———————-+———————-+
      | 1 GeForce GTX 1070 On | 00000000:03:00.0 Off | N/A |
      | 60% 57C P2 102W / 100W | 4653MiB / 8119MiB | 98% Default |
      +——————————-+———————-+———————-+
      | 2 GeForce GTX 1070 On | 00000000:04:00.0 Off | N/A |
      | 60% 55C P2 102W / 100W | 4653MiB / 8119MiB | 100% Default |
      +——————————-+———————-+———————-+
      | 3 GeForce GTX 106… On | 00000000:05:00.0 Off | N/A |
      | 60% 59C P2 71W / 80W | 3007MiB / 3019MiB | 100% Default |
      +——————————-+———————-+———————-+
      | 4 GeForce GTX 106… On | 00000000:06:00.0 Off | N/A |
      | 60% 63C P2 83W / 80W | 3007MiB / 3019MiB | 100% Default |
      +——————————-+———————-+———————-+
      | 5 GeForce GTX 107… On | 00000000:07:00.0 Off | N/A |
      | 60% 60C P2 103W / 110W | 4673MiB / 8119MiB | 100% Default |
      +——————————-+———————-+———————-+

      +—————————————————————————–+
      | Processes: GPU Memory |
      | GPU PID Type Process name Usage |
      |=============================================================================|
      | 0 1982 G /usr/lib/xorg/Xorg 6MiB |
      | 0 23809 C /hive/miners/custom/miniZ/miniZ 2989MiB |
      | 1 1982 G /usr/lib/xorg/Xorg 6MiB |
      | 1 23809 C /hive/miners/custom/miniZ/miniZ 4635MiB |
      | 2 1982 G /usr/lib/xorg/Xorg 6MiB |
      | 2 23809 C /hive/miners/custom/miniZ/miniZ 4635MiB |
      | 3 1982 G /usr/lib/xorg/Xorg 6MiB |
      | 3 23809 C /hive/miners/custom/miniZ/miniZ 2989MiB |
      | 4 1982 G /usr/lib/xorg/Xorg 6MiB |
      | 4 23809 C /hive/miners/custom/miniZ/miniZ 2989MiB |
      | 5 1982 G /usr/lib/xorg/Xorg 6MiB |
      | 5 23809 C /hive/miners/custom/miniZ/miniZ 4655MiB |
      +—————————————————————————–+
      This is with miniZ miner 1.3n2 (started half hour ago 9.30 am CET)

      • Darko says:

        Another failture …

        The miner was down after 3 hours …

        • miniZ says:

          Hi Darko,
          Did you manage to run the 3GB cards?
          Your failures appear to be related with the OC settings, remember that different miners require different settings.
          On the upcoming version 1.3n3 it should be easier to see the GPU errors. You can download it already https://miniz.ch/download/
          Cheers

          • Darko says:

            The LA is high 2 most in red on hive …

            invalid shares,also on sunpool …

            will try now with n3 version

            • miniZ says:

              Hi Darko,
              Thanks for taking you time to report and test.
              After the main stability issues we had with the version 1.3 are fixed, we will look after the high LA.
              Cheers

  8. Darko says:

    The miner is working for 12 hours now,with a smaller number of inwalid shares …
    (changed the pool to sunpool wich is in germania and I’m in croatia so the latecy should be low)

    the n3 version is much,much better must say now it’s a great work from your side …

    And the LA will come in some days,I hope 🙂

    • miniZ says:

      Hi Darko,
      thanks for letting us know that it is working fine for you.
      Mining to sparkpool is working fine now, but it is true that you may get better latency from closer servers.
      We keep trying to improve the LA 🙂
      Cheers

  9. Steve says:

    1070tis – Average 25 S/s – +100 core, + 500 Mem – 70% power
    1080tis – Average 36 S/s – +100 core, + 500 Mem – 70% power
    1070’s – Average 21 S/s – +100 core, + 500 Mem – 70% power

    1070tis – Average 26 S/s – +100 core, + 700 Mem – 70% power
    1080tis – Average 36 S/s – +100 core, + 700 Mem – 70% power
    1070’s – Average 21.5 S/s – +100 core, + 700 Mem – 70% power

  10. ZhieN says:

    0>GTX 1060 3GB 99.8% [55°C/80%] 16.88 I/s 33.6(33.7)Sol/s 91( 90.0)W clk=1847MHz mclk=4201MHz Sol/W=0.37
    1>GTX 1060 3GB
    100% [61°C/80%] 16.98 I/s 34.4(33.8)Sol/s 89( 89.8)W clk=1809MHz mclk=4201MHz Sol/W=0.38
    2>GTX 1060 3GB 100% [57°C/80%] 17.01 I/s 34.4(33.9)Sol/s 97( 90.0)W clk=1797MHz mclk=4201MHz Sol/W=0.38
    3>GTX 1060 3GB
    100% [59°C/80%] 17.17 I/s 34.7(34.4)Sol/s 93( 90.4)W clk=1771MHz mclk=4201MHz Sol/W=0.38

    GTX 1060 3GB : Power 80 | Core Clock 99% | Memory Clock 399% | Fan Speed 80%

  11. CuChO says:

    Just stopping by and drooping my test , I test OC1 and got less sols and OC2 is slightly less then my own clocks on its own , I try some of the values from the tablet but didn’t do anything , like a quick explain will be once the gpu need more power to OC higher any from +100 to +150 wont affect that’s how I got to know my GPUs in Windows but downclocking memory this make space for more OC on core.
    So on afterburner I run my 2070s at -270 on Memory and my 1080s a -370 , for some reason this allow me to OC higher the clocks
    My GPUS Models taking the order from the list are
    GPU0 MSI Duke Triple Fans RTX2070 stock clocks are a bit lower compared to the GPU1
    GPU1 MSI Duke Triple Fans RTX2070 this card has better clocks
    GPU2 Zotac Mini RTX2070 cards has good clocks compare to the other Zotac
    GPU3 EVGA Gaming GTX1080 overall hash is good comparing to my others cards
    GPU4 Zotac Mini RTX2070 clocks are lowers then the GPU2 in stocks settings
    GPU5 Gigabyte Gaming OC edition GTX1080 worse card , this card need more power in order to OC higher
    GPU6 Asus Gaming Strix GTX1080 good clocks will run most of the time same hashrate as GPU7
    GPU7 EVGA SC GTX1080 Best card ever since has higher clocks with out the need of increasing power

    My Clocks
    [ 0d 1h56m45s] 524(523.7)Sol/s 1002(1016.1)W
    0>RTX 2070 100% [51°C/51%] 35.87 I/s 72.1(71.0)Sol/s 128(128.5)W clk=1680MHz mclk=6530MHz Sol/W=0.55
    1>RTX 2070
    100% [53°C/53%]*36.10 I/s 72.4(72.1)Sol/s 128(128.4)W clk=1695MHz mclk=6530MHz Sol/W=0.56
    2>RTX 2070 100% [61°C/61%] 33.48 I/s 66.7(67.7)Sol/s 124(124.0)W clk=1590MHz mclk=6530MHz Sol/W=0.55
    3>GTX 1080
    100% [52°C/52%] 30.23 I/s 60.8(61.7)Sol/s 117(124.3)W clk=1607MHz mclk=4140MHz Sol/W=0.50
    4>RTX 2070 100% [59°C/60%]*32.16 I/s 63.6(64.2)Sol/s 124(124.4)W clk=1515MHz mclk=6530MHz Sol/W=0.52
    5>GTX 1080
    100% [55°C/55%] 30.43 I/s 60.6(60.6)Sol/s 131(133.8)W clk=1569MHz mclk=4140MHz Sol/W=0.45
    6>GTX 1080 100% [50°C/51%] 31.65 I/s 63.4(62.9)Sol/s 128(129.3)W clk=1670MHz mclk=4140MHz Sol/W=0.49
    7>GTX 1080
    100% [55°C/55%] 31.96 I/s 64.2(63.6)Sol/s 121(125.6)W clk=1708MHz mclk=4140MHz Sol/W=0.51

    oc1
    [ 0d 0h 5m12s] 509(509.4)Sol/s 991(997.6)W
    0>RTX 2070 100% [52°C/52%] 35.84 I/s 71.4(71.7)Sol/s 129(128.6)W clk=1695MHz mclk=6530MHz Sol/W=0.56
    1>RTX 2070
    100% [53°C/52%] 36.16 I/s 72.7(73.0)Sol/s 129(128.6)W clk=1695MHz mclk=6530MHz Sol/W=0.57
    2>RTX 2070 100% [61°C/60%] 33.49 I/s 66.3(66.7)Sol/s 123(124.0)W clk=1590MHz mclk=6530MHz Sol/W=0.54
    3>GTX 1080
    100% [52°C/52%] 28.87 I/s 58.1(58.1)Sol/s 115(121.6)W clk=1670MHz mclk=4140MHz Sol/W=0.48
    4>RTX 2070 100% [59°C/60%] 32.26 I/s 65.5(65.3)Sol/s 125(124.6)W clk=1515MHz mclk=6530MHz Sol/W=0.52
    5>GTX 1080
    100% [53°C/53%] 28.90 I/s 57.0(57.1)Sol/s 132(127.7)W clk=1670MHz mclk=4140MHz Sol/W=0.45
    6>GTX 1080 100% [50°C/50%] 29.16 I/s 58.6(58.4)Sol/s 117(123.5)W clk=1746MHz mclk=4140MHz Sol/W=0.47
    7>GTX 1080
    100% [55°C/54%] 29.25 I/s 58.4(58.5)Sol/s 120(119.0)W clk=1771MHz mclk=4140MHz Sol/W=0.49

    -oc2
    [ 0d 0h 5m32s] 517(517.3)Sol/s 1009(1009.6)W
    0>RTX 2070 100% [52°C/52%] 35.74 I/s 71.0(71.1)Sol/s 128(128.5)W clk=1665MHz mclk=6530MHz Sol/W=0.55
    1>RTX 2070
    100% [53°C/53%] 36.11 I/s 71.6(71.6)Sol/s 128(128.5)W clk=1695MHz mclk=6530MHz Sol/W=0.56
    2>RTX 2070 100% [61°C/61%]*33.46 I/s 66.4(66.5)Sol/s 123(123.6)W clk=1605MHz mclk=6530MHz Sol/W=0.54
    3>GTX 1080
    100% [52°C/53%] 30.17 I/s 61.3(61.0)Sol/s 123(122.0)W clk=1607MHz mclk=4140MHz Sol/W=0.50
    4>RTX 2070 100% [60°C/60%] 32.16 I/s 62.7(63.1)Sol/s 124(124.4)W clk=1530MHz mclk=6530MHz Sol/W=0.51
    5>GTX 1080
    100% [54°C/54%] 30.25 I/s 61.3(61.0)Sol/s 134(132.7)W clk=1594MHz mclk=4140MHz Sol/W=0.46
    6>GTX 1080 100% [50°C/50%] 30.88 I/s 61.0(60.8)Sol/s 128(126.9)W clk=1683MHz mclk=4140MHz Sol/W=0.48
    7>GTX 1080
    100% [55°C/55%] 31.18 I/s 62.1(62.1)Sol/s 120(123.0)W clk=1683MHz mclk=4140MHz Sol/W=0.51
    -oc2 test 2
    [ 0d 0h56m28s] 518(519.1)Sol/s 1015(1006.3)W
    0>RTX 2070 100% [51°C/51%] 35.66 I/s 71.5(71.3)Sol/s 129(128.4)W clk=1680MHz mclk=6530MHz Sol/W=0.56
    1>RTX 2070
    100% [53°C/53%] 36.21 I/s 72.1(72.1)Sol/s 129(128.5)W clk=1695MHz mclk=6530MHz Sol/W=0.56
    2>RTX 2070 100% [61°C/60%] 33.46 I/s 66.2(66.9)Sol/s 124(123.9)W clk=1605MHz mclk=6530MHz Sol/W=0.54
    3>GTX 1080
    100% [52°C/52%] 30.16 I/s 59.9(60.4)Sol/s 127(122.0)W clk=1620MHz mclk=4140MHz Sol/W=0.50
    4>RTX 2070 100% [60°C/60%] 32.09 I/s 64.0(64.4)Sol/s 124(124.4)W clk=1515MHz mclk=6530MHz Sol/W=0.52
    5>GTX 1080
    100% [54°C/54%] 30.24 I/s 60.5(60.4)Sol/s 131(130.4)W clk=1569MHz mclk=4140MHz Sol/W=0.46
    6>GTX 1080 100% [50°C/49%] 30.88 I/s 61.1(61.6)Sol/s 122(124.8)W clk=1683MHz mclk=4140MHz Sol/W=0.49
    7>GTX 1080
    100% [55°C/55%] 31.18 I/s 62.1(61.9)Sol/s 129(124.1)W clk=1708MHz mclk=4140MHz Sol/W=0.50

    Note: The Gigabyte card if I go positive on memory the core will just drop -100 just because of the power limit, card is a 200 watts model same as the ASUS , the Zotacs Minis are rated a 175 watts , the rest is 180 watts models

    • miniZ says:

      Hi CuChO,
      First of all THANKS a lot for the feedback!

      Second, our GPUs are from different brand but they should be more or less similar. Except for the minis, these tend to be a bit slower but not so much, likely due to power limit as you mentioned. However, your 2070 seems to be running faster than ours 🙂

      Finally, we believe that we need to clarfy something because from what you wrote it looks that we were not clear in our previous suggestions, sorry for this. The --oc1/2 in the command line does not apply OCs to the GPU, it just makes the GPU run with different kernel functions. When you adjust the OCs in Afterburner (or other program) and run miniZ without --oc1/2 the miner will run with the default kernels (usually optimized for stock settings). So, in summary the --oc‘s just change the way miniZ runs not the OC settings of the GPU. We hope this is clear now. We’ll try to make it more clear also in FAQ.

      In Table 2, we applied the OCs as shown *and* ran the 1080 with --oc1. At least for our 1080 Eco running with –oc1 boosts performance.

      Thanks for your preference!
      Cheers

      Note 1: For memory clock in AF, you need to divide our value by 2. We have a note there in darkred.
      Note 2: --oc1/2 can be set up per GPU if necessary, check FAQ page.

      • CuChO says:

        thanks make more sense , like a not good OC the –oc options will help to get extra hash in case if there is any missing , I post the clocks that they are actually running since +100 or any other number doesn’t apply unless every card can run on the same core right out of the box 😀 but on memory this all match since they all run a same like 1080s have the same memory speed . Well maybe is Linux I read there are better hashrate there, thanks for the help.
        Cheers guys great work on this miner

  12. CuChO says:

    Another benchmark for 192,7
    My GPUS Models and Afterburner settings
    GPU0 MSI Duke Triple Fans RTX2070 70% +100 core -270Mem
    GPU1 MSI Duke Triple Fans RTX2070 70% +50 core -270Mem
    GPU2 Zotac Mini RTX2070 71% +125 core -270Mem
    GPU3 EVGA Gaming GTX1080 70% +100 core + 0Mem
    GPU4 Zotac Mini RTX2070 71% +150 core -270Mem
    GPU5 Gigabyte Gaming OC edition GTX1080 65% +120 core -370Mem
    GPU6 Asus Gaming Strix GTX1080 65% +150 core + 0Mem
    GPU7 EVGA SC GTX1080 70% +100 core + 0Mem

    0d 8h50m53s] 298(297.3)Sol/s 992(1002.7)W
    0>RTX 2070 100% [51°C/51%] 20.52 I/s 40.7(41.1)Sol/s 127(127.6)W clk=1665MHz mclk=6530MHz Sol/W=0.32
    1>RTX 2070
    100% [53°C/53%] 20.66 I/s 41.5(41.2)Sol/s 127(126.7)W clk=1695MHz mclk=6530MHz Sol/W=0.33
    2>RTX 2070 100% [61°C/61%] 19.18 I/s 38.1(38.3)Sol/s 123(123.0)W clk=1590MHz mclk=6530MHz Sol/W=0.31
    3>GTX 1080
    100% [52°C/52%] 17.41 I/s 34.5(34.6)Sol/s 116(122.8)W clk=1556MHz mclk=4513MHz Sol/W=0.28
    4>RTX 2070 100% [60°C/60%] 18.52 I/s 37.2(37.0)Sol/s 123(123.7)W clk=1515MHz mclk=6530MHz Sol/W=0.30
    5>GTX 1080
    100% [55°C/55%] 16.98 I/s 34.5(33.7)Sol/s 134(132.6)W clk=1620MHz mclk=4140MHz Sol/W=0.25
    6>GTX 1080 100% [51°C/50%]*17.84 I/s 35.8(35.5)Sol/s 118(124.7)W clk=1670MHz mclk=4513MHz Sol/W=0.28
    7>GTX 1080
    100% [54°C/54%] 18.06 I/s 35.9(36.0)Sol/s 124(123.2)W clk=1708MHz mclk=4513MHz Sol/W=0.29

  13. Jamie says:

    Help please I have 2 1070 Asus Turbo
    tried many settings but not getting passed 32 sol/s (always stabilizes down to 30 or 31 sol/s)
    here is the settings
    Core 180-185 Memory 1500-1250 Power 120 both. HiveOS
    0>GTX 1070 100% [63°C/70%] 15.59 I/s 31.3(31.0)Sol/s 119(117.5)W clk=1607MHz mclk=4428MHz Sol/W=0.26 1.989 Sol/I
    1>GTX 1070
    100% [64°C/70%] 15.63 I/s 31.5(31.1)Sol/s 120(118.1)W clk=1594MHz mclk=4551MHz Sol/W=0.26 1.996 Sol/I
    help would be appreciated thanks 🙂

    • miniZ says:

      Hi Jamie,
      sorry for taking a bit longer to reply.
      Which algo are you mining?
      In the next version there will be some improvements for the 1070. However, if we know the algo we may be able to help you before the release.
      Thanks!
      Cheers

  14. Kos says:

    Hello,

    I am currently mining to 192.7 and am looking for optimal settings for GTX1070s. I am on Linux currently +100 core 0 mem 140w

    Thank you in advance.

    • miniZ says:

      Hi Kos,
      If you have 1070 Ti, you can find some values for the 192,7 here. We haven’t been able to update it to the last version yet, but this algorithm did not have major changes recently.

      If you have only 1070 maybe the OC settings we tested with another algorithm may serve as a starting reference.

      You can use ocX option with your settings too. miniZ then looks for the best kernel mode for the OCs that you applied.

      Let us know what worked best for you.
      Thank you for using miniZ. 🙂
      Cheers

  15. THIAGO says:

    Hello friends,

    Im trying to achieve gtx 1080 eco performance: https://miniz.ch/1445-2/.

    Can someone help me with the command line?

  16. william says:

    Any info on 30xx series? Using XC3 3070, and was playing around for the first time last night. I noticed using miniz on fluxpool, i’d get a lot of shares, but also a decent amount of bad shares. I could push upwards to 70sol/s at around 180 core, 1000 mem, 200w, but seemed kind of unstable? Granted, most pools, I have about 180ms on West US.

    Currently now trying 2miners with gMiner. If anyone got info for 3070 for best balance, shoot it out there! Unless this isn’t a good algo for my cards?

    • miniZ says:

      Hi william,

      We’re having a look at mining flux with 30XX series.
      We’ll try to reproduce the issue.
      Thank you for the feedback!

      Cheers

  17. Nagata says:

    hi, i’m new to this mining world
    trying to learn more about this
    running some miners on a GTX1060-3GB i get about 35Sol/s from 144/5
    with MiniZ this was increased to 40Sol/s

    GTX 1060 3GB 100% [66°C/54%]*20.13 I/s 40.36(40.18)Sol/s 116(114.2)W clk=1822MHz mclk=4404MHz Sol/W=0.35
    [ 0d 0h16m30s] 40(40.1)Sol/s 118(114.4)W
    0>GTX 1060 3GB
    100% [66°C/54%]*20.13 I/s 40.08(40.13)Sol/s 118(114.4)W clk=1822MHz mclk=4404MHz Sol/W=0.35
    [ 0d 0h16m40s] 40(40.1)Sol/s 120(114.5)W
    0>GTX 1060 3GB 100% [66°C/54%]*20.14 I/s 40.14(40.14)Sol/s 120(114.5)W clk=1822MHz mclk=4404MHz Sol/W=0.35
    [ 0d 0h16m50s] 40(40.1)Sol/s 120(114.6)W
    0>GTX 1060 3GB
    100% [66°C/54%] 20.14 I/s 40.09(40.13)Sol/s 120(114.6)W clk=1847MHz mclk=4404MHz Sol/W=0.35
    [ 0d 0h17m00s] 40(40.1)Sol/s 120(114.7)W
    0>GTX 1060 3GB ` 100% [66°C/54%]*20.14 I/s 40.09(40.13)Sol/s 120(114.7)W clk=1822MHz mclk=4404MHz Sol/W=0.35
    [ 0d 0h17m10s] 40(40.1)Sol/s 117(114.7)W

    • miniZ says:

      Hi Nagata,
      Good to know that with miniZ you get major improvements, when mining 144,5!
      Usually we are able to test the miner very well with the 1060 3GB, so you will also benefit with other algorithms.
      Thank you for the feedback!
      Cheers

  18. sparky says:

    Howdy from Texas!!!

    0>GTX 1080     96.8% [57°C/95%] 10.74 I/s 21.7(21.7)Sol/s 195(195.2)W clk=1911MHz mclk=5315MHz Sol/W=0.11

     1>GTX 1080     100% [52°C/95%] 10.70 I/s 21.5(21.6)Sol/s 195(191.7)W clk=1885MHz mclk=5315MHz Sol/W=0.11

     2>GTX 1080     100% [70°C/100%] 10.92 I/s 22.0(21.8)Sol/s 208(206.7)W clk=1923MHz mclk=5315MHz Sol/W=0.11

     3>GTX 1080     100% [59°C/96%] 10.70 I/s 21.5(21.4)Sol/s 186(191.6)W clk=1873MHz mclk=5315MHz Sol/W=0.11

     4>GTX 1080     ` 100% [54°C/95%] 10.45 I/s 20.6(21.1)Sol/s 195(192.7)W clk=1847MHz mclk=5315MHz Sol/W=0.11

    • miniZ says:

      Hi sparky,
      Thank you for sharing!
      Could you confirm if you are mining Beam? Could you also share your OC settings?
      Cheers

  19. Joe says:

    Hello and thanks for a great miner.

    Can Raven be mined with 1060 3gb on Windows 10?  I have tried and gotten the  “out of memory error”.

    I ask because a friend is mining Raven with similar cards but not on Windows.

    Cheers.

    • miniZ says:

      Hi Joe,
      Raven can be mined with 1060 3GB but only on Linux and Windows 7.
      Unfortunately, Windows 10 only allows to use around 81% of the card memory, and the raven DAG is about 2.8GB.

      You’ll be able to mine Zano for example that uses a similar algorithm. Or most equihash algorithms.

      Thank you for using miniZ.
      Cheers

  20. Nagata says:

    my 1060-3GB oc core 200 mem 860 pl 100

    v 1.8y2

    GTX 1060 3GB ` 100% [59°C/42%] 19.07 I/s 38.16(38.16)Sol/s  82( 91.4)W clk=1759MHz mclk=4233MHz Sol/W=0.42

    mining Zhash 144,5 on Nicehash improved BTC  from 0.000023/4 (v1.74) to 0.000025/6 (1.8y2)  daily

    • miniZ says:

      Hi Nagata,

      It is good to know that your GPU is more profitable now.

      Thank you for the feedback, this is the only way we have to know if our improvements were successful.

      Also, thank you for using miniZ.

      Cheers

  21. Julien says:

    hello

    I wanted to mine FLUX with Nvidia 30xx séries but i don’t find any OC setup

    Do you will propose it soon ?

     

    thanks

    • miniZ says:

      Hi Julien,
      You are right, the FLUX table is missing RTX 30XX information.
      Tomorrow we’ll start gradually adding some values.
      Thank you for your message!
      Cheers

  22. Scott says:

    OC Settings Linux HiveOS: CC -150 MEM 1980 – 2025 PL 120

    Miner options ETH
    –mt-auto
    –fee-time=360

    [ 0d 0h16m10s] 157(154.2)MH/s 479(475.3)W
    0>RTX 3060 100% [54°C/50%] 39.03(38.78)MH/s 120(118.8)W clk=1425MHz mclk=8312MHz MH/W=0.33
    1>RTX 3060
    50.0% [65°C/53%] 39.39(38.76)MH/s 120(119.0)W clk=1560MHz mclk=8290MHz MH/W=0.33
    2>RTX 3060 100% [58°C/50%] 39.05(38.76)MH/s 120(118.6)W clk=1560MHz mclk=8312MHz MH/W=0.33
    3>RTX 3060
    100% [52°C/50%] 39.57(38.96)MH/s 120(118.9)W clk=1620MHz mclk=8312MHz MH/W=0.33
    [ 0d 0h16m20s] 157(154.2)MH/s 479(475.4)W
    0>RTX 3060 100% [54°C/50%] 39.00(38.78)MH/s 120(118.8)W clk=1605MHz mclk=8312MHz MH/W=0.33
    1>RTX 3060
    50.0% [65°C/53%] 39.36(38.77)MH/s 120(119.0)W clk=1567MHz mclk=8290MHz MH/W=0.33
    2>RTX 3060 100% [58°C/50%] 39.10(38.78)MH/s 120(118.6)W clk=1687MHz mclk=8312MHz MH/W=0.33
    3>RTX 3060
    100% [52°C/50%] 39.61(38.98)MH/s 120(118.9)W clk=1635MHz mclk=8312MHz MH/W=0.33
    [ 0d 0h16m30s] 157(154.2)MH/s 479(475.5)W
    0>RTX 3060 100% [54°C/50%] 39.04(38.79)MH/s 120(118.8)W clk=1575MHz mclk=8312MHz MH/W=0.33
    1>RTX 3060
    50.0% [65°C/53%] 39.34(38.77)MH/s 120(119.1)W clk=1560MHz mclk=8290MHz MH/W=0.33
    2>RTX 3060 100% [58°C/50%] 39.24(38.82)MH/s 120(118.6)W clk=1695MHz mclk=8312MHz MH/W=0.33
    3>RTX 3060
    100% [52°C/50%] 39.64(39.00)MH/s 120(118.9)W clk=1620MHz mclk=8312MHz MH/W=0.33

    • miniZ says:

      Hi Scott,
      Thank you for the feedback.
      Great that it is working for you!
      For us, lowering PL to ~100W had no impact on performance. Maybe you can give it a try.
      Cheers

  23. Yesid Torres says:

    Hi, I have 4 RTX 3060 and I would like to change from lolMiner to miniZ, I tried with different OCs and they didnt work. Please help me to find the best OC or parameters , in lolMiner I’m using: Fan: 70% / Core: 100 / Mem: 2050 / PL: 115

    Thanks

    • miniZ says:

      Hi Yesid Torres,

      Thank you for your message.

      The following setting worked well for us:
      core: -150 core; mem: +2700 (Linux)/+1350 (Windows); PL: 100.

      If it doesn’t work try to add --tune=37 to the command line.

      Let us know how it goes.
      Cheers

      • Weisz says:

        Hello miniZ,

        Before try the setup i am using following OC core: -120 core; mem: +2900 (Linux); PL: 100, fan:80 and 27 MHs and with the following settings core: -150 core; mem: +2700 (Linux)/+1350 (Windows); PL: 100,–tune=37 its increased to 35MHs

        is there anyother way to tweak RTX 3060.

        Thanks

        • miniZ says:

          Hi Weisz,
          Thanks for the feedback.

          It looks that it working well for you.

          You could also try Nvidia Driver 461.40, it doesn’t work for all 3060s. If it works you may achieve ~40Mh/S.
          You could try it out. With this driver you may need to add --tune=37 if needed to make it more stable.

          We’ve been working on a new release and a few improvements should apply to the 3060, both in performance and stability.
          It has been delayed but it will be out very soon.
          Cheers

  24. Stian Arnetvedt says:

    Hmmmmm rtx 3060 LHR, rtx 3070ti LHR and rtx 3060 ti LHR dosent seam to work.

    • miniZ says:

      Hi Stian Arnetvedt,
      Could you give a bit more information?
      What OS are you using? Which Nvidia driver version?
      What is the error you’re getting (if any)?

      Are you using miniZ beta version? If you are using beta version try adding --tune=5 to your command line (maybe --tune=4 if it is not stable enough).
      We’re working on the 3070 Ti, we hope we can make a new release soon.

      Thanks.
      Cheers

  25. Yesid Torres says:

    Hi miniZ, I can’t…

    Please, help me to use it.
    Kernel 5.4.0-hiveos #108 / [email protected] VERSION OS / A 20.40 (5.9.0325) N 460.39 DRIVERS /
    FAN 0 / CORE -150 / MEM 2700 / PL 100
    miniz-ver. 1.8y4 /

    %WAL% / %URL% / -cd 0 1 2 3 –tune=37 (try with –mode=80, without tune)

    And Doesn’t work.

    Thanks

    • miniZ says:

      Hi Yesid Torres,

      Could you give us some more information so that we can understand what is not working?

      Which GPU are you using?

      What exactly is the error you get?

      Thank you for your feedback.
      Cheers

  26. hugh says:

    rtx 3060 ti LHR

  27. hugh says:

    rtx 3060 ti LHR,please tell me,how to set.someone says can be 40-45m

    windows 10

    miniz 1.8y3

    Nvidia driver version  471.11DCH

    i can tryout 42m when the generated DAG 15-16,but is not success everytime,most of the time generated DAG is 20-28,the hash is 20-23.

     

    • miniZ says:

      Hi hugh,
      We are not sure we fully understood your message.
      Your GPU should be able to make 40MH/s or a bit more.

      Are you applying any OC? Lowering power helps. Try to lower power closer to 100W.
      If it doesn’t help try adding --tune=5 (or --tune=4) to your command line.

      Also, be sure you use miniZ v1.8y4rc1

      Let us know if this helps.
      Cheers

  28. YESID TORRES says:

    Hi, I have 4 RTX 3060 and I would like to change from lolMiner to miniZ, I tried with different OCs and they didnt work. Please help me to find the best OC or parameters , in lolMiner I’m using: Fan: 70% / Core: 100 / Mem: 2050 / PL: 115

    Thanks

    Hi miniZ, I can’t…

    Please, help me to use it.
    Kernel 5.4.0-hiveos #108 / [email protected] VERSION OS / A 20.40 (5.9.0325) N 460.39 DRIVERS /
    FAN 0 / CORE -150 / MEM 2700 / PL 100
    miniz-ver. 1.8y4 /

    %WAL% / %URL% / -cd 0 1 2 3 –tune=37 (try with –mode=80, without tune)

    And Doesn’t work.

    Thanks

    • miniZ says:

      Hi YESID TORRES,
      Thank you for your message.

      Could you specify what is happening? Is it mining slow? Or it doesn’t start?
      Could you send the error message or a screenshot?

      Cheers

  29. silentminer says:

    Hi miniZ Team,

     

    I was wondering if I can get some help here. I have a whole bunch of RTX 3060 LHR v2 cards that can only work on the newer nvidia drivers. I am only able to get them to around 29-31 MH/s (not beyond). It would be much appreciated if you can tell me where is wrong here.. I am currently mining RVN on T-Rex but if I can get them up to the 37-39 range, I will gladly switch them over to miniZ on Ethash.

    GPU: RTX 3060 LHR v2 (multiple manufacturer)

    OS: HiveOS [email protected]

    Driver: 470.63.01

    OC: Core -150 MEM 2700 PL 100

    Looking forward to your response and thank you in advance!

    • miniZ says:

      Hi silentminer,

      Thank you for your message.

      With those OCs you should be able to get ~35MH/s.

      If the miniZ miner becomes unstable (not being able to get rif of the anti-mining lock) you may need to use --tune option. If it is stable running without do not use it. But if you get a message like this “[TRACE] GPU(0) Searching lock…” very often, then you may need to add --tune=5.

      Let us know how it goes.

      Cheers

  30. Mauricio says:

    My rig is with 3x rtx 3060 ( all memorys samsung 12053 ) using the same OC to all.

    40.07 MH     / Temp  66°  /Fan(locked in 70%)   69% / 115 W  / fan  70  /core 150  / memory 2600 /pl 115   < GIGABYTE>
    40.73 MH < ZOTAC> 
    40.32 MH < GALAX > ( free fan ) to me is the better card cuz it dont heat to much, the is working in 33% with temp 60º

     

  31. Volkan says:

    Hi miniZ Team,
    I have rig with 6pcs of RTX3090. Using MSI Afterburner to overclock on windows 10.
    I am switching from ETH mining to FLUX mining. It has been really very hard to make the overclock settings because each time with wrong settings system is freezing and I need to restart the PC. I have come out more or less a working condition but even now system is restarting or miniZ is turning off itself after some hours (up to 12 hours) of working. As I have 6 GPUs, I could not understand which GPU is crashing. Could not find any LOG flie etc. How can I find out the crashing one to underclock it a little bit. Do you have any suggestion about the way of overclocking ?
    I am familiar with core clock locking and voltage locking by MSI afterburner. I have been trying for 3 days to find out an optimized settings. It should not be soo hard. I may not know some properties of miniZ. I need your help.
    Thanks

    • miniZ says:

      Hi Volkan,
      Thank you for the feedback.

      miniZ doesn’t log the file by default. To have the miner log written to a file you need to add to the command line: --log, or --logfile [filename].

      The error you’re getting should be similar to this:
      [FATAL ] GPU[0]: CUDA error 77 ‘an illegal memory access was encountered’

      You can check the GPU number in the error message.

      Here you can find some OCs we tested for 192,7 (should be similar for other equihash algos like 125,4).
      Cheers

  32. Ieso Nagata says:

    AntiX linux 21 kernel 5.14.0-2-amd64 nvidia 495.44 RTX3060 v2 Asus dual 12GB (LHR)
    xorg.conf with cool-bits 31
    #nvidia-smi -i 0 -pl 115
    #nvidia-smi -i 0 -lgc 1550
    nvidia-settings MTR Offset 2200
    miniZ —tune=5
    RTX 3060 ` 100% [58°C/61%] 36.36(34.99)MH/s 107(106.3)W clk=1552MHz mclk=8400MHz MH/W=0.32

  33. Usman Khan says:

    GPU: EVGA SC2 (Micron Memory) Nvidia GeForce GTX 1080Ti

    OS: Windows 10 Pro x64

    GPU DRIVERS: 472.12 (Standard)

    MINIZ VERSION: 1.8y3

    ALGORITHM: Zelproof (125,4) (FLUX COIN)

    OVER CLOCK SETTINGS (MSI AFTERBURNER):-

    Power: 100%

    Core Clock: +120 (MHz)

    Memory Clock: +750 (MHz)

    Fan: 80%

    Temperature: 58′ C

    On Miniz :

    GTX 1080 Ti : 100% : [58′ C/81%] : 30.71 I/S : 60-61 Sol/S : 245 Watt : Sol/W=0.25

     

     

  34. Larry says:

    Is there a way to lock the core clock in miniz?

    Using absolute core clock in hiveos has no effect on what miniz ultimately uses for cc. Ie I could set acc at 1850 in hiveos but miniz is only using 1770

     

    • miniZ says:

      Hi Larry,
      Not at the moment, but we’re having a look at it.
      Maybe this will be possible in the next version.
      Cheers

  35. Salva says:

    MSI rtx2080 ventus v2 = 61solMSI Afterburner :Vcore locked to 706mV / GPU +170(1500) / Ram +950(7745) / PL : 111% / Watt : 140W / Efficiency : 0.44 / Fans : 90% / Temp : 58°

  36. mark says:

    This is an awesome miner. I have been running on Hive OS for the past few months. However I am testing on a linux environment and would like to know how to manual OC my card using the same values like I’m had in Hive OS.

    Hive OC settings:
    CLOCK=”180″
    MEM=”2000″
    FAN=”85″
    PLIMIT=”132″

     

    So when I ran the –ocX –write-config it creates a config file with the following values.

    "Devices": [
    {
    "name": "GeForce RTX 3060",
    "gpuid": 0,
    "mode": 17,
    "f11": 255,
    "oc": 255,
    "intensity": 0.0,
    "enabled": 1
    },

    I  am getting the same amount of sol/s and sometime less than in Hive OS and I’m also using more wattage. In Hive with my current setting I am using 110 WATT but now I am using 136 WATT . I would like to have the option to input my values for testing purposes.

    Can someone provide some insight here?

    Thanks

    • miniZ says:

      Hi mark,
      Thank you for using miniZ.
      The --ocX option is used to chose the best kernel mode for the GPU. It is not for OC tweaking.
      To OC the card you need to use Nvidia tools.

      If you run this in the shell, it should work (for GPU 0):
      nvidia-smi -i 0 -pm 1
      nvidia-smi -i 0 -pl 132
      nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[4]=+180
      nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[4]=+2000

      nvidia-smi:
      * -i To specify the GPU you want to modify.
      * -pl To specify max PL in watts.
      * -pm Persistence mode. Sets immediate effect, but doesn’t persist after reboot.

      nvidia-settings:
      * -a To assign…
      * [gpu:n] Defines the target (gpu) and target id (n is gpu number).
      * GPUGraphicsClockOffset and GPUMemoryTransferRateOffset are the attributes you want to modify.
      * number 4 here is the performance level, depending on the GPU there will be different PL available.

      From a quick read these seem OK:
      http://blog.zencoffee.org/2021/05/nvidia-overclocking-headless/
      https://www.ethmining.net/posts/overclocking-nvidia-cards-on-ubuntu-for-ethereum-mining/

      You may need to edit your /etc/X11/xorg.conf (Set Coolbits with caution. We use Coolbits=28)

      Hope this helps.
      Cheers

  37. Kiggi says:

    Currently messing around with a Asus Tuf Gaming 3060 12gb card, trying my hand with Beam. Is there any reference on what a 3060 should be getting Sol wise at all?? have been looking around but can’t find any details and i find it hard to believe around the 20sol’s mark is this cards maximum speed.

    • miniZ says:

      Hi Kiggi,

      After a quick test we got ~20 Sol/s @ 100W, with -150 on core and 2700 on mem clocks. (Linux)

      These settings are the ones we have for ETH. But, it seems quite good hashrate for Beam at 100W.

      However, it is likely that modifying these clock settings, and PL, may increase hashrate.

      Cheers

      ps: You can check https://whattomine.com/, by selecting one 3060. We find that sometimes the values are not up to date, in any case it’s another reference for you.

  38. rtx 2070 super says:

    RTX 2070 SUPER45.6 Sol/s , 125W , CLK=1295MHz , MCLK=6294 MHz , Sol/W=0.37.I’m using MSI afterburner with: Power limit=58 , CLK=+40 , MCLK=-500MHz.How are these measures compared to others with similar graphics cards. I tried different settings but couldn’t really improve the Sol/W. Any suggestions?

    • miniZ says:

      Hi rtx 2070 super,
      We do not have a 2070 SUPER, however it should be somewhat similar to the 2070.
      Are you mining FLUX? You could try the ECO OCs we share here https://miniz.ch/1254-2/
      On Windows you need to set half the value on memory clock. For example we set -260 on mem, which should be -130 on windows.
      Cheers

  39. SysLeg says:

    1080 TiTemp: 60Fans: 59%Hash rate: 55 Sol/sPower: 202WEfficiency: 0.27 Sol/Wclk: 1580 Mhzmclk: 5163 MHz

  40. Doctor Lizardo says:

    4 Jan. 2022 – HiveOS – MiniZ- Asus TUF 3080 Gaming OC (LHR) – Core 1800; Mem 0; PL 300W; Sol/s: 90.1- EVGA RTX 3070 FTW 3 (non-LHR) – Core 1800; Mem 0; PL 200W; Sol/s: 64.6

  41. Oky says:

    Any news or oc settings for rtx 3070?

  42. ebi says:

    os : hiveos

    driver: 460.91.03

    cc=55 mem=1600 pl=280 fan=80

    hash = 86 sol temp=55

    can you writhe –tune setting for 3080 lhr

    • miniZ says:

      Hi ebi,
      Thank you sharing your settings with everyone.
      Are you mining Flux?
      If you are mining Flux there is no need for tune settings.
      Cheers

  43. itchibahn says:

    I’ve been using GMiner for Flux mining, and decided to try out miniZ.  Didn’t find any difference between v 1.8y3 and 1.8y4rc2 on Sol/s.  MiniZ Sol/s is about 2% better than GMiner.  Also in miniZ, the memory clock doesn’t seem to make much difference, and core clock makes little difference.  In most cases, pushing the core clock above +100, crashes miniZ with “/hive/miner/miniz/h-run.sh: line 20:  4359 Segmentation fault     (core dumped)  ./miniZ $(< {MINER_NAME}.conf) –logfile $MINER_LOG_BASENAME.log –telemetry 127.0.0.1:${MINER_APT_PORT} –gpu-line”.

    How are some of you getting +50Sol/s for 1070 cards?

    0>GTX 1080 Ti 100% [58°C/80%] 29.07 I/s 57.72(57.85)Sol/s 194(203.1)W clk=1695MHz mclk=5005MHz Sol/W=0.28
    1>RTX 2080 SUPER
    100% [57°C/80%] 32.52 I/s 64.74(64.85)Sol/s 166(167.4)W clk=1830MHz mclk=7500MHz Sol/W=0.39
    2>RTX 2070 100% [47°C/70%] 24.59 I/s 49.41(48.79)Sol/s 127(127.9)W clk=1665MHz mclk=6801MHz Sol/W=0.38
    3>RTX 2080 SUPER
    100% [54°C/70%] 31.96 I/s 63.86(63.71)Sol/s 165(166.3)W clk=1725MHz mclk=7500MHz Sol/W=0.38
    4>RTX 2070 100% [53°C/70%] 24.63 I/s 48.81(49.00)Sol/s 124(126.6)W clk=1605MHz mclk=6801MHz Sol/W=0.39
    5>GTX 1070
    100% [48°C/70%] 17.90 I/s 35.65(35.60)Sol/s 114(115.8)W clk=1645MHz mclk=3802MHz Sol/W=0.31
    6>GTX 1080 Ti 96.6% [49°C/71%] 28.57 I/s 56.00(56.61)Sol/s 178(205.1)W clk=1657MHz mclk=5005MHz Sol/W=0.28
    7>RTX 2070 SUPER
    100% [48°C/70%] 27.93 I/s 55.36(55.63)Sol/s 128(128.6)W clk=1635MHz mclk=6801MHz Sol/W=0.43

    • itchibahn says:

      Geewiz, I had the text nicely formatted, but it displays scrambled.

    • miniZ says:

      Hi itchibahn,
      Thank you for your message.
      We were expecting a bit more than 2% 🙂
      You can try adding --ocX to your command line. Possibly it will not make much difference but it is worth to try in case there is a better kernel for some of the GPUs.
      Cheers

  44. Glenn Goodliffe says:

    GTX 980 averaging 36 sols, varies from 34 to 40 sols.
    GPU 1569 Mem 3850 1225mV temp 67 fan 48%

    I love miniZ!  Running it under NiceHash but miniZ keeps restarting…  Any suggestions?

    i7 5820K 4300GHz, 32GB DDR4 2666GHz ASUS x99 Aii mobo

  45. Ed says:

    How can I set power limit, fan, core clock, memory clock in the Miniz bat file in windows. I don’t like using MSI Afterburner. I just want to run the miniz bat file without using MSI Afterburner.

    • miniZ says:

      Hi Ed,
      Thank you for your message.
      At the moment this is not possible, but we’re having a look at it (for PL and clocks).
      Maybe this will be possible in the next version.
      Which GPUs are you using?
      Cheers

  46. PJ says:

    Hello – Piggybacking off of Ed’s post. It would be greatly appreciated if there’s a way to set the PL, Core Clock, and Memory. Here are the GPU’s I’m using:- EVGA 3080 TI FTW3 Ultra – EVGA 3070 TI FTW3 Ultra- EVGA 3060 TI XC

  47. AZ says:

    hi, i’m on windows, testing a zotac 3070 ti my console gives no feedback from card sensors whatsoeverclk = 1830 and mclk = 9501 no matter what i change on fireburnermining flux on minerpoor, averaging 75 mhs/day on 250 wgpuz averaging gpu temp at 63, mem temp at 83ps. screen attached to the same GPU

    • AZ says:

      miniz 1.8y4rc2

      • miniZ says:

        Hi AZ,
        Sorry, but we cannot fully understand the issue you are trying report.
        Could you explain it again?

        Do you mean that you have no report of temperature?
        Which driver version are you using? It could be an nvml issue.
        If you are mining Flux, you can try to update your driver to a more recent version.

        Let us know how it goes.
        Cheers

    Leave a Reply

    Your email address will not be published.

    I accept the Privacy Policy