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

Mind if I ask why you are mining on nicehash? I mean your earnings will be slightly less compared to any ethereum pool like nanopool and nicehash pays Bitcoin which is higher transaction fees....

what the fuck is wrong with these people posting whole log content? you deserve to have lots of problems.

I Just switched to Phoenix. Performance is roughly the same as Claymore's, lower dev fee, it's a no brainer.

Dual mining is overrated as usual, unless you have free electricity.

Just one question: I had to set mining intensity to 12 to get same performance as Claymore's 11.4, no problem, power consumption is the same and all seems stable. But how about -dcri? C's 11.4 actually improved performance a bit by auto setting dcri in Eth only mode. I got -dcri 110,44,110.

Tried to use those values with -gt parameter in Phoenix bat file, but performance was much lower.

Tried to use phoenix miner for the first time today, got 0,00 MHS for some reason

17604:04:37:03.269: main Phoneix Miner 2.7c Windows/msvc - Release
17604:04:37:03.269: main Cmd line: -pool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -wal nicehashwallet -pass x -proto 4 -stales 0 -amd
17604:04:37:03.950: main Available GPUs for mining:
17604:04:37:03.950: main GPU1: Radeon (TM) RX 480 Graphics (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
17604:04:37:03.950: main GPU2: Radeon (TM) RX 480 Graphics (pcie 3), OpenCL 2.0, 8 GB VRAM, 36 CUs
17604:04:37:03.950: main GPU3: Radeon (TM) RX 480 Graphics (pcie 5), OpenCL 2.0, 8 GB VRAM, 36 CUs
17604:04:37:03.950: main GPU4: Radeon (TM) RX 480 Graphics (pcie 6), OpenCL 2.0, 8 GB VRAM, 36 CUs
17604:04:37:03.950: main GPU5: Radeon (TM) RX 480 Graphics (pcie 7), OpenCL 2.0, 8 GB VRAM, 36 CUs
17604:04:37:03.950: main GPU6: Radeon (TM) RX 480 Graphics (pcie , OpenCL 2.0, 8 GB VRAM, 36 CUs
17604:04:37:03.979: main ADL library initialized
17604:04:37:04.269: main Listening for CDM remote manager at port 3333 in read-only mode
17604:04:37:04.269: main Eth: the pool list contains 2 pools
17604:04:37:04.269: main Eth: primary pool: daggerhashimoto.eu.nicehash.com:3353
17604:04:37:04.269: main Starting GPU mining
17604:04:37:04.269: main Matched GPU1 to ADL adapter index 24 (method 1)
17604:04:37:04.299: main GPU1: Using the X2 ODN API
17604:04:37:04.299: main GPU1: Created ADL monitor for adapter 24; overdrive version: 7
17604:04:37:04.299: main Matched GPU2 to ADL adapter index 12 (method 1)
17604:04:37:04.329: main GPU2: Using the X2 ODN API
17604:04:37:04.329: main GPU2: Created ADL monitor for adapter 12; overdrive version: 7
17604:04:37:04.330: main Matched GPU3 to ADL adapter index 30 (method 1)
17604:04:37:04.360: main GPU3: Using the X2 ODN API
17604:04:37:04.360: main GPU3: Created ADL monitor for adapter 30; overdrive version: 7
17604:04:37:04.360: main Matched GPU4 to ADL adapter index 0 (method 1)
17604:04:37:04.390: main GPU4: Using the X2 ODN API
17604:04:37:04.390: main GPU4: Created ADL monitor for adapter 0; overdrive version: 7
17604:04:37:04.390: main Matched GPU5 to ADL adapter index 18 (method 1)
17604:04:37:04.421: main GPU5: Using the X2 ODN API
17604:04:37:04.421: main GPU5: Created ADL monitor for adapter 18; overdrive version: 7
17604:04:37:04.421: main Matched GPU6 to ADL adapter index 6 (method 1)
17604:04:37:04.454: main GPU6: Using the X2 ODN API
17604:04:37:04.454: main GPU6: Created ADL monitor for adapter 6; overdrive version: 7
17604:04:37:04.454: wdog Starting watchdog thread
17604:04:37:04.454: main Eth: Connecting to ethash pool daggerhashimoto.eu.nicehash.com:3353 (proto: Nicehash)
17604:04:37:04.495: eths Eth: Connected to ethash pool daggerhashimoto.eu.nicehash.com:3353 (159.122.29.199)
17604:04:37:04.495: eths Eth: Send: {"id":1,"method":"mining.subscribe","params":["PhoenixMiner/2.7c","EthereumStratum/1.0.0"]}

17604:04:37:04.566: eths Eth: Received: {"id":1,"error":null,"result":[["mining.notify","1b823da44765203241b8224983007c12","EthereumStratum/1.0.0"],"4b61a2"]}
17604:04:37:04.566: eths Eth: Extranonce set to 4b61a2
17604:04:37:04.566: eths Eth: Subscribed to ethash pool
17604:04:37:04.566: eths Eth: Send: {"id":2,"method":"mining.extranonce.subscribe","params":[]}
{"id":3,"method":"mining.authorize","params":["3C6VmPEhFSM7cj4aw89NhpZGmSovKffKVH","x"]}

17604:04:37:04.613: eths Eth: Received: {"id":3,"result":true,"error":null}
17604:04:37:04.613: eths Eth: Worker 3C6VmPEhFSM7cj4aw89NhpZGmSovKffKVH authorized
17604:04:37:04.631: eths Eth: Received: {"id":null,"method":"mining.set_difficulty","params":[0.5]}
17604:04:37:04.631: eths Eth: Difficulty set to 0.5
17604:04:37:04.631: eths Eth: Received: {"params":["000000251564b3f1","08e704bf06ac983d776d734cacf1f611802b802efb5a5f5cb8086d6a0d966ac5","ead2f865f18fd460b8938e49795e17d876b1cec5cda5ebc65b5381c46645ef18",true],"id":null,"method":"mining.notify"}
17604:04:37:04.631: eths Eth: New job #ead2f865 from daggerhashimoto.eu.nicehash.com:3353; diff: 2147MH
17604:04:37:04.631: GPU1 GPU1: Starting up... (0)
17604:04:37:04.631: GPU1 Eth: Generating light cache for epoch #175
17604:04:37:04.631: GPU2 GPU2: Starting up... (0)
17604:04:37:04.633: GPU3 GPU3: Starting up... (0)
17604:04:37:04.635: GPU4 GPU4: Starting up... (0)
17604:04:37:04.637: GPU5 GPU5: Starting up... (0)
17604:04:37:04.639: GPU6 GPU6: Starting up... (0)
17604:04:37:04.641: eths Eth: Received: {"id":2,"result":true,"error":null}
17604:04:37:04.659: main GPU1: 32C 0%, GPU2: 24C 70%, GPU3: 23C 75%, GPU4: 20C 75%, GPU5: 26C 95%, GPU6: 36C 60%
17604:04:37:07.205: GPU2 GPU2: Using optimized OpenCL kernels (device name 'Ellesmere')
17604:04:37:09.590: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17604:04:37:09.590: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
17604:04:37:14.714: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17604:04:37:14.714: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
17604:04:37:19.862: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17604:04:37:19.862: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
17604:04:37:25.029: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17604:04:37:25.029: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
17604:04:37:30.157: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17604:04:37:30.157: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
17604:04:37:32.720: main GPU1: 32C 0%, GPU2: 25C 70%, GPU3: 23C 75%, GPU4: 21C 75%, GPU5: 26C 95%, GPU6: 37C 60%

BAT: -pool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -wal nicehashwallet -pass x -proto 4 -stales 0 -amd

any ideas appreciated!

I'm getting same error on my 1060 GTX 6GB card. 1070 seems ok with no issues.

I have noticed that when this error occurs and I switch on Nvidia Afterburner the system becomes extremelly choppy and laggy.. then I have to restart rig.. After restart it is OK.

Sometimes it takes more than one day that this error appears.

In previous version this error was not present.

Wow, you have very cheap electricity there!!
By the way dual mine fee is 1.5% and zero for 2gb cards like RX560.

Too high memory overclock makes all readings on GPU-Z or similar programs return no data. Restart the rig, check which GPU returns no temperature, dial down the overclock and try again.
Phoenix is slightly more intensive compared to Claymore with default intensity, so if you are on the edge of stability on Claymore - it might crash with Phoenix.

I'm getting the same error in the last day. Before that I mined for about 60 hours without any problems. But now that error keeps popping up and restarting the miner and sometimes the rig.
6x 1050ti, my OC settings are more or less stable, running on Claymore with the same settings with no problems. But I would prefer Phoenix, the hash rate is better.
In Claymore you can override this problem by switching off temperature and fan speed stats by typing "-tt 0" into the batch file. The same command isn't recognized by Phoenix, maybe somebody has some suggestions on that matter for Phoenix?

Didn't he talk about his 1060 rig? And what AMD card can produce 1600 mh/s?

Either I mine ONLY ETH (my rig generates 399 mh/s) or I dualmine ETH (still 399 mh/s) plus DCR makes no difference to me. My electricity cost is 0.6 euro cts per kwh and whether single or dual mine does not change my power consumption on the wall.... Only difference is the dev fee between 1 and 2%.

  Thank you for the information. The blockchain drivers definitely doesn't work properly with our way of controlling fan speed and voltages (only the clock settings seem to work properly and reliably). The new drivers (18.x.x) have fixed almost all bugs in fan speed control (without any significant hashrate changes) so you can try them and see if they solve the problem for you.

  Yes, this could be useful in some cases but we have a lot on our plate and it may take a while before this is implemented.

  We need the log file of PhoenixMiner itself in order to make any conclusions. This log file doesn't contain any information that would tell us why the program is crashing or closing.

 Not yet. Rest assured, whenever it's ready, it will be posted on the first page (and even on thread's title).

  This is just bad luck, nothing wrong with the log.

  We support the monitoring JSON API of Claymore but some programs may try to parse the log messages themselves, which obviously are quite different in PhoenixMiner. We are adding support for miner_getstat2 request too, which was missing in the current versions, so this should improve the compatibility.

  In about a week there will be a beta release (maybe even sooner if no issues are found during the internal testing). There will be a lot of small improvements; support for -li, -tstop, and -tstart options; and some other changes...


  The problem is that there is no reliable way to get the default settings, without resetting all settings to the defaults. PhoenixMiner resets the settings to the default only if a "clean exit" is made with Ctrl+C in the command console. We can also reset the settings on startup but this may interfere with any other programs that are used for control of clocks/voltages/fans, etc. Perhaps the best way is to add an option -hwclean or something like this, which to tell PhoenixMiner that it is OK to reset the settings on startup.

 This seems like a connectivity problem - the connection is established and then closed by the pool.

 This is typically result of too much memory overclock. Lower the memory overclock on this card by 20-30 MHz and the problem should go away.

He probably meant he uses only amd cards.

Can anyone tell me what "i'm from Red Army" means ?
Is that some video card I've never heard of ?

The reason might be in too much GPU overclocking on Memory, try to lower overclocking for 10-20 MHz

I'm not on 1060. i'm from Red Army. Depending on card, each gives from 1300 to 1600 Mh\s. Without any impact on ETH speed.
So for all who use RX in rigs, this miner is useless.

I Used ver 2.7c and and I was error 999.
https://i.imgur.com/46nKKyN.jpg

I just check the shares from the pool per hour. It’s the same as the numbers showed by the miner but the average hourly stat is more useful when comparing different miners in my opinion.

Come on.. how much xvg can one 1060 mine per month?

decred is almost dead on gpu and if you are mining decred on your gpu then it means you are paying to mine it. The eth devfee 0.5-1% claymore gets from you by dual mining has higher profit than mining decred. So you are wasting electricity and profit.

but what was the difficulty of the shares? it is pointless to count shares as each one can have a different weight. for all that you know claymore 11.4 can provide more eth than the 174 shares. so how did you get the 0.08 eth?