Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)

[skdsw]

Hi
Does -ttli option works with nvidia cards?

[1713518024]

1713518024

[1713518024]

1713518024

[1713518024]

1713518024

[1713518024]

1713518024

[1713518024]

1713518024

[valbuena77]

Sinces today i get this error , whats this ?
https://i.imgur.com/PeOh4nB.jpg

[afm]

Hi all,

Using the same hardware, i get about 0.5 MH/s using Linux.

Is this normal? If so - why?

[tutu_young]

I can't for the life of me get Siacoin to dual mine. Anything obvious I'm doing wrong? Ethereum runs fine, but SC never gets authorized, and my SC hash rate just sits at 0.000 MH/s and I just keep getting SC job timeouts.

My startup script:

Code:

ethdcrminer64.exe -epool eth-us-east1.nanopool.org:9999 -ewal ***my ethereum info*** -epsw x -dpool stratum+tcp://sia-us-west1.nanopool.org:7777 -dwal ***my siacoin address***/***miner name***/***email address*** -ftime 10 -dcoin sia

My output (edited slightly for compactness):

Code:

����������������������������������������������������������������ͻ 
 � Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v9.7 � 
����������������������������������������������������������������ͼ 

ETH: 5 pools are specified 
Main Ethereum pool is eth-us-east1.nanopool.org:9999 
SC: 5 pools are specified 
Main Siacoin pool is sia-us-west1.nanopool.org:7777 
AMD OpenCL platform not found 
CUDA initializing... 
NVIDIA Cards available: 5 
CUDA Driver Version/Runtime Version: 9.0/8.0 
GPU #0: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1 
GPU #1: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1 
GPU #2: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1 
GPU #3: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1 
GPU #4: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1 
Total cards: 5 
ETH: Stratum - connecting to 'eth-us-east1.nanopool.org' <158.69.85.38> port 9999 
DUAL MINING MODE ENABLED: ETHEREUM+SIACOIN 
ETH: eth-proxy stratum mode 
ETH: Stratum - Connected (eth-us-east1.nanopool.org:9999) 
Watchdog enabled 
  SC: Stratum - connecting to 'sia-us-west1.nanopool.org' <45.32.71.82> port 7777 
Remote management (READ-ONLY MODE) is enabled on port 3333 

  SC: Stratum - Connected (sia-us-west1.nanopool.org:7777) 
ETH: Authorized 
Setting DAG epoch #133... 
Setting DAG epoch #133 for GPU0 
[snip]
Create GPU buffer for GPU0 
[snip]
GPU0 DAG creation time - 5327 ms 
Setting DAG epoch #133 for GPU0 done 
[snip]
 
ETH: 07/09/17-20:52:04 - SHARE FOUND - (GPU 0) 
ETH: Share accepted (140 ms)! 
Socket was closed remotely (by pool) 
  SC: Job timeout, disconnect, retry in 20 sec... 

ETH - Total Speed: 155.754 Mh/s, Total Shares: 1(1+0+0+0+0), Rejected: 0, Time: 00:00 
ETH: GPU0 32.165 Mh/s, GPU1 27.200 Mh/s, GPU2 31.693 Mh/s, GPU3 32.887 Mh/s, GPU4 31.810 Mh/s 
  SC - Total Speed: 0.000 Mh/s, Total Shares: 0(0+0+0+0+0), Rejected: 0 
  SC: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s

Notice in there that it says ETH: Authorized, but it never says anything about SC: Authorized? I think this is my problem, but I don't know what else to do about it.

What I've tried so far, none of which have been successful:

• Generating a new Siacoin wallet address
• Changing my email address to a Gmail address
• -dcri intensities from about 1 to 500
• switching from Nanopool to Miningpoolhub
• switching to different Nanopool servers
• Claymore 9.5 and 9.7

Any thoughts?

Did you comment out the config file dpools.txt and\or epools.txt? the miner will go check those file first then the parameter in the .bat file.

[delle54]

Did you comment out the config file dpools.txt and\or epools.txt? the miner will go check those file first then the parameter in the .bat file.

Please learn to read the readme.txt. The miner only reads the dpools.txt and/or epools.txt if nothing is specified in the start.bat file.

[skdsw]

I can't for the life of me get Siacoin to dual mine. Anything obvious I'm doing wrong? Ethereum runs fine, but SC never gets authorized, and my SC hash rate just sits at 0.000 MH/s and I just keep getting SC job timeouts.

My startup script:

Code:

ethdcrminer64.exe -epool eth-us-east1.nanopool.org:9999 -ewal ***my ethereum info*** -epsw x -dpool stratum+tcp://sia-us-west1.nanopool.org:7777 -dwal ***my siacoin address***/***miner name***/***email address*** -ftime 10 -dcoin sia

Specify -allpools 1 -allcoins 1 in startup script

[Jdope]

Does anyone face a problem where the miner just stops? i mean the cards are running and everything is running but the miner just freezes

[cryptokizzy]

I can't for the life of me get Siacoin to dual mine. Anything obvious I'm doing wrong? Ethereum runs fine, but SC never gets authorized, and my SC hash rate just sits at 0.000 MH/s and I just keep getting SC job timeouts.

My startup script:

Code:

ethdcrminer64.exe -epool eth-us-east1.nanopool.org:9999 -ewal ***my ethereum info*** -epsw x -dpool stratum+tcp://sia-us-west1.nanopool.org:7777 -dwal ***my siacoin address***/***miner name***/***email address*** -ftime 10 -dcoin sia

Specify -allpools 1 -allcoins 1 in startup script

Thanks, but no luck there either. Same issue as before.

I think it's really weird that I get the "SC - Stratum: connected" line but never get a "SC Authorized" line. Would there be any weird firewall stuff that could be causing this that would let through ETH but not SC?

Did you comment out the config file dpools.txt and\or epools.txt? the miner will go check those file first then the parameter in the .bat file.

Everything in config.txt appears to be commented out already, and dpools and epools contain consistent info with what I'm putting into my startup script.

[cryptokizzy]

Does anyone face a problem where the miner just stops? i mean the cards are running and everything is running but the miner just freezes

Are you using Windows, and have you clicked on the command window? cmd.exe stops scrolling new text when you select even one character. If you push enter, it will scroll again.

[Bothebu]

My MSI GTX 1070 Gaming X cards went up 1.2 M/H each card with 9.7 version (no change in clock settings)!

@Claymore  Nice Job!

[scryptr]

If I understand correctly, the DAG is meant to be randomised on the fly, but I wanted to know 2 things :-
1) Is it possible to manually set the DAG Epoch?

or

2) Does anyone perhaps have an idea what is causing this issue?

Where did you hear that? Since I started mining its only going up

NICEHASH MINES NEWER DAGGERHASHIMOTO COINS--

Buyers of hashrate on NiceHash may direct your miner at alt-Ethereum coins that may be at very low Epochs.  That is, not all hashrate is directed at ETH, or at ETC.  If you mine on NiceHash, you cannot avoid the low Epoch coins.       --scryptr

[Jdope]

Does anyone face a problem where the miner just stops? i mean the cards are running and everything is running but the miner just freezes

Are you using Windows, and have you clicked on the command window? cmd.exe stops scrolling new text when you select even one character. If you push enter, it will scroll again.

Im using windows yeah but most of the times it stops without even me being there to press anything.

[achalmersman]

Hello.  Excuse my newbish question but I am trying to learn how to interpret the log files to diagnose stability issues I am having.  Does this mean GPU 2 is the GPU I should be questioning?  They all go out, but GPU 2 always leads the pack.  Any help is much appreciated!

21:48:57:240   2168   ETH: job is the same
21:48:57:240   2168   new buf size: 0
21:48:58:319   1434   recv: 51
21:48:58:319   1434   srv pck: 50
21:48:58:319   1434   srv bs: 0
21:48:58:334   1434   sent: 326
21:49:02:866   2138   GPU 2, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:866   2138   GPU 2, GpuMiner kx failed 1
21:49:02:866   2138   Set global fail flag, failed GPU2
21:49:02:866   213c   GPU 2, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:866   2138   GPU 2 failed
21:49:02:882   214c   GPU 4, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:882   2128   GPU 0, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:882   213c   GPU 2, GpuMiner kx failed 1
21:49:02:897   213c   Set global fail flag, failed GPU2
21:49:02:897   2158   GPU 6, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:897   2164   GPU 7, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:897   2140   GPU 3, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:913   214c   GPU 4, GpuMiner kx failed 1
21:49:02:913   2128   GPU 0, GpuMiner kx failed 1
21:49:02:913   2128   Set global fail flag, failed GPU0
21:49:02:913   213c   GPU 2 failed
21:49:02:928   2158   GPU 6, GpuMiner kx failed 1
21:49:02:928   2164   GPU 7, GpuMiner kx failed 1
21:49:02:928   2140   GPU 3, GpuMiner kx failed 1
21:49:02:913   214c   Set global fail flag, failed GPU4
21:49:02:944   2154   GPU 5, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:944   2128   GPU 0 failed
21:49:02:944   212c   GPU 0, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:928   2158   Set global fail flag, failed GPU6
21:49:02:960   2158   GPU 6 failed
21:49:02:960   2130   GPU 1, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:928   2140   Set global fail flag, failed GPU3
21:49:02:960   2148   GPU 4, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:975   214c   GPU 4 failed
21:49:02:975   2154   GPU 5, GpuMiner kx failed 1
21:49:02:975   212c   GPU 0, GpuMiner kx failed 1
21:49:02:928   2164   Set global fail flag, failed GPU7
21:49:02:991   215c   GPU 6, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:991   2130   GPU 1, GpuMiner kx failed 1
21:49:02:991   2144   GPU 3, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:03:007   2140   GPU 3 failed
21:49:03:007   2148   GPU 4, GpuMiner kx failed 1
21:49:02:975   2154   Set global fail flag, failed GPU5
21:49:03:007   2154   GPU 5 failed
21:49:03:007   2160   GPU 7, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:03:022   2164   GPU 7 failed
21:49:03:022   215c   GPU 6, GpuMiner kx failed 1
21:49:02:991   2130   Set global fail flag, failed GPU1
21:49:03:038   2144   GPU 3, GpuMiner kx failed 1
21:49:02:991   212c   Set global fail flag, failed GPU0
21:49:03:007   2148   Set global fail flag, failed GPU4
21:49:03:053   2148   GPU 4 failed
21:49:03:053   2160   GPU 7, GpuMiner kx failed 1
21:49:03:038   215c   Set global fail flag, failed GPU6
21:49:03:053   215c   GPU 6 failed
21:49:03:069   2130   GPU 1 failed
21:49:03:038   2144   Set global fail flag, failed GPU3
21:49:03:069   2144   GPU 3 failed
21:49:03:069   2150   GPU 5, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:03:053   2160   Set global fail flag, failed GPU7
21:49:03:085   2134   GPU 1, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:03:085   212c   GPU 0 failed
21:49:03:085   2150   GPU 5, GpuMiner kx failed 1
21:49:03:085   2160   GPU 7 failed
21:49:03:100   2134   GPU 1, GpuMiner kx failed 1
21:49:03:085   2150   Set global fail flag, failed GPU5
21:49:03:100   2150   GPU 5 failed
21:49:03:100   2134   Set global fail flag, failed GPU1
21:49:03:116   2134   GPU 1 failed
21:49:03:335   1f94   recv: 51
21:49:03:335   1f94   srv pck: 50
21:49:03:335   1f94   srv bs: 0
21:49:03:335   1f94   sent: 243
21:49:05:616   1c48   GPU0 t=60C fan=100%, GPU1 t=50C fan=70%, GPU2 t=58C fan=100%, GPU3 t=55C fan=100%, GPU4 t=63C fan=100%, GPU5 t=58C fan=100%, GPU6 t=59C fan=100%, GPU7 t=59C fan=100%
21:49:05:616   1c48   em hbt: 0, dm hbt: 0, fm hbt: 16,
21:49:05:616   1c48   watchdog - thread 0 (gpu0), hb time 2922
21:49:05:616   1c48   watchdog - thread 1 (gpu0), hb time 2813
21:49:05:632   1c48   watchdog - thread 2 (gpu1), hb time 2938
21:49:05:632   1c48   watchdog - thread 3 (gpu1), hb time 2829
21:49:05:632   1c48   watchdog - thread 4 (gpu2), hb time 2954
21:49:05:632   1c48   watchdog - thread 5 (gpu2), hb time 2875
21:49:05:632   1c48   watchdog - thread 6 (gpu3), hb time 2954
21:49:05:647   1c48   watchdog - thread 7 (gpu3), hb time 2859
21:49:05:647   1c48   watchdog - thread 8 (gpu4), hb time 2797
21:49:05:647   1c48   watchdog - thread 9 (gpu4), hb time 2906
21:49:05:647   1c48   watchdog - thread 10 (gpu5), hb time 2875
21:49:05:647   1c48   watchdog - thread 11 (gpu5), hb time 2969
21:49:05:663   1c48   watchdog - thread 12 (gpu6), hb time 2985
21:49:05:663   1c48   watchdog - thread 13 (gpu6), hb time 2891
21:49:05:663   1c48   watchdog - thread 14 (gpu7), hb time 2875
21:49:05:663   1c48   watchdog - thread 15 (gpu7), hb time 2985
21:49:05:663   1c48   WATCHDOG: GPU error, you need to restart miner
21:49:06:851   1c48   Restarting OK, exit...

[achalmersman]

Also, I my power graphs on this rig are way way different than my other Windows 10 desktop that only has 4 cards.  This one the power graphs go all over the place and the other machine they are a rock solid line.  Is this normal or does this indicate a problem?  Thanks again

https://drive.google.com/open?id=0B7yTVsE3BqDWRjQ2c1dCTWVEemM

Edit:  ^^^ That is a link to a screenshot picture.  I guess I can't figure out how to insert a picture in my post

[ranastic]

Why my rig have 6 Colorful P106-100 (GDDR5 Samsung(GPU-Z info)) can't increase memory clock higher than 270? if i try to increase to 300 or more Claymore tool will give me error:

GpuMiner cu_k1 failed 73, an illegal instruction was encountered

my PSU is 1600w

[ushba]

May be it is simple...
But HOW to exclude first two of six cards from mining in latest versions of miner (v. 9.6 & more)?

[jackbox]

May be it is simple...
But HOW to exclude first two of six cards from mining in latest versions of miner (v. 9.6 & more)?

Add switch "-di 2345" to the start.bat file. Cards 0 and 1 will not be mined.

[ushba]

Thanks tried it on my GTX 1070. Up to par with ethminer. speeds now
For dual mining I get quite some ETH hashrate drop for little DCR, so for now dual mining on my gtx 1070 is a no go.

well, dual-mining with gtx1070 still disappointed results ...

It depends on GPU, settings, selected coin, it's price and net diff. For example, for SIA on stock 1070 ccminer shows 1400MH/s. In dual mode in v9.7 I get 650MH/s SIA (so 45% of pure SIA speed) with only 2% ETH lost (about 25.8MH/s instead of 26.4MH/s).
DCR speed is not so good, agreed.

ETH - Total Speed: 119.699 Mh/s, Total Shares: 284, Rejected: 0, Time: 02:46
ETH: GPU0 28.884 Mh/s, GPU1 30.478 Mh/s, GPU2 30.198 Mh/s, GPU3 30.139 Mh/s
 SC - Total Speed: 2992.474 Mh/s, Total Shares: 843, Rejected: 1
 SC: GPU0 722.094 Mh/s, GPU1 761.959 Mh/s, GPU2 754.947 Mh/s, GPU3 753.474 Mh/s

gtx 1070 etc + sia

I would love to learn you setting mate. Currently 3 Asus Dual GTX1070 @ 8708MHz mem clock 80%TDP. I'm getting poor result on Sia. average 30.4mh/s for eth 350mh/s for sia per card which is not even half of yours. DCRI 35

-dcri 75

-dcri 75 is giving me 22Mh/S for ETH instead of 30 with default value.
I really have no idea how did you manage to get both SIA and ETH performing like this

same here.. any chance to share the secret behind?

Try to use  -dcri value between 15 and 20.   75 is TOO high.

[NoOneLt]

Thanks for the 9.7 version, nice work here.

[ushba]

May be it is simple...
But HOW to exclude first two of six cards from mining in latest versions of miner (v. 9.6 & more)?

Add switch "-di 2345" to the start.bat file. Cards 0 and 1 will not be mined.

Khm... is it still supported after version 9.6?