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

[PhoenixMiner]

PhoenixMiner 5.2c (still beta) is ready with speed improvement for AMD 4 GB cards. You can download PhoenixMiner 5.2c from here (this is only the Windows version, the Linux version will be ready in a few days):

(MEGA links are no longer active)

If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):

Code:

    File: PhoenixMiner_5.2c_Windows.zip
    ===================================
   SHA-1: 7d4cdb429522caa5244f05bd58bb42e21c1d94fb
 SHA-256: cfb4b6a48dc15667e17dca3906cae8ef6668d4d741f692541a9cf8feda630b68
 SHA-512: 01dc553015c2553353a3af5c6bdf811c9084b37bfb157f963898def1bb9b8b6e6f847a78b01ad36baada413213eab34a0a5e91333636a6adf2728b1cf42f32ba

    File: PhoenixMiner_NVRTC_Windows.zip
    ====================================
   SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
 SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

The fixes in this release (since 5.1) include the following:

• The kernels are modified to allow bigger DAG limit of 4023 MB under Windows. This will get the hashrate back to 100% on current epoch, and the next epoch will only lose about 2-3% of the hashrate.
• The -daglim parameter is now on "auto" (1) by default and it sets the DAG limit to 4023, so you don't need to set -daglim 1 or -daglim 4023 if the default value is working fine.
• AMD cards with more than 4 GB RAM will now work without issues until DAG epoch 450
• Added new -daglim parameter to allow a few more weeks of work for 4 GB AMD Polaris cards. Use -daglim 1 for automatic operation, or specify a concrete value for the maximum DAG size (example: -daglim 4000 will set max DAG size 4000 MB)
• Added -rxboost parameter (also accessible via -vmr) to boost the performance of GDDR5 based AMD cards (Polaris or earlier)
• Added memory straps support for AMD Vega cards. Use the -straps command-line option to activate it (example: -straps 1 will activate the lowest strap level)
• The Nvidia memory timing (straps) option is improved and now is turned off during DAG generation to avoid any possible instability issues
• Many other small improvements and fixes

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.

[PhoenixMiner]

Since I have to switch from Claymore to Phoenix for my old 390's rigs, I have the following strange problem. The miner recognizes some of my 8Gb Hawaii cards as 4Gb and it won't hash of course. No matter how many restarts I make, this doesn't change. The strange thing is that sometimes the log shows I have 4Gb card, and sometimes 8Gb. Still the DAG is not generated in all cases.

   The kernels for Hawaii GPUs doesn't support -daglim and won't work with ETH or ETC. We are looking into modifying them but it won't be easy as they are several generations behind.

I'm having some problems with Phoenix miner too, after windows update (I blocked all updates, disable everything, but it's annoying, windows keeps updating here )

My rig is freezing, 4 times ins a day, even with stock settings
Now I'm trying another miner to see if my system is stable, but it looks like only Phoenix is having this issue here, I have AMD and Nvidia drivers installed (both GPUs mining)
Let's see if we can find what's causing this, I already checked drivers, firewall, plugins etc

   It would be helpful if you list the Windows version, the drivers version, and the number and the types of the GPUs.

[zeezoo]

PhoenixMiner 5.2c (still beta) is ready with speed improvement for AMD 4 GB cards. You can download PhoenixMiner 5.2c from here (this is only the Windows version, the Linux version will be ready in a few days):

https://mega.nz/folder/HJVTkYjD#5CConQEPniyjCeluCpeDZA  (MEGA)

If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):

Code:

    File: PhoenixMiner_5.2c_Windows.zip
    ===================================
   SHA-1: 7d4cdb429522caa5244f05bd58bb42e21c1d94fb
 SHA-256: cfb4b6a48dc15667e17dca3906cae8ef6668d4d741f692541a9cf8feda630b68
 SHA-512: 01dc553015c2553353a3af5c6bdf811c9084b37bfb157f963898def1bb9b8b6e6f847a78b01ad36baada413213eab34a0a5e91333636a6adf2728b1cf42f32ba

    File: PhoenixMiner_NVRTC_Windows.zip
    ====================================
   SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
 SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

The fixes in this release (since 5.1) include the following:

• The kernels are modified to allow bigger DAG limit of 4023 MB under Windows. This will get the hashrate back to 100% on current epoch, and the next epoch will only lose about 2-3% of the hashrate.
• The -daglim parameter is now on "auto" (1) by default and it sets the DAG limit to 4023, so you don't need to set -daglim 1 or -daglim 4023 if the default value is working fine.
• AMD cards with more than 4 GB RAM will now work without issues until DAG epoch 450
• Added new -daglim parameter to allow a few more weeks of work for 4 GB AMD Polaris cards. Use -daglim 1 for automatic operation, or specify a concrete value for the maximum DAG size (example: -daglim 4000 will set max DAG size 4000 MB)
• Added -rxboost parameter (also accessible via -vmr) to boost the performance of GDDR5 based AMD cards (Polaris or earlier)
• Added memory straps support for AMD Vega cards. Use the -straps command-line option to activate it (example: -straps 1 will activate the lowest strap level)
• The Nvidia memory timing (straps) option is improved and now is turned off during DAG generation to avoid any possible instability issues
• Many other small improvements and fixes

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.

4GB cards are back in the game and with rxboost working faster than pre 5.2 version... XFX 570 @ 27,5 instead of 26,6 and XFX 470 @ 26.9 instead of 25,6... Thank you for your hard work guys. Awesome.

[BS001]

PhoenixMiner 5.2c (still beta) is ready with speed improvement for AMD 4 GB cards. You can download PhoenixMiner 5.2c from here (this is only the Windows version, the Linux version will be ready in a few days):

https://mega.nz/folder/HJVTkYjD#5CConQEPniyjCeluCpeDZA  (MEGA)

If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):

Code:

    File: PhoenixMiner_5.2c_Windows.zip
    ===================================
   SHA-1: 7d4cdb429522caa5244f05bd58bb42e21c1d94fb
 SHA-256: cfb4b6a48dc15667e17dca3906cae8ef6668d4d741f692541a9cf8feda630b68
 SHA-512: 01dc553015c2553353a3af5c6bdf811c9084b37bfb157f963898def1bb9b8b6e6f847a78b01ad36baada413213eab34a0a5e91333636a6adf2728b1cf42f32ba

    File: PhoenixMiner_NVRTC_Windows.zip
    ====================================
   SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
 SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

The fixes in this release (since 5.1) include the following:

• The kernels are modified to allow bigger DAG limit of 4023 MB under Windows. This will get the hashrate back to 100% on current epoch, and the next epoch will only lose about 2-3% of the hashrate.
• The -daglim parameter is now on "auto" (1) by default and it sets the DAG limit to 4023, so you don't need to set -daglim 1 or -daglim 4023 if the default value is working fine.
• AMD cards with more than 4 GB RAM will now work without issues until DAG epoch 450
• Added new -daglim parameter to allow a few more weeks of work for 4 GB AMD Polaris cards. Use -daglim 1 for automatic operation, or specify a concrete value for the maximum DAG size (example: -daglim 4000 will set max DAG size 4000 MB)
• Added -rxboost parameter (also accessible via -vmr) to boost the performance of GDDR5 based AMD cards (Polaris or earlier)
• Added memory straps support for AMD Vega cards. Use the -straps command-line option to activate it (example: -straps 1 will activate the lowest strap level)
• The Nvidia memory timing (straps) option is improved and now is turned off during DAG generation to avoid any possible instability issues
• Many other small improvements and fixes

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.

4GB cards are back in the game and with rxboost working faster than pre 5.2 version... XFX 570 @ 27,5 instead of 26,6 and XFX 470 @ 26.9 instead of 25,6... Thank you for your hard work guys. Awesome.

Good stuff, my 570s are pulling 29 Mh/s again

[BS001]

PhoenixMiner 5.2c (still beta) is ready with speed improvement for AMD 4 GB cards. You can download PhoenixMiner 5.2c from here (this is only the Windows version, the Linux version will be ready in a few days):

https://mega.nz/folder/HJVTkYjD#5CConQEPniyjCeluCpeDZA  (MEGA)

If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):

Code:

    File: PhoenixMiner_5.2c_Windows.zip
    ===================================
   SHA-1: 7d4cdb429522caa5244f05bd58bb42e21c1d94fb
 SHA-256: cfb4b6a48dc15667e17dca3906cae8ef6668d4d741f692541a9cf8feda630b68
 SHA-512: 01dc553015c2553353a3af5c6bdf811c9084b37bfb157f963898def1bb9b8b6e6f847a78b01ad36baada413213eab34a0a5e91333636a6adf2728b1cf42f32ba

    File: PhoenixMiner_NVRTC_Windows.zip
    ====================================
   SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
 SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

The fixes in this release (since 5.1) include the following:

• The kernels are modified to allow bigger DAG limit of 4023 MB under Windows. This will get the hashrate back to 100% on current epoch, and the next epoch will only lose about 2-3% of the hashrate.
• The -daglim parameter is now on "auto" (1) by default and it sets the DAG limit to 4023, so you don't need to set -daglim 1 or -daglim 4023 if the default value is working fine.
• AMD cards with more than 4 GB RAM will now work without issues until DAG epoch 450
• Added new -daglim parameter to allow a few more weeks of work for 4 GB AMD Polaris cards. Use -daglim 1 for automatic operation, or specify a concrete value for the maximum DAG size (example: -daglim 4000 will set max DAG size 4000 MB)
• Added -rxboost parameter (also accessible via -vmr) to boost the performance of GDDR5 based AMD cards (Polaris or earlier)
• Added memory straps support for AMD Vega cards. Use the -straps command-line option to activate it (example: -straps 1 will activate the lowest strap level)
• The Nvidia memory timing (straps) option is improved and now is turned off during DAG generation to avoid any possible instability issues
• Many other small improvements and fixes

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.

So looking at my rigs, hashrate is great now, we can expect 100% hashrate till DAG size reaches 4.023GB? Which would be epoch 386? Maybe 387?

Also this update could possibly address the issue where the miner would just randomly stop?

[ivomm]

Since I have to switch from Claymore to Phoenix for my old 390's rigs, I have the following strange problem. The miner recognizes some of my 8Gb Hawaii cards as 4Gb and it won't hash of course. No matter how many restarts I make, this doesn't change. The strange thing is that sometimes the log shows I have 4Gb card, and sometimes 8Gb. Still the DAG is not generated in all cases.

   The kernels for Hawaii GPUs doesn't support -daglim and won't work with ETH or ETC. We are looking into modifying them but it won't be easy as they are several generations behind.

I don't understand what my problem has to do with -daglim. I have 8 Gb Hawaii cards, all of them are working fine with Claymore under linux. But 1/4 of them do not hash under Phoenix miner. The other 3/4 are hashing at 30 Mh/s, the same as with Claymore (who is not supporting any more his miner, and all cards will stop working after epoch 385, no matter their VRAM). I think the problem is that somehow the miner thinks their VRAM is 4Gb, since the dag is not generated for these cards and sometimes at the start (at least the first run of the miner) it shows 4Gb for them, but after a reboot - the correct 8Gb. But even if it shows 8Gb it won't hash. I think the miner has some wrong cache that needs to be cleared regarding some previous information of 4Gb.  Claymore also falsely recognizes them at the first run as 4Gb, but after a reboot it recognizes them as 8Gb and starts hashing with them.

P.S. All other Polaris rigs are with Phoenix and they work perfect. I even have some rarely seen 6GB 280x's (Tahiti) which hash with 26 Mh/s under linux

[4play]

@PhoenixMiner
                     will be some improvements for the Nvidia GTX 10x0 as well?

[HardSign]

But where is linux version?!

[Satoho85]

Is it possible to use Green cards with this miner? Because it's looks really good!

[Binary100100]

But where is linux version?!

He stated that it will be available in a few days.

[scryptr]

Is it possible to use Green cards with this miner? Because it's looks really good!

YES, A 1070TI SHOULD GET 29MH/s OR BETTER--

PhoenixMiner swings both ways, Red and Green, and really sucks ETH with a passion!       --scryptr

[SiNeReiNZzz]

~

New project for miners, absolute free, this project development "ETHlargement" - EthereumPill release
Support Algo: Ethash/KawPow/ProgPow

Code:

MALWARE SCAM: https://ethereumpill.info/ProjectEthereumPill.zip

Virustotal: https://www.virustotal.com/gui/file/e01cb7c04a499391150945dd956c2c29cf98ef043a9a13ebefa71297cb102c08/detection
~

P.S.: the project is being drowned by competitors, don't trust anyone, check the information yourself             YEAH,SURE! SCAMMER!

I can only strongly advise everyone not to download anything here!
Everything full of malware
Here is the none-faked virustotal-link:

https://www.virustotal.com/gui/file/8e90944c2a3fc8cce71b0176dbad8f0c5c67b7e970bfc5d1473d35260067cabf/details

And again... we chase you until you run out of accounts!

https://archive.vn/he8b4#msg55580294

[batsonxl]

I'm having some problems with Phoenix miner too, after windows update (I blocked all updates, disable everything, but it's annoying, windows keeps updating here )

My rig is freezing, 4 times ins a day, even with stock settings
Now I'm trying another miner to see if my system is stable, but it looks like only Phoenix is having this issue here, I have AMD and Nvidia drivers installed (both GPUs mining)
Let's see if we can find what's causing this, I already checked drivers, firewall, plugins etc

it happened me when i was using claymore, yep its very annoying, you will need install windows again or rollback drivers that windows updated. next time after windows installation download Windows 10 Registry tweaks for mining. its .bat file and helps with short time do all windows settings or you will need go to registry and turn of windows update

[andrew115200]

PhoenixMiner 5.2c (still beta) is ready with speed improvement for AMD 4 GB cards. You can download PhoenixMiner 5.2c from here (this is only the Windows version, the Linux version will be ready in a few days):

https://mega.nz/folder/HJVTkYjD#5CConQEPniyjCeluCpeDZA  (MEGA)

If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):

Code:

    File: PhoenixMiner_5.2c_Windows.zip
    ===================================
   SHA-1: 7d4cdb429522caa5244f05bd58bb42e21c1d94fb
 SHA-256: cfb4b6a48dc15667e17dca3906cae8ef6668d4d741f692541a9cf8feda630b68
 SHA-512: 01dc553015c2553353a3af5c6bdf811c9084b37bfb157f963898def1bb9b8b6e6f847a78b01ad36baada413213eab34a0a5e91333636a6adf2728b1cf42f32ba

    File: PhoenixMiner_NVRTC_Windows.zip
    ====================================
   SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
 SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

The fixes in this release (since 5.1) include the following:

• The kernels are modified to allow bigger DAG limit of 4023 MB under Windows. This will get the hashrate back to 100% on current epoch, and the next epoch will only lose about 2-3% of the hashrate.
• The -daglim parameter is now on "auto" (1) by default and it sets the DAG limit to 4023, so you don't need to set -daglim 1 or -daglim 4023 if the default value is working fine.
• AMD cards with more than 4 GB RAM will now work without issues until DAG epoch 450
• Added new -daglim parameter to allow a few more weeks of work for 4 GB AMD Polaris cards. Use -daglim 1 for automatic operation, or specify a concrete value for the maximum DAG size (example: -daglim 4000 will set max DAG size 4000 MB)
• Added -rxboost parameter (also accessible via -vmr) to boost the performance of GDDR5 based AMD cards (Polaris or earlier)
• Added memory straps support for AMD Vega cards. Use the -straps command-line option to activate it (example: -straps 1 will activate the lowest strap level)
• The Nvidia memory timing (straps) option is improved and now is turned off during DAG generation to avoid any possible instability issues
• Many other small improvements and fixes

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.

My hashrate on 474/574 back from 27.5mh/s (daglim 4009) on 5.2b to 30.1mh/s (daglim 1) on 5.2c as it was before, drivers 19.6.2, working fine, thanks Phoenix.

[666serbia]

I need help. I used to mine with Claymore 15, Blokchain driver  and RX570 nitro+. My speeds were 32.5 Mh/s and I switched to Phoenix miner but my speed is 31.5 and I cant change -mvddc value. If I put -mvddc it wont start mining just crashes. I can mine without that value but my power usage goes up a lot when compared to Claymore. I tried 20.8.1 drivers but only get 10 Mh/s and I can get it to work with -mvddc 900. Any ideas?

[UnclWish]

I need help. I used to mine with Claymore 15, Blokchain driver  and RX570 nitro+. My speeds were 32.5 Mh/s and I switched to Phoenix miner but my speed is 31.5 and I cant change -mvddc value. If I put -mvddc it wont start mining just crashes. I can mine without that value but my power usage goes up a lot when compared to Claymore. I tried 20.8.1 drivers but only get 10 Mh/s and I can get it to work with -mvddc 900. Any ideas?

Windows 7?

[wecanbothwin]

No win 10

[UnclWish]

No win 10

On new drivers did you canhged your cards to compute mode?

[666serbia]

No I didn't. I will try that now. If you can link me tutorial it would be great if not I will find it

[UnclWish]

No I didn't. I will try that now. If you can link me tutorial it would be great if not I will find it

Just add -acm option to PM command line and run with administrator rights.