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

[fonost]

Has the memory controller load issue been solved, or a workaround found yet?

Running the latest claymore 9.3 on windows 10 with 16.11.5 drivers using the usual setx parameters. (Issue occurs on every driver I've tried)

I currently have 2 4gb reference 480s acting up with the last few versions of the miner. Troublesome cards are both Hynix memory.

This particular rig is my daily use PC and newly built with 3 RX 480. One card works great, while the other two have difficulties getting to 100% memory controller load. Getting stuck at 70%, 83%, and sometimes 90-94% depending on memory clocks.
It doesn't seem to matter which slot, or driver they are using.

I did spend some time testing various memory straps and timings for on the of the RX 480's.
The only way I was reliably able get 100% memory controller load was to use 1375 or 1425 straps copied over all others and keep the memory clocks no higher than 1750mhz. This seemed to be the only option despite the card being fully stable at much higher clocks. Occasionally a PC reboot would allow 1800mhz at 100% However more often than not, going over 1750mhz will instantly drop memory controller load to around 83% and hashrate down to around 19 mh/s.

Keeping the memory at 1750, and modding the bios to a rather low strap/tight timings it's possible to get 25.8 Eth and 774 DCR with dcri 30 (lowering dcr, only bumps it up to 25.9 give or take.) Compared to my other RX 480 which is working well at 29.3 Eth and 877 Dcr, or even a hynix 470 at 27 Eth these 480 seem stuck at a low hashrate.

I have yet to play around with the newest card, but I expect to hit a similar limitation.


This almost seems like a windows resource management/allocation issue than an problem with the card.

I saw a few similar posts back when 9.0 came out, and I'm hoping someone else with more experience, or luck has figured this out.

[a7med918]

Dear All
i am looking for Bios for Sapphire Rx480 8G Nitro+ with samsung Ram to get  stable higher hashrate for  Eth+ DCR . any one upload it please

[EdjOne]

Hi Claymore and Community.

I'm switched from 8.0 to 9.3 and noticed that time of share accepted increased 2-3 times. And totally effected pool average hashrate.
See below, (dual-mining or single mode result the same):

Version 8.0
ETH: Share accepted (62 ms)!

Version 9.3
ETH: Share accepted (156 ms)!
ETH: Share accepted (172 ms)!

So, seems this affect hashrate and I lost around 10% in 24 hours period.

Any suggestion are welcome, thanks in advance.

[pikachuy]

What can I expect from the
MSI Radeon RX 570 GAMING X
getting 22 from my RX470 Gaming X

You can expect a month long wait while you RMA their defective crap. I'm betting eventually they just hand me back the garbage cards and tell me to eat it.

That's why gotta go with XFX, from my experience, they got superb service. Got my RMA with working same model back to me in 1 week timeframe.

[chup]

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?

I believe You can achieve that if You use config-file and no pools specified in starting command line. Changing config file as well as epools/dpools files should bring You there.

[AlainC]

@claymore
As I understand ethdcrminer can overclock,under/overvolt, GPU or VRAM independently from the bios.
if you want to over/underclock a Polaris card, (RX470/480/570/580...) what is the minimum set of mod ?
I guess:

• Memory strides (shifting stride from lower freq to higher freq)
• downclocking GPU because ATI does not allow downclocking with the API you use

and for all the rest:

Code:

-cclock -mclock -cvddc -mvddc -powlim -tt -fanmin -fanmax 

am I right?

Is atitweak still useful?

[pwpwpw]

What can I expect from the
MSI Radeon RX 570 GAMING X
getting 22 from my RX470 Gaming X

You can expect a month long wait while you RMA their defective crap. I'm betting eventually they just hand me back the garbage cards and tell me to eat it.

What cards are you recommending - sub $200 with 22+ hashrate

Buyer beware with MSI, my Gigabyte RX card is working perfectly.

I heard r9 390 MSI cards OC the best and have the highest hashrate/stability, the RX series MSI suck ? About gigabyte, I bought 3years ago 3x r9 280x gigabyte and 5x asus dc2t, all of the gigabyte still run, after almost 24/7 3 years and 4 of the asus died within a year, all had fan failures withing 6months but 1 simply can't display anything, crashes during driver load. So in my opinion, gigabyte is pretty good, it's usually the cheapest card and maybe I've been lucky but they are quite durable, right now they are on zec mining with 380hour+ uptime. All I know, avoid asus, it's pretty easy now that they are priced the highest tho

[r79]

Been fiddling around with the -r 1 param, but I could not make it work.

Working on Ubuntu 16.04:
- I created "reboot.sh" in the claymore-dir, put in the reboot command, chmod 755, tested it manually, worked flawlessly.
- waited for the miner to crash, apparently the miner did try to reboot using the script, but it seems like the script never got called.

Is there any way to debug this? Any way to test it? What does Claymore call exactly? Is it beeing called as the superuser, as I'm starting ethdcrminer as root?

Any help is highly appreciated

[infowire]

NVIDIA DRIVERS:

9xx cards in Windows 10 x64: you have to use old drivers (for example, 352.xx) and miner built for cuda6.5.

GTX 970

The driver 352.84 did not work, still MH's 3.x.  I use 347.52 and it works except i can't run:
C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi" -acp UNRESTRICTED"
C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi" -ac 3505,1455
It works on 352.84... but MH's is 3....


Edit: 350.12 Works! http://www.nvidia.com/download/driverResults.aspx/83819/en-us

[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

 some help would be good  thanks in advance

[AlainC]

Been fiddling around with the -r 1 param, but I could not make it work.
...

did you put

#!/bin/sh

as first line?
Are you running as root... shutdown often need to be root (via sudo, but as server you cannot ask a password...).

To trace maybe you can add "-x'" to trace the script.

#!/bin/sh -x

add echo command before and after, in case problem is with shutdown itself...


I run something like

/sbin/shutdown -r 1
(restart in 1 minute)

check the path of shutdown with

whereis shutdown

It works well, and I even send email including a journalctl extract with ssmtp during the last minute.

[r79]

did you put

#!/bin/sh

as first line?

yes

Are you running as root... shutdown often need to be root (via sudo, but as server you cannot ask a password...).

I start claymore with an @reboot cron in a screen, so technically it should be running as root (the screen is in the "root"-screenlist).

To trace maybe you can add "-x'" to trace the script.

#!/bin/sh -x

add echo command before and after, in case problem is with shutdown itself...

Good idea, did not get to that when I fiddled around with it yesterday evening, gonna check that at home.

I run something like

/sbin/shutdown -r 1
(restart in 1 minute)

You put this command in a "restart.sh" file inside the claymore folder or into bin? I was lazy and just put a "restart" into my script, I'll check your way aswell (sounds wise giving the cards some time to cool before rebooting).

It works well, and I even send email including a journalctl extract with ssmtp during the last minute.

Holy damn, that sounds epic

[bayloth]

Hi there
I got problem
         ETH: Job timeout, disconnect, retry in 20 sec....
My worker:
      - 6x MSI rx 480 4g gaming x
      - windows 10 64bit
      - Claymore v 9.3
      - crimson v 15.12
      - firewall off
      - my .bat setting:
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 -epool eth-hk.dwarfpool.com:8008 -ewal XXXXXX.rig1 -mport 0 -mode 1 -eworker t1 -esm 1

Please help me. thanks!

[adly3000]

Hi there
I got problem
         ETH: Job timeout, disconnect, retry in 20 sec....
My worker:
      - 6x MSI rx 480 4g gaming x
      - windows 10 64bit
      - Claymore v 9.3
      - crimson v 15.12
      - firewall off
      - my .bat setting:
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 -epool eth-hk.dwarfpool.com:8008 -ewal XXXXXX.rig1 -mport 0 -mode 1 -eworker t1 -esm 1

Please help me. thanks!

Remove "-eworker t1" and try again it should be:
ethdcrminer64 -epool eth-hk.dwarfpool.com:8008 -ewal XXXXXX/rig1 -mport 0 -mode 1 -esm 1
otherwise try different pool. as dwarf sometimes fail to connect

[bayloth]

Hi there
I got problem
         ETH: Job timeout, disconnect, retry in 20 sec....
My worker:
      - 6x MSI rx 480 4g gaming x
      - windows 10 64bit
      - Claymore v 9.3
      - crimson v 15.12
      - firewall off
      - my .bat setting:
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 -epool eth-hk.dwarfpool.com:8008 -ewal XXXXXX.rig1 -mport 0 -mode 1 -eworker t1 -esm 1

Please help me. thanks!

Remove "-eworker t1" and try again it should be:
ethdcrminer64 -epool eth-hk.dwarfpool.com:8008 -ewal XXXXXX/rig1 -mport 0 -mode 1 -esm 1
otherwise try different pool. as dwarf sometimes fail to connect

Removed -ewoker t1 + change pool to asia1.ethermine.org:4444 but still got this problem (((http://imageshack.com/a/img923/3708/dfSgZu.jpg

[Yutard]

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

You can search the forum. It is quite easy.

[AzzAz]

Hi there
I got problem
         ETH: Job timeout, disconnect, retry in 20 sec....
My worker:
      - 6x MSI rx 480 4g gaming x
      - windows 10 64bit
      - Claymore v 9.3
      - crimson v 15.12
      - firewall off
      - my .bat setting:
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 -epool eth-hk.dwarfpool.com:8008 -ewal XXXXXX.rig1 -mport 0 -mode 1 -eworker t1 -esm 1

Please help me. thanks!

Remove "-eworker t1" and try again it should be:
ethdcrminer64 -epool eth-hk.dwarfpool.com:8008 -ewal XXXXXX/rig1 -mport 0 -mode 1 -esm 1
otherwise try different pool. as dwarf sometimes fail to connect

Removed -ewoker t1 + change pool to asia1.ethermine.org:4444 but still got this problem (((

15.12 and 480s! You want to be 1st to make it happen? Use any between 16.9.1 to 16.11.5

[ffthomas]

v9.3:
- improved dual mining speed stability in ASM mode.
- added "-altnum" option for alternative GPU indexing.
- a few minor bug fixes and improvements.

Oh bugger ... just spent the last hour updating all my rigs to 9.2 ... LOL  
Thanks Claymore, not complaining!

Soon I will add ability to update miners on all rigs with EthMan so it will be easy.

@claymore: WOW!! That will be a very useful feature, thanks!

[666mrga999]

I get 4-5% more effective speed (24h average) on pool side with 9.3 patch (ethermine).
From 89 MHps tp 94 MHps effective average speed.

Is this intended Claymore? Please confirm

tnx

[Teress]

Hi Claymore and Community.

I'm switched from 8.0 to 9.3 and noticed that time of share accepted increased 2-3 times. And totally effected pool average hashrate.
See below, (dual-mining or single mode result the same):

Version 8.0
ETH: Share accepted (62 ms)!

Version 9.3
ETH: Share accepted (156 ms)!
ETH: Share accepted (172 ms)!

So, seems this affect hashrate and I lost around 10% in 24 hours period.

Any suggestion are welcome, thanks in advance.

Yes, I have also on v9.3 increased share submit time, from 31 to 70 ms on v9.0 to 150 ms and more on v9.3. Thats a huge step back, because it causes less accepted shares and huge drop on accepted hashrate on pool.
So I'm back on v9.0

(RX470 4GBs, RX480 4 and 8GBs, nanopool)

Also lots of ETH: Job timeout, disconnect, retry in 20 sec....