Claymore's CryptoNote AMD GPU Miner v11.3

[Deepcleen]

I downloaded the newest v11.3 for windows and have been trying to mine Worktips on a couple different pools but I keep getting this error message, can anyone help me out with what is causing this ?

Share rejected (281 ms)!
{"id":4,"jsonrpc":"2.0","error":{"code":-1,"message":"lowdifficultyshare"}}

You may reduce the overclocking or the intensity.

[1714917504]

1714917504

[noreit]

I downloaded the newest v11.3 for windows and have been trying to mine Worktips on a couple different pools but I keep getting this error message, can anyone help me out with what is causing this ?

Share rejected (281 ms)!
{"id":4,"jsonrpc":"2.0","error":{"code":-1,"message":"lowdifficultyshare"}}

DOnt really think Claymore supports CN lite

[ustcstone]

I downloaded the newest v11.3 for windows and have been trying to mine Worktips on a couple different pools but I keep getting this error message, can anyone help me out with what is causing this ?

Share rejected (281 ms)!
{"id":4,"jsonrpc":"2.0","error":{"code":-1,"message":"lowdifficultyshare"}}

lowdifficultyshare usually means wrong algo

[UnclWish]

Stop to attract to SRB miner. It unstable in hash speed as hell! To get max speed for my 580 cards I relaunch it 5-10 times. Rebuilding kernel bins is also different story...
Claymore's miners are stable as rock! Fast starting, stable speed.
Plus SRB miner slower on old 2xx and 3xx cards.
If people didn't like Claymore's miners they didn't use them.

[Call_Me_Bambi]

Stop to attract to SRB miner. It unstable in hash speed as hell! To get max speed for my 580 cards I relaunch it 5-10 times. Rebuilding kernel bins is also different story...
Claymore's miners are stable as rock! Fast starting, stable speed.
Plus SRB miner slower on old 2xx and 3xx cards.
If people didn't like Claymore's miners they didn't use them.

Some people swear by one miner over another with almost religious fervour, I've used lots of different miners and use the one I feel happy with, be it Claymore, SRBminer or whatever, it sometimes comes down to a matter of individual preference, but one will never convince the fanatics - Die Heretic !

[UnclWish]

Stop to attract to SRB miner. It unstable in hash speed as hell! To get max speed for my 580 cards I relaunch it 5-10 times. Rebuilding kernel bins is also different story...
Claymore's miners are stable as rock! Fast starting, stable speed.
Plus SRB miner slower on old 2xx and 3xx cards.
If people didn't like Claymore's miners they didn't use them.

Some people swear by one miner over another with almost religious fervour, I've used lots of different miners and use the one I feel happy with, be it Claymore, SRBminer or whatever, it sometimes comes down to a matter of individual preference, but one will never convince the fanatics - Die Heretic !

I use SRB miner right now. But it doesn't means that it's the best one. If Claymore returns to develope CN miner it can do best of them. That's why we here. I don't know what you're doing here...

[etsRX]

Hello!

Can U mine Cryptonight Heavy w/ this miner?

[UnclWish]

Hello!

Can U mine Cryptonight Heavy w/ this miner?

No. That's why we asking Claymore to update his miner.

[dingdongtobias]

Stop to attract to SRB miner. It unstable in hash speed as hell! To get max speed for my 580 cards I relaunch it 5-10 times. Rebuilding kernel bins is also different story...
Claymore's miners are stable as rock! Fast starting, stable speed.
Plus SRB miner slower on old 2xx and 3xx cards.
If people didn't like Claymore's miners they didn't use them.

sorry to drop in
i have 380, 470, 480, 570, 580 4&8 MB cards and never had to relaunch srb 5-10 times, it always made 1 .srb file for each of cards, i see people say it creates a .srb file on every launch, what version does that?

stability is also good, never got freeze or lockups, i am running it on windows 10 x64 v1703 with blockchain drivers :

https://pasteboard.co/Hp4Y0mS.jpg

[Call_Me_Bambi]

Unable to get -cvddc to work, any help, thanks.

Running Windows 10 Pro (x64) 1803, latest AMD drivers.
Monitoring GPU core voltage with 'HwInfo64'.

I have a small rig with two RX470 (one 4GB and one 8GB, bios modded) and can't get -cvddc to reduce the core voltage, no matter what I set it to it will not go lower than 988mV.
Now if I use MSI Afterburner to reduce the core voltage it works, if I set the core voltage to -25mV (both cards) Hwinfo64 will show the voltage drop from 988mV to 963mV, but Claymore's -cvddc does nothing ?
I've been using AB until now to reduce the core voltage but thought I'd give Claymore's option a try but with no success, I've just updated Windows to 1803 so I'm wondering if this is the problem.
Getting between 880-900 h/s with these cards so I hate to have to roll-back Windows to 1703 in case it all goes horribly wrong.

My Command Line:

Code:

NsGpuCNMiner -xpool ssl://europe.cryptonight-hub.miningpoolhub.com:20580 -xwal user.worker -xpsw x -pow7 1 -ftime 5 -mport 0 -r 1 -h 1024,896 -cvddc 970,970

[UnclWish]

Unable to get -cvddc to work, any help, thanks.

Running Windows 10 Pro (x64) 1803, latest AMD drivers.
Monitoring GPU core voltage with 'HwInfo64'.

I have a small rig with two RX470 (one 4GB and one 8GB, bios modded) and can't get -cvddc to reduce the core voltage, no matter what I set it to it will not go lower than 988mV.
Now if I use MSI Afterburner to reduce the core voltage it works, if I set the core voltage to -25mV (both cards) Hwinfo64 will show the voltage drop from 988mV to 963mV, but Claymore's -cvddc does nothing ?
I've been using AB until now to reduce the core voltage but thought I'd give Claymore's option a try but with no success, I've just updated Windows to 1803 so I'm wondering if this is the problem.
Getting between 880-900 h/s with these cards so I hate to have to roll-back Windows to 1703 in case it all goes horribly wrong.

My Command Line:

Code:

NsGpuCNMiner -xpool ssl://europe.cryptonight-hub.miningpoolhub.com:20580 -xwal user.worker -xpsw x -pow7 1 -ftime 5 -mport 0 -r 1 -h 1024,896 -cvddc 970,970

Why nobody dasn't allowes that HWInfo can read sensors wrong or with bugs due to new AMD driver's specifics?

[notbatman]

Set the memory voltage to 875 in the bios mod for rx570 cards if the software is being stubborn.

[Call_Me_Bambi]

Set the memory voltage to 875 in the bios mod for rx570 cards if the software is being stubborn.

I rolled-back to Windows 1703 and it made no difference at all. So I'll have a go a burning the voltage into the BIOS, not something I like doing as if it doesn't work it's more work to fix than just changing a number in a line of code.

[dirtypaws]

Hello, may I ask a question which is more script / batch file related.  I run Claymore on CPU under winpe, I have alot of hardware from different years and I point them all to a pool, it's common to often be 25KHS, I made it all automated and they boot my script from my winpe image.  Now the problem comes in the fact I have different hardware from the last 5 years upto current day Xeons, I want it to be automated and run on the currect number of threads (leaving it to default is not ideal, I like to utilise around 80% only).

Onto my question, in winpe I can pull the level3cache with wmic (wmic cpu get l3cachesize), there a way the output of this command into my claymore switch options?  It would be ideal since I could leave all my machines to Pxeboot and run the most optimal thread count (cache /2). 

Thank you.

[altsay]

I just build a new rig today, R9 280x and a fresh driver Adrenaline 18.5.2. Now this happens:

Code:

C:\Claymore>NsGpuCNMiner.exe  -pow7 1 -xpool ssl://us-east.cryptonight-hub.miningpoolhub.com:20596 -xwal account.worker -xpsw x

╔════════════════════════════════════════════════════════════════╗
║           Claymore's CryptoNote AMD GPU Miner v11.3            ║
╚════════════════════════════════════════════════════════════════╝

XMR: 2 pools are specified
Main Monero pool is us-east.cryptonight-hub.miningpoolhub.com:20596

C:\Claymore>

What might be the reason?

[Call_Me_Bambi]

I just build a new rig today, R9 280x and a fresh driver Adrenaline 18.5.2. Now this happens:

Code:

C:\Claymore>NsGpuCNMiner.exe  -pow7 1 -xpool ssl://us-east.cryptonight-hub.miningpoolhub.com:20596 -xwal account.worker -xpsw x

╔════════════════════════════════════════════════════════════════╗
║           Claymore's CryptoNote AMD GPU Miner v11.3            ║
╚════════════════════════════════════════════════════════════════╝

XMR: 2 pools are specified
Main Monero pool is us-east.cryptonight-hub.miningpoolhub.com:20596

C:\Claymore>

What might be the reason?

I tested your configuration and it run OK, no problems. Since this is a new build one thing to look out for is Windows Defender deleting 'NsGpuCNMiner.exe', as it usually does, unless added to exeptions.

[hieunguyen]

Stop to attract to SRB miner. It unstable in hash speed as hell! To get max speed for my 580 cards I relaunch it 5-10 times. Rebuilding kernel bins is also different story...
Claymore's miners are stable as rock! Fast starting, stable speed.
Plus SRB miner slower on old 2xx and 3xx cards.
If people didn't like Claymore's miners they didn't use them.

Because it does not cryptonight lite v7 and cryptonight heavy ... and it is not updated anymore

[UnclWish]

I just build a new rig today, R9 280x and a fresh driver Adrenaline 18.5.2. Now this happens:

Code:

C:\Claymore>NsGpuCNMiner.exe  -pow7 1 -xpool ssl://us-east.cryptonight-hub.miningpoolhub.com:20596 -xwal account.worker -xpsw x

╔════════════════════════════════════════════════════════════════╗
║           Claymore's CryptoNote AMD GPU Miner v11.3            ║
╚════════════════════════════════════════════════════════════════╝

XMR: 2 pools are specified
Main Monero pool is us-east.cryptonight-hub.miningpoolhub.com:20596

C:\Claymore>

What might be the reason?

Look, what miner writes in log file.

[citronick]

Hi Claymore - would you consider VEGA basic optimization support for the miner? Thanks

===
Make sure you defined GPU_MAX_ALLOC_PERCENT 100
Be careful with overclocking, use default clocks for first tests
Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools
OpenCL initializing...
AMD Cards available: 2
GPU #0: gfx900 (Radeon RX Vega), 8176 MB available, 56 compute units (pci bus 3:0:0)
GPU #0 recognized as Vega
GPU #1: gfx900 (Radeon RX Vega), 8176 MB available, 56 compute units (pci bus 6:0:0)
GPU #1 recognized as Vega
POOL version
GPU #0 algorithm ASM, -h 3072, -dmem 0 (Memory used: 6297MB)
GPU #0 - NOTE: this miner is not optimized for Vega
GPU #1 algorithm ASM, -h 3072, -dmem 0 (Memory used: 6297MB)
GPU #1 - NOTE: this miner is not optimized for Vega
Total cards: 2
"-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
Watchdog enabled
Monero Pow7 algorithm enabled
XMR: Stratum - connecting to 'xmr-asia1.nanopool.org' <139.99.101.197> port 14444 (unsecure)
Remote management (READ-ONLY MODE) is enabled on port 3333
===

[Beyerd17]

Stop to attract to SRB miner. It unstable in hash speed as hell! To get max speed for my 580 cards I relaunch it 5-10 times. Rebuilding kernel bins is also different story...
Claymore's miners are stable as rock! Fast starting, stable speed.
Plus SRB miner slower on old 2xx and 3xx cards.
If people didn't like Claymore's miners they didn't use them.

Some people swear by one miner over another with almost religious fervour, I've used lots of different miners and use the one I feel happy with, be it Claymore, SRBminer or whatever, it sometimes comes down to a matter of individual preference, but one will never convince the fanatics - Die Heretic !

It's a matter of personal taste, some prefer the GUI of Claymore and some just don't. Personally I prefer Claymore over the others.