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

[br2459]

Hi all,

I have 13 x RTX580 4GB cards, I can still have 5.4c version running, but the hashrate is no more than 9.3MHs per card. Is there any way to still use them or are they condemned to die?
Last year I was mining @ 31 per card, now is less than 1/3, is the power consumption also reduced towards 31MHs or it's still consuming the same but the result is 1/3 (9.3MHs) ?

Just let it die. DAG is over 4GB now so it's pretty surprising that they still are running at all.

[Permonik]

Hi all,

I have 13 x RTX580 4GB cards, I can still have 5.4c version running, but the hashrate is no more than 9.3MHs per card. Is there any way to still use them or are they condemned to die?
Last year I was mining @ 31 per card, now is less than 1/3, is the power consumption also reduced towards 31MHs or it's still consuming the same but the result is 1/3 (9.3MHs) ?

580 with 4GB is done on the ETH.

You can try to mine ETC with full speed.

[Jonet]

Hi all,

I have 13 x RTX580 4GB cards, I can still have 5.4c version running, but the hashrate is no more than 9.3MHs per card. Is there any way to still use them or are they condemned to die?
Last year I was mining @ 31 per card, now is less than 1/3, is the power consumption also reduced towards 31MHs or it's still consuming the same but the result is 1/3 (9.3MHs) ?

580 with 4GB is done on the ETH.

You can try to mine ETC with full speed.

If You switch to Linux You will get around 20 MHs om ETH. Far better than 30 on ETC.
Performance on ETH will sink on each New epoc though.

[batsonxl]

Hi all,

I have 13 x RTX580 4GB cards, I can still have 5.4c version running, but the hashrate is no more than 9.3MHs per card. Is there any way to still use them or are they condemned to die?
Last year I was mining @ 31 per card, now is less than 1/3, is the power consumption also reduced towards 31MHs or it's still consuming the same but the result is 1/3 (9.3MHs) ?

580 with 4GB is done on the ETH.

You can try to mine ETC with full speed.

If You switch to Linux You will get around 20 MHs om ETH. Far better than 30 on ETC.
Performance on ETH will sink on each New epic though.

yes i agree. after dag reduction and hashrate grow etc profit waaaaay down than used before. i was exited 1st day then slowly dissapointed on etc.

[mercurius10]

I ask you a question, I am new.

Can you mine with a Geforce GTX 980 TI

start_miner.bat:

REM
REM Example bat file for starting PhoenixMiner.exe to mine ETH
REM

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 90

REM IMPORTANT: Replace the ETH address with your own ETH wallet address in the -wal option (Rig001 is the name of the rig)
PhoenixMiner.exe -pool ssl://us1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0x07dc04bc7c9ab4fc9bdf3a1ccf9b6b8b53df622a.Rig001
pause

...

And on the other hand when I execute start_miner.bat and the DAC reaches 97%, then the screen goes black, and it throws me the following error:


CUDA version: 11.0, CUDA runtime: 8.0
No OpenCL platforms found
Available GPUs for mining:
GPU1: GeForce GTX 980 Ti (pcie , CUDA cap. 5.2, 6 GB VRAM, 22 CUs
Nvidia driver version: 461.09
Eth: the pool list contains 2 pools (2 from command-line)
Eth: primary pool: ssl://us1.ethermine.org:5555
Starting GPU mining
Eth: Connecting to ethash pool ssl://us1.ethermine.org:5555 (proto: EthProxy)
GPU1: 51C 0% 18W
GPUs power: 18.0 W
Eth: Connected to SSL ethash pool us1.ethermine.org:5555 (172.65.218.238)
Listening for CDM remote manager at port 3333 in read-only mode
Eth: New job #a64bac20 from ssl://us1.ethermine.org:5555; diff: 4000MH
GPU1: Starting up... (0)
GPU1: Generating ethash light cache for epoch #388
Light cache generated in 1.9 s (34.2 MB/s)
GPU1: Allocating DAG (4.05) GB; good for epoch up to #390
GPU1: Generating DAG for epoch #388
Eth: New job #a3185cbe from ssl://us1.ethermine.org:5555; diff: 4000MH
GPU1: DAG  13%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPU1: DAG  27%
GPU1: DAG  41%
Eth: New job #2c75af58 from ssl://us1.ethermine.org:5555; diff: 4000MH
Eth: New job #ccddc397 from ssl://us1.ethermine.org:5555; diff: 4000MH
Eth: New job #aadfef96 from ssl://us1.ethermine.org:5555; diff: 4000MH
GPU1: DAG  55%
GPU1: DAG  69%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPU1: DAG  83%
Eth: New job #4f8511a3 from ssl://us1.ethermine.org:5555; diff: 4000MH
GPU1: DAG  97%
GPU1: DAG generated in 10.8 s (382.1 MB/s)
GPU1: Using v2 Ethash CUDA kernels (GeForce GTX 980 Ti)
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #7d2f9679 from ssl://us1.ethermine.org:5555; diff: 4000MH
CUDA error in CudaProgram.cu:465 : unknown error (999)
GPU1 search error: unknown error
Fatal error detected. Restarting.
Eth: New job #593be957 from ssl://us1.ethermine.org:5555; diff: 4000MH


can this be fixed?

[miner29]

Im showing a gtx980ti is cuda 6.0. ... and you are using cuda 11.0
Thats all i notice right away....besides the fail near the bottom

[scryptr]

A GTX 980TI HAS GDDR5X VRAM--

But there was no "Pill" for this Maxwell chip GPU.  It mined ETH at 26MH/s at best and used more energy than a GTX 1080ti mining at 35-50MH/s (depending on tuning and pill-taking).

It will mine ETH with the right miner.  If the miner is not compiled to include Maxwell-chip compatibility, it won't work.  If you compile the stock Ethereum miner (no fee, free, open-source), it will mine ETH.  You will need to set the compile options to include Maxwell chips.

--scryptr

EDIT:  I have a couple 980ti cards, but I don't feel like plugging them in.  Try setting options for CUDA kernels and "nvmem"?  Good luck!

--scryptr

[PhoenixMiner]

The new beta version is ready. You can download PhoenixMiner 5.5b from here:

(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.5b_Windows.zip
    ===================================
   SHA-1: 52ac75b2c8d5432aeb88900f034045d2bf023395
 SHA-256: 10e022d95514a682d749a593042f02b6f6a8adea112c470c68a3ae7b7b1cb187
 SHA-512: 84dbc3df53c38cd0d1956f92c4eb0226341e3230102d0214661bd795455d4995b9ceeb1c19aa98d46b98d710f0790ed1804029899ef9e1b6c85f77696e25e957

    File: PhoenixMiner_5.5b_Linux.tar.gz
    ====================================
   SHA-1: d64c126fb31d53ab367288bd69021ffe9d26e974
 SHA-256: a870d7c2427e005a502f728ea3d9711a36b126e0a1f91bcfbe5dfb23c5700ed1
 SHA-512: b86269cf3985dfbd45779226ff4b15f01ee36dd332af3f4a42396dfa9cdcc0e012172c622f55f16b9a49c5d8e5aff0d757b95ae7d8fc58fd322e6c2b758d007d

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

The new features in this release are:

• Added native kernels for AMD RX6800 and RX6900 GPUs. These are faster than the generic kernels and produce a lot less stale shares
• Updated kernels for AMD Polaris, Vega and Navi GPUs that are slightly faster and use less power than before when mining ETH. To use these updated kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux
• The Nvidia mining cards (P106, P104, etc.) can now use straps and hardware control options (power limit, memory overclock, max temperature, etc.) under Windows
• Added support for AMD Linux drivers 20.45-1164792 and 20.45-1188099. Use this drivers only if you have RX6800 or RX6900 GPU. WARNING: Vega and Navi GPUs wont' work with these drivers!
• Automatically set -ttli instead of -tmax when the later is not supported by the driver. This will throttle down the GPUs when they reach the specified temperature to avoid overheating

If you have RX6800 or RX6900 card, do not use the PhoenixMiner hardware control options (-cclock, -mclock, etc.) because there is yet another undocumented change in OverDrive and some of them will work, but some won't with weird results - we will implement them properly in the next version. Instead use the AMD control panel to set the card parameters. Good starting point are the following options: core clock 1500 MHz, mem clock 2050 MHz, core voltage 800 mV, set faster memory timings, and a custom fan curve to  keep the temperature below 65-66 C.

Please let us know if you have any problems or questions related to PhoenixMiner 5.5b.

[Guigs321]

• Updated kernels for AMD Polaris, Vega and Navi GPUs that are slightly faster and use less power than before when mining ETH. To use these updated kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux

Do we need to reset -GT settings ?

[theerachate.p]

The new beta version is ready. You can download PhoenixMiner 5.5b from here:

https://mega.nz/folder/jUdTiQhS#vVz_39HlXUK--Leql280iQ  (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.5b_Windows.zip
    ===================================
   SHA-1: 52ac75b2c8d5432aeb88900f034045d2bf023395
 SHA-256: 10e022d95514a682d749a593042f02b6f6a8adea112c470c68a3ae7b7b1cb187
 SHA-512: 84dbc3df53c38cd0d1956f92c4eb0226341e3230102d0214661bd795455d4995b9ceeb1c19aa98d46b98d710f0790ed1804029899ef9e1b6c85f77696e25e957

    File: PhoenixMiner_5.5b_Linux.tar.gz
    ====================================
   SHA-1: d64c126fb31d53ab367288bd69021ffe9d26e974
 SHA-256: a870d7c2427e005a502f728ea3d9711a36b126e0a1f91bcfbe5dfb23c5700ed1
 SHA-512: b86269cf3985dfbd45779226ff4b15f01ee36dd332af3f4a42396dfa9cdcc0e012172c622f55f16b9a49c5d8e5aff0d757b95ae7d8fc58fd322e6c2b758d007d

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

The new features in this release are:

• Added native kernels for AMD RX6800 and RX6900 GPUs. These are faster than the generic kernels and produce a lot less stale shares
• Updated kernels for AMD Polaris, Vega and Navi GPUs that are slightly faster and use less power than before when mining ETH. To use these updated kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux
• The Nvidia mining cards (P106, P104, etc.) can now use straps and hardware control options (power limit, memory overclock, max temperature, etc.) under Windows
• Added support for AMD Linux drivers 20.45-1164792 and 20.45-1188099. Use this drivers only if you have RX6800 or RX6900 GPU. WARNING: Vega and Navi GPUs wont' work with these drivers!
• Automatically set -ttli instead of -tmax when the later is not supported by the driver. This will throttle down the GPUs when they reach the specified temperature to avoid overheating

If you have RX6800 or RX6900 card, do not use the PhoenixMiner hardware control options (-cclock, -mclock, etc.) because there is yet another undocumented change in OverDrive and some of them will work, but some won't with weird results - we will implement them properly in the next version. Instead use the AMD control panel to set the card parameters. Good starting point are the following options: core clock 1500 MHz, mem clock 2050 MHz, core voltage 800 mV, set faster memory timings, and a custom fan curve to  keep the temperature below 65-66 C.

Please let us know if you have any problems or questions related to PhoenixMiner 5.5b.

What about RTX 3000 series get insane amount of invalid shares after every epoch change, and you have to reset everything to stock everything until epoch is fully loaded on every card then you can re-overclock again?

[ser_merged]

The new beta version is ready. You can download PhoenixMiner 5.5b

Hello, do you have plans to fix ethash performance under win7 for Nvidia 10 series GPUs?

[sirmathew]

Hi, new user and player here and this is my first post

First of all thank you for all your work guys so far.

Have tried the 5.5.b driver for 20-30 mins on my modded 5700xt , so far i see no difference on hash rate power consumption ( still 54-55 MH/s with 108-113w ).

Shall test it later and if i see difference i will post again.

edit: Windows 10 with latest stable amd drivers 20.11.1

[UnclWish]

• Updated kernels for AMD Polaris, Vega and Navi GPUs that are slightly faster and use less power than before when mining ETH. To use these updated kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux

Do we need to reset -GT settings ?

Yes. For my Polaris cards best -gt changed.

[br2459]

The new beta version is ready. You can download PhoenixMiner 5.5b

Hello, do you have plans to fix ethash performance under win7 for Nvidia 10 series GPUs?

What issue are you referring to? If you are talking about the slow down over the years, there is nothing miner software can do to fix that. It's an problem with hardware/firmware design and NVIDIA won't fix it.

[earlybird36]

Radeon 7 hashrate decreased and fluctuating since epoch 384. From 89mhs down to 82mhs. It was fine before epoch 384. My 5700 on the same rig is not affected. Tried other versions of the miner but still the same problem. Anybody have the same issue. Im on driver 20.8.1. GT on autotune

[batsonxl]

@Mr.Phoenix thanks for update. what about add strap option for polaris cards?

[batsonxl]

Something is not right with 5.5b, after running like 20-30minutes miner turns off. same setting used in 5.4c. it was working many days without any issue.

[Kiawpqe]

The new beta version is ready. You can download PhoenixMiner 5.5b from here:

https://mega.nz/folder/jUdTiQhS#vVz_39HlXUK--Leql280iQ  (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.5b_Windows.zip
    ===================================
   SHA-1: 52ac75b2c8d5432aeb88900f034045d2bf023395
 SHA-256: 10e022d95514a682d749a593042f02b6f6a8adea112c470c68a3ae7b7b1cb187
 SHA-512: 84dbc3df53c38cd0d1956f92c4eb0226341e3230102d0214661bd795455d4995b9ceeb1c19aa98d46b98d710f0790ed1804029899ef9e1b6c85f77696e25e957

    File: PhoenixMiner_5.5b_Linux.tar.gz
    ====================================
   SHA-1: d64c126fb31d53ab367288bd69021ffe9d26e974
 SHA-256: a870d7c2427e005a502f728ea3d9711a36b126e0a1f91bcfbe5dfb23c5700ed1
 SHA-512: b86269cf3985dfbd45779226ff4b15f01ee36dd332af3f4a42396dfa9cdcc0e012172c622f55f16b9a49c5d8e5aff0d757b95ae7d8fc58fd322e6c2b758d007d

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

The new features in this release are:

• Added native kernels for AMD RX6800 and RX6900 GPUs. These are faster than the generic kernels and produce a lot less stale shares
• Updated kernels for AMD Polaris, Vega and Navi GPUs that are slightly faster and use less power than before when mining ETH. To use these updated kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux
• The Nvidia mining cards (P106, P104, etc.) can now use straps and hardware control options (power limit, memory overclock, max temperature, etc.) under Windows
• Added support for AMD Linux drivers 20.45-1164792 and 20.45-1188099. Use this drivers only if you have RX6800 or RX6900 GPU. WARNING: Vega and Navi GPUs wont' work with these drivers!
• Automatically set -ttli instead of -tmax when the later is not supported by the driver. This will throttle down the GPUs when they reach the specified temperature to avoid overheating

If you have RX6800 or RX6900 card, do not use the PhoenixMiner hardware control options (-cclock, -mclock, etc.) because there is yet another undocumented change in OverDrive and some of them will work, but some won't with weird results - we will implement them properly in the next version. Instead use the AMD control panel to set the card parameters. Good starting point are the following options: core clock 1500 MHz, mem clock 2050 MHz, core voltage 800 mV, set faster memory timings, and a custom fan curve to  keep the temperature below 65-66 C.

Please let us know if you have any problems or questions related to PhoenixMiner 5.5b.

GOOOOD WORK




WITH 5.4c

x7 RX-580 8Gb

Speed = 227.5 MH/s
GPUs Power = 628/630 Watts




WITH 5.5b

x7 RX-580 8Gb

Speed = 227.5 MH/s
GPUs Power = 600/602 Watts


 PhoenixMiner team.

veeeery thanks

[aname23]

The new beta version is ready. You can download PhoenixMiner 5.5b from here:

https://mega.nz/folder/jUdTiQhS#vVz_39HlXUK--Leql280iQ  (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.5b_Windows.zip
    ===================================
   SHA-1: 52ac75b2c8d5432aeb88900f034045d2bf023395
 SHA-256: 10e022d95514a682d749a593042f02b6f6a8adea112c470c68a3ae7b7b1cb187
 SHA-512: 84dbc3df53c38cd0d1956f92c4eb0226341e3230102d0214661bd795455d4995b9ceeb1c19aa98d46b98d710f0790ed1804029899ef9e1b6c85f77696e25e957

    File: PhoenixMiner_5.5b_Linux.tar.gz
    ====================================
   SHA-1: d64c126fb31d53ab367288bd69021ffe9d26e974
 SHA-256: a870d7c2427e005a502f728ea3d9711a36b126e0a1f91bcfbe5dfb23c5700ed1
 SHA-512: b86269cf3985dfbd45779226ff4b15f01ee36dd332af3f4a42396dfa9cdcc0e012172c622f55f16b9a49c5d8e5aff0d757b95ae7d8fc58fd322e6c2b758d007d

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

The new features in this release are:

• Added native kernels for AMD RX6800 and RX6900 GPUs. These are faster than the generic kernels and produce a lot less stale shares
• Updated kernels for AMD Polaris, Vega and Navi GPUs that are slightly faster and use less power than before when mining ETH. To use these updated kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux
• The Nvidia mining cards (P106, P104, etc.) can now use straps and hardware control options (power limit, memory overclock, max temperature, etc.) under Windows
• Added support for AMD Linux drivers 20.45-1164792 and 20.45-1188099. Use this drivers only if you have RX6800 or RX6900 GPU. WARNING: Vega and Navi GPUs wont' work with these drivers!
• Automatically set -ttli instead of -tmax when the later is not supported by the driver. This will throttle down the GPUs when they reach the specified temperature to avoid overheating

If you have RX6800 or RX6900 card, do not use the PhoenixMiner hardware control options (-cclock, -mclock, etc.) because there is yet another undocumented change in OverDrive and some of them will work, but some won't with weird results - we will implement them properly in the next version. Instead use the AMD control panel to set the card parameters. Good starting point are the following options: core clock 1500 MHz, mem clock 2050 MHz, core voltage 800 mV, set faster memory timings, and a custom fan curve to  keep the temperature below 65-66 C.

Please let us know if you have any problems or questions related to PhoenixMiner 5.5b.

5.5b seems to run pretty well on 6800 XT. So far seems to have fixed a stale share issue I was getting before that.

Any idea why it reports 6800 XT as 36 CUs? As far as I understand 6800 XT has 72 CUs?
Is there a known reason for this?

See: https://i.imgur.com/AQDUr5E.png

Thanks

[Arn0]

Still no DAG fix for 3000 series