Pages:
Author

Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 22. (Read 60122 times)

member
Activity: 695
Merit: 17
Hello,

I have big problems with MiniZ since I changed algo 144.5 to 192.7.

Lots of invalid shares and the miner reboots after a while. In 8 times last night he rebooted 8x.

I am on SimpleMiningOS and also on EasyMiningOS, the same problem is present on both OS and is happening to me on all my Nvidia 1080ti 1070gtx 2070rtx 2080ti rigs.

I have asked several people to mine the same algo and they also suffer from invalid shares.

I was advised to decrease the OC but it didn't have much effect. I still have invalid shares leaving the base frequencies and decreasing the watts.

My question is therefore, as this algo is used very little is that there is always an optimization concerning this algo. I had to go back to Gminer, I lost all 60sol but I have no invalid or no reboot of the miner.

Thank you.
Hi Quentin0208,
Thanks for the feedback.
We did not manage to reproduce your issue. Could you give us some more information?
 
Which miniZ version are you using?
Also, could you paste here your command line, and the beginning of the log when the miner starts?

We'll try to replicate the behaviour.
Cheers
newbie
Activity: 6
Merit: 0
Hello,

I have big problems with MiniZ since I changed algo 144.5 to 192.7.

Lots of invalid shares and the miner reboots after a while. In 8 times last night he rebooted 8x.

I am on SimpleMiningOS and also on EasyMiningOS, the same problem is present on both OS and is happening to me on all my Nvidia 1080ti 1070gtx 2070rtx 2080ti rigs.

I have asked several people to mine the same algo and they also suffer from invalid shares.

I was advised to decrease the OC but it didn't have much effect. I still have invalid shares leaving the base frequencies and decreasing the watts.

My question is therefore, as this algo is used very little is that there is always an optimization concerning this algo. I had to go back to Gminer, I lost all 60sol but I have no invalid or no reboot of the miner.

Thank you.
member
Activity: 695
Merit: 17
no github, or sourcecode?
i need to compile for cuda 9.1
Hi mirny,
miniZ is not an opensource project.
If you cannot upgrade the NVIDIA driver, you can use CUDA 8 version.
It should perform as well as a 9.1 version.
Cheers
legendary
Activity: 1108
Merit: 1005
no github, or sourcecode?
i need to compile for cuda 9.1
newbie
Activity: 23
Merit: 0
Yes, it works fine now. Thanks!
member
Activity: 695
Merit: 17

Thank you for the answer!

Here is command line:
Code:
.\miniZ.exe --url=28acc5ea73280ffea8a8d2a61358f7c500c0c9eb132b0b3bb15eeb63f52fea65a3e@beam-eu.leafpool.com:3333 --par=beam3 --log --ocX


Hi Xadja,
To mine Beam to LeafPool you need to indicate that it is a ssl connection port. Most (if not all) Beam pools use ssl ports.

In this case, the command line needs 'to know' that the port is ssl:
Code:
.\miniZ.exe --url=ssl://28acc5ea73280ffea8a8d2a61358f7c500c0c9eb132b0b3bb15eeb63f52fea65a3e@beam-eu.leafpool.com:3333 --par=beam3 --log --ocX

You'll see that in the log now appears ssl[yes]. It should work now.

Let us know if this solved your issue.
Thanks for for the feedback and for using miniZ. Smiley
Cheers
newbie
Activity: 23
Merit: 0
Hi Xadja,
Could you tell us what algo are you mining, and the command line you are using?
Also, could you paste here the start of the log? We mean the log information that miniZ prints, before it starts mining.
Maybe we'll be able to understand what is going on then.
Thanks!
Cheers
Thank you for the answer!

Here is command line:
Code:
.\miniZ.exe --url=28acc5ea73280ffea8a8d2a61358f7c500c0c9eb132b0b3bb15eeb63f52fea65a3e@beam-eu.leafpool.com:3333 --par=beam3 --log --ocX


Here is log:
Code:
************ miniZ v1.6v5 ************
Number of CUDA[10.0] devices found: 1
Algo: EQ[beam3]
Pool#0: user[28acc5ea73280ffea8a8d2a61358f7c500c0c9eb132b0b3bb15eeb63f52fea65a3e]
server[beam-eu.leafpool.com] port[3333] ssl[no] pers[Beam-PoW]
Telemetry: [http://localhost:20000]
Logging:: file[miniZ.log] period[10] delay[0]
Optimisation: ocX[0]
member
Activity: 695
Merit: 17
Guys, Why do I have 0 hashrate?
Code:
miniZ<144,5s>[06:0:00:6747]: Selecting GPU#0[0] GeForce RTX 2060 SUPER
[ 0d 0h 0m06s] 0>RTX 2060 SUPER ` 100% [45°C/ 0%] 0.00 I/s 0.0(0.0)Sol/s  42( 42.2)W clk=1470MHz mclk=6801MHz Sol/W=0.00
[ 0d 0h 0m10s] 0>RTX 2060 SUPER ` 100% [45°C/ 0%] 0.00 I/s 0.0(0.0)Sol/s  42( 42.2)W clk=1470MHz mclk=6801MHz Sol/W=0.00
[ 0d 0h 0m20s] 0>RTX 2060 SUPER ` 100% [45°C/ 0%] 0.00 I/s 0.0(0.0)Sol/s  42( 41.5)W clk=1470MHz mclk=6801MHz Sol/W=0.00
I tried to use miniZ on different machines and got the same result.
Thanks.
Hi Xadja,
Could you tell us what algo are you mining, and the command line you are using?
Also, could you paste here the start of the log? We mean the log information that miniZ prints, before it starts mining.
Maybe we'll be able to understand what is going on then.
Thanks!
Cheers
member
Activity: 695
Merit: 17

That's OC1. OC2 works, but I see no improvement over 1.5t2.
About running with less GPUs - I cannot try that. I'm only able to remote control my rigs at the moment. Maybe set the miner only to use 1 GPU.
Hi MineOrDie,
Thanks for the feedback.
We're looking into it.
We were suggesting to mine with less gpus but not physically removing the GPUs, by using -cd, for example. Smiley
Cheers
newbie
Activity: 23
Merit: 0
Guys, Why do I have 0 hashrate?
Code:
miniZ<144,5s>[06:0:00:6747]: Selecting GPU#0[0] GeForce RTX 2060 SUPER
[ 0d 0h 0m06s] 0>RTX 2060 SUPER ` 100% [45°C/ 0%] 0.00 I/s 0.0(0.0)Sol/s  42( 42.2)W clk=1470MHz mclk=6801MHz Sol/W=0.00
[ 0d 0h 0m10s] 0>RTX 2060 SUPER ` 100% [45°C/ 0%] 0.00 I/s 0.0(0.0)Sol/s  42( 42.2)W clk=1470MHz mclk=6801MHz Sol/W=0.00
[ 0d 0h 0m20s] 0>RTX 2060 SUPER ` 100% [45°C/ 0%] 0.00 I/s 0.0(0.0)Sol/s  42( 41.5)W clk=1470MHz mclk=6801MHz Sol/W=0.00
I tried to use miniZ on different machines and got the same result.
Thanks.
jr. member
Activity: 75
Merit: 1
Hi MineOrDie,
Thank you for all the feedback. It is really important since it helps us to make miniZ better.

We could not reproduce this issue. Have you tried to run it with --oc1 or --oc2? Also, does it work if you run with less GPUs?
(Btw, f11 was only working for 144,5, it was removed on version 1.5u and now it is ignored.)

It is a bit frustrating for us when we cannot reproduce the issues, it becomes much harder to fix them.
We'll keep looking into this.
Cheers
Code:
miniZ<125,4>[14:0:00:2904]: Selecting GPU#1[1] GeForce GTX 1060 3GB
miniZ<125,4>[14:0:00:2904]: Selecting GPU#5[5] GeForce GTX 1060 3GB
miniZ<125,4>[14:0:00:2904]: Selecting GPU#3[3] GeForce GTX 1060 3GB
miniZ<125,4>[14:0:00:2904]: Selecting GPU#2[2] GeForce GTX 1060 3GB
miniZ<125,4>[14:0:00:2904]: Selecting GPU#4[4] GeForce GTX 1060 3GB
miniZ<125,4>[16:0:00:2814]: Selecting GPU#0[0] GeForce GTX 1060 3GB
[FATAL  ] Cannot load deviceZ code.
[INFO   ] Disconnecting from zel.2miners.com
[INFO   ]zel.2miners.com Stopping miner
[INFO   ] Miner monitor exited.

That's OC1. OC2 works, but I see no improvement over 1.5t2.
About running with less GPUs - I cannot try that. I'm only able to remote control my rigs at the moment. Maybe set the miner only to use 1 GPU.
member
Activity: 695
Merit: 17

Well, it's a hell of an unstable kernel then. I cannot even run it on 0 / 0. Just adjusting my power. I'm reverting back to 1.5t2. Can you test it out on a 1060 3GB?
Hi MineOrDie,
Do you also have issues with t3?
Thanks for your feedback, we are going to look into it carefuly.
Cheers
Nope, t3 has that strange memory allocation bug on 3GB cards mining ZEL. Then I think there was another version that had a bug that caused the miner to operate in mode 10 even if I'm running Windows 8.1.
The latest one fixed everything, but it's a mess again...
I know you work hard, so really appreciate it.
Hi MineOrDie,
Thank you for all the feedback. It is really important since it helps us to make miniZ better.

We could not reproduce this issue. Have you tried to run it with --oc1 or --oc2? Also, does it work if you run with less GPUs?
(Btw, f11 was only working for 144,5, it was removed on version 1.5u and now it is ignored.)

It is a bit frustrating for us when we cannot reproduce the issues, it becomes much harder to fix them.
We'll keep looking into this.
Cheers
jr. member
Activity: 75
Merit: 1

Well, it's a hell of an unstable kernel then. I cannot even run it on 0 / 0. Just adjusting my power. I'm reverting back to 1.5t2. Can you test it out on a 1060 3GB?
Hi MineOrDie,
Do you also have issues with t3?
Thanks for your feedback, we are going to look into it carefuly.
Cheers
Nope, t3 has that strange memory allocation bug on 3GB cards mining ZEL. Then I think there was another version that had a bug that caused the miner to operate in mode 10 even if I'm running Windows 8.1.
The latest one fixed everything, but it's a mess again...
I know you work hard, so really appreciate it.
member
Activity: 695
Merit: 17

Well, it's a hell of an unstable kernel then. I cannot even run it on 0 / 0. Just adjusting my power. I'm reverting back to 1.5t2. Can you test it out on a 1060 3GB?
Hi MineOrDie,
Do you also have issues with t3?
Thanks for your feedback, we are going to look into it carefuly.
Cheers
jr. member
Activity: 75
Merit: 1
Mining ZEL on 1060 3GB, Windows 10, latest drivers.

Code:
[FATAL  ] GPU[4]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL  ] GPU[1]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL  ] GPU[2]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL  ] GPU[0]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL  ] GPU[3]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL  ] GPU[5]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[INFO   ] Disconnecting from zel.2miners.com
[INFO   ]zel.2miners.com Stopping miner
[INFO   ] Miner monitor exited.
[INFO   ] Exited main loop

Can you help me out? Same OC settings like on 1.5.

Hi MineOrDie,
These CUDA errors you're getting really seam related to OCs.
Because we did changes to the kernels it can happen that some adjustments to the OC are required too.
It is possilbe that it became unstable to only one of the GPU. You can start by adjusting the first one that gave the error, however if the rig crashes again maybe it is good to adjust the others.
Let us know if you managed to make it more stable.
Cheers
Well, it's a hell of an unstable kernel then. I cannot even run it on 0 / 0. Just adjusting my power. I'm reverting back to 1.5t2. Can you test it out on a 1060 3GB?
member
Activity: 695
Merit: 17
Mining ZEL on 1060 3GB, Windows 10, latest drivers.

Code:
[FATAL  ] GPU[4]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL  ] GPU[1]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL  ] GPU[2]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL  ] GPU[0]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL  ] GPU[3]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL  ] GPU[5]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[INFO   ] Disconnecting from zel.2miners.com
[INFO   ]zel.2miners.com Stopping miner
[INFO   ] Miner monitor exited.
[INFO   ] Exited main loop

Can you help me out? Same OC settings like on 1.5.

Hi MineOrDie,
These CUDA errors you're getting really seam related to OCs.
Because we did changes to the kernels it can happen that some adjustments to the OC are required too.
It is possilbe that it became unstable to only one of the GPU. You can start by adjusting the first one that gave the error, however if the rig crashes again maybe it is good to adjust the others.
Let us know if you managed to make it more stable.
Cheers
member
Activity: 695
Merit: 17
Hi, miniZ! Can you add a hotkey for starting ocX again? My rig is crashed on the exit and I must restart comp every times. I use W7 with ConEmu.
Thanks for the nice miner, bro! Smiley
Hi Star65,
Thank you for contacting us.
We are not sure whether we have properly understood your suggestion Smiley
Maybe, you can clarify us a little, giving a few more details?
Cheers
jr. member
Activity: 75
Merit: 1
Mining ZEL on 1060 3GB, Windows 10, latest drivers.

Code:
************ miniZ v1.6v5 ************
Number of CUDA[10.0] devices found: 6
Algo:           EQ[125,4]
Pool#0:         user[t1SNnYcs4Z4u9uKPLDMfBzVWfDbtkCs8Pwb.RIG2-1060GAMINGX-3GB]
                server[zel.2miners.com] port[19090] ssl[yes] pers[ZelProof]
Optimisation:   f11[0 1 2 3 4 5]
Temp. limit:    [90°C]
miniZ<125,4>[00:0:00:2904]: Selecting GPU#3[3] GeForce GTX 1060 3GB
miniZ<125,4>[00:0:00:2904]: Selecting GPU#5[5] GeForce GTX 1060 3GB
miniZ<125,4>[00:0:00:2904]: Selecting GPU#2[2] GeForce GTX 1060 3GB
miniZ<125,4>[16:0:00:2807]: Selecting GPU#0[0] GeForce GTX 1060 3GB
miniZ<125,4>[00:0:00:2904]: Selecting GPU#1[1] GeForce GTX 1060 3GB
miniZ<125,4>[00:0:00:2904]: Selecting GPU#4[4] GeForce GTX 1060 3GB
[ 0d 0h 0m06s] S:  0/0 237(236.7)Sol/s 137(137.1)W [zel.2miners.com]- 38ms
 0>GTX 1060 3GB S:  0/0 [43°C/44%] 0.00 I/s 0.0(0.0)Sol/s  24( 24.1)W clk=1328MHz mclk=3007MHz Sol/W=0.00
 1>GTX 1060 3GB S:  0/0 [43°C/43%] 0.00 I/s 0.0(0.0)Sol/s  23( 23.4)W clk=1379MHz mclk=3007MHz Sol/W=0.00
 2>GTX 1060 3GB S:  0/0 [39°C/40%] 0.30 I/s 0.8(0.8)Sol/s  22( 21.5)W clk=1366MHz mclk=3007MHz Sol/W=0.04
 3>GTX 1060 3GB S:  0/0 [44°C/44%] 0.00 I/s 0.0(0.0)Sol/s  23( 22.6)W clk=1303MHz mclk=3007MHz Sol/W=0.00
 4>GTX 1060 3GB S:  0/0 [42°C/42%] 0.00 I/s 0.0(0.0)Sol/s  23( 22.8)W clk=1366MHz mclk=3007MHz Sol/W=0.00
 5>GTX 1060 3GB S:  0/0 [45°C/45%] 0.30 I/s 0.8(0.8)Sol/s  23( 22.6)W clk=1316MHz mclk=3007MHz Sol/W=0.03
[ 0d 0h 0m10s] S:  0/0 224(224.3)Sol/s 137(137.1)W [zel.2miners.com]- 38ms
 0>GTX 1060 3GB S:  0/0 [43°C/44%] 7.95 I/s 15.9(15.9)Sol/s  24( 24.1)W clk=1328MHz mclk=3007MHz Sol/W=0.66
 1>GTX 1060 3GB S:  0/0 [43°C/43%] 8.96 I/s 17.9(17.9)Sol/s  23( 23.4)W clk=1379MHz mclk=3007MHz Sol/W=0.76
 2>GTX 1060 3GB S:  0/0 [39°C/40%] 8.40 I/s 16.8(16.8)Sol/s  22( 21.5)W clk=1366MHz mclk=3007MHz Sol/W=0.78
 3>GTX 1060 3GB S:  0/0 [44°C/44%] 8.49 I/s 16.9(16.9)Sol/s  23( 22.6)W clk=1303MHz mclk=3007MHz Sol/W=0.75
 4>GTX 1060 3GB S:  0/0 [42°C/42%] 0.00 I/s  0.0( 0.0)Sol/s  23( 22.8)W clk=1366MHz mclk=3007MHz Sol/W=0.00
 5>GTX 1060 3GB S:  0/0 [45°C/45%] 8.63 I/s 17.2(17.2)Sol/s  23( 22.6)W clk=1316MHz mclk=3007MHz Sol/W=0.76
[FATAL  ] GPU[4]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL  ] GPU[1]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL  ] GPU[2]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL  ] GPU[0]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL  ] GPU[3]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[FATAL  ] GPU[5]: CUDA error 6 'the launch timed out and was terminated' in line 1380
[INFO   ] Disconnecting from zel.2miners.com
[INFO   ]zel.2miners.com Stopping miner
[INFO   ] Miner monitor exited.
[INFO   ] Exited main loop

Can you help me out? Same OC settings like on 1.5.
member
Activity: 109
Merit: 13
Hi, miniZ! Can you add a hotkey for starting ocX again? My rig is crashed on the exit and I must restart comp every times. I use W7 with ConEmu.
Thanks for the nice miner, bro! Smiley
jr. member
Activity: 212
Merit: 6
Hi, yes, 1.6v5 fixed that problem for me, thanks.
Pages:
Jump to: