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

laik2

sr. member

Activity: 652

Merit: 266

Quote from: Xazax310 on June 12, 2019, 07:24:49 AM

So I have Sapphire Nitro RX470 4GB's(Samsungs) I noticed my Max hashrate caps out at 31.8Mh/s No matter how high I put the memory overclock. I unlocked my BIOs to allow 2250 memory overclock for 4GB cards. However no matter what straps, 1-6 I tried, and memory speed from 2150-2250 the max hashrate is 31.8mh/s.

Does anyone have any idea's? is this just the limit for Claymore software implementation? Not saying it's awful but this Samsungs look like they can do much more!

Your cards are core limited, you need to bump core, thus increase voltage and wattage too.

Xazax310

member

Activity: 246

Merit: 24

So I have Sapphire Nitro RX470 4GB's(Samsungs) I noticed my Max hashrate caps out at 31.8Mh/s No matter how high I put the memory overclock. I unlocked my BIOs to allow 2250 memory overclock for 4GB cards. However no matter what straps, 1-6 I tried, and memory speed from 2150-2250 the max hashrate is 31.8mh/s.

Does anyone have any idea's? is this just the limit for Claymore software implementation? Not saying it's awful but this Samsungs look like they can do much more!

TheHas

full member

Activity: 616

Merit: 167

Quote from: ivanpop on June 09, 2019, 05:20:06 PM

I have 6 1070's on a rig with h81 pro btc and g1820. After 15-30min the cpu goes to 100% and the rig becomes unresponsive. Some of the cards start mining with 4-5mh and I start to get rejected shares. I'm using MSI AB to overclock my cards. Task manager reports System, System interrupts, EthDcrMiner64.exe or MSI AB maxing out the cpu.

A few people have been having similar issues - myself included. Haven't managed to find a solution yet. It might be hardware related, like insufficient ram for that many GPU's to maintain being run at max capacity from straps? Only speculating.

In short though, I'm in the same position as you and if I find a solution I'll post here or PM you.

bategojko74

member

Activity: 220

Merit: 12

Quote from: arianx on June 12, 2019, 02:35:23 AM

i get 32.8 per card. how can i get better? Grin

Flash your current straps to the bios and use Phoenix miner.You will get between 32.9 and 33.1.

ShowMeCoins

member

Activity: 129

Merit: 11

Quote from: biospb on June 11, 2019, 07:39:31 AM

Hi, Claymore

the bug with P104 on linux with 418 & 430 drivers still present.
please fix it. the last working version is 11.9.
miner kills itself after starting to create gpu buffer

Second that.
ETC-mining, using 418.56 drivers

Guigs321

newbie

Activity: 41

Merit: 0

Quote from: arianx on June 12, 2019, 02:35:23 AM

i get 32.8 per card. how can i get better? Grin

http://uupload.ir/files/bg0j_eth.jpg

32,91 Mh/s Tongue

arianx

newbie

Activity: 3

Merit: 0

i get 32.8 per card. how can i get better? Grin

http://uupload.ir/files/bg0j_eth.jpg

darkCryptoMiner

newbie

Activity: 30

Merit: 0

Quote from: blytz on June 11, 2019, 05:39:44 AM

I might be doing something wrong but the latest radeon drivers (19.6.1) have halved the mining rate of my Vega 56 but not changed the rate of my RX580.

Any ideas anyone ?

Make sure you are running compute mode on the rx580

-y enables Compute Mode and disables CrossFire for AMD cards. "-y 1" works as pressing "y" key when miner starts. This option works in Windows only.

biospb

newbie

Activity: 64

Merit: 0

Quote from: Claymore on June 11, 2019, 03:37:04 PM

It seems drivers are unstable at this number of cards.
If 11.9 works fine you can try to add "-eres 2" option, miner will use old-style DAG generation (since v12 it tries to reduce GPU memory used for DAG in most cases, non-zero "-eres" option value disables it).

yes! -eres 2 make it work! only LA is relatively high. but anyway thanks for advise!!!

btw, in first post it is written that it is default option:

Quote

-eres this setting is related to Ethereum mining stability. Every next Ethereum epoch requires a bit more GPU memory, miner can crash during reallocating GPU buffer for new DAG.
To avoid it, miner reserves a bit larger GPU buffer at startup, so it can process several epochs without buffer reallocation.
This setting defines how many epochs miner must foresee when it reserves GPU buffer, i.e. how many epochs will be processed without buffer reallocation. Default value is 2.

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: biospb on June 11, 2019, 03:16:04 PM

Quote from: Claymore on June 11, 2019, 02:29:54 PM

Thanks, I had a good laugh here

Unfortunately, I don't have 13 p104 cards to test it. So 12 cards work fine and 13 fail, right? There is no difference for miner if you use 12 or 13 cards so it must be something else, try "-gser 2" option to see if it helps.

hmm, yes. 12 cards are working. you definitely do not like this number)
and 13 with with -gser 2 option, too. but very slow startup.
with -gser 1 does not. and I found in syslog this

Code:

[27382.925779] Out of memory: Kill process 10880 (ethdcrminer64) score 684 or sacrifice child
[27382.925822] Killed process 10880 (ethdcrminer64) total-vm:321404352kB, anon-rss:1346268kB, file-rss:1308172kB, shmem-rss:133120kB
[27382.948105] oom_reaper: reaped process 10880 (ethdcrminer64), now anon-rss:0kB, file-rss:1313400kB, shmem-rss:133120kB

sorry, forgot to take a look there earlier
hope this help to trace the problem
v11.9 also works without -gser.

It seems drivers are unstable at this number of cards.
If 11.9 works fine you can try to add "-eres 2" option, miner will use old-style DAG generation (since v12 it tries to reduce GPU memory used for DAG in most cases, non-zero "-eres" option value disables it).

biospb

newbie

Activity: 64

Merit: 0

Quote from: Claymore on June 11, 2019, 02:29:54 PM

Thanks, I had a good laugh here

Unfortunately, I don't have 13 p104 cards to test it. So 12 cards work fine and 13 fail, right? There is no difference for miner if you use 12 or 13 cards so it must be something else, try "-gser 2" option to see if it helps.

hmm, yes. 12 cards are working. you definitely do not like this number)
and 13 with with -gser 2 option, too. but very slow startup.
with -gser 1 does not. and I found in syslog this

Code:

[27382.925779] Out of memory: Kill process 10880 (ethdcrminer64) score 684 or sacrifice child
[27382.925822] Killed process 10880 (ethdcrminer64) total-vm:321404352kB, anon-rss:1346268kB, file-rss:1308172kB, shmem-rss:133120kB
[27382.948105] oom_reaper: reaped process 10880 (ethdcrminer64), now anon-rss:0kB, file-rss:1313400kB, shmem-rss:133120kB

sorry, forgot to take a look there earlier
hope this help to trace the problem
v11.9 also works without -gser.

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: biospb on June 11, 2019, 01:26:33 PM

Quote from: ustcstone on June 11, 2019, 09:44:58 AM

That's a lot of p104s....

Shhh! He do not like this number

Thanks, I had a good laugh here

Unfortunately, I don't have 13 p104 cards to test it. So 12 cards work fine and 13 fail, right? There is no difference for miner if you use 12 or 13 cards so it must be something else, try "-gser 2" option to see if it helps.

biospb

newbie

Activity: 64

Merit: 0

Quote from: ustcstone on June 11, 2019, 09:44:58 AM

Quote from: biospb on June 11, 2019, 07:39:31 AM

https://postimg.cc/XrY10Fws

That's a lot of p104s....

Shhh! He do not like this number

ustcstone

newbie

Activity: 49

Merit: 0

Quote from: biospb on June 11, 2019, 07:39:31 AM

Hi, Claymore

the bug with P104 on linux with 418 & 430 drivers still present.
please fix it. the last working version is 11.9.
miner kills itself after starting to create gpu buffer
https://postimg.cc/XrY10Fws

That's a lot of p104s....

biospb

newbie

Activity: 64

Merit: 0

Hi, Claymore

the bug with P104 on linux with 418 & 430 drivers still present.
please fix it. the last working version is 11.9.
miner kills itself after starting to create gpu buffer
https://postimg.cc/XrY10Fws

blytz

newbie

Activity: 3

Merit: 0

I might be doing something wrong but the latest radeon drivers (19.6.1) have halved the mining rate of my Vega 56 but not changed the rate of my RX580.

Any ideas anyone ?

ManDoneKTM

newbie

Activity: 150

Merit: 0

Quote from: imenno on June 10, 2019, 03:30:09 AM

Quote from: ivanpop on June 09, 2019, 05:20:06 PM

I have 6 1070's on a rig with h81 pro btc and g1820. After 15-30min the cpu goes to 100% and the rig becomes unresponsive. Some of the cards start mining with 4-5mh and I start to get rejected shares. I'm using MSI AB to overclock my cards. Task manager reports System, System interrupts, EthDcrMiner64.exe or MSI AB maxing out the cpu.
https://i.imgur.com/eajKQYu.png

Or use OverdriveNTool instead of MSI AB

before you post bullsºººº , google more Wink

Xazax310

member

Activity: 246

Merit: 24

Quote from: imenno on June 10, 2019, 03:30:09 AM

Quote from: ivanpop on June 09, 2019, 05:20:06 PM

I have 6 1070's on a rig with h81 pro btc and g1820. After 15-30min the cpu goes to 100% and the rig becomes unresponsive. Some of the cards start mining with 4-5mh and I start to get rejected shares. I'm using MSI AB to overclock my cards. Task manager reports System, System interrupts, EthDcrMiner64.exe or MSI AB maxing out the cpu.

Or use OverdriveNTool instead of MSI AB

OverDriveNTool is for AMD ONLY. he has GTX1070 cards so like the other guy said use NVinspector. You need higher VM that could help, 6 GTX1070 8GB means you need to 6x8GB for VM 48GB. I typically set my VM around 55000mb.

imenno

newbie

Activity: 11

Merit: 0

Quote from: ivanpop on June 09, 2019, 05:20:06 PM

I have 6 1070's on a rig with h81 pro btc and g1820. After 15-30min the cpu goes to 100% and the rig becomes unresponsive. Some of the cards start mining with 4-5mh and I start to get rejected shares. I'm using MSI AB to overclock my cards. Task manager reports System, System interrupts, EthDcrMiner64.exe or MSI AB maxing out the cpu.
https://i.imgur.com/eajKQYu.png

Or use OverdriveNTool instead of MSI AB

MATHReX

sr. member

Activity: 861

Merit: 281

Quote from: ivanpop on June 09, 2019, 05:20:06 PM

I have 6 1070's on a rig with h81 pro btc and g1820. After 15-30min the cpu goes to 100% and the rig becomes unresponsive. Some of the cards start mining with 4-5mh and I start to get rejected shares. I'm using MSI AB to overclock my cards. Task manager reports System, System interrupts, EthDcrMiner64.exe or MSI AB maxing out the cpu.

Use Nvidia Inspector for OC, add Claymore miner to whitelist in Windows Defender.
Close all the apps that are not required in the background, virtual mem set to 20GB+ and give it a try again.

Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 114. (Read 6590757 times)