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

[Matthew_Nanopool]

Hey guys,

I would like the dev team to confirm that Claymore does not mine PascalCoin (RandomHash algo) any longer (cannot find it anywhere). There are people that think Claymore is still capable of mining PascalCoin and blame mining pools when they don't see results at their accounts.

Thanks in advance!

[Havane]

Hello

Strap and rxboost don't increase my hashrate. I have rx480 and rx570 cards, latest AMD drivers on Win10, bios are moded, and I use the -cclock and -mclock option : I get ~30 Mh/s for each card for solo mining.
Is it OK ? Why strap and rxboost don't increase ?

Thanks

[awarywocki]

Hello

Strap and rxboost don't increase my hashrate. I have rx480 and rx570 cards, latest AMD drivers on Win10, bios are moded, and I use the -cclock and -mclock option : I get ~30 Mh/s for each card.
Is it OK ? Why strap and rxboost don't increase ?

Thanks

Did you start ethdcrminer64.exe with admin privileges for the first time to install the driver? If your bioses are modded you can see no difference with strap mode but you should see the difference with rxboost option

[Havane]

Hello

Strap and rxboost don't increase my hashrate. I have rx480 and rx570 cards, latest AMD drivers on Win10, bios are moded, and I use the -cclock and -mclock option : I get ~30 Mh/s for each card.
Is it OK ? Why strap and rxboost don't increase ?

Thanks

Did you start ethdcrminer64.exe with admin privileges for the first time to install the driver? If your bioses are modded you can see no difference with strap mode but you should see the difference with rxboost option

Yes I ran the  install driver, and now I don't have any error.

With rxboost, I 've only ~31 Mh/s instead of 30

[awarywocki]

Hello

Strap and rxboost don't increase my hashrate. I have rx480 and rx570 cards, latest AMD drivers on Win10, bios are moded, and I use the -cclock and -mclock option : I get ~30 Mh/s for each card.
Is it OK ? Why strap and rxboost don't increase ?

Thanks

Did you start ethdcrminer64.exe with admin privileges for the first time to install the driver? If your bioses are modded you can see no difference with strap mode but you should see the difference with rxboost option

Yes I ran the  install driver, and now I don't have any error.

With rxboost, I 've only ~31 Mh/s instead of 30

So it is quite ok i guess. I get about 5mh/s up on my 6gpu rig after rxboost

[ZPDM]

Can't download Claymore from MEGA

"SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data"
occured on a Windows and Linux machine

Don't see any other download sites.

Edit: it seems to be working again.

you can download the already configured miner by the link in this video. there everything is configured, you need to put only your wallet address. https://www.youtube.com/watch?v=xyWP8f_Ajqo&t=3s

Working fine now, but, Spasibo Comrade.

[ZPDM]

Always download from official Claymore links. If not, sooner or later another noob start to cry here that Claymore is a thief.
[/quote]

That was the point it was the link from the OP, it didn't work.  Likely something brief on MEGA's side.  The VII is purring along, now to optomize this week-end.  If I recall some years back there was a back-up link for downloading the miner, might not be a bad idea to reincorporate some such for increased Claymore revenue if the only current link remains intermittant.

[ZPDM]

I downloaded and until now I alive
[/quote]


Was likely an uptime problem on MEGA's side, or she turned me into a newt but I got better.

You know I didn't get the conern till this second, but no, everything has been running fine on a new machine with one VII for fun. 

[abg00]

21:45:54:383    54900700    Setting DAG epoch #280 for GPU0
21:45:54:383    54900700    Create GPU buffer for GPU0
21:45:54:383    54900700    GPU0 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
21:45:54:383    54900700    GPU0 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

same trouble now with nicehash

OpenCL error -38 - cannot write buffer for DAG

[awarywocki]

21:45:54:383    54900700    Setting DAG epoch #280 for GPU0
21:45:54:383    54900700    Create GPU buffer for GPU0
21:45:54:383    54900700    GPU0 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
21:45:54:383    54900700    GPU0 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

same trouble now with nicehash

OpenCL error -38 - cannot write buffer for DAG

Switch mining to ETH (epoch 272 for now). I wrote about this few days ago. We need new version of claymore I guess

[abg00]

21:45:54:383    54900700    Setting DAG epoch #280 for GPU0
21:45:54:383    54900700    Create GPU buffer for GPU0
21:45:54:383    54900700    GPU0 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
21:45:54:383    54900700    GPU0 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

same trouble now with nicehash

OpenCL error -38 - cannot write buffer for DAG

Switch mining to ETH (epoch 272 for now). I wrote about this few days ago. We need new version of claymore I guess

possible drivers trouble? use 18.6.1
14.6 same trouble
phoenixminer work without this trouble?

add
check again. trouble because ETC coin DAG epoch #281

[abg00]

check phoenix. work fine with DAG epoch 281 ETC coin

check 8gb card. same trouble error dag file size

[sharmanov]

does anyone know what error 1002 means? I'm getting GPU #0 strap "1" failed, error 1002  how do I fix that and what does that error mean? all straps get that error
Using Radeon VII

[dvz35]

21:45:54:383    54900700    Setting DAG epoch #280 for GPU0
21:45:54:383    54900700    Create GPU buffer for GPU0
21:45:54:383    54900700    GPU0 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
21:45:54:383    54900700    GPU0 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

same trouble now with nicehash

OpenCL error -38 - cannot write buffer for DAG

Switch mining to ETH (epoch 272 for now). I wrote about this few days ago. We need new version of claymore I guess

possible drivers trouble? use 18.6.1
14.6 same trouble
phoenixminer work without this trouble?

add
check again. trouble because ETC coin DAG epoch #281

https://www.youtube.com/watch?v=P8EdQGm9x74&t=1s

[NefariousFool]

Hey Claymore any input or any sort of work going on to get the new rx 5700xt mining on your platform? Thanks!

Yes I'm checking this card, but I need a few days to see what hashrate it can achieve.
[/quote]

Any update friend? We are sitting on the edge of our seats!  Is there anything anybody can contribute to help you out with this process?

Did you try the washer fix for cooling on your card if you have one?

[NefariousFool]

does anyone know what error 1002 means? I'm getting GPU #0 strap "1" failed, error 1002  how do I fix that and what does that error mean? all straps get that error
Using Radeon VII

The straps do not work on Radeon Vii thats why you're getting that error, its not supported. You should try running the intensity tricks on the miner vs straps.

[abg00]

any news about ETC dag 281+ mining? use phoenix now. this miner dont work

[Claymore]

Any update friend? We are sitting on the edge of our seats!  Is there anything anybody can contribute to help you out with this process?
Did you try the washer fix for cooling on your card if you have one?

I'm working on it, just need a couple of days more. AMD even did not release official ISA docs for RDNA yet...

any news about ETC dag 281+ mining? use phoenix now. this miner dont work

What's wrong with dag 281 epoch? It works fine in my tests. If you want to get some support, it's a good idea to post your config.txt file and some hardware info (or log file).

[awarywocki]

What's wrong with dag 281 epoch? It works fine in my tests. If you to get some support, it's a good idea to post your config.txt file and some hardware info (or log file).

I have a miner hang at epoch 280 (both Rx 470 4gb and Rx 480 4gb). After switch to ETH (epoch 272 it still working well). It is not a config problem it is problem with miner. Check phoenix miner topic and there is same epoch problem with older miner versions

C&p
"Read this if you can't mine ETH or ETC with PhoenixMiner: important message for everyone that is running older versions of PhoenixMiner (before 4.2).

IMPORTANT! The versions of PhoenixMiner before 4.2 only support DAG epoch up to 265. Both ETC and ETH has reached epoch 266 already. To ensure uninterrupted operation, please upgrade to 4.2. If you are mining other coins, you can safely disregard this message.

The reason for this limitation is that we need to perform some quite complex calculations for each future DAG epoch in order to increase the hashrate of the optimized kernels. Recently we have added more computational resources and PhoenixMiner 4.2 will work without problems up to DAG epoch 329. We will increase this number significantly (e.g. 400 or more) in the next version."

[UnclWish]

What's wrong with dag 281 epoch? It works fine in my tests. If you to get some support, it's a good idea to post your config.txt file and some hardware info (or log file).

I have a miner hang at epoch 280 (both Rx 470 4gb and Rx 480 4gb). After switch to ETH (epoch 272 it still working well). It is not a config problem it is problem with miner. Check phoenix miner topic and there is same epoch problem with older miner versions

C&p
"Read this if you can't mine ETH or ETC with PhoenixMiner: important message for everyone that is running older versions of PhoenixMiner (before 4.2).

IMPORTANT! The versions of PhoenixMiner before 4.2 only support DAG epoch up to 265. Both ETC and ETH has reached epoch 266 already. To ensure uninterrupted operation, please upgrade to 4.2. If you are mining other coins, you can safely disregard this message.

The reason for this limitation is that we need to perform some quite complex calculations for each future DAG epoch in order to increase the hashrate of the optimized kernels. Recently we have added more computational resources and PhoenixMiner 4.2 will work without problems up to DAG epoch 329. We will increase this number significantly (e.g. 400 or more) in the next version."

Phoenix miner works another way than Claymore's. It use optimized kernels wich is must be calculated with depends of DAG epoch. This is why if miner didn't contains optimized kernels for some DAG it would give error.

Claymore's miner didn't use kernels optimized for each epoch. So it must work on any DAG. You must provide your config, bat file and log to determine what's your problem.