miniZ v1.8z3 is out!
Hi everyone,
A new miniZ version v1.8z3 is out with improved and increased support for AMD GPUs.
For detailed changelog, read below.
Please find miniZ version v1.8z3
@ Download page.
Changelog:
- Added support for AMD GPUs RX 6600/6800/6900 (XT).
- Added support for AMD RX 590.
- Reduced stale shares on Aion.
- Improved stability.
- Minor bug fixes.
NOTE: If you only have AMD GPUs then use --amd option to prevent the miner from getting stuck on the message LoadLibrary “nvcuda.dll” failed!
*** Thank you all for the feedback! ***
Remember to try --oc1/--oc2/--ocX options for optimum performance. (NVIDIA only)
For additional information check our Usage or FAQ pages.
*** Download miniZ version v1.8z3 here. ***
Engage, feedback and support
Because your feedback is very important, miniZ kindly encourages you to use the comment box below for general questions and feedback.
Certainly we will strive to help you with any doubt and provide a solution to any problem you may encounter. In case you need to reach us, please check the Support page.
Follow us
On Twitter
Our thread on bitcointalk.org
We wish you a fast and friendly mining experience!
Hi, thanks for adding other AMD, unfortunately I have a problem. MiniZ v1.8z3 seems to freeze and does not show any information but actually works. I can only monitor in telemetry and in the pool. As in telemetry for AMD shows only how much Sols/s is in at the moment, no other information. For Nvidia, everything is correct.Regards
Hi Ivan,
Thank you for the feedback.
These issues are related – freezing the output and the incomplete information in telemetry.
It seems that the miner is waiting for GPU information (temperature, etc).
What OS are you using? Could you paste here the output of running miniZ with
-ci(only this option)?Cheers
Hi miniZ, OS is Windows 11 and AMD 6600XT.Everything works perfectly differently, just nothing is visible when started. Visible only in telemetry or in the poolNumber of miniZ CUDA>=[8.0] using driver CUDA[11.60] devices found: 4 #0 MSI GeForce RTX 3070 Ti | SM version: 8.6 | SM count: 48 | cores: 6144 | Memory: 6.959GB | BusID: 0000:07:00.0 #1 MSI GeForce RTX 3060 Ti | SM version: 8.6 | SM count: 38 | cores: 4864 | Memory: 6.993GB | BusID: 0000:0b:00.0 #2 Nvidia GeForce RTX 3060 Ti | SM version: 8.6 | SM count: 38 | cores: 4864 | Memory: 6.993GB | BusID: 0000:0c:00.0 #3 Palit GeForce RTX 3070 Ti | SM version: 8.6 | SM count: 48 | cores: 6144 | Memory: 6.959GB | BusID: 0000:0d:00.0 #4 AMD Radeon RX 6600 XT | SM version: | SM count: 16 | cores: 0 | Memory: 7.984GB | BusID: 0000:0a:00.0Number of OpenCL[Advanced Micro Devices, Inc.] devices found: 1
This is only with Nvidia 0>RTX 3070 Ti 100% [38 C/43%] 34.66 I/s 69.16(69.16)Sol/s 71( 71.2)W clk=2192MHz mclk=9492MHz Sol/W=0.972 1>RTX 3060 Ti 100% [33 C/41%] 25.78 I/s 51.43(51.43)Sol/s 59( 58.6)W clk=2153MHz mclk=6974MHz Sol/W=0.878 2>RTX 3060 Ti 100% [36 C/42%] 25.20 I/s 50.27(50.27)Sol/s 58( 58.0)W clk=1462MHz mclk=3702MHz Sol/W=0.866 3>RTX 3070 Ti 100% [35 C/41%]*34.97 I/s 69.77(69.77)Sol/s 42( 41.7)W clk=1222MHz mclk=5636MHz Sol/W=1.674
0MSI GeForce RTX 3070 Ti5633.2466.066.00.35187.93/0/0
1MSI GeForce RTX 3060 Ti5024.8249.949.90.36139.31/0/0
2Nvidia GeForce RTX 3060 Ti5724.8548.448.40.35139.40/0/0
3Palit GeForce RTX 3070 Ti5634.3067.167.10.36187.91/0/0
4AMD Radeon RX 6600 XT011.6023.823.8inf0.01/0/0
Hi Ivan,
Thanks a lot for the information.
We’ll see if we can understand and resolve the issue.
Cheers
Hi ..
I already mining with solo flux start from 1 june 2022 until today, the question : how long the payout will be made? And how to check the running process ?
Hi Vicent,
With solo mining you’ll only get a reward when you find a block.
If you mine with a special solo mining pool, you can follow the progress there.
You can read more about this, for example, here https://2miners.com/blog/how-the-mining-pool-works-pplns-vs-solo/
Cheers
On the page of the new version of MiniZ (v1.8z3), it would be good to specify to activate the “–amd” function to prevent the miner from getting stuck on the message LoadLibrary “nvcuda.dll” failed!
Hi .Yumiya,
Thanks for the suggestion, we’ve added a note to the release post!
Cheers
Hello. I am mining SERO on pool.sero.cash with miniZ last release. The worker ID is not managed correctly. It is always displayed as 0 on the pool.How can I help you to correct this? Thank you for your work.
Working flawlessly on rtx, but on my 6800, i cant see anything showing up on the miner itself, windowsCant wait for 5xxx series, got a bunch of 5500 and 5600 that i want to mine flux with, keep up the good work
Hi Ruben,
Thanks for the information.
Are you using the latest version v1.8z3?
Which OS are you using?
We’ll see if we can understand the issue with the AMD 6800.
Cheers
Hey, sorry for the late reply, the issue is happening with both my 6800, i cant test any other at the moment, im running windows on the last version, the miner is running (gpus too because i can feel the heat and amd software is reporting wattage) but the miner is not “showing” it. Pool also detects that i have it runningCheers
Hi Ruben,
Do you get any error or warning on the console?
Could you paste here the output of running
miniZ.exe -ci?Thanks.
Cheers
Something is not right with new version in hive. I have gpu 0 as 480, gpu1 as 6600xt, gpu 2 2070 super, gpu 3 6600xt, gpu 4 3060ti and gpu 5 570. When i use –cd 1 2 3 in hive os it picks 6600xt, 6600xt and 3060ti. Should be picking 6600xt, 2070 super, and 6600xt.seem like there something wrong with the selection not sure. Seems like it wont let me pick 2070 super no matter what number I use.
Hi Mike,
In the command line run
./miniZ -ciThis will list all gpus, and you’ll be able to see the order that miniZ uses.
Check if this order is the same that you mentioned.
Cheers
Hi, The settings –gpuclock and –memclock seems to be completely ignored in the bat file when mining on Windows, is that for Linux only?It would be nice if it worked for Windows as well.
Hi Lombard,
The options work with Windows (we need to have a look ate
--memclock…) but you need to run the bat file as administrator.Just open a console – “Run as administrator” (read here). Or read here for another example, by creating a shortcut.
Let us know if this helps.
Cheers
I tried to use miniz on Hive with a 6700xt but it just gives an error:
[ERROR ] GPU[09]: cannot load kernelZ! It works fine on the 6600xt though if I disable the 6700 in the options. Also it would be really nice if the 5700 series could be added as I will have to run a separate miner just for that one card as it is.Hi Home miner,
We may have solved this issue already.
Could you paste here the output of running miniZ with -ci option?
miniZ.exe -ciWe’ll support 5700 in the next release.
Cheers
ASRock RX 590 GME8 GB 08:00.0 , Hynix GDDR5, 113-EXT800151-L01 BIOS??????
Hi MOHSEN.
Could you paste here the miner’s output message?
Thanks.
Cheers
Support for Navi 56/57 series?
Hi John D,
miniZ will support AMD 5600/5700(XT) GPUs in the next release.
Cheers
I’m trying to get my Nvidia cards (2×3060, 3060ti, 3070) and 1 6700XT to mine Flux in HiveOS. I can’t get it to mine with both Nvidia/AMD or just AMD by itself using —AMD. It pops up “cannot load kernalZ.” Any ideas for fixes?
Hi Bob,
Thank you for the feedback.
We think we already understand the issue.
It should be fixed on the next release.
Cheers
Its Work With Driver 488 b4 update..OS : Ubuntu 22.04 LTS************ miniZ v1.8z3 ************Number of miniZ CUDA>=[8.0] using driver CUDA[0.00] devices found: 1Segmentation fault (core dumped)NVIDIA-SMI 510.73.05 Driver Version: 510.73.05 CUDA Version: 11.6Number of miniZ CUDA>=[8.0] using driver CUDA[11.60] devices found: 1 #0 MSI GeForce RTX 3080
Hi CCMT,
Thank you.
We could not reproduce the issue.
Could you paste here your command line?
Cheers
Without config ..just :./miniZ************ miniZ v1.8z2 ************Number of miniZ CUDA>=[8.0] using driver CUDA[0.00] devices found: 1Segmentation fault (core dumped)
Hi CCMT,
Does this also happen with version v1.8z3?
Could you try adding miniZ
--nvidiato your command line? Does this help?Let us know how it goes.
Cheers
ok its work now with ./miniZ –nvidia
Correction : ./miniZ –Nvidia
Hi CCMT,
Good to know that it worked.
Thank you for the feedback.
Cheers
Hey TeamLove that you added AMD support for Flux. I can run and work around the issue in Windows 11. Only small thing is not stats is coming through around frequency temps ect. In hive if its a mixed rig it just flat out doesnt want to start. But otherwise looking good. Do you have a date in mind for the next release?
Hi 2nd TL Mining,
We’re working on the new release. Having a look at this issue with Hive. Thanks for the information.
Planning to post the new version next week.
Cheers
Hi all just a heads up. I have a mixed rig and NVIDIA on miniZ for Flux and AMD on teamred for ETH. Recentlyc i had my amd cards coming up with Card detected dead, and after much searching I found that switching from 1.8z3 to 1.8z2 solved my problem.Almost like there was a conflict between the two miners, a strange anomaly that showed up was that it looked like the AMD cars was trying to mine both ETH and FLUX(sol’s)Hope this helps someone else
Hi Philip Nel,
Thank you for sharing.
We’re not sure we understand the issue. However, it is possible that miniZ is trying to mine with all cards in your rig. Both nvidia and amd cards.
If you want miniZ to mine with only nvidia cards you need to explicitly mention this in the command line. You can use
--nvidia, or explicitly refer to each card using-cd(or-cdeto exclude) options.For more information read here.
Let us know if this helps.
Cheers
Hey TeamGetting the Kernel error on 6700XT. Any dates for support for the 6700XT?
Hi 2nd Time Lucky,
We’re working on the new release.
Planning to post the new version next week.
Cheers
hi. i am new user
and i would to ask community, most powerful forum engine is?
mybb etc? thanks digg
hi, i m using v1.8z3 with amd6800 mining Flux 61.6sol/162w on windows10/64bit , but it haven’t show clk/mclk/watt in program , how can i fix it?
Hi eric,
We’ll have a look. Which driver version are you using?
Thanks!
Cheers
With the merge around the corner I was doing some testing on my Gaming machines to see what I would do after ETH.
My plan was to put them on Flux but sadly the built in overclocking support will not work for this. Some of the issues I faced when testing:
The built in overclocking totally screws up the System overclocks requiring a restart to fix it
It does not reset the overclocks when you exit the miner
Does not support core offset overclocks (which work best on flux most of the time). Sometimes locked core + offset works good but you need the offset for sure on a core intensive algo, that is what undervolts and allows higher efficiency.
P.S. The 6700xt does not work for me on Hive. Saw above this should be fixed in the next release?
Hi Gamer,
We’re having a look at this, however it may not be fully functional in the next version. The AMDs do not have this option yet.
You can reset the clocks by setting the option to 1. We’ll try to implement the reset when exiting for the next release.
Also, the 6700XT should be working on Hive in the next release.
Thanks for your message with valuable information.
Cheers
Hello,Does the AMD RX 6750XT will be supported?Thank you
Hi Nicolas,
Thanks for your message.
Yes, the RX 6750 XT will be supported in the next release.
Cheers
Hey TeamCurious if you have a date target for the new version? Super excited to get my AMD GPU’s rocking on Flux 😉
Hi 2nd Time Lucky Mining,
We think that it will be out September 1-2.
Thanks for using miniZ!
Cheers
Hi miniZ, it was really nice to lock core clock, set memclock, power limit and fan speeds in other miners (Trex,NBminer). Is miniZ capable of doing this?I found the following commands–memclock, –gpuclock, -plIs gpuclock = core clock and can you lock this? Is memclock an offset or absolute? Is power a percentage or wattage? Can fan speeds be implemented?
Hi Mike,
Sorry about taking longer to reply. Somehow your message got mixed with spam.
miniZ is able to lock core and memory clocks, and you can also set PL.
In the next release you’ll be able to control fan too.
With
--memclock,--gpuclock, and--poweryou set absolute values (in MHz and W).Sudo (Linux) or administrator priviledges (Windows) are required.
At the moment these options are only available for nvidia GPUs.
We’ll try to implement this for AMDs, in the future.
Cheers
ps: Let us know if you find any issue(s) with any of these options.
Thanks for the response miniZ. Is there any plans to make core clock and mem clock offsettable as well? I am assuming gpuclock = core clock is that correct? Cant wait till fan speed on next release.
Hi Mike,
Yes, gpuclock refers to core clock. 🙂
Making core/mem clocks offsettable is not a priority at the moment, but we’ll think about it.
Thanks for the suggestion!
Cheers
Hello,I am running an AMD rig with 6800’s, 6800xt, 5700’s, 5700xt’s and a rx 580 on HiveOS.When I create a flight sheet for FLUX, the flight sheet is created fine but when I go to the rig page/flight sheet. It isn’t showing up. I have rebooted, etc. Do you have any suggestions.Thanks
Hi Jon,
Currently, miniZ supports your RX 6800’s and RX 580. We’re preparing the new release with better support for AMD, including RX 5700’s.
Howver, at the moment HiveOS marks miniZ as Nvidia miner only. We think that this is causing your issue.
We’ll see what we can do to fix this.
Cheers
I keep getting load average too high when running equihash on my 6600xt. It will run sometimes for 4 hours and sometimes for 12 hours. Then the load average goes crazy. Any idea? Running on hive os 1600mhz 675 core 1130 memory clock 1275 memory voltage soc freq 990 soc vddmax 800driver 21.40.1 (5.13.0201) hive 0.6-219@220828
Hi Mike,
We need to have a look at this, to understand what is going on.
Thanks for the feedback!
Cheers
Hi Dears
good day and Tnx for all your efforts
I am using hive os and flux pools to mine Flux and I am using Miniz for my 12x 6800XT, I am also having same config for my 12x 2060S. The Nvidia rig has no issue and working super stable for the past 7 days but on the other hand the AMD rig is so unreliable and unstable.
my OC seems to be so ok with 67 sol/s per GPU and the miner works fine for 3-4 hrs and sometimes for 7-8 hrs and then it crashes in a way that it must be manually restarted. Wit gminer everything is stable but the hashrate drops to 56 sol/s.
All my drivers and Hive os are upgraded to latest version but still not much of progress.
Hi SAM,
This should be related to OCs.
Could you adjust them a little and check again?
You can also use the latest version v1.9z3.
Thanks!
Cheers