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

GabryRox

sr. member

Activity: 600

Merit: 261

Quote from: EvilHamster on March 04, 2018, 12:13:19 PM

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

new24core

member

Activity: 413

Merit: 17

Quote from: ascaloon on March 05, 2018, 07:27:00 AM

Quote from: new24core on March 05, 2018, 06:35:35 AM

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 ?

sztygar

newbie

Activity: 1

Merit: 0

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

ascaloon

newbie

Activity: 36

Merit: 0

Quote from: baga105 on March 05, 2018, 08:39:56 AM

Quote from: ascaloon on March 05, 2018, 08:36:09 AM

Quote from: Metroid on March 05, 2018, 07:38:24 AM

Quote from: ascaloon on March 05, 2018, 07:27:00 AM

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.

muzuca

member

Activity: 182

Merit: 13

Quote from: Xkeeper on March 05, 2018, 08:29:22 AM

Quote from: baga105 on March 05, 2018, 08:16:40 AM

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.

j4rd4

newbie

Activity: 41

Merit: 0

Quote from: Bigdrago on March 05, 2018, 11:53:31 AM

Quote from: j4rd4 on March 05, 2018, 11:45:11 AM

...
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.

Bigdrago

newbie

Activity: 312

Merit: 0

Quote from: j4rd4 on March 05, 2018, 11:45:11 AM

...
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.

Ratledge

jr. member

Activity: 84

Merit: 1

Quote from: Bigdrago on March 05, 2018, 11:31:36 AM

Quote from: Ratledge on March 05, 2018, 11:24:29 AM

Seriously? It varies widely especially for rigs that have inexpensive CPUs like Celerons and some of the slower Pentium models. Even the i3-7100 takes longer than 60 seconds to complete the boot process and load the purposefully delayed start items.

Any i5, i7 or faster or Ryzen 1500+ should get there in under a minute, true. It also depends a lot on exactly what is installed on each rig, although if it is a true bare bones system without anything other than mining software added, it's probably fine unless it's a Celeron under 3.0GHz.

Overdriventool starts after 10 sek, miner starts 20 sec after logon.
4gb ram, pentium g4560. 13 amd gpu. Ssd.
No problem.

Yep, G4560 or 4600/4620 are hyperthreaded, therefore essentially twice as fast from a logical point of view. You should be fine!

Bwtmn7

member

Activity: 109

Merit: 10

anyone here knows how to force 2GB mode?

j4rd4

newbie

Activity: 41

Merit: 0

...
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?

Bigdrago

newbie

Activity: 312

Merit: 0

Quote from: KGV on March 05, 2018, 11:33:26 AM

Quote from: Bigdrago on March 05, 2018, 11:27:53 AM

Quote from: KGV on March 05, 2018, 11:04:26 AM

Quote from: KGV on March 03, 2018, 10:48:32 PM

2 Claymore.
After i start to use 11.2 version, i got amdocl64.dll crashes.
Any clues?

I posted this question early, but no answers for serious question as usual.

But i solved this issue.
If anyone have same error you need to do:
1. Increase amount of ram at you rig (if you have 2gb make it at least 4gb)
2. Increase swap file 32-64 gb (or more if you have large rig).
3. GPU_FORCE_64BIT_PTR 0 set to 1
4. Copy atiadlxx.dll to folder where claymore miner

For me it was 3 and 4. All my rigs have at least 8gb of ram and huge swap.

What does setting 1 do? I have 0.
I got 65gb swap and 4gb ram. 13 amd radeon 570 8gb.

It enable 64 bit address space.
4Gb of ram for 13 cards with 8gb on board is to small. All my rigs above 10 cards have 16 gb of ram and 64-90gb of swap.

Ok.
Strange. Running for a week here without issues. Guess all systems is different.

KGV

newbie

Activity: 55

Merit: 0

Quote from: Bigdrago on March 05, 2018, 11:27:53 AM

Quote from: KGV on March 05, 2018, 11:04:26 AM

Quote from: KGV on March 03, 2018, 10:48:32 PM

2 Claymore.
After i start to use 11.2 version, i got amdocl64.dll crashes.
Any clues?

I posted this question early, but no answers for serious question as usual.

But i solved this issue.
If anyone have same error you need to do:
1. Increase amount of ram at you rig (if you have 2gb make it at least 4gb)
2. Increase swap file 32-64 gb (or more if you have large rig).
3. GPU_FORCE_64BIT_PTR 0 set to 1
4. Copy atiadlxx.dll to folder where claymore miner

For me it was 3 and 4. All my rigs have at least 8gb of ram and huge swap.

What does setting 1 do? I have 0.
I got 65gb swap and 4gb ram. 13 amd radeon 570 8gb.

It enable 64 bit address space.
4Gb of ram for 13 cards with 8gb on board is to small. All my rigs above 10 cards have 16 gb of ram and 64-90gb of swap.

Bigdrago

newbie

Activity: 312

Merit: 0

Quote from: Ratledge on March 05, 2018, 11:24:29 AM

Quote from: Metroid on March 05, 2018, 07:38:24 AM

Quote from: ascaloon on March 05, 2018, 07:27:00 AM

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.

Seriously? It varies widely especially for rigs that have inexpensive CPUs like Celerons and some of the slower Pentium models. Even the i3-7100 takes longer than 60 seconds to complete the boot process and load the purposefully delayed start items.

Any i5, i7 or faster or Ryzen 1500+ should get there in under a minute, true. It also depends a lot on exactly what is installed on each rig, although if it is a true bare bones system without anything other than mining software added, it's probably fine unless it's a Celeron under 3.0GHz.

Overdriventool starts after 10 sek, miner starts 20 sec after logon.
4gb ram, pentium g4560. 13 amd gpu. Ssd.
No problem.

Bigdrago

newbie

Activity: 312

Merit: 0

Quote from: KGV on March 05, 2018, 11:04:26 AM

Quote from: KGV on March 03, 2018, 10:48:32 PM

2 Claymore.
After i start to use 11.2 version, i got amdocl64.dll crashes.
Any clues?

I posted this question early, but no answers for serious question as usual.

But i solved this issue.
If anyone have same error you need to do:
1. Increase amount of ram at you rig (if you have 2gb make it at least 4gb)
2. Increase swap file 32-64 gb (or more if you have large rig).
3. GPU_FORCE_64BIT_PTR 0 set to 1
4. Copy atiadlxx.dll to folder where claymore miner

For me it was 3 and 4. All my rigs have at least 8gb of ram and huge swap.

What does setting 1 do? I have 0.
I got 65gb swap and 4gb ram. 13 amd radeon 570 8gb.

Ratledge

jr. member

Activity: 84

Merit: 1

Quote from: Metroid on March 05, 2018, 07:38:24 AM

Quote from: ascaloon on March 05, 2018, 07:27:00 AM

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.

Seriously? It varies widely especially for rigs that have inexpensive CPUs like Celerons and some of the slower Pentium models. Even the i3-7100 takes longer than 60 seconds to complete the boot process and load the purposefully delayed start items.

Any i5, i7 or faster or Ryzen 1500+ should get there in under a minute, true. It also depends a lot on exactly what is installed on each rig, although if it is a true bare bones system without anything other than mining software added, it's probably fine unless it's a Celeron under 3.0GHz.

KGV

newbie

Activity: 55

Merit: 0

Quote from: KGV on March 03, 2018, 10:48:32 PM

2 Claymore.
After i start to use 11.2 version, i got amdocl64.dll crashes.
Any clues?

I posted this question early, but no answers for serious question as usual.

But i solved this issue.
If anyone have same error you need to do:
1. Increase amount of ram at you rig (if you have 2gb make it at least 4gb)
2. Increase swap file 32-64 gb (or more if you have large rig).
3. GPU_FORCE_64BIT_PTR 0 set to 1
4. Copy atiadlxx.dll to folder where claymore miner

For me it was 3 and 4. All my rigs have at least 8gb of ram and huge swap.

KGV

newbie

Activity: 55

Merit: 0

Quote from: john1010 on March 05, 2018, 10:33:41 AM

My 570 8gb nitro got this kind of error..

OpenCL error -4 - cannot write buffer for DAG

even I change my Vram to 17500-25500

Is anyone of you have the solution for this? I already also the riser, cable etc but I always got this message continuously..

Set swap file size 32-64 gb

Call_Me_Bambi

sr. member

Activity: 574

Merit: 261

Quote from: xenonwon on January 30, 2018, 06:00:03 AM

Quote from: Call_Me_Bambi on January 29, 2018, 07:53:20 PM

Quote from: xxvitalxx on January 29, 2018, 06:13:03 PM

Quote from: xenonwon on January 29, 2018, 06:09:50 PM

hello, I have put the rig of mined by wifi, the wifi works perfectly arrives all the signal and the rig has internet, the problem comes when I put the claymore to mine, it appears "Socket was closed remotely (by pool)", I have been investigating and I can not find any information so I had to put it back in the other room with the network cable. Any help around here?

Im using powerline adapter and i can move my rig where i want... try to search on ebay for powerline adapter (my one is 200mbps). i hope this helps.

I think that if you use a WiFi dongle and put the dongle on a USB extension lead the problems with the WiFi interfering with Claymore is removed, I'm going to give this a try in the next couple of weeks and see what happens.

Ok, when you try it on, let me know. Thanks

Well it's been a bit more than a couple of weeks but I finally got round to it (had to sort out a PSU wiring problem first).
I put a USB WiFi dongle on a USB extension lead, fired-up Claymore and it's been working just as it did when hard wired through a network cable.

john1010

hero member

Activity: 2100

Merit: 562

My 570 8gb nitro got this kind of error..

OpenCL error -4 - cannot write buffer for DAG

even I change my Vram to 17500-25500

Is anyone of you have the solution for this? I already change also the riser, cable etc but I always got this message continuously..

atomant

newbie

Activity: 6

Merit: 0

Is there any way to actually determine why my cards, which are all identical 1050Tis all hash at different rates?
then all of a sudden, the whole rig goes down to a 0MH's rate

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