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

Is there now any way to watch mem errors on nvidia? Because straps brought all the pain from amd tuning, but at least amd reports mem errors which helps a lot to make rigs stable. Now I get to wait 20+ hours just to see one gpu in rig fail and try again.

Windows ONLY.. no linux version since v12... latest linux release is 6 month old..
Could you please upload the linux version ?

Claymore, remove please the space in the "Remote manager" folder name, it sometimes causes an error when opening over the network, thks.

14.5b good for polaris samsung vram, epila crash

Dual Mining of VBK would be awesome! I saw in other Forums user, who say it is currently also possible to run the Claymore Miner and another separat Veriblock Miner to Dual Mine this way but I never check/confirm it by myself. Any experience here?

Hey Mister Claymore, good job on picking up the slack on the miner now that profitability is going up again

Two suggestions:

1) clean up the OP (and the miner): there's a lot of irrelevant legacy stuff there now. Nobody dual-mines DCR or SIA with GPUs anymore. When you have time, I think it would be good to get rid of some of the clag.

2) (unless I missed it) you should enable VBK and/or other more relevant dual-mining coins/algos.

Thx

Will there be a Linux release soon?

not a typo and i have replied to him, obviously amds are crap with about 1/2 efficiency per watt

in nvidia inspector you can go as low as you wish, 650mV is not as low as it will go


However after the straps I have problem on two rigs, one card is crashing on each, I have even tried settings like this
-strap 1,1,6,1,1,1,1,1,1,1,1,1 -sintensity 100,100,2,100,100,100,100,100,100,100,100,100
-strap 1,1,0,1,1,1,1,1,1,1,1,1 -sintensity 100,100,0,100,100,100,100,100,100,100,100,100
and 0 mem OC, and even disable undervolting
then cards now gets about 20MHS and still crashes, while before with ethminer or phoenix both cards could get 23 or 22mhs undervolted overclocked

Well no rig is truly stable now, but that is expected while finding new OC values, best I got was 22h58m uptime while before the straps months

Maybe just first dead GPU, but so far these things were unkillable.

Any chances to use at the same time 2 miners? (for nvidia and amd)
Whenever use second window got next message:
So second window works only without strap command ;(

NVIDIA Inspector command line lets you go as low as 650mV. There are guides around the internet, look it up.

I am guessing its a typo and maybe he meant 935mV. I've tried different voltages and I think its impossible to be able to run it that low and even get Windows to load.

He might get lucky and have an extremely high ASIC quality however its not possible that 635mV would be enough to mine with.

With the RX 470/570, they generally need about 120 Watts (from the wall, not including cpu+ram+mobo) to run without hardware error or hangs. If you want it to use less power you need to mine an algo like XMR which uses like  100 Watts.

i need help, i have 2 mining rigs 1 with 3 rx 580 8gb and the other with 8 rx 580 8g also, claymore its working fine with the straps on the 1 with 3 cards, on the other with 8 cards keeps freezing after installing the driver, can anybody help out? 

Same here.. Seems to have happened after using -rxboost 1 while trying different -strap values. My RX580 hangs after starting the miner now. In fact, it hangs with any other miner as well. Tried -driver uninstall, and the driver was apparently uninstalled, but the card still hangs. Not sure what to do now.

What kind of bug was that? The Hashrate will drop to next to 0 after some time. Happens on some of my rigs already, no GPU crashed. Driver is 19.4.1, compute mode on. Use -rxboost 1 and -strap 1




21:01:39:019   6b4   ETH - Total Speed: 73.538 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:05
21:01:39:019   6b4   ETH: GPU0 14.945 Mh/s, GPU1 14.944 Mh/s, GPU2 14.953 Mh/s, GPU3 28.696 Mh/s
21:01:40:081   6b4   buf: {"id":0,"jsonrpc":"2.0","result":["0x5b93ccbeaf1615d5b55d7a2e1105331ea2e7cb8abc2780415398ceccf55f57c3","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}

21:01:40:081   6b4   ETH: 05/19/19-21:01:40 - New job from etp.2miners.com:9292
21:01:40:081   6b4   target: 0x000000007fd9a601 (diff: 8600MH), epoch 74(1.58GB)
21:01:40:081   6b4   ETH - Total Speed: 73.545 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:05
21:01:40:081   6b4   ETH: GPU0 14.945 Mh/s, GPU1 14.947 Mh/s, GPU2 14.957 Mh/s, GPU3 28.696 Mh/s
21:01:44:787   1e7c   em hbt: 16, fm hbt: 16,
21:01:44:787   1e7c   watchdog - thread 0 (gpu0), hb time 4703
21:01:44:787   1e7c   watchdog - thread 1 (gpu0), hb time 4312
21:01:44:787   1e7c   watchdog - thread 2 (gpu1), hb time 4359
21:01:44:787   1e7c   watchdog - thread 3 (gpu1), hb time 4703
21:01:44:787   1e7c   watchdog - thread 4 (gpu2), hb time 4703
21:01:44:787   1e7c   watchdog - thread 5 (gpu2), hb time 4359
21:01:44:787   1e7c   watchdog - thread 6 (gpu3), hb time 4312
21:01:44:787   1e7c   watchdog - thread 7 (gpu3), hb time 4703
21:01:44:949   6b4   sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x3480bbe", "0x000000000000000000000000000000000000000000000000000000005121eb8e"]}

21:01:45:094   6b4   buf: {"id":6,"jsonrpc":"2.0","result":true}

21:01:45:204   6b4   ETH: checking pool connection...
21:01:45:204   6b4   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:01:45:333   6b4   buf: {"id":3,"jsonrpc":"2.0","result":["0x5b93ccbeaf1615d5b55d7a2e1105331ea2e7cb8abc2780415398ceccf55f57c3","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}

21:01:49:491   1ea4   GPU0 t=47C fan=0%, GPU1 t=46C fan=0%, GPU2 t=46C fan=0%, GPU3 t=60C fan=42%
21:01:55:229   6b4   ETH: checking pool connection...
21:01:55:230   6b4   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:01:55:396   6b4   buf: {"id":3,"jsonrpc":"2.0","result":["0x5b93ccbeaf1615d5b55d7a2e1105331ea2e7cb8abc2780415398ceccf55f57c3","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}

21:02:04:975   6b4   sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x3f0b6b", "0x000000000000000000000000000000000000000000000000000000005121eb8e"]}

21:02:05:120   6b4   buf: {"id":6,"jsonrpc":"2.0","result":true}

21:02:05:265   6b4   ETH: checking pool connection...
21:02:05:265   6b4   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:02:05:411   6b4   buf: {"id":3,"jsonrpc":"2.0","result":["0x5b93ccbeaf1615d5b55d7a2e1105331ea2e7cb8abc2780415398ceccf55f57c3","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}

21:02:15:301   6b4   ETH: checking pool connection...
21:02:15:301   6b4   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:02:15:431   6b4   buf: {"id":3,"jsonrpc":"2.0","result":["0x5b93ccbeaf1615d5b55d7a2e1105331ea2e7cb8abc2780415398ceccf55f57c3","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}

21:02:17:520   1e7c   em hbt: 31, fm hbt: 0,
21:02:17:520   1e7c   watchdog - thread 0 (gpu0), hb time 3328
21:02:17:520   1e7c   watchdog - thread 1 (gpu0), hb time 8187
21:02:17:520   1e7c   watchdog - thread 2 (gpu1), hb time 8187
21:02:17:520   1e7c   watchdog - thread 3 (gpu1), hb time 3328
21:02:17:520   1e7c   watchdog - thread 4 (gpu2), hb time 3328
21:02:17:520   1e7c   watchdog - thread 5 (gpu2), hb time 8187
21:02:17:520   1e7c   watchdog - thread 6 (gpu3), hb time 8187
21:02:17:520   1e7c   watchdog - thread 7 (gpu3), hb time 3328
21:02:19:349   6b4   buf: {"id":0,"jsonrpc":"2.0","result":["0x3cd8fc592c3cb07cda97b393bb121129f6760ca49903959d2b87ecff4e47addc","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}

21:02:19:444   6b4   ETH: 05/19/19-21:02:19 - New job from etp.2miners.com:9292
21:02:19:444   6b4   target: 0x000000007fd9a601 (diff: 8600MH), epoch 74(1.58GB)
21:02:19:567   6b4   ETH - Total Speed: 4.121 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:05
21:02:19:698   6b4   ETH: GPU0 0.780 Mh/s, GPU1 0.780 Mh/s, GPU2 0.780 Mh/s, GPU3 1.782 Mh/s
21:02:19:845   1ea4   GPU0 t=50C fan=0%, GPU1 t=49C fan=0%, GPU2 t=49C fan=0%, GPU3 t=54C fan=33%
21:02:25:002   6b4   sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x3ecca2", "0x000000000000000000000000000000000000000000000000000000005121eb8e"]}

21:02:25:163   6b4   buf: {"id":6,"jsonrpc":"2.0","result":true}

21:02:25:337   6b4   ETH: checking pool connection...
21:02:25:337   6b4   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:02:25:483   6b4   buf: {"id":3,"jsonrpc":"2.0","result":["0x3cd8fc592c3cb07cda97b393bb121129f6760ca49903959d2b87ecff4e47addc","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}

21:02:32:702   6b4   buf: {"id":0,"jsonrpc":"2.0","result":["0x7c83633d401594ae85b51f8fc309491da4e6cf24131570112436c278574cf72c","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}

21:02:32:702   6b4   ETH: 05/19/19-21:02:32 - New job from etp.2miners.com:9292
21:02:32:702   6b4   target: 0x000000007fd9a601 (diff: 8600MH), epoch 74(1.58GB)
21:02:32:812   6b4   ETH - Total Speed: 4.142 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:06
21:02:32:957   6b4   ETH: GPU0 0.784 Mh/s, GPU1 0.784 Mh/s, GPU2 0.784 Mh/s, GPU3 1.791 Mh/s

nvidiainspector, but I think there is issue wit p2 states after claymore driver hack, I think undervolting no longer applies maybe, maybe p2 disable deactivation is why i'm having issue with cards even with -sintensity 0 and -strap 0 even when these same cards worked without issue before hack

I don't know why, but on some rigs I needed to disable force p2 state, on others not, and I have issue with one gpu on 2 rigs now, so maybe this?

EDIT: hmm so force p2 state for cuda is removed from new drivers, so that is not it

How are you able to set low voltage like that?
In my afterburner in curve editor voltage starts from 800mv, so there is probably a different way

Hmm, i'm still having crashes with nvidia gpus even when using strap 0, these gpus worked before (using ethminer) even with much higher clocks that what i'm trying now.

Does sintensity apply to strap 0 too?

Managed to fix it. I just reinstalled iGPU drivers (Intel VGA), now it works. 

whats ur command line? and what pool?

Hello,
Can anyone help me into this matter ?
I have played with different AMD drivers, between 18.6.1 and 19.4.1 on all my rigs, but on two of them i am stuck here:

https://imgur.com/a/A72fj9o

Also other miner software work without problems.
All that i did is using DDU to remove 19.4.1 and installed 18.6.1. I also tried to put back 19.4.1 and its the same, can't go further "Main ethereum pool is".