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

arielbit

legendary

Activity: 3444

Merit: 1061

Quote from: thesaltonsea on April 26, 2016, 05:39:12 AM

Even with lowered ethi , my rig is crashing and cant boot after that, its like that from the last 3-4 versions ... When we calculate the time that it is chrased and not mining for hours, the profit from the decred mining cant cover the so many hours downtime ... So the problem is not the ethi setting, maybe you changed something with the optimizations ?

you have to look elsewhere for other problems..if the miner is stable with other users there must be something in your system that causes that crashing or hanging etc..

focusing on the main players here...

-gpu temp (fan failure, dried thermal paste)

-power supply issue (defective, not enough power, loose connection, burned and slightly burned connections)

-and other pc components...HDD bad sector, failing RAM, CPU overheating etc..

mining pushes these components to the limits, running 24/7 specially this summer (people in hotter climates here)

kanoptx

sr. member

Activity: 406

Merit: 250

www.cryptocompare.com

Quote from: baykan on April 26, 2016, 06:48:18 AM

Quote from: Trimegistus on April 26, 2016, 01:10:27 AM

Quote from: baykan on April 25, 2016, 07:27:27 PM

With ethminer system is working without PC restarting, using Dual Miner is heating up the cards more ? because it's dual mining ?
May be I missed if somebody already mentioned this?

Dual mining significantly increases the workload on your video cards, therefore they will generate a lot more heat.

I will measure the temps with both miner and type here later.
Thank you for the info.

- My 5 card rig now working with ethminer.
Whenever I try with dual miner, during or after 2nd dag file generation PC restarts. I will place a fan tomorrow and retest.

which cards are you using btw?

baykan

full member

Activity: 133

Merit: 100

Quote from: Trimegistus on April 26, 2016, 01:10:27 AM

Quote from: baykan on April 25, 2016, 07:27:27 PM

With ethminer system is working without PC restarting, using Dual Miner is heating up the cards more ? because it's dual mining ?
May be I missed if somebody already mentioned this?

Dual mining significantly increases the workload on your video cards, therefore they will generate a lot more heat.

I will measure the temps with both miner and type here later.
Thank you for the info.

- My 5 card rig now working with ethminer.
Whenever I try with dual miner, during or after 2nd dag file generation PC restarts. I will place a fan tomorrow and retest.

qqqq

legendary

Activity: 1596

Merit: 1011

Any news about stratum implementation for solo ETH ?

restless

legendary

Activity: 1151

Merit: 1001

Quote from: Rux on April 26, 2016, 05:12:52 AM

claymore, i have 15.12 and my 2 x 280x on this new miner are mining aprox 11.6 mhs Sad

what to do?

Reboot.
Sometimes after start&stop miners several times cards got stuck into half-speed mode or whatever

Zitdadast

sr. member

Activity: 312

Merit: 250

LTC fan 4ever

Quote from: thesaltonsea on April 26, 2016, 05:39:12 AM

Even with lowered ethi , my rig is crashing and cant boot after that, its like that from the last 3-4 versions ... When we calculate the time that it is chrased and not mining for hours, the profit from the decred mining cant cover the so many hours downtime ... So the problem is not the ethi setting, maybe you changed something with the optimizations ?

Same here. My PC crashed several times. So I have to reduce the clock speed and the intensity again.

olajos

newbie

Activity: 46

Merit: 0

why is lowered ethi to 8? my miners was perfectly working on 16. even i have a slightly bigger hashrate with 16

thesaltonsea

newbie

Activity: 64

Merit: 0

Even with lowered ethi , my rig is crashing and cant boot after that, its like that from the last 3-4 versions ... When we calculate the time that it is chrased and not mining for hours, the profit from the decred mining cant cover the so many hours downtime ... So the problem is not the ethi setting, maybe you changed something with the optimizations ?

Rux

legendary

Activity: 1291

Merit: 1024

https://crypto.ba

Quote from: Claymore on April 26, 2016, 05:17:54 AM

Quote from: Rux on April 26, 2016, 05:12:52 AM

claymore, i have 15.12 and my 2 x 280x on this new miner are mining aprox 11.6 mhs Sad

what to do?

Did they mine faster on v3.2?

it was 21-22 mhs per card on 3.2...

gimme 5 min to download 3.2 and start build dag with it... will get back with results asap

EDIT: same :/

270 8,9 mhs

2 x 280x 11mhs

i dont know what to do? :/

EDIT2:

in this rig i have 2 x 280x, and 2 x 270 ... on last miner no problems, 270 hashing 14 mhs and 280x hashing 21mhs

after i tried this new miner i got 11 mhs and 8 mhs

Masked_Immortal

member

Activity: 67

Merit: 10

is it possible to specify cards by name?
it seems different order between msi afterburner and miner

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: Rux on April 26, 2016, 05:12:52 AM

claymore, i have 15.12 and my 2 x 280x on this new miner are mining aprox 11.6 mhs Sad

what to do?

Did they mine faster on v3.2?

Rux

legendary

Activity: 1291

Merit: 1024

https://crypto.ba

claymore, i have 15.12 and my 2 x 280x on this new miner are mining aprox 11.6 mhs Sad

what to do?

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: Gagana on April 26, 2016, 04:47:02 AM

The only one rig has this problem.

If I start it without "-allpools 1" option it can't connect to devfee pool and exits. If I start it with this option, then it starts, gets jobs but doesdidn't send the results back. I see in the log file:

Code:

12:29:25:775	a88	ETH: put share nonce c8fadd01420866c
12:29:25:775	a88	ETH round found 1 shares
12:29:25:785	10e4	ETH: 04/27/16-12:29:25 - SHARE FOUND - (GPU 2)
12:29:25:785	10e4	send: {"worker":"rig04","id":4,"method":"eth_submitWork","params":["0x0c8fadd01420866c","0x0373b2ccd691ee8dd82b0bf5cf6c6f7fa6b0cad8314253d69f4124659eec3a1e","0xb76e79e4824dca1525ea252fd29fc08a2819959a83331c571a2b16c2c0f6ee59"]}


12:29:25:835	10e4	got 15 bytes
12:29:25:835	10e4	buf: Internal Error

12:29:25:835	10e4	buf: InternalError

DCR is working perfect here. The problem is only with ETH.

My start command is

Code:

EthDcrMiner64.exe -wd 1 -r 0 -epool eth-ru.dwarfpool.com:8008 -ewal 0xXXXXXX -epsw rig04 -dpool stratum+tcp://dcr.suprnova.cc:2252 -dwal gagana.rig04 -eworker rig04 -dpsw x -allpools 1

What could it be?

1. -allpools is ignored for pools that support wallet addresses, like dwarfpool, ethpool, ethermine etc. So you can use -allpools 0 or 1 or remove it at all.
2. Just checked your command line (only set my wallet address) and it works, it finds ETH shares and pool accepts them.

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: restless on April 26, 2016, 04:45:42 AM

Sorry, now I remember taht I added allpools 1 to dwarfpool in order to be sure that devfee is mined, can this be a problem?
Setting 1 when its not needed?

-allpools is ignored for pools that support wallet addresses, like dwarfpool, ethpool, ethermine etc.

Gagana

member

Activity: 80

Merit: 10

The only one rig has this problem.

If I start it without "-allpools 1" option it can't connect to devfee pool and exits. If I start it with this option, then it starts, gets jobs but doesdidn't send the results back. I see in the log file:

Code:

12:29:25:775	a88	ETH: put share nonce c8fadd01420866c
12:29:25:775	a88	ETH round found 1 shares
12:29:25:785	10e4	ETH: 04/27/16-12:29:25 - SHARE FOUND - (GPU 2)
12:29:25:785	10e4	send: {"worker":"rig04","id":4,"method":"eth_submitWork","params":["0x0c8fadd01420866c","0x0373b2ccd691ee8dd82b0bf5cf6c6f7fa6b0cad8314253d69f4124659eec3a1e","0xb76e79e4824dca1525ea252fd29fc08a2819959a83331c571a2b16c2c0f6ee59"]}


12:29:25:835	10e4	got 15 bytes
12:29:25:835	10e4	buf: Internal Error

12:29:25:835	10e4	buf: InternalError

DCR is working perfect here. The problem is only with ETH.

My start command is

Code:

EthDcrMiner64.exe -wd 1 -r 0 -epool eth-ru.dwarfpool.com:8008 -ewal 0xXXXXXX -epsw rig04 -dpool stratum+tcp://dcr.suprnova.cc:2252 -dwal gagana.rig04 -eworker rig04 -dpsw x -allpools 1

What could it be?

restless

legendary

Activity: 1151

Merit: 1001

Sorry, now I remember taht I added allpools 1 to dwarfpool in order to be sure that devfee is mined, can this be a problem?
Setting 1 when its not needed?

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: restless on April 26, 2016, 04:34:54 AM

Quote from: Claymore on April 26, 2016, 04:15:54 AM

Where do you see that -allpools option for every pool defined?
If devfee cannot work on a pool, you won't be able to use this pool, miner will show warning and remove this pool from the list until you add "-allpools 1" option.

Its in the sample epools.txt

Quote

# POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F , PSW: x, WORKER: r270x, ESM: 1, ALLPOOLS: 1
# POOL: us1.ethermine.org:4444, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F, PSW: x, WORKER: , ESM: 1, ALLPOOLS: 0
# POOL: coinotron.com:3344, WALLET: YourUserName.YourWorkerName, PSW: YourWorkerPass, WORKER: , ESM: 2, ALLPOOLS: 1

Default epools.txt is a bit different:

# POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F, PSW: x, WORKER: , ESM: 0, ALLPOOLS: 0
# POOL: us1.ethermine.org:4444, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F, PSW: x, WORKER: , ESM: 1, ALLPOOLS: 0
# POOL: coinotron.com:3344, WALLET: YourUserName.YourWorkerName, PSW: YourWorkerPass, WORKER: , ESM: 2, ALLPOOLS: 1

So ALLPOOLS is 0 for most pools. It is required only for pools that use USERNAME.WORKER as login or as worker, miner will show warning and removes such pool from the list.

PS. I think everyone understands that "#" disables line as explained in readme. I did it because otherwise miner could switch to these pools and if you did not change credentials it will mine but not for you. At startup miner shows how many pools it accepted for ETH and DCR.

restless

legendary

Activity: 1151

Merit: 1001

Quote from: Claymore on April 26, 2016, 04:15:54 AM

Where do you see that -allpools option for every pool defined?
If devfee cannot work on a pool, you won't be able to use this pool, miner will show warning and remove this pool from the list until you add "-allpools 1" option.

Its in the sample epools.txt

Quote

# POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F , PSW: x, WORKER: r270x, ESM: 1, ALLPOOLS: 1
# POOL: us1.ethermine.org:4444, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F, PSW: x, WORKER: , ESM: 1, ALLPOOLS: 0
# POOL: coinotron.com:3344, WALLET: YourUserName.YourWorkerName, PSW: YourWorkerPass, WORKER: , ESM: 2, ALLPOOLS: 1

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: rednoW on April 26, 2016, 02:42:17 AM

ver 3.3 is bad for machines with weak cpu/hdd
Many freezes when finished generating first dag, then starting next one and attempt to start mining.
Also I had several "crc dag fail" after normal miner restart.
I'm back to 3.2 - it is cool! But I miss failover option.
Can we disable crc check somehow? I had no problem with corrupted DAG's before with Claymore miner ...

I had problems with DAG on one of my test rigs after hard reboot. It sent wrong shares for a few hours before I noticed that something is wrong.
DAG file size was ok and it had correct signature at beginning, but it was corrupted. So I think checking CRC is necessary.
PM me some logs so I can check the details. I can postpone next DAG generation for a few minutes and/or reduce CPU load for it.
Anyway, v3.2 creates next DAG too, so you must see same freezes. The only difference is CRC check when DAG is loaded, but it must not take more than 2-4 seconds even on slow CPU.

citronick

legendary

Activity: 1834

Merit: 1080

---- winter*juvia -----

Quote from: Lastmoadman on April 26, 2016, 03:54:44 AM

Quote from: rednoW on April 26, 2016, 02:42:17 AM

ver 3.3 is bad for machines with weak cpu/hdd
Many freezes when finished generating first dag, then starting next one and attempt to start mining.
Also I had several "crc dag fail" after normal miner restart.
I'm back to 3.2 - it is cool! But I miss failover option.
Can we disable crc check somehow? I had no problem with corrupted DAG's before with Claymore miner ...

I have the same problem. After generating the first DAG, the computer will crash. I may have to reduce the intensity or the clock frequency.

similar scenario here... my CPU is Celeron 1840 with 8 GB RAM, and 20GB windows virtual memory.

It "freezes" for awhile, about 3-4 seconds.... then mine as per normal... I guess it got passed the DAG tasks completed with just enough juice to start mining.

I don't get this freezing in my AMD 8-core CPU, 16GB system.

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