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

[kanoptx]

to me - it doesn't seem worth it to duel mine . BTC per day is less than mining either of them directly

Ether 20M h/s normally get 22-24
DRC - 300 Mh/s normally get 1.3 Gh/s

yeah but here you're getting both..

[kanoptx]

Since using your client, i've only been running in pure ETH mode (no DCR mining)

Since my rigs have been running super stable, I thought i'd try dual mining mode.
I reconfigured my command line according to your example for dcr.suprnova.cc and started it up.

Everything connected and then started hashing away.  Shares were being submitted for both, but after 1-2 minutes of mining, the whole rig freezes up.
At first I thought it was because I didn't set the virtual memory to 16384 (I have 8GB in each rig - never set the virtual mem settings as everything ran fine while mining ETH) so I made the setting and restarted.

Still crashing after 1-2 minutes.  So I reduced the OC on my cards to stock levels.
Still crashing after 1-2 minutes.

Thought this was a rig issue, so I tried dual mining on another newer rig with different cards and hardware (both running Windows 8 x64 with 8GB RAM).  Still the same problem is happening.

Log files show that it always crashes after a few DCR shares have been found.

I'm not sure why this is happening.  I've since gone back to ETH only mining mode, and things are stable as usual.  Is this a bug with v3.3?

think i may try this for my r9 290... setting it to eth only. i tried setting ethi to 0. it's been doing like 20,21. not sure if it will freeze or not.. it's a shame, this works so good on my r9 280x

[Patrice7]

stratum socket send failure 10053 i've been getting this alot lately from supernove. why? :\ it connects again rly fast though :\

I'm getting the same on dwarfpool. It happens just after finding a share and rejecting it.

[o00o]

I updated to v3.3 from a previous 3.x version and was no longer able to mine due to failing to create a big buffer.  I was forced to revert to v 1.2 to resolve the issue as any other builds replicate the problem.  Absolutely no changes were made to the system in question; all I did was close the previously working miner and updated the directory's contents to the most recent build. All environment variables have been set as well as 2 x 8 GB pagefiles and I've also removed temp files as well as the dag directory which I additionally decided to provide an alternate one on a seperate hard drive to hopefully eliminate the problem.  I also tried renaming the dag files successfully created by QTminer in hopes of using them with Claymore's but that also didn't work. My other rig surprisingly doesn't suffer from this symptom.

[restless]

What about 2GB GPUs - will they be able to create new DAG in video memory too? (I guess so, but...)

[qqqq]

Wolf0, could you check this thread pls. https://bitcointalk.org/index.php?topic=1366011.80

[kanoptx]

setting ethi to 0 seemed to solve my freezing problem. please try it out before setting dual mode off or giving up altogether ^^

[BitSquare]

setting ethi to 0 seemed to solve my freezing problem. please try it out before setting dual mode off or giving up altogether ^^

What was your ethi value before, the default 8. How much performance degradation after you change the ethi to 0?

[zorvalth]

@Claymore in my command line i use ethermine with eth-proxy:

Code:

EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal 0x8d5ad572f59fbc5bb********266d3083ea9290.RigName -epsw x -esm 0 -mode 1 -wd 1 -r 1 -dbg -1  -etha 1

Because there is no way to check if my failover is set properly does it suppose to look like that:

Code:

POOL: us1.ethermine.org:4444, WALLET: 0x8d5ad572f59fbc5bb********266d3083ea9290, PSW: x, WORKER:RigName , ESM: 0, ALLPOOLS: 0
POOL: eth-eu.dwarfpool.com:8008, WALLET: 0x8d5ad572f59fbc5bb********266d3083ea9290, PSW: x, WORKER:RigName , ESM: 0, ALLPOOLS: 0

or should i put the name of the worker after the wallet separated wit dot?

[kanoptx]

setting ethi to 0 seemed to solve my freezing problem. please try it out before setting dual mode off or giving up altogether ^^

What was your ethi value before, the default 8. How much performance degradation after you change the ethi to 0?

it was on default. i'm getting around 20/21 mh... power consumption is the same. i should be getting around 25. will try with 3-4 intensity maybe. but that card sucks. it makes my r9 280x hotter. i'll have to make a sep rig for r9 290 and keep them seperate.

[Claymore]

I already got some feedback and logs, soon I will release an update with improvements related to CRC. Since I found that some people use DAGs from ethminer I will return compatibilty with it, but still will check CRC. To avoid freezes I will start next DAG calculation not immediately but a bit later and will do it with idle priority. Also there will be options to create several future DAGs or disable next DAG creation.

It takes like 5s to create the goddamned DAG on GPU itself - making epoch switches a breeze, too. The verification on CPU can be done with only the cache... why would you spend so much time implementing something that is more complex and sucks on top of it?

Actually I did not spend much time for CRC yet, making DAG on GPU and related changes will require more time.
But it seems it can be better to postpone other features and finally solve issues with DAGs completely.

[elzium]

I've also had problems with dual mining while eth only was stable. One rig died, other restarted. Both were weak psu and nothing more. Gave them more juice and now works like a charm on 3.2

There is easy way to test it, start dual mode with -dcri 1 and if no problems, start to increase it while mining by pressing +. Maximum consumption is reached somewhere around -dcri 80.
Wattmeter showed me 200W extra power on 4x280x rig..

Same thing with dag creation, draws more power.

Anyone sees sent hashrate on dwarf?

[baykan]

Hi,

first, thank you very much for this wonderful miner.
This is being one of the best miners...

I have a 5 card rig and individual pcs with single cards inside arround.
I have no problem with single gpu card pcs. They mine wonderfull.

The problematic 5 card rig,
PC mem was 4Gigabytes. Now 8. and I moded to enable 5th GPU.
the 5 card rig, with 3.2 miner, PC RESTARTS after dag file generation and approximately after 10 minutes of hashing.

Now I'm trying the 3.3 version. Hope it's not the low memory (8GB).
With Ethminer system works just fine. without crashing.

-

Is there any way you can program if the gpu temp reaches let's say 80 degrees celcius, slows hashing to keep the temp at 80
I have card 86 degrees fan is %100

Claymore you are doing a good job
Thanks in advance

I have two 6 card rigs mining flawlessly with Win7 x64 8Gb system RAM. Your problem has nothing to do with low memory but with excess heat. If your cards are at 86º and fan already at 100% you have to improve your cooling. Try adding extra fans. I use a small USB fan to push fresh air from bellow and two 120mm fans (connected to the motherboard as case fans) to pull the hot air from above.

I use the -tt 75 parameter and my cards are always around 72º with fans ~60%.

Trimegistus, it's a little bit early but. Looks like you are correct.
Ethminer also crashed my system.
Interestingly with Dual Miner PC was restarting after or during 2nd Dag file generation.
with ethminer I was thinking system was working fine, but yesterday night while I was together with my old schooll friends, drinking and having fun. Miner crashed with remote desktop unavailable.
So Instead of placing a fan in front of the 5 card rig. I moved it to the systems room which is air conditioned.
It has been more than half an hour now with dual miner working smoothly with fingers crossed.

So looks like excessive heat as you have mentioned was my problem.

Thank you very much anyway...

EDIT: more than 1 hour past. Still running....

[Fanpant]

setting ethi to 0 seemed to solve my freezing problem. please try it out before setting dual mode off or giving up altogether ^^

What was your ethi value before, the default 8. How much performance degradation after you change the ethi to 0?

it was on default. i'm getting around 20/21 mh... power consumption is the same. i should be getting around 25. will try with 3-4 intensity maybe. but that card sucks. it makes my r9 280x hotter. i'll have to make a sep rig for r9 290 and keep them seperate.

For my R9 390, I run them at -100mV and 1080/1200 MHz, they are not so hot. The temperature is about 70 degree.

[divan0w]

Hi, I try for first time this Dual miner, so far I mined only ETH with my 2x290(I have 4 machines with 2x290). Installed 15.12 driver and made corrections to start.bat and now looks like this:



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 eu1.nanopool.org:8888 -ewal 0x3d5f3243ed50c3614efbe6853bab45d1a55a5892/probt -epsw x -dpool dcr.suprnova.cc:9112 -dwal DseAYH56epfWxYmdo8XD9voCbrej9vwPpEi -dpsw x





I think all was going fine but I receive this:


16:22:43:011   13bc   checkread timeout
16:22:43:011   13bc   ETH: Job timeout, disconnect, retry in 20 sec...
16:22:44:281   13c8   checkread timeout
16:22:44:284   13c8    DCR: Job timeout, disconnect, retry in 20 sec...

[Marvell1]

I've also had problems with dual mining while eth only was stable. One rig died, other restarted. Both were weak psu and nothing more. Gave them more juice and now works like a charm on 3.2

There is easy way to test it, start dual mode with -dcri 1 and if no problems, start to increase it while mining by pressing +. Maximum consumption is reached somewhere around -dcri 80.
Wattmeter showed me 200W extra power on 4x280x rig..

Same thing with dag creation, draws more power.

Anyone sees sent hashrate on dwarf?

I though i had a problem with the 1k watt XFX psu as well i had but i tried it with just 2 390 cards rather than the four i nonmally run and my miner still crashes in dual mode, works fine in solo eth mode.

[baykan]

Hi,

first, thank you very much for this wonderful miner.
This is being one of the best miners...

I have a 5 card rig and individual pcs with single cards inside arround.
I have no problem with single gpu card pcs. They mine wonderfull.

The problematic 5 card rig,
PC mem was 4Gigabytes. Now 8. and I moded to enable 5th GPU.
the 5 card rig, with 3.2 miner, PC RESTARTS after dag file generation and approximately after 10 minutes of hashing.

Now I'm trying the 3.3 version. Hope it's not the low memory (8GB).
With Ethminer system works just fine. without crashing.

-

Is there any way you can program if the gpu temp reaches let's say 80 degrees celcius, slows hashing to keep the temp at 80
I have card 86 degrees fan is %100

Claymore you are doing a good job
Thanks in advance

I have two 6 card rigs mining flawlessly with Win7 x64 8Gb system RAM. Your problem has nothing to do with low memory but with excess heat. If your cards are at 86º and fan already at 100% you have to improve your cooling. Try adding extra fans. I use a small USB fan to push fresh air from bellow and two 120mm fans (connected to the motherboard as case fans) to pull the hot air from above.

I use the -tt 75 parameter and my cards are always around 72º with fans ~60%.

Trimegistus, it's a little bit early but. Looks like you are correct.
Ethminer also crashed my system.
Interestingly with Dual Miner PC was restarting after or during 2nd Dag file generation.
with ethminer I was thinking system was working fine, but yesterday night while I was together with my old schooll friends, drinking and having fun. Miner crashed with remote desktop unavailable.
So Instead of placing a fan in front of the 5 card rig. I moved it to the systems room which is air conditioned.
It has been more than half an hour now with dual miner working smoothly with fingers crossed.

So looks like excessive heat as you have mentioned was my problem.

Thank you very much anyway...

EDIT: more than 1 hour past. Still running....

After six hours. Still working rock solid, in the cold systems room.

Many thanks Trimegistus...

[revelacaogr]

Hi, I try for first time this Dual miner, so far I mined only ETH with my 2x290(I have 4 machines with 2x290). Installed 15.12 driver and made corrections to start.bat and now looks like this:

these commnands u need only once (( new OS install )) (( go to control panel/system/advanced system settings/advanced/environment variables/user variables )) to check

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 eu1.nanopool.org:8888 -ewal 0x3d5f3243ed50c3614efbe6853bab45d1a55a5892/probt -epsw x -dpool dcr.suprnova.cc:9112 -dwal DseAYH56epfWxYmdo8XD9voCbrej9vwPpEi -dpsw x

I think all was going fine but I receive this:


16:22:43:011   13bc   checkread timeout
16:22:43:011   13bc   ETH: Job timeout, disconnect, retry in 20 sec...
16:22:44:281   13c8   checkread timeout
16:22:44:284   13c8    DCR: Job timeout, disconnect, retry in 20 sec...

[/quote]
try this :
EthDcrMiner64.exe -epool eu1.nanopool.org:8888 -ewal 0x3d5f3243ed50c3614efbe6853bab45d1a55a5892 -epsw x -ethi 10 -dpool stratum+tcp://dcr.suprnova.cc:2252 -dwal user.worker -dpsw pass -dcri 50 -mode 0

[Mrga666]

I still have the same issue of this miner recognising my 2 390 graphics cards as 290 ones.
Reinstalling drivers did nothing to help...
Does it even matter?

[elzium]

I've also had problems with dual mining while eth only was stable. One rig died, other restarted. Both were weak psu and nothing more. Gave them more juice and now works like a charm on 3.2

There is easy way to test it, start dual mode with -dcri 1 and if no problems, start to increase it while mining by pressing +. Maximum consumption is reached somewhere around -dcri 80.
Wattmeter showed me 200W extra power on 4x280x rig..

Same thing with dag creation, draws more power.

Anyone sees sent hashrate on dwarf?

I though i had a problem with the 1k watt XFX psu as well i had but i tried it with just 2 390 cards rather than the four i nonmally run and my miner still crashes in dual mode, works fine in solo eth mode.

To make sure its not a power issue, run it at -dcri 1. Risers are powered?