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

[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?

[reb0rn21]

I try to send API call to claymore to disable all GPU but nothing happens, I set  -mpsw xxx, and I try with telnet:

{"id":0,"jsonrpc":"2.0", "psw":"xxx", "method":"control_gpu", "params":[-1, 0]}

[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.

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?

WHAT THE HELL DOES IT MATTER AND WHAT IS IT TO YOU???
Mind your own business. If I like Coke over Pepsi, I'll drink Coke. If I like mustard on my hot dog, I'll take mustard on it. Last I knew I needn't explain my preferences or loyalty.
I don't give a shit who or what you like, do I?
What does my GENDER have to do with anything? Are you wanting to fucking ask me out? Will you try to date rape me or some shit? Fuck off!

[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.

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?

WHAT THE HELL DOES IT MATTER AND WHAT IS IT TO YOU???
Mind your own business. If I like Coke over Pepsi, I'll drink Coke. If I like mustard on my hot dog, I'll take mustard on it. Last I knew I needn't explain my preferences or loyalty.
I don't give a shit who or what you like, do I?
What does my GENDER have to do with anything? Are you wanting to fucking ask me out? Will you try to date rape me or some shit? Fuck off!

This loss of control obviously shows what your gender is. Don't worry! I date only normal female.

You don't know shit. Mind your own business and stay on topic.

[UnclWish]

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?

WHAT THE HELL DOES IT MATTER AND WHAT IS IT TO YOU???
Mind your own business. If I like Coke over Pepsi, I'll drink Coke. If I like mustard on my hot dog, I'll take mustard on it. Last I knew I needn't explain my preferences or loyalty.
I don't give a shit who or what you like, do I?
What does my GENDER have to do with anything? Are you wanting to fucking ask me out? Will you try to date rape me or some shit? Fuck off!

This loss of control obviously shows what your gender is. Don't worry! I date only normal female.

You don't know shit. Mind your own business and stay on topic.

But he right about PM. And here is only positives - less fee, faster speed, equal or less power with him...

[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.

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?

WHAT THE HELL DOES IT MATTER AND WHAT IS IT TO YOU???
Mind your own business. If I like Coke over Pepsi, I'll drink Coke. If I like mustard on my hot dog, I'll take mustard on it. Last I knew I needn't explain my preferences or loyalty.
I don't give a shit who or what you like, do I?
What does my GENDER have to do with anything? Are you wanting to fucking ask me out? Will you try to date rape me or some shit? Fuck off!

This loss of control obviously shows what your gender is. Don't worry! I date only normal female.

You don't know shit. Mind your own business and stay on topic.

But he right about PM. And here is only positives - less fee, faster speed, equal or less power with him...

Regardless of the opinion, THIS thread is about Claymore and HIS development. Not PM. If you were to open a thread sharing work that you've dedicated several hours to (and profiting from for those hours) just for someone to post reason(s) not to support him and to support someone else's work, would that be appropriate? On top of that express an inappropriate, rude and sexist attitude toward another member? Sure, I posted the original statement about PM software being updated. Obviously, that wasn't the best idea since now it put this douchwad on my ignore list (because he is clearly out of line) but I shared that information to spur development on Claymore and to INFORM other members of the advancement. At no point was my intention to ever persuade or coerce anyone to switch to PhoenixMiner. He on the other hand appears to be doing exactly that... in Claymore's thread. Which is definitely inappropriate. If he is such a PM supporter then what the hell is he doing posting in this thread? The sexist comments that he was posting was not only off topic but also libel. He doesn't know shit about me or anyone else on here, no less to even assume what a "normal female" is. His comments were definitely inappropriate, sexist, libel, rude, inappropriate and definitely off topic. Such are nothing but counterproductive.

[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?

WHAT THE HELL DOES IT MATTER AND WHAT IS IT TO YOU???
Mind your own business. If I like Coke over Pepsi, I'll drink Coke. If I like mustard on my hot dog, I'll take mustard on it. Last I knew I needn't explain my preferences or loyalty.
I don't give a shit who or what you like, do I?
What does my GENDER have to do with anything? Are you wanting to fucking ask me out? Will you try to date rape me or some shit? Fuck off!

This loss of control obviously shows what your gender is. Don't worry! I date only normal female.

You don't know shit. Mind your own business and stay on topic.

But he right about PM. And here is only positives - less fee, faster speed, equal or less power with him...

Regardless of the opinion, THIS thread is about Claymore and HIS development. Not PM. If you were to open a thread sharing work that you've dedicated several hours to (and profiting from for those hours) just for someone to post reason(s) not to support him and to support someone else's work, would that be appropriate? On top of that express an inappropriate, rude and sexist attitude toward another member? Sure, I posted the original statement about PM software being updated. Obviously, that wasn't the best idea since now it put this douchwad on my ignore list (because he is clearly out of line) but I shared that information to spur development on Claymore and to INFORM other members of the advancement. At no point was my intention to ever persuade or coerce anyone to switch to PhoenixMiner. He on the other hand appears to be doing exactly that... in Claymore's thread. Which is definitely inappropriate. If he is such a PM supporter then what the hell is he doing posting in this thread? The sexist comments that he was posting was not only off topic but also libel. He doesn't know shit about me or anyone else on here, no less to even assume what a "normal female" is. His comments were definitely inappropriate, sexist, libel, rude, inappropriate and definitely off topic. Such are nothing but counterproductive.

Sorry, i didn' want to be rude.

[zeef]

Hi,

Is this miner still maintained? Where can i see the changelog? 

[larryhg]

Need Help for strap
My rig has 3 GTX 1070 and 3 DTX 1060.

I am using 1@4600 for GTX 1070 to get an extra 7% of hash rate.

like

-strap 1@4600, 1@4600,1@4600,1,1,1

but sometime the 1070  would have an unknown error, causing the GPU out of line and miner would restart its own. Also one of 1060 is going to run at 4600 and causing 1060 has error and the miner keeping crash.

Someone has a solution for this. If the strap option can apply to PCI bus could solve this issue.

Thanks a lot

Larry

[jpmonster]

I have 8 x GTX 1050 Ti 4GB on Windows 10.
This morning they stopped with DAG creation error.
Any idea how to resolve this, the DAG is only 3.3GB I believe
My Virtual Memory is more than enough to cover all of my cards in the rig.

[jpmonster]

I already have these set:

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

Has any one go this to work with a 4GB GTX 1050 ti recently

[bategojko74]

I already have these set:

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

Has any one go this to work with a 4GB GTX 1050 ti recently

Check with gpu-z how match gpu memory is used from windows before starting the miner.

[jpmonster]

I already have these set:

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

Has any one go this to work with a 4GB GTX 1050 ti recently

Check with gpu-z how match gpu memory is used from windows before starting the miner.

GPU-z says 77MB used

[dortortz]

I'm having the same issue today out of nowhere with all 5 of my 1050ti. Cannot write DAG. I've tried many things:
Updated driver, no go
Downgraded driver, no go
-eres 0, no go
increase page file size to 40gb, no go

please, we need help, our 1050ti's are dying lol