Claymore's CryptoNote AMD GPU Miner v11.3

[Call_Me_Bambi]

How to mine coins other than XMR with version 9.7?

You can, of course, mine any Cryptonote coin with the Claymore Cryptonote miner; how to mine depends on which coin and what pool you want to use.

For example, if you want to mine Sumokoin, https://bitcointalk.org/index.php?topic=1905086.0 , this is what you could use.
Sumokoin pool: https://pool.sumokoin.com/

Code:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_SINGLE_ALLOC_PERCENT 100
setx GPU_MAX_ALLOC_PERCENT 100

NsGpuCNMiner -o stratum+tcp://pool.sumokoin.com:3333 -u SumokoinAddress -p x -a 0 -ftime 10 -allpools 1 

[pehoko]

KMC mining not working with 9.7 with 10.2 always crash, I will try sgminer as this claymore miner  is useless for me.

[swiftfox]

Hi! I have a problem after I start the miner with what I can say are the right settings, but when I launch it, I get a red error code. The code says:
UNKNOWN OPTION -u
UNKNOWN OPTION My username
UNKNOWN OPTION -p
UNKNOWN OPTION my password

What do you suggest I should do?

Let's start with a clean slate.

Make sure the "config.txt" file looks something like this, it does not matter what is in there as long as each line starts with a # symbol.

Code:

#-xpool 
#-xwal 
#-xpsw x
#-allpools 1

Delete everything in the "start.bat" file then add this to the start.bat file save and run start.bat - let us know how you get on.

Code:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_SINGLE_ALLOC_PERCENT 100
setx GPU_MAX_ALLOC_PERCENT 100

NsGpuCNMiner.exe -xpool ssl://europe.cryptonight-hub.miningpoolhub.com:20580 -xwal monolith.worker -xpsw x  -nofee 1 -ftime 10 -h 0 -dmem -1

Okay, it sorta worked, but now I get this
GPU 0, GpuMiner dk2a failed -4
GPU 0, GpuMiner dk2an0 failed - 4
GPU 0, GpuMiner dk2an0 failed - 4
GPU 0, GpuMiner dk2an0 failed - 4

[BSAlex]

Okay, it sorta worked, but now I get this
GPU 0, GpuMiner dk2a failed -4
GPU 0, GpuMiner dk2an0 failed - 4
GPU 0, GpuMiner dk2an0 failed - 4
GPU 0, GpuMiner dk2an0 failed - 4

Okay, if you sorta care to read a few messages of the topic you'll surely find that virtual memory setting that you are using are too low. Please set virtual memory to more then total RAM of all your GPU, I am using 64Gb

[gsanjin]

Hi! I have a problem after I start the miner with what I can say are the right settings, but when I launch it, I get a red error code. The code says:
UNKNOWN OPTION -u
UNKNOWN OPTION My username
UNKNOWN OPTION -p
UNKNOWN OPTION my password

What do you suggest I should do?

Let's start with a clean slate.

Make sure the "config.txt" file looks something like this, it does not matter what is in there as long as each line starts with a # symbol.

NsGpuCNMiner.exe -xpool ssl://europe.cryptonight-hub.miningpoolhub.com:20580 -xwal monolith.worker -xpsw x  -nofee 1 -ftime 10 -h 0 -dmem -1

Okay, it sorta worked, but now I get this
GPU 0, GpuMiner dk2a failed -4
GPU 0, GpuMiner dk2an0 failed - 4
GPU 0, GpuMiner dk2an0 failed - 4
GPU 0, GpuMiner dk2an0 failed - 4

Try -dmem 0

[Call_Me_Bambi]

Okay, it sorta worked, but now I get this
GPU 0, GpuMiner dk2a failed -4
GPU 0, GpuMiner dk2an0 failed - 4
GPU 0, GpuMiner dk2an0 failed - 4
GPU 0, GpuMiner dk2an0 failed - 4

There have been a couple of good suggestions already posted to help fix this problem. The "-dmem -1" is the auto setting, setting it to "-dmem 0" is a good start as it switches off 'double memory mode' which might be causing your problem.
I'm sure there was a post that suggested 8GB of virtual memory PER CARD,  so 64GB should be fine for upto 8 cards
How to set virtual memory (AKA Swap File) in Windows 10 https://www.geeksinphoenix.com/blog/post/2016/05/10/how-to-manage-windows-10-virtual-memory.aspx

[invicta]

I just wanted to add that I'm suffering issues with Pitcairn based cards (270/270X), they seem fine on 10.2 but get incorrect shares, on 9.7 they are fine but hash slower and run hotter. As they are part of other mixed rigs I've just run them on 10.2 anyway but I'd rather not be wasting shares. I am at the stage now where all my spare cards are in use, I could deal with losing a bit of hashrate if they run cooler and stable on 10.2. The obvious solution is to buy newer RX cards but why waste what is still a very powerful piece of hardware and I'm not convinced that long-term buying more cards now is a smart move - I also found RX cards present their own issues.

If anyone has a temporary fix for Pitcairn cards please post it (other than using 9.7), I was looking at other miners but Claymore just seems simple, stable and easy to configure.

[garytheasshole]

I just wanted to add that I'm suffering issues with Pitcairn based cards (270/270X), they seem fine on 10.2 but get incorrect shares, on 9.7 they are fine but hash slower and run hotter. As they are part of other mixed rigs I've just run them on 10.2 anyway but I'd rather not be wasting shares. I am at the stage now where all my spare cards are in use, I could deal with losing a bit of hashrate if they run cooler and stable on 10.2. The obvious solution is to buy newer RX cards but why waste what is still a very powerful piece of hardware and I'm not convinced that long-term buying more cards now is a smart move - I also found RX cards present their own issues.

If anyone has a temporary fix for Pitcairn cards please post it (other than using 9.7), I was looking at other miners but Claymore just seems simple, stable and easy to configure.

Try xmr-stark-amd and sgminer

[invicta]

I just wanted to add that I'm suffering issues with Pitcairn based cards (270/270X), they seem fine on 10.2 but get incorrect shares, on 9.7 they are fine but hash slower and run hotter. As they are part of other mixed rigs I've just run them on 10.2 anyway but I'd rather not be wasting shares. I am at the stage now where all my spare cards are in use, I could deal with losing a bit of hashrate if they run cooler and stable on 10.2. The obvious solution is to buy newer RX cards but why waste what is still a very powerful piece of hardware and I'm not convinced that long-term buying more cards now is a smart move - I also found RX cards present their own issues.

If anyone has a temporary fix for Pitcairn cards please post it (other than using 9.7), I was looking at other miners but Claymore just seems simple, stable and easy to configure.

Try xmr-stark-amd and sgminer

Thanks, I read up on that but also read conflicting information on stability and SGMiner not being in development any more and XMR-STAK-AMD not being supported on Nicehash. I could be wrong about all this but concluded that the time I spend fiddling with the machines and time offline might be offset by the shares I'm losing due to being incorrect.

Also on another note, are the Blockchain drivers better for older cards - 200/300 series? My R9 380 have seen a slowdown on ETH to about 17MH/s from 20MH/s few months back. I could try them but am reluctant to fiddle if it's stable and working.

Thanks

[pehoko]

I don't see any difference in speed with blockchain driver and Crimson 15.12 with my old cards 79xx, 380's. Even with blockchain driver on some of cards were missing settings like powerune in AB, so I am sticking with 15.12.

[carlo_0000]

last msi afterburner works with blockchain driver   but speed on r9 series won't change
but not working on win7

but stay on 9.7
i tested xmr stak but not stable and not faster, even slower on some model , did not find any good setting
also not good on rx460-560

[a1unicorn]

Is anyone else having 'GPU ## found incorrect share" errors using this miner w/ Nicehash ?

Probably around 10% of my shares are incorrect. Changing the '-h' value doesn't make it better nor worse.

I'm using Radeon R9 280x's with 16gb virtual memory, and "-h 700 -dmem 1".

[carlo_0000]

Is anyone else having 'GPU ## found incorrect share" errors using this miner w/ Nicehash ?

Probably around 10% of my shares are incorrect. Changing the '-h' value doesn't make it better nor worse.

I'm using Radeon R9 280x's with 16gb virtual memory, and "-h 700 -dmem 1".

r9 series need to stay on 9.7, they bug on 10.x   except the 390

[pehoko]

Agree, I didn't find the way to work 10.x with older cards.

[a1unicorn]

r9 series need to stay on 9.7, they bug on 10.x   except the 390

Agree, I didn't find the way to work 10.x with older cards.

I updated to the new Nicehash Legacy 1.8.1.5, which has the option to switch to Claymore's Cryptonight v9.7.

Running 9.7, everything seems to work fine now.

Thanks!

[invicta]

Is anyone else having 'GPU ## found incorrect share" errors using this miner w/ Nicehash ?

Probably around 10% of my shares are incorrect. Changing the '-h' value doesn't make it better nor worse.

I'm using Radeon R9 280x's with 16gb virtual memory, and "-h 700 -dmem 1".

Yes, this is the problem I mentioned above. As Carlo said, it's not flawless on older R9 cards, specifically Pitcairn (78xx and 270) and Tahiti (280X, 79xx, etc.), I do find it works fine on the 285/380 (Tonga GCN 3rd series). 10.2 is important as my cards run a lot cooler with less power, but that might just be because they're churning out rubbish. I might rebuild my rigs and put all the older cards in one rig running 9.7 and all the newer, stable stuff into another and run 10.2 - sounds like a great plan but I bet I'm more likely to end up with everything broken...

[FFI2013]

Hi. Help please, I'm from Venezuela.

I have a rig of 470, 460 cards.

I use the v10.2 and blockchain drivers in win 10. Value -h not defined.

I receive many share rejected. Nicehash pool. Europe, USA, Brazil in all I receive a lot of "share rejected"

Excuse my bad English.

It's not claymore I get rejected shares and pool interrupts on sgminer and GG it's nicehash

[a1unicorn]

Yes, this is the problem I mentioned above. As Carlo said, it's not flawless on older R9 cards, specifically Pitcairn (78xx and 270) and Tahiti (280X, 79xx, etc.), I do find it works fine on the 285/380 (Tonga GCN 3rd series). 10.2 is important as my cards run a lot cooler with less power, but that might just be because they're churning out rubbish. I might rebuild my rigs and put all the older cards in one rig running 9.7 and all the newer, stable stuff into another and run 10.2 - sounds like a great plan but I bet I'm more likely to end up with everything broken...

Interesting that your cards run significantly cooler on 10.2. I haven't noticed any difference in temperatures and both versions of the miner run very cool: I get temps of 50-60C with my fans at 45%. Hashrate is 2020h/s running 4x R9 280x's.

[invicta]

Yes, this is the problem I mentioned above. As Carlo said, it's not flawless on older R9 cards, specifically Pitcairn (78xx and 270) and Tahiti (280X, 79xx, etc.), I do find it works fine on the 285/380 (Tonga GCN 3rd series). 10.2 is important as my cards run a lot cooler with less power, but that might just be because they're churning out rubbish. I might rebuild my rigs and put all the older cards in one rig running 9.7 and all the newer, stable stuff into another and run 10.2 - sounds like a great plan but I bet I'm more likely to end up with everything broken...

Interesting that your cards run significantly cooler on 10.2. I haven't noticed any difference in temperatures and both versions of the miner run very cool: I get temps of 50-60C with my fans at 45%. Hashrate is 2020h/s running 4x R9 280x's.

The 270/X Pitcairn cards were cooler by about 10C. My office is now so hot they run at about 65-70C at 100% fans on a good day. The hashrate is also better, about 440H/s vs 400 on 9.7. Obviously this is all a moot point if they're slinging out bad data all the time.

Cryptonote is also a lot cooler than Equihash I noticed.

Finally, the Beta Blockchain drivers on Win10 took my R9 380s from 17.7MH/s to 19.5MH/s in ETH as well as making them respond properly to Power Limit controls in MSI AB so they are slightly underclocked as ETH doesn't seem core speed sensitive on those cards, it is memory speed sensitive though.

[carlo_0000]

on my 380 2G there was no difference in speed with blockchain driver