Topic: Claymore's ZCash/BTG AMD GPU Miner v12.6 (Windows/Linux) - page 49. (Read 3839203 times)

If you mod the miner ... I assume you are the bastard
Claymore is doing a good work. If you don't want his miner ... just don't use it, or disable the optimizations.
It's not the only miner available.

Good work deserve to be retributed.

But you are probably a man you love movies, but download them all.
Or love video games and crack them all.
No effort and all for free is not how this works
I hope you can understand that

Who is the greedy one?  The person wanting something for nothing? Or the person who provided us a service and continues to do so.  I will never understand this argument of the developer being greedy. If you don't agree with it just don't use it.  If you can't afford the developer fee this def is not the line of work you should be in. Maybe go work for someone else. I mean company owners give 100% to the employees right?/s.  Just so tired of the threads getting filled with useless comments on the fees. 

BR
d57heinz

no ther isnt

The ZEC miner does not work with nVidia. The ETH miner work with nVidia.

 ZEC isn't memory limited - unlike ETH - so trying to dual-mine it isn't going to work well with anything.

 The ONLY reason ETH can be dual-mined effectively is that it's not pushing the GPU cores very hard, so they have a fair bit of room to "play with" doing other stuff at the same time, as long as that "other stuff" doesn't push the memory interface very hard.

 In any event, Claymore doesn't work with NVidia cards, he's strictly AMD.

This looks pretty interesting man. Thank you for taking the time to write this, and for sharing it

 claymore's  A greedy bastard But its commissions can be turned off 100%, there is a modified miner 8-)

Tool for hashrate / GPU temperature / Fan speeds analysis

---

Hey guys. I've just uploaded the small pyhon script that parses this miner's log files and builds an interactive graphs using this data.
https://ibb.co/gwR9oQ

It allows you to:

• easily check if everything was fine with temps
• evaluate the average hashrate for your hardware
• verify your pools's statistics. To be specific, it lets you check how much your mining performance reported by that pool corellate with the actual hardware performance

It's more of a prototype than a complete application. But it's already useable and works just fine.
Most likely "professional miners" won't need it. Since they already have something similar made by themselves.
But it may be useful for beginners.

It's interactive so you can zoom/pan the graphs.
https://ibb.co/df8xSk
https://ibb.co/g1XkDQ

Download on github: https://github.com/Lex-DRL/mining-graph/releases
Installation instructions: https://github.com/Lex-DRL/mining-graph

P.S.: sorry for my broken english, I'm a russian native speaker.

More than 24h is giving this error.

Help me...



15:33:38:718   1c38   ZEC: Stratum - Connected (zec.pool.minergate.com:3357) (unsecure)
15:33:38:929   1c38   got 59 bytes
15:33:38:930   1c38   buf: {"id": 1, "result": ["283357", "00000000"], "error": null}

15:33:38:931   1c38   parse packet: 52
15:33:38:931   1c38   new buf size: 0
15:33:39:162   1c38   got 165 bytes
15:33:39:163   1c38   buf: {"id": 2, "result": true, "error": null}
{"id": null, "method": "mining.set_target", "params": ["0040000000000000000000000000000000000000000000000000000000000000"]}

15:33:39:164   1c38   parse packet: 35
15:33:39:165   1c38   ZEC: Authorized
15:33:39:166   1c38   remove first packet 119
15:33:39:167   1c38   new buf size: 119
15:33:39:168   1c38   parse packet: 118
15:33:39:169   1c38   Pool sets new share target: 0x00400000 (diff: 1023H)
15:33:39:170   1c38   new buf size: 0
15:33:42:181   1c38   checkread timeout
15:33:45:192   1c38   checkread timeout
15:33:48:203   1c38   checkread timeout
15:33:51:215   1c38   checkread timeout
15:33:54:226   1c38   checkread timeout
15:33:55:150   119c   GPU0 t=54C fan=39%
15:33:55:151   119c   em hbt: 16661, fm hbt: 16,
15:33:55:153   119c   watchdog - thread 0, hb time 31
15:33:55:155   119c   watchdog - thread 1, hb time 31
15:33:55:156   119c   watchdog - thread 2, hb time 31
15:33:55:157   119c   watchdog - thread 3, hb time 16
15:33:57:237   1c38   checkread timeout
15:34:00:248   1c38   checkread timeout
15:34:03:259   1c38   checkread timeout
15:34:03:260   1c38   ZEC: Job timeout, disconnect, retry in 20 sec...
15:34:13:396   1c70   Quit...



Is there a problem with the minergate?

That speed is OK.

280-290 h/s is ok for msi 280x ? or i can get more ?
and is there some list for GPU's hashrate?

Is anyone having a similar problem to this: One of my 280x cards suddenly started freezing the miner and windows as soon as it starts hashing. If I put -li option it hashes a bit longer but again hangs. I tried several different risers and different psu, installed newer drivers but still the same result. Then I dissasembled and reassebled again the card. I put it back again and here we go... it works perfectly untill now (2 months later). Now, the funny part: the same problem happened to another 2 cards of the same rig. Unfortunately this trick doesn't work on them What may be the reason for that? Is it possible that the thermal paste has something to do with it?

$350 for fury is reasonable.

Ok, thank you, I will let it mine one day. I'm quite curious 

About 25 hours or so...

So I have to mine at least 0.01 zec for it to be added to my wallet? How long does it take approx on 280H/s?

Your GPU is just too old. With that GPU you can only mine maybe XMR.

minimum payout 0.01

Hi there, I've been mining for 3 hours for my jaxx wallet and then 3 hours for my cryptonator wallet, but I don't see any balance on either of my wallet. I mean... there should be at least 0.00000001 zec or so, shouldn't it? Am I doing something wrong? Or does it take some time to appear in my wallet? (both times used zcash address as a -zwal parameter)

I am trying to run Claymore on my AMD 6950 but I am having problems. It is a 1GB card so it sets the intensity down to 1, which is fine. However, v12.5 starts spamming "gpu returned incorrect data". If I use v11.1 it works but my hashrate is ~5 H/s.