Re: testing cards...

If you can use that specific card for your on-screen video, run Furmark (it will stress the gpu, I use the burn in default).  Slowly increase the clock (and apply, because I've forgotten occassionally).  You will eventually hit a point where the gpu can't get pushed anymore (usually obvious, like screen freezes)   I've only had it freeze the application and Win 10 stayed up and running without issue.  It can take some time, particularly if you have multiple cards.  I still feel this is the best way, as you can also do the same for the memory oc and look for issues to pop up as well.  With the 1070's I've had for gaming, you'll usually hit a gpu overclock that you can't go past regardless of voltage.  For example, the current one I have is +202.  It's completely stable doing that from 65% power upwards (though voltage will limit the oc amount, but you're going for efficiency anyway).  +203 and it doesn't matter if I overvolt it, it will still crash at some point.

Another way would be to set up some way for the miner to close and restart.  I'm using the following in the bat file to start the app.  Found this setup with a google search, and it does the job.  For below to work, you have to add "eexit 3" so the miner closes and this can start it.  If not it will just stay in the miner and keep kicking out errors.

@Echo off
:Start
miner
echo Program terminated at %Date% %Time% with Error %ErrorLevel% >> D:\logs\ewbfminer.log
echo Press Ctrl-C if you don't want to restart automatically
ping -n 10 localhost

goto Start

Again you'll still be doing the minor incremental changes, but now you have to wait for the miner to crash out.  That said this will keep restarting the miner if there is an issue (only good if the miner stays running for a decent period of time before crashing, or you're actual sol/s will be horrible)

GPU's MODEL NAME: MSI GeForce GTX 1070 Sea Hawk EK X
VRAM: 8gb GDDR5 (Micron)
CORE/MEMORY CLOCK: 2176/4681
HASHRATE: ~520 Sol/s
MINER SOFTWARE: EWBF 3.4b
OS: Windows 10 64-bit
TDP(OPTIONAL): 85%

So I've run into something interesting in using the beta 2.2.1, using cuda 9.

I originally ran the following command line in a bat file.

• ccminer-x64 -a lyra2v2 -d 0 -o stratum+tcp://18.85.34.148:9171 -u Vg39fRFWf2CwAuAXuXzMTs99Jh1ZTaCUDJ -p workwork -t 1 -b 0

After a period of time, it would fail out saying that the result did not validate with the cpu

I messed around with various settings for intensity as well as overclocking (memory, gpu, memory+gpu, various voltage adjustments) and the result always ended with the same error.  I noticed that the rate was also slowly decreasing over time.

I also tried --cuda-schedule spin.  It actually lasted a bit longer with a higher rate, but it still eventually errored out, the same quickly repeating did not validate with the cpu error message.

So in messing around more, I did the thing you're not supposed to... changed multiple things at once and it resolved the validation check but showed json-rpc call failed: method not found.  As I'm seeing my rates on the server page, I'm guessing (and by a stretch) that this is not a huge problem.

I changed the command line to:

• ccminer-x64 -a lyra2v2 -d 0 -o 18.85.34.148:9171 -u Vg39fRFWf2CwAuAXuXzMTas99Jh1ZTaCUDJ -p workwork -t 1 -b 0 -D 1 (and I just noticed that I added an a to my wallet address for this one... oh well)
• I set my i5-6600k back to stock voltage from lower multipliers, voltage, etc. (trying to reduce overall wattage as kwh here is 0.21)
  

I wanted to try out adding the NSIGHT_CUDA_DEBUGGER, but I know nothing about coding at the moment so I have no idea where I would put that.

I'm guessing that it was reverting the settings on the cpu back to normal, but I figured I'd mention it in case others were experiencing similar issues

In case it helps I'm currently running that last command line without issue so far connecting to p2pool (18.85.34.148:9171 Cambridge US) at around 37.25 MH/s:

• i5-6600k
• 16 gb ram
• gigabyte z170x gaming 7
• msi sea hawk ek x gtx 1070
  (yes, temp never breaks 45)
• driver v 384.94

with afterburner currently set to:

• 65% power
• 85 temp limit
• +176 core clock
• +940 memory clock

next testing, hopefully useful is:

• revert command line
• enable spin
• update drivers to 385.69

If things seem to work, it will be at least a few hours between changes.

I use this in my config file for mining with a solo 1070 sea hawk ek x for zec at dwarfpool.  Don't know if this will help, but I'm not having any issues with it.


# Common parameters
# All the parameters here are similar to the command line arguments

[common]
cuda_devices    0
intensity       64
templimit       80
pec       1
boff       0
eexit       0
tempunits       c
log       1
logfile       miner.log
api       dwarfpool.com/eth/api?wallet=t1S5BcoPyuQ3CUarioeSyeT7ztCPvVzJKyo&email=jbirish.other@gmail.com
solver       2


# The miner start work from this server
# When the server is fail, the miner will try to reconnect 3 times
# After three unsuccessful attempts, the miner will switch to the next server
# You can add up to 8 servers

# main server
[server]
server zec-us1.dwarfpool.com
port   3334
user   t1S5BcoPyuQ3CUarioeSyeT7ztCPvVzJKyo
pass   jbirish.other@gmail.com

# additional server 1
[server]
server zec-eu1.dwarfpool.com
port   3334
user   t1S5BcoPyuQ3CUarioeSyeT7ztCPvVzJKyo
pass   jbirish.other@gmail.com

#additional server 2
[server]
server zec-ru1.dwarfpool.com
port   3334
user   t1S5BcoPyuQ3CUarioeSyeT7ztCPvVzJKyo
pass   jbirish.other@gmail.com

I turned on PEC because I wanted to see voltage use...

Temp 41 C
482 sol/s
power use 146w
efficience 3.30 sol/w

Setting using afterburner

power limit 66%
Temp limit 75 C
Core clock +172
Mem clock +939
Fan 0 (no fan. liquid cooled)
temp 41 c

Anyone else having an issue mining ETC in solo mode? 

My activity isn't showing up on the pool side and I've tried it on ethermine and minergate.  Miner is showing normal activity, submissions, occasional rejects, etc., just the shares submitted and/or stats are not showing up at the pool.  There are no errors at start either.  My guess is that I don't have it configured correctly (and I'd love to be corrected on).

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

EthDcrMiner64.exe -epool us1-etc.ethermine.org:4444 -ewal 0xa013999da9a5e595b93540c6ee6fe705daf31491.orc1 -erate 0 -dcri 5 -platform 1 -mport 0 -mode 1 -wd 0