Supported GPUs

* Updated  – Nov 2020 *

Compatible with:

  • Ampere: RTX 30XX series from v1.6w2
  • Turing: RTX 20XX and 16xx series from v1.0f
  • Pascal: GTX 10XX series, GT 1030, Titan Xp, Titan X…
  • Maxwell: Geforce 8XXM, 9XX …
  • Kepler: Geforce 6XX, 7XX, GTX Titan Black *

Although we did not test miniZ miner on all available GPUs, it is expected to run on all Maxwell, Pascal, Turing, Volta and Ampere architectures.

It should work on nvidia mining series: P106-100 and P104-100 GPUs. Previously, a miner asked about support for these cards. Support since December 2018.

If you are having trouble with any of these GPUs, do leave your comment below for support.

* We’ll try to include Kepler again, for some algos. Support was removed from version 1.5s.

Recent Posts

Categories

Search

Comments

  1. solotrade says:

    https://imgur.com/a/vHIWCSg
    hi as per picture show, this version even more faster crash compare with previous version.
    im using 4 gtx 1070 and 1 1070ti

    • miniZ says:

      Hi solotrade,
      we have been unable to reproduce this error, so it is hard for us to fix it. We are looking into it and we’ll provide a version for you to test soon.
      Can you tell us the minig pool you’re using?
      Thanks for the quick feedback!
      Cheers

      • solotrade says:

        seems like not pool related. im mining using 144_5 older version would crash a day plus, this new version take only 2 hours to crash

        i have gtx 1060 rig that is very stable to using ur miner

        • miniZ says:

          Hi solotrade,
          Only few people have experienced this crash error that we have not been able to reproduce.
          We updated miniZ to v1.0i+, with some modifications. Hopefully this one will fix this.
          If you can, drop us a message telling how it goes.
          Thank you!
          Cheers

  2. kaban says:

    gives an error of 1060 6 GB and 6 * 1050 ti

    • miniZ says:

      Hi kaban, could you give more details? What is the error? Which miniZ version are you using? Are you using Windows or Linux? Thank you. Cheers

      • kaban says:

        windows 7 64bit, miniZ v.1.0i, https://ibb.co/3cnvsPQ

        • miniZ says:

          Hi kaban, thanks for the screenshot.
          You need to increase pagefile. From what we could see you seem to have 2 1050Ti and 2 1060 6GB, is this correct?
          On Windows to use all memory of your GPUs you must increase the page file to have ~20GB. For miniZ it may work with 12 GB, but if you have enough space go with at least 20 GB.

          A suggestion for you to have a cleaner console: use the --nocolor option. You can try and use another console. A few months ago, we tried ConEmu terminal emulator and it worked fine. There are others available, which should also work OK.
          We mentioned this @ https://miniz.ch/usage/

          Cheers

  3. David says:

    I tried to change EWBF to minerZ on my rig
    But I see message: Number of CUDA devices found: 0
    No devices selected, exiting…

    My rig info:
    Win10_64bit
    2- GTX1080ti
    3- GTX1060

  4. solotrade says:

    hi, i am now back to report that miner is stable with 1070 and 1070ti
    7 days 19min at the moment i report!
    thanks
    using 1.0i +

  5. Ben says:

    Hi there, I have a rig with 6x 1080ti and 2x titan xp. With version v1.2m, the titan xp are getting 78 sol at 70% power, while the 1080ti are getting 88 sol at 70% power. Seems like the miniz miner is not optimized for the Tian xp?

    • miniZ says:

      Hi Ben,
      Thanks for letting us know. It is not optimized out of the box for that GPU.

      Probably you can get good hashrates by running miniZ with both --f11=1 and --mode=8 (or 7). We think this may improve performance.
      Feel free to try other values with --mode. You can try: 0,1,2,3,6,7, or 8. It will be interesting to know if any of these gives better performance.

      Let us know how it goes.
      Cheers

      • Ben says:

        Hi there, I tried mode 0 to 8, nothing has change for the titan xp. Still the same sol. But they do affect the performance for the 1080ti. However, my rig performed best without using –f11=1 and -mode. Hopefully on the next update you can make some progress on the titans =)

        • miniZ says:

          Hi Ben,
          thanks for the feedback.

          When you run miniZ without --mode, the console output starts with some information about the GPUs? Can you copy here that part?
          Something like this:
          Number of CUDA devices found: 4
          miniZ,144,5[3]: Selecting GPU#0 GeForce GT 710
          miniZ,144,5[7]: Selecting GPU#1 GeForce GTX 1050 Ti
          miniZ,144,5[1]: Selecting GPU#3 GeForce GTX 1070 Ti
          miniZ,144,5[3]: Selecting GPU#2 GeForce GTX 1050

          And, running miniZ with --mode=8 (for ex), could you paste here that same bit of information?

          Also, could you send us the output of running miniZ with just -ci? (Just run miniZ -ci)
          This may help us understand better the Titan xp 🙂
          Cheers

  6. Ben says:

    I had upgraded my video card driver from v397 to the latest v419, and running the cuda 10 version of the miniz v12m. This time, the –f11-1 and mode=8 is healping the titan xp to do 84 sol, which is on par with the other 1080ti. I have a feeling that the extra cuda cores the titan has over the 1080ti is not being use? here is the copy and paste from my computer.

    C:\miniz>miniz.exe –url [email protected]:4040 –log –gpu-line –extra –f11-1 –mode=8
    ************ miniZ v1.2m ************
    Number of CUDA devices found: 8
    miniZ,144,5[8]: Selecting GPU#0 GeForce GTX 1080 Ti
    miniZ,144,5[8]: Selecting GPU#4 TITAN Xp COLLECTORS EDITION
    miniZ,144,5[8]: Selecting GPU#5 GeForce GTX 1080 Ti
    miniZ,144,5[8]: Selecting GPU#6 TITAN Xp COLLECTORS EDITION
    miniZ,144,5[8]: Selecting GPU#7 GeForce GTX 1080 Ti
    miniZ,144,5[8]: Selecting GPU#2 GeForce GTX 1080 Ti
    miniZ,144,5[8]: Selecting GPU#3 GeForce GTX 1080 Ti
    miniZ,144,5[8]: Selecting GPU#1 GeForce GTX 1080 Ti
    Algo: EQ[144,5]
    Pool#0: user[GUPJk3iHbQE3gtgcdww9Q1Bh7Chh3U6mJp.cuda8]
    server[us-btg.2miners.com] port[4040] ssl[no] pers[BgoldPoW]
    Telemetry: [http://localhost:20000]
    Temp. limit: [90°C]
    [ 0d 0h 4m01s] S: 37/0 688(688.5)Sol/s 1433(1436.5)W [us-btg.2miners.com] (92.6%) (7.4%)
    0>GTX 1080 Ti 100% [36°C/100%] 45.83 I/s 92.1(92.2)Sol/s 199(198.0)W clk=1746MHz mclk=5499MHz Sol/W=0.47
    1>GTX 1080 Ti
    100% [41°C/100%] 41.85 I/s 84.0(84.0)Sol/s 178(174.6)W clk=1556MHz mclk=5499MHz Sol/W=0.48
    2>GTX 1080 Ti 100% [37°C/100%] 41.17 I/s 83.0(83.0)Sol/s 173(173.7)W clk=1544MHz mclk=5499MHz Sol/W=0.48
    3>GTX 1080 Ti
    100% [28°C/100%] 44.09 I/s 88.6(88.5)Sol/s 176(172.7)W clk=1632MHz mclk=5499MHz Sol/W=0.51
    4>TITAN Xp COLLECTORS EDITION 100% [46°C/100%] 42.34 I/s 84.4(84.4)Sol/s 173(175.9)W clk=1480MHz mclk=5999MHz Sol/W=0.48
    5>GTX 1080 Ti
    100% [45°C/100%] 45.44 I/s 90.4(90.3)Sol/s 194(194.6)W clk=1695MHz mclk=5499MHz Sol/W=0.46
    6>TITAN Xp COLLECTORS EDITION 100% [55°C/100%] 42.10 I/s 84.6(84.6)Sol/s 170(173.5)W clk=1468MHz mclk=5999MHz Sol/W=0.49
    7>GTX 1080 Ti
    100% [42°C/100%] 41.84 I/s 83.5(83.4)Sol/s 170(173.7)W clk=1569MHz mclk=5499MHz Sol/W=0.48

    C:\miniz>miniz.exe –url [email protected]:4040 –log –gpu-line –extra
    ************ miniZ v1.2m ************
    Number of CUDA devices found: 8
    miniZ,144,5[8]: Selecting GPU#0 GeForce GTX 1080 Ti
    miniZ,144,5[1]: Selecting GPU#6 TITAN Xp COLLECTORS EDITION
    miniZ,144,5[8]: Selecting GPU#5 GeForce GTX 1080 Ti
    miniZ,144,5[8]: Selecting GPU#7 GeForce GTX 1080 Ti
    miniZ,144,5[1]: Selecting GPU#4 TITAN Xp COLLECTORS EDITION
    miniZ,144,5[8]: Selecting GPU#3 GeForce GTX 1080 Ti
    miniZ,144,5[8]: Selecting GPU#2 GeForce GTX 1080 Ti
    miniZ,144,5[8]: Selecting GPU#1 GeForce GTX 1080 Ti
    Algo: EQ[144,5]
    Pool#0: user[GUPJk3iHbQE3gtgcdww9Q1Bh7Chh3U6mJp.cuda8]
    server[us-btg.2miners.com] port[4040] ssl[no] pers[BgoldPoW]
    Telemetry: [http://localhost:20000]
    Temp. limit: [90°C]
    [ 0d 0h 3m55s] S: 23/0 679(678.2)Sol/s 1449(1424.0)W [us-btg.2miners.com] (92.5%) (7.5%)
    0>GTX 1080 Ti 100% [38°C/100%] 46.02 I/s 91.7(91.7)Sol/s 200(192.9)W clk=1733MHz mclk=5499MHz Sol/W=0.48
    1>GTX 1080 Ti
    100% [41°C/100%] 41.92 I/s 83.6(83.7)Sol/s 176(168.1)W clk=1594MHz mclk=5499MHz Sol/W=0.50
    2>GTX 1080 Ti 100% [37°C/100%] 41.34 I/s 83.0(82.9)Sol/s 178(175.1)W clk=1531MHz mclk=5499MHz Sol/W=0.47
    3>GTX 1080 Ti
    100% [28°C/100%] 44.23 I/s 87.9(87.9)Sol/s 178(173.8)W clk=1632MHz mclk=5499MHz Sol/W=0.51
    4>TITAN Xp COLLECTORS EDITION 100% [48°C/100%] 40.35 I/s 80.8(80.8)Sol/s 170(174.3)W clk=1582MHz mclk=5999MHz Sol/W=0.46
    5>GTX 1080 Ti
    100% [46°C/100%] 45.58 I/s 90.8(90.8)Sol/s 198(193.4)W clk=1695MHz mclk=5499MHz Sol/W=0.47
    6>TITAN Xp COLLECTORS EDITION 100% [55°C/100%] 40.05 I/s 79.5(79.4)Sol/s 174(171.6)W clk=1569MHz mclk=5999MHz Sol/W=0.46
    7>GTX 1080 Ti
    100% [43°C/100%] 41.97 I/s 84.1(84.1)Sol/s 176(174.9)W clk=1556MHz mclk=5499MHz Sol/W=0.48

    C:\miniz>miniz.exe –ci
    ************ miniZ v1.2m ************
    Number of CUDA devices found: 8
    miniZ,144,5[8]: Selecting GPU#0 GeForce GTX 1080 Ti
    miniZ,144,5[8]: Selecting GPU#1 GeForce GTX 1080 Ti
    miniZ,144,5[8]: Selecting GPU#2 GeForce GTX 1080 Ti
    miniZ,144,5[8]: Selecting GPU#3 GeForce GTX 1080 Ti
    miniZ,144,5[1]: Selecting GPU#4 TITAN Xp COLLECTORS EDITION
    miniZ,144,5[8]: Selecting GPU#5 GeForce GTX 1080 Ti
    miniZ,144,5[1]: Selecting GPU#6 TITAN Xp COLLECTORS EDITION
    Algo: EQ[144,5]
    miniZ,144,5[8]: Selecting GPU#7 GeForce GTX 1080 Ti
    [WARNING] No mining pool specified!
    Telemetry: [http://localhost:20000]
    Temp. limit: [90°C]
    [ 0d 0h 1m31s] 631(631.1)Sol/s 416(793.4)W
    0>GTX 1080 Ti 100% [28°C/100%] 46.33 I/s 90.5(90.5)Sol/s 53(107.0)W clk=139MHz mclk=405MHz Sol/W=0.85
    1>GTX 1080 Ti
    100% [25°C/100%] 42.07 I/s 83.8(83.8)Sol/s 51( 99.4)W clk=139MHz mclk=405MHz Sol/W=0.84
    2>GTX 1080 Ti 100% [19°C/100%] 41.28 I/s 84.6(84.6)Sol/s 51( 99.4)W clk=139MHz mclk=405MHz Sol/W=0.85
    3>GTX 1080 Ti
    100% [18°C/100%] 43.98 I/s 88.2(88.2)Sol/s 50( 97.9)W clk=139MHz mclk=405MHz Sol/W=0.90
    4>TITAN Xp COLLECTORS EDITION 100% [29°C/100%] 40.54 I/s 80.8(80.8)Sol/s 57(103.6)W clk=139MHz mclk=405MHz Sol/W=0.78
    5>GTX 1080 Ti
    100% [34°C/100%] 45.96 I/s 90.0(90.0)Sol/s 50(100.0)W clk=139MHz mclk=405MHz Sol/W=0.90
    6>TITAN Xp COLLECTORS EDITION 100% [26°C/100%] 40.52 I/s 78.7(78.7)Sol/s 55(100.0)W clk=139MHz mclk=405MHz Sol/W=0.79
    7>GTX 1080 Ti
    100% [21°C/100%] 42.61 I/s 84.9(84.9)Sol/s 50( 86.1)W clk=139MHz mclk=405MHz Sol/W=0.99
    [WARNING] Cannot connect to any mining pool!!!

    • miniZ says:

      Hi Ben,
      thanks for the information.

      We noticed that you have a typo on your command line: --f11-1. It should be --f11=1. --f11-1 is ignored by miniZ.
      It might worth to check it out. We suspect that, besides --mode-8, using --f11=1 might be beneficial for the Titan XP.

      Also, C:\miniz>miniz.exe --ci will just start the miner.
      Could you try again miniZ.exe -ci (one dash) and post it here? This will not start the miner, just lists GPUs information.

      We’ll do our best in trying to get the best performance out of Titan XP 🙂
      Cheers

      • Ben says:

        C:\miniz>miniz.exe –url [email protected]:4040 –log –gpu-line –extra –f11=1 –mode=8
        ************ miniZ v1.2m ************
        Number of CUDA devices found: 8
        miniZ,144,5[8]: Selecting GPU#0 GeForce GTX 1080 Ti
        miniZ,144,5[8]: Selecting GPU#7 GeForce GTX 1080 Ti
        miniZ,144,5[8]: Selecting GPU#6 TITAN Xp COLLECTORS EDITION
        miniZ,144,5[8]: Selecting GPU#5 GeForce GTX 1080 Ti
        miniZ,144,5[8]: Selecting GPU#4 TITAN Xp COLLECTORS EDITION
        miniZ,144,5[8]: Selecting GPU#3 GeForce GTX 1080 Ti
        miniZ,144,5[8]: Selecting GPU#2 GeForce GTX 1080 Ti
        miniZ,144,5[8]: Selecting GPU#1 GeForce GTX 1080 Ti
        Algo: EQ[144,5]
        Pool#0: user[GUPJk3iHbQE3gtgcdww9Q1Bh7Chh3U6mJp.cuda8]
        server[us-btg.2miners.com] port[4040] ssl[no] pers[BgoldPoW]
        Telemetry: [http://localhost:20000]
        Temp. limit: [90°C]
        [ 0d 0h 3m45s] S: 31/0 680(679.5)Sol/s 1427(1421.9)W [us-btg.2miners.com] (92.9%) (7.1%)
        0>GTX 1080 Ti 100% [39°C/100%] 45.71 I/s 92.6(92.5)Sol/s 195(194.3)W clk=1721MHz mclk=5499MHz Sol/W=0.48
        1>GTX 1080 Ti
        100% [44°C/100%] 41.74 I/s 84.3(84.3)Sol/s 174(172.0)W clk=1544MHz mclk=5499MHz Sol/W=0.49
        2>GTX 1080 Ti 100% [40°C/100%] 41.09 I/s 81.9(82.0)Sol/s 174(172.6)W clk=1531MHz mclk=5499MHz Sol/W=0.47
        3>GTX 1080 Ti
        100% [32°C/100%] 43.68 I/s 86.6(86.6)Sol/s 164(169.9)W clk=1632MHz mclk=5499MHz Sol/W=0.51
        4>TITAN Xp COLLECTORS EDITION 100% [51°C/100%] 41.90 I/s 82.9(82.8)Sol/s 170(173.4)W clk=1366MHz mclk=5999MHz Sol/W=0.48
        5>GTX 1080 Ti
        100% [48°C/100%] 45.32 I/s 90.7(90.7)Sol/s 198(194.8)W clk=1695MHz mclk=5499MHz Sol/W=0.47
        6>TITAN Xp COLLECTORS EDITION 100% [58°C/100%] 41.08 I/s 82.3(82.2)Sol/s 178(174.9)W clk=1455MHz mclk=5999MHz Sol/W=0.47
        7>GTX 1080 Ti
        100% [46°C/100%] 41.51 I/s 82.2(82.2)Sol/s 174(170.1)W clk=1569MHz mclk=5499MHz Sol/W=0.48

        C:\miniz>miniz.exe -ci
        ************ miniZ v1.2m ************
        Number of CUDA devices found: 8
        #0 GeForce GTX 1080 Ti | SM version: 6.1 | SM count: 28 | Memory: 9.09GB
        #1 GeForce GTX 1080 Ti | SM version: 6.1 | SM count: 28 | Memory: 9.09GB
        #2 GeForce GTX 1080 Ti | SM version: 6.1 | SM count: 28 | Memory: 9.09GB
        #3 GeForce GTX 1080 Ti | SM version: 6.1 | SM count: 28 | Memory: 9.09GB
        #4 TITAN Xp COLLECTORS EDITION | SM version: 6.1 | SM count: 30 | Memory: 9.93GB
        #5 GeForce GTX 1080 Ti | SM version: 6.1 | SM count: 28 | Memory: 9.09GB
        #6 TITAN Xp COLLECTORS EDITION | SM version: 6.1 | SM count: 30 | Memory: 9.93GB
        #7 GeForce GTX 1080 Ti | SM version: 6.1 | SM count: 28 | Memory: 9.09GB

        • Ben says:

          C:\miniz>miniz.exe –url [email protected]:4040 –log –gpu-line –extra –f11=1
          ************ miniZ v1.2m ************
          Number of CUDA devices found: 8
          miniZ,144,5[1]: Selecting GPU#4 TITAN Xp COLLECTORS EDITION
          miniZ,144,5[8]: Selecting GPU#5 GeForce GTX 1080 Ti
          miniZ,144,5[1]: Selecting GPU#6 TITAN Xp COLLECTORS EDITION
          miniZ,144,5[8]: Selecting GPU#0 GeForce GTX 1080 Ti
          miniZ,144,5[8]: Selecting GPU#7 GeForce GTX 1080 Ti
          miniZ,144,5[8]: Selecting GPU#3 GeForce GTX 1080 Ti
          miniZ,144,5[8]: Selecting GPU#1 GeForce GTX 1080 Ti
          miniZ,144,5[8]: Selecting GPU#2 GeForce GTX 1080 Ti
          Algo: EQ[144,5]
          Pool#0: user[GUPJk3iHbQE3gtgcdww9Q1Bh7Chh3U6mJp.cuda8]
          server[us-btg.2miners.com] port[4040] ssl[no] pers[BgoldPoW]
          Telemetry: [http://localhost:20000]
          Temp. limit: [90°C]
          [ 0d 0h 3m17s] S: 23/0 669(668.6)Sol/s 1443(1430.0)W [us-btg.2miners.com] (92.4%) (7.6%)
          0>GTX 1080 Ti 100% [45°C/100%]*45.81 I/s 91.1(91.1)Sol/s 196(196.8)W clk=1721MHz mclk=5499MHz Sol/W=0.46
          1>GTX 1080 Ti
          100% [43°C/100%] 41.86 I/s 83.2(83.2)Sol/s 172(171.8)W clk=1544MHz mclk=5499MHz Sol/W=0.48
          2>GTX 1080 Ti 100% [38°C/100%] 41.30 I/s 82.7(82.7)Sol/s 178(173.1)W clk=1531MHz mclk=5499MHz Sol/W=0.48
          3>GTX 1080 Ti
          100% [30°C/100%] 44.00 I/s 87.9(87.9)Sol/s 174(172.3)W clk=1620MHz mclk=5499MHz Sol/W=0.51
          4>TITAN Xp COLLECTORS EDITION 100% [50°C/100%] 38.39 I/s 75.8(75.8)Sol/s 177(174.4)W clk=1556MHz mclk=5999MHz Sol/W=0.43
          5>GTX 1080 Ti
          100% [50°C/100%] 45.57 I/s 90.8(90.8)Sol/s 193(192.9)W clk=1683MHz mclk=5499MHz Sol/W=0.47
          6>TITAN Xp COLLECTORS EDITION 100% [56°C/100%] 38.21 I/s 76.9(76.9)Sol/s 178(172.5)W clk=1544MHz mclk=5999MHz Sol/W=0.45
          7>GTX 1080 Ti
          100% [43°C/100%] 41.90 I/s 83.2(83.2)Sol/s 176(176.1)W clk=1544MHz mclk=5499MHz Sol/W=0.47

          • Ben says:

            Hi there, I figure that the titans are running at lower clock speeds when using –f11=1 –mode=8, so I realized the 70% power might not be the most optimal power to feed the card to it best perfomance/w. Hence, I increase the power to 82%, and here you go.

            [ 0d 0h 9m01s] S: 39/0 704(702.6)Sol/s 1466(1475.3)W [us-btg.2miners.com] (96.8%) (3.2%)
            0>GTX 1080 Ti 100% [43°C/100%] 45.88 I/s 90.4(90.8)Sol/s 181(191.1)W clk=1759MHz mclk=5499MHz Sol/W=0.48
            1>GTX 1080 Ti
            100% [44°C/100%] 41.72 I/s 84.3(83.8)Sol/s 168(171.7)W clk=1556MHz mclk=5499MHz Sol/W=0.49
            2>GTX 1080 Ti 100% [40°C/100%] 41.14 I/s 81.3(81.6)Sol/s 178(173.4)W clk=1531MHz mclk=5499MHz Sol/W=0.47
            3>GTX 1080 Ti
            100% [31°C/100%] 43.62 I/s 87.7(87.4)Sol/s 167(172.2)W clk=1620MHz mclk=5499MHz Sol/W=0.51
            4>TITAN Xp COLLECTORS EDITION 100% [55°C/100%] 47.05 I/s 93.7(93.3)Sol/s 194(200.9)W clk=1645MHz mclk=5999MHz Sol/W=0.46
            5>GTX 1080 Ti
            100% [48°C/100%] 45.42 I/s 91.1(91.0)Sol/s 192(191.1)W clk=1683MHz mclk=5499MHz Sol/W=0.48
            6>TITAN Xp COLLECTORS EDITION 100% [64°C/100%] 46.49 I/s 93.2(92.2)Sol/s 214(203.0)W clk=1657MHz mclk=5999MHz Sol/W=0.45
            7>GTX 1080 Ti
            100% [44°C/100%] 41.51 I/s 83.4(83.4)Sol/s 173(172.0)W clk=1544MHz mclk=5499MHz Sol/W=0.49

            Thank you very much for the support! I will play with some other settings to see if I can get more sol from this bad boy.

            • miniZ says:

              Hi Ben,
              Thank you for reporting all these details about the Titan Xp.
              On power saving it may be worth trying --f11=0 --mode=7 (combined).
              If you manage to find something interesting do let us know. It would be much appreciated. 🙂
              Cheers

  7. greg says:

    I’m trying to get 2 Titan Blacks to hash on the BEAM network. I can get a bit from lolMiner but I am getting 0 sols on miniZ. Any suggestions? I’m running windows 10.

    • miniZ says:

      Hi greg,
      could you paste here the output of running miniZ.exe -ci?
      We also suggest you to try miniZ CUDA 8 version and let us know if it runs better.
      Thanks.
      Cheers

      • greg says:

        Number of CUDA devices found: 4
        #0 GeForce GTX 1080 Ti | SM version: 6.1 | SM count: 28 | Memory: 9.10GB
        #1 GeForce GTX 1080 | SM version: 6.1 | SM count: 20 | Memory: 6.60GB
        #2 GeForce GTX TITAN Black | SM version: 3.5 | SM count: 15 | Memory: 4.99GB
        #3 GeForce GTX TITAN Black | SM version: 3.5 | SM count: 15 | Memory: 4.99GB

        • miniZ says:

          Hi greg,
          thanks a lot for the information.
          For now your Titan Black should be able to mine Beam with miniZ version v1.3n5, CUDA 8. We will fix this for the next version.
          If it works, could you let us know what the hashrate is?
          You can also try and add --mode2 n --mode3 n option with n=1,2,4,6,7,9, and see which value mode give the best hashrate. This will apply mode n to GPU2 and GPU3 (2 and 3 refer to your Titan Black, we will document this better in our website soon).
          Could you also let us know which mode value is the best for the Titan? This can help us optimize miniZ for that GPU.
          Cheers

          • greg says:

            Thank you for your time miniZ,
            When I try using v1.3n5, CUDA 8 with the Titan Blacks I get this message:

            [FATAL ] GPU[3]: CUDA error 6 ‘the launch timed out and was terminated’ in line 1129
            [INFO ]beam-us.leafpool.com Disconnecting
            [INFO ]beam-us.leafpool.com Stopping miner
            [FATAL ] GPU[1]: CUDA error 6 ‘the launch timed out and was terminated’ in line 1129
            [FATAL ] GPU[2]: CUDA error 6 ‘the launch timed out and was terminated’ in line 1129
            [FATAL ] GPU[0]: CUDA error 6 ‘the launch timed out and was terminated’ in line 1129

            If I disconnect them from the motherboard the other 2 cards will mine as normal.

            • miniZ says:

              Hi greg,
              it is hard for us to get that error. If you run miniZ with just one Titan Black, or just one 1080, does it work?
              You can select GPU with -cd option. (Leave the GPUs on board and select with -cd option).
              Could you paste here the miniZ output, from the beginning (detects GPUs) until it exits?
              Thanks!
              Cheers

              • greg says:

                Thank you miniZ,

                miniZ v1.3n5 works with my 1080 and 1080ti and hashes normally
                with miniZ v1.4o I do not get the CUDA error 6 on the Titan Black, however I get a hashrate of 0sol/s

                the Titan Blacks will mine on lolminer at around 2 sol/s

                ************ miniZ v1.3n5 ************
                miniZ,150,5[8:1:00]: Selecting GPU#3[0] GeForce GTX TITAN Black
                Algo: EQ[150,5]
                Pool#0: user[3165ae66e8ba520b71688d90d07b4d98bacc1125a4f1c632baedec8a637b0e42b0e.11]
                server[beam-us.leafpool.com] port[3333] ssl[yes] pers[Beam-PoW]
                Telemetry: [http://localhost:20000]
                Temp. limit: [90°C]
                [FATAL ] GPU[3]: CUDA error 6 ‘the launch timed out and was terminated’ in line 1129
                [INFO ]beam-us.leafpool.com Disconnecting
                [INFO ]beam-us.leafpool.com Stopping miner

                C:\Users\g\Desktop\miniZ_v1.3n5_win-x64>timeout /t 5

                Waiting for 4 seconds, press a key to continue …

              • greg says:

                Sorry, here is the output for one of my other cards.

                ************ miniZ v1.3n5 ************
                miniZ,150,5[8:1:00]: Selecting GPU#0[0] GeForce GTX 1080 Ti
                Algo: EQ[150,5]
                Pool#0: user[3165ae66e8ba520b71688d90d07b4d98bacc1125a4f1c632baedec8a637b0e42b0e.11]
                server[beam-us.leafpool.com] port[3333] ssl[yes] pers[Beam-PoW]
                Telemetry: [http://localhost:20000]
                Temp. limit: [90°C]
                [ 0d 0h 0m09s] 0>GTX 1080 Ti ` 100% [49°C/84%]*17.66 I/s 35.5(35.5)Sol/s 171(171.4)W clk=1518MHz mclk=5805MHz Sol/W=0.21

                • miniZ says:

                  Hi Greg,
                  Thanks a lot for all the information!
                  We will investigate this further and try to solve it for the next version.
                  Cheers

  8. jeronymod says:

    May I ask why miniZ consumes a significant amount (17%) of CPU power? Isn’t miniZ a GPU-only miner? I’m trying to run xmrig for CPU-only mining (Ryzen 3600) and I get lower CPU hashrates while miniZ is running.

    Just tried gminer and it consumes zero CPU! How come? I’d love to use miniZ since it’s a bit more efficient, but you need to do something about people who want to use their CPU for other mining apps/algos.

    • miniZ says:

      Hi jeronymod,
      thank you for letting us know!

      We would like to solve this. Could you give us a few more details?

      1. What miniZ version are you using?
      2. What algo are you mining with miniZ?
      3. Do you know if it happens with other algos?
      4. Could you paste here the output of running miniZ with -ci option?
      miniZ.exe -ci

      We are currently working on a new version and with your feedback maybe we can include a fix for your issue.
      Cheers

      • jeronymod says:

        1. v1.5s CUDA 10
        2. –par=150,5,3 –pers=Beam-PoW
        3. Haven’t tried any other GPU algos, I’m currently mining Beam.
        4. ************ miniZ v1.5s ************
        Number of CUDA[10.0] devices found: 2
        #0 GeForce RTX 2060 SUPER | SM version: 7.5 | SM count: 34 | Memory: 6.58GB | BusID: 0000:27:00.0
        #1 GeForce GTX 1660 SUPER | SM version: 7.5 | SM count: 22 | Memory: 4.90GB | BusID: 0000:28:00.0

        • miniZ says:

          Hi jeronymod,
          thanks a lot for the information!

          We managed to reproduce your conditions and found the issue on Windows. (It does not happen on Linux.)
          It is also specific to BeamHashII.

          We fixed this already and it should work fine in the next version.
          Also, you can expect speed improvements for your GPUs, specially for the 1660 🙂

          Thanks again for reporting this!
          Cheers

          • jeronymod says:

            When should we expect the new version?

            • miniZ says:

              Hi jeronymod,
              the new version is almost ready but, since we did a lot of changes, it needs to be well tested. That’s why it’s taking longer.
              Everything going well, we expect to release the new version on Sunday.
              Cheers

  9. matthew wong says:

    hi im totally newbie on this…

    im using miniZ 1.5s.. GeForce GTX 1050 Ti …is there any problem with my parameters??any advice to improve the performance??

    https://imgur.com/I711BUw
    https://imgur.com/unGRuE9

    • miniZ says:

      Hi matthew wong,

      Thank you for using miniZ.

      Your values for the 1050 Ti, mining Aion, are not substantially different from ours (see: https://miniz.ch/2109-2/).

      However, you may be able to improve the speed a little if you:
      1. Lower the temperature (increase fan speed for example);
      2. Increase the clocks (overclocking GPU). For this you can use for example MSI Afterburner software.

      In the tables (see: https://miniz.ch/2109-2/) you can see some OC values we tried:

      1. “Overclock” (right side in Table 1) sets power limit to max allowed.
      Usually this is not the most efficient (Sol/W) since is draws more energy, even though it tends to be the fastest. Expect the temperature to rise too.

      2. “Eco” (left side on Table 2) sets power limit to minimum allowed (except for one or two cases).
      Usually the most efficient but also the slowest.

      3. “Eco70” (right side on Table 2) sets the power limit to 70% of the default power for the GPU.
      Since 70% is a setting that many like to use we add it here. Tends to be a good compromise between power and speed.

      You can try it out and set OC that best suits you.
      Best to start with lower OC values, increase them slowly and select what seem to be the most stable for your set up. These can vary from one rig to another.

      Lets us know if this was usefull.
      Feel free to contact if you need further help.

      Cheers

      Note: Memory clock in MSI Afterburner should be half of the indicated values, in the Tables. Ex. mem=+200 in the table, means mem=+100 in MSI Afterburner

  10. alex says:

    Hello! I have a low hashrate on RTX 2080 Super, it show 2-3 Sols (instead 50 Sols) on Beam, could you check?
    Also have a trouble with Zhash algo show me error “illegal memory error”, Could you check also?
    MiniZ 1.5t (mining on Nicehash pool)

    • miniZ says:

      Hi alex,

      The error you get in Zhash can be related to your OC settings. Could you tweek them and check if the error persists?

      Regarding the 2080 Super, could you send us some more information:
      1. What OS are you using?
      2. Your command line,
      3. The very begining (where it has information about GPUs,…) of miniZ console output, and including a little of mining results (with I/s, Sol/s…).

      Thank you for the feedback.
      Cheers

      • Alex says:

        1) Win 10 with latest updates. Nvidia drivers 441.41. miniz 1.5t
        2) I used Nicehash client and CMD used default
        3) Sorry, 2nd card RTX2070 Super show lower hashrate on beamv2:

        0>RTX 2080 SUPER 100% [54шC/69%] 33.33 I/s 67.0(67.0)Sol/s 200(199.5)W clk=1995MHz mclk=8000MHz Sol/W=0.34
        1>RTX 2070 SUPER
        100% [33шC/38%] 3.27 I/s 7.4( 7.4)Sol/s 46( 46.5)W clk=1995MHz mclk=7250MHz Sol/W=0.16
        2>RTX 2070 SUPER 100% [52шC/68%] 30.51 I/s 61.6(61.6)Sol/s 194(193.4)W clk=1980MHz mclk=7250MHz Sol/W=0.32
        3>GTX 1080 Ti
        100% [46шC/58%] 28.56 I/s 57.2(57.2)Sol/s 206(200.0)W clk=1949MHz mclk=5760MHz Sol/W=0.29

        • miniZ says:

          Hi Alex,

          thank you for the information.

          It is strange that only one 2070 is getting such low hashrate.

          We also notice that the GPU is basically idle, could it be crashed? (Are values frozen or decreasing if you let it run for a while?)
          It looks that you are overclocking your GPUs, and that 2070 may require other values.

          We suggest you to tweak the OCs a little and give it another try. We share some of our tests here https://miniz.ch/15053-2/.

          Or/and…have you tried to mine with only that 2070, and see if it works?

          If these suggestions do not help, could you paste here the very start of miniZ console output?
          Something like this:
          miniZ[1:1:00:6787]: Selecting GPU#0[0] GeForce GTX 1070
          miniZ[1:1:00:6787]: Selecting GPU#1[1] GeForce GTX 1070

          Cheers

  11. Alex says:

    Beam I fixed, it was something with OC settings on this card.
    I restored OC settings to default and this videocard working fine.

    But on Zhash (on Nicehash) miner always crashed with this error:
    Telemetry: [http://localhost:4005]
    Logging:: file[miniZ.log] period[10] delay[0]
    Temp. limit: [90шC]
    miniZ[6:2:00:6703]: Selecting GPU#2[1] GeForce RTX 2070 SUPER
    miniZ[6:2:00:6703]: Selecting GPU#3[2] GeForce RTX 2070 SUPER
    miniZ[6:2:00:6687]: Selecting GPU#1[0] GeForce RTX 2080 SUPER
    miniZ[8:1:00:9316]: Selecting GPU#0[3] GeForce GTX 1080 Ti
    [FATAL ] GPU[0]: CUDA error 77 ‘an illegal memory access was encountered’ in line 607
    [INFO ] Disconnecting from zhash.eu.nicehash.com
    [FATAL ] GPU[2]: CUDA error 77 ‘an illegal memory access was encountered’ in line 607
    [FATAL ] GPU[1]: CUDA error 77 ‘an illegal memory access was encountered’ in line 607
    [FATAL ] GPU[3]: CUDA error 77 ‘an illegal memory access was encountered’ in line 607
    [INFO ] Miner monitor exited.
    [INFO ] Exited main loop

    • miniZ says:

      Hi Alex,
      nice that it worked for Beam 🙂

      The error you get for ZHash also looks OC related. It can be that it’s just one of them that is causing this.
      If you run them all with stock settings does this also happen?

      The best would be to test them separately.
      You can try and tweak just one and see if is becomes stable…if so we suggest starting with the 2080 SUPER.

      Let us know if it works.
      Cheers

  12. Grillsum says:

    C:\Users\Grill\Desktop\miner\miniZ>.\miniZ.exe –url=ssl://[email protected]:3333 –par=beam3 –pers=Beam-PoW -i=100
    ************ miniZ v1.6w2 ************
    Number of CUDA[11.1] devices found: 1
    Algo: EQ[beam3]
    Pool#0: user[address]
    server[beam-asia.leafpool.com] port[3333] ssl[yes] pers[Beam-PoW]
    Telemetry: [http://localhost:20000]
    Temp. limit: [90°C]
    miniZ[13:0:100:9105]: Selecting GPU#0[0] GeForce RTX 3080
    [ 0d 0h 0m04s] 0>RTX 3080 100% [40°C/100%] 0.97 I/s 1.9(1.9)Sol/s 65( 64.8)W clk=1995MHz mclk=10457MHz Sol/W=0.03
    [ 0d 0h 0m10s] 0>RTX 3080
    100% [42°C/100%] 0.98 I/s 1.9(1.9)Sol/s 146(146.1)W clk=1995MHz mclk=10457MHz Sol/W=0.01
    [ 0d 0h 0m20s] 0>RTX 3080 100% [43°C/100%] 0.98 I/s 2.0(2.0)Sol/s 150(149.5)W clk=1995MHz mclk=10457MHz Sol/W=0.01
    [ 0d 0h 0m30s] 0>RTX 3080
    100% [43°C/100%] 0.97 I/s 1.9(1.9)Sol/s 151(150.6)W clk=1980MHz mclk=10457MHz Sol/W=0.01

    Tried using a 3080 to mine beam (144,5s) but for some reason, it does not seem to be pushing the performance of the card. Temps are staying at idle and performance is capped at 2 Sol/s

    • miniZ says:

      Hi Grillsum,
      It looks that miniZ did not load the best kernel for the RTX 3080.

      Please try running with --mode=6.

      Also, -i doesn’t seem to be doing anything there. Maybe is best to try running without -i.

      Thank you for the feedback. We will try to further optimise Beam for your GPU.

      Let us know if this helped solving the issue.
      Cheers

      • Grillsum says:

        C:\Users\grill\Desktop\miner\miniZ>.\miniZ.exe –url=ssl://[email protected]:333 –par=beam3 –pers=auto –mode=6
        ************ miniZ v1.6w2 ************

        Number of CUDA[11.1] devices found: 1
        Algo: EQ[beam3]
        Pool#0: user[address]
        server[beam-asia.leafpool.com] port[3333] ssl[yes] pers[Beam-PoW]
        Telemetry: [http://localhost:20000]
        Temp. limit: [90°C]
        miniZ[06:0:00:9105]: Selecting GPU#0[0] GeForce RTX 3080

        [ 0d 0h 0m04s] 0>RTX 3080 100% [43°C/100%] 0.93 I/s 1.9(1.9)Sol/s 68( 67.8)W clk=1995MHz mclk=10555MHz Sol/W=0.03
        [ 0d 0h 0m10s] 0>RTX 3080
        100% [45°C/100%] 0.93 I/s 1.9(1.9)Sol/s 157(156.7)W clk=1995MHz mclk=10555MHz Sol/W=0.01
        [ 0d 0h 0m20s] 0>RTX 3080 ` 100% [46°C/100%] 0.93 I/s 1.9(1.9)Sol/s 161(161.0)W clk=1995MHz mclk=10555MHz Sol/W=0.01

        Ye probably an optimisation thingo but all g 😀 i can use my other cards in the mean time

        • miniZ says:

          Hi Grillsum,

          You can find miniZ v1.6w4 version (Beta version) here: https://miniz.ch/download-beta/ with a fix for the RTX 30XX series.

          Our tests were OK, but it may require a bit more testing. So, all the feedback is welcome. 🙂

          Hope that all goes well!
          Cheers

          • Grillsum says:

            [ 0d 0h 2m10s] 0>RTX 3080 100% [63°C/92%] 28.01 I/s 54.0(54.0)Sol/s 348(348.6)W clk=1935MHz mclk=10251MHz Sol/W=0.15
            [ 0d 0h 2m20s] 0>RTX 3080
            100% [64°C/95%] 27.98 I/s 54.3(54.3)Sol/s 348(348.5)W clk=1875MHz mclk=9251MHz Sol/W=0.16
            [ 0d 0h 2m30s] 0>RTX 3080 100% [63°C/98%] 27.98 I/s 54.5(54.5)Sol/s 348(348.5)W clk=1950MHz mclk=10251MHz Sol/W=0.16
            [ 0d 0h 2m40s] 0>RTX 3080
            100% [63°C/91%]*27.98 I/s 54.8(54.8)Sol/s 344(347.6)W clk=1875MHz mclk=9251MHz Sol/W=0.16
            [ 0d 0h 2m50s] 0>RTX 3080 100% [63°C/97%]*27.90 I/s 55.0(55.0)Sol/s 346(347.8)W clk=1950MHz mclk=10251MHz Sol/W=0.16
            [ 0d 0h 3m00s] 0>RTX 3080
            100% [63°C/100%]*27.94 I/s 54.6(54.6)Sol/s 347(347.8)W clk=1950MHz mclk=10251MHz Sol/W=0.16
            [ 0d 0h 3m10s] 0>RTX 3080 100% [63°C/100%]*27.92 I/s 54.7(54.7)Sol/s 348(348.0)W clk=1950MHz mclk=10251MHz Sol/W=0.16
            [ 0d 0h 3m20s] 0>RTX 3080
            100% [63°C/100%] 27.84 I/s 54.4(54.4)Sol/s 348(347.9)W clk=1950MHz mclk=10251MHz Sol/W=0.16
            [ 0d 0h 3m30s] 0>RTX 3080 100% [63°C/100%]*27.82 I/s 54.4(54.5)Sol/s 347(347.7)W clk=2010MHz mclk=10251MHz Sol/W=0.16
            [ 0d 0h 3m40s] 0>RTX 3080
            100% [63°C/100%] 27.57 I/s 53.9(54.0)Sol/s 347(347.8)W clk=2010MHz mclk=10251MHz Sol/W=0.16
            [ 0d 0h 3m50s] 0>RTX 3080 100% [63°C/100%] 27.33 I/s 53.3(53.5)Sol/s 347(347.6)W clk=2010MHz mclk=10251MHz Sol/W=0.15
            [ 0d 0h 4m00s] 0>RTX 3080
            100% [63°C/100%] 27.13 I/s 53.3(53.5)Sol/s 348(347.7)W clk=1965MHz mclk=10251MHz Sol/W=0.15
            [ 0d 0h 4m10s] 0>RTX 3080 ` 100% [63°C/100%] 27.14 I/s 53.4(53.5)Sol/s 349(347.9)W clk=1935MHz mclk=10251MHz Sol/W=0.15

            sweet it works! managed to get it stable at around 54 Sol/s give and take. gonna run it overnight and see how it performs and I shall let you know.

  13. Andy says:

    Hi Grillsum,

    Which version of the miniZ works with GPU TITAN – TITAN BLACK (_sm35) on the 144,5s – BeamHash III algorithm

    • miniZ says:

      Hi Andy,

      Thank you for your message.

      miniZ is not compliled for _sm35, so you will not be able to use it with that GPU.
      We will try to include it in the next version, however performance should be very modest.

      Cheers

      • Andy says:

        Thanks for all.

        If it does not make it difficult, please add sm_35 support for GPU Titan. It’s just that GPU Titan is available in some quantity.

        Best wishes

        • miniZ says:

          Hi Andy,
          Next cuda 10 version will support sm_35 for 144,5s – BeamHash III algorithm 🙂
          Cheers

          • Andy says:

            I installed a new version, unfortunately the support GPU TITAN sm_35 does not work.

            From log:

            ************ miniZ v1.6x ************
            Algo: EQ[144,5s]
            Pool#0: user[3d3475ee5e4618f2fd378a9263133e72eca24e01c49a6c152dc17baaf479402ab0e.dxs252]
            server[beam.2miners.com] port[5252] ssl[yes] pers[Beam-PoW]
            Telemetry: [http://localhost:20000]
            Logging:: file[miniZ.log] period[10] delay[0]
            Temp. limit: [90шC]
            miniZ[09:0:00:5268]: Selecting GPU#0[0] GeForce GTX TITAN
            [FATAL ] GPU[0]: CUDA error 6 ‘the launch timed out and was terminated’ in line 935
            [INFO ] Disconnecting from beam.2miners.com

            • miniZ says:

              Hi Andy,

              We’ve tried with another sm_35 GPU and it was running fine.

              Are you overclocking? Have you tried mining with stock settings?

              You could also try mining with another kernel. For example add --mode=0 to your command line.
              Also, you may test --mode=n, n=0-5,7-10,13-15. (0-15, except 6,11,12)

              But, test stock settings first, it really looks like it’s related to that.

              Let us know how it goes.
              Cheers

              • Andy says:

                Hi,
                I tested on stock settings and with parameters –mode=n, n=0-5,7-10,13-15 .
                Drivers used 440.97 and 411.70
                Result in the log file:

                ************ miniZ v1.6x ************
                Algo: EQ[144,5s]
                Pool#0: user[3d3475ee5e4618f2fd378a9263133e72eca24e01c49a6c152dc17baaf479402ab0e.dxs382]
                server[beam.2miners.com] port[5252] ssl[yes] pers[Beam-PoW]
                Telemetry: [http://localhost:20000]
                Logging:: file[miniZ.log] period[10] delay[0]
                Temp. limit: [90шC]
                miniZ[00:0:00:5264]: Selecting GPU#0[0] GeForce GTX TITAN
                [ 0d 0h 0m05s] 0>GTX TITAN 100% [43шC/54%] 0.65 I/s 1.8(1.8)Sol/s 161(160.9)W clk=954MHz mclk=3004MHz Sol/W=0.01- 54ms
                [ 0d 0h 0m10s] 0>GTX TITAN
                100% [43шC/54%] 0.92 I/s 1.8(1.8)Sol/s 161(160.9)W clk=954MHz mclk=3004MHz Sol/W=0.01- 54ms
                [FATAL ] GPU[0]: CUDA error 4 ‘unspecified launch failure’ in line 935
                [INFO ] Disconnecting from beam.2miners.com
                ************ miniZ v1.6x ************
                Algo: EQ[144,5s]
                Pool#0: user[3d3475ee5e4618f2fd378a9263133e72eca24e01c49a6c152dc17baaf479402ab0e.dxs382]
                server[beam.2miners.com] port[5252] ssl[yes] pers[Beam-PoW]
                Telemetry: [http://localhost:20000]
                Logging:: file[miniZ.log] period[10] delay[0]
                Temp. limit: [90шC]
                miniZ[00:0:00:5264]: Selecting GPU#0[0] GeForce GTX TITAN
                [ 0d 0h 0m05s] 0>GTX TITAN 100% [47шC/56%] 0.65 I/s 1.8(1.8)Sol/s 172(171.5)W clk=954MHz mclk=3004MHz Sol/W=0.01- 45ms
                [FATAL ] GPU[0]: CUDA error 6 'the launch timed out and was terminated' in line 935
                [INFO ] Disconnecting from beam.2miners.com
                ************ miniZ v1.6x ************
                Algo: EQ[144,5s]
                Pool#0: user[3d3475ee5e4618f2fd378a9263133e72eca24e01c49a6c152dc17baaf479402ab0e.dxs382]
                server[beam.2miners.com] port[5252] ssl[yes] pers[Beam-PoW]
                Telemetry: [http://localhost:20000]
                Logging:: file[miniZ.log] period[10] delay[0]
                Temp. limit: [90шC]
                miniZ[00:0:00:5264]: Selecting GPU#0[0] GeForce GTX TITAN
                [ 0d 0h 0m05s] 0>GTX TITAN
                100% [48шC/64%] 0.66 I/s 1.8(1.8)Sol/s 164(163.8)W clk=980MHz mclk=3004MHz Sol/W=0.01- 45ms
                [ 0d 0h 0m10s] 0>GTX TITAN ` 100% [48шC/64%] 0.92 I/s 1.8(1.8)Sol/s 164(163.8)W clk=980MHz mclk=3004MHz Sol/W=0.01- 45ms
                [FATAL ] GPU[0]: CUDA error 4 ‘unspecified launch failure’ in line 935
                [INFO ] Disconnecting from beam.2miners.com

                etc

                Thanks

                • Andy says:

                  HI,

                  THANKS FOR ALL

                  Everything is working.
                  Works –mode=7 and –mode=10.
                  Works stably –mode=7 !!!

                  Thanks
                  Best wishes!

                  • miniZ says:

                    Hi Andy,
                    Thank you for the feedback!
                    Great that it worked well.
                    Are they performing ok?
                    Cheers

                    • Andy says:

                      ID DEVICE NAME °C I/S SOL/S SOL3H/S SOL/W WATT SHARES
                      0 GeForce GTX TITAN 53 2.27 4.7 4.5 0.03 150.0 998/67/1
                      1 GeForce GTX TITAN 55 2.26 4.5 4.5 0.03 150.0 1019/61/1
                      Total 55 4.53 9.2 9.0 0.03 300.0 2017/128/2
                      ocX summary miniZ 1.6x @ REK5KN9
                      algo 144,5s

  14. Shannon Haslam says:

    Hi I have a 680GTX and when running the MINIZ under nicehash it just says excluding GPU#1.

    Im not sure why this is any feedback would be great.

    • miniZ says:

      Hi Shannon Haslam,

      miniZ is not compliled for _sm3X architectures (Kepler), so you will not be able to use it with your GTX680.

      To include architectures below _sm35 we would need to make major modifications to the program, so that it would be able to run on those GPUs.

      We believe that your GPU is sm30, could you please confirm this by running miniZ with -ci program?:

      miniZ.exe -ci

      Could you also tell us which algo where you trying to run?

      Thank you for your feedback!
      Cheers

      • Shannon Haslam says:

        Thanks for the feedback. Yes it is in fact SM version 3.0.

        No dramas thought id ask the question. I managed to get it running on version v1.5u2

        But it only supports 144,5 and it doesn’t seem to download the files required to run it.

        Thanks for your help anyway.

        • miniZ says:

          Hi Shannon Haslam,

          Possibly, with version v1.5u2 you are be able to mine 144,5 210,9 and 96,5.

          “But it only supports 144,5 and it doesn’t seem to download the files required to run it.”
          Sorry but we didn’t quite understand which files are you referring to. 🙂

          If you are interested in a particular algo we may try to have a look at it for the next version.
          Just let us know which and we’ll see what we can do.

          Thanks for your feedback!
          Feel free to contact us anytime for support or information.
          Cheers

          • Shannon Haslam says:

            I tried miniz om my rtx 3090, but that does not seem to work either. It looks like it ready but waiting from data from nicehash server.

            I have added a screen shot, maybe this will help.

            ************ miniZ v1.5u2 ************
            Algo: EQ[144,5]
            Pool#0: user[removed]
            server[zhash.eu.nicehash.com] port[3369] ssl[no] pers[auto]
            Telemetry: [http://localhost:4000]
            Temp. limit: [90°C]
            miniZ[13:0:00:23336]: Selecting GPU#0[0] GeForce RTX 3090
            [ 0d 0h 0m10s] 0>RTX 3090 100% [46°C/38%] 134684.11 I/s 0.0( 0.0)Sol/s 113(112.8)W clk=1695MHz mclk=9501MHz Sol/W=0.00
            [ 0d 0h 0m20s] 0>RTX 3090
            100% [47°C/38%] 140636.54 I/s 0.0( 0.0)Sol/s 113(113.0)W clk=1695MHz mclk=9501MHz Sol/W=0.00
            [ 0d 0h 0m30s] 0>RTX 3090 100% [48°C/38%] 142149.27 I/s 0.0( 0.0)Sol/s 113(113.5)W clk=1695MHz mclk=9501MHz Sol/W=0.00
            [ 0d 0h 0m40s] 0>RTX 3090
            100% [46°C/38%] 142341.16 I/s 0.0( 0.0)Sol/s 69( 71.9)W clk=210MHz mclk=405MHz Sol/W=0.00

            • miniZ says:

              Hi Shannon Haslam,

              The RTX 30XX are recent GPUs, only the most recent miniZ version supports them, and needs to be Cuda 11.

              You need to use v1.6w4, Cuda 11 version to be able to mine with your RTX 3090.

              Regarding the older hardware, we will try to compile for the sm_30. Maybe it will work for some algo. Which one interests you more? We will try to give that one a closer look.

              Let us know how it goes 🙂
              Thanks for the feedback!

              • Shannon Haslam says:

                I have 6X the older Gtx 680s. I thought I would use them to mine instead of throwing them out. I know its not efficient, but I run them off my solar so power is free.

                The other thing I think might be a big issue is the fact they are only 2 gigabytes of Vram.

                In the latest version of miniz 1.6w I get the fatal error cannot load device code.

                C:\Users\shasl\Desktop\minizcuda11>.\miniZ.exe –[email protected].com:3369 –pers=AION0PoW -cd 1
                ************ miniZ v1.6w4 ************
                Algo: EQ[210,9]
                Pool#0: user[removed]
                server[zhash.eu.nicehash.com] port[3369] ssl[no] pers[AION0PoW]
                Telemetry: [http://localhost:20000]
                Temp. limit: [90°C]
                miniZ[01:0:00:1669]: Selecting GPU#1[0] GeForce GTX 680
                [FATAL ] Cannot load deviceZ code.
                [INFO ] Disconnecting from zhash.eu.nicehash.com
                [INFO ]zhash.eu.nicehash.com Stopping miner

                • miniZ says:

                  Hi Shannon Haslam,

                  The Cuda 11 version is needed to run in the RTX 3090. It is not appropriate for GTX 680.

                  At the moment, you will not be able to run miniZ with the GTX 680.

                  We see that you have a command line that will not work. In Nicehash you can omit –pers.
                  With the RTX 3090, with Cuda 11 version you can run:

                  miniZ.exe [email protected]:3369

                  We’ll see what we can do with the GTX 680, sm_30 architecture, to mine Zhash 🙂

                  Cheers

  15. Shannon says:

    No worries thanks for all the help.

  16. Alex says:

    Benchmark doesnt find from NVIDIA Ge Force GTX 765M
    https://prnt.sc/wljxhr

    • miniZ says:

      Hi Alex,
      Thank you for the feedback.
      GTX765M is Kepler architecture, you’ll need to force miniZ to use the GPU.
      You need to use -cd option: -cd 0.
      Let us know if this solved the issue.
      Cheers

  17. Charles says:

    Hi,

    I get “CUDA error 4 ‘unspecified launch failure’ in line 626” when running miniZ with my GTX660Tis using launch parameter -cd 0.

    • miniZ says:

      Hi Charles,
      Which algorithm are you running?
      Also, which operating system are you using?
      Thanks,
      Cheers

      • Charles says:

        I’m sorry, I’m kinda new to this, so I’m using miniZ through NiceHash on Windows 10. It only says “algorithm: ZHash”. NiceHash’s benchmark feature “approved” miniZ on two of my cards, but the CMD shell returns the error message and crashes everytime I try to start mining.
        Did I understand correctly that Kepler only works with the 144,5 algorithm?

        • miniZ says:

          Hi Charles,
          It is OK, we’ll try to understand the issue.

          Maybe you need to choose a different kernel to be able to mine with your gpu,
          it may be too slow for the default kernel.Which algo are you trying to mine?
          miniZ supports all Kepler architecture for all algos.

          Cheers

          • Charles says:

            Thanks for taking the time.

            I’m trying to use algo 144,5 according to the shell window before it auto shuts down, and NiceHash calls the algo ZHash.

            I tried the launch parameter –ocX to select the best kernel, and it still fails in line 626 but this time with CUDA error 6 ‘the launch timed out and was terminated’.

            • miniZ says:

              Hi Charles,

              You may need to add the kernel explicitly to the command line.
              Could you try adding --mode=n, n=[0,1,2,3,4,5,7,8,9,10,12,14,15]?

              Let us know if this helped.
              Cheers,
              miniZ

              • Charles says:

                No luck. Still error 6 in line 626. After I added –mode=n, n=[0,1,2,3,4,5,7,8,9,10,12,14,15] it also says [WARNING] GPU[2] cannot run in mode 0.

                • miniZ says:

                  Hi Charles,
                  We realize that on windows your 2GB GPU will only work with --mode=15. On windows 7 and linux, mode 14 should be also available.

                  Is there a possibility for you to try linux? It would be better because windows always reserves considerable amount of memory that limits the GPU potential.

                  Regarding the crash: possibly it occurs because the GPU is a bit slow, and the driver ‘thinks’ that the GPU crashed.
                  Are you running the GPU with overclock?
                  Cheers,
                  miniZ

  18. Charles says:

    Hi,
    I tried –mode=15, and it still alternated between error 4 and 6 in line 626. One time, it appeared to be working, but then it said “cannot resolve” instead.

    I would love to ditch M$ forever, but I’m too invested in the Cubase environment. :-/ The plan is to use the GPUs to heat up the room while I’m making music, and recuperate some of the cost.

    I attempted to overclock ~10% with MSI Afterburner, but the computer immediately froze, and woke up after a couple of minutes with all GPUs clocked at 324MHz. So, maybe there’s a driver issue.

    • miniZ says:

      Hi Charles,

      It seems you have an old system. Have you tried mining other algorithms?

      210,9 (AION) may work better with older systems. 96,5 could also work, but Aion may be more profitable.

      The ‘cannot resolve’ error is usually related to pool server misspelling in the command line.
      If, after checking this, you still have this error, could you paste here your command line?

      Let us know if you managed to make it work.
      Cheers,
      miniZ

  19. Mustang says:

    Hi,

    I’m desperately trying to get my Nvidia GeForce GT 710 to mine BTGs (I know, it’s not the best GPU for mining but it’s all I’ve got) and I can’t seem to get it to work. Any help would be greatly appreciated…

    When I use the “-ci” option my GPU is correctly seen/found:
    Number of miniZ CUDA>=[8.0] using driver CUDA[11.20] devices found: 1
    #0 GeForce GT 710 | SM version: 3.5 | SM count: 1 | cores: 192 | Memory: 1.654GB | BusID:0000:04:00.0

    However, it seems to exclude my GPU when I try running it :
    C:\Users\Admin\Desktop\crypto\miniZ_v1.7x3_win-x64>miniZ.exe –[email protected]:4040
    ************ miniZ v1.7×3 ************
    miniZ: Excluding GPU#0 GeForce GT 710
    Number of CUDA[8.0] devices found: 0
    No devices selected, exiting…

    When I try forcing it to use my GPU I get a timeout :
    C:\Users\Admin\Desktop\crypto\miniZ_v1.7x3_win-x64>miniZ.exe –cuda-devices 0 –[email protected]:4040 –par=144,5
    ************ miniZ v1.7×3 ************
    Algo: EQ[144,5] [smart-pers]
    Pool#0: user[GWzhsddbsVhwowRu1PjugmjTKenFRDppur.mustang]
    server[btg.2miners.com] port[4040] ssl[no] pers[BgoldPoW]
    Telemetry: [http://localhost:20000]
    Temp. limit: [90°C]
    [INFO ] Mining fee set to 2.00%
    miniZ[15:0:00.0:1694]: Selecting GPU#0[0] GeForce GT 710
    [FATAL ] GPU[0]: CUDA error 6 ‘the launch timed out and was terminated’ in line 617
    [INFO ] Disconnecting from btg.2miners.com

    And when I try increasing the timeout I get an “unknown error”:
    C:\Users\Admin\Desktop\crypto\miniZ_v1.7x3_win-x64>miniZ.exe –cuda-devices 0 –[email protected]:4040 –par=144,5 –jobtimeout=30
    ************ miniZ v1.7×3 ************
    Algo: EQ[144,5] [smart-pers]
    Pool#0: user[GWzhsddbsVhwowRu1PjugmjTKenFRDppur.mustang]
    server[btg.2miners.com] port[4040] ssl[no] pers[BgoldPoW]
    Telemetry: [http://localhost:20000]
    Temp. limit: [90°C]
    [INFO ] Mining fee set to 2.00%
    miniZ[15:0:00.0:1694]: Selecting GPU#0[0] GeForce GT 710
    [FATAL ] GPU[0]: CUDA error 30 ‘unknown error’ in line 617
    [INFO ] Disconnecting from btg.2miners.com

    Many thanks in advance!

    • miniZ says:

      Hi Mustang,
      Thank you for the feedback.
      We are able to use our GT 710, on Windows 10 with 461.72 driver. Which OS and driver do you have installed?
      It also works with Linux OS without any issue.
      It seems that in your system the GPU is a bit slower, and the driver ‘thinks’ that the GPU crashed.
      You can try and mine other algorithm, Aion for example.
      Let us know if you managed to get it working.
      Cheers

      • Ko MIN says:

        I also use 710, it found gpu. When I run miniZ_gui.exe , it is loop and not run miniZ.exe. I dont see more. ” \miniZ.exe –url=ssl://[email protected]+tcp://stratum.okpool.me:16896 –par=144,5 –pers=BgoldPoW -ci -cd 0 –f11=1 –mode=1 –log –donate=2% ” what wrong is it? I use only single gpu. Thanks

        • miniZ says:

          Hi Ko MIN,

          Thank you for contacting us.

          There are a few things that are not well in the command line that you are using.

          First, the option -ci is used only to output information about your GPUs. If you use this in the command line miniZ will just output the information and then exits.

          Second, --mode 1 will not run in the GT 710. It’s best to not specify the mode, in this case. miniZ will use the best kernel mode. It will use mode 14 or 15.

          Third, the pool+port you are trying to use is not ssl. You need to remove the ssl information in the comand line.

          (You can also remove the --f11 option, this is an old option that is deprecated.)

          The command line should be as follows.
          .\miniZ.exe [email protected]:16896 --par=144,5 --pers=BgoldPoW -cd 0 --log --donate=2%

          Thank you for using --donate. Because, your gpu is will not be very efficient, we understand if you do not use it.

          However, the pool seems to be down. It seems that the pool is not working. We are also not able to mine with OKX pool. Are you able to use another pool?

          Let us know how it goes.
          Cheers

          • Ko MIN says:

            Hello, Thanks your reply. Now I am still learning after that I do buy more efficient cards. May I know your prefer pool for btg.

          • Ko Min says:

            Hello I got with btg.2miners.com. It is going but sol is 0.0.

            • miniZ says:

              Hi Ko Min,
              The GPU that you are using will not perform very well. It will hash close to zero. Something like 0.2-0.3 Sol/s for BTG.

              Do you see 0.0 on the pool side? 2miners is a high difficulty pool. Try using a pool that provides low difficulty ports. In this case you may be able to see the value go above zero for BTG.
              For example, you can try zhash.pro – https://btg.zhash.pro/getting_started with their ‘single gpu’ port.
              Suprnova is also OK – https://btg.suprnova.cc/ – but you need to get a username.
              This way maybe you can submit a share at some point. With that GPU will be very hard to submit when mining 144,5 (BTG, BTCZ…), and without submitting shares the pool doesn’t get information about your mining.

              With GT 710 you can try mining 210,9 algorithm, Aion. You’ll be able to make ~2.5-3.0 Sol/s.

              Cheers

  20. Oliver says:

    Hi,

     

    I’m testing miniZ with my notebook and a Nvidia Quadro K3000M card. It does not work.

    miniZ: Excluding GPU#0 Quadro K3000M
    Number of CUDA[8.0] devices found: 0
    No devices selected, exiting…

     

    what can I do?

     

    regards

    Oliver

     

    • miniZ says:

      Hi Oliver,
      Thank you for the feedback.

      Try adding to your command line: -cd 0.
      Kepler GPUs are excluded by default, you need to include them ‘by hand’.

      Let us know if this works for you.
      Cheers

  21. Oliver says:

    Hi, I’m back,

    thanks for your help, miner version v1.6w2 reports an error, (can not load deviceZ)

    miner version 1.5t3 starts, everything seems ok, quadro 3000M selected, reports everything. Also get some new job, cards detected, temp ok, but thats all. every 10 sec. comes a new line, but no interations, always 0.

    I use the 2miner, and mining BTG.

    Can I try anything else?

    regards

    Oliver

    • miniZ says:

      Hi Oliver,
      Thanks for letting us know.

      The error with v1.6w2 means that this version did not contain the kernel for your gpu.

      The issue with v1.5t3 is a bit more unspecific. Could be that the miner was not able to start the GPU.

      Have you tried the latest version, 1.7×3? Or 1.6x? Do they give the same errors?

      Cheers

  22. Oliver says:

    Hi,

    and many thanks for your help, I hope we can get the f.. machine running!
    So here are the results:

    Latest Version v1.7x
    -miner starts ….ok
    -Algo, Pool, Telemetry, Temp.Limit…ok
    -Info about mining fee ….ok
    then:
    miniZ<144,5>[15:0:00.0:1699]: Selecting GPU#0 Quadro K3000M
    [Fatal] GPU[0]: CUDA error 4 ‘unspecified launch failure’ in line 617
    [Info] disconnecting from btg.2miners.com

    …then restart…and again same procedure

    Version 1.6x
    same but the failure is in 626

    Any ideas to fix the problem?
    regards
    Oliver

    • miniZ says:

      Hi Oliver,
      Thank you for your message.
      Unfortunately if the GPU very slow the windows driver may think that the GPU crashed and will stop the miner, it should work in Linux though.
      Have you tried to mine 210,9 – Aion? It is a lighter algorithm, and most likely a good option for your GPU.
      Cheers

  23. Oliver says:

    Hi,

    i tried Linux, the miner starts without error, but after that nothing happenend!

    BUT;…..AION works fine 🙂 nice tip……thanks so much! So my 2 old K3000M notebooks can have some fun 🙂

    many thanks for your help and always quick replay!

    Oliver

     

    • miniZ says:

      Hi Oliver,
      Great that you managed to get it working 🙂
      Thanks for the feedback, and for using miniZ!
      Cheers

  24. ertan says:

    Hello,

    I’m new at mining, every thing seems okay,

    But I have some question; I have mined for 8-12 hours a few times, but no coins are transferred to the wallet, there is a limit for this? It was shares of 80-150 a few times.

    thank you

    • miniZ says:

      Hi ertan,
      Usually the pool defines a minimum treshold that you need to achieve before a transaction is made for your wallet. Most (if not all) pools allow you to modify the treshold. The way this is done depends on the pool.
      Check with the pool what is their minimum threshold for the coin you are mining. Normally this information is available at the pool website.
      Let us know if this helped.
      Thanks for using miniZ!
      Cheers

  25. yann says:

    Hello, I have a problem to increase my memory clock. I parameter it on msi afterburner but when I start miniz, it is like I did nothing and stay at the same level. I m on 125.4 with a gtx 970. Can you help me

    Thank you by advance

  26. Spoinky says:

    Hi,

    I purchase an raspberry screen to hang to my rig for showing some output of miniZ process. Since i miss read the specs and i received a 5inch screen rather a 7inch i was wonder :

    Does it exist a way to make a custom mining output string for sparing space on each line ? Meaning how can i print only like hashrate and temp and GPU’s name for example ?

    Thanks, best regards… ( sorry for my poor english )

    • miniZ says:

      Hi Spoinky,

      Thank you for your message.

      We have no explicit way to do what you ask. However, maybe the best is to use the json API.

      Use curl http://rig2:20000/getstat -s |jq and then parse the information you want.

      You can also parse the log (or the csv) file.

      Possibly, the option --coolui may also do the trick for you.

      Let us know if this helps.
      Cheers

      • Fabrice DAO says:

        Hello, thank for you answer…

        Finally i keep the –coolui as option. It’s fit perfectly the 5’inch screen. AlL info are there. It’s perfect.

        Thank for your great work !

  27. Matthew Hedgecock says:

    Hi, I added a GTX 970 to my rig to boost my hashrate, but when I use it with my 2070, my 2070s hashrate goes down. Essentially I’m seeing no difference in performance because of this. Alone my 2070 does around 65-70 sols, and with my 970 running it does around 50. Anyway I can fix this? Thanks!

    • miniZ says:

      Hi Matthew Hedgecock,

      Is it possible that your power supply is not enough for the two GPUs? If you run miniZ selecting only the RTX 2070 (use -cd option) what happens?
      You repport a quite significant difference, but is temperature much higher with the two GPUs?

      What algorithm are you mining?

      Thanks for the feedback.
      Cheers

  28. Spoinky says:

    Hi, apparently LoLminer manage to unblock some of the 3060 performance mining…

    Here https://github.com/Lolliedieb/lolMiner-releases/wiki/3060-Booster

    Will we see the same update soon on MiniZ ?

    • Spoinky says:

      Apparently HiveOS with LoLMiner should unlock 100% of hashrate now. Will we see this kind of update for linux ( Ubuntu ) soon with miniZ ? I really like MiniZ and i wanna stick with it as long as i can… But my rig is full 3060, so the loose is hudge rightnow…
      Let me know. Best regard guys and thank for this great miners software…

      • miniZ says:

        Hi Spoinky,
        Sorry for taking a bit longer to reply.
        We’ll have a look and see what we can do for future releases.
        Thanks a lot for the suggestion and for using miniZ 🙂
        Cheers

        • Fabrice DAO ( Spoinky ) says:

          Hey miniZ, I would like to thank you about your last release ( v1.8y2 ). Now RTX3060 work like a charm with HyveOs/MiniZ. I achieve this :

           3>  RTX 3060       `   100%   [  56°C  / 0%]    40.93  (40.91)MH/s 120(119.8)W clk=1777MHz mclk=7501MHz MH/W=0.34 

          with this preset : FAN 80% CORE -150 Mem 2500 PL 120w options are (GPU focused) : –mode3 7 –tune3 38

          • Fabrice DAO ( Spoinky) says:

            Well i got a little bit excited, sometime i have this error after some mining time : miniZ 3060 CUDA error 6 ‘the launch timed out and was terminated’.The miner restart and mine again for 5min before restarting again and again …I try to tunes ( unacknowledged ) options -mode & -tune.

            • miniZ says:

              Hi Fabrice DAO,
              Thank you for the feedback.
              These CUDA errors are usually related to OC settings.
              Try to adjust a bit your settings and check if it helps.
              Cheers

  29. tubs says:

    trying to mine equihash 125,4 but keep getting Error: invalid mode 0 for gpu[0]
    I am using gtx 1650

    tried manually setting mode0=0 still didn’t work

    • miniZ says:

      Hi tubs,

      Thank you for the feedback.

      Are you using Windows 10? With this OS, the available memory for the 4GB GPUs is not enough to take the best out of this GPU with 125,4. We’ll add a kernel that should be enough to support lower memory GPUs, but efficiency and performance will be slightly reduced. (It is better with Windows 7 or Linux).

      Cheers

  30. samuel says:

    bonjour

    j’utilise miniz depuis un moment sans soucie et y a peux j’ai eu cette erreur [FATAL ] CUDA Driver API error = 0700 from <125,4>, line 1279

    j’ai redémarrer le pc et sa ma fais l’erreur 2 fois de suite au lancement de miniz puis la troisième fois non est sa a lancer le minage

    je l’utilise avec une rtx 3070 sous windows 10 et les drivers sont a jour.

    il n ‘y a aucun écrans brancher sur la cg ils sont brancher sur la carte mère

    je sais pas si vous avez déjà eu de retour sur ce soucis

     

    merci

    • miniZ says:

      Hi samuel,

      Merci de votre contact.

      This error seems to be related to overclocking. Are you applying any OCs?

      With OCs the GPU/Driver may become unstable. If this is the case, try to mine without any OC and see if the error persists.

      If you only have error with OC, you need to adjust the values a little.

      Let us know if you still have the same error without any OC. In this case, could you paste here the start of miniZ log? The information that appears before the actual mining starts.

      Let us know if this helps.
      Cheers

  31. samuel says:

    désoler impossible de répondre a votre message

    j’ai trouver d’où vener le soucis j’ai cette erreur que quand j utilise le logiciel internet download manager .

    juste en utilisant ce logiciel et sans rien changer d autre j’ai cette erreur qui apparais au bout d un moment et puis plus rien quand je le coupe .

     

    • miniZ says:

      Salut Samuel,

      Nous ne pouvons pas comprendre le soucis.
      Cela pourrait-il être lié au firewall de Windows?

      Pourriez-vous nous envoyer, ou coller ici, une capture d’écran ?
      Merci

  32. Mike says:

    Hello, I am trying the new v1.8y3 with a 3060 lhr 2409 version but am still limited to half of the hash rate. Is there something else that I need to do to achieve a higher rate? Thanks

    • miniZ says:

      Hi Mike,

      Thank you for the feedback,

      Which OS and driver are you using?
      Or could you paste a screenshot with start of the miner?

      Do you get a message similar to this: [TRACE ] GPU[2]: Searching lock... speed=22.3/49.1[2,54.0,2.320,1.00]?
      Values may be different. Could you paste here it here too?

      Did you try driver 460.39 (Linux) or 461.40(Windows)?

      We are still improving this, we notice that not everyone seems to be getting the same output from the GPU.

      Cheers

      • ultra says:

        Hi,

        I have a similar problem. I’ve got a new Zotac GeForce 3060 Ti LHR. The hashrate is throttled to 20 MH/s with miniZ v1.8y3 and NVIDIA driver v471.68. I tried to install v461.40, but it does not pass the system check, saying

        This NVIDIA graphics driver is not compatible with this version of Windows.
        This graphics driver could not find compatible graphics hardware.

        Is there a chance to unlock it?

        Thank you in advance.

        • miniZ says:

          Hi ultra,
          It looks that you need to install a recent driver.
          Be sure to use version v1.8y4rc1 (beta version).
          Possibly you will need to add --tune=5 (or 4) to your command line.
          Let us know how it goes.
          Cheers

  33. kardook says:

    bonjour

    je n’est pas trouver dans command line arguments  se qu’il fallait mettre pour couper miniz si on avais un CUDA Driver API error = 0700 from <125,4>, line 1279 .

    cette option est disponible dans miniz ?

     

    merci

    • miniZ says:

      Hi kardook,

      Thank you for your message.

      Usually, when this happens miniZ exits. But it may not be able to do so when the driver/GPU crashes, or gets too unstable.

      It is better to adjust a bit your OC settings.

      Cheers

  34. Tontan says:

    First I am using rtx 3060 with latest driver version and it get only ~18MHz.
    However, I tried to install 461.40 but It could not install 461.40 (Windows) driver. It show a message the graphics driver is  not compatible

    • miniZ says:

      Hi Tontan,

      Thank you for your message.

      You need to install a recent driver. Some GPUs are not supported by the old driver.

      When mining, do you see any message like this “[TRACE ] GPU[1]: Searching lock… ” ?

      You may not get the message, but it seems that miniZ is not able to get rid of the mining lock. Try adding --tune=5 to your command line (or 4 if the lock persists).

      A new version will come out very soon and should work better with your GPU.
      Let us know how it goes.
      Cheers

  35. Danish Farooq says:

    CUDA error 6 ‘the launch timed out and was terminated’ in line 1046 <-= This Error comes4 x RTX 3060 SOFTWARE LOCKUSING –mode 80 command and using Driver 460.39 Sometime i got this error and miner restart and some time miner working fine dont know what to changei m using -150 core and 2700 mem, 130 power limit, using in HIVEOS

    • miniZ says:

      Hi Danish Farooq,
      This seems to be related to OCs.
      Try to lower power limit to ~100W.
      Let us know if this helps.
      Cheers

  36. Robert P Ringstad says:

    Cannot reliably get any of the most recent 2 stable and beta versions working for more than 2 hours on a computer with a 2060 and 3070Ti. Errors vary, but typically the error is ‘an illegal memory access was encountered’ and references line 2451. I have tried 3 different versions of the Nvidia driver, all with the same result. Hope we can figure this one out…

    • miniZ says:

      Hi Robert P Ringstad,
      This seems to be OC related.
      Could you adjust your values a bit and see if it helps?
      Cheers

  37. Daniel says:

    In hiveos on miniz miner mining flux, my rtx 2060 super wont work, why might it not work? sometimes it just comes error failure and sometimes it shows up and mines for a few swconds and then get the error again.

  38. Daniel says:

    Hi when im mining flux on miniz my rtx2060super wont work, sometimes it mines for a minte and then it gets an error failure.and sometimes it is at startup i get the error

    • miniZ says:

      Hi Daniel,
      It should work. From what you describe it looks that it is related to the OCs.
      Try to adjust the Ocs a little and see if it helps.
      Let us know how it goes.
      Cheers

  39. Tom says:

    Getting Fatal error Could not load deviceZ when trying to mine flux on 1650Supers in HiveOS. I am using the latest version and it works great on my 1660’s.

    • miniZ says:

      Hi Tom,
      Thank you for letting us know.
      We were expecting it to work. Does this also happen with other algos?
      Could you paste here the miner log?
      Cheers

      • Jeremy Winright says:

        I am also having issues mining with the 1650 super. I am getting:

            [FATAL  ]   Cannot load deviceZ code.                                                                                                                                                                                                                                                                                                               
        • miniZ says:

          Hi Jeremy Winright,
          miniZ may be starting with kernel mode 6, which is not good for that GPU.

          You can try adding --mode 11 to your command line. (This will apply mode 11 to all your GPUs.
          To apply to only this GPU use --modeN 11 (N is the GPU number).

          In the case you have a screen attached to your GPU, it may not have much memory availble for mining.
          If you see that mode 11 is not good for the GPU, try adding --mode 18 instead.

          Let us know if this helps.
          Cheers

      • Tom says:

        GPU #0: GTX 1650 SUPER – 11.54 MH/s, [ T: 51 C, P:80W, F:60%, E:146kH/W ] , 44/44 R: 0 % I: 0 %
        GPU #1: GTX 1650 SUPER – 11.37 MH/s, [ T: 52 C, P:79W, F:60%, E:144kH/W ] , 35/35 R: 0 % I: 0 %
        GPU #2: GTX 1650 SUPER – 11.50 MH/s, [ T: 56 C, P:80W, F:60%, E:146kH/W ] , 36/36 R: 0 % I: 0 %
        Hashrate: 34.41 MH/s, Shares/min: 5.701 (Avg. 4.112), Avg.P: 237W, Avg.E: 145kH/W
        Max diff share was found by GPU #0, diff: 20.27 G
        Uptime: 28 mins 1 sec | Algo: kawpow | T-Rex v0.24.8

        20220126 12:00:18 [ OK ] 116/116 – 34.41 MH/s, 31ms … GPU #1 | 671.27 M
        20220126 12:00:22 [ OK ] 117/117 – 34.42 MH/s, 50ms … GPU #0 | 475.37 M
        20220126 12:00:41 [ OK ] 118/118 – 34.42 MH/s, 31ms … GPU #2 | 635.56 M
        ^C 20220126 12:00:42 WARN: shutdown t-rex, signal [2] received
        20220126 12:00:42 Main loop finished. Cleaning up resources…
        20220126 12:00:42 ApiServer: stopped listening on 127.0.0.1:4059
        20220126 12:00:44 T-Rex finished.

        Miner: miniz
        Version: 1.8y4rc2

        ************ miniZ v1.8y4rc2 ************
        Number of CUDA[8.0] devices found: 3
        miniZ<125,4>[06:0:00.0:3837] : Selecting GPU#0[0] NVIDIA GeForce GTX 1650 SUPER
        [FATAL ] Cannot load deviceZ code.

        miniz exited (exitcode=1), waiting to cooldown a bit

        Skipping miner log rotation due to execution time < 30sec

        ************ miniZ v1.8y4rc2 ************
        Number of CUDA[8.0] devices found: 3
        miniZ<125,4>[06:0:00.0:3837] : Selecting GPU#0[0] NVIDIA GeForce GTX 1650 SUPER
        [FATAL ] Cannot load deviceZ code.

        miniz exited (exitcode=1), waiting to cooldown a bit

        Skipping miner log rotation due to execution time < 30sec

        ************ miniZ v1.8y4rc2 ************
        Number of CUDA[8.0] devices found: 3
        miniZ<125,4>[06:0:00.0:3837] : Selecting GPU#0[0] NVIDIA GeForce GTX 1650 SUPER
        [FATAL ] Cannot load deviceZ code.

        miniz exited (exitcode=1), waiting to cooldown a bit

        Skipping miner log rotation due to execution time < 30sec

        ************ miniZ v1.8y4rc2 ************
        Number of CUDA[8.0] devices found: 3
        miniZ<125,4>[06:0:00.0:3837] : Selecting GPU#0[0] NVIDIA GeForce GTX 1650 SUPER
        [FATAL ] Cannot load deviceZ code.

        miniz exited (exitcode=1), waiting to cooldown a bit

        Skipping miner log rotation due to execution time < 30sec

        ************ miniZ v1.8y4rc2 ************
        Number of CUDA[8.0] devices found: 3
        miniZ<125,4>[06:0:00.0:3837] : Selecting GPU#0[0] NVIDIA GeForce GTX 1650 SUPER
        [FATAL ] Cannot load deviceZ code.

        miniz exited (exitcode=1), waiting to cooldown a bit

        Skipping miner log rotation due to execution time < 30sec

        ************ miniZ v1.8y4rc2 ************
        Number of CUDA[8.0] devices found: 3
        miniZ<125,4>[06:0:00.0:3837] : Selecting GPU#0[0] NVIDIA GeForce GTX 1650 SUPER
        [FATAL ] Cannot load deviceZ code.

        miniz exited (exitcode=1), waiting to cooldown a bit

        Skipping miner log rotation due to execution time < 30sec

        ************ miniZ v1.8y4rc2 ************
        Number of CUDA[8.0] devices found: 3
        miniZ<125,4>[06:0:00.0:3837] : Selecting GPU#0[0] NVIDIA GeForce GTX 1650 SUPER
        [FATAL ] Cannot load deviceZ code.

        miniz exited (exitcode=1), waiting to cooldown a bit

        > Miner screen is running

        • Tom says:

          Progpow algo works just fine on the cards.

          • miniZ says:

            Hi Tom,
            Thank you for the feedback. We see that miniZ is starting with kernel mode 6, which is not good for that GPU.

            You can try --mode 11. This will apply mode 11 to all your GPUs.

            It looks like GPU 0 doesn’t have much memory availble for mining (possibly you have a screen attached to this one).
            If you see that mode 11 is not good for GPU 0, try adding --mode 11 --mode0 18 (order is important). This will start kernel mode 18 on GPU 0 and 11 on all other GPUs.

            Let us know if this helps.
            Cheers

  40. hany says:

    Hi what about support AMD cards specially for Flux mining ? RX 570 , RX 580 etc ,I found that Miniz miner is the best for my Nvidia cards so it sure will be great when support AMD cards also

    • miniZ says:

      Hi hany,
      Thank you for your interest and suggestion.
      We’re having look at it, and may release soon AMD support for Flux for RX 570 and RX 580.
      Later, we would like to support all other algos.
      Cheers

  41. Attila says:

    Please consider supporting AMD gpus

    • miniZ says:

      Hi Attila,
      Thank you for your interest and suggestion.
      We’re having look at it, and may release soon AMD support for Flux for RX 570 and RX 580.
      Later, we would like to support all other algos.
      Cheers

  42. Sam says:

    Bonjour,cela fait un mois que je tourne avec miniz et ça va bienmais depuis ce matin, j’ai souvent une erreur qui me ferme miniz[FATAL ] CUDA Driver API error = 0716 from <125,4>, line 1279.de quoi viens cette erreur et que puis je faire pour la corriger ?Merci

    • miniZ says:

      Hi Sam,
      Have you tried adjusting the OCs?
      This error is often related to that. Could you adjust the OC settings a little and try again?
      Let us know how it goes.
      Cheers

  43. jd.clie says:

    hi my msi rtx3090 suprimx is detected in windows (driver 470.05 27.21.14.5671) but not with Mininz miniZ_v1.8y3_win-x64 or MiniZ miniZ_v1.6w4_cuda11_win-x64Why ?Thanks

    • miniZ says:

      Hi jd.clie,
      It does not work with version v1.8y3? Have you tried using version v1.8yrc2?
      Could you paste here the output of running miniZ.exe -ci?
      Also could you paste here your command line, and the error you get when trying to run miniZ?
      Thank you.
      Cheers

  44. Krakow says:

    Hi, 

    Sometimes, after few hours of working one of my gpu stopped mining.

    Is there a command to add to prevent this and auto restart the miner?

    Best regards.

     

    • miniZ says:

      Hi Krakow,

      If by “stopped mining” you mean that the miner crashed (but not totally hang), you can run the miner by creating a bat file (will make the miner restart) as follows. Do not forget to customize your wallet address, worker name, server and port number:

      :loop
      miniZ.exe [email protected]:port --log --extra
      timeout /t 5
      goto loop

      Let us know if this helps.
      Cheers

  45. Tas says:
    Hi. I'm having this  '[WARNING] Telemetry socket xxxx error when I have telemetry on.'
    I can see that there is no values on Power, Fan Speed and Temperature:
    [ 0d 1h18m20s] S: 15/0/0 20(20.6)Sol/s 0( 0.0)W [eu.tent.k1pool.com]- 49ms (97.6%) (2.4%)
    0>GTX 1650 ` 100% [0 C/ 0%] 10.29 I/s 20.49(20.56)Sol/s 0( 0.0)W clk=1590MHz mclk=6001MHz Sol/W=inf
    I think this initial note on starting miniz tells what is the problem:
    --nohttpheaders
    ************ miniZ v1.8y4rc2 ************
    Cannot read health status! (is libnvidia-ml.so installed?): No such file or directoryNumber of CUDA[8.0] devices found: 1
    miniZ<144,5>[11:0:00.0:3326]: Selecting GPU#0[0] NVIDIA GeForce GTX 1650

    If this is the problem can you help me please?

    • miniZ says:

      Hi Tas,
      Thank you for your message.

      --nohttpheaders is unrelated.
      It looks like the socket is occupied with some other process.

      The message “Cannot read health status! (is libnvidia-ml.so installed?)” suggests that the driver is not correclty installed. Could you reinstall it, or make an update. (Which driver version are you using at the moment?)

      Let us know if this helps.
      Cheers

      • Tas says:

        Thank you for trying to help. I’m liking miniZ a lot. It is fantastic. The only think I miss is the telemetry readings ;). My nVidia drivers version is 30.0.14.7212.Thanks in advance. 🙂👍

        • miniZ says:

          Hi Tas,
          Have you tried to update the driver?
          You can try to update the driver, possibly this would be enough to solve the issue.

          If this doesn’t work maybe you are missing the nvidia library nvml.dll.
          It could be misplaced, or during driver instalation the antivirus got rid of it.

          You’ll need to find/download the file and add it to C:\Program Files\NVIDIA Corporation\NVSMI\, or to miniZ folder (should work too).

          You can also have a look at another message (with a bit more information) we posted here

          Let us know if this helped.
          Cheers

          ps: If you added --nonvml to your command line then do not use it.
          The option --nonvml is used to disable GPU monitoring. In this case, it shows that message, and disables the report of GPU data status (fan, temperature, power…).

  46. CK says:

    I like to use miniZ for equihash stable mining. It will be great if there is a version for AMD Card. Please release it soon. Eager to wait!

    • miniZ says:

      Hi CK,
      AMD version will be introduced in the next version.
      We will release first the support for 125,4 algorithm.
      Thank you for your preference!
      Cheers

  47. Ali says:

    Hi , I have an old Nvidia GeForce GT 640m and I want to using your miner for mining test.

    My GPU driver is 425.31 (latest driver for this card) and cuda version is 10.1 and using windows 11 x64.

    I download your miniZ_v1.6w2_cuda10_win-x64 miner ; but when I run it , get this error :

    “MiniZ: Excluding GPU#0 GeForce GT 640M

    Number of CUDA(10.0) devices found:0

    No devices selected, exiting…”

    Do you tell me what is the problem? My card not supported? Or what?

    Thanks

    • miniZ says:

      Hi Ali,

      Try adding -cd 0 to your command line.
      For older Kepler GPUs, you need to explicitly tell the miner to use them.

      Let us know if this helps.
      Cheers

  48. Shaun says:

    Hey I am having problems with miniz and Polaris GPU with flux mining it is saying opencl kernel0: cl_invalid_worker_group_size

    • miniZ says:

      Hi Shaun,
      Sorry to take a bit longer to reply.
      Thank you for the feedback. We detected the error and fixed it.
      It will be working in the next version.
      Cheers

  49. UselessGuru says:

    MiniZ-v1.8 (all versions)How can I select OpenCL devices? For CUDA there is –cuda-devices, but I cannot find anthing like it for OpenCL.

    • miniZ says:

      Hi UselessGuru,
      You can continue to use -cd for OpenCL devices.
      To list all devices use -ci.
      To select only nvidia/amd you can use --nvidia/--amd.
      Hope this can help.
      Cheers

  50. UselessGuru says:

    I tried this (assuming RX 5700 is AMD device 2)miniZ.exe –par=144,5 –smart-pers –ocX –url [email protected]:3345 –pass a=equihash-144_5,n=XXXXXXXXX,o=XXXXXXX –jobtimeout=900 –retries=99 –retrydelay=1 –stat-int 10 –latency –all-shares –extra –tempunits C –show-pers –fee-time=60 –telemetry 4005 –amd –cuda-devices 2and get this:************ miniZ v1.8z3 ************miniZ: Excluding GPU#1 RX 580Number of OpenCL[OpenCL 2.1 AMD-APP (3380.6)] devices found: 2Driver: 512.15Algo: EQ[144,5] [smart-pers]Pool#0: user[xxxxxxxxxxxxxxxx] server[eu.prohashing.com] port[3345] ssl[no] pers[BgoldPoW]Telemetry: [http://localhost:4005]Temp. limit: [90 C][INFO ] Mining fee set to 2.00%miniZ<144,5>[20:0:00.0: 8176]: Selecting GPU#2[0] AMD Radeon RX 5700 XT[FATAL ] GPU[02]: cannot program to device: CL_INVALID_VALUE[INFO ] Disconnecting from eu.prohashing.com

  51. UselessGuru says:

    Thanks for your prompt response. I cannot get this to work.
    I want to be able to run the miner with ONE selected amd card only (same as it can be done with nvidia).

    >To list all devices use -ci.

    This is the output:

    miniZ.exe -ci
    Number of miniZ CUDA>=[8.0] using driver CUDA[11.60] devices found: 2
    #0 MSI GeForce GTX 1660 Super Gaming X 6G | SM version: 7.5 | SM count: 22 | cores: 1408 | Memory: 5.047GB | BusID: 0000:0b:00.0
    #1 ASUS GeForce GT 1030 | SM version: 6.1 | SM count: 3 | cores: 384 | Memory: 1.621GB | BusID: 0000:10:00.0
    #2 Radeon RX 580 Series | SM version: | SM count: 36 | cores: 0 | Memory: 8.000GB | BusID: 0000:01:00.0
    #3 AMD Radeon RX 5700 XT | SM version: | SM count: 20 | cores: 0 | Memory: 7.984GB | BusID: 0000:09:00.0
    Number of OpenCL[Advanced Micro Devices, Inc.] devices found: 2

    >To select only nvidia/amd you can use –nvidia/–amd.

    I tried this (assuming RX 5700 is AMD device 2)

    miniZ.exe –par=144,5 –smart-pers –ocX –url [email protected]:3345 –pass a=equihash-144_5,n=XXXXXXXXX,o=XXXXXXX –jobtimeout=900 –retries=99 –retrydelay=1 –stat-int 10 –latency –all-shares –extra –tempunits C –show-pers –fee-time=60 –telemetry 4005 –amd –cuda-devices 2

    and get this:

    ************ miniZ v1.8z3 ************
    miniZ: Excluding GPU#1 RX 580
    Number of OpenCL[OpenCL 2.1 AMD-APP (3380.6)] devices found: 2
    Driver: 512.15
    Algo: EQ[144,5] [smart-pers]
    Pool#0: user[xxxxxxxxxxxxxxxx]
    server[eu.prohashing.com] port[3345] ssl[no] pers[BgoldPoW]
    Telemetry: [http://localhost:4005]
    Temp. limit: [90 C]
    [INFO ] Mining fee set to 2.00%
    miniZ<144,5>[20:0:00.0: 8176]: Selecting GPU#2[0] AMD Radeon RX 5700 XT
    [FATAL ] GPU[02]: cannot program to device: CL_INVALID_VALUE
    [INFO ] Disconnecting from eu.prohashing.com

    • miniZ says:

      Hi UselessGuru,
      Thank you for the information.
      The issue is: miniZ doesn’t support RX 5700 XT. 🙁
      We’ll see if we can fix this soon.
      Cheers

  52. UselessGuru says:

    The device numbering is inconsistent:NVIDIA starts with 0:************ miniZ v1.8z3 ************Number of miniZ CUDA>=[8.0] using driver CUDA[0.00] devices found: 2miniZ: Excluding GPU#0 NVIDIA GeForce GTX 1660 SUPERminiZ: Excluding GPU#1 NVIDIA GeForce GT 1030AMD starts with 1:************ miniZ v1.8z3 ************miniZ: Excluding GPU#1 RX 580miniZ: Excluding GPU#2 RX 5700 XTNumber of OpenCL[OpenCL 2.1 AMD-APP (3380.6)] devices found: 2

  53. UselessGuru says:

    miniZ.exe -ci Number of miniZ CUDA>=[8.0] using driver CUDA[11.60] devices found: 2 #0 MSI GeForce GTX 1660 Super Gaming X 6G | SM version: 7.5 | SM count: 22 | cores: 1408 | Memory: 5.047GB | BusID: 0000:0b:00.0 #1 ASUS GeForce GT 1030 | SM version: 6.1 | SM count: 3 | cores: 384 | Memory: 1.621GB | BusID: 0000:10:00.0 #2 Radeon RX 580 Series | SM version: | SM count: 36 | cores: 0 | Memory: 8.000GB | BusID: 0000:01:00.0 #3 AMD Radeon RX 5700 XT | SM version: | SM count: 20 | cores: 0 | Memory: 7.984GB | BusID: 0000:09:00.0 Number of OpenCL[Advanced Micro Devices, Inc.] devices found: 2

    • miniZ says:

      Hi UselessGuru,
      Thanks! We got the issue.
      For now, you can use -cd option instead of --cuda-devices.
      It will be fixed in the next release.
      Cheers

  54. Random Miner says:

    I was trying to use miniz with some 6700xt’s but it gives a kernel error in hiveos? Works GREAT on 6600XT though, ~4 sols improvement from lol/gminer. Actually makes the AMD cards usable for flux if the 6700xt could see the same improvements.

    I am on the latest hive/AMD drivers version.

    I would love to see the 5700xt added as well so that I could run all the cards on a single miner.

    • miniZ says:

      Hi Random Miner,
      We’re working to fix this. It should work well for the 6700XT in the next version.
      Support for the 5700xt will also be added.
      Cheers

  55. Foz says:

    I’m having low hashrate, low core clock and low voltage on my laptop 1070. From the beginning when I first started mining everything was at a higher rate but now slowly has become so low. I get below 20sols on the 192_7 ZERO_PoW. My overclock seems to make no difference. When mining I get below 1000mhz core clock 60watt, whilst I should be getting 1600mhz overclock 120watt. Please email me with update and solutions for my nvidia 1070.

    • miniZ says:

      Hi Foz,
      We’re about to reply on Twitter.
      Do you notice that the temperature is higher now, when compared with the beginning you mention? Do you mean when you start miniZ?
      Which miniZ version are you using? Was this happening with previous versions also?
      You may need to opt for lowering the PL, and using --oc1 or --oc2. Let us know if this helps.
      Let us know how it goes.
      Cheers

  56. Diego says:

    I have a 2080 ti that is giving error cuda error 74Do you have any idea why OCCore = 170Memory = 700in windows

    • miniZ says:

      Hi Diego,
      This issue should be related to your OCs.
      We’re not sure what algo are you mining. For example, for Flux we usually use the Eco70 settings we share here (Linux).
      On Windows, Eco70, the OCs for our 2080Ti would be: core = +160, memory = +500, PL = 210 W. These might work for you, but it is likely that you need to adjust for your system a little.
      Hope this helps. Let us know how it goes.
      Cheers

  57. nik says:

    [FATAL] Ошибка API драйвера CUDA = 0700 из строки 261

    • miniZ says:

      Hi nik,
      This is an unspecific error.
      Which algo are you mining?
      Could you try the new version and see if this issue persists? If so, could you paste here your command line?
      Thanks.
      Cheers

  58. WereWolf says:

    hi, got trouble on hiveos, with miniZ 1.9z3. AMD rig 2x6700xt (XFX) 2×6800 (1 Founder, 1 PowerColor), Powercolor one stay at 6sol, can’t up like the founder one at 90sol: 0>RX 6800 100% [68.C/69%] 43.78 I/s 87.20(87.41)Sol/s 179(194.8)W clk=2000MHz mclk=1000MHz Sol/W=0.449 1>RX 6700 XT 100% [65.C/34%] 29.95 I/s 58.86(58.90)Sol/s 100(100.0)W clk=2000MHz mclk=1000MHz Sol/W=0.589 2>RX 6800 100% [44.C/34%] 2.96 I/s 6.00( 5.90)Sol/s 72( 71.8)W clk=2000MHz mclk=1000MHz Sol/W=0.082 3>RX 6700 XT 100% [56.C/34%] 27.07 I/s 54.51(54.11)Sol/s 92( 93.5)W clk=2000MHz mclk=1000MHz Sol/W=0.579Trying to let OC stock but nothing change

    • miniZ says:

      Hi WereWolf,
      Could you try the new release v1.9z4 and see if it helps?
      We’ve introduced a few new kernels maybe these will help.
      Let us know how it goes.
      Cheers

      • WereWolf says:

        Hi, sorry but nothing change, same card stay at 6 sol, I try to reboot rig but same problem (with or without OC).

        • miniZ says:

          Hi WereWolf,
          Thank you for the feedback.
          Do you get the same behavior with other miners?
          Or other equihash algo like 144,5?
          Cheers

  59. simovich says:

    Instead of using hard coded OpenCL library path, try to use normal linux LD_LIBRARY_PATH, strace found several hard coded paths.

    • miniZ says:

      Hi simovich,
      Thank you for your suggestion.
      You can use LIBOPENCL_SO_PATH. Is this useful for you still?
      We’ll add LD_LIBRARY_PATH.
      Cheers

  60. killzill says:
     hello Im having a problem with one of my rigs: 1660 supers, I mining flux on equihash 125/4. I t keeps crashing down after around 15min, 30min. I m seeing this error below on hiveshell. I have the latest hiveos, latest miniz, and nvidia drivers 495.46.
    Do you know what this error means or what can I do to fix it?
    
    
     
     4>  GTX 1660 SUPER      100%   [  45°C  /65%] 12.25 I/s   24.44  (24.44)Sol/s  69( 69.0)W clk=1410MHz mclk=6801MHz Sol/W=0.354   5>  GTX 1660 SUPER      100%   [  47°C  /65%] 12.23 I/s   24.40  (24.40)Sol/s  72( 72.3)W clk=1410MHz mclk=6801MHz Sol/W=0.337  [FATAL  ]   GPU[5]: CUDA error 77 'an illegal memory access was encountered' in line 304  [INFO   ]   QUIT miniZ  [INFO   ]   Disconnecting from flux-eu.minerpool.pro                                                                                                                                                                                                                       miniz   exited (exitcode=0), waiting to cooldown a bit                                                                                                                                                                                                                       Skipping miner log rotation due to execution time < 30sec 
    • miniZ says:

      Hi killzill,
      This error is related to OCs.
      Try to adjust your OC settings a little and try again.
      Let us know if this helps.
      Cheers

  61. Rok says:

    Hello, I have a problem with mining BitcoinZ. Miner is set up correctly and when started it shows this:

    https://files.fm/f/dft5cgu7y

    and after some time it goes to 0 sol/s :

    https://files.fm/f/b5q5ns6jh

    i tried clen install of drivers but it did not work.

     

    • miniZ says:

      Hi Rok,
      Could you try the new version v2.0a? It should be running OK now.
      Thanks for the feedback.Let us know how it goes
      Cheers

    • miniZ says:

      Hi aminer,
      Thank you for your message.
      Are you still observing this issue?
      Have you checked if the configuration for failoverpool was well?
      We found no issue with this. The miner is connecting well to 2nd pool.
      Could it be that the pool was down? Both servers?…
      Cheers

    Leave a Reply

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

    I accept the Privacy Policy