|
Those of you on Windows 10 getting random shutdowns do this:
Right click start. bat file - properties - options - uncheck QuickEdit Mode - apply - ok
What happens is a window like control panel, Windows defender or task manager comes up and the console freezes. Then the window goes away Claymore resumes and uh oh! Looks like our GPUs failed. But they didnt. Fall creator update did this not Claymore.
While you're in there increase the font size and make it bold.
|
|
|
|
Same here, it worked good at the begging and then it started to fluctuate (3 rigs on 11.5 oldknrl rest on 11.4)  Click in "effective current hashrate" to remove it and you will get better resolution for the other two. Try closing gpuz or hwmonitor. |
|
|
|
|
AMD cards that are BIOS modded definitely use oldkernels
AMD cards that are overclocked right on the edge might need oldkernels
Go ahead and try new kernels. With everything the same as before. If theres any instability or increase in rejected/incorrect do not bother underclocking just go straight to oldkernels.
The main difference between the two I've found is you don't get the fluctuating hash rate with the newer ones. So if you can get away using them do it.
That's my story and I am sticking to it.
|
|
|
|
|
Still getting stale shares on ethermine. It's worse during the day which makes me think its their server
Also I'm getting 1% incorrect shares. Does not seem to go down with lowering clocks.
Still some fluctuation in speed too. Bios nodded rx580s using oldkernels on windows. Each card will drop 3% to 5% randomly for a short period of time.
Edit: stale shares correlates to when the rig current effective hashrate drops. It is only 63mhs. So this makes sense. Pings are 40 to 60 ms. I bet if I add some horsepower the stales disappear.
|
|
|
|
This script can help to users who wants to use versions of Claymore which will be less then version where this new feature will be implemented.
Yes a very smart way of doing it! For those who don't understand you can run different coins AND different versions of claymore. |
|
|
|
I have 4 rigs that have MSI RX 570 Armor cards and 4 with other brand cards, when i upgrade claymore to 11.4 from 11 at least 3 of the cards on each of the MSI card rigs fail.
1 x MSI rig is using 6 x RX570 4GB = Cards stop mining 11.4 on linux, 1500 straps bios
3 x MSI rigs are 18 x RX570 8GB = Cards stop mining with 11.4 on linux, standard bios
4 x Rigs with mix of RX570 Nitro+, Gigabyte RX570, RX570 Pulse on 11.4 on linux = mining fine with not a single card stopping.
Very odd that its just the MSI Armor cards, only one else seeing this?
Is everyone getting the same hashrate increase with 11.5 using the oldkernals?
Thanks
If your bios is stock you shouldn't have to use oldkernels. Try it both ways and let us know. |
|
|
|
|
I think the problem is ethermine servers.
|
|
|
|
Hi guys,
I just cannot get it in dual mining that ETH have same rate like the claymore said on the first page.
"Supports new "dual mining" mode: mining both Ethereum and Decred/Siacoin/Lbry/Pascal at the same time, with no impact on Ethereum mining speed. Ethereum-only mining mode is supported as well."
I try to dual mine ETH/PASC but hash rate for ETH falls down from 28 to 18.
Somebody got some explanation?
Thank you
Yes you need to manually set dcri. Hit the - as it's mining. This will increase ETH rate and decrease the second coin. You may want to split different dcri numbers between your cards. After you have settled on what you want you can do the dcri in the bat file. |
|
|
|
|
You guys on ethermine have you had any stales from 1030pm central to 130am central?
|
|
|
|
|
So in a perfect world effective hash rate would be 2% lower than reported on ethermine?
|
|
|
|
|
That's one expensive 550w heater
|
|
|
|
Cheers. Question (off topic) whats the performance like with dual mining ETH + Keccak using your 580s? Been thinking about ETH + BLAKE2S... but not sure which combo would suit best with these cards.
Hot and cranky! Msi rx580 bios flashed 8gb micron Card 1: 32.2 ETH/193 KEC/dcri 6/137 watts/1200 core/2209 memory Card 2: 30.8 ETH/215 KEC/dcri 7/132 watts/1215 core/2216 memory If you are dual mining with keccak start with dcri at 6 and try some of the slower cards at 7. Your fast cards will be unstable at 7 and all will be at 8. I use the nicehash keccak server at keccak.usa.nicehash.com:3338. Just give it your bitcoin address and go to town. If you want smartcoin they have their own pools but you need to set up with them. |
|
|
|
Been running 10.6....has been rock solid. bit the bullet and moved to 11.5 and hash improvements 3.5 mhs per rig...(better than nothing)..
rig 1 x6 580s
rig 2 x6 580s
i forgot to add -oldkernal 1 initially and got a stack of memory errors...and the errors dramatically reduced when -oldkernal 1 was added and hash rate stayed the same.
just notices some instability with the hash rates..jumps to and from 173-181 a fair bit....
my current config:
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
EthDcrMiner64.exe -epool eth-asia1.nanopool.org:9999 -ewal xxx.rig1/xxx -epsw x -mode 1 -ftime 10 -oldkernels 1
any help would be fantastic.
thanks.
cheers
I too have noticed some fluctuation. 3 to 5% per card. I have bios modded rx580s. Very stable though. I am dual mining keccac. 0 rejected and incorrect. Some stale on keccac none on ETH. Hit Z to have it auto tune in mode 1. |
|
|
|
I am using now the latest but a little bit confusion about the -dcri value in the previous version the miner is not asking that thing, oh by the way what is exactly work of dcri and what is the best value to put? I am using rx 570 cards mixed with 4 and 8gb memory
GPU #0: apply best detected -dcri value: 12
GPU0 t=58C fan=0%, GPU1 t=53C fan=66%, GPU2 t=49C fan=0%, GPU3 t=51C fan=0%, GPU4 t=49C fan=0%, GPU5 t=51C fan=0%, GPU6 t=53C fan=0%, GPU7 t=51C fan=54%, GPU8 t=58C fan=0%, GPU9 t=57C fan=0%, GPU10 t=52C fan=0%, GPU11 t=58C fan=0%
GPU #1: apply best detected -dcri value: 6
GPU #2: apply best detected -dcri value: 8
GPU #3: apply best detected -dcri value: 6
GPU #4: apply best detected -dcri value: 8
GPU #5: apply best detected -dcri value: 8
GPU #6: apply best detected -dcri value: 8
GPU #7: apply best detected -dcri value: 8
GPU #8: apply best detected -dcri value: 12
GPU #9: apply best detected -dcri value: 8
GPU #10: apply best detected -dcri value: 8
GPU #11: apply best detected -dcri value: 10
Automatic detection of best -dcri values completed
P.S
Is it necessary to put the -oldkernels value? Kindly need some help.
Thanks
If you are single mining perfect! If you want to enter them in the bat file that will save time. They will not change unless you start dual mining. Only apply oldkernels if you have instability or lots of rejected shares. Try it either way. It will be slower with it applied. |
|
|
|
I just switched a rig over from ETC+XVG (blake2s) to ETC+SMART (keccak).
But my ETC hashrate on RX580s went from 31 mh/s down to 11 mh/s with keccak as 2nd coin.
Obviously this isn't going to work for me.
Anyone else seeing this with keccak as 2nd coin?
Try dcri of 6 7 will get you a bit more keccak but more heat and instability Play with it. Don't be afraid to have the "hotter" GPUs at 6 and the cooler more stable ones at 7 |
|
|
|
|
It dropped after putting it in a different computer? Try:
- update windows 10
- set card to compute
- what mining software?
|
|
|
|
smartcash more profitable than verge ?
Yes I am using the nicehash keccak pool so you have to account for that too. I think that is the best way to go. Keccak profit will disappear once Nicehash upgrades to Claymore 11.x |
|
|
|
Whats ur 2nd coin you mine using keccak if dont mind me asking? I was mining Pascal but it is going down the drain...
all dual coins are dead, mine eth only. Says who? It all depends on the situation. I pay 10 cents CAD per kwhr for power. If I mine smartcash it pays the whole power bill for that card and then some. |
|
|
|
i noticed. thanks. gosh, i was spoiled by higher hashrate already with the new kernels. using old kernels, hashrate swings are noticeable (i dont know if its because my oc has been messed up) and of course the little decrease in hashrate. guess what, i came back deleting -oldkernels parameter and enjoy higher hashrate, i'll just readjust mclocks whenever incorrect share is logged. cant go back to old hashrates/kernels anymore.  atleast we now have options to revert back to old kernels without downgrading. thanks sir You may not get improvement with lower clocks. Do you have modified ram timing straps? When I get home I will compare stock bios with new kernel vs modified bios with old kernel in 11.5 really? isn't it the reported hashrate is an indication of speed? as long as you get no hwinfo errors and incorrect shares? I had 4% incorrect shares no matter how much I slowed down in 11.x Plus instability. It's all gone with 11.5 running old kernels |
|
|
|
i noticed. thanks. gosh, i was spoiled by higher hashrate already with the new kernels. using old kernels, hashrate swings are noticeable (i dont know if its because my oc has been messed up) and of course the little decrease in hashrate. guess what, i came back deleting -oldkernels parameter and enjoy higher hashrate, i'll just readjust mclocks whenever incorrect share is logged. cant go back to old hashrates/kernels anymore. atleast we now have options to revert back to old kernels without downgrading. thanks sir You may not get improvement with lower clocks. Do you have modified ram timing straps? When I get home I will compare stock bios with new kernel vs modified bios with old kernel in 11.5 |
|
|
|
|
Show Posts
