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

[oskoa]

Hey, ive a question.

I ve RX 570 (Ellesmere) and i use a little OC in memory (like 1600 to 2000). and i use this way always. Now reading the author's notes, i used the Driver install, Strap and RXBoost, and i can see a good changre (since 24 to 31 hasrate), and i dont see changes in the MSI Afterburner (same clock/mermory/tdp/temp that without these options). The question is, if my cards will be afected really with this options. Thanks.

If you have set the OC settings in the Claymore config file and you actually are getting 31 MH/s then you have done it correctly. Depending what AMD drivers you are running, you might get issues with MSI Afterburner. So if you want to verify your clocks you can try using the AMD Driver software called WattMan which is in the AMD display settings, or you can just use GPU-Z. Launch it and you will see your current clocks.

You should also undervolt if you haven't to save some watts and lower the temperature of your GPUs. You can also verify your hash speed in your pool after a few hours since the difference between 24 to 31 mh/s should be noticeable.

Hello and thanks. What i win exactly undervolting the Cards?

[batsonxl]

Hi claymore and everyone else.
I need help with this timing straps and OC.
Im using nicehash.there is claymore 15 on it.

1st problem: i use -strap 1 into settings (extra lunch parameters) it works if i OC gpus from after burner.gets 29Mhz for rx 470.but after while every time after new DAG settings happens my cards starts use more power(wattman same result) so every time i need from after burner move slider low or high and hot apply.then again anda again happens.im tired of this, what is the problem? when it drains more power more hotter my gpu are get.

2nd problem: i cant lunch rxboost. on nicehash in extran lunch parametrs i write -strap1 -rxboost, strap works but rxboost not.

Help guys in this difficult days
Thanks

[zenstrive]

Anyone mining with RX 5700,
has any of you experiencing strange phenomena where only the one of the GPU is actually mining/or having its memory loaded with mining job?

[WhackOBill]

Hello and thanks. What i win exactly undervolting the Cards?

Lower power usage and cooler GPU temps.

[Binary100100]

Well... I hate to say this... but I'm getting 60MH/s using PhoenixMiner 4.6c now.

-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -acm -mi 12 -gt 126 -mode 1 -clKernel 1 -clNew 1 -clf 0 -lidag 1 -openclLocalWork 128 -openclGlobalMultiplier 4096

~95 watts per card and 59C.

I like it a lot!

(Credit to PedPandaMining)

[Bathmat]

Well... I hate to say this... but I'm getting 60MH/s using PhoenixMiner 4.6c now.

-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -acm -mi 12 -gt 126 -mode 1 -clKernel 1 -clNew 1 -clf 0 -lidag 1 -openclLocalWork 128 -openclGlobalMultiplier 4096

~95 watts per card and 59C.

I like it a lot!

I'm getting incorrect shares with those settings... and not just a couple.

[Binary100100]

Well... I hate to say this... but I'm getting 60MH/s using PhoenixMiner 4.6c now.

-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -acm -mi 12 -gt 126 -mode 1 -clKernel 1 -clNew 1 -clf 0 -lidag 1 -openclLocalWork 128 -openclGlobalMultiplier 4096

~95 watts per card and 59C.

I like it a lot!

I'm getting incorrect shares with those settings... and not just a couple.

Yeah, I got a lot too. About 30%.
I'm trying this now:
-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -acm -mi 12 -mode 1 -clKernel 3 -clNew 1 -clf 0 -lidag 1 -openclLocalWork 128 -openclGlobalMultiplier 4096

I removed the -gt and hope that clears up a bit. Seems like it needs some tuning still but it's progress!


-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -clKernel 3 -clNew 1 -openclLocalWork 64
Seems much better. It's been running for about 4 minutes and no incorrect shares (yet).

[bategojko74]

Well... I hate to say this... but I'm getting 60MH/s using PhoenixMiner 4.6c now.

-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -acm -mi 12 -gt 126 -mode 1 -clKernel 1 -clNew 1 -clf 0 -lidag 1 -openclLocalWork 128 -openclGlobalMultiplier 4096

~95 watts per card and 59C.

I like it a lot!

It seems to me that PM is optimized especially for 32 threads per work group and doesn't work correctly for more. So I think that this 60 MH/s is fake and that your -openclLocalWork 64/128 causes incorrect shares.

[Binary100100]

Well... I hate to say this... but I'm getting 60MH/s using PhoenixMiner 4.6c now.

-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -acm -mi 12 -gt 126 -mode 1 -clKernel 1 -clNew 1 -clf 0 -lidag 1 -openclLocalWork 128 -openclGlobalMultiplier 4096

~95 watts per card and 59C.

I like it a lot!

It seems to me that PM is optimized especially for 32 threads per work group and doesn't work correctly for more. So I think that this 60 MH/s is fake and that your -openclLocalWork 128 causes incorrect shares.

I'm trying this:
-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -gt 100 -clKernel 3 -clNew 1 -openclLocalWork 64

And it's pretty solid. I'm only getting 56.6 though. No incorrect shares.

[bategojko74]

Well... I hate to say this... but I'm getting 60MH/s using PhoenixMiner 4.6c now.

-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -acm -mi 12 -gt 126 -mode 1 -clKernel 1 -clNew 1 -clf 0 -lidag 1 -openclLocalWork 128 -openclGlobalMultiplier 4096

~95 watts per card and 59C.

I like it a lot!

It seems to me that PM is optimized especially for 32 threads per work group and doesn't work correctly for more. So I think that this 60 MH/s is fake and that your -openclLocalWork 128 causes incorrect shares.

I'm trying this:
-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -gt 100 -clKernel 3 -clNew 1 -openclLocalWork 64

And it's pretty solid. I'm only getting 56.6 though. No incorrect shares.

..for now. You are a great optimist.

[Binary100100]

Well... I hate to say this... but I'm getting 60MH/s using PhoenixMiner 4.6c now.

-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -acm -mi 12 -gt 126 -mode 1 -clKernel 1 -clNew 1 -clf 0 -lidag 1 -openclLocalWork 128 -openclGlobalMultiplier 4096

~95 watts per card and 59C.

I like it a lot!

It seems to me that PM is optimized especially for 32 threads per work group and doesn't work correctly for more. So I think that this 60 MH/s is fake and that your -openclLocalWork 128 causes incorrect shares.

I'm trying this:
-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -gt 100 -clKernel 3 -clNew 1 -openclLocalWork 64

And it's pretty solid. I'm only getting 56.6 though. No incorrect shares.

..for now. You are a great optimist.

As stated, it still needs some tweaking but it's progress!
I'm keeping it with these settings for now. Only 1 incorrect share out of 22 so far.

[Bathmat]

Well... I hate to say this... but I'm getting 60MH/s using PhoenixMiner 4.6c now.

-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -acm -mi 12 -gt 126 -mode 1 -clKernel 1 -clNew 1 -clf 0 -lidag 1 -openclLocalWork 128 -openclGlobalMultiplier 4096

~95 watts per card and 59C.

I like it a lot!

It seems to me that PM is optimized especially for 32 threads per work group and doesn't work correctly for more. So I think that this 60 MH/s is fake and that your -openclLocalWork 128 causes incorrect shares.

I'm trying this:
-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -gt 100 -clKernel 3 -clNew 1 -openclLocalWork 64

And it's pretty solid. I'm only getting 56.6 though. No incorrect shares.

..for now. You are a great optimist.

As stated, it still needs some tweaking but it's progress!
I'm keeping it with these settings for now. Only 1 incorrect share out of 22 so far.

So you have a 5% speed gain, but losing 5% to incorrect shares.... seems like a wash to me. Until the kernels are written for that worksize (if it's even possible), seems like using the default settings is the best way to go.

[Binary100100]

Well... I hate to say this... but I'm getting 60MH/s using PhoenixMiner 4.6c now.

-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -acm -mi 12 -gt 126 -mode 1 -clKernel 1 -clNew 1 -clf 0 -lidag 1 -openclLocalWork 128 -openclGlobalMultiplier 4096

~95 watts per card and 59C.

I like it a lot!

It seems to me that PM is optimized especially for 32 threads per work group and doesn't work correctly for more. So I think that this 60 MH/s is fake and that your -openclLocalWork 128 causes incorrect shares.

I'm trying this:
-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -gt 100 -clKernel 3 -clNew 1 -openclLocalWork 64

And it's pretty solid. I'm only getting 56.6 though. No incorrect shares.

..for now. You are a great optimist.

As stated, it still needs some tweaking but it's progress!
I'm keeping it with these settings for now. Only 1 incorrect share out of 22 so far.

So you have a 5% speed gain, but losing 5% to incorrect shares.... seems like a wash to me. Until the kernels are written for that worksize (if it's even possible), seems like using the default settings is the best way to go.

You mean a 10% gain?
50MH/s increased to 55MH/s is 10%. But I get your point.

[Bathmat]

So you have a 5% speed gain, but losing 5% to incorrect shares.... seems like a wash to me. Until the kernels are written for that worksize (if it's even possible), seems like using the default settings is the best way to go.

You mean a 10% gain?
50MH/s increased to 55MH/s is 10%. But I get your point.

Yeah, sure. I tried all the settings you just did, and every time, the % gain was almost exactly offset by % invalid shares. However, I did not run very long tests, so it could be possible that pool-side effective hashrate might go up even with the incorrect shares, but I doubt it.

[Binary100100]

So you have a 5% speed gain, but losing 5% to incorrect shares.... seems like a wash to me. Until the kernels are written for that worksize (if it's even possible), seems like using the default settings is the best way to go.

You mean a 10% gain?
50MH/s increased to 55MH/s is 10%. But I get your point.

Yeah, sure. I tried all the settings you just did, and every time, the % gain was almost exactly offset by % invalid shares. However, I did not run very long tests, so it could be possible that pool-side effective hashrate might go up even with the incorrect shares, but I doubt it.

All of my incorrect shares were from the same GPU (I have three) so it's possible that it's just my XFX GPU since it's also the GPU that won't let me clock past 900Mhz without the watchdog error. Thinking of returning it.

But from 49.5 to 57 seems like an improvement to me. Once Claymore releases some Navi kernels for his software then we'll be in business for sure.

[bategojko74]

So you have a 5% speed gain, but losing 5% to incorrect shares.... seems like a wash to me. Until the kernels are written for that worksize (if it's even possible), seems like using the default settings is the best way to go.

You mean a 10% gain?
50MH/s increased to 55MH/s is 10%. But I get your point.

Yeah, sure. I tried all the settings you just did, and every time, the % gain was almost exactly offset by % invalid shares. However, I did not run very long tests, so it could be possible that pool-side effective hashrate might go up even with the incorrect shares, but I doubt it.

All of my incorrect shares were from the same GPU (I have three) so it's possible that it's just my XFX GPU since it's also the GPU that won't let me clock past 900Mhz without the watchdog error. Thinking of returning it.

But from 49.5 to 57 seems like an improvement to me. Once Claymore releases some Navi kernels for his software then we'll be in business for sure.

Claymore has already released his version with Navi support. Quoting Claymore:
-----------------------------------------------------
v15.0:

- now miner supports up to #384 epoch (4GB DAG size). Note that previous versions support up to #299 epoch, you will not be able to use old versions after #299 epoch.
- added support for Navi cards (ETH-only mode).
- now miner sets environment variables automatically (required for 4GB AMD cards).
- a few minor bug fixes and improvements.

PS. AMD still has no public Navi drivers with DAG-fix, so currently 5700XT shows a very bad hashrate. But AMD already solved this issue and they promise to release public drivers soon...
-----------------------------------------------------

What else do you expect from him, to start walking on water like Jesus did?

[Binary100100]

So you have a 5% speed gain, but losing 5% to incorrect shares.... seems like a wash to me. Until the kernels are written for that worksize (if it's even possible), seems like using the default settings is the best way to go.

You mean a 10% gain?
50MH/s increased to 55MH/s is 10%. But I get your point.

Yeah, sure. I tried all the settings you just did, and every time, the % gain was almost exactly offset by % invalid shares. However, I did not run very long tests, so it could be possible that pool-side effective hashrate might go up even with the incorrect shares, but I doubt it.

All of my incorrect shares were from the same GPU (I have three) so it's possible that it's just my XFX GPU since it's also the GPU that won't let me clock past 900Mhz without the watchdog error. Thinking of returning it.

But from 49.5 to 57 seems like an improvement to me. Once Claymore releases some Navi kernels for his software then we'll be in business for sure.

Claymore has already released his version with Navi support. Quoting Claymore:
-----------------------------------------------------
v15.0:

- now miner supports up to #384 epoch (4GB DAG size). Note that previous versions support up to #299 epoch, you will not be able to use old versions after #299 epoch.
- added support for Navi cards (ETH-only mode).
- now miner sets environment variables automatically (required for 4GB AMD cards).
- a few minor bug fixes and improvements.

PS. AMD still has no public Navi drivers with DAG-fix, so currently 5700XT shows a very bad hashrate. But AMD already solved this issue and they promise to release public drivers soon...
-----------------------------------------------------

What else do you expect from him, to start walking on water like Jesus did?

I've removed the "-openclLocalWork 64" completely and I'm averaging 52 instead of 49.5 with ZERO errors or incorrect shares. PhoenixMiner says that the new kernel is included in the latest version. IF the developers coordinate and assist each other instead of competing against each other more can be accomplished. Granted I don't know if they do share tips with each other. Anyway, I still prefer Claymore... but so far Phoenix yields better results after this update. Not sure how he did it but it is an improvement nonetheless. I hope he can figure something out (and I'm sure he will) because I prefer Claymore.

[Bathmat]

What else do you expect from him, to start walking on water like Jesus did?

I've removed the "-openclLocalWork 64" completely and I'm averaging 52 instead of 49.5 with ZERO errors or incorrect shares. PhoenixMiner says that the new kernel is included in the latest version. IF the developers coordinate and assist each other instead of competing against each other more can be accomplished. Granted I don't know if they do share tips with each other. Anyway, I still prefer Claymore... but so far Phoenix yields better results after this update. Not sure how he did it but it is an improvement nonetheless. I hope he can figure something out (and I'm sure he will) because I prefer Claymore.

Well, the faster he can make his miner, the more dev fee he will collect. So yeah, I think optimizing the kernel would be worth it to him.

[Binary100100]

What else do you expect from him, to start walking on water like Jesus did?

I've removed the "-openclLocalWork 64" completely and I'm averaging 52 instead of 49.5 with ZERO errors or incorrect shares. PhoenixMiner says that the new kernel is included in the latest version. IF the developers coordinate and assist each other instead of competing against each other more can be accomplished. Granted I don't know if they do share tips with each other. Anyway, I still prefer Claymore... but so far Phoenix yields better results after this update. Not sure how he did it but it is an improvement nonetheless. I hope he can figure something out (and I'm sure he will) because I prefer Claymore.

Well, the faster he can make his miner, the more dev fee he will collect. So yeah, I think optimizing the kernel would be worth it to him.

I hope so.

So... I let this run for exactly 5 hours and 19 minutes.
Three XFX 5700 XT cards.
Accepted 318, Rejected 0, HW Errors 0
Averaging 52 MH/s for 156 MH/s combined and 277w combined (92w - 94w each)

This is my setting for PhoenixMiner:
-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -clKernel 1 -clNew 1

You have to admit that these are very solid, stable and promising. Results of 52MH/s for 92w is 0.56MH/s per watt seems pretty efficient. Ideally I'd love to have a 500+MH/s Ethereum mining rig on a 1,000w PSU and I believe that it's achievable with these cards.

[bategojko74]

So you have a 5% speed gain, but losing 5% to incorrect shares.... seems like a wash to me. Until the kernels are written for that worksize (if it's even possible), seems like using the default settings is the best way to go.

You mean a 10% gain?
50MH/s increased to 55MH/s is 10%. But I get your point.

Yeah, sure. I tried all the settings you just did, and every time, the % gain was almost exactly offset by % invalid shares. However, I did not run very long tests, so it could be possible that pool-side effective hashrate might go up even with the incorrect shares, but I doubt it.

All of my incorrect shares were from the same GPU (I have three) so it's possible that it's just my XFX GPU since it's also the GPU that won't let me clock past 900Mhz without the watchdog error. Thinking of returning it.

But from 49.5 to 57 seems like an improvement to me. Once Claymore releases some Navi kernels for his software then we'll be in business for sure.

Claymore has already released his version with Navi support. Quoting Claymore:
-----------------------------------------------------
v15.0:

- now miner supports up to #384 epoch (4GB DAG size). Note that previous versions support up to #299 epoch, you will not be able to use old versions after #299 epoch.
- added support for Navi cards (ETH-only mode).
- now miner sets environment variables automatically (required for 4GB AMD cards).
- a few minor bug fixes and improvements.

PS. AMD still has no public Navi drivers with DAG-fix, so currently 5700XT shows a very bad hashrate. But AMD already solved this issue and they promise to release public drivers soon...
-----------------------------------------------------

What else do you expect from him, to start walking on water like Jesus did?

I've removed the "-openclLocalWork 64" completely and I'm averaging 52 instead of 49.5 with ZERO errors or incorrect shares. PhoenixMiner says that the new kernel is included in the latest version. IF the developers coordinate and assist each other instead of competing against each other more can be accomplished. Granted I don't know if they do share tips with each other. Anyway, I still prefer Claymore... but so far Phoenix yields better results after this update. Not sure how he did it but it is an improvement nonetheless. I hope he can figure something out (and I'm sure he will) because I prefer Claymore.

Why do you prefer Claymore? It is slower than PM on any GPU. It takes twice more devfee. Consumes less or equal power. What is more important than these three facts? Your emotional affection? Are you a female?