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

[UnclWish]

there is no way to change to compute mod in win7?!!!

Only if you find some not official drivers. Official AMD drivers for Win7 can't do that.

P.S. You can try Blockchain drivers for Windows 7, but not all miners work with them...

[henry293]

just should change win?! its really funny!

[UnclWish]

just should change win?! its really funny!

No fun. Windows 7 is already old and Microsoft droped it support in january 2020.

[henry293]

but 7very better need lower ram lower vram lower every things its just for money that people go to buy new pc new gpu and ... its like a scam

[UnclWish]

but 7very better need lower ram lower vram lower every things its just for money that people go to buy new pc new gpu and ... its like a scam

It's your business - believe me or not. Read the end of post from Phoenix miner dev:

Let us reprint the important message from the first post about the mining after DAG epoch 350:

IMPORTANT! All owners of AMD cards with 4 GB RAM must upgrade to PhoenixMiner 5.0e or later version to continue mining after DAG epoch 350 (both ETH and ETC has already passed DAG epoch 350). Additionally, here are some important tips for longest possible usage of 4 GB AMD cards with PhoenixMiner 5.0e and later:

• If your rig is using Intel CPU, use the integrated graphics as primary display adapter. To do this, go to motherboard's BIOS setup and change the "Primary display adapter" to iGPU (or integrated GPU). Also, if you are using actual monitor or HDMI plug, put it in the motherboard video output.
• If you can't use integrated GPU, replace the primary GPU with one with 6 or 8 GB VRAM.
• Do not upgrade to a new AMD driver unless it is explicitly supported by PhoenixMiner. With 4 GB AMD cards, this will not only lower your hashrate but it will make impossible to mine when the DAG epoch is above 350.
• After the DAG epoch becomes more than 350, the optimal -gt value for the 4 GB AMD cards may change. So, we recommend to run auto-tune again after DAG epoch 350 to find the best GT values for the cards.

After extensive testing of AMD Windows drivers for the last two years or so, we identified two broad groups of drivers:

• Good drivers. These are versions from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.4.2 (inclusive). These will allow you to mine until DAG epoch 372-373 and won't need restart of PhoenixMiner on each DAG epoch change.
• Not so good drivers. These are versions 18.1.1 to 18.10.1 (inclusive), and from 19.8.1 to 19.12.1 (inclusive). This will allow you to mine until DAG epoch 365-366 and will require restart of PhoenixMiner on each DAG epoch change (for these drivers this will be preformed automatically unless you have added -dagrestart 0 command-line option to explicitly disable the auto-restart).
• If you are using a pool with automatic switching between the coins (like nicehash for example), you should use one of the good drivers above, and shouldn't use the -dagrestart option.
• Drivers older than 18.1.1 were not tested for 4 GB DAG operation. Specifically, there are multiple reports that the old blockchain drivers from 2017 doesn't work with 4 GB cards beyond epoch 350. If you are still using the blockchain drivers, you must upgrade to newer drivers if you have 4 GB AMD cards. After that, do not forget to turn on the Compute mode for all cards in AMD control center.

Under Linux all relatively recent drivers (i.e. last 24-36 months) allow mining until epoch 378-380 but there are much more driver bugs, so if you are happy with your current driver version, do not change it.

Please note that the usage of 4 GB AMD cards on Windows 7 is problematic, because the blockchain driver from 2017 doesn't seem to work properly with big DAGs, and the newer drivers do not support turning on the compute mode. There are some possible workarounds with patched/hacked drivers but we haven't tested them and can't tell you how to do it.

[henry293]

which driver is best for phoenix and give hashrate more than claymore in win10?

[UnclWish]

which driver is best for phoenix and give hashrate more than claymore in win10?

Hashrate is the same on Win10 at any drivers. You can use f.e. 20.4.2.
More than Claymore you can recieve only if you use PM with AMD Memory tweak tool to set REF parameter, cause PM didn't have -rxboost parameter.

[cscheat]

which driver is best for phoenix and give hashrate more than claymore in win10?

Hashrate is the same on Win10 at any drivers. You can use f.e. 20.4.2.
More than Claymore you can recieve only if you use PM with AMD Memory tweak tool to set REF parameter, cause PM didn't have -rxboost parameter.

Hi ! my issue with slowest hashrate for the last gpu fixed using 20.4.2 !

however, i would like to know how much longer can we mine ETH using 4GB cards ?  I am using Sapphire RX470 4GB

hashrate looks ok for now.. But the Phoenix miner say "good for EPOCH up to 355"

[UnclWish]

which driver is best for phoenix and give hashrate more than claymore in win10?

Hashrate is the same on Win10 at any drivers. You can use f.e. 20.4.2.
More than Claymore you can recieve only if you use PM with AMD Memory tweak tool to set REF parameter, cause PM didn't have -rxboost parameter.

Hi ! my issue with slowest hashrate for the last gpu fixed using 20.4.2 !

however, i would like to know how much longer can we mine ETH using 4GB cards ?  I am using Sapphire RX470 4GB

hashrate looks ok for now.. But the Phoenix miner say "good for EPOCH up to 355"

Read carefully "Good drivers".

Let us reprint the important message from the first post about the mining after DAG epoch 350:

IMPORTANT! All owners of AMD cards with 4 GB RAM must upgrade to PhoenixMiner 5.0e or later version to continue mining after DAG epoch 350 (both ETH and ETC has already passed DAG epoch 350). Additionally, here are some important tips for longest possible usage of 4 GB AMD cards with PhoenixMiner 5.0e and later:

• If your rig is using Intel CPU, use the integrated graphics as primary display adapter. To do this, go to motherboard's BIOS setup and change the "Primary display adapter" to iGPU (or integrated GPU). Also, if you are using actual monitor or HDMI plug, put it in the motherboard video output.
• If you can't use integrated GPU, replace the primary GPU with one with 6 or 8 GB VRAM.
• Do not upgrade to a new AMD driver unless it is explicitly supported by PhoenixMiner. With 4 GB AMD cards, this will not only lower your hashrate but it will make impossible to mine when the DAG epoch is above 350.
• After the DAG epoch becomes more than 350, the optimal -gt value for the 4 GB AMD cards may change. So, we recommend to run auto-tune again after DAG epoch 350 to find the best GT values for the cards.

After extensive testing of AMD Windows drivers for the last two years or so, we identified two broad groups of drivers:

• Good drivers. These are versions from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.4.2 (inclusive). These will allow you to mine until DAG epoch 372-373 and won't need restart of PhoenixMiner on each DAG epoch change.
• Not so good drivers. These are versions 18.1.1 to 18.10.1 (inclusive), and from 19.8.1 to 19.12.1 (inclusive). This will allow you to mine until DAG epoch 365-366 and will require restart of PhoenixMiner on each DAG epoch change (for these drivers this will be preformed automatically unless you have added -dagrestart 0 command-line option to explicitly disable the auto-restart).
• If you are using a pool with automatic switching between the coins (like nicehash for example), you should use one of the good drivers above, and shouldn't use the -dagrestart option.
• Drivers older than 18.1.1 were not tested for 4 GB DAG operation. Specifically, there are multiple reports that the old blockchain drivers from 2017 doesn't work with 4 GB cards beyond epoch 350. If you are still using the blockchain drivers, you must upgrade to newer drivers if you have 4 GB AMD cards. After that, do not forget to turn on the Compute mode for all cards in AMD control center.

Under Linux all relatively recent drivers (i.e. last 24-36 months) allow mining until epoch 378-380 but there are much more driver bugs, so if you are happy with your current driver version, do not change it.

Please note that the usage of 4 GB AMD cards on Windows 7 is problematic, because the blockchain driver from 2017 doesn't seem to work properly with big DAGs, and the newer drivers do not support turning on the compute mode. There are some possible workarounds with patched/hacked drivers but we haven't tested them and can't tell you how to do it.

[cscheat]

which driver is best for phoenix and give hashrate more than claymore in win10?

Hashrate is the same on Win10 at any drivers. You can use f.e. 20.4.2.
More than Claymore you can recieve only if you use PM with AMD Memory tweak tool to set REF parameter, cause PM didn't have -rxboost parameter.

Hi ! my issue with slowest hashrate for the last gpu fixed using 20.4.2 !

however, i would like to know how much longer can we mine ETH using 4GB cards ?  I am using Sapphire RX470 4GB

hashrate looks ok for now.. But the Phoenix miner say "good for EPOCH up to 355"

Read carefully "Good drivers".

Let us reprint the important message from the first post about the mining after DAG epoch 350:

IMPORTANT! All owners of AMD cards with 4 GB RAM must upgrade to PhoenixMiner 5.0e or later version to continue mining after DAG epoch 350 (both ETH and ETC has already passed DAG epoch 350). Additionally, here are some important tips for longest possible usage of 4 GB AMD cards with PhoenixMiner 5.0e and later:

• If your rig is using Intel CPU, use the integrated graphics as primary display adapter. To do this, go to motherboard's BIOS setup and change the "Primary display adapter" to iGPU (or integrated GPU). Also, if you are using actual monitor or HDMI plug, put it in the motherboard video output.
• If you can't use integrated GPU, replace the primary GPU with one with 6 or 8 GB VRAM.
• Do not upgrade to a new AMD driver unless it is explicitly supported by PhoenixMiner. With 4 GB AMD cards, this will not only lower your hashrate but it will make impossible to mine when the DAG epoch is above 350.
• After the DAG epoch becomes more than 350, the optimal -gt value for the 4 GB AMD cards may change. So, we recommend to run auto-tune again after DAG epoch 350 to find the best GT values for the cards.

After extensive testing of AMD Windows drivers for the last two years or so, we identified two broad groups of drivers:

• Good drivers. These are versions from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.4.2 (inclusive). These will allow you to mine until DAG epoch 372-373 and won't need restart of PhoenixMiner on each DAG epoch change.
• Not so good drivers. These are versions 18.1.1 to 18.10.1 (inclusive), and from 19.8.1 to 19.12.1 (inclusive). This will allow you to mine until DAG epoch 365-366 and will require restart of PhoenixMiner on each DAG epoch change (for these drivers this will be preformed automatically unless you have added -dagrestart 0 command-line option to explicitly disable the auto-restart).
• If you are using a pool with automatic switching between the coins (like nicehash for example), you should use one of the good drivers above, and shouldn't use the -dagrestart option.
• Drivers older than 18.1.1 were not tested for 4 GB DAG operation. Specifically, there are multiple reports that the old blockchain drivers from 2017 doesn't work with 4 GB cards beyond epoch 350. If you are still using the blockchain drivers, you must upgrade to newer drivers if you have 4 GB AMD cards. After that, do not forget to turn on the Compute mode for all cards in AMD control center.

Under Linux all relatively recent drivers (i.e. last 24-36 months) allow mining until epoch 378-380 but there are much more driver bugs, so if you are happy with your current driver version, do not change it.

Please note that the usage of 4 GB AMD cards on Windows 7 is problematic, because the blockchain driver from 2017 doesn't seem to work properly with big DAGs, and the newer drivers do not support turning on the compute mode. There are some possible workarounds with patched/hacked drivers but we haven't tested them and can't tell you how to do it.

20.4.2 i confirm is good ! Thanks !

[UnclWish]

20.4.2 i confirm is good ! Thanks !

I'm about epoch, that you asked. 372-373.

[cscheat]

20.4.2 i confirm is good ! Thanks !

I'm about epoch, that you asked. 372-373.

so you mean we can mine ETH at full speed till EPOCH 372-373 ?

however, I saw this at Phoenix Miner start up

2020.08.05:20:44:19.538: GPU1 Light cache generated in 3.8 s (15.7 MB/s)
2020.08.05:20:44:20.646: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB
2020.08.05:20:44:20.646: GPU1 GPU1: Allocating DAG (3.77) GB; good for epoch up to #355
2020.08.05:20:44:20.726: GPU1 GPU1: Generating DAG for epoch #353

[UnclWish]

20.4.2 i confirm is good ! Thanks !

I'm about epoch, that you asked. 372-373.

so you mean we can mine ETH at full speed till EPOCH 372-373 ?

however, I saw this at Phoenix Miner start up

2020.08.05:20:44:19.538: GPU1 Light cache generated in 3.8 s (15.7 MB/s)
2020.08.05:20:44:20.646: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB
2020.08.05:20:44:20.646: GPU1 GPU1: Allocating DAG (3.77) GB; good for epoch up to #355
2020.08.05:20:44:20.726: GPU1 GPU1: Generating DAG for epoch #353

It's not maximum. It's miner reserve 3.77Gb vmem and this used mem can be used up to 355 epoch just in this session.

[cscheat]

20.4.2 i confirm is good ! Thanks !

I'm about epoch, that you asked. 372-373.

so you mean we can mine ETH at full speed till EPOCH 372-373 ?

however, I saw this at Phoenix Miner start up

2020.08.05:20:44:19.538: GPU1 Light cache generated in 3.8 s (15.7 MB/s)
2020.08.05:20:44:20.646: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB
2020.08.05:20:44:20.646: GPU1 GPU1: Allocating DAG (3.77) GB; good for epoch up to #355
2020.08.05:20:44:20.726: GPU1 GPU1: Generating DAG for epoch #353

It's not maximum. It's miner reserve 3.77Gb vmem and this used mem can be used up to 355 epoch just in this session.

so you mean I still have lots of room for ETH till November ? hahah ! See Free VRAM: 3.948 GB; used: 0.052 GB message above

[UnclWish]

20.4.2 i confirm is good ! Thanks !

I'm about epoch, that you asked. 372-373.

so you mean we can mine ETH at full speed till EPOCH 372-373 ?

however, I saw this at Phoenix Miner start up

2020.08.05:20:44:19.538: GPU1 Light cache generated in 3.8 s (15.7 MB/s)
2020.08.05:20:44:20.646: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB
2020.08.05:20:44:20.646: GPU1 GPU1: Allocating DAG (3.77) GB; good for epoch up to #355
2020.08.05:20:44:20.726: GPU1 GPU1: Generating DAG for epoch #353

It's not maximum. It's miner reserve 3.77Gb vmem and this used mem can be used up to 355 epoch just in this session.

so you mean I still have lots of room for ETH till November ? hahah ! See Free VRAM: 3.948 GB; used: 0.052 GB message above

Sure.

[cscheat]

20.4.2 i confirm is good ! Thanks !

I'm about epoch, that you asked. 372-373.

so you mean we can mine ETH at full speed till EPOCH 372-373 ?

however, I saw this at Phoenix Miner start up

2020.08.05:20:44:19.538: GPU1 Light cache generated in 3.8 s (15.7 MB/s)
2020.08.05:20:44:20.646: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB
2020.08.05:20:44:20.646: GPU1 GPU1: Allocating DAG (3.77) GB; good for epoch up to #355
2020.08.05:20:44:20.726: GPU1 GPU1: Generating DAG for epoch #353

It's not maximum. It's miner reserve 3.77Gb vmem and this used mem can be used up to 355 epoch just in this session.

so you mean I still have lots of room for ETH till November ? hahah ! See Free VRAM: 3.948 GB; used: 0.052 GB message above

Sure.

3.948GB - 3.77GB = 178MB headroom left..good

https://i.imgur.com/HzCIpmW.png

[cryptoyes]

@PhoenixMiner Would it be possible for you to implement devfee on nicehash so that when mining on nicehash it won't reload the DAG so often? You mine devfee every 1.5 hours for 38 seconds, but the dag reload in a system with many cards can go up to 10-15 seconds, which has to be done twice ... it also makes it more prone to crashing, as you know. I'd rather pay you for the 38 seconds than trying to redirect the devfee to myself but wasting 30 seconds anyway due to the double DAG loading.

Alternatively, if the cards have enough memory, then why not load both DAGs at the beginning only once?

[UnclWish]

AMD driver 20.8.1 is supported by PM. I just installed it. PM recognized it like 20.7.1 and works.

[cscheat]

AMD driver 20.8.1 is supported by PM. I just installed it. PM recognized it like 20.7.1 and works.

One issue is MSI Afterburner voltage adjustment won't work after setting the display to onboard intel display...

also the MSI Afterburner Fan Target Temp won't work...

[UnclWish]

AMD driver 20.8.1 is supported by PM. I just installed it. PM recognized it like 20.7.1 and works.

One issue is MSI Afterburner voltage adjustment won't work after setting the display to onboard intel display...

also the MSI Afterburner Fan Target Temp won't work...

It's not driver issue, it's Afterburner problem...