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

[Kiawpqe]

i try only pool.binance!
not Fee, one month.
yes , 3000 shareds to Diff 2000Mh as 1500 to 4000Mh

[Kiawpqe]

Later I will remove the GPU6 that I have from the monitor in the MB and I will put it in a riser and change it for an nvidia 710 for only the monitor.
Then I will do some tests and changes in the PM config.txt and have what result gives everything in 24hrs.
I can't download the xfx 580 8gb dual bios 90 / 92w , any help?
the msi only at 80 / 83w

[miner29]

i try only pool.binance!
not Fee, one month.
yes , 3000 shareds to Diff 2000Mh as 1500 to 4000Mh

As it shoud be as diff goes up shares go down...but value of each share goes up so it is a wash.

Why this is important...if your mining effort is too small then you may not be able to find the higher difficulty share...so for some very small mining it is better to have a lower diff so you can actually hit blocks.  But generally this is not an issue.

[volig]

Hello. There is a problem: There are several rigs composition; win10, cards RX 580 8Gb, mother Asrock 81, driver 20.9.1 If after rebooting immediately turn on Phoenix v5.2c then the speed from the card is 30mh/s, and if you first run the nanominer v1.12.0 and then Phoenix, the speed on fenex rises more than 32mh/s and keeps stable. If the rig is reloaded, it will be 30mh/s again. To get 32mh/s, the operation with the launch of the nano miner must be repeated and then again it will be 32mh/s. Currently, no additional parameters are registered. If you pre-launch the nano miner only on one map, then the speed will increase only on one map. If you put strap 1 on the map where the speed is already 32mh/s, then the speed drops to 30 mh/s. What could be the problem? Which parameter should I add or change? This pattern always works on different rigs.

yes im having that problem too. it looks like 5.2a 5.2b 5.2c has that problem, also developer do not recommend 20.9.1 driver

I haven't tried all the other drivers. The 20.9.1 driver is recommended for Phoenix version 5.2 . The first page says that we recommend drivers from 19.12.2 to 20.11.1 (inclusive). Maybe someone checked on which drivers there is no such problem?

[batsonxl]

Later I will remove the GPU6 that I have from the monitor in the MB and I will put it in a riser and change it for an nvidia 710 for only the monitor.
Then I will do some tests and changes in the PM config.txt and have what result gives everything in 24hrs.
I can't download the xfx 580 8gb dual bios 90 / 92w , any help?
the msi only at 80 / 83w

add -mvddc 920-950 then it should be around 70-80w, . if it crashes on 920 then increase it.good luck

[sreetglide2011]

Hello. There is a problem: There are several rigs composition; win10, cards RX 580 8Gb, mother Asrock 81, driver 20.9.1 If after rebooting immediately turn on Phoenix v5.2c then the speed from the card is 30mh/s, and if you first run the nanominer v1.12.0 and then Phoenix, the speed on fenex rises more than 32mh/s and keeps stable. If the rig is reloaded, it will be 30mh/s again. To get 32mh/s, the operation with the launch of the nano miner must be repeated and then again it will be 32mh/s. Currently, no additional parameters are registered. If you pre-launch the nano miner only on one map, then the speed will increase only on one map. If you put strap 1 on the map where the speed is already 32mh/s, then the speed drops to 30 mh/s. What could be the problem? Which parameter should I add or change? This pattern always works on different rigs.

yes im having that problem too. it looks like 5.2a 5.2b 5.2c has that problem, also developer do not recommend 20.9.1 driver

I haven't tried all the other drivers. The 20.9.1 driver is recommended for Phoenix version 5.2 . The first page says that we recommend drivers from 19.12.2 to 20.11.1 (inclusive). Maybe someone checked on which drivers there is no such problem?

 19.12.2 to 20.8.1 (inclusive).

[volig]

Hello. There is a problem: There are several rigs composition; win10, cards RX 580 8Gb, mother Asrock 81, driver 20.9.1 If after rebooting immediately turn on Phoenix v5.2c then the speed from the card is 30mh/s, and if you first run the nanominer v1.12.0 and then Phoenix, the speed on fenex rises more than 32mh/s and keeps stable. If the rig is reloaded, it will be 30mh/s again. To get 32mh/s, the operation with the launch of the nano miner must be repeated and then again it will be 32mh/s. Currently, no additional parameters are registered. If you pre-launch the nano miner only on one map, then the speed will increase only on one map. If you put strap 1 on the map where the speed is already 32mh/s, then the speed drops to 30 mh/s. What could be the problem? Which parameter should I add or change? This pattern always works on different rigs.

yes im having that problem too. it looks like 5.2a 5.2b 5.2c has that problem, also developer do not recommend 20.9.1 driver

I haven't tried all the other drivers. The 20.9.1 driver is recommended for Phoenix version 5.2 . The first page says that we recommend drivers from 19.12.2 to 20.11.1 (inclusive). Maybe someone checked on which drivers there is no such problem?

 19.12.2 to 20.8.1 (inclusive).

Page 293, post 5843, author of the Phoenix Miner. Quote:Here are some additional notes:

With PhoenixMiner 5.2c either remove the -daglim option entirely, or set it to -daglim 4023, which should work on all 470/480/570/580/590 cards with "good" drivers (see bellow)
The -daglim option works only on Polaris cards (RX470, RX480, RX570, RX580, RX590). It limits the DAG size to <n> MB to allow mining on 4 GB cards a few weeks after epoch 374 on Windows (or after 380-383 on Linux). The possible values are the exact DAG limit in MB, or 0 (turn off the DAG limit), or 1 (automatic DAG limit size, usually around 4023 MB under Windows; this is the default option). Note that the  hashrate will drop significantly with each epoch after the DAG limit is in effect. If the hashrate drops too much (e.g. from 28 MH/s to just 2-3 MH/s, you need to use lower value, for example -daglim 3990
It is also important to use auto-tune (do not specify -gt values in the command line) because the optimal -gt value may change with each new epoch, and will definitely be different than before.
If you cards doesn't work with the default DAG limit of 4023 and require substantial decrease to 4006 or 3990, you need to update to one of the "good" AMD drivers for Windows: from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.11.1 (inclusive)
Using -rxboost, -vmr, or -straps on AMD cards requires running as administrator (or as root under Linux), so you need to run PhoenixMiner as administrator for the VRAM timing options to work. Note that the -mt option will still work without running as administrator/root.
The -rxboost option is only supported on GDDR5 cards (RX4xx/RX5xx or older).
The VRAM timing options can be quite different between the GPUs, even when the GPUs are the same model. Therefore, you can (and probably should) specify the VRAM timing options separately for each GPU.
Please let us know if you have any problems or questions related to PhoenixMiner 5.2c.

Where is my mistake?
Is the 20.9.1 driver recommended? Or do you need to put some other ones?
Dear developers please advise how to remove the error

[Nightworker88]

its the driver

use 20.4.2 (and updated intel driver!- if you have) -all will work like a charme!

( i use since some days also win 10 20h2, working perfect)

[sakorokas]

https://www.part.lt/img/7ed71afccfc9cec659ef7b66738131e5613.png


The same thing happens with 5.2c

How to solve this trouble ?

[Nightworker88]

you have to update PM to 5.2 c

[thatBeardoGuy]

I'm having a serious problem, All 8 of my RX580 8GB goes to 0.00Mh/s after an hour or so mostly when a new DAG is being created. It started happening only after I updated to Phoenix miner 5.2 (I am on Nicehash, Windows 10, AMD driver 20.7.2, also tried 20.9.2). My rig was stable from a month before updating Phoenix miner.  LOL miner works perfectly and TRM also works perfectly. Please Help!

[UnclWish]

I'm having a serious problem, All 8 of my RX580 8GB goes to 0.00Mh/s after an hour or so mostly when a new DAG is being created. It started happening only after I updated to Phoenix miner 5.2 (I am on Nicehash, Windows 10, AMD driver 20.7.2, also tried 20.9.2). My rig was stable from a month before updating Phoenix miner.  LOL miner works perfectly and TRM also works perfectly. Please Help!

Using Windows 10 1909, AMD 20.11.1 driver, PM 5.2c, nicehash, RX 580 8Gb cards - all fine. Miner works many hours without any problem.

[zergbitcore]

Version 5.2c still has low hashrate on my Radeon VII rig. 80MH/s instead of 91MH/s for several tasks on nicehash (sometimes 91MH/s sometimes 80MH/s).

[thatBeardoGuy]

I'm having a serious problem, All 8 of my RX580 8GB goes to 0.00Mh/s after an hour or so mostly when a new DAG is being created. It started happening only after I updated to Phoenix miner 5.2 (I am on Nicehash, Windows 10, AMD driver 20.7.2, also tried 20.9.2). My rig was stable from a month before updating Phoenix miner.  LOL miner works perfectly and TRM also works perfectly. Please Help!

Using Windows 10 1909, AMD 20.11.1 driver, PM 5.2c, nicehash, RX 580 8Gb cards - all fine. Miner works many hours without any problem.

Thanks for your reply, I want to ask how can you be on PM 5.2c ?, Nicehash software only updated it till 5.2b.  Also, can you please give some more details about your system: like the motherboard moel, Amount of RAM, Virtual memory and settings like PCIe link speed, and if you're using Overdrive N tool or MSI or both? And what parameters are you using with PM?

[UnclWish]

I'm having a serious problem, All 8 of my RX580 8GB goes to 0.00Mh/s after an hour or so mostly when a new DAG is being created. It started happening only after I updated to Phoenix miner 5.2 (I am on Nicehash, Windows 10, AMD driver 20.7.2, also tried 20.9.2). My rig was stable from a month before updating Phoenix miner.  LOL miner works perfectly and TRM also works perfectly. Please Help!

Using Windows 10 1909, AMD 20.11.1 driver, PM 5.2c, nicehash, RX 580 8Gb cards - all fine. Miner works many hours without any problem.

How can you be on PM 5.2c ?, Nicehash software only updated it till 5.2b.  Also, can you please give some more details about your system: like the motherboard moel, Amount of RAM, Virtual memory and settings like PCIe link speed, and if you're using Overdrive N tool or MSI or both?

I'm didn't use Nicehash software. I'm use PM miner with manual settings for nicehash pool.
Virtual memory is 8gb * amount of cards. I'm use modded vbioses.

You can update PM in nicehash. Just find folder with PM in nicehash folder and replace files.

[SpeedY_Hun]

Hello. There is a problem: There are several rigs composition; win10, cards RX 580 8Gb, mother Asrock 81, driver 20.9.1 If after rebooting immediately turn on Phoenix v5.2c then the speed from the card is 30mh/s, and if you first run the nanominer v1.12.0 and then Phoenix, the speed on fenex rises more than 32mh/s and keeps stable. If the rig is reloaded, it will be 30mh/s again. To get 32mh/s, the operation with the launch of the nano miner must be repeated and then again it will be 32mh/s. Currently, no additional parameters are registered. If you pre-launch the nano miner only on one map, then the speed will increase only on one map. If you put strap 1 on the map where the speed is already 32mh/s, then the speed drops to 30 mh/s. What could be the problem? Which parameter should I add or change? This pattern always works on different rigs.

20.8.1 will work

[volig]

Hello. There is a problem: There are several rigs composition; win10, cards RX 580 8Gb, mother Asrock 81, driver 20.9.1 If after rebooting immediately turn on Phoenix v5.2c then the speed from the card is 30mh/s, and if you first run the nanominer v1.12.0 and then Phoenix, the speed on fenex rises more than 32mh/s and keeps stable. If the rig is reloaded, it will be 30mh/s again. To get 32mh/s, the operation with the launch of the nano miner must be repeated and then again it will be 32mh/s. Currently, no additional parameters are registered. If you pre-launch the nano miner only on one map, then the speed will increase only on one map. If you put strap 1 on the map where the speed is already 32mh/s, then the speed drops to 30 mh/s. What could be the problem? Which parameter should I add or change? This pattern always works on different rigs.

20.8.1 will work

On the advice of the participants, I checked the work on the driver 20.4.2. Nothing changed, the problem remained. I think that the driver 20.8.1 will not change the situation. I'll check and let you know. Dear forum, this situation is only for me?

[bobben2]

Can confirm that 5.2c is working great with my RX 570  4Gb cards

Windows 10
Adrenalin 2019-Edition-18.12.3-Dec19 driver

2 x Sapphire Pulse Rx 570 4Gb cards mining ETH at 1100/2000 core/mem

hashrate now 29.9MH/s
hashrate before the DAG limitation: 30.3MH/s

[7anonminer7]

Can confirm that 5.2c is working great with my RX 570  4Gb cards

Windows 10
Adrenalin 2019-Edition-18.12.3-Dec19 driver

2 x Sapphire Pulse Rx 570 4Gb cards mining ETH at 1100/2000 core/mem

hashrate now 29.9MH/s
hashrate before the DAG limitation: 30.3MH/s

Happy for you. Could you please post your config settings? As you can see from my post I get 0 MH/s for my 4 x RX570 4G and I had to switch to lolminer which is unstable:

Hello.

I'm using PhoenixMiner 5.2c on Windows 10 with Adrenaline 19.7.5 drivers,  4 x 570RX 4GB cards in "compute mode" (VGA output connected to intergrated Intel GPU) with following settings:

Code:

-acm
-eres 1
-lidag 2
-tt -60,-45,-60,-60
-cclock 1050,1050,1050,1050
-cvddc 900,950,900,900
-mclock 1970,1970,1970,1970
-mvddc 850,850,850,850
-daglim 3990

Yet after DAG generation I get 0 Mh/s on every card, please advise what could be wrong, thank you.

PS. https://pastebin.com/Mb1asrvP <- the the log - I couldn't pinpoint anything strange or any errors that are in there though.

[FloppyPurpleGherkin]

Linux ETA?