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

[Claymore]

On the rigs that i have connected to the same network as my ETH Pool ( one PC running geth ) i get the
"No new jobs where received from the pool"  error

its connected to the pool, it shows GPU temp but it wont start mining

any suggestions?

geth must show "imported 1 block" message a few times per minute. If it does not, that's the reason.

[1714291317]

1714291317

[1714291317]

1714291317

[1714291317]

1714291317

[1714291317]

1714291317

[36524s]

I have flashed my bios and 4 out of my 5 cards are running at 29mh but 1 is running at 18. Is there an easy way of identifying which physical card it is using the Claymore mining app (which is awesome btw!!!)?

See it tempo on claymore, example Gpu1 65c, press 1 on your keyboard, it ill stop mining on it, go to msi afterburn search for a low temp card, stop it fans, profit

Man that's perfect! Thanks!

[CoRpO]

On the rigs that i have connected to the same network as my ETH Pool ( one PC running geth ) i get the
"No new jobs where received from the pool"  error

Screenshot

http://imgur.com/a/veWvW

its connected to the pool, it shows GPU temp but it wont start mining

any suggestions?

Do you run the latest geth ? 1.4.14 ? If not, it's the reason, due to latest attacks against the network
You can find it here : https://github.com/ethereum/go-ethereum/releases

[maxmad_x]

Is there any way to specify difficulty in dual mining?

[alevlaslo]

-logfile 0 do not working at 7.1

[wll1rah]

another issue with Linux version, from few days it constantly switching SIA pools every 30-40minutes..
Windows version is ok, even if I revert rigs :S

Code:

SC: http error #28.
 SC: Failed to check work on pool, retry in 10 sec..

This error code means "operation timeout".
I can say again and again: don't use Linux if you can use Windows! Most problems are related not to miner but to Linux itself and I have to find workarounds all the time.

Hmm Windows is too expensive, and is unstable  if miner crash =windows crash and hard reset is necessary. If on linux fail = just kill the process

you can do the same on windows and it isn't to expensive since you can buy a POS tablet and use the product key from that, which you can get using slmgr or grab from the bios since they usually enable secure boot.

[Ziscadas]

I have flashed my bios and 4 out of my 5 cards are running at 29mh but 1 is running at 18. Is there an easy way of identifying which physical card it is using the Claymore mining app (which is awesome btw!!!)?

You can use -di command to activate just one card and see if that cards is working with the GPU usage in the MSI afterburner.

[Claymore]

-logfile 0 do not working at 7.1

Where did you find "-logfile 0" option value? It must be filename, not "0" or "1" (or do you want to name file as "0"?). From readme:

-logfile debug log file name. After restart, miner will append new log data to the same file. If you want to clear old log data, file name must contain "noappend" string.
   If missed, default file name will be used.

If you want to disable logging, use "-dbg -1".

[kenshirothefist]

Claymore, you could fix the issue when using NVIDIA GPUs without fans (watercooling, server-grade GPUs, etc.):

Code:

NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
NVML: cannot get fan speed, error 3
GPU0 t=48C fan=0%, GPU1 t=76C fan=0%, GPU2 t=44C fan=0%, GPU3 t=71C fan=0%, GPU4 t=63C fan=0%, GPU5 t=52C fan=0%, GPU6 t=61C fan=0%, GPU7 t=50C fan=0%

Code:

+-----------------------------------------------------------------------------+
| NVIDIA-SMI 367.48                 Driver Version: 367.48                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Tesla M60           Off  | 0000:05:00.0     Off |                    0 |
| N/A   50C    P0   111W / 150W |   1766MiB /  7613MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   1  Tesla M60           Off  | 0000:06:00.0     Off |                    0 |
| N/A   81C    P0   118W / 150W |   1768MiB /  7613MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+

[gorgamin]

Claymore, any idea what the following might be?

4x RX470, win10:

10:56:51:597   1150   em hbt: 0, dm hbt: 0, fm hbt: 63,
10:56:51:597   1150   watchdog - thread 0, hb time 78
10:56:51:613   1150   watchdog - thread 1, hb time 219
10:56:51:613   1150   watchdog - thread 2, hb time 219
10:56:51:613   1150   watchdog - thread 3, hb time 94
10:56:51:613   1150   watchdog - thread 4, hb time 109
10:56:51:613   1150   watchdog - thread 5, hb time 234
10:56:51:613   1150   watchdog - thread 6, hb time 23828
10:56:51:628   1150   watchdog - thread 7, hb time 23688
10:56:51:628   1150   WATCHDOG: GPU error, you need to restart miner

Faulty GPU, or Riser?
Thanks in advance, if you have a XMR address I'll buy you an untraceable beer^^

[Claymore]

Claymore, you could fix the issue when using NVIDIA GPUs without fans (watercooling, server-grade GPUs, etc.):

Ok, I see, you mean not to show messages. Ok, I will hide messages so they will appear in log file only.

Claymore, any idea what the following might be?

4x RX470, win10:

10:56:51:597   1150   em hbt: 0, dm hbt: 0, fm hbt: 63,
10:56:51:597   1150   watchdog - thread 0, hb time 78
10:56:51:613   1150   watchdog - thread 1, hb time 219
10:56:51:613   1150   watchdog - thread 2, hb time 219
10:56:51:613   1150   watchdog - thread 3, hb time 94
10:56:51:613   1150   watchdog - thread 4, hb time 109
10:56:51:613   1150   watchdog - thread 5, hb time 234
10:56:51:613   1150   watchdog - thread 6, hb time 23828
10:56:51:628   1150   watchdog - thread 7, hb time 23688
10:56:51:628   1150   WATCHDOG: GPU error, you need to restart miner
Faulty GPU, or Riser?
Thanks in advance, if you have a XMR address I'll buy you an untraceable beer^^

Probably riser if you don't overclock GPUs. Due to dev fee you already buy me a beer when you use my miner

[maxmad_x]

i give up and hope someone can help me...

i have 8x nvidia gtx 1080.
windows 7, cause its not yet working under ubuntu 16.04

i have installed cuda but keep getting errors....
i added one image which shows everything i can show or what is needed.
Newest drivers are installed etc etc.

dude. Did you install windows 10 anniversary edition? My problems got solved with that. 

[voidwalker]

is it a known issue with rx 480 8gb  that it takes 60-90 seconds after showing "POOL/SOLO version" for the miner to proceed to DAG generation?
happens on all my 4 rigs with windows 7/windows 10

[Claymore]

is it a known issue with rx 480 8gb  that it takes 60-90 seconds after showing "POOL/SOLO version" for the miner to proceed to DAG generation?
happens on all my 4 rigs with windows 7/windows 10

It depends on CPU speed, GPU name and number of GPUs, OpenCL recompiles kernels when necessary (for some cards). In past it worked faster, but currently miner has a lot of GPU code. I will reduce this delay, it's in my todo list.

[Joemid]

Hello

Its possible that claymore bat send a email to me when miner stopped?

Thanks

[tlmoscow]

is it a known issue with rx 480 8gb  that it takes 60-90 seconds after showing "POOL/SOLO version" for the miner to proceed to DAG generation?
happens on all my 4 rigs with windows 7/windows 10

Try to press anykey when miner window in focus...

[Claymore]

Hello

Its possible that claymore bat send a email to me when miner stopped?

Thanks

You can execute .bat file in EthMan when miner stopped/disconnected/overheated or its hashrate is low. Probably you can send email from .bat.
Miner itself cannot send email, use pool for it.

[MantaMine]

Claymore, any idea what the following might be?

4x RX470, win10:

10:56:51:597   1150   em hbt: 0, dm hbt: 0, fm hbt: 63,
10:56:51:597   1150   watchdog - thread 0, hb time 78
10:56:51:613   1150   watchdog - thread 1, hb time 219
10:56:51:613   1150   watchdog - thread 2, hb time 219
10:56:51:613   1150   watchdog - thread 3, hb time 94
10:56:51:613   1150   watchdog - thread 4, hb time 109
10:56:51:613   1150   watchdog - thread 5, hb time 234
10:56:51:613   1150   watchdog - thread 6, hb time 23828
10:56:51:628   1150   watchdog - thread 7, hb time 23688
10:56:51:628   1150   WATCHDOG: GPU error, you need to restart miner

Faulty GPU, or Riser?
Thanks in advance, if you have a XMR address I'll buy you an untraceable beer^^

Did you set the virtual memory to the size recommended in the readme?

[Claymore]

v7.2:

- added "-lidag" option to reduce intensity of DAG generation, it can help with OC or weak PSU.
- added temperature/fan monitoring for Linux version for gpu-pro drivers. Only monitoring is supported currently, not management.
- "r" key reloads pools from epools.txt and dpools.txt in runtime.
- fixed issue with wrong detection of card names.
- systems with up to 32 GPUs are supported now (with some minor limitations).
- Linux version: fixed issue with closing miner with "Ctrl-C".
- several minor improvements and bug fixes.
- EthMan: added "total online miners" and "total working gpus" info.
- EthMan: added color and font size options for the list of miners.

[voidwalker]

another issue with Linux version, from few days it constantly switching SIA pools every 30-40minutes..
Windows version is ok, even if I revert rigs :S

Code:

SC: http error #28.
 SC: Failed to check work on pool, retry in 10 sec..

This error code means "operation timeout".
I can say again and again: don't use Linux if you can use Windows! Most problems are related not to miner but to Linux itself and I have to find workarounds all the time.

Hmm Windows is too expensive, and is unstable  if miner crash =windows crash and hard reset is necessary. If on linux fail = just kill the process

you can do the same on windows and it isn't to expensive since you can buy a POS tablet and use the product key from that, which you can get using slmgr or grab from the bios since they usually enable secure boot.

what is a POS tablet?

is it a known issue with rx 480 8gb  that it takes 60-90 seconds after showing "POOL/SOLO version" for the miner to proceed to DAG generation?
happens on all my 4 rigs with windows 7/windows 10

Try to press anykey when miner window in focus...

I tried that, it's not because console scrolling is stuck. It's something else. Seems very random sometimes.