miniZv2.5e Equihsh144,5 125,4 210,9 150,5 192,7 Beam ProgPoW Ethash CFX IRON KLS

[miniZ]

Hello

After update to v2.3c report hrate it is broke, mest up


aka instead report a ~37 Sol/s it report ~19 Sol/s, command line it same for bouth, nothing change

Code:

:loop
.\miniZ.exe --url=X@equihash192.eu.mine.zpool.ca:2192 --pass c=X,zap=YEC/ZCL/ZER --par=192,7 --pers=auto --cuda-devices=0 --coolui --list-modes --show-mode --telemetry=0 --server-share --log --log-period 30 --log-delay 30
timeout /t 5
goto loop

cheers

im seeing same as sir_blacks.  Cut hashrate by like 1/2.  Rolled back to 2.2 and full hash again.

Please fix…its nice to just leave miner on latest version. 

Hi sir_blacks, miner29,

Thank you for your messages.
We're about to release a new version.
Could you check it out and let us know if issue persists?
This should be resolved now.
Cheers

[miniZ]

equihash 144,5 for BTG has huge hashrate drop vs 2.2c.

Hi arch111,
Could you check the new version and let us know if this is ok now?
If not let us know which GPU are you using.
Maybe, pool also.
Thanks!
Cheers

[miniZ]

Hi everyone,

A new miniZ version v2.4d is out with improvements for KarlsenHash and PyrinHash algorithms.

Also, added AMD support for Equihash 192,7, PyrinHash, and KarlsenHash algos!

Maybe there is still some room for improvement on the dual mining. Let us know about your favorite algo combinations and we will have a look!

Please find miniZ version v2.4d @ Download page



Changelog:

* Improved hashrate for PyrinHash and KarlsenHash. Up to 7%, this depends on GPU.
* Added support for PyrinHash algo - Pyrin (PYI), for AMD. Fee: 0.8%.
* Added support for KarlsenHash algo - Karlsen (KLS), Nexell-ia for AMD. Fee: 0.8%.
* Added support for 192,7 algo, for AMD.
* Added new option -pl auto. miniZ will find best power when optimizing for efficiency.
* Major improvements for Equihash dual mining.
* Fixed issues with dual mining with k1pool.
* Fixed EthashB3 (HYP), for AMD.
* Added support for RX 7800 XT, AMD GPU.
* Fixed invalid shares in 192,7.
* Added ZIL stats to telemetry. Ex: localhost:20000/zil
* Added --minimal, --hideclocks options for minimal console log output.
* Fixed JSON getsats for dual mining.
* Removed support for obsolete Kepler GPUS.
* Removed support for kHeavyHash algo.
* Few minor fixes.

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

For additional information check our Usage or FAQ pages.

Download miniZ latest version here.

Follow us on X/Twitter

Happy dual/triple mining!

[miniZ]

Too many rejects with 2.3c mining 125.4, back to 2.2c and again 0 rejects. Kernel number is shown like "0019", not "19" like with older versions and because of this console window looks very messy with multigpu rigs -> info per gpu does not feet to one line like it was before, now it takes two lines, that second one is almost empty.

Hi somaton,

Could you check the new version and let us know how it goes?
It should be working well now.

Thanks!
Cheers

[miniZ]

v2.3c
ZIL mining hashrate not available in API.

Hi angelbs,
You can check ZIL stats:

Code:

curl 'localhost:20000?/getstat"id":2' -s|jq

You can now also check ZIL stats on localhost:20000/zil 
Cheers

[miniZ]

hey guys I am trying to mine some equihash 144,5 coins and it works great on both my RX 5700 and my RX 5700 XT but not w5700 pro (the card works great on other algos and/or other miners but miniz is by far faster)

Tried to downgrade version but all I get is this:

any clues? currently I have to use another miner on the w5700 that is slower

Hi Sikkan666,
Sorry, this is not yet resolved in the new version.
Please try adding --mode3=22 to your command line. This will run mode 22 in GPU#3.
Let us know if this helps.
Cheers

[somaton]

Hi, did not had time to check 125.4 with new version, but tried 125.4 + pyrin and it does not work. Is it me or something else?

************ miniZ v2.4d ************
Number of miniZ CUDA>=[.] using driver CUDA[12.00] devices found: 1
Driver:      528.49
Algo:      [Equihash125,4] [smart-pers]
Pool#0:    user[xxx.5950x] server[zelhash.auto.nicehash.com] port[9200] ssl[no] var[ZelProof]
Pool#1:    user[xxx.5950x] server[pyrinhash.auto.nicehash.com] port[9200] ssl[no] var[pyrin]
Logging::    file[miniz-pyrin-125.4-nice.log] period[10] delay[0]
Optimisation:   ocX[0]
Temp. limit:   [90 C]
[INFO   ] Mining fee set to 2.00%
[INFO   ] Applying clocks to GPU[00] core offset= +240MHz mem offset=   +1MHz power=  0W gpuclk=1560
miniZ<Equihash125,4+pyrin>[18:0:00.0: 9087]: Selecting GPU#0[0] Gigabyte RTX3080 Gaming OC 10G

It is crashing right after selecting gpu. Tried with 2.3c and it does start mining, but it is mining 125.4 only and does not show anything about pyrin?

[miniZ]

Hi, did not had time to check 125.4 with new version, but tried 125.4 + pyrin and it does not work. Is it me or something else?

************ miniZ v2.4d ************
Number of miniZ CUDA>=[.] using driver CUDA[12.00] devices found: 1
Driver:      528.49
Algo:      [Equihash125,4] [smart-pers]
Pool#0:    user[xxx.5950x] server[zelhash.auto.nicehash.com] port[9200] ssl[no] var[ZelProof]
Pool#1:    user[xxx.5950x] server[pyrinhash.auto.nicehash.com] port[9200] ssl[no] var[pyrin]
Logging::    file[miniz-pyrin-125.4-nice.log] period[10] delay[0]
Optimisation:   ocX[0]
Temp. limit:   [90 C]
[INFO   ] Mining fee set to 2.00%
[INFO   ] Applying clocks to GPU[00] core offset= +240MHz mem offset=   +1MHz power=  0W gpuclk=1560
miniZ<Equihash125,4+pyrin>[18:0:00.0: 9087]: Selecting GPU#0[0] Gigabyte RTX3080 Gaming OC 10G

It is crashing right after selecting gpu. Tried with 2.3c and it does start mining, but it is mining 125.4 only and does not show anything about pyrin?

Hi somaton,
Thanks for the message.
Could you paste here your command line?
Cheers

[somaton]

Here:

miniZ.exe --url=btc.5950x@zelhash.auto.nicehash.com:9200 --url2=btc.5950x@pyrinhash.auto.nicehash.com:9200 --pass=x --priority=1 --telemetry=0 --minimal --logfile miniz-pyrin-125.4-nice.log --gpuclock=1560 --fanspeed=42 --fantemp=65 --gpuoffset=240

lets hope it can be fixed fast

[miniZ]

Here:

miniZ.exe --url=btc.5950x@zelhash.auto.nicehash.com:9200 --url2=btc.5950x@pyrinhash.auto.nicehash.com:9200 --pass=x --priority=1 --telemetry=0 --minimal --logfile miniz-pyrin-125.4-nice.log --gpuclock=1560 --fanspeed=42 --fantemp=65 --gpuoffset=240

lets hope it can be fixed fast

Hi somaton,
Thanks for the information.
We were able to run your command line...
Could it be that it didn't crash that it's just taking a bit longer to start?
Could you also try with stock settings, just to discard some issue with OCs?
Let us know if this helps.
Cheers

[somaton]

Of course i tried without any oc settings. Like i said, previous version starts fine with same command line (without --minimum), but this new one not. I run miniz from bat file with loop command, and it will open one more window for miniz, but it will be closed right after miniz it triying to select gpu, then again open new window and will not stop until bat with loop command is closed manually.

Tried with other rig, same story - exiting right after selecting gpu:

************ miniZ v2.4d ************
Number of miniZ CUDA>=[.] using driver CUDA[12.00] devices found: 1
Driver:      528.49
Algo:      [Equihash125,4] [smart-pers]
Pool#0:    user[xxx.5950x] server[zelhash.auto.nicehash.com] port[9200] ssl[no] var[ZelProof]
Pool#1:    user[xxx.5950x] server[pyrinhash.auto.nicehash.com] port[9200] ssl[no] var[pyrin]
Logging::    file[miniz-pyrin-125.4-nice.log] period[10] delay[0]
Optimisation:   ocX[0]
Temp. limit:   [90 C]
[INFO   ] Mining fee set to 2.00%
[INFO   ] Applying clocks to GPU[00] core offset= +240MHz mem offset=   +1MHz power=  0W gpuclk=1560
miniZ<Equihash125,4+pyrin>[19:0:00.0: 7113]: Selecting GPU#0[0] ASUS GeForce RTX 3070

mining just pyrin or 125.4 is working fine, but not together.

[somaton]

and still too much stales/rejects with 2.4d like with 2.3c when mining 125.4, so, back again to 2.2c

[miniZ]

and still too much stales/rejects with 2.4d like with 2.3c when mining 125.4, so, back again to 2.2c

Hi somaton,

Thank you for the feedback.

Could you try adding --stale=200 (or maybe 300) to your command line and see if it helps?

Cheers

[Sikkan666]

hey guys I am trying to mine some equihash 144,5 coins and it works great on both my RX 5700 and my RX 5700 XT but not w5700 pro (the card works great on other algos and/or other miners but miniz is by far faster)

Tried to downgrade version but all I get is this:

any clues? currently I have to use another miner on the w5700 that is slower

Hi Sikkan666,
Sorry, this is not yet resolved in the new version.
Please try adding --mode3=22 to your command line. This will run mode 22 in GPU#3.
Let us know if this helps.
Cheers

hey, it actually started mining on the card.. crashed after a few mins but that was probably due to a bad OC for this algo.. and also, it had the same speed as the other cards

what does mode 22 do?

[miniZ]

hey guys I am trying to mine some equihash 144,5 coins and it works great on both my RX 5700 and my RX 5700 XT but not w5700 pro (the card works great on other algos and/or other miners but miniz is by far faster)

Tried to downgrade version but all I get is this:

any clues? currently I have to use another miner on the w5700 that is slower

Hi Sikkan666,
Sorry, this is not yet resolved in the new version.
Please try adding --mode3=22 to your command line. This will run mode 22 in GPU#3.
Let us know if this helps.
Cheers

hey, it actually started mining on the card.. crashed after a few mins but that was probably due to a bad OC for this algo.. and also, it had the same speed as the other cards

what does mode 22 do?

Hi Sikkan666,

Thanks for your message.

In some cases you may want to select a specific mode/kernel for miniZ to run in your GPU.

In this case --mode3=22 selects mode/kernel 22 to run on GPU3. (miniZ was not selecting the correct kernel for your GPU.)

It is possible that some kernels do become unstable and others do not, when applying OCs. Have you tried adjusting OCs?

In any case, we appreciate that you leave us a message if a mode is dramatically unstable also after trying with stock settings.

Cheers

[somaton]

Hi somaton,

Thank you for the feedback.

Could you try adding --stale=200 (or maybe 300) to your command line and see if it helps?

Cheers

Hi, i tried --stale=300 and it does not help, still too much rejects compared to 2.2c.

[TBOEMC]

Hello there,
I am not able to run 2.4d
In the same rigs, drivers, cards, settings (OC and without OC), AV exceptions (or OFF).
New version only "blinks" for about 0,5sec and closes. No erros, no warnings.
Version 2.2 runs good and stable.
Also tried just run standalone miner with just doubleclick - the same result.

[somaton]

192.7 stopped working with latest and older versions few days ago. Working only for first ~30min, then stops. Dev-fee server problem? Same with different pools.

[miniZ]

Hi everyone,

A new miniZ  version v2.4d2 is out with various fixes and added support for MeowPow (MEWC).

Thank you all for your feedback and suggestions!

Please find miniZ version v2.4d2 @ Download page



Changelog:

 * Added support for MeowPow algo - MeowCoin (MEWC). Fee: 1.0%.
 * Fixed memory leak on ProgPow family algorithms.
 * Fixed BEAM (144,5s) mining on Windows.
 * Fixed GRIMM (150,5) mining on Windows.
 * Fixed AION (210,9) mining on Windows.
 * Few minor fixes.

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

For additional information check our Usage or FAQ pages.

Download miniZ latest version here.

Follow us on X/Twitter

Happy mining!

192.7 stopped working with latest and older versions few days ago. Working only for first ~30min, then stops. Dev-fee server problem? Same with different pools.

Hi somaton,
Thanks for your message.
It should be running OK now.
Cheers

[moderator's note: consecutive posts merged]

[miniZ]

Hello there,
I am not able to run 2.4d
In the same rigs, drivers, cards, settings (OC and without OC), AV exceptions (or OFF).
New version only "blinks" for about 0,5sec and closes. No erros, no warnings.
Version 2.2 runs good and stable.
Also tried just run standalone miner with just doubleclick - the same result.

Hi TBOEMC,
Thank you for your feedback.
Could you please try the new version v2.4d2, and let us know if the issue is resolved?
Cheers