Claymore's ZCash/BTG AMD GPU Miner v12.6 (Windows/Linux)

[BitJunkie556]

I have 2x280X cards. Miner shows temp and fan speed only from GPU0
I'd like to see it from all cards. Possible ?

That's kind of strange. I would say just run MSI Afterburner and keep the monitor window thing open. Works well enough to glance at your system's performance, temps etc. Been using MSI Afterburner for years now.

[bolvan]

That's kind of strange. I would say just run MSI Afterburner and keep the monitor window thing open. Works well enough to glance at your system's performance, temps etc. Been using MSI Afterburner for years now.

MSI afterburner requires windows and requires local desktop access. It cant run in RDP session.
I like using http feature of the miner. Dont need any remote desktop access.
May be crossfire is the reason, ill check

[Batelk]

Claymore. When can we see Vega Frontier Edition support in Calymore? Apparently they are currently not compatible (cant build OpenCL application).

I can confirm this as well that it is not compatible

https://forum.z.cash/t/amd-vega-frontier/18788/8

Not many people own the Frontier version. So when the RX version comes out, Claymore should have enough time to do the work.

[Belix]

Running a single R9 Fury X on a windows box, using 15.12 drivers, which runs Claymore's Duel Eth and DCR miner without issue.
But I cannot get the claymore Zec miner to work.

Card is not overclocked at all.

It runs but shows a hash speed of zero:

16:48:47:056   1a1c   ZEC: 07/07/17-16:48:47 - New job from zec.suprnova.cc:2242
16:48:47:071   1a1c   target: 0x003c3c3c (diff: 1088H)
16:48:47:081   1a1c   ZEC - Total Speed: 0.000 H/s, Total Shares: 0, Rejected: 0, Time: 00:00
16:48:47:096   1a1c   ZEC: GPU0 0.000 H/s

and then after a minute or two
16:49:59:356   1ae8   watchdog - thread 0, hb time 72313
16:49:59:371   1ae8   WATCHDOG: GPU 0 hangs in OpenCL call, exit
16:49:59:386   1ae8   watchdog - thread 1, hb time 72484
16:49:59:396   1ae8   WATCHDOG: GPU 0 hangs in OpenCL call, exit
16:49:59:406   1ae8   watchdog - thread 2, hb time 72578
16:49:59:421   1ae8   WATCHDOG: GPU 0 hangs in OpenCL call, exit
16:49:59:431   1ae8   watchdog - thread 3, hb time 72391
16:49:59:446   1ae8   WATCHDOG: GPU 0 hangs in OpenCL call, exit
16:50:00:976   1ae8   Restarting OK, exit...

Anyone had a similar experience?

[Zyxi]

I'm new to mining but am having a tiny issue so wanted to see if I was doing something wrong.

I have 3 GPU's in my system and all of them are stock RX 470's.  While running it shows GPU 0, 1, and 2 all working fine.  The odd thing is when it shows the temperatures and fan speeds it will only show this for GPU 0 and GPU 1.  I have tried using -gmap 012 and also -gmap 210 and it still only shows 2 of the GPU's.  See below:

ZEC: 07/09/17-03:04:40 - SHARE FOUND - (GPU 2)
ZEC: Share accepted (156 ms)!
ZEC: 07/09/17-03:04:41 - SHARE FOUND - (GPU 2)
ZEC: Share accepted (156 ms)!
ZEC: 07/09/17-03:04:45 - SHARE FOUND - (GPU 1)
ZEC: Share accepted (156 ms)!
ZEC: 07/09/17-03:04:51 - SHARE FOUND - (GPU 1)
ZEC: Share accepted (156 ms)!
Pool sets new share target: 0x000e3b07 (diff: 4605H)
ZEC: 07/09/17-03:04:56 - New job from zec.suprnova.cc:2242
ZEC - Total Speed: 822.119 H/s, Total Shares: 36, Rejected: 0, Time: 00:04
ZEC: GPU0 279.209 H/s, GPU1 272.246 H/s, GPU2 270.664 H/s
GPU0 t=71C fan=46%, GPU1 t=69C fan=27%
ZEC: 07/09/17-03:05:12 - SHARE FOUND - (GPU 0)

From reading the documentation this should be showing all three GPU temps and fan speeds, so I wanted to ask what I am doing wrong that is preventing this from happening.

Thanks in advance for the help!

[bolvan]

May be crossfire is the reason, ill check

Yes, it was crossfire. With crossfire enabled miner show only temp from GPU0

[bolvan]

I have 3 GPU's in my system and all of them are stock RX 470's.  While running it shows GPU 0, 1, and 2 all working fine.  The odd thing is when it shows the temperatures and fan speeds it will only show this for GPU 0 and GPU 1.  I have tried using -gmap 012 and also -gmap 210 and it still only shows 2 of the GPU's.  See below:

Probably the same is applicable to your case

[nano1014]

Hello, i have a problem.
"Miner thread hangs, need to restart Miner"
I keep getting this error after about a hour of mining, not sure why I keep getting it. The miner itself freezes at a certain time period and only hitting a keyboard button will bring up the error and restart the miner.
http://oi66.tinypic.com/sol5j6.jpg

[Blisk]

I still get error because of this library  libssl.so.1.0.0
this lib is security risk, why it is used in Claymores?

[Sylv88]

Hi everyone, I'm having a problem with zcash mining lately, everthing worked fine for weeks, but recently every time In try mining zcash my miner crashes the hard way.. the entire miner freezes up after only 10-15minutes of mining, nothing can Bring it back to life except a hard reset. Ethereum mining works fine, zencash mining works fine but Zcash always crashes... Often it happens right after difficulty retarget. And Sometimes (not always) there is An error message "gpu 1 returned invalid data"..

Anyway I'm Running 5x 4gb rx 480, using a 4gb ram system.. the problem only occurs on zcash mining and happens on both windows 10 and Ubuntu...

If anyone could help me out that'd be great!

[Old_Timer]

The message "GPU #x returned wrong data" is mostly due to bad ram overclock or very high core clock?

[Sylv88]

I don't overclock, my settings are 1200 core & 1500 mem.. I think it's even a bit below stock settings...

I just find it weird that all other coins mine without problems.. but Zec always crashes.. Zen for example is equihash aswell and that doesn't crash.

[Rastanan]

The message "GPU #x returned wrong data" is mostly due to bad ram overclock or very high core clock?

Yes. Just reduce the frequency.

[orbital_station1]

Hello, i have a problem.
"Miner thread hangs, need to restart Miner"
I keep getting this error after about a hour of mining, not sure why I keep getting it. The miner itself freezes at a certain time period and only hitting a keyboard button will bring up the error and restart the miner.
http://oi66.tinypic.com/sol5j6.jpg

Swap risers around, then see if any of them is faulty.
It could also mean too high clock/mem oc.

Ofc before any of that do obligatory driver reinstall with DDU.

If none of that fails, try heavy underclock of the card in question. Then increase the clock bit by bit.
I had that message showing, and after a couple of hours of testing I found out my GPU was faulty. It was stable only when I downclocked heavily.
My r9 390x has stock clock of 1080, but I had to downclock to 990 to get any kind of stability. Ended up RMA-ing it, since it crashed every 5 minutes at stock speeds.

Hope this helps.

[Munhenhos]

Claymore, any news on Zcash support for AMD RX460 like you did on Ethereum side?

[Old_Timer]

The message "GPU #x returned wrong data" is mostly due to bad ram overclock or very high core clock?

Yes. Just reduce the frequency.

ram or core frequency?

[BitJunkie556]

Hello, i have a problem.
"Miner thread hangs, need to restart Miner"
I keep getting this error after about a hour of mining, not sure why I keep getting it. The miner itself freezes at a certain time period and only hitting a keyboard button will bring up the error and restart the miner.

Swap risers around, then see if any of them is faulty.
It could also mean too high clock/mem oc.

Ofc before any of that do obligatory driver reinstall with DDU.

If none of that fails, try heavy underclock of the card in question. Then increase the clock bit by bit.
I had that message showing, and after a couple of hours of testing I found out my GPU was faulty. It was stable only when I downclocked heavily.
My r9 390x has stock clock of 1080, but I had to downclock to 990 to get any kind of stability. Ended up RMA-ing it, since it crashed every 5 minutes at stock speeds.

Hope this helps.

Yep, I second this. Uninstall your drivers, and be sure to install 16.12.2. I've found it runs very stable. And as Orbital said, lower clocks for stability are better than trying to squeeze ever last sol/s out of the card with bad stability.

I've found for RX 480's, I do about 1200mhz core, 2075mhz clock, -42mv undervolt, and at -i 4 in Claymore. Seems to give me about 280-290 sol/s.

RX 470, try something like 1200mhz core, 1675 memory, and again, try undervolting a bit.

I've also found that issues with power supply lead to system freezing, hanging, etc. Swapped out my old Rosewill Photon 1050 on my four card rig of RX480's, to just a crappy Sentey Metal Blade 850m. Works like a charm and very rarely hangs up.

Checking risers and whatnot are an option, but much harder to really diagnose and narrow down. I'd recommend the aforementioned fixes first before doing that. Good luck!

[SonOfCrypton]

thanks claymore

[Bidnant]

The message "GPU #x returned wrong data" is mostly due to bad ram overclock or very high core clock?

Yes. Just reduce the frequency.

ram or core frequency?

That is try and error. Mostly RAM.

[Branko]

Support for Baffin chips incoming?