miniZv2.3c Equihash144,5 125,4 210,9 150,5 192,7 Beam ProgPoW Ethash CFX KLS PYI

[miniZ]

some gpu stop mining on 12 gpu rig.... and the miner not restart when mining zero.... can u fix this?

Hi! I keep on getting the same mistake with Miniz 1.4 mining zelcash: "cuda error 4...error in line 864". The rig consists of 6x1080, drivers updated. Please specify what does it mean?

Hi ayiphelmy, Alex356,
It looks that this is related to your OC settings, probably the driver has crashed and the GPU is unstable.
Could you try adjusting your OC values?
Let us know if this suggestion helped and it solved your issue.
Thanks!
Cheers

[Alex356]

Hi ayiphelmy, Alex356,
It looks that this is related to your OC settings, probably the driver has crashed and the GPU is unstable.
Could you try adjusting your OC values?
Let us know if this suggestion helped and it solved your issue.
Thanks!
Cheers

Hi Miniz! Thanks for the prompt feedback. You mean the cards are overclocked? If so, I'll decrease the boost params and see if it helps. Best Regards!

[$@X]

@miniZ It appears the high CPU usage is on my rig with RTX 2060 cards. I happens with both the recent beta and the newest release.

On my rig with GTX 1080s it has normal CPU usage.

On a positive note, the latest beta has fixed the issue where GPU usage would stop randomly for short periods of time.

Thanks for your work!

[somaton]

$@X: remove your current driver from your system with 2060 and install 431.60 driver. I think you will not have that problem with high cpu usage after this.

[$@X]

@somaton You are correct! I switched to driver 431.60 and CPU usage returned to normal. Thank you!

[filko]

https://ibb.co/pywBLXW
You can restart the miner or wait half an hour. And so it was every day for a month. I returned to the Gminer - the problem is gone.
1060 - Win7. 1070 -Win10

[miniZ]

Hi ayiphelmy, Alex356,
It looks that this is related to your OC settings, probably the driver has crashed and the GPU is unstable.
Could you try adjusting your OC values?
Let us know if this suggestion helped and it solved your issue.
Thanks!
Cheers

Hi Miniz! Thanks for the prompt feedback. You mean the cards are overclocked? If so, I'll decrease the boost params and see if it helps. Best Regards!

Hi Alex356,
did you make any modifications to you OC?
Let us know how it goes!
Cheers

[miniZ]

@miniZ It appears the high CPU usage is on my rig with RTX 2060 cards. I happens with both the recent beta and the newest release.

On my rig with GTX 1080s it has normal CPU usage.

On a positive note, the latest beta has fixed the issue where GPU usage would stop randomly for short periods of time.

Thanks for your work!

$@X: remove your current driver from your system with 2060 and install 431.60 driver. I think you will not have that problem with high cpu usage after this.

Hi $@x, somaton,
thanks for the feedback.
Good that it worked for you.
Could you let us know which driver version caused the high CPU usage?
Cheers

[miniZ]

You can restart the miner or wait half an hour. And so it was every day for a month. I returned to the Gminer - the problem is gone.
1060 - Win7. 1070 -Win10

Hi filko,
thanks for the information.
Do you mean that the miner stops mining?
Could you let us know which miniZ version are you using?

On the latest version you can adjust some connection parameters that may solve your issue (ex. --jobtimeout=900).
Others have reported that it helped: https://bitcointalk.org/index.php?topic=4767892.msg52453403#msg52453403.
Cheers

[filko]

You can restart the miner or wait half an hour. And so it was every day for a month. I returned to the Gminer - the problem is gone.
1060 - Win7. 1070 -Win10

Hi filko,
thanks for the information.
Do you mean that the miner stops mining?
Could you let us know which miniZ version are you using?

On the latest version you can adjust some connection parameters that may solve your issue (ex. --jobtimeout=900).
Others have reported that it helped: https://bitcointalk.org/index.php?topic=4767892.msg52453403#msg52453403.
Cheers

The first minutes of the video card sequentially make short stops (not simultaneously). Miner does not stop and finds shares. The pool does not see the miner. Miner does not show the transition to another pool. After half an hour, everything is restored. --jobtimeout = 900 does not change anything. The last miner. Everything is perfect with the gminer

[miniZ]

The first minutes of the video card sequentially make short stops (not simultaneously). Miner does not stop and finds shares. The pool does not see the miner. Miner does not show the transition to another pool. After half an hour, everything is restored. --jobtimeout = 900 does not change anything. The last miner. Everything is perfect with the gminer

Hi filko,
thanks for your message!
We're trying to replicate the error.
In case you run miniZ again, could you paste here the miner console/logfile output when it stops mining?
Cheers

[filko]

The first minutes of the video card sequentially make short stops (not simultaneously). Miner does not stop and finds shares. The pool does not see the miner. Miner does not show the transition to another pool. After half an hour, everything is restored. --jobtimeout = 900 does not change anything. The last miner. Everything is perfect with the gminer

Hi filko,
thanks for your message!
We're trying to replicate the error.
In case you run miniZ again, could you paste here the miner console/logfile output when it stops mining?
Cheers

Your log does not display real time. Sync files yourself. File creation time 14:10-14:14. The pause lasted an hour.
miniZ.exe --url=ssl://XXXXXXXXXXXXXXXX.1060@beam-eu.leafpool.com:3333 --par=150,5 --pers=Beam-PoW --templimit=70c --telemetry=0.0.0.0:42000 -cd  0 1 2 3 --jobtimeout=900 --log
https://ibb.co/g9Vy7tZ
https://ibb.co/kKXpsrQ
https://my-files.ru/gqv3qn

[miniZ]

The first minutes of the video card sequentially make short stops (not simultaneously). Miner does not stop and finds shares. The pool does not see the miner. Miner does not show the transition to another pool. After half an hour, everything is restored. --jobtimeout = 900 does not change anything. The last miner. Everything is perfect with the gminer

Hi filko,
thanks for your message!
We're trying to replicate the error.
In case you run miniZ again, could you paste here the miner console/logfile output when it stops mining?
Cheers

Your log does not display real time. Sync files yourself. File creation time 14:10-14:14. The pause lasted an hour.
miniZ.exe --url=ssl://XXXXXXXXXXXXXXXX.1060@beam-eu.leafpool.com:3333 --par=150,5 --pers=Beam-PoW --templimit=70c --telemetry=0.0.0.0:42000 -cd  0 1 2 3 --jobtimeout=900 --log

Hi filko,
thank you very much for your patience, and for this information,
We will analyze it and try to solve your issue.
Cheers

[crypt_fr]

Hello guys,
I don't see miniZ listed on https://equihub.pro/. Too bad cause an Equihash-only mining pool seems like a perfect fit for you! 😉
They've got a Telegram and a discord if you want to contact them: https://t.me/EquiHub, https://discordapp.com/invite/CkbPGxs.
Cheers

[miniZ]

Hello guys,
I don't see miniZ listed on https://equihub.pro/. Too bad cause an Equihash-only mining pool seems like a perfect fit for you! 😉
They've got a Telegram and a discord if you want to contact them: https://t.me/EquiHub, https://discordapp.com/invite/CkbPGxs.
Cheers

Hi crypt_fr,
thank you for your suggestion.
We've just contacted them.
Cheers

[Kringel]

This happened on different rigs several times before, but only today I managed to catch the error details on my test rig:

https://ibb.co/t3zQ7k6

The annoying thing here is not the error itself (which, BTW, is not permanent and could be resolved just by continuing trying) but the fact that after stopping (but not exiting!) MiniZ keeps reporting the last average hashrate to the Nicehash client so the latter one thinks that all is fine and does not restart the miner to resolve the situation.

https://ibb.co/vZBNDP9

[miniZ]

This happened on different rigs several times before, but only today I managed to catch the error details on my test rig:

https://ibb.co/t3zQ7k6

The annoying thing here is not the error itself (which, BTW, is not permanent and could be resolved just by continuing trying) but the fact that after stopping (but not exiting!) MiniZ keeps reporting the last average hashrate to the Nicehash client so the latter one thinks that all is fine and does not restart the miner to resolve the situation.

https://ibb.co/vZBNDP9

Hi Kringel,
thanks for the feedback. We are working on this now.

We will make sure miniZ doesn't get stuck reporting the last average hashrate, when it stops mining.
Does this error happen often? This looks like a bug on the pool side, we are working on a few possible workarounds for this.

We plan to release a new version by the end of the week and this should be taken care of.
Cheers
    

[MineOrDie]

So is there any connection issue with miniZ and Sparkpool again? Can someone confirm? I cannot connect my rigs to sparkpool mining BEAM.

[miniZ]

So is there any connection issue with miniZ and Sparkpool again? Can someone confirm? I cannot connect my rigs to sparkpool mining BEAM.

Hi MineOrDie,
we've just tested and it runs fine.
Could you paste here the error? Which miniZ version are you using?
Cheers

[MineOrDie]

So is there any connection issue with miniZ and Sparkpool again? Can someone confirm? I cannot connect my rigs to sparkpool mining BEAM.

Hi MineOrDie,
we've just tested and it runs fine.
Could you paste here the error? Which miniZ version are you using?
Cheers

It just cannot connect to Sparkpool and retries every 5 seconds. I'm using 1.5q6.