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

[GabryRox]

Nice work with 9.3 , before i could oc rx480 4GB hynix memory only 1920-1950, now without peoblems can to 2080 at least (still samsung memory better with 9.2 and 9.3 to 2150 without problem) Who would want buy 8GB cards when 4GB do the same work...

Yeah, that was my thought as well when buying 4 rigs worth of 470 4GB over the past 6 months. However, I have heard that the potential life is likely longer on the 8GB variety due to ever-expanding difficulties of mining algos, etc.  While that in theory may have some validity, I doubt the 4GB versions will be ineffective any time soon. I fully expect them to very productive at least through the end of 2017 and hopefully beyond. Personally, I think that ETH will go POC before the 4GB 400 series becomes ineffective in mining it, so i am happy with my 4gb versions that I got for much cheaper than the 8gb variety.

[RobertD]

Hello mining community,

I would like to ask for some help. Recently bought a mining rig 6x RX 480

https://www.mindfactory.de/product_info.php/8GB-PowerColor-Radeon-RX-480-Red-Dragon-Aktiv-PCIe-3-0-x16--Retail-_1124443.html

I am using Biostar TB85 motherboard, 12 GB RAM, EVGA 1300w, 120ssd, intel celeron 2x2.8GHz, windows 10 64.


I have this problem. On minute after I start claymore miner hashrate on one card drop to 0 and I get report - GPU hangs in opencl call - Need to restart miner.

I am searching for solution for couple of days already.

- I tried different GPU drivers, if I try to install 17.3 or 17.4 crimson computer crash.

- Virtual memory is on 16GB.

- If I start a miner without this card which lost hashrate then same thing happen to other 5 cards, hashrate drop to 0 on all 5 cards.

- I reinstall windows and all drivers, still same issue

- I switch cables and cards, nothing positive happen.

- tried other miners, pools, old version of claymore miner..

- tried function -gser -eser

Tried probly everything i could find on google, still no solution. Not sure if that is specific problem of motherboard, graphic card? other parts are more or less standard mining parts and probly have nothing to do with that problem.

Hop someone can help or give any proposition what should I do or try.

Thank you

Best regards

Don't just plug in 6 cards and expect it to work. Don't randomly remove cards, windows drivers don't like it.

Test each card and pcie slot individually. That is how everyone else does it.

I'm averaging 1 faulty card per 10 new cards. Most fail within 10 days.

[PandaPanda!]

I have one rig in my farm which keeps crashing every 3 hours or so.

Usually I can open up the log file and find out which particular GPU is causing issues, and rectify the problem without much headache.  But this time, i'm getting this message...

13:18:08:445   5ac   buf: {"id":4,"jsonrpc":"2.0","result":true}
13:18:08:445   5ac   parse packet: 38
13:18:08:445   5ac   ETH: Share accepted (47 ms)!
13:18:08:445   5ac   new buf size: 0
13:18:09:865   eb8   GPU0 t=70C fan=82%, GPU1 t=67C fan=78%, GPU2 t=65C fan=81%, GPU3 t=65C fan=74%, GPU4 t=71C fan=79%
13:18:09:865   eb8   em hbt: 0, fm hbt: 16,
13:18:09:865   eb8   watchdog - thread 0, hb time 250
13:18:09:865   eb8   watchdog - thread 1, hb time 32
13:18:09:865   eb8   watchdog - thread 2, hb time 32
13:18:09:865   eb8   watchdog - thread 3, hb time 19906
13:18:09:865   eb8   watchdog - thread 4, hb time 234
13:18:09:865   eb8   watchdog - thread 5, hb time 32
13:18:09:865   eb8   watchdog - thread 6, hb time 297
13:18:09:865   eb8   watchdog - thread 7, hb time 94
13:18:09:865   eb8   watchdog - thread 8, hb time 125
13:18:09:865   eb8   watchdog - thread 9, hb time 328
13:18:09:865   eb8   WATCHDOG: GPU error, you need to restart miner
13:18:09:865   eb8   Rebooting


Its not specifically telling me which GPU is having issues, although i'm assuming its whatever was working on "thread 3" - how can I find out which GPU is working on thread 3?  Claymore, please help!  This is driving me nuts.   This rig usually hangs after the "Rebooting" message.

2 threads per GPU in their order, "time 19906"

So thread 3 is GPU1?

[PandaPanda!]

@Claymore - your warning system on ethmon is not working properly.  When the batch file runs, it always returns "1" for %2 variable, regardless of whether the rig is overheating, low hash, or offline - it will always return "1".  Please fix this! Thanks!

[Claymore]

@Claymore - your warning system on ethmon is not working properly.  When the batch file runs, it always returns "1" for %2 variable, regardless of whether the rig is overheating, low hash, or offline - it will always return "1".  Please fix this! Thanks!

Just check it, it works properly. My test:
1. Start miner and EthMan.
2. Add miner to EthMan, set zero delay for BAT file.
3. In miner properties, set target hashrate x2 more than miner produces. BAT is started immediately, sample.bat shows "Problem ID: 3".
4. Return target hashrate to zero.
5. Set target temperature as 10C. BAT is started immediately, sample.bat shows "Problem ID: 2".

If you get some different result, let me know step-by-step guide how to reproduce the issue.

[AlainC]

Hi,
I just build a Rig with 2 RX480 8G (Saphire) and an Asrock H81 pro btc v2 (4GB dram, +20GB swap), on ubuntu 16.04 desktop and amdgpu-pro-17.10-414273 (reinstalled from scratch with a clean procedure)
I don't yet have all my risers so GPU 0 is on my 16x PCIE slot.
Rom are stock (I suppose, reconditioned).
I used claymore 9.3 to mine ETH only.
I optimised ethi and dcri,
my config.txt contains

Code:

-mode 1 -asm 2 -etha 0,0 -dcri 12,12 -ethi 16,16
-tt 80 -ttli 85 -tstop 90 -fanmin 80
-etht 200 -ftime 10 -r 1 -retrydelay 5
-gser 1

and for the environment I need 64bits pointers, or else it does not work.

Code:

GPU_FORCE_64BIT_PTR=1
GPU_MAX_HEAP_SIZE=100
GPU_USE_SYNC_OBJECTS=1
GPU_MAX_ALLOC_PERCENT=100
GPU_SINGLE_ALLOC_PERCENT=100

and all seemed fine. never invalid shares, stable throughput at 24.535MH/s*2 (total >49MH/s ...). I consume 395W from the plug (MB consume about 50W).

at the beginning there was no other message than

WATCHDOG: GPU 0 hangs in OpenCL call, exit

but with time  I caught kernel messages

kernel: gmc_v8_0_process_interrupt: 36 callbacks suppressed
kernel: amdgpu 0000:01:00.0: GPU fault detected: 147 0x00504802
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001E920A
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04048002
kernel: amdgpu 0000:01:00.0: VM fault (0x02, vmid 2) at page 2003466, read from 'TC4' (0x54433400) (72)
...
WATCHDOG: GPU 0 hangs in OpenCL call, exit
...
gmc_v8_0_process_interrupt: 36 callbacks suppressed
amdgpu 0000:01:00.0: GPU fault detected: 146 0x0600480c
amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001032C0
amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C
amdgpu 0000:01:00.0: VM fault (0x0c, vmid 4) at page 1061568, read from 'TC4' (0x54433400) (72)
amdgpu 0000:01:00.0: GPU fault detected: 147 0x06004808
amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001032C0
amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x08048008
amdgpu 0000:01:00.0: VM fault (0x08, vmid 4) at page 1061568, read from 'TC4' (0x54433400) (72)
amdgpu 0000:01:00.0: GPU fault detected: 146 0x0678040c
amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001432CF
amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0800400C
amdgpu 0000:01:00.0: VM fault (0x0c, vmid 4) at page 1323727, read from 'TC1' (0x54433100) (4)
...
amdgpu 0000:01:00.0: GPU fault detected: 147 0x06004808
amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001432C0
amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x08048008
amdgpu 0000:01:00.0: VM fault (0x08, vmid 4) at page 1323712, read from 'TC4' (0x54433400) (72)
...
WATCHDOG: GPU 0 hangs in OpenCL call, exit
...
kernel: gmc_v8_0_process_interrupt: 36 callbacks suppressed
kernel: amdgpu 0000:01:00.0: GPU fault detected: 146 0x06404404
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001832C8
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04044004
kernel: amdgpu 0000:01:00.0: VM fault (0x04, vmid 2) at page 1585864, read from 'TC5' (0x54433500) (68)
kernel: amdgpu 0000:01:00.0: GPU fault detected: 146 0x0668440c
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001832CD
kernel: amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0404400C
kernel: amdgpu 0000:01:00.0: VM fault (0x0c, vmid 2) at page 1585869, read from 'TC5' (0x54433500) (68)
...
WATCHDOG: GPU 0 hangs in OpenCL call, exit
...
ethdcrminer64[1166]: ETH - Total Speed: 49.078 Mh/s, Total Shares: 41, Rejected: 0, Time: 01:03
ethdcrminer64[1166]: ETH: GPU0 24.539 Mh/s, GPU1 24.539 Mh/s
ethdcrminer64[1166]: GPU0 t=77C fan=72%, GPU1 t=75C fan=72%
gmc_v8_0_process_interrupt: 36 callbacks suppressed
amdgpu 0000:01:00.0: GPU fault detected: 147 0x06004808
amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001032C0
amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04048008
amdgpu 0000:01:00.0: VM fault (0x08, vmid 2) at page 1061568, read from 'TC4' (0x54433400) (72)
amdgpu 0000:01:00.0: GPU fault detected: 146 0x0678480c
amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001832CF
...
amdgpu 0000:01:00.0: GPU fault detected: 146 0x06780804
amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001432CF
amdgpu 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04008004
amdgpu 0000:01:00.0: VM fault (0x04, vmid 2) at page 1323727, read from 'TC0' (0x54433000) (8)
...
 WATCHDOG: GPU 0 hangs in OpenCL call, exit
...

I have many hypothesis.

• One if that it does not work well with 16x slot ? Is that a known problem?
• One is that it is related to overheating of the card (I've pushed the fan to test) . Is it s usual symptom?
• One is overclocking (I did not change ROM but maybe the card is modded). Is it a usual symptoom
• One is my DCRI/ETHI being "abusive" for the card . Is it a typical symptom?
• One is software problem. NB: I've migrated to 9.2. maybe some option to tweak? Since GPU1 is OK (maybe it does not have time to worry), I'm not convinced.

The good point is that the watchdog works well...

[ish894]

Could someone please help me with running claymore 9.3 for ethereum? Every time I try - it starts, initialises GPU and then closes itself automatically. What I am doing wrong here? Which crimson version should I use for Claymore? I've tried earlier versions of Claymore and it's the same issue.

Here's my configuration:

• OS: Windows 10 x64
• GPU: MSI RX480 8GB
• Crimson Version: 17.4.2

Last few lines from the log file:

Code:

.............................
10:42:22:274	1610	OpenCL platform: AMD Accelerated Parallel Processing
10:42:22:284	1610	OpenCL platform: AMD Accelerated Parallel Processing
10:42:22:299	1610	OpenCL initializing...
10:42:22:309	1610	AMD Cards available: 2 
10:42:22:318	1610	GPU #0: Ellesmere, 8192 MB available, 36 compute units
10:42:22:328	1610	GPU #0 recognized as Radeon RX 480/580
10:42:22:337	1610	GPU #1: Ellesmere, 8192 MB available, 36 compute units
10:42:22:347	1610	GPU #1 recognized as Radeon RX 480/580
10:42:22:356	1610	POOL/SOLO version
10:42:22:365	1610	b343 
10:42:22:373	1610	Platform: Windows

Thanks.

[AzzAz]

I have one rig in my farm which keeps crashing every 3 hours or so.

Usually I can open up the log file and find out which particular GPU is causing issues, and rectify the problem without much headache.  But this time, i'm getting this message...

13:18:08:445   5ac   buf: {"id":4,"jsonrpc":"2.0","result":true}
13:18:08:445   5ac   parse packet: 38
13:18:08:445   5ac   ETH: Share accepted (47 ms)!
13:18:08:445   5ac   new buf size: 0
13:18:09:865   eb8   GPU0 t=70C fan=82%, GPU1 t=67C fan=78%, GPU2 t=65C fan=81%, GPU3 t=65C fan=74%, GPU4 t=71C fan=79%
13:18:09:865   eb8   em hbt: 0, fm hbt: 16,
13:18:09:865   eb8   watchdog - thread 0, hb time 250
13:18:09:865   eb8   watchdog - thread 1, hb time 32
13:18:09:865   eb8   watchdog - thread 2, hb time 32
13:18:09:865   eb8   watchdog - thread 3, hb time 19906
13:18:09:865   eb8   watchdog - thread 4, hb time 234
13:18:09:865   eb8   watchdog - thread 5, hb time 32
13:18:09:865   eb8   watchdog - thread 6, hb time 297
13:18:09:865   eb8   watchdog - thread 7, hb time 94
13:18:09:865   eb8   watchdog - thread 8, hb time 125
13:18:09:865   eb8   watchdog - thread 9, hb time 328
13:18:09:865   eb8   WATCHDOG: GPU error, you need to restart miner
13:18:09:865   eb8   Rebooting


Its not specifically telling me which GPU is having issues, although i'm assuming its whatever was working on "thread 3" - how can I find out which GPU is working on thread 3?  Claymore, please help!  This is driving me nuts.   This rig usually hangs after the "Rebooting" message.

2 threads per GPU in their order, "time 19906"

So thread 3 is GPU1?

My GOD! Tread 1 and 2 are CARD 0
            Tread 3 and 4 are CARD 1
and so on. Your problem is card 1 ( second card of 4 )

[AzzAz]

Hello mining community,

I would like to ask for some help. Recently bought a mining rig 6x RX 480

https://www.mindfactory.de/product_info.php/8GB-PowerColor-Radeon-RX-480-Red-Dragon-Aktiv-PCIe-3-0-x16--Retail-_1124443.html

I am using Biostar TB85 motherboard, 12 GB RAM, EVGA 1300w, 120ssd, intel celeron 2x2.8GHz, windows 10 64.


I have this problem. On minute after I start claymore miner hashrate on one card drop to 0 and I get report - GPU hangs in opencl call - Need to restart miner.

I am searching for solution for couple of days already.

- I tried different GPU drivers, if I try to install 17.3 or 17.4 crimson computer crash.

- Virtual memory is on 16GB.

- If I start a miner without this card which lost hashrate then same thing happen to other 5 cards, hashrate drop to 0 on all 5 cards.

- I reinstall windows and all drivers, still same issue

- I switch cables and cards, nothing positive happen.

- tried other miners, pools, old version of claymore miner..

- tried function -gser -eser

Tried probly everything i could find on google, still no solution. Not sure if that is specific problem of motherboard, graphic card? other parts are more or less standard mining parts and probly have nothing to do with that problem.

Hop someone can help or give any proposition what should I do or try.

Thank you

Best regards

Don't just plug in 6 cards and expect it to work. Don't randomly remove cards, windows drivers don't like it.

Test each card and pcie slot individually. That is how everyone else does it.

I'm averaging 1 faulty card per 10 new cards. Most fail within 10 days.

Tribrzinec : just reinstal Windows and use drivers from 16.9.1 to 16.11.5.  Then if problems, use last DDU and reinstall same drivers.

[wishxy]

"ETH: Job timeout, disconnect, retry in 20 sec..." After I've installed 9.3,  I'm getting this message all the time. Any help?
RX 470 8/4GB
ETH:Dwrarfpool
DCR: Suprnova

[woodaxe]

Running 6x 470 nitro + oc 8gig  one card hashes at 19m/hs the others at 29 m/hash i assume the one running at 19 M/hash is the card ive got the monitor plugged into  do i need a dummy plug and to use teamviewer to get the card up to 29 m/hash the same as the others and if so any links to suitable dummy plugs for sale

 many thanks

[coinzoid]

I've a question regarding stats:

Pool reports following:
290.9 MH/s 249.0 MH/s 277.0 MH/s
Reported hashrate - Effective 60 mins - Effective 24 hours

Sometimes my effective 60 mins goes over 300, but sometimes goes below 250 just like in this example. I understand that if I mine an uncle block hash rate increase on pool is expected, but is it also expected to lose regular hashrate on 60 mins cycle and 24 hours this much?

I have 10 gpus currently. All RX 480 nitro + oc with Samsung Memory.

[rednoW]

2 Claymore

Just tried "e" button to switch to pool from epools.txt list without restarting the whole miner. Very convinient!
But when I switch to pool from epools.txt it treats it as Failover pool and switches back to main pool after some time (to the pool from starting command line the miner was run).
Is there a way to manually switch to the pool and it will be the main pool during this miner session and others become Failover pools?

[RD965]

I have rigs with Asus RX480 8GB with Samsung memory and also Sapphire Nitro's+ RX470 4GB, I have been switching to the latest versions of the miner but I have noticed they do not necessarily improve the hashrate

Is there some necessary setting like -asm 1 that would improve hashrate or decrease power draw? Which version of the miner do you guys recommend as best?

[notbatman]

I have rigs with Asus RX480 8GB with Samsung memory and also Sapphire Nitro's+ RX470 4GB, I have been switching to the latest versions of the miner but I have noticed they do not necessarily improve the hashrate

Is there some necessary setting like -asm 1 that would improve hashrate or decrease power draw? Which version of the miner do you guys recommend as best?

I'm getting substantial gains on my R9, anybody with a nano should be getting an impressive hashrate.

IMO, If you're going to shell out a grand for a card the nano is the ticket, these 1080s are so flimsy and hash like an RX460.

[fisheth]

hi guys,my gpu rx480 4gb,anyone can help mod it?speed just 24.xx mh/s
really appreciate it

[BenCodie]

can anybody share hashrate of SAPPHIRE NITRO Radeon™R9 FURY 4G HBM with Back Plate https://www.newegg.com/Product/Product.aspx?Item=9SIA57546D8028&cm_re=R9_FURY_4G-_-9SIA57546D8028-_-Product

I'm getting brand new unused for $290 from a friend

Thanks

[h311m4n]

hi guys,my gpu rx480 4gb,anyone can help mod it?speed just 24.xx mh/s
really appreciate it

Don't mean to be rude man, but ever heard of a search function? Either here or on Google, you'll find answers to your question just by searching a bit...

[hendsan]

anyone have good config bat file for dual mining eth and dcr? thanks

[fredeq]

can anybody share hashrate of SAPPHIRE NITRO Radeon™R9 FURY 4G HBM with Back Plate https://www.newegg.com/Product/Product.aspx?Item=9SIA57546D8028&cm_re=R9_FURY_4G-_-9SIA57546D8028-_-Product

I'm getting brand new unused for $290 from a friend

Thanks

You can check my values for this card at https://whattomine.com/coins
Select number of fury cards and deselect any other you might have selected (probably 280x)

All values are for 1050/500 with -0.1V undervolt.