Ninjastic
Search content
Sort by
Showing 16 of 16 results by gglala
Post
Topic
Board Hardware
Re: Pangolinminer & Whatsminer FAQs
by
gglala
on 03/04/2018, 13:38:54 UTC
Quote from: HagssFIN on April 03, 2018, 06:05:34 AM
What wire gauge does the power cord from socket to psu have?

It’s the cable provider by Pangolinminer together with the M3 and PSU.
Post
Topic
Board Hardware
Re: Pangolinminer & Whatsminer FAQs
by
gglala
on 03/04/2018, 01:42:28 UTC
Thanks and the electrician confirmed it’s 2.5mm2 wiring and the socket is working. However the plug of the power cable to M3 burnt after running for more than 36 hours. What else can be done to rectify this?
Post
Topic
Board Hardware
Re: Pangolinminer & Whatsminer FAQs
by
gglala
on 03/04/2018, 00:05:44 UTC
Quote from: HagssFIN on April 02, 2018, 04:33:24 PM
Quote from: Vene on April 02, 2018, 04:23:34 PM
Quote from: gglala on April 02, 2018, 10:31:20 AM
Hi all,
I tried with a host for my M3s that I received 2 weeks ago but there’s not much luck What happened is that after running for 24 to 48 hours straight, the cables got burnt out once, another time the fuse of the socket got burnt. Anyone has similar challenge or able to advise how to overcome this? Thanks

Guys you need to do some homework before runing a miner or you will ger your house burnt down. So M3 drains approx 2200w, if you are on 230v you should use 1,5mm2 cables. It should be rated 16amps. It should be also in a power circuit that is protected with 16A fuse.
Wrong.

1.5 mm2 - Max. circuit breaker size: 10 Amps

2.5 mm2 - Max. circuit breaker size: 16 Amps

This is how it is done in installations which comply with the IEC standards.

Thanks for the advice. Can I please confirm if this 2.5mm2 cable is for electrical wiring from the DB breaker to the socket or for the power cord cable to connect from M3 to the socket?
Post
Topic
Board Hardware
Re: Pangolinminer & Whatsminer FAQs
by
gglala
on 02/04/2018, 10:31:20 UTC
Hi all,
I tried with a host for my M3s that I received 2 weeks ago but there’s not much luck What happened is that after running for 24 to 48 hours straight, the cables got burnt out once, another time the fuse of the socket got burnt. Anyone has similar challenge or able to advise how to overcome this? Thanks
Post
Topic
Board Mining (Altcoins)
Re: Very first tests P104-100: 39 Mh/s ETH; 470 sol/s ZEC - Nice GPU!
by
gglala
on 11/02/2018, 13:30:15 UTC
Quote from: cnilsecure on February 06, 2018, 04:25:50 AM
Hi,

I am kinda new here (as a registered user that is), I had to reply to this p-104 trend that been going on here.
so let me tell you I have no idea what is unique "bios" who is getting to 39mhs...

I have made some changes today we are running a machine with 8 cards P-104 (44-43 mhs per card) reaching
easily to 345 mhs not to mention running on 160watts instead of 180watts with linux centos.

I am using a private version of ethminer here are some screen shots from the teamviewer.
https://imgur.com/gallery/SwKM6U0

https://imgur.com/gallery/YvkfGym

Best regards,

CNILSECURE.

P.S. Sorry i havent figure out yet how to insert the image directly to here

What is your overclock setting like?
Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.6 (Windows/Linux)
by
gglala
on 09/02/2018, 05:07:56 UTC
Quote from: dollos on February 08, 2018, 11:26:08 AM
the above is because you have overclocked too much. startthe mem overclock at 100mhz run for a few days and see if this occurs and beleive me this will not happen . you need to find that one card that is moaning...

Thanks and I’ve been trying to reduce it each time but not getting it right. I finally tried to limit power to 85%, core +100 and memory +650. Been running for more than 5 hours without issue so far. Smiley
Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.6 (Windows/Linux)
by
gglala
on 08/02/2018, 10:37:34 UTC
@claymore any advice on the below error?

Quote from: gglala on February 05, 2018, 03:09:40 PM
Dear all, need your advice on my new rig. I constantly get the following error message and the miner restarts itself, which is a good thing instead of just hanging and sit idle. This happens as short as 2 hours or up to 5 hours. Tried searching around but yet to find any solutions. Thanks.

quote
21:09:47:912   16b8   ETH: checking pool connection...
21:09:47:991   16b8   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:09:48:288   16b8   got 243 bytes
21:09:48:397   16b8   buf: {"jsonrpc":"2.0","id":0,"result":["0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

21:09:48:491   16b8   parse packet: 242
21:09:48:569   16b8   ETH: job is the same
21:09:48:662   16b8   new buf size: 0
21:09:51:397   18b8   ETH: put share nonce 31272c01dbf3959
21:09:51:491   9b0   GPU 3, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:569   1b34   GPU 0, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:663   2a8   GPU 6, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:757   d18   GPU 4, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:835   226c   GPU 5, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:491   18b8   ETH round found 1 shares
21:09:52:007   16b8   ETH: 02/05/18-21:09:51 - SHARE FOUND - (GPU 5)
21:09:52:085   16b8   send: {"id":15,"method":"eth_submitWork","params":["0x031272c01dbf3959","0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb1c8e687425ef63e31ab56f46f302ed8f5c949eba43483f0f118681f19b06c97"]}

21:09:52:178   2d10   GPU 1, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:52:272   1e5c   GPU 7, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:52:350   9b0   GPU 3, GpuMiner kx failed 1
21:09:52:429   1b34   GPU 0, GpuMiner kx failed 1
21:09:52:522   2a8   GPU 6, GpuMiner kx failed 1
21:09:52:600   d18   GPU 4, GpuMiner kx failed 1
21:09:52:694   226c   GPU 5, GpuMiner kx failed 1
21:09:52:772   16bc   GPU 2, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:52:866   2d10   GPU 1, GpuMiner kx failed 1
21:09:52:944   1e5c   GPU 7, GpuMiner kx failed 1
21:09:52:397   16b8   got 40 bytes
21:09:53:116   16b8   buf: {"jsonrpc":"2.0","id":15,"result":true}

21:09:53:194   16b8   parse packet: 39
21:09:53:272   16b8   ETH: Share accepted (1094 ms)!

21:09:53:366   16b8   new buf size: 0
21:09:52:772   226c   Set global fail flag, failed GPU5
21:09:53:522   16bc   GPU 2, GpuMiner kx failed 1
21:09:52:944   2d10   Set global fail flag, failed GPU1
21:09:53:022   1e5c   Set global fail flag, failed GPU7
21:09:52:429   9b0   Set global fail flag, failed GPU3
21:09:52:522   1b34   Set global fail flag, failed GPU0
21:09:52:600   2a8   Set global fail flag, failed GPU6
21:09:52:694   d18   Set global fail flag, failed GPU4
21:09:54:116   18b8   GPU 5, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:194   226c   GPU 5 failed
21:09:53:616   16bc   Set global fail flag, failed GPU2
21:09:54:366   1984   GPU 1, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:460   2d10   GPU 1 failed
21:09:54:538   2a7c   GPU 7, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:616   1e5c   GPU 7 failed
21:09:54:710   20cc   GPU 3, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:788   9b0   GPU 3 failed
21:09:54:882   208   GPU 0, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:960   1b34   GPU 0 failed
21:09:55:038   28b8   GPU 6, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:55:132   2a8   GPU 6 failed
21:09:55:210   2cb0   GPU 4, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:55:288   d18   GPU 4 failed
21:09:55:382   18b8   GPU 5, GpuMiner kx failed 1
21:09:55:460   2b90   GPU 2, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:55:538   16bc   GPU 2 failed
21:09:55:632   1984   GPU 1, GpuMiner kx failed 1
21:09:55:710   2a7c   GPU 7, GpuMiner kx failed 1
21:09:55:804   20cc   GPU 3, GpuMiner kx failed 1
21:09:55:882   208   GPU 0, GpuMiner kx failed 1
21:09:55:976   28b8   GPU 6, GpuMiner kx failed 1
21:09:56:054   2cb0   GPU 4, GpuMiner kx failed 1
21:09:55:460   18b8   Set global fail flag, failed GPU5
21:09:56:226   2b90   GPU 2, GpuMiner kx failed 1
21:09:55:710   1984   Set global fail flag, failed GPU1
21:09:55:804   2a7c   Set global fail flag, failed GPU7
21:09:55:882   20cc   Set global fail flag, failed GPU3
21:09:55:976   208   Set global fail flag, failed GPU0
21:09:56:054   28b8   Set global fail flag, failed GPU6
21:09:56:132   2cb0   Set global fail flag, failed GPU4
21:09:56:820   18b8   GPU 5 failed
21:09:56:304   2b90   Set global fail flag, failed GPU2
21:09:56:991   1984   GPU 1 failed
21:09:57:070   2a7c   GPU 7 failed
21:09:57:148   20cc   GPU 3 failed
21:09:57:242   208   GPU 0 failed
21:09:57:320   28b8   GPU 6 failed
21:09:57:398   2cb0   GPU 4 failed
21:09:57:492   2b90   GPU 2 failed
21:09:57:085   4fc   srv_thr cnt: 1, IP: 127.0.0.1
21:09:57:648   4fc   recv: 60
21:09:57:742   4fc   srv pck: 59
21:09:57:835   4fc   srv bs: 0
21:09:57:913   4fc   sent: 241
21:09:57:929   16b8   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x00000000000000000000000000000000000000000000000000000000d2e3fbe7"]}

21:09:58:085   1dcc   GPU0 t=51C fan=75%, GPU1 t=57C fan=75%, GPU2 t=56C fan=75%, GPU3 t=57C fan=74%, GPU4 t=52C fan=74%, GPU5 t=54C fan=75%, GPU6 t=57C fan=74%, GPU7 t=52C fan=74%
21:09:58:101   16b8   ETH: checking pool connection...
21:09:58:257   16b8   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:09:58:539   16b8   got 243 bytes
21:09:58:617   16b8   buf: {"jsonrpc":"2.0","id":0,"result":["0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

21:09:58:695   16b8   parse packet: 242
21:09:58:789   16b8   ETH: job is the same
21:09:58:867   16b8   new buf size: 0
21:10:08:352   16b8   ETH: checking pool connection...
21:10:08:430   16b8   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:10:08:727   16b8   got 243 bytes
21:10:08:805   16b8   buf: {"jsonrpc":"2.0","id":0,"result":["0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

21:10:08:883   16b8   parse packet: 242
21:10:08:977   16b8   ETH: job is the same
21:10:09:055   16b8   new buf size: 0
21:10:09:102   ae0   got 484 bytes
21:10:09:227   ae0   buf: {"method":"mining.notify","params":["7d5","0000000000000000000000000000000000000000000000000000000000000000","32AF0200CA02200042B6D71C8BDD83EB6DAB79713BCFCFF330C4AB5BA2BB7B7C02A30882B54E31E 62000CA1FF7B7804CE8BC3AFA0C5A7F7F72E372C30A3A3FFAC81563C67672781D2DFD40420F0000 00000002000200E02B0736","0FC510114C3C9EC4B844C4DFF39C4A2018F413126F58AF73F62D818C467355B7E3B0C44298FC1C1 49AFBF4C8996FB92427AE41E4649B934CA495991B7852B85500000000",[],"00000000","24000000","5a7857b0",true],"id":null}

21:10:09:305   ae0   parse packet: 483
21:10:09:383   ae0   new buf size: 0
21:10:09:477   ae0    PASC: 02/05/18-21:10:09 - New job from pasc-asia1.nanopool.org:15555
21:10:09:555   ae0   target: 0x000000000ffff000 (diff: 68GH)
21:10:10:540   52c   em hbt: 16, dm hbt: 16, fm hbt: 78,
21:10:10:618   52c   watchdog - thread 0 (gpu0), hb time 19266
21:10:10:696   52c   watchdog - thread 1 (gpu0), hb time 19234
21:10:10:790   52c   watchdog - thread 2 (gpu1), hb time 19328
21:10:10:868   52c   watchdog - thread 3 (gpu1), hb time 19516
21:10:10:962   52c   watchdog - thread 4 (gpu2), hb time 19594
21:10:11:040   52c   watchdog - thread 5 (gpu2), hb time 19578
21:10:11:118   52c   watchdog - thread 6 (gpu3), hb time 19750
21:10:11:212   52c   watchdog - thread 7 (gpu3), hb time 19938
21:10:11:290   52c   watchdog - thread 8 (gpu4), hb time 19953
21:10:11:368   52c   watchdog - thread 9 (gpu4), hb time 19938
21:10:11:446   52c   watchdog - thread 10 (gpu5), hb time 20125
21:10:11:540   52c   watchdog - thread 11 (gpu5), hb time 19532
21:10:11:618   52c   watchdog - thread 12 (gpu6), hb time 20188
21:10:11:712   52c   watchdog - thread 13 (gpu6), hb time 20375
21:10:11:790   52c   watchdog - thread 14 (gpu7), hb time 20328
21:10:11:884   52c   watchdog - thread 15 (gpu7), hb time 20531
21:10:11:962   52c   WATCHDOG: GPU error, you need to restart miner Sad
21:10:15:056   52c   Restarting OK, exit...
unquote

Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.6 (Windows/Linux)
by
gglala
on 05/02/2018, 15:09:40 UTC
Dear all, need your advice on my new rig. I constantly get the following error message and the miner restarts itself, which is a good thing instead of just hanging and sit idle. This happens as short as 2 hours or up to 5 hours. Tried searching around but yet to find any solutions. Thanks.

quote
21:09:47:912   16b8   ETH: checking pool connection...
21:09:47:991   16b8   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:09:48:288   16b8   got 243 bytes
21:09:48:397   16b8   buf: {"jsonrpc":"2.0","id":0,"result":["0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

21:09:48:491   16b8   parse packet: 242
21:09:48:569   16b8   ETH: job is the same
21:09:48:662   16b8   new buf size: 0
21:09:51:397   18b8   ETH: put share nonce 31272c01dbf3959
21:09:51:491   9b0   GPU 3, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:569   1b34   GPU 0, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:663   2a8   GPU 6, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:757   d18   GPU 4, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:835   226c   GPU 5, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:51:491   18b8   ETH round found 1 shares
21:09:52:007   16b8   ETH: 02/05/18-21:09:51 - SHARE FOUND - (GPU 5)
21:09:52:085   16b8   send: {"id":15,"method":"eth_submitWork","params":["0x031272c01dbf3959","0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb1c8e687425ef63e31ab56f46f302ed8f5c949eba43483f0f118681f19b06c97"]}

21:09:52:178   2d10   GPU 1, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:52:272   1e5c   GPU 7, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:52:350   9b0   GPU 3, GpuMiner kx failed 1
21:09:52:429   1b34   GPU 0, GpuMiner kx failed 1
21:09:52:522   2a8   GPU 6, GpuMiner kx failed 1
21:09:52:600   d18   GPU 4, GpuMiner kx failed 1
21:09:52:694   226c   GPU 5, GpuMiner kx failed 1
21:09:52:772   16bc   GPU 2, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:52:866   2d10   GPU 1, GpuMiner kx failed 1
21:09:52:944   1e5c   GPU 7, GpuMiner kx failed 1
21:09:52:397   16b8   got 40 bytes
21:09:53:116   16b8   buf: {"jsonrpc":"2.0","id":15,"result":true}

21:09:53:194   16b8   parse packet: 39
21:09:53:272   16b8   ETH: Share accepted (1094 ms)!

21:09:53:366   16b8   new buf size: 0
21:09:52:772   226c   Set global fail flag, failed GPU5
21:09:53:522   16bc   GPU 2, GpuMiner kx failed 1
21:09:52:944   2d10   Set global fail flag, failed GPU1
21:09:53:022   1e5c   Set global fail flag, failed GPU7
21:09:52:429   9b0   Set global fail flag, failed GPU3
21:09:52:522   1b34   Set global fail flag, failed GPU0
21:09:52:600   2a8   Set global fail flag, failed GPU6
21:09:52:694   d18   Set global fail flag, failed GPU4
21:09:54:116   18b8   GPU 5, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:194   226c   GPU 5 failed
21:09:53:616   16bc   Set global fail flag, failed GPU2
21:09:54:366   1984   GPU 1, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:460   2d10   GPU 1 failed
21:09:54:538   2a7c   GPU 7, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:616   1e5c   GPU 7 failed
21:09:54:710   20cc   GPU 3, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:788   9b0   GPU 3 failed
21:09:54:882   208   GPU 0, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:54:960   1b34   GPU 0 failed
21:09:55:038   28b8   GPU 6, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:55:132   2a8   GPU 6 failed
21:09:55:210   2cb0   GPU 4, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:55:288   d18   GPU 4 failed
21:09:55:382   18b8   GPU 5, GpuMiner kx failed 1
21:09:55:460   2b90   GPU 2, GpuMiner cu_k03 failed 73, an illegal instruction was encountered
21:09:55:538   16bc   GPU 2 failed
21:09:55:632   1984   GPU 1, GpuMiner kx failed 1
21:09:55:710   2a7c   GPU 7, GpuMiner kx failed 1
21:09:55:804   20cc   GPU 3, GpuMiner kx failed 1
21:09:55:882   208   GPU 0, GpuMiner kx failed 1
21:09:55:976   28b8   GPU 6, GpuMiner kx failed 1
21:09:56:054   2cb0   GPU 4, GpuMiner kx failed 1
21:09:55:460   18b8   Set global fail flag, failed GPU5
21:09:56:226   2b90   GPU 2, GpuMiner kx failed 1
21:09:55:710   1984   Set global fail flag, failed GPU1
21:09:55:804   2a7c   Set global fail flag, failed GPU7
21:09:55:882   20cc   Set global fail flag, failed GPU3
21:09:55:976   208   Set global fail flag, failed GPU0
21:09:56:054   28b8   Set global fail flag, failed GPU6
21:09:56:132   2cb0   Set global fail flag, failed GPU4
21:09:56:820   18b8   GPU 5 failed
21:09:56:304   2b90   Set global fail flag, failed GPU2
21:09:56:991   1984   GPU 1 failed
21:09:57:070   2a7c   GPU 7 failed
21:09:57:148   20cc   GPU 3 failed
21:09:57:242   208   GPU 0 failed
21:09:57:320   28b8   GPU 6 failed
21:09:57:398   2cb0   GPU 4 failed
21:09:57:492   2b90   GPU 2 failed
21:09:57:085   4fc   srv_thr cnt: 1, IP: 127.0.0.1
21:09:57:648   4fc   recv: 60
21:09:57:742   4fc   srv pck: 59
21:09:57:835   4fc   srv bs: 0
21:09:57:913   4fc   sent: 241
21:09:57:929   16b8   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x00000000000000000000000000000000000000000000000000000000d2e3fbe7"]}

21:09:58:085   1dcc   GPU0 t=51C fan=75%, GPU1 t=57C fan=75%, GPU2 t=56C fan=75%, GPU3 t=57C fan=74%, GPU4 t=52C fan=74%, GPU5 t=54C fan=75%, GPU6 t=57C fan=74%, GPU7 t=52C fan=74%
21:09:58:101   16b8   ETH: checking pool connection...
21:09:58:257   16b8   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:09:58:539   16b8   got 243 bytes
21:09:58:617   16b8   buf: {"jsonrpc":"2.0","id":0,"result":["0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

21:09:58:695   16b8   parse packet: 242
21:09:58:789   16b8   ETH: job is the same
21:09:58:867   16b8   new buf size: 0
21:10:08:352   16b8   ETH: checking pool connection...
21:10:08:430   16b8   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:10:08:727   16b8   got 243 bytes
21:10:08:805   16b8   buf: {"jsonrpc":"2.0","id":0,"result":["0xfa97d85090728cba653f36496f8395cd4e120d4dfc4ebf62ef84ff8a1a83c70d","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

21:10:08:883   16b8   parse packet: 242
21:10:08:977   16b8   ETH: job is the same
21:10:09:055   16b8   new buf size: 0
21:10:09:102   ae0   got 484 bytes
21:10:09:227   ae0   buf: {"method":"mining.notify","params":["7d5","0000000000000000000000000000000000000000000000000000000000000000","32AF0200CA02200042B6D71C8BDD83EB6DAB79713BCFCFF330C4AB5BA2BB7B7C02A30882B54E31E 62000CA1FF7B7804CE8BC3AFA0C5A7F7F72E372C30A3A3FFAC81563C67672781D2DFD40420F0000 00000002000200E02B0736","0FC510114C3C9EC4B844C4DFF39C4A2018F413126F58AF73F62D818C467355B7E3B0C44298FC1C1 49AFBF4C8996FB92427AE41E4649B934CA495991B7852B85500000000",[],"00000000","24000000","5a7857b0",true],"id":null}

21:10:09:305   ae0   parse packet: 483
21:10:09:383   ae0   new buf size: 0
21:10:09:477   ae0    PASC: 02/05/18-21:10:09 - New job from pasc-asia1.nanopool.org:15555
21:10:09:555   ae0   target: 0x000000000ffff000 (diff: 68GH)
21:10:10:540   52c   em hbt: 16, dm hbt: 16, fm hbt: 78,
21:10:10:618   52c   watchdog - thread 0 (gpu0), hb time 19266
21:10:10:696   52c   watchdog - thread 1 (gpu0), hb time 19234
21:10:10:790   52c   watchdog - thread 2 (gpu1), hb time 19328
21:10:10:868   52c   watchdog - thread 3 (gpu1), hb time 19516
21:10:10:962   52c   watchdog - thread 4 (gpu2), hb time 19594
21:10:11:040   52c   watchdog - thread 5 (gpu2), hb time 19578
21:10:11:118   52c   watchdog - thread 6 (gpu3), hb time 19750
21:10:11:212   52c   watchdog - thread 7 (gpu3), hb time 19938
21:10:11:290   52c   watchdog - thread 8 (gpu4), hb time 19953
21:10:11:368   52c   watchdog - thread 9 (gpu4), hb time 19938
21:10:11:446   52c   watchdog - thread 10 (gpu5), hb time 20125
21:10:11:540   52c   watchdog - thread 11 (gpu5), hb time 19532
21:10:11:618   52c   watchdog - thread 12 (gpu6), hb time 20188
21:10:11:712   52c   watchdog - thread 13 (gpu6), hb time 20375
21:10:11:790   52c   watchdog - thread 14 (gpu7), hb time 20328
21:10:11:884   52c   watchdog - thread 15 (gpu7), hb time 20531
21:10:11:962   52c   WATCHDOG: GPU error, you need to restart miner Sad
21:10:15:056   52c   Restarting OK, exit...
unquote
Post
Topic
Board Mining (Altcoins)
Re: Very first tests P104-100: 39 Mh/s ETH; 470 sol/s ZEC - Nice GPU!
by
gglala
on 03/02/2018, 09:12:20 UTC
Quote from: smoolae on February 02, 2018, 06:27:35 AM
Quote from: Q_R_V on February 02, 2018, 04:10:02 AM
Quote from: gglala on February 02, 2018, 02:46:03 AM


Silly question, I’m using free version of W10 and not activated on the key yet. Will that make a difference to driver compatibility and reading by the OS? Does getting the official key and having it installed make a better difference?

There should be no difference at all.
No difference, been mining with unlicensed Win 10 for some time now.
Thanks to all of your help. It was due to my W10 installer on older version, an upgrade fixed it and driver installed.

Mining dual coin with claymore 10.6 gets about 36mh/s for p104 but the claymore hanged and kept resetting with 0 hashrate though temperature of all GPUs showing. Trying now again with version 10.5.
Post
Topic
Board Mining (Altcoins)
Re: Very first tests P104-100: 39 Mh/s ETH; 470 sol/s ZEC - Nice GPU!
by
gglala
on 02/02/2018, 02:46:03 UTC
Quote from: Q_R_V on February 02, 2018, 01:44:46 AM
Quote from: gglala on February 02, 2018, 12:35:26 AM

Thanks I will try it again later. By the way I just started this new rig with new installation of W10 on biostar 250 btc pro MB. Is there other app or software I need to install in order for the Nvidia app to run smooth installation after download of the Driver?

Driver and msi afterburner is all you need.

Silly question, I’m using free version of W10 and not activated on the key yet. Will that make a difference to driver compatibility and reading by the OS? Does getting the official key and having it installed make a better difference?
Post
Topic
Board Mining (Altcoins)
Re: Very first tests P104-100: 39 Mh/s ETH; 470 sol/s ZEC - Nice GPU!
by
gglala
on 02/02/2018, 00:35:26 UTC
Quote from: Q_R_V on February 01, 2018, 11:55:20 PM
Quote from: gglala on February 01, 2018, 11:37:33 PM
Dear all, I just got my p104 cards yesterday however having problem getting my Windows 10 to recognise it. I tried using 390.77 Driver version but Nvidia said the Driver is not compatible with my system.

Can you please advise how and where to download the Drivers for the p104? Thanks in advance!

Works fine for Palit p104-100:
http://www.nvidia.com/download/driverResults.aspx/129081/en-us


Thanks I will try it again later. By the way I just started this new rig with new installation of W10 on biostar 250 btc pro MB. Is there other app or software I need to install in order for the Nvidia app to run smooth installation after download of the Driver?
Post
Topic
Board Mining (Altcoins)
Re: Very first tests P104-100: 39 Mh/s ETH; 470 sol/s ZEC - Nice GPU!
by
gglala
on 01/02/2018, 23:37:33 UTC
Dear all, I just got my p104 cards yesterday however having problem getting my Windows 10 to recognise it. I tried using 390.77 Driver version but Nvidia said the Driver is not compatible with my system.

Can you please advise how and where to download the Drivers for the p104? Thanks in advance!
Post
Topic
Board Mining (Altcoins)
Re: Owners of GTX 1060, what is your hashrate?
by
gglala
on 23/11/2017, 04:22:24 UTC
Sorry for my non tech language. It is TechPowerUp GPU-Z.
Post
Topic
Board Mining (Altcoins)
Re: Owners of GTX 1060, what is your hashrate?
by
gglala
on 23/11/2017, 02:10:46 UTC
Dear all,
How do I set my GPU to be read in the MSI afterburner etc? I have downloaded TECHGPU app but the readings do not show up when I ran it, not the speed etc..

And currently, my 1060 6GB GPU is running at 20.8Mh/s at about 70-73C, fan power is about 55-57%. Is this temperature still ambient or too high? Thanks to help.

Newbie to mining here.
Post
Topic
Board Mining (Altcoins)
Re: Claymore's ZCash/BTG GPU Miner v12.6 (Windows/Linux)
by
gglala
on 23/11/2017, 02:03:44 UTC
The error message is from a pop up window after I double clicked on the zecminer64.exe application.

"Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item."

Even if I ran the file as administrator, same error message.
Post
Topic
Board Mining (Altcoins)
Re: Claymore's ZCash/BTG GPU Miner v12.6 (Windows/Linux)
by
gglala
on 22/11/2017, 15:41:37 UTC
Dear all,
I need some help with the zecminer64. I downloaded the files for claymore and updated the wallet etc. When I ran the zecminer64.exe, it does not work and has error message saying the path cannot be found. Any advice on how to fix this?