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

[Bigdrago]

...
17:12:12:475    cd7fa700        ETH: 03/05/18-17:12:12 - New job from eth-eu1.nanopool.org:9999
17:12:12:475    cd7fa700        target: 0x000000006df37f67 (diff: 10000MH), epoch 173(2.35GB)
17:12:12:475    cd7fa700        ETH - Total Speed: 187.017 Mh/s, Total Shares: 84, Rejected: 0, Time: 01:18
17:12:12:475    cd7fa700        ETH: GPU0 32.320 Mh/s, GPU1 28.793 Mh/s, GPU2 32.324 Mh/s, GPU3 32.150 Mh/s, GPU4 29.107 Mh/s, GPU5 32.323 Mh/s
17:12:13:865    1242d700        watchdog - fminer thread hangs
17:12:13:865    1242d700        em hbt: 1, fm hbt: 147423,
17:12:13:865    1242d700        Miner thread hangs, need to restart miner!
17:12:13:865    1242d700        Rebooting

Yea, yea, too much overclocking/undervolting. But how to identify the card concerned - efficiently?
Any ideas, please?

Set all to default clock.
Oc and undervolt one at a time.

[1714700717]

1714700717

[1714700717]

1714700717

[1714700717]

1714700717

[1714700717]

1714700717

[1714700717]

1714700717

[j4rd4]

...
17:12:12:475    cd7fa700        ETH: 03/05/18-17:12:12 - New job from eth-eu1.nanopool.org:9999
17:12:12:475    cd7fa700        target: 0x000000006df37f67 (diff: 10000MH), epoch 173(2.35GB)
17:12:12:475    cd7fa700        ETH - Total Speed: 187.017 Mh/s, Total Shares: 84, Rejected: 0, Time: 01:18
17:12:12:475    cd7fa700        ETH: GPU0 32.320 Mh/s, GPU1 28.793 Mh/s, GPU2 32.324 Mh/s, GPU3 32.150 Mh/s, GPU4 29.107 Mh/s, GPU5 32.323 Mh/s
17:12:13:865    1242d700        watchdog - fminer thread hangs
17:12:13:865    1242d700        em hbt: 1, fm hbt: 147423,
17:12:13:865    1242d700        Miner thread hangs, need to restart miner!
17:12:13:865    1242d700        Rebooting

Yea, yea, too much overclocking/undervolting. But how to identify the card concerned - efficiently?
Any ideas, please?

Set all to default clock.
Oc and undervolt one at a time.

That's what I worried about, because one try could cost me an hour or more of waiting. I will try, but by halving a set (first three GPUs and then - after a couple of hours at worst - it will remain only 3 cards suspected). This for a couple of rigs...
Thanks.

[muzuca]

Does your miner recognizes all GPUs? or only 1?

Yes all GPUs are recognized and are mining.

GPU0 reports 30.030MH, GPU1-6 report 30.6MH

Basically I have flashed BIOS on all of them and now I try to lower the clock just a little bit with Claymore's, just to see If I get more stability.

Sometimes, when for some reason my config don't work in any gpu, I open and close the miner 2-3 times. I wait until the last setting dag and then close.

[ascaloon]

When you restart the rig wait for 12-15 minutes before you start Claymore. That freeze also happend to one of my rigs after restart and the only solution for me is to wait before I start miner. It`s unbelivable but that help.

Delay should be only 1 minute at most, there is no need for more than that.

Yes I know but my rig freeze`s than. i dont know what happend with driver or something else in that period of 12-15 minutes but that is the only thing that helps for normal start of claymore.

Try doing that with OverdriveNtool.

Im use OverdriveNtool from the beginings.

[sztygar]

Problem with DAG generation (no errors, just confirmation of DAG creation is never there) on R7 370 while mining EXP

OS: Ubuntu 16.04
Driver: amdgpu-pro:17.40-492261
Claymore: 11.0, 11.1, 11.2

Works like a charm with Claymore 10.6

[new24core]

I have a really annoying problem, with one mining rig, where I want to use my onboard GPU as the primary graphics but I can't. In MS Windows 10 I have a scheduled task to reboot once a day.  On one rig all works fine but on the other rig I get the following error :

start building OpenCL program for GPU 0...
.
.
.
Miner cannot initialize for 5 minutes, need to restart miner!
ADL: CAnnot find any AMD adapters.

The funny thing is that once I remote into the rig the miner can then see the cards.

Please note in the log just before is does state that there are 5 cards found.

Anyone seen this problem ?

When you restart the rig wait for 12-15 minutes before you start Claymore. That freeze also happend to one of my rigs after restart and the only solution for me is to wait before I start miner. It`s unbelivable but that help.

I increased the time slightly but 12 minutes is not the answer.

If I change the M/B settings so the primary card is PCIE2(no on board) then there is not a problem.  It's bloody annoying as my rigs have the same hardware so I don't get these sort of issues. 

Does anyone have any ideas ?

[GabryRox]

Firstly, thank you all for your help so far (messages and so on)

My rig - now 4 weeks old, ALL new kit.

Tried 11.2 today and apart from virus guards kicking off all over the place (until I disabled them all) failed to work.

I have now kind of got the rig working thanks to some help, however...

Starts at 64 Mh/s then reduces down and down...

ETH: 03/04/18-17:07:42 - SHARE FOUND - (GPU 0)
ETH: Share accepted (15 ms)!
ETH: 03/04/18-17:07:43 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 64.106 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:00
ETH: GPU0 21.917 Mh/s, GPU1 10.142 Mh/s, GPU2 10.124 Mh/s, GPU3 21.923 Mh/s

ETH: 03/04/18-17:07:55 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 64.281 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:00
ETH: GPU0 21.952 Mh/s, GPU1 10.191 Mh/s, GPU2 10.195 Mh/s, GPU3 21.943 Mh/s

GPU0 t=54C fan=22%%, GPU1 t=57C fan=0%%, GPU2 t=52C fan=0%%, GPU3 t=54C fan=0%%
ETH: 03/04/18-17:08:29 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 42.352 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:01
ETH: GPU0 0.000 Mh/s, GPU1 10.197 Mh/s, GPU2 10.178 Mh/s, GPU3 21.977 Mh/s

GPU0 t=55C fan=22%%, GPU1 t=62C fan=30%%, GPU2 t=62C fan=28%%, GPU3 t=59C fan=26%%
ETH: 03/04/18-17:08:32 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 42.215 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:01
ETH: GPU0 0.000 Mh/s, GPU1 10.132 Mh/s, GPU2 10.176 Mh/s, GPU3 21.906 Mh/s



Followed shortly by:

WATCHDOG: GPU 0 hangs in OpenCL call, exit
WATCHDOG: GPU 0 hangs in OpenCL call, exit
Quit, please wait...
Restarting OK, exit...

Then rig comes to a complete stand still...Wont go further.

Virtual memory 16gb, virus guard disabled...

Please any thoughts - this is killing me now...

Rig

Celeron - K170 board - 4gb ram - Msata HDD - 2 x rx570 4gb - 2 x RX550 4gb - Thermaltake 850psu...Windows 10 64bit.

yup... i posted the exact same issue a few days back but never saw a reply with fix suggested. Here's the thing... this is happening on all 4 of my 6x470 rigs... and really only since that last major W10 update.  So, I am saying it is NOT a hardware issue because what are the odds that on 4 rigs, there is an actual problem with GPU0 on all 4?  It never happens on any other GPU, so this means it is a software/settings issue, but I have not been able to figure it out.  On Claymore Cryptonite miner, the solution to fix a lagging GPU0 was to manually designate the "-h" value in the .bat file, but no such option existing in this miner, at least not -h but maybe something else can be tweaked only on GPU0 to fix this... that has been what i've tried to discover for the past weeks but no solution yet. I actually had to disable GPU0 on 1 of my rigs that it got so bad, and looks like another 1 is headed that direction as well.

The one difference with mine is that they don't actually crash/freeze, but they get stuck in a non-stop look of resarting the miner due to that hanging GPU0 issue. So it restarts every couple minutes, usually with GPU0 at zero speed.

Claymore... or anyone else that knows of this issue... please advise. Thanks!

Windows 10 Pro - 8GB RAM - 16-32GB virtual memory - Claymore dual miner versions 10.2/10.5/10.6

[leonix007]

and really only since that last major W10 update.  

What about fixing this? I see somewhat messed up with the AMD driver, Win10 update made a mess, how about Rolling back to previous old version of windows 10? then Install Drivers and disable Win10 update

[cryptoillusion1]

Firstly, thank you all for your help so far (messages and so on)

My rig - now 4 weeks old, ALL new kit.

Tried 11.2 today and apart from virus guards kicking off all over the place (until I disabled them all) failed to work.

I have now kind of got the rig working thanks to some help, however...

Starts at 64 Mh/s then reduces down and down...

ETH: GPU0 21.917 Mh/s, GPU1 10.142 Mh/s, GPU2 10.124 Mh/s, GPU3 21.923 Mh/s


ETH: GPU0 0.000 Mh/s, GPU1 10.132 Mh/s, GPU2 10.176 Mh/s, GPU3 21.906 Mh/s



Followed shortly by:

WATCHDOG: GPU 0 hangs in OpenCL call, exit
WATCHDOG: GPU 0 hangs in OpenCL call, exit
Quit, please wait...
Restarting OK, exit...

Then rig comes to a complete stand still...Wont go further.

Virtual memory 16gb, virus guard disabled...

Please any thoughts - this is killing me now...

Rig

Celeron - K170 board - 4gb ram - Msata HDD - 2 x rx570 4gb - 2 x RX550 4gb - Thermaltake 850psu...Windows 10 64bit.

yup... i posted the exact same issue a few days back but never saw a reply with fix suggested. Here's the thing... this is happening on all 4 of my 6x470 rigs... and really only since that last major W10 update.  So, I am saying it is NOT a hardware issue because what are the odds that on 4 rigs, there is an actual problem with GPU0 on all 4?  It never happens on any other GPU, so this means it is a software/settings issue, but I have not been able to figure it out.  On Claymore Cryptonite miner, the solution to fix a lagging GPU0 was to manually designate the "-h" value in the .bat file, but no such option existing in this miner, at least not -h but maybe something else can be tweaked only on GPU0 to fix this... that has been what i've tried to discover for the past weeks but no solution yet. I actually had to disable GPU0 on 1 of my rigs that it got so bad, and looks like another 1 is headed that direction as well.

The one difference with mine is that they don't actually crash/freeze, but they get stuck in a non-stop look of resarting the miner due to that hanging GPU0 issue. So it restarts every couple minutes, usually with GPU0 at zero speed.

Claymore... or anyone else that knows of this issue... please advise. Thanks!

Windows 10 Pro - 8GB RAM - 16-32GB virtual memory - Claymore dual miner versions 10.2/10.5/10.6

Do you have a dummy plug or a monitor connected to GPU0 ? I have noticed this behavior when you remote and don't have a monitor/dummy plug connected

[GabryRox]

and really only since that last major W10 update.  

What about fixing this? I see somewhat messed up with the AMD driver, Win10 update made a mess, how about Rolling back to previous old version of windows 10? then Install Drivers and disable Win10 update

yeah, i actually have WU turned off but as i understand it, for major updates such as the Fall Creators Update, you can only push it so long.  I kept getting notified and kept pushing out week after week but eventually it didnt give me the option to not install it and just did it on it's own.  If anyone knows of a way around this I would be very happy to hear it :-)

And... i have a monitor plugged into the GPU via HDMI cable on all 4 rigs.

[fanisk21]

Goodnight guys, one question, im using 11.2 version since the release and everthing was good till now. Dont know why but my miner showed always 87+eth / 5800 blake2s and 1 minute avg was the same for eth. But now it's reporting only 86+ 1 minute avg. Anyone having this problem?

https://i.imgur.com/muCgX8P.png

[leonix007]

and really only since that last major W10 update.  

What about fixing this? I see somewhat messed up with the AMD driver, Win10 update made a mess, how about Rolling back to previous old version of windows 10? then Install Drivers and disable Win10 update

yeah, i actually have WU turned off but as i understand it, for major updates such as the Fall Creators Update, you can only push it so long.  I kept getting notified and kept pushing out week after week but eventually it didnt give me the option to not install it and just did it on it's own.  If anyone knows of a way around this I would be very happy to hear it :-)

And... i have a monitor plugged into the GPU via HDMI cable on all 4 rigs.

Try this, Kudos to Vann, he was able to update his rigs without affecting his drivers

gpedit ==> Computer Configuration ==> Administrative Templates ==> Windows Components ==> Windows Update and set 'Do not include drivers with Windows Update' to enabled.


Read other suggestions here

https://bitcointalk.org/index.php?topic=2878646.0

[king_pin]

How many STALE shares is normal to get with Claymore 11.2

[tenmoi]

Windows keeps restarting. Had to readjust oc settings after update to 11.2

I guess your hash rate is reduced now. So what’s the point in updating to 11.2? Claymore must look into this problem. Mine rig kept restarting every 10-20 minutes so I reverted to 11.0. The hash rates are lower but the rig runs stable.

P.S
I dualmine.

[Dimm123456]

After some time of the work of the miner, errors appear:
ETH: Stratum - Cannot connect to eu1.ethermine.org:5555
DevFee: ETH: Stratum - Failed to connect, retry in 20 sec...
What is the reason?

My start.bat file:

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.ethermine.org:4444 -ewal 0xWALLET.rig_1 -epsw x -dpool stratum+tcp://stratum.decredpool.org:3343 -dwal USER.rig_1 -dpsw x

[0xb1]

I am puzzled.

There is a huge difference (shares) in what claymore reports and what pool reports.

Claymore Report / 1 hour:



RiG01 > 193 Shares
RiG02 > 165 Shares

Ethermine Report / 1 hour:



RiG01 > 148 Shares (6 Stale)
RiG02 > 143 Shares (1 Stale)

...

Poolfee is 1%, claymore devfee is turned off.
This is quite a difference. Why is it like that?

Thanks for your feedback guys!

[wOvAN]

with 11.2 I rather got more stales +3-4% stale shares

[0xb1]

with 11.2 I rather got more stales +3-4% stale shares

I wouldn`t mind a few more stale shares...
but i have a difference in what claymore reports and what pool reports that is unacceptable.

Claymore reports 50 more shares than pool (1 hour timeframe).

193 (Claymore) > 148 (Pool)
165 (Claymore) > 143 (Pool)

Check my previous post:

https://bitcointalk.org/index.php?topic=1433925.msg31682140#msg31682140

No clue why what how.

[djmuler]

F**king windows defender forgot to add the exception for the new version, all the night without mining 

[bileq]

in the latest version of Claymore (v11.2) my rigs temp increased. any idea?