Pages:
Author

Topic: Zealot/Enemy (z-enemy) NVIDIA GPU miner (ver2.6.2 - kawpow RavenCoin). - page 34. (Read 107046 times)

member
Activity: 81
Merit: 16
Hey gues i have problem on 1 of my rig. Some times i getting ERROR: GPU#2: GeForce GTX 1080 Ti >>> unspecified launch failure

Any suggestion ??


POWER 75%
CORE 100+
MAM 0+


Thanks !




Try to reduce intensity GPU#2 or reduce OC  ( core +50-70)

Mean intensity in *.cmd like  :  -i 20,20,19,20,20,20   ( Rig 6 GPU)
newbie
Activity: 9
Merit: 0
Hey gues i have problem on 1 of my rig. Some times i getting ERROR: GPU#2: GeForce GTX 1080 Ti >>> unspecified launch failure

Any suggestion ??


POWER 75%
CORE 100+
MAM 0+


Thanks !

newbie
Activity: 92
Merit: 0
Am i the only one having problem with xevan ?
I tried many pools and each time all my shares are rejected. Others algorithms are working well with latest release but not xevan... I have no problems with ccminer-xevan...

Any ideas ?

You only one. Show your  ***xevan.cmd  file or check pool:port

Ok sorry i found my error. A stupid error ! I was sending a bad argument in my command line. Everything is ok now. Just a bad copy paste....
member
Activity: 81
Merit: 16
Am i the only one having problem with xevan ?
I tried many pools and each time all my shares are rejected. Others algorithms are working well with latest release but not xevan... I have no problems with ccminer-xevan...

Any ideas ?

You only one. Show your  ***xevan.cmd  file or check pool:port
newbie
Activity: 92
Merit: 0
Am i the only one having problem with xevan ?
I tried many pools and each time all my shares are rejected. Others algorithms are working well with latest release but not xevan... I have no problems with ccminer-xevan...

Any ideas ?
newbie
Activity: 57
Merit: 0
On some algo (e.g. PHI1612), enemy initialize my cards very slowly ( 10+GPU rigs on W10, 390+ ), I mean minutes.
I have experienced this "issue" with ccminer too, but a "--cuda-schedule 12" command solve my problem without high CPU usage (if I use any other number as 12 my CPU usages go to the moon and the system becomes unmanageable).
In enemy, I tried all options:

--cuda-schedule     set CUDA scheduling option:
  0: BlockingSync (default)
  1: Spin
  2: Yield

but unfortunatelly did not help (max CPU usage, except with 0).

Can you add the "old / original" --cuda-schedule options?
newbie
Activity: 54
Merit: 0
Running it for 2 hours, loving it so far, thanks a lot.

Quick question btw... One rig I got... 5x 1070 1x 1060... how should I calc the -d difficulty?

How much does this affect hashing?

I just put -d 20 in there seems to be going ok.. but should probably be higher.. no?

Thanks again.

Check first page, but -p d=20 good too for you on  x16r

O sorry man missed that on the fist page. I put d=28 for 5x1070 1x 1060.... and d=20 for 4x 1070.. should be good now?
jr. member
Activity: 39
Merit: 1
jr. member
Activity: 138
Merit: 2
Globalcurrency -100% backed by gold
I m testing the 1.09 version, thanks you for your work.

Did you solve the problem "Stratum connection interrupted" ?

Thanks
newbie
Activity: 84
Merit: 0
- Now supporting failover pool! It is now possible to add additional pools incase your main pool loses stratum connection. Here is an example for your .bat file:
z-enemy -a x16r -o stratum+tcp://ravenminer.com:6666 -u RFQXKVKpHMwyJ86YqQUJSZK1S8m8oRbC5h -p d=16 -o stratum+tcp://krawww-miner.eu:3636 -u RFQXKVKpHMwyJ86YqQUJSZK1S8m8oRbC5h -p d=3

This i really good.
What's the failover mechanism? like once it's switched to secondary pool, how long does it take to re-connect to the main pool?
member
Activity: 81
Merit: 16
about DDOS the message was not for you.
Btw , did  you check - difficulty 25348.673 ?
member
Activity: 308
Merit: 10
many pools x16r had a problem with DDOS
i dont see yuiimp was affected by ddos, my hashrate graph is stable for last few days.
also if there was any ddos on some pools that should affect networks hashratem but if it didnt affect yiimp, that actually should increase my daily earnings but it didnt, so im confused even more now.
member
Activity: 81
Merit: 16
many pools x16r had a problem with DDOS
member
Activity: 308
Merit: 10
x16rr is doing well so far, but overall earnings is dropped on latest version.
Not sure if its caused by network hashrate increaso so will keep wathcing
newbie
Activity: 92
Merit: 0
Hello,
There's also a problem with xevan, at least on zergpool. All my shares were rejected. Switching back to ccminer xevan make things back to normal...
newbie
Activity: 19
Merit: 0
Miner just seems to stop mining at certain points, nothing is happening, no crash, just stops mining like it's in pause mode. Checking MSI Afterburner, all clocks are dropped down like it's not mining anything and miner screen is just sitting on idle. Is this a known issue? I have 8x 1080 ti rig using this new 1.09a version. It's been paused like this for 10 minutes now, I will be restarting it in a minute.

Update: I was about to restart it but I just decided to hit backspace to see if something happened and soon as I did it kick started again? Then I got this:

[ERROR  ] 18/05/09 22:52:56 submit_upstream_work stratum_send_line failed
[ERROR  ] 18/05/09 22:52:56 ...retry after 30 seconds
[ERROR  ] 18/05/09 22:52:56 Stratum authentication failed
[ERROR  ] 18/05/09 22:52:56 ...retry after 30 seconds
[ERROR  ] 18/05/09 22:53:26 submit_upstream_work stratum_send_line failed
[ERROR  ] 18/05/09 22:53:26 ...retry after 30 seconds
[ERROR  ] 18/05/09 22:53:27 Stratum authentication failed
[ERROR  ] 18/05/09 22:53:27 ...retry after 30 seconds
[ERROR  ] 18/05/09 22:53:56 submit_upstream_work stratum_send_line failed
[ERROR  ] 18/05/09 22:53:56 ...retry after 30 seconds
[ERROR  ] 18/05/09 22:53:57 Stratum authentication failed
[ERROR  ] 18/05/09 22:53:57 ...retry after 30 seconds
[ERROR  ] 18/05/09 22:54:26 submit_upstream_work stratum_send_line failed
[ERROR  ] 18/05/09 22:54:26 ...retry after 30 seconds
[ERROR  ] 18/05/09 22:54:28 Stratum authentication failed
[ERROR  ] 18/05/09 22:54:28 ...retry after 30 seconds

And then after a few more retries it kicked in and is working again.

Few more pauses have occurred, some for 2mins, some for shorter, but I don't know if it's because Suprnova is overloaded with 11k miners or what the deal is. Switching back to 1.08 overnight and switching to 1.09 in the morning when I can monitor it again.


Same problems , on more pools. There is some kinda of problema .
Which drivers are you guys using ?
ULF
newbie
Activity: 75
Merit: 0
Hey guys I'm using a GTX 760 2g card. with the latest Nvidia drivers installed. And the miners says this:

[INFO   ] 18/05/08 16:14:44 zealot/enemy-1.08 miner
[INFO   ] 18/05/08 16:14:44 NVIDIA CUDA 9.1
[INFO   ] 18/05/08 16:14:44 Dev fee is 1.0%
[NOTICE ] 18/05/08 16:14:44 Starting on stratum+tcp://rvn-eu.coinblockers.com:4449
[INFO   ] 18/05/08 16:14:44 GPU monitoring enabled (NVAPI).
[ERROR  ] 18/05/08 16:14:44 GPU#0: Unsupported compute capability device. Ignoring
[INFO   ] 18/05/08 16:14:44 Mining 'x16r' with 0 thread.
[X16    ] 18/05/08 16:14:44 Hashorder algorithm legend: Slow Medium Fast
[WARNING] 18/05/08 16:14:45 New difficulty: 1.125 (0.00439)
[NOTICE ] 18/05/08 16:14:45 Block 203461, difficulty 21649.000
[NOTICE ] 18/05/08 16:14:56 Block 203462, difficulty 21649.000

Why is my Card not supported?
probably gtx760 doesnt support cuda 9.1 as its quite old GPU generation, did you check it?

:face_palm:  2.2.5 job

Unfortunately our zealot-1.09a does not support old video cards.

What about Gigabyte GTX 750ti 2GB OC Version?
Is not many years old...Is 2GB enough for enemy miner?
Card works never a problem with CCMiner 2.2.4 and SPMod2
I use it for setup, instead of take miner off job.
Should it work?  
member
Activity: 81
Merit: 16
Running it for 2 hours, loving it so far, thanks a lot.

Quick question btw... One rig I got... 5x 1070 1x 1060... how should I calc the -d difficulty?

How much does this affect hashing?

I just put -d 20 in there seems to be going ok.. but should probably be higher.. no?

Thanks again.

Check first page, but -p d=20 good too for you on  x16r
newbie
Activity: 54
Merit: 0
Running it for 2 hours, loving it so far, thanks a lot.

Quick question btw... One rig I got... 5x 1070 1x 1060... how should I calc the -d difficulty?

How much does this affect hashing?

I just put -d 20 in there seems to be going ok.. but should probably be higher.. no?

Thanks again.
member
Activity: 93
Merit: 10
Miner just seems to stop mining at certain points, nothing is happening, no crash, just stops mining like it's in pause mode. Checking MSI Afterburner, all clocks are dropped down like it's not mining anything and miner screen is just sitting on idle. Is this a known issue? I have 8x 1080 ti rig using this new 1.09a version. It's been paused like this for 10 minutes now, I will be restarting it in a minute.

Update: I was about to restart it but I just decided to hit backspace to see if something happened and soon as I did it kick started again? Then I got this:

[ERROR  ] 18/05/09 22:52:56 submit_upstream_work stratum_send_line failed
[ERROR  ] 18/05/09 22:52:56 ...retry after 30 seconds
[ERROR  ] 18/05/09 22:52:56 Stratum authentication failed
[ERROR  ] 18/05/09 22:52:56 ...retry after 30 seconds
[ERROR  ] 18/05/09 22:53:26 submit_upstream_work stratum_send_line failed
[ERROR  ] 18/05/09 22:53:26 ...retry after 30 seconds
[ERROR  ] 18/05/09 22:53:27 Stratum authentication failed
[ERROR  ] 18/05/09 22:53:27 ...retry after 30 seconds
[ERROR  ] 18/05/09 22:53:56 submit_upstream_work stratum_send_line failed
[ERROR  ] 18/05/09 22:53:56 ...retry after 30 seconds
[ERROR  ] 18/05/09 22:53:57 Stratum authentication failed
[ERROR  ] 18/05/09 22:53:57 ...retry after 30 seconds
[ERROR  ] 18/05/09 22:54:26 submit_upstream_work stratum_send_line failed
[ERROR  ] 18/05/09 22:54:26 ...retry after 30 seconds
[ERROR  ] 18/05/09 22:54:28 Stratum authentication failed
[ERROR  ] 18/05/09 22:54:28 ...retry after 30 seconds

And then after a few more retries it kicked in and is working again.

Few more pauses have occurred, some for 2mins, some for shorter, but I don't know if it's because Suprnova is overloaded with 11k miners or what the deal is. Switching back to 1.08 overnight and switching to 1.09 in the morning when I can monitor it again.

I'm getting the same error also on Suprnova. It works fine with Suprminer.
Pages:
Jump to: