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

[Xkeeper]

Hello

I have flashed the bios on my Sapphire Nitro+ RX570 4GB under Windows and I'm getting 30MH stable with Claymores.

But when I try same flashed card under Ubuntu I get only 21.2MH with Claymores

Any Idea what I might be missing?
I realy dont want to end up mining under windows.

I'm running Xubuntu 16.04
Kernel 4.10.0-28
amdgpu-pro beta mining driver 17.40.3.12
Claymores 10.6

[1715181624]

1715181624

[1715181624]

1715181624

[Ratledge]

So decred, sia and pascal already has asic's? What about pascal and coins on the same algo?

Those ASIC folks don't miss a beat: it would be rather silly of them to bake in support for any particular algo and not make it extensible.

Bottom line: if one algo fits multiple coins, it's likely going to be eat up by ASICs.

[hashestohashes]

So, somewhere in these 1k pages, is the answer I need probably, sadly  google searches failed me. Each time the miner has to reload the DAG file (dev fee as an example) the gpu's show less VRAM, and won't load the dag, causing the miner to crash.

I went -nofee to solve this, and obviously everyone loses here, but it's been running non stop since (long enough for it to fail if it was going to). Anyone have an obvious solution that's been stated 37 times in here and I failed to find it?

I am thinking a parameter or something would work (besides nofee). Linux, Smos rx580s

[Ratledge]

"Overclocking resistant" graphics cards?

I finally figured out exactly what the problem was with my shiny new Gigabyte GTX 1060 6GB "OC" card.

It's always a good idea not to have more than one overclocking tool installed, but I suppose that I didn't look closely enough at software downloads for the new replacement video card? Their website doesn't seem to differentiate between the VGA Tool (for overclocking) and their Aorus graphics card software which I thought was simply a support and required load, but it turns out that it is simply a different style overclocking tool.

Their basic (now v 1.25) version is a glitzy graphical tool with more bells and whistles, whereas the Aorus tool is more straightforward and easier to use - sort of. Your mileage will vary!

Anyway, apparently having both of them installed causes them to fight over which has control over the overclocking - and neither wins. Frankly they both pretty much lose bumping the opposite tool in the head.

Once I had removed both of them, I installed "nVidia Inspector", more or less a generic overclocking solution for nVidia cards sort of along the lines of CCC for the AMD cards.  I used the parameters that I knew worked well for this specific card, and now it is always mining at 18.7MHm/sec as opposed to the 14.8-MH/sec it ran out of the box.

Just a little tuning and ended up with 18.8MH/s every time. I should note that Claymore Miner seems to be a little temperamental if you adjust the GPU clock while it is running, so use the tool to create a shortcut to your preferred settings, and add it to your START.BAT file.

Now I will futz around and see if I can get back to 20+

[HFman]

Odd situation.

Have a rig with 3 x RX570 4GB.  Was getting 27Mh/s with Claymore 10.6.

Had to change rig to different board and hard drive.  Board is the same, hard drive is slightly different (slower, but didn't think this mattered).
Same amount or RAM *GB, same pagefile, 16GB, same divers, same version of windows but now only getting 20Mh/s.

ANy ideas?  Really frustrated.

Drivers version is the latest, 18.2 blockchain from amd site.
Bios is modded the same
"UberMix v3.1

777000000000000022CC1C00AD615C41C0590E152ECC8608006007000B031420FA8900A00300000 010122F3FBA354"

Card info:

Radeon Software Version - 18.2.1
Radeon Software Edition - Adrenalin
Graphics Chipset - Radeon RX 570 Series
Memory Size - 4096 MB
Memory Type - GDDR5
Core Clock - 1244 MHz
Windows Version - Windows 10 (64 bit)
System Memory - 8 GB
CPU Type - Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz

Radeon Settings Version - 2018.0131.1849.33856
Driver Packaging Version - 17.50.17.03-180131a-323782E-RadeonSoftwareAdrenalin
Provider - Advanced Micro Devices, Inc.
2D Driver Version - 8.1.1.1634
Direct3D® Version - 9.14.10.01316
OpenGL® Version - 6.14.10.13506
OpenCL™ Version - 23.20.15017.3010
AMD Audio Driver Version - 10.0.1.6
Vulkan™ Driver Version - 2.0.1
Vulkan™ API Version - 1.0.65

Graphics Card Manufacturer - Powered by AMD
Graphics Chipset - Radeon RX 570 Series
Device ID - 67DF
Vendor ID - 1002
SubSystem ID - 22F7
SubSystem Vendor ID - 1458
Revision ID - EF
Bus Type - PCI Express 3.0
Current Bus Settings - Not Available
BIOS Version - 015.050.002.001
BIOS Part Number - xxx-xxx-xxx
BIOS Date - 2017/05/18 08:21
Memory Size - 4096 MB
Memory Type - GDDR5
Memory Clock - 1750 MHz
Core Clock - 1244 MHz
Total Memory Bandwidth - 224 GByte/s
Memory Bit Rate - 7.00 Gbps
2D Driver File Path - /REGISTRY/MACHINE/SYSTEM/ControlSet001/Control/Class/{4d36e968-e325-11ce-bfc1-08002be10318}/0005

TIA

Sounds like you need still to change from graphics to compute :

https://i0.wp.com/mining.help/wp-content/uploads/2018/01/ethereum_mining_windows_amd_settings_gpu_workload.jpg?w=1050&ssl=1

What memory does your card have ? your hashrate is still quite low...

[achalmersman]

So my AMD rig updated to the latest Windows build and screwed my drivers up.  Downloaded the latest AMD drivers (18.2.1) and MSI Afterburner 4.4.0 and Claymore 10.6.  I cannot get afterburner to recognize the cards / control the cards at all.  Is Afterburner not yet compatible with the latest drivers?  Didn't find anything via google searches

[Vann]

If you want to use the compute drivers, Afterburner will not work with the AMD Adrenaline drivers and multiple cards. Either use the Claymore config file to apply the overclock and undervolt settings at runtime, or use OverdriveNtool to create overclocking profiles for your cards as explained on www.mining.help.

If you want to use Afterburner with multiple cards you need to use the AMD blockchain drivers and you are limited to 8 AMD cards. You still need to use the pixel patcher with RX 470/480 and 570 cards after installing the driver.

Since you don't want Windows updating your drivers, I would disable drivers updates in Windows Update.

gpedit ==> Computer Configuration ==> Administrative Templates ==> Windows Components ==> Windows Update and set 'Do not include drivers with Windows Update' to enabled.

[Ursul0]

"Overclocking resistant" graphics cards?

I finally figured out exactly what the problem was with my shiny new Gigabyte GTX 1060 6GB "OC" card.

It's always a good idea not to have more than one overclocking tool installed, but I suppose that I didn't look closely enough at software downloads for the new replacement video card? Their website doesn't seem to differentiate between the VGA Tool (for overclocking) and their Aorus graphics card software which I thought was simply a support and required load, but it turns out that it is simply a different style overclocking tool.

Their basic (now v 1.25) version is a glitzy graphical tool with more bells and whistles, whereas the Aorus tool is more straightforward and easier to use - sort of. Your mileage will vary!

Anyway, apparently having both of them installed causes them to fight over which has control over the overclocking - and neither wins. Frankly they both pretty much lose bumping the opposite tool in the head.

Once I had removed both of them, I installed "nVidia Inspector", more or less a generic overclocking solution for nVidia cards sort of along the lines of CCC for the AMD cards.  I used the parameters that I knew worked well for this specific card, and now it is always mining at 18.7MHm/sec as opposed to the 14.8-MH/sec it ran out of the box.

Just a little tuning and ended up with 18.8MH/s every time. I should note that Claymore Miner seems to be a little temperamental if you adjust the GPU clock while it is running, so use the tool to create a shortcut to your preferred settings, and add it to your START.BAT file.

Now I will futz around and see if I can get back to 20+

I'm not entirely sure what's the meaning of your post, but 1060 should be stable at about 23-24MH with mem oc to +800-900

[gglala]

@claymore any advice on the below error?

Dear all, need your advice on my new rig. I constantly get the following error message and the miner restarts itself, which is a good thing instead of just hanging and sit idle. This happens as short as 2 hours or up to 5 hours. Tried searching around but yet to find any solutions. Thanks.

quote
21:09:47:912   16b8   ETH: checking pool connection...
21:09:47:991   16b8   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:09:48:288   16b8   got 243 bytes
21:09:48:397   16b8   buf: {"jsonrpc":"2.0","id":0,"result":["0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

21:09:48:491   16b8   parse packet: 242
21:09:48:569   16b8   ETH: job is the same
21:09:48:662   16b8   new buf size: 0
21:09:51:397   18b8   ETH: put share nonce 31272c01dbf3959
21:09:51:491   9b0   GPU 3, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:569   1b34   GPU 0, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:663   2a8   GPU 6, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:757   d18   GPU 4, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:835   226c   GPU 5, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:491   18b8   ETH round found 1 shares
21:09:52:007   16b8   ETH: 02/05/18-21:09:51 - SHARE FOUND - (GPU 5)
21:09:52:085   16b8   send: {"id":15,"method":"eth_submitWork","params":["0x031272c01dbf3959","0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb1c8e687425ef63e31ab56f46f302ed8f5c949eba43483f0f118681f19b06c97"]}

21:09:52:178   2d10   GPU 1, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:52:272   1e5c   GPU 7, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:52:350   9b0   GPU 3, GpuMiner kx failed 1
21:09:52:429   1b34   GPU 0, GpuMiner kx failed 1
21:09:52:522   2a8   GPU 6, GpuMiner kx failed 1
21:09:52:600   d18   GPU 4, GpuMiner kx failed 1
21:09:52:694   226c   GPU 5, GpuMiner kx failed 1
21:09:52:772   16bc   GPU 2, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:52:866   2d10   GPU 1, GpuMiner kx failed 1
21:09:52:944   1e5c   GPU 7, GpuMiner kx failed 1
21:09:52:397   16b8   got 40 bytes
21:09:53:116   16b8   buf: {"jsonrpc":"2.0","id":15,"result":true}

21:09:53:194   16b8   parse packet: 39
21:09:53:272   16b8   ETH: Share accepted (1094 ms)!

21:09:53:366   16b8   new buf size: 0
21:09:52:772   226c   Set global fail flag, failed GPU5
21:09:53:522   16bc   GPU 2, GpuMiner kx failed 1
21:09:52:944   2d10   Set global fail flag, failed GPU1
21:09:53:022   1e5c   Set global fail flag, failed GPU7
21:09:52:429   9b0   Set global fail flag, failed GPU3
21:09:52:522   1b34   Set global fail flag, failed GPU0
21:09:52:600   2a8   Set global fail flag, failed GPU6
21:09:52:694   d18   Set global fail flag, failed GPU4
21:09:54:116   18b8   GPU 5, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:194   226c   GPU 5 failed
21:09:53:616   16bc   Set global fail flag, failed GPU2
21:09:54:366   1984   GPU 1, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:460   2d10   GPU 1 failed
21:09:54:538   2a7c   GPU 7, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:616   1e5c   GPU 7 failed
21:09:54:710   20cc   GPU 3, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:788   9b0   GPU 3 failed
21:09:54:882   208   GPU 0, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:960   1b34   GPU 0 failed
21:09:55:038   28b8   GPU 6, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:55:132   2a8   GPU 6 failed
21:09:55:210   2cb0   GPU 4, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:55:288   d18   GPU 4 failed
21:09:55:382   18b8   GPU 5, GpuMiner kx failed 1
21:09:55:460   2b90   GPU 2, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:55:538   16bc   GPU 2 failed
21:09:55:632   1984   GPU 1, GpuMiner kx failed 1
21:09:55:710   2a7c   GPU 7, GpuMiner kx failed 1
21:09:55:804   20cc   GPU 3, GpuMiner kx failed 1
21:09:55:882   208   GPU 0, GpuMiner kx failed 1
21:09:55:976   28b8   GPU 6, GpuMiner kx failed 1
21:09:56:054   2cb0   GPU 4, GpuMiner kx failed 1
21:09:55:460   18b8   Set global fail flag, failed GPU5
21:09:56:226   2b90   GPU 2, GpuMiner kx failed 1
21:09:55:710   1984   Set global fail flag, failed GPU1
21:09:55:804   2a7c   Set global fail flag, failed GPU7
21:09:55:882   20cc   Set global fail flag, failed GPU3
21:09:55:976   208   Set global fail flag, failed GPU0
21:09:56:054   28b8   Set global fail flag, failed GPU6
21:09:56:132   2cb0   Set global fail flag, failed GPU4
21:09:56:820   18b8   GPU 5 failed
21:09:56:304   2b90   Set global fail flag, failed GPU2
21:09:56:991   1984   GPU 1 failed
21:09:57:070   2a7c   GPU 7 failed
21:09:57:148   20cc   GPU 3 failed
21:09:57:242   208   GPU 0 failed
21:09:57:320   28b8   GPU 6 failed
21:09:57:398   2cb0   GPU 4 failed
21:09:57:492   2b90   GPU 2 failed
21:09:57:085   4fc   srv_thr cnt: 1, IP: 127.0.0.1
21:09:57:648   4fc   recv: 60
21:09:57:742   4fc   srv pck: 59
21:09:57:835   4fc   srv bs: 0
21:09:57:913   4fc   sent: 241
21:09:57:929   16b8   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x00000000000000000000000000000000000000000000000000000000d2e3fbe7"]}

21:09:58:085   1dcc   GPU0 t=51C fan=75%, GPU1 t=57C fan=75%, GPU2 t=56C fan=75%, GPU3 t=57C fan=74%, GPU4 t=52C fan=74%, GPU5 t=54C fan=75%, GPU6 t=57C fan=74%, GPU7 t=52C fan=74%
21:09:58:101   16b8   ETH: checking pool connection...
21:09:58:257   16b8   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:09:58:539   16b8   got 243 bytes
21:09:58:617   16b8   buf: {"jsonrpc":"2.0","id":0,"result":["0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

21:09:58:695   16b8   parse packet: 242
21:09:58:789   16b8   ETH: job is the same
21:09:58:867   16b8   new buf size: 0
21:10:08:352   16b8   ETH: checking pool connection...
21:10:08:430   16b8   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:10:08:727   16b8   got 243 bytes
21:10:08:805   16b8   buf: {"jsonrpc":"2.0","id":0,"result":["0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

21:10:08:883   16b8   parse packet: 242
21:10:08:977   16b8   ETH: job is the same
21:10:09:055   16b8   new buf size: 0
21:10:09:102   ae0   got 484 bytes
21:10:09:227   ae0   buf: {"method":"mining.notify","params":["7d5","0000000000000000000000000000000000000000000000000000000000000000","32AF0200CA02200042B6D71C8BDD83EB6DAB79713BCFCFF330C4AB5BA2BB7B7C02A30882B54E31E 62000CA1FF7B7804CE8BC3AFA0C5A7F7F72E372C30A3A3FFAC81563C67672781D2DFD40420F0000 00000002000200E02B0736","0FC510114C3C9EC4B844C4DFF39C4A2018F413126F58AF73F62D818C467355B7E3B0C44298FC1C1 49AFBF4C8996FB92427AE41E4649B934CA495991B7852B85500000000",[],"00000000","24000000","5a7857b0",true],"id":null}

21:10:09:305   ae0   parse packet: 483
21:10:09:383   ae0   new buf size: 0
21:10:09:477   ae0    PASC: 02/05/18-21:10:09 - New job from pasc-asia1.nanopool.org:15555
21:10:09:555   ae0   target: 0x000000000ffff000 (diff: 68GH)
21:10:10:540   52c   em hbt: 16, dm hbt: 16, fm hbt: 78,
21:10:10:618   52c   watchdog - thread 0 (gpu0), hb time 19266
21:10:10:696   52c   watchdog - thread 1 (gpu0), hb time 19234
21:10:10:790   52c   watchdog - thread 2 (gpu1), hb time 19328
21:10:10:868   52c   watchdog - thread 3 (gpu1), hb time 19516
21:10:10:962   52c   watchdog - thread 4 (gpu2), hb time 19594
21:10:11:040   52c   watchdog - thread 5 (gpu2), hb time 19578
21:10:11:118   52c   watchdog - thread 6 (gpu3), hb time 19750
21:10:11:212   52c   watchdog - thread 7 (gpu3), hb time 19938
21:10:11:290   52c   watchdog - thread 8 (gpu4), hb time 19953
21:10:11:368   52c   watchdog - thread 9 (gpu4), hb time 19938
21:10:11:446   52c   watchdog - thread 10 (gpu5), hb time 20125
21:10:11:540   52c   watchdog - thread 11 (gpu5), hb time 19532
21:10:11:618   52c   watchdog - thread 12 (gpu6), hb time 20188
21:10:11:712   52c   watchdog - thread 13 (gpu6), hb time 20375
21:10:11:790   52c   watchdog - thread 14 (gpu7), hb time 20328
21:10:11:884   52c   watchdog - thread 15 (gpu7), hb time 20531
21:10:11:962   52c   WATCHDOG: GPU error, you need to restart miner
21:10:15:056   52c   Restarting OK, exit...
unquote

[dollos]

the above is because you have overclocked too much. startthe mem overclock at 100mhz run for a few days and see if this occurs and beleive me this will not happen . you need to find that one card that is moaning...

[LucianoBM]

So my AMD rig updated to the latest Windows build and screwed my drivers up.  Downloaded the latest AMD drivers (18.2.1) and MSI Afterburner 4.4.0 and Claymore 10.6.  I cannot get afterburner to recognize the cards / control the cards at all.  Is Afterburner not yet compatible with the latest drivers?  Didn't find anything via google searches

I have the same configuration except for MSI Afterburner 4.4.2 and the same problem.

Afterburner recognize the cards and control the temperature and fan but don't control core clock and memory clock when claymore is already opened.
I found out that I can disable mining without closing claymore by just pressing the number of gpu (to disable gpu#0, press 0)
After disabling (waiting 1 min) and enabling, my settings on MSI Afterburner are applied to the cards and I can increase hashrate.

But on another rig with 1 RX 570 and 1 GTX 1070, when I change something on MSI Afterburner, it changes the hashrate immediately on claymore.

[osfera69]

Hi,

I'm new with Claymore. I have just set up a RX460 4 GB OC and configure it to work with Dwarfpool. Claymore detects the Graphic card and connects to the pool correctly. However, after a few seconds (in some cases a little more) I got the following message: job timeout disconnect retry in 20 seconds.

Any idea how to solve it?

[Teress]

Why are colors in console when mining with NVidida GPUs so dimmed and washed out? Mining with AMDs have much brighter and better readable colors.

[MrDeity]

Hi,

I'm new with Claymore. I have just set up a RX460 4 GB OC and configure it to work with Dwarfpool. Claymore detects the Graphic card and connects to the pool correctly. However, after a few seconds (in some cases a little more) I got the following message: job timeout disconnect retry in 20 seconds.

Any idea how to solve it?

The reply I gave on page 979 of this thread is what I used to solve this issue. 

[AlainC]

@Claymore
"WattMan Support Coming For Radeon Polaris GPUs On Linux"
https://www.phoronix.com/scan.php?page=news_item&px=Auto-WattMan-Polaris
"Back in 2016 AMD introduced WattMan to their Radeon Software driver to allow for fine-tuning of GPU voltage, engine clocks, memory clocks and more. An incarnation of that is now approaching their open-source Linux driver. "

Not for now

[whoismoses]

So my AMD rig updated to the latest Windows build and screwed my drivers up.  Downloaded the latest AMD drivers (18.2.1) and MSI Afterburner 4.4.0 and Claymore 10.6.  I cannot get afterburner to recognize the cards / control the cards at all.  Is Afterburner not yet compatible with the latest drivers?  Didn't find anything via google searches

Overdrive no longer works with the latest AMD drivers. Use OverdriveNtool.

https://forums.guru3d.com/threads/overdriventool-tool-for-amd-gpus.416116/

[Rickirs]

Why are colors in console when mining with NVidida GPUs so dimmed and washed out? Mining with AMDs have much brighter and better readable colors.

Try -colors feature:

-colors enables or disables colored text in console. Default value is "1", use "-colors 0" to disable coloring. Use 2...4 values to remove some of colors.

[jackbox]

So my AMD rig updated to the latest Windows build and screwed my drivers up.  Downloaded the latest AMD drivers (18.2.1) and MSI Afterburner 4.4.0 and Claymore 10.6.  I cannot get afterburner to recognize the cards / control the cards at all.  Is Afterburner not yet compatible with the latest drivers?  Didn't find anything via google searches

Overdrive no longer works with the latest AMD drivers. Use OverdriveNtool.

https://forums.guru3d.com/threads/overdriventool-tool-for-amd-gpus.416116/

Sapphire TRIXX works but every time the rig reboots you have to manually reapply the settings. It is not resetting them at boot like it is supposed to do. Semi functional but better than Afterburner's non-functional status.

[Teress]

Why are colors in console when mining with NVidida GPUs so dimmed and washed out? Mining with AMDs have much brighter and better readable colors.

Try -colors feature:

-colors enables or disables colored text in console. Default value is "1", use "-colors 0" to disable coloring. Use 2...4 values to remove some of colors.

-colors just reduces ammount of colors used. I am talking about the deafult behavior of miner.

[dragonmike]

The suspense is killing me !  At the same time, I dont wish to upgrade all my rigs again... but progress is progress and we need more profits

Betcha Neoscrypt will be in there. This means it'll just rape profitability for all those new shitcoins out there you could extract an extra buck or two of. Oh well.

EDIT: or maybe not