Search content
Sort by

Showing 6 of 6 results by gh05t77
Post
Topic
Board Exchanges
Re: CEX.IO Withdrawal times - any experience?
by
gh05t77
on 29/01/2018, 15:30:58 UTC
I try to withdraw USD to my verified VISA card, but my request rejected.
I tried to do it several days and with different amount, but all time it was rejected instantly.
Why it happens? I did not received any answer on my ticket 645698 from support.

Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.7 (Windows/Linux)
by
gh05t77
on 17/07/2017, 17:33:24 UTC


What is wrong with AMD GPU at Dual Mining ?

My Dual Mining Settings:
EthDcrMiner64.exe -epool eth-eu1.nanopool.org:9999 -ewal MyAdress -epsw x -dcoin sia -dpool stratum+tcp://sia-eu1.nanopool.org:7777 -dwal MyAdress  -dpsw x -ftime 10

Try to play with -dcri key. Set it about -dcri 10 and press + / - in miner window to find the best value
Post
Topic
Board Mining (Altcoins)
Re: Poloniex zcash temporarily disabled
by
gh05t77
on 17/07/2017, 09:08:30 UTC
Now all working good
Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.7 (Windows/Linux)
by
gh05t77
on 17/07/2017, 08:57:42 UTC
Dear Claymore
Please, pay attention on dramatically decrease hash rate with epoch growth.
I test it on my rig with 3 RX580 4Gb (use -benchmark key) and here are results:
epoch #120 ETH: GPU0 29.380 Mh/s, GPU1 29.532 Mh/s, GPU2 29.944 Mh/s
epoch #130 ETH: GPU0 29.146 Mh/s, GPU1 29.273 Mh/s, GPU2 29.700 Mh/s
epoch #140 ETH: GPU0 27.567 Mh/s, GPU1 27.664 Mh/s, GPU2 27.992 Mh/s
epoch #160 ETH: GPU0 21.309 Mh/s, GPU1 21.397 Mh/s, GPU2 21.666 Mh/s
epoch #180 ETH: GPU0 18.493 Mh/s, GPU1 18.509 Mh/s, GPU2 18.795 Mh/s

So very shortly we got decrease hash rate on 5% (between epoch #130 and #140).
Please fix this bug or explain what to do.


That isn't a bug. As epoch goes up, hashrate of many amd gpu's goes down. It is known.  Cheesy

I run benchmark on RX480 8Gb and got the same results. So it's not depend of memory size.
Does this problem have NVIDIA cards too?
Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.7 (Windows/Linux)
by
gh05t77
on 16/07/2017, 20:53:19 UTC
Dear Claymore
Please, pay attention on dramatically decrease hash rate with epoch growth.
I test it on my rig with 3 RX580 4Gb (use -benchmark key) and here are results:
epoch #120 ETH: GPU0 29.380 Mh/s, GPU1 29.532 Mh/s, GPU2 29.944 Mh/s
epoch #130 ETH: GPU0 29.146 Mh/s, GPU1 29.273 Mh/s, GPU2 29.700 Mh/s
epoch #140 ETH: GPU0 27.567 Mh/s, GPU1 27.664 Mh/s, GPU2 27.992 Mh/s
epoch #160 ETH: GPU0 21.309 Mh/s, GPU1 21.397 Mh/s, GPU2 21.666 Mh/s
epoch #180 ETH: GPU0 18.493 Mh/s, GPU1 18.509 Mh/s, GPU2 18.795 Mh/s

So very shortly we got decrease hash rate on 5% (between epoch #130 and #140).
Please fix this bug or explain what to do.
Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.4 (Windows/Linux)
by
gh05t77
on 28/05/2017, 11:02:43 UTC
Thank you very much for you cool miner.

I using v.9.3. for dual mining ETH+Pasc and notice this strange behavior:


I.  In the log I see some enonce but miner send to pool other one:

11:30:46:478   10f0   PASC: put share nonce 30909ba enonce 275
11:30:46:497   10f0   PASC round found 1 shares
11:30:46:515   330    PASC: 05/28/17-11:30:46 - SHARE FOUND - (GPU 2)
11:30:46:515   330   send: {"params": ["yfife5.wm", "1002", "3237643030303030", "592A8AB3", "ba090903"], "id": 4, "method": "mining.submit"}

Here enonce= "275" but send "27d00000" (if convert to ASCII).  And it happens all time. Send "enonce + 8" (275+8 = 27d)

II. But the worth thing is when enonce growth out of 3 digit. The miner continue send (and calculate) only first 3 digit:

11:34:03:392   139c   PASC: put share nonce 30909ba enonce 27c8
11:34:03:392   139c   PASC round found 1 shares
11:34:03:408   330    PASC: 05/28/17-11:34:03 - SHARE FOUND - (GPU 0)
11:34:03:408   330   send: {"params": ["yfife5.wm", "1002", "3237643030303030", "592A8AB3", "ba090903"], "id": 4, "method": "mining.submit"}

You can see here the same nonce as in previous example, but enonce must be "27c8" but sending the same "27d00000". (actually miner works correct 27c8+8 = 27d0, but when adding "0000" it looks like "27d" + "00000").

So can you add "0" before enonce, like this "000027d0". It will increase real hashrate by 1/16 (6.25%), because now we calculate the same hashes for different enonce (each hash for enonce "xx" equal hash for enonce "xx8").

Also, will be good, to add solo mining mode for Pascal.