EWBF's CUDA Zcash miner

[usernameisalreadyinuse]

Dont hate me, but I would like explanation on --fee option
I get that it controls amount of devfee, but setting it to 0 (testing purposes ) still shows devfee shares. So my question really is, what does value 0 default to? 2%? Again, I dont have anything against devfee, just setting the value to 0 is misleading IMHO. Tested on 0.3.3b version. Did not try on 0.3.4b

[1714777936]

1714777936

[1714777936]

1714777936

[1714777936]

1714777936

[1714777936]

1714777936

[1714777936]

1714777936

[Romeo26222]

Hello
I am using a 6x zotac 1060 AMP+ version with 9gbps memory.

I have something weird and need advice

these are my API state when I start the mining software

https://i.gyazo.com/09d1888e9da938c8cb8b833719bec5b8.png

but after only 2 minutes of running the 1st GPU card gives this redings

https://i.gyazo.com/cdda2315d5a88eadf595bfbb9aa7a7fb.png

this is not happening with excavator miner from nicehash which keeps the card at constant speed and voltage consumption.

I tried everything, I swapped the card with others, swapped the riser, swapped the power supplies and still get same issue..
any tips here to help..
PS. I am using MSI AB to boost the memory clock to 4700 with no power or core clock modifications.

What are you using to connect to the desktop?  VNC, Team Viewer, RDP ect?

I am using teamviewer, do you think it uses the GPU so it reduces the hash rate?

[nUm81]

Hello
I am using a 6x zotac 1060 AMP+ version with 9gbps memory.

I have something weird and need advice

these are my API state when I start the mining software



but after only 2 minutes of running the 1st GPU card gives this redings



this is not happening with excavator miner from nicehash which keeps the card at constant speed and voltage consumption.

I tried everything, I swapped the card with others, swapped the riser, swapped the power supplies and still get same issue..
any tips here to help..
PS. I am using MSI AB to boost the memory clock to 4700 with no power or core clock modifications.

What are you using to connect to the desktop?  VNC, Team Viewer, RDP ect?

I am using teamviewer, do you think it uses the GPU so it reduces the hash rate?

Yes teamviewer uses gpu power to render the desktop.  If you change your API address to the actual IP of the mining rig and view the api from another pc, with teamviewer not connected, you will find that your hash goes back up. 

[nUm81]

Dont hate me, but I would like explanation on --fee option
I get that it controls amount of devfee, but setting it to 0 (testing purposes ) still shows devfee shares. So my question really is, what does value 0 default to? 2%? Again, I dont have anything against devfee, just setting the value to 0 is misleading IMHO. Tested on 0.3.3b version. Did not try on 0.3.4b

if it is showing devfee shares then the program has not accepted your --fee parameter at startup, so just check that your formatting is correct.

If you do not define a --fee then it will be the default of 2%

If you put --fee 0 it will be 0%

If you put --fee 2.5 it will be 2.5%

ect.

[Romeo26222]

Yes teamviewer uses gpu power to render the desktop.  If you change your API address to the actual IP of the mining rig and view the api from another pc, with teamviewer not connected, you will find that your hash goes back up. 

thank you so much, I monitor the cards now via API and it works great, no hash drop.

[silverkamote]

no reject with coinmine at all,
works on 660 ti – 46-47 sols. 1070 – 275-280 sols OC. and it’s workin with pools! much more profit to come.

[Gaglam]

Temp: GPU0: 64C GPU1: 65C GPU2: 64C GPU3: 65C
GPU0: 378 Sol/s GPU1: 375 Sol/s GPU2: 377 Sol/s GPU3: 372 Sol/s
Total speed: 1502 Sol/s
+-----+-------------+--------------+
| GPU | Power usage |  Efficiency  |
+-----+-------------+--------------+
|  0  |     93W     |  4.06 Sol/W  |
|  1  |     91W     |  4.12 Sol/W  |
|  2  |     89W     |  4.24 Sol/W  |
|  3  |     91W     |  4.09 Sol/W  |
+-----+-------------+--------------+

4x GTX 1070

[PokerStein1]

Temp: GPU0: 64C GPU1: 65C GPU2: 64C GPU3: 65C
GPU0: 378 Sol/s GPU1: 375 Sol/s GPU2: 377 Sol/s GPU3: 372 Sol/s
Total speed: 1502 Sol/s
+-----+-------------+--------------+
| GPU | Power usage |  Efficiency  |
+-----+-------------+--------------+
|  0  |     93W     |  4.06 Sol/W  |
|  1  |     91W     |  4.12 Sol/W  |
|  2  |     89W     |  4.24 Sol/W  |
|  3  |     91W     |  4.09 Sol/W  |
+-----+-------------+--------------+

4x GTX 1070

Which line do i need to add to my bat file to see this statistics ?

And my second question is when i open my bat file to work my gpu`s accepting shares very quickly at first but later they start to accept shares slowly is it normal or not ?

[ayke99]

Temp: GPU0: 64C GPU1: 65C GPU2: 64C GPU3: 65C
GPU0: 378 Sol/s GPU1: 375 Sol/s GPU2: 377 Sol/s GPU3: 372 Sol/s
Total speed: 1502 Sol/s
+-----+-------------+--------------+
| GPU | Power usage |  Efficiency  |
+-----+-------------+--------------+
|  0  |     93W     |  4.06 Sol/W  |
|  1  |     91W     |  4.12 Sol/W  |
|  2  |     89W     |  4.24 Sol/W  |
|  3  |     91W     |  4.09 Sol/W  |
+-----+-------------+--------------+

4x GTX 1070

Which line do i need to add to my bat file to see this statistics ?

And my second question is when i open my bat file to work my gpu`s accepting shares very quickly at first but later they start to accept shares slowly is it normal or not ?

1. --pec or --api to see it in you browser
2. lower you memory clock because slows the miner , on mi rig i only use max +450 mem

[nUm81]

Temp: GPU0: 64C GPU1: 65C GPU2: 64C GPU3: 65C
GPU0: 378 Sol/s GPU1: 375 Sol/s GPU2: 377 Sol/s GPU3: 372 Sol/s
Total speed: 1502 Sol/s
+-----+-------------+--------------+
| GPU | Power usage |  Efficiency  |
+-----+-------------+--------------+
|  0  |     93W     |  4.06 Sol/W  |
|  1  |     91W     |  4.12 Sol/W  |
|  2  |     89W     |  4.24 Sol/W  |
|  3  |     91W     |  4.09 Sol/W  |
+-----+-------------+--------------+

4x GTX 1070

Which line do i need to add to my bat file to see this statistics ?

And my second question is when i open my bat file to work my gpu`s accepting shares very quickly at first but later they start to accept shares slowly is it normal or not ?

The pool you are mining to is most likely adjusting the difficulty of the shares that it send to you based on your performance.  It will start off fast until the pool determines your hashing speed and finds the correct difficulty for your rig.  Its nothing that you should be worried about.

[Dum3]

Periodically, the application hangs and does nothing, after pressing Enter in the window the application displays the message "Temp: ERROR: Lost connection with the server." Next, the connection is reconnected and the execution continues. The parameter --eexit 3 is enabled, the temperature of the GPU is normally not more than 70 degrees Celsius. Someone faced a similar problem?

I've been having a similar problem. Only in my case the GPU stop mining and I have close the program and open it again.

The worst is that this is happening more during the night, just when I'm sleeping.

This did not happen in version 0.3.3b.

Exactly same here,no overclock on a 1080Ti and 1070, good temps.

0.3.4 after 1-2 hours will simply stop mining and do nothing.

0.3.3B works perfectly after 24 hours. Little bit lower hashrate but at least is problem-free.

[rdluffy]

Periodically, the application hangs and does nothing, after pressing Enter in the window the application displays the message "Temp: ERROR: Lost connection with the server." Next, the connection is reconnected and the execution continues. The parameter --eexit 3 is enabled, the temperature of the GPU is normally not more than 70 degrees Celsius. Someone faced a similar problem?

I've been having a similar problem. Only in my case the GPU stop mining and I have close the program and open it again.

The worst is that this is happening more during the night, just when I'm sleeping.

This did not happen in version 0.3.3b.

Exactly same here,no overclock on a 1080Ti and 1070, good temps.

0.3.4 after 1-2 hours will simply stop mining and do nothing.

0.3.3B works perfectly after 24 hours. Little bit lower hashrate but at least is problem-free.

Exactly same here
I'll try the 0.3.3B

[tpd09]

when I type http://127.0.0.1:42000/getstat in browser the stats wont come up - do I need to active the API somehow?

Thanks in advance.

[iamnewhere]

when I type http://127.0.0.1:42000/getstat in browser the stats wont come up - do I need to active the API somehow?

Thanks in advance.

you have to add "--api 127.0.0.1:42000" to your command line and then go to http://127.0.0.1:42000 in your browser (without the /getstat)

[usernameisalreadyinuse]

if it is showing devfee shares then the program has not accepted your --fee parameter at startup, so just check that your formatting is correct.

If you do not define a --fee then it will be the default of 2%

If you put --fee 0 it will be 0%

If you put --fee 2.5 it will be 2.5%

ect.

Give it a try and see for yourself. At least on 0.3.3b with --fee 0 you will still have devfee shares - use log to check

[usernameisalreadyinuse]

What to put in --api to see them all on one PC, I have 2 and got api bind error when i use ip from first pc on which i want to see it.

cannot be done like that.

[iamnewhere]

What to put in --api to see them all on one PC, I have 2 and got api bind error when i use ip from first pc on which i want to see it.

you like to check from remote computer or multiple instances on the same local computer?

for remote computer:
--api *:42000

and allow that port on the firewall - on remote PC type in http://IP-OF-REMOTE-COMPUTER:42000

if multiple instances on local computer use:
--api 127.0.0.1:42000
--api 127.0.0.1:42001
...
...

and open with http://127.0.0.1:42000 or http://127.0.0.1:42001

[ayke99]

What to put in --api to see them all on one PC, I have 2 and got api bind error when i use ip from first pc on which i want to see it.

you like to check from remote computer or multiple instances on the same local computer?

for remote computer:
--api *:42000

and allow that port on the firewall - on remote PC type in http://IP-OF-REMOTE-COMPUTER:42000

if multiple instances on local computer use:
--api 127.0.0.1:42000
--api 127.0.0.1:42001
...
...

and open with http://127.0.0.1:42000 or http://127.0.0.1:42001

The Api is very simple tu use :1. Put just --api in you .bat , then open the rig browser and it`s there use http://localhost:42000 !
2. Use your Lan ip from your rig in your .bat file ex:--api 192.168.1.199:42000 (your-lan-ip:desired-port) to see the api from other computer connected to the same lan.
3. To use the Api on "Exterior" you have to forward the ip:port from your router this is much more complicated use google : How to Forward Ports on Your Router , to see the api from anywhere .

[tpd09]

https://ibb.co/bRvPSk

thanks a lot guys!

[wojzet]

Hi
Sorry for my Eng  
When i start nheqminer 0.5c on computer with win 10, i7 6 core and Asus Strix gtx1070 all work fine.
When i start this program on my old computer with win 10, c2q and gtx750 ti I must add -cv 1 and work (slow, but working)
When i put to my old computer new MSI gtx1070, install new graphic driver, i have this error "CUDA error 'misaligned address' in func 'eq_cuda_context::solve' line 988"
I try reinstall drivers, rebooting systems, update system, using another version nheqminer, using all -cd, cv, cx etc, kissing my computer, kicking my computer, and all time is this error...
And i was downloading your's program to test, and I have:
(For me problem is with drivers, because on this computer with GTX750 Ti all was fine, but do you have any suggestion?)


EWBF's Zcash CUDA miner. 0.3.3b         |
+-------------------------------------------------+
INFO: Server: eu1-zcash.flypool.org:3333
INFO: Solver Auto.
INFO: Devices: User defined.
INFO: Temperature limit: 90
INFO: Api: Disabled
---------------------------------------------------
INFO: Target: 00083126e978d4fd...
INFO: Detected new work: ce839587b04bebd120f6
CUDA: Device: 0 GeForce GTX 1070, 8192 MB
INFO: Detected new work: c005a82f3de9a9f7d31f
CUDA: Device: 0 Selected solver: 0
CUDA: Device: 0 Thread exited with code: 77
Temp: GPU0: 39C
GPU0: 0 Sol/s
Total speed: 0 Sol/s
Temp: GPU0: 41C
GPU0: 0 Sol/s
Total speed: 0 Sol/s
Temp: GPU0: 42C
GPU0: 0 Sol/s
Total speed: 0 Sol/s
ERROR: Looks like GPU0 are stopped. Restart attempt.
INFO: GPU0 are restarted.
CUDA: Device: 0 User selected solver: 0
CUDA: Device: 0 Thread exited with code: 46
Temp: GPU0: 41C