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

[wizwiz316]

Do you guys still mining with rx470?
Planning to rebuild this rig. I want to know if still worth mining with rx470.

If someone still mining with this cards can you share your power consumption. Thanks.

using ethOS, RX 470 4GB

ram amount:     3.7G   used: 3.5G   free: 219M
cpu usage / temp / load: 95.2% / 50C / 2.54 2.14 1.17

53°C  Fan: 2.7    Hash: 22.03    03 Ellesmere RX 470 113-WE353FU-M73 Samsung
57°C  Fan: 2.8    Hash: 22.01    05 Ellesmere RX 470 113-WE353FU-M73 Samsung
57°C  Fan: 2.8    Hash: 22.02    09 Ellesmere RX 470 113-WE353FU-M73 Samsung
57°C  Fan: 2.8    Hash: 22.03    0a Ellesmere RX 470 113-WE353FU-M73 Samsung
48°C  Fan: 2.7    Hash: 22.03    0b Ellesmere RX 470 113-WE353FU-M73 Samsung
57°C  Fan: 2.8    Hash: 22.03    0c Ellesmere RX 470 113-WE353FU-M73 Samsung
50°C  Fan: 2.7    Hash: 22.03    0d Ellesmere RX 470 113-WE353FU-M73 Samsung
54°C  Fan: 2.8    Hash: 22.03    0e Ellesmere RX 470 113-WE353FU-M73 Samsung

176.2 hash: miner active


GPU1: 52C 80% 84W, GPU2: 56C 80% 88W, GPU3: 57C 80% 85W, GPU4: 57C 80% 84W, GPU5: 48C 80% 84W, GPU6: 57C 80% 85W, GPU7: 50C 80% 85W, GPU8: 53C 80% 81W
GPUs power: 676.0 W
Eth: New job #e652962b from eth-asia1.nanopool.org:9999; diff: 10000MH
Eth: New job #10c86f7b from eth-asia1.nanopool.org:9999; diff: 10000MH
Eth speed: 176.210 MH/s, shares: 5/0/0, time: 0:06
GPUs: 1: 22.030 MH/s (0) 2: 22.015 MH/s (0) 3: 22.020 MH/s (0) 4: 22.029 MH/s (1) 5: 22.035 MH/s (1) 6: 22.029 MH/s (0) 7: 22.033 MH/s (1) 8: 22.019 MH/s (2)

Hi newbie here,

I have just tried to run the PhenoixMiner and got this error can anyone help me fix it?

Phoenix Miner 5.4c Windows/msvc - Release build
-----------------------------------------------

Waiting 15 s for previous instance to close
CUDA version: 11.0, CUDA runtime: 8.0
No OpenCL platforms found
Available GPUs for mining:
GPU1: GeForce GTX 1050 Ti (pcie 1), CUDA cap. 6.1, 4 GB VRAM, 6 CUs
Nvidia driver version: 460.89
Eth: Loading pools from epools.txt
Eth: the pool list contains 3 pools (0 from command-line)
Eth: primary pool: eu1.ethermine.org:4444
Starting GPU mining
Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: EthProxy)
GPU1: 40C 0% 24W
GPUs power: 23.5 W
Eth: Connected to ethash pool eu1.ethermine.org:4444 (172.65.207.xxx)
Eth: New job #18430768 from eu1.ethermine.org:4444; diff: 4000MH
GPU1: Starting up... (0)
GPU1: Generating ethash light cache for epoch #383
Listening for CDM remote manager at port 3333 in read-only mode
Eth: New job #d715a735 from eu1.ethermine.org:4444; diff: 4000MH
Light cache generated in 4.4 s (14.6 MB/s)
GPU1: Allocating DAG (4.01) GB; good for epoch up to #385
CUDA error in CudaProgram.cu:388 : out of memory (2)
GPU1: CUDA memory: 4.00 GB total, 3.30 GB free
GPU1 initMiner error: out of memory
Fatal error detected. Restarting.
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #3f576799 from eu1.ethermine.org:4444; diff: 4000MH
Eth: New job #b691a7b3 from eu1.ethermine.org:4444; diff: 4000MH



Eth: New job #13ca4a33 from eu1.ethermine.org:4444; diff: 4000MH
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00



Thanks

try this :

-dagrestart 2 -gser 2

Thank how do I run this command? sorry new to all this!

[hesido]

I really like this miner. Here's a feature suggestion;

I would like to have the option of having the following ability:

• Do not mine if N number of GPU's are NOT present.

short:
A failed GPU/Riser can result in GPU reordering and this will almost always en up with OC settings applied to the wrong card, and could be a real show-stopper especially in mixed rigs, or even end up burning stuff up, this can be handled in two ways:

• Option A: where if N number of target GPU's are not present, do not mine.

OR

• Option B: Simply if you have ANY setting in config where any setting cannot be applied to a specific gpu, just error out and do not mine.

The latter even could be the default behavior, and could optionally be overridden by those adventurous miners who for some reason want to keep mining with mis-matching OC settings when one of their GPU's fail.

Longer Explanation:
This is not the same as "if hashrate is below certain amount, stop / restart miner" feature, and is directly related to the safety of rigs.
Sometimes a pci-riser can fail or simply even lose connection (there were many times issues could be fixed by simply re-inserting a riser in slot or re-inserting the usb cables), if that happens, system usually resets and phoenix restarts in the beginning. This may not be much of a problem for homogeneous rigs where you can set every parameter the same, but this is rarely the case, as rigs are fine tuned down to gpu level mostly and OC settings can differ massively in mixed rings, where you would rarely want to apply settings to a different card.

An example of how Option B could work on a 3 gpu system:

Code:

-cvddc 1150, 1200, 1150

When a gpu fails, the last setting won't be applied, error out, because if the one of the first gpu has failed, you'd be applying the 1200 setting to the gpu that requires 1150. The difference could be big enough to create bigger problems.

Code:

-cvddc 1150

When a gpu fails, just keep on working.

Code:

-cvddc 1200, 1175, 1150
-disablegpusettingfailsafe   #disclaimer: this is a made up option, do not use this in your config, there's no such option yet.

When a gpu fails, keep on applying OC with the default behaviour.

For lazy miners who e.g. have 5 gpus and don't want to subscribe to the new failsafe setting system by writing

Code:

-cvddc 1170, 1150, 1150, 1150, 1150

They can still go:

Code:

-cvddc 1170, 1150
-disablegpusettingfailsafe #disclaimer: this is a made up option, do not use this in your config, there's no such option yet.

[wizwiz316]

Can anyone help me with this problem please?


Phoenix Miner 5.4c Windows/msvc - Release build
-----------------------------------------------

Waiting 15 s for previous instance to close
CUDA version: 11.0, CUDA runtime: 8.0
No OpenCL platforms found
Available GPUs for mining:
GPU1: GeForce GTX 1050 Ti (pcie 1), CUDA cap. 6.1, 4 GB VRAM, 6 CUs
Nvidia driver version: 460.89
Eth: Loading pools from epools.txt
Eth: the pool list contains 3 pools (0 from command-line)
Eth: primary pool: eu1.ethermine.org:4444
Starting GPU mining
Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: EthProxy)
GPU1: 45C 0% 24W
GPUs power: 23.9 W
GPU tuning is only supported on dual kernels or on AMD GPUs with optimized kernels
Eth: Connected to ethash pool eu1.ethermine.org:4444 (172.65.207.xxx)
Eth: New job #92ca47d1 from eu1.ethermine.org:4444; diff: 4000MH
GPU1: Starting up... (0)
GPU1: Generating ethash light cache for epoch #383
Listening for CDM remote manager at port 3333 in read-only mode
Eth: New job #7c2c836b from eu1.ethermine.org:4444; diff: 4000MH
Light cache generated in 4.5 s (14.2 MB/s)
GPU1: Allocating DAG (4.01) GB; good for epoch up to #385
CUDA error in CudaProgram.cu:388 : out of memory (2)
GPU1: CUDA memory: 4.00 GB total, 3.30 GB free
GPU1 initMiner error: out of memory
Fatal error detected. Restarting.
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #78994abc from eu1.ethermine.org:4444; diff: 4000MH

[cirlama]

Hello guys, i have 5 gtx 1080ti and im getting 210MH/s (42MH/s each and consuming 160w each) with power75% +50 +650 clocksettings. im just using the miner and the PILL, and basically 0 configs
Any hints to pump these rookie numbers ?  

you can try using straps instead of the pill by adding it on your cmd line (but the miner has to run in admin to set the straps):
 -nvdo 1 -straps 2 -mi 14
(with the straps, the +xxx on mem does almost nothing, I set mine to -200 for improved stability)

you can test a bit higher in core, or increase your power to 85% (but more watts...)

I am getting 45 MH/s @75%power, 47.5 @85%

[Cryptomining2003]

I really like this miner. Here's a feature suggestion;

I would like to have the option of having the following ability:

• Do not mine if N number of GPU's are NOT present.

short:
A failed GPU/Riser can result in GPU reordering and this will almost always en up with OC settings applied to the wrong card, and could be a real show-stopper especially in mixed rigs, or even end up burning stuff up, this can be handled in two ways:

• Option A: where if N number of target GPU's are not present, do not mine.

OR

• Option B: Simply if you have ANY setting in config where any setting cannot be applied to a specific gpu, just error out and do not mine.

The latter even could be the default behavior, and could optionally be overridden by those adventurous miners who for some reason want to keep mining with mis-matching OC settings when one of their GPU's fail.

Longer Explanation:
This is not the same as "if hashrate is below certain amount, stop / restart miner" feature, and is directly related to the safety of rigs.
Sometimes a pci-riser can fail or simply even lose connection (there were many times issues could be fixed by simply re-inserting a riser in slot or re-inserting the usb cables), if that happens, system usually resets and phoenix restarts in the beginning. This may not be much of a problem for homogeneous rigs where you can set every parameter the same, but this is rarely the case, as rigs are fine tuned down to gpu level mostly and OC settings can differ massively in mixed rings, where you would rarely want to apply settings to a different card.

An example of how Option B could work on a 3 gpu system:

Code:

-cvddc 1150, 1200, 1150

When a gpu fails, the last setting won't be applied, error out, because if the one of the first gpu has failed, you'd be applying the 1200 setting to the gpu that requires 1150. The difference could be big enough to create bigger problems.

Code:

-cvddc 1150

When a gpu fails, just keep on working.

Code:

-cvddc 1200, 1175, 1150
-disablegpusettingfailsafe   #disclaimer: this is a made up option, do not use this in your config, there's no such option yet.

When a gpu fails, keep on applying OC with the default behaviour.

For lazy miners who e.g. have 5 gpus and don't want to subscribe to the new failsafe setting system by writing

Code:

-cvddc 1170, 1150, 1150, 1150, 1150

They can still go:

Code:

-cvddc 1170, 1150
-disablegpusettingfailsafe #disclaimer: this is a made up option, do not use this in your config, there's no such option yet.

that´s a good point. I already recognized that if you have one GPU as GPU0, it will not stay GPU0 if you add or remove a card. I added 2 cards to my rig...I printed the GPU number with a label printer to the GPU´s...but you can forget everything if you edit the number of gpu´s...you need to find out with spinning fans which one is which one and set oc manually again. if one card crashes and the rig restarts without that card...your oc settings will be totally mixed...true ! good point.....but maybe a point for the operating system not to start the miner.....

but if one could add this to phoenixminer, would be great to see.

[batsonxl]

albornoz albornoz albornoz dude arent you tired keep posting these scam posts???

[Toughit]

Do you guys still mining with rx470?
Planning to rebuild this rig. I want to know if still worth mining with rx470.

If someone still mining with this cards can you share your power consumption. Thanks.

Of course you can mine with RX 470.   Mine are doing 30 MH/s.  They are the Sapphire variant with Samsung 8Gb.

Mind sharing your settings, Im struggling to get 20-22 on my 470 8gb cards...

[hesido]

that´s a good point. I already recognized that if you have one GPU as GPU0, it will not stay GPU0 if you add or remove a card. I added 2 cards to my rig...I printed the GPU number with a label printer to the GPU´s...but you can forget everything if you edit the number of gpu´s...you need to find out with spinning fans which one is which one and set oc manually again. if one card crashes and the rig restarts without that card...your oc settings will be totally mixed...true ! good point.....but maybe a point for the operating system not to start the miner.....

but if one could add this to phoenixminer, would be great to see.

Thanks, I just made a powershell script that counts the display adapters using devcon.exe (windows) and shuts down the system after a timeout if it can't find required number of display adapters, or runs the normal batch. It's not fool-proof or as graceful as having it on phoenix miner. Haven't yet tested the script in real-life conditions yet, and don't know what happens if the drivers are disabled instead of a gpu/riser failure. Will have to test those some time.

I hope this kind of behaviour can make it into phoenix miner itself.

[lovefxspot]

i am trying to set fan at 100% always by -fanmin 100, -fanmax 100. but it doesn't work...what's the right parameters to set fan at 100% always? Thanks!

[lovefxspot]

i noticed the cvddc value in printout is actually mvddc. wondering why...

btw i am on ubuntu 20.04.1 + amd 20.30 and card is rx580.

[Redymix]

https://i.ibb.co/xS1Xbyd/1.png

i get low share rates but high difficulty.
this is on a rtx 3060 ti with 70% powerlimit and +1000 on memspeed in afterburner.
is this good/bad and how solve this?

That's about what I got with my 3060 ti and 3070, however, I discovered that I could set them to +1200 to get 61.5MHs.

[Deafran]

try this :

-dagrestart 2 -gser 2

Thank how do I run this command? sorry new to all this!

add it in your phoenix miner bat file : example

windows :
PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal 0xBB942274AB3C8285400519e7F0c343Fca2394908 -worker Phoenix -epsw x -mode 1 -Rmode 1 -dagrestart 2 -gser 2 -log 0 -mport 0 -etha 0 -retrydelay 1 -ftime 55 -tt 79 -tstop 89 -tstart 79 -coin eth
pause


EthOS :

loc xxxxxx Cobalt

maxgputemp 80
stratumproxy miner
proxywallet 0xEC.Cobalt/miner@gmail.com
proxypool1 eth-asia1.nanopool.org:9999
proxypool2 eth-us-east1.nanopool.org:9999
flags --cl-global-work 8192 --farm-recheck 200
globalfan 80

globalminer phoenixminer
phoenixminer=flags -dagrestart 2 -gser 2 -gt 20

[Deafran]

Do you guys still mining with rx470?
Planning to rebuild this rig. I want to know if still worth mining with rx470.

If someone still mining with this cards can you share your power consumption. Thanks.

Of course you can mine with RX 470.   Mine are doing 30 MH/s.  They are the Sapphire variant with Samsung 8Gb.

Mind sharing your settings, Im struggling to get 20-22 on my 470 8gb cards...

ethOS :

ram amount:     3.8G   used: 1.1G   free: 2.7G
cpu usage / temp / load: 13.3% / 40C / 0.73 0.50 0.40

56°C  Fan: 0.0    Hash: 26.99    01 Ellesmere RX 480 113-1E353GU.O52 Micron
65°C  Fan: 2.8    Hash: 27.00    02 Ellesmere RX 480 113-1E353GU.O52 Micron
46°C  Fan: 0.8    Hash: 00.00    03 Ellesmere RX 480 115-D000PIL-100 Samsung
63°C  Fan: 2.8    Hash: 29.95    05 Ellesmere RX 580 113-1E3870U-O4B Samsung
52°C  Fan: 2.7    Hash: 27.00    06 Ellesmere RX 480 113-1E353GU.O52 Micron
68°C  Fan: 2.4    Hash: 27.65    07 Ellesmere RX 480 115-D000PIL-100 Samsung

138.6 hash: miner active

local config :

globalminer phoenixminer
phoenixminer=flags -dagrestart 2 -gser 2 -lidag 1 -tstop 80 -gt 69,69,67,61,70,67


fan xxxxxx 70 80 80 80 80 80 80 80
vlt xxxxxx 875 875 875 875 875 875 875 875
vddci xxxxxx 900 900 900 900 900 900 900 900

all 8 GB card

[drsimkein]

what AMD driver to use with 5.4c
I have random driver stops every 6 to 8 hours.

[oskoa]

hello, happy xmax.

In the past i found un this forum this files




these is a "Crimson Beta" Driver (MSI afterburner report), but this driver was really very cool. With this driver (today inclusive, 12/25/20) Play "almost" all games, and minning ETH to the max of my card (RX 570 8 GB, 25 Mhz) without set Compute/Gaming mode, And with Windows 7!

But unfortunatly, this driver doesnt work more with 4 GB Cards. And with the new drivers i have a lot of problems with 4 GB Cards (Epic low hash (12, was 24), 1 of 4 cards of 4gb doesnt start... etc...

anyone knows if exist a modern version of this driver?


MSI Afterburner capture:

[arielbit]

any info/ideas why on windows 7 1080ti ETH hashrate dropped from ~48MH to ~18MH?

last time i've seen this is when i used 4gb system ram, when I updated to 6gb system ram, the issue is resolved..but now rigs with 6gb and 8gb system ram have the same issue.

on windows 10 hashrate unaffected.

[soda37]

I'm trying to set cvddc on latest 5.4c for nvidia cards (1060,1080):


Out of range -cvddc value: -100 (must be between 0 and 2000)
Invalid value in -cvddc option: -100

[ronelord]

any info/ideas why on windows 7 1080ti ETH hashrate dropped from ~48MH to ~18MH?

last time i've seen this is when i used 4gb system ram, when I updated to 6gb system ram, the issue is resolved..but now rigs with 6gb and 8gb system ram have the same issue.

on windows 10 hashrate unaffected.

Same problem here with WIN7, any solution ?
Will 16GB RAM help ?

[arielbit]

any info/ideas why on windows 7 1080ti ETH hashrate dropped from ~48MH to ~18MH?

last time i've seen this is when i used 4gb system ram, when I updated to 6gb system ram, the issue is resolved..but now rigs with 6gb and 8gb system ram have the same issue.

on windows 10 hashrate unaffected.

Same problem here with WIN7, any solution ?
Will 16GB RAM help ?

i think not, have not tried 16gb...because 6gb and 8gb system ram rigs slowed down at the same time.

still looking for a solution, my last solution will be to shift to windows 10.

[j2james]

To @PhoenixMiner!

Dear devs. I do not understand what is happening! But, after some time I again have 21Mh per card on Rig with 8 cards ASUS ROX STRIX GTX-1070 8Gb. So instead of 180Mh per 6 cards, I have 127Mh. Windows 7. Both miners PM 5.3b and 5.4c have the same speed.

Can you comment that somehow? I asked you before that, but still there is no any comments

Just any changes of MC (-mclock) do nothing. Mining speed always like speed with -mclock 0.

Please, answer. Do not ignore.

Thank you.


----------------
config:

#******************************#
#   Mining options             #
#******************************#

-nvidia
-nvf 2
-minRigSpeed 100
-eres 0

-rmode 2

-logsmaxsize 0

#******************************#
#   Remote control options     #
#******************************#

-cdm 2
-cdmport 3333
-cdmpass xxxxx
-cdmrs

#******************************#
#   Hardware control options   #
#******************************#

-hstats 2

-tstop 70
-tstart 40

-mclock +340,+440,+400,+440,+430,+330
-cclock 1:+70,2-6:+102