PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 484.

dohfish

newbie

Activity: 65

Merit: 0

Quote from: evlo on February 02, 2018, 11:07:40 AM

I'm trying 2.4 on my farm, because of the stale shares reports on 2.5d and i'm mostly seeing gains on having less stale shares.
PhoenixMiner crashes - like process is just gone, no error, nothing, not even crashed app message from windows - in about 2 days of running. Is this fixed in later version?

Etherminer or Claymore don't suffer this issue.

Disadvantage of etherminer 0.13 I see is that it does not have color console on windows. It does have much less stale shares then 0.12. But seems to still be bit more then PhoenixMiner.

I have had the 2.5d version running for 3 days now, stale shares are not higher, what I posted earlier was more than likely a ethermine issue, it went away some 8 hours later and have been perfectly stable around 2-3% stales since then.

evlo

jr. member

Activity: 155

Merit: 4

I'm trying 2.4 on my farm, because of the stale shares reports on 2.5d and i'm mostly seeing gains on having less stale shares.
PhoenixMiner crashes - like process is just gone, no error, nothing, not even crashed app message from windows - in about 2 days of running. Is this fixed in later version?

Etherminer or Claymore don't suffer this issue.

Disadvantage of etherminer 0.13 I see is that it does not have color console on windows. It does have much less stale shares then 0.12. But seems to still be bit more then PhoenixMiner.

leonos007

newbie

Activity: 11

Merit: 0

I mined some days with this phoenix and it is giving me a few more hashes per seconds more then ethminer.0.14.0

Amount of solutions found is less, probably because the software is running only for the dev-fee on regular base.

Well because the amount of solutions is what counts, I went back to ethminer.0.14.0, giving me a few less hashes per second, but more solutions due to the non existing dev-fee.

I think that we are currently on the ceiling of squeezing hashes out of the GPU's, so new miners with dev-fee will not contribute this in a positive manner.

alkoholik24

newbie

Activity: 2

Merit: 0

Hello,

Code:

17564:12:26:44.968: main Phoneix Miner 2.5d Windows/msvc - Release
17564:12:26:44.968: main Cmd line: -pool eu1.ethermine.org:4444 -wal 0x36fd6ca7b320c46189bb9e78f5390573cace4745.Rig003 -proto 3
17564:12:26:47.093: main Available GPUs for mining:
17564:12:26:47.170: main GPU1: GeForce GTX 1070 (pcie 1), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17564:12:26:47.170: main GPU2: GeForce GTX 1070 (pcie 2), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17564:12:26:47.170: main GPU3: GeForce GTX 1070 (pcie 3), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17564:12:26:47.210: main NVML library initialized
17564:12:26:51.887: main Listening for CDM remote manager at port 3333 in read-only mode
17564:12:26:51.887: main Eth: the pool list contains 3 pools
17564:12:26:51.887: main Eth: primary pool: eu1.ethermine.org:4444
17564:12:26:51.888: main Eth: Connecting to ethash pool eu1.ethermine.org:4444
17564:12:26:52.171: eths Eth: Connected to ethash pool eu1.ethermine.org:4444
17564:12:26:52.171: eths Eth: Starting GPU mining
17564:12:26:52.238: wdog Starting watchdog thread
17564:12:26:52.239: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_login","params":["0x36fd6ca7b320c4g07cab9e78f5390573cace4745.Rig003"]}

17564:12:26:52.294: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
17564:12:26:52.295: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17564:12:26:52.355: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xf4b2522add423224a6cb7b8f6388076fcc9d2b37ef4576e8ee8ed4f2f1bf4242","0xb683d2a97f567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4c8da2"]}
17564:12:26:52.355: eths Eth: New job #f4b2522a from eu1.ethermine.org:4444; diff: 4000MH
17564:12:26:52.360: GPU1 GPU1: Starting up...
17564:12:26:52.360: GPU1 Eth: Generating light cache for epoch #167
17564:12:26:52.381: GPU2 GPU2: Starting up...
17564:12:26:54.430: GPU3 GPU3: Starting up...
17564:12:26:55.306: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x29db229bbcc8f6acc243be972de280ed12e2a302b18c1a00eeeda7bc7b2f9fbb","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4c8da3"]}
17564:12:26:55.306: eths Eth: New job #29db229b from eu1.ethermine.org:4444; diff: 4000MH
17564:12:26:56.977: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17564:12:26:56.977: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0)
17564:12:26:59.874: GPU2 GPU2: Allocating DAG (2.32) GB; good for epoch up to #169
17564:12:26:59.984: GPU2 CUDA error in CudaProgram.cu:282 : out of memory (2)
17564:12:26:59.987: GPU1 GPU1: Allocating DAG (2.32) GB; good for epoch up to #169
17564:12:27:00.004: GPU2 GPU2 initMiner error: out of memory
17564:12:27:00.191: GPU3 GPU3: Allocating DAG (2.32) GB; good for epoch up to #169
17564:12:27:00.318: GPU3 CUDA error in CudaProgram.cu:282 : out of memory (2)
17564:12:27:00.318: GPU3 GPU3 initMiner error: out of memory
17564:12:27:00.400: GPU1 GPU1: Allocating light cache buffer (37.1) MB; good for epoch up to #169
17564:12:27:00.521: GPU1 GPU1: Generating DAG for epoch #167
17564:12:27:00.572: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x2e8a792c718867a8bdf1df222574c99b608f9a441e2b75bbc50af387f5842ad4","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4c8da4"]}
17564:12:27:00.572: eths Eth: New job #2e8a792c from eu1.ethermine.org:4444; diff: 4000MH
17564:12:27:00.590: GPU2 GPU2: Starting up...
17564:12:27:00.603: GPU3 GPU3: Starting up...
17564:12:27:00.848: wdog GPU thread(s) not responding. Restarting.
17564:12:27:02.073: GPU1 GPU1: DAG 13%
17564:12:27:02.084: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17564:12:27:02.084: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0)
17564:12:27:03.755: GPU1 GPU1: DAG 25%

the same in PhoenixMiner2.4
GPU default setting

Why is that?

zeii

newbie

Activity: 41

Merit: 0

Quote from: shanepottermi on February 01, 2018, 08:42:01 PM

If you really want to make your fee lower than claymore and increase the fees you receive i'd suggest running your dev fee less often but for longer. Claymore runs his every hour.. it takes a minute for a system with a lot of gpus to spin them all up making that 30-70 seconds less effective because 10+ seconds its spinning the cards up.. then when it cuts off i have to wait for my cards to spin up to start mining again. It makes his 1% fee a lot larger than 1% an produces less for him. If you ran your fee like once every 4-6 hours instead of every 90 minutes but you ran it for an equivalent time relative to the 90 min dev fee.. we'd all make more long term. You might end up with some of the gamer miners trying to cut the fee but the people running a lot of cards 24/7 won't. Since you're not spinning up all the large farms over n over again for a short burst an instead mined for a 1-2 minutes you'd probably pull more in fees and we'd pay less due to downtime switching to dev pools. Win win for everyone.

Agree with you.

santan

member

Activity: 102

Merit: 11

Quote from: PcChip on February 01, 2018, 05:32:41 PM

I'm getting "Debugger detected" on my gaming rig, which I do have Visual studio installed as I'm a hobbyist visual c++ programmer - could that be why ?

Use the switch ..... -nvidia
if you are on NVIDIA GPU.... I was in the same situation.... solved by it.

Marvell2

full member

Activity: 1148

Merit: 132

Quote from: shanepottermi on February 01, 2018, 08:42:01 PM

If you really want to make your fee lower than claymore and increase the fees you receive i'd suggest running your dev fee less often but for longer. Claymore runs his every hour.. it takes a minute for a system with a lot of gpus to spin them all up making that 30-70 seconds less effective because 10+ seconds its spinning the cards up.. then when it cuts off i have to wait for my cards to spin up to start mining again. It makes his 1% fee a lot larger than 1% an produces less for him. If you ran your fee like once every 4-6 hours instead of every 90 minutes but you ran it for an equivalent time relative to the 90 min dev fee.. we'd all make more long term. You might end up with some of the gamer miners trying to cut the fee but the people running a lot of cards 24/7 won't. Since you're not spinning up all the large farms over n over again for a short burst an instead mined for a 1-2 minutes you'd probably pull more in fees and we'd pay less due to downtime switching to dev pools. Win win for everyone.

dev fee keeps crashing my rigs , stopped using it

zeii

newbie

Activity: 41

Merit: 0

Quote from: P00P135 on February 01, 2018, 05:57:38 PM

Trojan.Win64.Wdfload is back in this version.

https://www.virustotal.com/#/file/57b3f97da3918232205201daf548a522a1dba920c1fccd94a483bad30420ed59/detection

this from claymore
https://www.virustotal.com/#/file/eec33b077ffa3ed4226ba97b7b6d996177cd1b01b6825abc3d8a6aa5b877cb32/detection

akuci

full member

Activity: 226

Merit: 100

If you still don't know that many miners gets flaged as viruses then go, sell your rigs please, and do something else. Or use Nicehash. It's designed to not get flaged by AV.
It's a friendly advice. Don't spread panic.

kurupilav

newbie

Activity: 10

Merit: 0

Quote from: P00P135 on February 01, 2018, 05:57:38 PM

Trojan.Win64.Wdfload is back in this version.

https://www.virustotal.com/#/file/57b3f97da3918232205201daf548a522a1dba920c1fccd94a483bad30420ed59/detection

yesterday I have downloaded this version and scanned it through virustotal.com and it was as clean as water, and now I have scanned once again and viruses came back and my kaspersky immediately deleted the file

this virus thing really need some explanation since it really confusing and stopped me using the proggy

zeii

newbie

Activity: 41

Merit: 0

Quote from: Miner59 on February 01, 2018, 01:02:15 PM

Been using this miner for like 6 hours now and it's amazing. 4-5 MH/s more than Claymore, which is great!

But I'm having this weird problem right now, I have 2x RX560's which are getting 14.7 MH/s each, but every ~10 seconds they both drop to ~12 MH/s for 2 seconds and then it goes back to 14.7 MH/s. My RX580's are not doing this and are keeping strong on the 30.5 MH/s mark. With Claymore I do not have this issue, I also tested this with Ethminer and the RX560's do not drop in hashrate at all.

Would be great if you could get that fixed somehow, other than that, this miner simply amazes me, keep up the good work!

Same here,wait for fix.

rockk

jr. member

Activity: 20

Merit: 0

please make the fucking devfee run every 10 hours or so and for more time to compensate, dont every fucking hour cuz fucks up shit.

shanepottermi

newbie

Activity: 55

Merit: 0

If you really want to make your fee lower than claymore and increase the fees you receive i'd suggest running your dev fee less often but for longer. Claymore runs his every hour.. it takes a minute for a system with a lot of gpus to spin them all up making that 30-70 seconds less effective because 10+ seconds its spinning the cards up.. then when it cuts off i have to wait for my cards to spin up to start mining again. It makes his 1% fee a lot larger than 1% an produces less for him. If you ran your fee like once every 4-6 hours instead of every 90 minutes but you ran it for an equivalent time relative to the 90 min dev fee.. we'd all make more long term. You might end up with some of the gamer miners trying to cut the fee but the people running a lot of cards 24/7 won't. Since you're not spinning up all the large farms over n over again for a short burst an instead mined for a 1-2 minutes you'd probably pull more in fees and we'd pay less due to downtime switching to dev pools. Win win for everyone.

P00P135

full member

Activity: 1124

Merit: 136

Trojan.Win64.Wdfload is back in this version.

https://www.virustotal.com/#/file/57b3f97da3918232205201daf548a522a1dba920c1fccd94a483bad30420ed59/detection

PcChip

sr. member

Activity: 418

Merit: 250

I'm getting "Debugger detected" on my gaming rig, which I do have Visual studio installed as I'm a hobbyist visual c++ programmer - could that be why ?

Dhino

jr. member

Activity: 41

Merit: 1

Any plan for Linux version?

puch0021

newbie

Activity: 35

Merit: 0

Reporting in Phoenix 2.5d

8x1060 3gb cards with samsung memory @ 50 power limit, +185 core, +800 memory, p0 state. 390.65 drivers

Average 196 mh/s ~ 24.5 per card, 555 watts at the wall. Stale percentage 0.5%

So far so good. Will compare to poolside reported shares with Claymore 10.6 tomorrow but I'm currently seeing a 1.5% increase in local hash rates when you factor in dev fees.

Hobosnax

newbie

Activity: 2

Merit: 0

Love the miner, 1060's consistently pushing 24.4 MH/s on main rig. Unfortunatly I am getting the "Fatal error: debugger detected" on secondary rig that is nearly a carbon copy (both Win7/1060's/same drivers). Would love to get a version that spits out more data on this error so I can troubleshoot.

dixa

newbie

Activity: 31

Merit: 0

using about 4 hours not have any problem speeds are same for me but shares more at pool i like this miner keep update!

murgorx

member

Activity: 443

Merit: 13

Okay dev and more in-depth people I need your opinion on this - https://imgur.com/a/aggai.
All cards are with the same BIOS, all cards are usually running on 31.5+ mh/s when tested solo.
But when I run them all simultaneously, the main one is hashing around 11mh/s less.
As you can see in the pic, some of them are submitting 10 shares, where some just 1, and they are all constantly at the same speeds ? What am I doing wrong?
I am using TRIXX 1240/2200 and all cards are -25V, because 150w are 150w Cheesy

Not to mention they are a bit cooler when undervolted.
In HWINFO the cards are not giving any errors at all.

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