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

[nc50lc]

Claymore may be placing both ETH and ETC DAG to each of your Cards.

No that is not what the -allcoins 1 command does. What it means is that during every single dev mining session you will need to load new DAG to mine for Claymore and after the dev miner is done, it will reload the older DAGs to continue your regular mining.

Isn't that for: -allcoins -1 not for -allcoins 1? TIA

It didn't worked anyways, so the issue is somewhere else.

[1714234895]

1714234895

[1714234895]

1714234895

[1714234895]

1714234895

[adaseb]

Claymore may be placing both ETH and ETC DAG to each of your Cards.

No that is not what the -allcoins 1 command does. What it means is that during every single dev mining session you will need to load new DAG to mine for Claymore and after the dev miner is done, it will reload the older DAGs to continue your regular mining.

Isn't that for: -allcoins -1 not for -allcoins 1? TIA

It didn't worked anyways, so the issue is somewhere else.

I think what the above poster should try is to increase the virtual memory, only issue I can think of that causes this since all his gpus are 8GB. Phoenix works but maybe it allocates a slightly different amount of virtual memory and hence might not run into this issue.

Regarding "allcoins" command, I used it many times in the past.

Basically the issue is that if you mine some new altcoin with a Epoch of 10 and later switch to an Epoch of 300 for ETH, it will sometimes crash when it tries to switch to Epoch 300, so thats why there is the -allcoins -1 which mines dev fee first so loads Epoch 300 and later Epoch 10, this resolves some crashes however the issue is the constant writing of the DAG on the GPUs every 15 minutes, eventually one or more GPUs will crash.

This is why the only way to mine alts with Claymore was with the -devfree 0 at a reduced speed. It mined slower and not optimized but at least it never crashed because it never switched to dev fee mode.

[nurilham]

What should I do?
I tried mining using 4 gpu 1050ti 4gb, but I found that there was mine, there was an explanation of 0 mh/s and another 15mh/s.

Does anyone have a solution?
please helpme

[cdog]

What should I do?
I tried mining using 4 gpu 1050ti 4gb, but I found that there was mine, there was an explanation of 0 mh/s and another 15mh/s.

Does anyone have a solution?
please helpme

I think there is something wrong in the VGA bios or take a look in the device manager, does the VGA driver have an exclamation mark (!)?
If the VGA driver shows a (!) Sign then I suggest restarting your mining rig

[alexkidd360]

Hello Everyone   
first post!!

i am running 2 rigs, all cards are RX 580 8g armors, Windows 10 with claymore v15, both rigs stopped working when the ETC epoch hit #379
All GPU's  "not enough GPU memory to place DAG, you cannot mine this coin with this GPU"
"OpenCL error -61 - cannot allocate big buffer for DAG"
"OpenCl error -38 - cannot write buffer for DAG"
server: accept failed with error: 10004

my virtual mem is at 55000
AMD Drivers 19.9.2
im using AMD software for tuning GPU's "GPU 1165MHz, 853mV" "Memory 2080MHz, 853mV"

Now when i update drivers to either latest 20.9.2 or drivers back to near beginning of the year i can mine again but now the hashrate is 19.2
Without tuning gpus i get 22.4 hash

Before #379 my hashrate was 31.3

In my bat file i have "-eres 0 -epsw x -mode 1 -r 1 -strap 1 -rxboost 1"

looking forward to solution
thanks

[thatBeardoGuy]

Hello Guys, I have a 8x RX580 8GB Rig stable for last 2 months but from last 3 days it's having "cannot write buffer for DAG" issue.
I'm using nicehash, It is also happening on Betterhash, and I even tried using Claymore standalone mining on a demo address, it still gives " cannot write buffer for DAG ".

I've experimented a lot and observed that as soon as the eth epoch #379 starts to load up, the DAG size becomes 3.96GB and the DAG error comes up, But if it's still working on epoch #368 (size 3.78GB) then it keeps working fine.

I have tested on Windows 10 Build 2004 and also on Windows 10 build 1708 (just to make sure it's not windows update related) and have also tried 6 different Radeon Drivers ranging from Dec 2019 to Sep 2020 but all are having the same issue. On the Phoenix, it seems to work fine and Team Red Miner also works fine.
I have my Virtual memory set to 250GB (yes TwoHundredFifty GB) and I have upgraded my 4GB to 8GB system RAM and it still gives the same error. I've tried using the Gen 3 link speed on the PCI-E bus, the same error. This issue is only in Claymore, seems to me that somehow the claymore is unable to access more than 4GB of VRAM on 8GB RX580 cards. Please, if anyone found a working solution, post it here. Thanks for reading all of it.

[bategojko74]

Hello Guys, I have a 8x RX580 8GB Rig stable for last 2 months but from last 3 days it's having "cannot write buffer for DAG" issue.
I'm using nicehash, It is also happening on Betterhash, and I even tried using Claymore standalone mining on a demo address, it still gives " cannot write buffer for DAG ".

I've experimented a lot and observed that as soon as the eth epoch #379 starts to load up, the DAG size becomes 3.96GB and the DAG error comes up, But if it's still working on epoch #368 (size 3.78GB) then it keeps working fine.

I have tested on Windows 10 Build 2004 and also on Windows 10 build 1708 (just to make sure it's not windows update related) and have also tried 6 different Radeon Drivers ranging from Dec 2019 to Sep 2020 but all are having the same issue. On the Phoenix, it seems to work fine and Team Red Miner also works fine.
I have my Virtual memory set to 250GB (yes TwoHundredFifty GB) and I have upgraded my 4GB to 8GB system RAM and it still gives the same error. I've tried using the Gen 3 link speed on the PCI-E bus, the same error. This issue is only in Claymore, seems to me that somehow the claymore is unable to access more than 4GB of VRAM on 8GB RX580 cards. Please, if anyone found a working solution, post it here. Thanks for reading all of it.

Update the drivers to the newest ones.

[thatBeardoGuy]

Update the drivers to the newest ones.

I've already mentioned that I tried all the drivers from last year upto the latest one sep 2020 release. Same Isuue.

[bambam99]

My vegas started to quit mining... I switched to another mining software.

[batsonxl]

No idea whats going on but im getting this errors with 8gb cards virtual memory set to 150gb. Any help appreciated. thanks



02:21:05:510   162c   AMD Cards available: 7
02:21:05:510   162c   GPU #0: Ellesmere (Radeon (TM) RX 480 Graphics), 8192 MB available, 36 compute units (pci bus 3:0:0)
02:21:05:511   162c   gpu 0 max alloc size is 4048 MB
02:21:05:511   162c   GPU #0 recognized as Radeon RX 480/580
02:21:05:512   162c   GPU #1: Ellesmere (Radeon (TM) RX 480 Graphics), 8192 MB available, 36 compute units (pci bus 9:0:0)
02:21:05:512   162c   gpu 1 max alloc size is 4048 MB
02:21:05:512   162c   GPU #1 recognized as Radeon RX 480/580
02:21:05:513   162c   GPU #2: Ellesmere (Radeon RX 570 Series), 8192 MB available, 32 compute units (pci bus 10:0:0)
02:21:05:513   162c   gpu 2 max alloc size is 4048 MB
02:21:05:515   162c   GPU #2 recognized as Radeon RX 470/570
02:21:05:515   162c   GPU #3: Ellesmere (Radeon (TM) RX 480 Graphics), 8192 MB available, 36 compute units (pci bus 11:0:0)
02:21:05:516   162c   gpu 3 max alloc size is 4048 MB
02:21:05:516   162c   GPU #3 recognized as Radeon RX 480/580
02:21:05:517   162c   GPU #4: Ellesmere (Radeon (TM) RX 480 Graphics), 8192 MB available, 36 compute units (pci bus 12:0:0)
02:21:05:517   162c   gpu 4 max alloc size is 4048 MB
02:21:05:518   162c   GPU #4 recognized as Radeon RX 480/580
02:21:05:518   162c   GPU #5: Ellesmere (Radeon (TM) RX 480 Graphics), 8192 MB available, 36 compute units (pci bus 13:0:0)
02:21:05:519   162c   gpu 5 max alloc size is 4048 MB
02:21:05:519   162c   GPU #5 recognized as Radeon RX 480/580
02:21:05:520   162c   GPU #6: Ellesmere (Radeon (TM) RX 480 Graphics), 8192 MB available, 36 compute units (pci bus 14:0:0)
02:21:05:520   162c   gpu 6 max alloc size is 4048 MB
02:21:05:521   162c   GPU #6 recognized as Radeon RX 480/580
02:21:05:521   162c   POOL/SOLO version
02:21:05:521   162c   Platform: Windows
02:21:05:644   162c   start building OpenCL program for GPU 0...
02:21:06:000   162c   done
02:21:06:205   162c   start building OpenCL program for GPU 1...
02:21:06:546   162c   done
02:21:06:751   162c   start building OpenCL program for GPU 2...
02:21:07:089   162c   done
02:21:07:293   162c   start building OpenCL program for GPU 3...
02:21:07:631   162c   done
02:21:07:836   162c   start building OpenCL program for GPU 4...
02:21:08:180   162c   done
02:21:08:385   162c   start building OpenCL program for GPU 5...
02:21:08:724   162c   done
02:21:08:930   162c   start building OpenCL program for GPU 6...
02:21:09:266   162c   done
02:21:09:514   162c   GPU #0: algorithm ASM 1
02:21:09:586   162c   GPU #1: algorithm ASM 1
02:21:09:672   162c   GPU #2: algorithm ASM 1
02:21:09:724   162c   GPU #3: algorithm ASM 1
02:21:09:787   162c   GPU #4: algorithm ASM 1
02:21:09:850   162c   GPU #5: algorithm ASM 1
02:21:09:908   162c   GPU #6: algorithm ASM 1
02:21:09:909   162c   cudaGetDeviceCount failed (35, CUDA driver version is insufficient for CUDA runtime version), probably no CUDA devices
02:21:09:909   162c   No NVIDIA CUDA GPUs detected.
02:21:09:910   162c   Total cards: 7
02:21:09:910   162c   No NVIDIA cards in the list, NVML library will not be used.
02:21:09:912   162c   Driver version: 0x802
02:21:09:996   162c   driver init ok
02:21:10:147   162c   GPU# 0 strap "POL8S1" is applied successfully, mclock 2060MHz
02:21:10:149   162c   GPU# 0 -rxboost option is applied successfully
02:21:10:310   162c   GPU# 1 strap "POL8S1" is applied successfully, mclock 2060MHz
02:21:10:311   162c   GPU# 1 -rxboost option is applied successfully
02:21:10:460   162c   GPU# 2 strap "POL8H1" is applied successfully, mclock 2010MHz
02:21:10:462   162c   GPU# 2 -rxboost option is applied successfully
02:21:10:616   162c   GPU# 3 strap "POL8S1" is applied successfully, mclock 2060MHz
02:21:10:617   162c   GPU# 3 -rxboost option is applied successfully
02:21:10:780   162c   GPU# 4 strap "POL8S1" is applied successfully, mclock 2060MHz
02:21:10:781   162c   GPU# 4 -rxboost option is applied successfully
02:21:10:928   162c   GPU# 5 strap "POL8S1" is applied successfully, mclock 2060MHz
02:21:10:930   162c   GPU# 5 -rxboost option is applied successfully
02:21:11:083   162c   GPU# 6 strap "POL8S1" is applied successfully, mclock 2060MHz
02:21:11:084   162c   GPU# 6 -rxboost option is applied successfully
02:21:12:240   162c   SSL: Imported 36 certificates from local storage
02:21:12:251   9a4   ETH: Stratum - connecting to 'daggerhashimoto.usa.nicehash.com' <172.65.223.147> port 3353 (unsecure)
02:21:12:278   9a4   sent: {"id": 1, "method": "mining.subscribe", "params": ["MinerName/1.0.0", "EthereumStratum/1.0.0"]}

02:21:12:278   9a4   sent: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}

02:21:12:278   9a4   sent: {"id": 2, "method": "mining.authorize", "params": ["3KPDtEhehBkrgKbXhTx4pZ86n8hgbNyy4E","x"]}

02:21:12:278   9a4   ETH: Stratum - Connected (daggerhashimoto.usa.nicehash.com:3353) (unsecure)
02:21:12:341   162c   No pool specified for Decred! Ethereum-only mining mode is enabled

02:21:12:344   162c   ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)

02:21:12:344   162c   ETH: nicehash stratum mode
02:21:12:345   162c   "-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
02:21:12:346   162c   Watchdog enabled
02:21:12:346   162c   Remote management (READ-ONLY MODE) is enabled on port 3333
02:21:12:347   162c   

02:21:12:348   162c   You did not specify -dcri values directly, so they will be detected automatically
02:21:12:348   162c   Automatic detection of best -dcri values started, please wait...

02:21:12:664   9a4   buf: {"id":1,"error":null,"result":[["mining.notify","79883f017b100ce104f9fc453eee3533","EthereumStratum/1.0.0"],"22edd5"]}
{"id":5,"result":true,"error":null}

02:21:12:664   9a4   remove first packet 36
02:21:12:675   9a4   buf: {"id":2,"result":true,"error":null}
{"id":null,"method":"mining.set_difficulty","params":[0.620119]}
{"id":null,"method":"mining.notify","params":["00000000666f4640","24a739dd7e88652c7b9c8b21ab1ea88a6a1bc824232e6ffb030387c1518290d7","d20ac47b7f2027c2fe70db241e1ee19c3ba0f375ef832e4912b8b8de5e6b62cb",true]}

02:21:12:675   9a4   ETH: Authorized
02:21:12:676   9a4   remove first packet 271
02:21:12:676   9a4   remove first packet 206
02:21:12:737   14ac   Setting DAG epoch #379(3.96GB)...
02:21:13:222   9a4   buf: {"id":null,"method":"mining.notify","params":["00000000666f5292","24a739dd7e88652c7b9c8b21ab1ea88a6a1bc824232e6ffb030387c1518290d7","c31863e1dedd417f1bbca5c7b2d82768e8ba2252c80211d4e054db567e06fb74",true]}

02:21:13:223   9a4   ETH: 10/13/20-02:21:13 - New job from daggerhashimoto.usa.nicehash.com:3353
02:21:13:223   9a4   target: 0x000000019cd15433 (diff: 2663MH), epoch 379(3.96GB)
02:21:13:224   9a4   ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
02:21:13:224   9a4   ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s, GPU6 0.000 Mh/s
02:21:16:607   9a4   buf: {"id":null,"method":"mining.notify","params":["00000000666ff49e","24a739dd7e88652c7b9c8b21ab1ea88a6a1bc824232e6ffb030387c1518290d7","1e1651e46eeb8d1c85523cff24837a6b0683566d6db1d0d5ad80519c4bec74d3",true]}

02:21:16:608   9a4   ETH: 10/13/20-02:21:16 - New job from daggerhashimoto.usa.nicehash.com:3353
02:21:16:608   9a4   target: 0x000000019cd15433 (diff: 2663MH), epoch 379(3.96GB)
02:21:16:609   9a4   ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
02:21:16:609   9a4   ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s, GPU6 0.000 Mh/s
02:21:17:079   aac   Setting DAG epoch #379 for GPU0
02:21:17:080   fd0   Setting DAG epoch #379 for GPU5
02:21:17:081   b84   Setting DAG epoch #379 for GPU3
02:21:17:075   ec4   Setting DAG epoch #379 for GPU2
02:21:17:080   aac   Create GPU buffer for GPU0
02:21:17:082   6a0   Setting DAG epoch #379 for GPU4
02:21:17:083   14ac   Setting DAG epoch #379 for GPU1
02:21:17:083   388   Setting DAG epoch #379 for GPU6
02:21:17:084   aac   GPU0 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
02:21:17:085   fd0   Create GPU buffer for GPU5
02:21:17:086   b84   Create GPU buffer for GPU3
02:21:17:082   ec4   Create GPU buffer for GPU2
02:21:17:087   ec4   GPU2 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
02:21:17:087   aac   GPU0 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

02:21:17:088   6a0   Create GPU buffer for GPU4
02:21:17:088   14ac   Create GPU buffer for GPU1
02:21:17:089   388   Create GPU buffer for GPU6
02:21:17:089   fd0   GPU5 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
02:21:17:090   6a0   GPU4 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
02:21:17:090   b84   GPU3 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
02:21:17:091   14ac   GPU1 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
02:21:17:091   ec4   GPU2 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

[bategojko74]

Update the drivers to the newest ones.

I've already mentioned that I tried all the drivers from last year upto the latest one sep 2020 release. Same Isuue.

Uninstall Claymore driver that is used for straps and rxboost perform DDU and install the newest drivers.

[netserver]

Update the drivers to the newest ones.

I've already mentioned that I tried all the drivers from last year upto the latest one sep 2020 release. Same Isuue.

Uninstall Claymore driver that is used for straps and rxboost perform DDU and install the newest drivers.

same issue in windows/linux using nicehash every 1-5h crash.  i move to phoenix and work ok in windows/linux.   

maybe claymore can say something or no...   

[thatBeardoGuy]

Update the drivers to the newest ones.

I've already mentioned that I tried all the drivers from last year upto the latest one sep 2020 release. Same Isuue.

Uninstall Claymore driver that is used for straps and rxboost perform DDU and install the newest drivers.

https://i.ibb.co/CVsGQwB/Capturenice.jpg
See the above screenshot, even the Nicehash disabled the Claymore due to the DAG issue with epoch more than 379. It's a confirmed issue with Claymore. So unless the developer updated it, claymore miner is dead for ETH.

[apolousm]

I've counted 34 collaborators/meritors for the miner (take a look at the header of this thread). None of them has contacted Claymore to let him know about the problems the miner is having? If there's not a fix for the recent issues, this miner is dead. It's very sad, this is one of the best and easiest programs to use for mining.

[john1010]

I found the solution. I  remove old devices and drivers  (intel, microsoft) in device manager -  display adaptors ! Now its OK!

Well that's good for you, in my case after uninstalling that driver in device manager and restart, the driver automatically reinstalled again, so there is no use of that method because windows has the cache of every driver we installed, unless we delete it using DDU.

[batsonxl]

Looks like it is time say goodbye to Claymore. Thanks for many years for miner. i moved to phoenixminer works good but cant get hashrates like in claymoe, i will appreciate if someon can share AMD mem tweaks for RX470/480/570/580, Thanks everybody

[botanik]

Hello Everyone   
first post!!

i am running 2 rigs, all cards are RX 580 8g armors, Windows 10 with claymore v15, both rigs stopped working when the ETC epoch hit #379
All GPU's  "not enough GPU memory to place DAG, you cannot mine this coin with this GPU"
"OpenCL error -61 - cannot allocate big buffer for DAG"
"OpenCl error -38 - cannot write buffer for DAG"
server: accept failed with error: 10004

my virtual mem is at 55000
AMD Drivers 19.9.2
im using AMD software for tuning GPU's "GPU 1165MHz, 853mV" "Memory 2080MHz, 853mV"

Now when i update drivers to either latest 20.9.2 or drivers back to near beginning of the year i can mine again but now the hashrate is 19.2
Without tuning gpus i get 22.4 hash

Before #379 my hashrate was 31.3

In my bat file i have "-eres 0 -epsw x -mode 1 -r 1 -strap 1 -rxboost 1"

looking forward to solution
thanks

rdeon settings => Settings => Graphics => Advenced => GPU Workload = Compute

[andrew115200]

Looks like it is time say goodbye to Claymore. Thanks for many years for miner. i moved to phoenixminer works good but cant get hashrates like in claymoe, i will appreciate if someon can share AMD mem tweaks for RX470/480/570/580, Thanks everybody

https://drive.google.com/file/d/1I-7MCcNIm2cV7Nf4nmq8DH6EibPbEhyb/view?usp=sharing
This tweak with command --ref 30 is analog -rxboost in claymore miner.
Create shortcut of file start_WAMDT.bat and put into autostart directory (C:\Users\USERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup), also you can change timeout in file start_WAMDT.bat to start tweak, i set 12sec.

[teosoph]

reinstalled Windows with rx480, switch to calculate in radeon drivers, add arguments to claymore specified -strap 1 -rxboost 1 in Nicehash miner ---- everything is as it was before, but claymore did not accept these arguments and gives 24 mx.

Can you tell me what the problem is?

[alexkidd360]

Hello Everyone   
first post!!

i am running 2 rigs, all cards are RX 580 8g armors, Windows 10 with claymore v15, both rigs stopped working when the ETC epoch hit #379
All GPU's  "not enough GPU memory to place DAG, you cannot mine this coin with this GPU"
"OpenCL error -61 - cannot allocate big buffer for DAG"
"OpenCl error -38 - cannot write buffer for DAG"
server: accept failed with error: 10004

my virtual mem is at 55000
AMD Drivers 19.9.2
im using AMD software for tuning GPU's "GPU 1165MHz, 853mV" "Memory 2080MHz, 853mV"

Now when i update drivers to either latest 20.9.2 or drivers back to near beginning of the year i can mine again but now the hashrate is 19.2
Without tuning gpus i get 22.4 hash

Before #379 my hashrate was 31.3

In my bat file i have "-eres 0 -epsw x -mode 1 -r 1 -strap 1 -rxboost 1"

looking forward to solution
thanks

rdeon settings => Settings => Graphics => Advenced => GPU Workload = Compute

Already have on Compute