Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 456. (Read 784877 times)

@PhoenixMiner

Thank you for your continuing development of this great miner

I found 2.7c very good although I had 1 problem today we had a power cut lost internet connection. Now that 2.7c is SSL enabled which we were using. We found that looking at console when the system loses internet connectivity the miner tries to resolve addresses, but it seems to look for port 4444 as though somewhere specified as default pool in the miner exe itself. It then hangs because it could not connect to that being SSL enabled. I didn't get chance to test again just stopped miner and restarted making sure we had connectivity and the miner carried on as normal.

What I have done now is set a fail over second pool being same eu address with 5555 in the hope that if it fails again in might try this before trying to resolve the 4444 port. Just a heads up if you need to look into this at all in the event that this might happen leaving the miner hanging.

The miner now reports on start up 4 pools specified. So somewhere there are 2 otherwise specified in the code I persume.

Tried 2.7c for 10mins. Within 1 min, 1 of my RX580 dropped from 30.5mh/s to 24mh/s and remain at that speed. Temp same as using ver 2.6. Infact I used same bat. file as ver 2.6.

Revert back to 2.6 immediately and hashrate goes up to 30.5mh/s for that gpu. My rig consist of mix of gtx 1070s and rx 580s in one rig.

Will continue using 2.6 until 2.7c becomes better.

Definitely this miner will bypass claymore! Thanks Mr. Dev! You've done a great job!!

Hello guys . Yesterday i installed the new version 2.7c , and i let the miner for 5 hours ... He found only 92 shares , compared to claymore , claymore found 181 shares in 5 hours . Should i go back to 2.6 ?

Yes 391.01 now, but i have same results with both versions and older versions. I have tried everything.

you mean 390.77 && 391.01?

I have used older and the latest 390.01

[/quote]

similar here, just haven't checked w/o OC. i wonder if there's issues with the 1070's and 2.7c .. what version of windows drivers are you using?
[/quote]

similar here, just haven't checked w/o OC. i wonder if there's issues with the 1070's and 2.7c .. what version of windows drivers are you using?

I keep getting this error , at random times, sometime after 48h sometimes after 20 minutes.
It does not matter if I OC or NO.
I get it with stock and overclock settings , i have changed the risers , checked cables etc. Reinstalled windows set pagefile bigger, added ddr. New nvidia drives old driver does not matter. Tried -eres 0 1 2 does not help.
I also need to mention that i have 2 rigs with 100% same specs , 1 with days of uptime no issue. 1 constantly needs to be rebototed.

My Rig
6x 1070 / 008 risers / 2x HX850i Psu / Biostar BT250 Mobo.
PM 2.7c

PhoenixMiner.exe -pool eu1.ethermine.org:4444 -wal XXXXX.MRORIG02 -proto 3 -cdm 0 -nvidia -eres 0 -minRigSpeed 170 -rmode 2






17595:13:48:32.912: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x0b9f0e5843454c7c5df42b3a5c1b09931866d99dcd4953f6e71f7ce023ec8e6b","0x4e2977c9152afafb8ea63ea5434ada0692b481b8ad37d05391c3a7738d63eb5d","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4f5b01"]}
17595:13:48:32.912: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x0b9f0e5843454c7c5df42b3a5c1b09931866d99dcd4953f6e71f7ce023ec8e6b","0x4e2977c9152afafb8ea63ea5434ada0692b481b8ad37d05391c3a7738d63eb5d","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4f5b01"]}
17595:13:48:33.123: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17595:13:48:34.039: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x67114b78abc6a0f415ef5fe733f79589e655abbe1da07798577c931cb34228cd","0x4e2977c9152afafb8ea63ea5434ada0692b481b8ad37d05391c3a7738d63eb5d","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4f5b02"]}
17595:13:48:34.039: eths Eth: New job #67114b78 from eu1.ethermine.org:4444; diff: 4000MH
17595:13:48:34.742: main Eth speed: 192.765 MH/s, shares: 61/0/0, time: 0:22
17595:13:48:34.742: main GPUs: 1: 32.327 MH/s (13) 2: 31.662 MH/s (5) 3: 32.451 MH/s (7) 4: 31.978 MH/s (13) 5: 32.355 MH/s (10) 6: 31.992 MH/s (13)
17595:13:48:35.364: GPU2 CUDART error in CudaProgram.cu:434 : unknown error (30)
17595:13:48:35.364: GPU4 CUDART error in CudaProgram.cu:434 : unknown error (30)
17595:13:48:35.368: GPU2 GPU2 search error: unknown error
17595:13:48:35.368: GPU4 GPU4 search error: unknown error
17595:13:48:35.386: GPU5 CUDART error in CudaProgram.cu:434 : unknown error (30)
17595:13:48:35.386: GPU5 GPU5 search error: unknown error
17595:13:48:35.387: GPU1 CUDART error in CudaProgram.cu:434 : unknown error (30)
17595:13:48:35.387: GPU1 GPU1 search error: unknown error
17595:13:48:35.388: GPU6 CUDART error in CudaProgram.cu:434 : unknown error (30)
17595:13:48:35.388: GPU6 GPU6 search error: unknown error
17595:13:48:35.388: GPU3 CUDART error in CudaProgram.cu:434 : unknown error (30)
17595:13:48:35.388: GPU3 GPU3 search error: unknown error
17595:13:48:35.419: wdog Thread(s) not responding. Restarting.

Currently testing new version 2.7c with very positive results.

SSL connection works OK
Lower stale shares then previous 2.7a/b version
Running 24h without any problem - both Nvidia and AMD rigs
No perfromace increase, but still better than Claymore 11

Keep up the good work!

thanks to all
everything is working

doesnt help still connection failed

same here..rig got +2mhs with 2.7c out of the blue..but a bit unstable..downclocked it a bit back (to the old hashrate) and now its okay.

same "line" bro, like this :

PhoenixMiner.exe -pool asia.ethereum.miningpoolhub.com:20535 -wal aneumoin.eth1 -pass x -proto 1 -mi 12 -log 0

seems 2.7c isn't as stable as 2.6 on my 1070's .. miner crashes after several hours.

I don't use both miners at same time but can't connect anyway