Topic: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free) - page 500. (Read 835461 times)

I think its is what you are looking for
https://tytanick.tinytake.com/sf/MTQ1NjExNF81MTY2NjY1

Quick question for OP, maybe it was already asked but did you ever consider adding the multi-algo nicehash miner ? 

if not mistaken, you can change this to MH from KH and vice-versa, in ethman utility in Claymore monitoring dashboard.

You are right, it's in MH/s!

Quick question. Did I just randomly lose my mind today, or did the Simplemining interface just start showing zcash mining with Claymore 12.4 in 'MH/s' instead of 'KH's'? It does in my interface for some reason.

At -dcri 80 I think they are pretty high. Like 1.5%.

I lowered mine but I may push it back up just because DCR price is so darn high.

I find suprnova no likey high DCRI when you start. Raise the DCRI gradually after the miner has been running for a few minutes. So start at 20 then go to 30, 40, etc.

If I started with a high DCRI on suprnova I get a dozen fast rejects and kicked from the server, then it tries again. (Not sure if this info helps you if you use HK pool but it might help you debug.)

hows the rejected shares on the decred hk pool?

Here is mine and its alive.

Dual mining is brutal on GPU and CPU, so lowest mining on ETH but maximum speed on DCR.

-dbg -1  -wd 1 -r 1 -mport -3333  -estale 1 -esm 1 -ethi 0  -epool asia1.ethpool.org:3333 -ewal .$rigName -esm 0 -epsw x -allpools 1 -mport -3333  -dpool stratum+tcp://decred.hk.nicehash.com:3354 -dwal .$rigName -dpsw x -dcoin dcr -dcri 80 -dcrt 1

Thank you. I tried it, but the problem persists: ETH mining is ok, but DCR shows "Job timeout" 

try this

1. remove "-mode 0"
2. replace "-dcoin decred"
3. add "-allpools 1" at the end of line

Thank you, reelen. I tried to copy/paste your settings and pools only replacing my wallets and workers, and it is still not workin: I hash ETH, but DCR gives me "Job Timeout"... I have even tried Claymore's default wallets and pools and I still have the same problem:

-epool us1.ethpool.org:3333 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F -epsw x -dpool stratum+tcp://yiimp.ccminer.org:4252 -dwal DsUt9QagrYLvSkJHXCvhfiZHKafVtzd7Sq4 -dpsw x -esm 1 -mode 0 -tt 70

This is so frustrating!  What am I doing wrong? Something related with my router or internet provider, perhaps?

Here are my settings if it helps (sorry don't have time to go through your bat lines, have to run):

-epool us2.ethermine.org:4444 -ewal .$rigName -epsw x -allpools 1 -wd 1 -r 1 -dpool dcr.suprnova.cc:2252 -dwal reelen1.$rigName -dpsw x -dcoin dcr -dcri 10

Hello guys, I have a question. While I am successful mining ETH or ZEC, I am totally unable to dual mine ETH + DCR. Probably is something very stupid I am missing in the options settings, but I am receiving constantly an error from the DCR pool:

“DCR: Job timeout, disconnect, retry in 20 sec...”

I am using the “claymore-eth v8.1” miner and I am introducing in the option lines settings like these:

-wd 1 -r 1 -epool eth.coinmine.pl:4000 -ewal myuser.myworker -epsw mypass -esm 2 -dpool stratum+tcp://dcr-us.coinmine.pl:2222 -dwal myuser.myworker -dpsw mypass -allpools 1 -mport -3333

-wd 1 -r 1 -epool eth-eu.dwarfpool.com:8008 -ewal MYWALLET -epsw x -dpool stratum+tcp://dcr-us.coinmine.pl:2222 -dwal myuser.myworker -dpsw mypass -mode 0 -dcoin dcr -allpools 1 -mport -3333

-wd 1 -r 1 -epool eth-eu.dwarfpool.com:8008 -ewal MYWALLET -epsw x -dpool dcr.suprnova.cc:2252 -dwal myuser.myworker -dpsw mypass -mode 0 -dcoin dcr -allpools 1 -mport -3333

Do you see something wrong that may explain it? :-(

Hi wolf.... -I 24?

any suggestions on -w and -g values ?

Hey T - I think some DCR mining action is good since DCR now is going to the moon.

I use the Pascal sgminer build and let my R9 Nanos and RX480s do the rest....


-k decred  -I 21 -w 64 -g 2  -o stratum+tcp://decred.hk.nicehash.com:3354 -u .$rigName  -p x  --text-only

Btw, I just copied the Pascal intensity settings and its working fine.... anyone knows what is best settings for DCR on sgminer?

I'll leave it like it is for now.
Will test on another motherboard when i have a chance. Last uptime for the rig was 18 hours without restart.

did you installed beta kernel and then beta amd driver?
if no, check it.

Results with these 2 settings added are same - nothing changed.
I'm using Jukebox bios for RX 480 Saph Nitro+ , goes to stable 29,8 MH/s in windows (28.9 MH/s in smOS) with no undervolting.

BUT
 * I made another test, i installed windows 7 on another partition on same harddrive, so to be sure that same hardware is used for correct testing. *
   Just to keep in mind that i'm using old motherboard for these 2 cards with only 1xPCI-e x16 and 1xPCI-e x1.

So results were:
I'm using the same driver under windows for all my rigs because its super stable with modded bioses , AMD 16.9.1.
When i installed the driver - miner is running stable with 29.8 with 1 card.
When i joined the 2nd card obviously with same driver - miner is showing that RAM on the graphic cards is 3GB each and not 8GB like it should be.
Well my concliusion is that this motherboard is splitting somehow the traffic between these 2 slots.
On windows miner is not starting at all, strange is that on smOS is working fine until GPU1 freeze.
So i'm pretty sure that for me its hardware problem with the PCI-e slots.

After I changed  PEG1 - Max Link Speed from [Gen1] back to [Auto], while leaving the two below changes in place, everything is running fine with 5 GPUs:

PEG0 - Max Link Speed: change from [Auto] to [Gen1]
Above 4G Decoding: [Disabled] to [Enabled]

As such, I am currently running two more GPUs with these two changes than I could run at the beginning of the night. I am hopeful I will be able to run cards off of all 7 PCIe slots with these settings once I get the necessary hardware to do so. I will keep you posted.

The main reason I provided all of the information in my previous post was that I hoped it would assist you with debugging the 300/300 problem others are experiencing. Once I have the necessary hardware to try and run 7 GPUs, I will report back.

On the other hand, if changing the one troublesome BIOS setting back to what caused the problems and then making the changes you suggested in your post would help you with identifying a larger problem, please let me know. I will be happy to oblige.


I am running the stock BIOS on my cards, at least for now. I figured it would be best first to get as many cards running as possible in stock form before I go monkeying with the cards' BIOS. That way, it is easier to track down the source of any problems that may crop up. Once I get everything running, I may modifying the memory timing, but that's the extent of my planned modding.