EWBF's CUDA Zcash miner

[EWBF_]

CUDA: Device: 3 Thread exited with code: 77
CUDA: Device: 4 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
ERROR: Some workers are stopped. Attempt to restart: 1
CUDA: Device: 0 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 1 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 2 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 3 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 4 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 0 Thread exited with code: 46
CUDA: Device: 1 Thread exited with code: 46
CUDA: Device: 2 Thread exited with code: 46
CUDA: Device: 3 Thread exited with code: 46
CUDA: Device: 4 Thread exited with code: 46
ERROR: Some workers are stopped. Attempt to restart: 2
CUDA: Device: 0 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 0 Thread exited with code: 46
CUDA: Device: 1 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 1 Thread exited with code: 46
CUDA: Device: 2 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 2 Thread exited with code: 46
CUDA: Device: 3 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 3 Thread exited with code: 46
CUDA: Device: 4 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 4 Thread exited with code: 46

Getting the same thing on two different rigs with 1060's and 1070's, I've tried 1.0 and 2.0 it doesn't seem to make a difference which one I'm running.  I'd also like to add that this doesn't happen right away, the miner works fine for 5-10 minutes first before this happens. The cards run valley benchmark just fine for hours but I removed all overclocking anyway to eliminate possibilities per EWBF's suggestion.  Any other ideas would be much appreciated, having two rigs down is a big waste of resources.

Try solver 2 or 1.

[1715187775]

1715187775

[sublimus]

CUDA: Device: 0 Thread exited with code: 46
CUDA: Device: 1 Thread exited with code: 46
CUDA: Device: 2 Thread exited with code: 46
CUDA: Device: 3 Thread exited with code: 46
CUDA: Device: 4 Thread exited with code: 46
ERROR: Some workers are stopped. Attempt to restart: 2
CUDA: Device: 0 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 0 Thread exited with code: 46
CUDA: Device: 1 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 1 Thread exited with code: 46
CUDA: Device: 2 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 2 Thread exited with code: 46
CUDA: Device: 3 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 3 Thread exited with code: 46
CUDA: Device: 4 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 4 Thread exited with code: 46

[/quote]

Just got the same glitch, restarting the script worked fine.
Some time ago I had kind of the same problem with Claymore and my AMD's.
hint to EWBF: Setting the (-r 240) "restart by user" switch to every 4 hours solved my problem.

[Amph]

can you still improve this miner?

[EWBF_]

can you still improve this miner?

Technically, yes. But on practice not significantly.

[dtawom]

Getting the same thing on two different rigs with 1060's and 1070's, I've tried 1.0 and 2.0 it doesn't seem to make a difference which one I'm running.  The cards run valley benchmark just fine for hours but I removed all overclocking anyway to eliminate possibilities per EWBF's suggestion.  Any other ideas would be much appreciated, having two rigs down is a big waste of resources.

OS ?
Drivers version ?
GPU's brand / model ?
Motherboard ?
Psu ?
type of risers ?
overall hardware config (especially how you connected everything, and especially power)
Command line to start miner ? (you can hide wallet/user)
Do you start miner in admin mode (if you aren't loggued as admin)

You said you tested with benchmark but they usually only run on main GPU or if you have SLI, have you tested cards one by one in main GPU slot of the mobo, also you didn't activated sli at all right ? (software or hardware with the bridge)

-Both Rigs are Win10 Pro x64
-Drivers 376.66
-GPU's 2x 1070 EVGA ACX 2.0 Superclocked in 1070 rig and 1x MSI GTX 1060 3GT OC (B01KUCL25Y) in 1060 rig.
-1070 rig is a gigabyte z97x-ud3h-cf motherboard and 1060 rig is an optiplex 390 desktop with PS replaced.
-1070 rig has I5-4460 and optiplex 390 1060 rig has an I5-2500s
-1070 rig has a PC power & cooling 950W Silencer MK-II PS and Optiplex has Thermaltake SP-650
-No risers.
-The 1070's all have two 8 pin connectors coming from the power supply (no adapters) and the 1060 has one 6 pin power cable direct from the power supply
-miner --server us1-zcash.flypool.org --port 3333 --user address.phoop --solver 1 --pass x --cuda_devices 0 1 2 Note: I've tried using all solvers 0-3 per ewbf's suggestion and I've also tried running the cards individually by using cuda_devices selection with the same results.
I start the miners from an account with administrator privileges, but I don't right click and run as admin.  If I run it from an admin command prompt I do get the same problem though.  I assume if it was admin related it wouldn't work at all, not work for 5-10 minutes then stop working.
The benchmarks will run on whatever you have set as your primary display.  I have one display connected to each video card so to make benchmark run off other gpu I just have to set the other monitor as my primary display.  No SLI mode is not on with hardware or software bridge.  No I have not tested the cards one by one in main GPU slot.  I have this case http://www.antec.com/product.php?id=705069&lan=nz so adding/removing cards can be a bit of a pain.

[bensam1231]

can you still improve this miner?

Technically, yes. But on practice not significantly.

No more EQM miners to gather data from.

[bughatti]

can you still improve this miner?

Technically, yes. But on practice not significantly.

No more EQM miners to gather data from.

 

There are some very smart people here that can code this stuff, @EWBF, you are one of them, so please dont take offense to this question.  Are we at a point of technology or knowledge that hinders progress?

[dtawom]

CUDA: Device: 3 Thread exited with code: 77
CUDA: Device: 4 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
ERROR: Some workers are stopped. Attempt to restart: 1
CUDA: Device: 0 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 1 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 2 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 3 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 4 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 0 Thread exited with code: 46
CUDA: Device: 1 Thread exited with code: 46
CUDA: Device: 2 Thread exited with code: 46
CUDA: Device: 3 Thread exited with code: 46
CUDA: Device: 4 Thread exited with code: 46
ERROR: Some workers are stopped. Attempt to restart: 2
CUDA: Device: 0 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 0 Thread exited with code: 46
CUDA: Device: 1 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 1 Thread exited with code: 46
CUDA: Device: 2 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 2 Thread exited with code: 46
CUDA: Device: 3 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 3 Thread exited with code: 46
CUDA: Device: 4 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 4 Thread exited with code: 46

Getting the same thing on two different rigs with 1060's and 1070's, I've tried 1.0 and 2.0 it doesn't seem to make a difference which one I'm running.  I'd also like to add that this doesn't happen right away, the miner works fine for 5-10 minutes first before this happens. The cards run valley benchmark just fine for hours but I removed all overclocking anyway to eliminate possibilities per EWBF's suggestion.  Any other ideas would be much appreciated, having two rigs down is a big waste of resources.

Try solver 2 or 1.

I tried much solver so hard and still nadda.  I did find a work around but it isn't really an acceptable one in my opinion.  If I under clock the graphics cards both memory and GPU the miner doesn't crash.  I'd say that I have two failing cards, but they work fine for gaming and hours of valley benchmark without crashes or artifact with massive overclocking.

[sublimus]

CUDA: Device: 3 Thread exited with code: 77
CUDA: Device: 4 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
ERROR: Some workers are stopped. Attempt to restart: 1
CUDA: Device: 0 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 1 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 2 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 3 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 4 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 0 Thread exited with code: 46
CUDA: Device: 1 Thread exited with code: 46
CUDA: Device: 2 Thread exited with code: 46
CUDA: Device: 3 Thread exited with code: 46
CUDA: Device: 4 Thread exited with code: 46
ERROR: Some workers are stopped. Attempt to restart: 2
CUDA: Device: 0 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 0 Thread exited with code: 46
CUDA: Device: 1 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 1 Thread exited with code: 46
CUDA: Device: 2 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 2 Thread exited with code: 46
CUDA: Device: 3 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 3 Thread exited with code: 46
CUDA: Device: 4 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 4 Thread exited with code: 46

Getting the same thing on two different rigs with 1060's and 1070's, I've tried 1.0 and 2.0 it doesn't seem to make a difference which one I'm running.  I'd also like to add that this doesn't happen right away, the miner works fine for 5-10 minutes first before this happens. The cards run valley benchmark just fine for hours but I removed all overclocking anyway to eliminate possibilities per EWBF's suggestion.  Any other ideas would be much appreciated, having two rigs down is a big waste of resources.

Try solver 2 or 1.

I tried much solver so hard and still nadda.  I did find a work around but it isn't really an acceptable one in my opinion.  If I under clock the graphics cards both memory and GPU the miner doesn't crash.  I'd say that I have two failing cards, but they work fine for gaming and hours of valley benchmark without crashes or artifact with massive overclocking.

You tried to rescan the driver's devices in Devices Manager?
Sometimes the drivers get corrupted... Microsoft advanced housekeeping.

[Psynthax]

When I close miner, I can`t get it to start again next time until I restart my PC..

Anyone know how to fix or get around this issue ?

[AzzAz]

When I close miner, I can`t get it to start again next time until I restart my PC..

Anyone know how to fix or get around this issue ?

I've met this. Lowering clocks did help.

[m1n1ngP4d4w4n]

When I close miner, I can`t get it to start again next time until I restart my PC..

Anyone know how to fix or get around this issue ?

Try to kill the miner cleanly with ctrl+c then exit, if you don't usually it let the drivers/gpu open in a way that force you to have reboot to get it working again. You can also use nvidiadriverinspector to reset the drivers, and reapply your overclock all in a script. But if your computer is fast better reboot.

-Both Rigs are Win10 Pro x64
-Drivers 376.66
-GPU's 2x 1070 EVGA ACX 2.0 Superclocked in 1070 rig and 1x MSI GTX 1060 3GT OC (B01KUCL25Y) in 1060 rig.
-1070 rig is a gigabyte z97x-ud3h-cf motherboard and 1060 rig is an optiplex 390 desktop with PS replaced.
-1070 rig has I5-4460 and optiplex 390 1060 rig has an I5-2500s
-1070 rig has a PC power & cooling 950W Silencer MK-II PS and Optiplex has Thermaltake SP-650
-No risers.
-The 1070's all have two 8 pin connectors coming from the power supply (no adapters) and the 1060 has one 6 pin power cable direct from the power supply
-miner --server us1-zcash.flypool.org --port 3333 --user address.phoop --solver 1 --pass x --cuda_devices 0 1 2 Note: I've tried using all solvers 0-3 per ewbf's suggestion and I've also tried running the cards individually by using cuda_devices selection with the same results.
I start the miners from an account with administrator privileges, but I don't right click and run as admin.  If I run it from an admin command prompt I do get the same problem though.  I assume if it was admin related it wouldn't work at all, not work for 5-10 minutes then stop working.
The benchmarks will run on whatever you have set as your primary display.  I have one display connected to each video card so to make benchmark run off other gpu I just have to set the other monitor as my primary display.  No SLI mode is not on with hardware or software bridge.  No I have not tested the cards one by one in main GPU slot.  I have this case http://www.antec.com/product.php?id=705069&lan=nz so adding/removing cards can be a bit of a pain.

Ok hum nothing seems to be wrong with your current setup, i suppose that your windows is updated properly to the anniversary edition of W10 ? Have you tried another pool too ? Have you also tried older version of drivers ? Other than that, no ideas, sorry mate.

[dtawom]

CUDA: Device: 0 Thread exited with code: 46
CUDA: Device: 1 Thread exited with code: 46
CUDA: Device: 2 Thread exited with code: 46
CUDA: Device: 3 Thread exited with code: 46
CUDA: Device: 4 Thread exited with code: 46
ERROR: Some workers are stopped. Attempt to restart: 2
CUDA: Device: 0 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 0 Thread exited with code: 46
CUDA: Device: 1 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 1 Thread exited with code: 46
CUDA: Device: 2 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 2 Thread exited with code: 46
CUDA: Device: 3 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 3 Thread exited with code: 46
CUDA: Device: 4 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 4 Thread exited with code: 46

Just got the same glitch, restarting the script worked fine.
Some time ago I had kind of the same problem with Claymore and my AMD's.
hint to EWBF: Setting the (-r 240) "restart by user" switch to every 4 hours solved my problem.
[/quote]

Thanks for the restart by user hint, didn't even know it existed till I saw your post.  I've set it up on all my miners as a just in case measure.  I believe I have found a solution for Thread exited with code: 46 , Thread exited with code: 77 , and Thread exited with code 30 .  After hours of tinkering and sifting through logs in EVGA precision X I noticed a correlation between power % and this error.  Every time it would happen on my 1060 and 1070 rigs they would be within 4% of 100%.  One of the times I even saw GPU voltage at 0.000% the line before the miner crashed.  I've found on both my rigs that were having this problem, setting the power % to 94% has stopped the problem and allowed me to returned to an overclocked (rather than under clocked) configuration.  My 1060 is now getting me a consistent 280-300 sol/sec with these overclocked settings on an MSI 1060 3GT OC 3GB.
http://i128.photobucket.com/albums/p193/dtawom/1060_zpsghnrimkv.jpg

[Zzsdr]

Hello Miners,

Can you suggest driver version and any settings to test, so I can get the maximum of my rig? Thank you in advance! Below is my setup

5 x GTX 1080 (ASUS ROG A8G) 8pin+6pin / Micron memory [2560-2590 Sol/s]

clock/mem: 2025(38)/5103 MHz / TDP 120% / 55-60C / Ambient 22C

Win7-64, drivers 375.70, nVidia Inspector 1.3.7.8
EWBF's miner ver 0.2.0b, solver 0

H81 PRO BTC rev.1.01
G1840 @2.8
8GB DDR3 1600 CORSAIR (1x8GB)
Corsair HX1200i - Main psu (powers everything + risers + 3 gpus)
Corsair RM750x - 2nd psu (powers only 2 gpus)
USB RISERS v.005s

Anyone with better speeds on any gtx 1080?


http://i63.tinypic.com/2njae5f.jpg

[giagge]

I have never believed the story that ewbf has copied someone or other miners, I'm sure that if he wants he can improve his miner without help from others.

[un4given]

hello lads, is there any way to tell the miner what gpus to use? normally its -cd 0,1,.... function but it doenst work with EWBF and also i cant find a readme for all comands
thx in advance

[m1n1ngP4d4w4n]

hello lads, is there any way to tell the miner what gpus to use? normally its -cd 0,1,.... function but it doenst work with EWBF and also i cant find a readme for all comands
thx in advance

"miner --help or -h" ?

[sublimus]

hello lads, is there any way to tell the miner what gpus to use? normally its -cd 0,1,.... function but it doenst work with EWBF and also i cant find a readme for all comands
thx in advance

--cuda_devices 012

[m1n1ngP4d4w4n]

hello lads, is there any way to tell the miner what gpus to use? normally its -cd 0,1,.... function but it doenst work with EWBF and also i cant find a readme for all comands
thx in advance

--cuda_devices 012

need to put a space between devices, there are examples in the miner help.

--cuda_devices 0 1 2

[sublimus]

CUDA: Device: 0 Thread exited with code: 46
CUDA: Device: 1 Thread exited with code: 46
CUDA: Device: 2 Thread exited with code: 46
CUDA: Device: 3 Thread exited with code: 46
CUDA: Device: 4 Thread exited with code: 46
ERROR: Some workers are stopped. Attempt to restart: 2
CUDA: Device: 0 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 0 Thread exited with code: 46
CUDA: Device: 1 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 1 Thread exited with code: 46
CUDA: Device: 2 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 2 Thread exited with code: 46
CUDA: Device: 3 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 3 Thread exited with code: 46
CUDA: Device: 4 GeForce GTX 1070, 8192 MB M0
CUDA: Device: 4 Thread exited with code: 46

NVidia do not need nor appreciate power starving.
Personnaly I push the Power Target all the way up.
Gives the GPU the overhead in case it needs it.
GPU clock = +145
Mem clock = +595
GTX 1070 = 440 H/s