Pages:
Author

Topic: EWBF's CUDA Zcash miner - page 78. (Read 2164327 times)

newbie
Activity: 54
Merit: 0
August 20, 2017, 01:08:22 PM
CUDA: Device: 5 Thread exited with code: 77
CUDA: Device: 4 Thread exited with code: 77
CUDA: Device: 3 Thread exited with code: 77
CUDA: Device: 2 Thread exited with code: 77
CUDA: Device: 1 Thread exited with code: 77
CUDA: Device: 0 Thread exited with code: 77

Every day I crash once or twice but I do not know the reason, stops mining, puts everything to 0 and does not restart, any help?

This usually caused by too much overcloack, but If you want to give it a try, this tool solve this issue (reboot the miner if it's stopped):https://bitcointalksearch.org/topic/ewbfs-cuda-miner-monitor-tool-2053739
full member
Activity: 226
Merit: 100
August 20, 2017, 08:23:51 AM
CUDA: Device: 5 Thread exited with code: 77
CUDA: Device: 4 Thread exited with code: 77
CUDA: Device: 3 Thread exited with code: 77
CUDA: Device: 2 Thread exited with code: 77
CUDA: Device: 1 Thread exited with code: 77
CUDA: Device: 0 Thread exited with code: 77

Every day I crash once or twice but I do not know the reason, stops mining, puts everything to 0 and does not restart, any help?
Lower the clocks of your GPUs, or just one of them.

I have 6 G1 1060s in one rig, 5 Samsung from the old series with that thermal pad oil issues, and one new without, but with Micron Memory. That 5 ones all go up tp +145 Core and 830 Mem, just that one cannot go above 120 core, and of course above 500 on Mem. I've had a same issue with them. You must find the optimal clocks for all of your cards.
full member
Activity: 226
Merit: 100
August 20, 2017, 08:19:07 AM
when will be the new version of EWBF zcash miner?
Looks like never...
newbie
Activity: 42
Merit: 0
August 20, 2017, 04:09:20 AM
CUDA: Device: 5 Thread exited with code: 77
CUDA: Device: 4 Thread exited with code: 77
CUDA: Device: 3 Thread exited with code: 77
CUDA: Device: 2 Thread exited with code: 77
CUDA: Device: 1 Thread exited with code: 77
CUDA: Device: 0 Thread exited with code: 77

Every day I crash once or twice but I do not know the reason, stops mining, puts everything to 0 and does not restart, any help?
member
Activity: 144
Merit: 10
August 20, 2017, 03:44:29 AM
Mem - +155
Core - +128
Power - 85% (about 210 watts for my cards)
This gives me 710 - 720 sol/s.

From what I can remember the ti's didn't really like to be undervolted on the gpu and i think that is how I ended up around 85%.  Those settings keep the core voltage above 900 mV. 

and i recommend NOT to undervolt Ti aswell (MAX to 90% to algos that dont required much energy for core ... like skunk with earlier miners) there is too much hashrate drop for doing that
and you can get ++++500 on mem (my FE did around +700to800 stable, 100% tdp and about +200 core with ewbf 0.3.3 ... cant remeber exactly nubers, its more then 2 months)

and btw rams eating so MUCH power (nonXMP vs XMP profile is about 70 fkin watts - ddr4 rams ... in vga its almost same)
newbie
Activity: 4
Merit: 0
August 20, 2017, 01:52:39 AM
Would you add graphical statistic for every variables (on http api) ?
Temp - Power - Speed - Efficiency - Accepted - Rejected - and even DevFree Share.

It would be very helpful for miner, and we could use those graphs to compare what we see on pool's graphs.

There is one project already for that: https://github.com/K4P11/GUI-for-EWBF
newbie
Activity: 14
Merit: 0
August 19, 2017, 06:09:14 AM
Would you add graphical statistic for every variables (on http api) ?
Temp - Power - Speed - Efficiency - Accepted - Rejected - and even DevFree Share.

It would be very helpful for miner, and we could use those graphs to compare what we see on pool's graphs.
newbie
Activity: 73
Merit: 0
August 19, 2017, 02:15:37 AM
Hi,
I using EWBF's CUDA Zcash miner on 6x1070
Have some strange problems with API,
miner still working, but API doesn't.

How to troubleshoot it, please advice.

The first obvious question is do you have --api in your startup bat or config file?

Yeah, the same's as here. I wrote about it more than once. At that time, even the developer was present in the subject, but ignored it .... Now he does not appear here ...
After a while, 10+ hours, or 24 hours -api become inaccessible until you restart the miner.
I launch from a BAT file.
member
Activity: 126
Merit: 11
August 17, 2017, 11:32:53 PM
Hi,
I using EWBF's CUDA Zcash miner on 6x1070
Have some strange problems with API,
miner still working, but API doesn't.

How to troubleshoot it, please advice.

The first obvious question is do you have --api in your startup bat or config file?
full member
Activity: 672
Merit: 154
Blockchain Evangelist.
August 17, 2017, 11:22:49 PM
--intensity option doesn't work at all. I tried values from 1-64 and even when I set it to 1 my mobile 1070 still working under full load....

Yeah, the same's as here. Some of my friends said it's a bit lower hashrate if intensity value is small but when I made several tests, hashrate's not much different. Only different in OC.
newbie
Activity: 3
Merit: 0
August 17, 2017, 05:58:30 PM
Hi,
I using EWBF's CUDA Zcash miner on 6x1070
Have some strange problems with API,
miner still working, but API doesn't.

How to troubleshoot it, please advice.
newbie
Activity: 4
Merit: 0
August 17, 2017, 09:42:56 AM
--intensity option doesn't work at all. I tried values from 1-64 and even when I set it to 1 my mobile 1070 still working under full load....
legendary
Activity: 1904
Merit: 1007
August 16, 2017, 03:07:24 PM
Hi all, i have used ewbf's cuda zcash miner since its inception, but recently Kaspersky identified the 0.32b version as having a Trojan:Win32 Skeeyah.A!bit. This seems strange because it is a miner, why wouldn't it detect it as crypto miner and a trojan instead?
Seems like a false positive. it's not a trojan in any way.

Not throwing any accusations, but how do you know without the source code being available?
newbie
Activity: 33
Merit: 0
August 16, 2017, 12:00:09 PM
Ive ran this for month now with flypool but lately the program just stops after a while. There is no error message or anything. I have to close the window and restart it. It might run few hours and stop again. I have four asus strix gtx 1070.

Try disabling "quickedit mode" in properties of the .bat file, fixed it for me
newbie
Activity: 25
Merit: 0
August 15, 2017, 03:05:44 PM
v.0.3.4b fast and more profit. Thank You, I'll wait to next version.
full member
Activity: 280
Merit: 100
I love crypto
August 15, 2017, 01:38:02 PM
Ive ran this for month now with flypool but lately the program just stops after a while. There is no error message or anything. I have to close the window and restart it. It might run few hours and stop again. I have four asus strix gtx 1070.
full member
Activity: 672
Merit: 154
Blockchain Evangelist.
August 15, 2017, 01:02:06 PM
I'm mining in flypool, as I check EWBF, the hashrate's never below 2000 sol/s (normally around 2030-2060) but flypool regularly give me current hashrate about 1920-1970 sol/s. It doesnt make sense for me.   
newbie
Activity: 29
Merit: 0
August 15, 2017, 10:48:33 AM
Hi all, i have used ewbf's cuda zcash miner since its inception, but recently Kaspersky identified the 0.32b version as having a Trojan:Win32 Skeeyah.A!bit. This seems strange because it is a miner, why wouldn't it detect it as crypto miner and a trojan instead?
Seems like a false positive. it's not a trojan in any way.

If he downloaded from less trustworthy sources it can be a trojan.
YIz
hero member
Activity: 686
Merit: 502
August 15, 2017, 09:33:16 AM
Hi all, i have used ewbf's cuda zcash miner since its inception, but recently Kaspersky identified the 0.32b version as having a Trojan:Win32 Skeeyah.A!bit. This seems strange because it is a miner, why wouldn't it detect it as crypto miner and a trojan instead?
Seems like a false positive. it's not a trojan in any way.
hero member
Activity: 784
Merit: 500
August 15, 2017, 09:07:38 AM
Hi all, i have used ewbf's cuda zcash miner since its inception, but recently Kaspersky identified the 0.32b version as having a Trojan:Win32 Skeeyah.A!bit. This seems strange because it is a miner, why wouldn't it detect it as crypto miner and a trojan instead?
Pages:
Jump to: