Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 1050. (Read 6590565 times)

is there any parameter in config.txt file to not use GPU2?
I'd like to use GPU 0,1 and 3 (they are 4GB cards) and use GPU2 for another miner.

Don't know.

2gb users can still mine expanse

ETH should change to PoS sometime during 2017, right?

So, now did we hit the 2GB limit or should add something in the config file?

remember to put this is your batfile:

GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100

The 2GB limit will be hit around mid-December 2016
The 3GB limit will be hit around mid-April 2018
The 4GB limit will be hit around mid-September 2019

My 2GB AMD r9 270 GPU stopped running. it was running fine before.
My other 3 gpus are r9 280x 4gb. They are fine.


Here the miner output:

AMD Cards available: 4
GPU #0: Tahiti, 3015 MB available, 32 compute units
GPU #0 recognized as Radeon 280X/380X
GPU #1: Tahiti, 3015 MB available, 32 compute units
GPU #1 recognized as Radeon 280X/380X
GPU #2: Pitcairn, 1993 MB available, 20 compute units
GPU #2 recognized as Radeon 270/270X
GPU #3: Tahiti, 3015 MB available, 32 compute units
GPU #3 recognized as Radeon 280X/380X
POOL/SOLO version
GPU #0: set -etha as 0 (ETH algo for fast cards)
GPU #1: set -etha as 0 (ETH algo for fast cards)
GPU #2: set -etha as 1 (ETH algo for slow cards)
GPU #3: set -etha as 0 (ETH algo for fast cards)
No NVIDIA CUDA GPUs detected.
Total cards: 4
ETH: Stratum - connecting to 'eu1.ethermine.org' <51.255.64.43> port 4444
ETH: Stratum - Connected (eu1.ethermine.org:4444)
ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
ETH: qtminer stratum mode
"-allcoins" option is set, default pools will be used for devfee, check "Readme" file for details.
Watchdog enabled

ETH: Authorized
Setting DAG epoch #89...
Setting DAG epoch #89 for GPU #0
Create GPU buffer for GPU #0
Setting DAG epoch #89 for GPU #1
Create GPU buffer for GPU #1
Setting DAG epoch #89 for GPU #2
Create GPU buffer for GPU #2
GPU 2, OpenCL error -4 (0) - cannot create DAG on GPU
Setting DAG epoch #89 for GPU #3
Create GPU buffer for GPU #3
Setting DAG epoch #89 for GPU #2
GPU 2, OpenCL error -4 (0) - cannot create DAG on GPU
GPU 0 DAG creation time - 5243 ms
Setting DAG epoch #89 for GPU #0 done
GPU 1 DAG creation time - 5354 ms
Setting DAG epoch #89 for GPU #1 done
GPU 3 DAG creation time - 5342 ms
Setting DAG epoch #89 for GPU #3 done
ETH: 11/23/16-14:11:38 - SHARE FOUND - (GPU 3)
ETH: Share accepted (49 ms)!
GPU0 t=50C fan=80%, GPU1 t=42C fan=80%, GPU2 t=37C fan=80%, GPU3 t=45C fan=80%
WATCHDOG: GPU error, you need to restart miner

It is always a very bad idea to use external fixed IP address directly on your miner, in better case you must use firewall like PFsense or usual router, it is harder for hackers to scan miners through NAT.

Version 2.5 just cut the Options.ini file to 25 nodes only. There were about 30 entries before. I stopped and started EthMan many times in the same directory before. I stopped it either by simply closing or via Task Manager. And the last time was via Task Manager. But this is the first time it's cut the list of nodes.

It's possible, but I foresee some problems:

1. Pools will have x2 connections all the time.
2. Some people may think that I take more fee than expected.
3. Devfee thread will have much less hashrate than main thread so pool will use much low target and people will ask again and again why devfee has same number of shares as main thread.

So I don't add this feature for now.

Claymore I have asked this before, is there way to include devfee in the hash? Like optiminer does?

Read README or OP, "-mport" option.

To Claymore:

Yesterday my rig was cracked through management port of Claymore Dual Miner. The rig has an external fixed IP address, than and the hacker used.

As a result of cracking in the directory of a miner start.bat on following was changed :


(my e-mail is changed)

After change of start.bat my miner was remotely restarted by the hacker, and several hours it worked for addresses of wallets of this bastard.
https://eth.nanopool.org/account/0x2303eB2dc0Fa11B3a1B330F80e7D0D360E751c1B

It is possible to exclude somehow this possibility of cracking further? Thanks in advance!

So far I replaced a port address with another from default port address...

2 All users: Beware!

This discussion of other similar attack of the same hacker: https://bitcointalksearch.org/topic/m.16915753

Changing the fan speed is a good idea, thanks 

can i mining only sia http with you miner? or only dual?

i'm getting 8mh/s per card for gigabyte 390 8gb any advice ?

Witch version of CLAYMORE'S miner is best for 390 8GB cards ?

I do not agree, tell my why MSI Afterburner can detect the card order... ?
You can use a different Windows system or drivers but the card order is ALWAYS THE SAME.

For ASRock H81 Pro BTC:

PCIE1 - GPU2
PCIE2 - GPU1
PCIE3 - GPU3
PCIE4 - GPU4
PCIE5 - GPU5
PCIE6 - GPU6

You can check it on your miner.

1. Run MSI Afterburner
2. Unlink the same GPU's settings
3. Change the fan speed to 100% and check the card number

even cooler, I use '+' or '-' to change it dynamically  .  This miner still has many features I look forward to trying.

All motherboards have that problem, find one that doesn't and I'll be seriously impressed.. To start the motherboard itself does not order them how they are physically laid down (e.g., all 16X slots take precedence, then it's a crap shoot on 1X slots based on dedicated or shared lanes), then you have the AMD driver on top of it.

same here... it is really a nightmare when I need to debug something..

thanks AriesIV10 for the instructions.