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

[arierep60]

https://imgur.com/OvEOwDU

hello;
Could you explain anyone what is this error on hiveOS ?

There is no any error messages on miner screen or hiveos notification. But i saw this errors when i connect the monitor to the rig.

https://i.imgur.com/OvEOwDU.jpg

broken riser or gpu, disconect all gpus and plug 1 by 1 to see which one is the broken one

[shimmishim]

I'm getting a strange occurrence. It took me a while to troubleshoot and I just can't seem to figure out what's wrong. After a random amount of time (anywhere between 5 minutes to almost 2 hours), the miner will "pause" and indicates to press any key to continue at which point it just shuts off. There's no error message. It just says "pause Press any key to continue..." Does anyone know what might cause this? Thanks!

[commandera]

I wish my simple report help
running Time :176 hour, 1 week ,,, 34k share

no issues , PhoenixMiner 5.0b

[Branko]

Crazy stuff, my single RX580 get recognized as two RX580 GPUs. and mining at 12MH/s each,
while fan stays at 0 rpm, until it crashes due to overheating

Does anyone have latest AMD driver and latest 2004 windows 10 version, and its working well?

[PhoenixMiner]

The new beta version is ready. You can download PhoenixMiner 5.1b 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.1b_Windows.zip
    ===================================
   SHA-1: b71a5b22bb9a6fbd26d4a85272f73defabad2b70
 SHA-256: 1592d04efa4ef427b6e42388d012ac6a68154f09848aaaa4f0418e3425e07155
 SHA-512: c543b8bc5d0c345e81fb2586b2807b842fc2b666bd033ceb78820d1732a61ef8529a228f9df8777029dfc9f7a8e90853fa65600c4d3b976787e1630f0ea03dfd

    File: PhoenixMiner_5.1b_Linux.tar.gz
    ====================================
   SHA-1: 9ba244a12698ca30015ef273c9f3cd9a9443c04f
 SHA-256: ade4a07bd0c738fb875b2a42b5153271fedd23c60ba4527655360a8f718be4de
 SHA-512: 860491408731c63bf42bb8288711de2f29534b4bac14313e376869d221a62a985ce4ea1a5a22cb39d875eb876016aa741275702665cc3ee1116c5cc3637ec21c

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

The new features in this release are:

• Added support for VRAM timing adjustments for Nvidia cards of 10x0 series (see the new command-line parameters -straps, -vmt1, -vmt2, -vmt3, and -vmr for more information)
• Added -ttli option to automatically decrease the mining speed to avoid overheating the GPUs over the target temperature (useful when -tmax option is not supported by the drivers)
• Added support for latest AMD drivers 20.7.1 under Windows and 20.20-1089974 under Linux
• Fixed long-standing problems with -gpow option, which now works properly
• Many other small improvements and fixes

Here are some additional notes about the VRAM timing adjustments of Nvidia 10x0 cards:

• Most recent Nvidia drivers require running as administrator (or as root under Linux) to allow hardware control, so you need to run PhoenixMiner as administrator for the VRAM timing options to work.
• The four independently adjustable VRAM timings are controlled by four different parameters: -vmt1, -vmt2, -vmt3, and -vmr. The last one controls the memory refresh rate, and the first three are other timings. The possible values for each of them are from 0 to 100, where 0 are the default timings, and 100 is the most aggressive timing (most GPUs probably wont work with 100).
• The -straps option gives an easy way to set one of the predefined levels of VRAM timing adjustment. The possible values are 0 to 6. 0 is the default value and uses the default timings from the VBIOS. Each strap level corresponds to a predefined set of memory timings ("-vmt1", "-vmt2", "-vmt3", "-vmr"). Strap level 3 is the fastest predefined level and may not work on most cards, 1 is the slowest (but still faster than the default timings). Strap levels 4 to 6 are the same as 1 to 3 but with less aggressive refresh rates (i.e. lower "-vmr" values).
• When using the VRAM timing options, start with lower values and make sure that the cards are stable before trying higher and more aggressive settings. You can use -straps along with the other options. For example -straps 1 -vmt1 60 will use the timings from 1st strap level but -vmt1 will be set to 60 instead of whatever value is specified by the 1st strap level. In such case the -straps option must be specified first.
• 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.1b.

[PhoenixMiner]

Crazy stuff, my single RX580 get recognized as two RX580 GPUs. and mining at 12MH/s each,
while fan stays at 0 rpm, until it crashes due to overheating

Does anyone have latest AMD driver and latest 2004 windows 10 version, and its working well?

  Probably a driver issue with two OpenCL drivers each reporting the same GPU. We had somewhat similar issue with DDU not removing the drivers completely -  to be sure, please check if all Radeon GPUs are missing from the Device Manager after DDU finishes and restarts the PC (and before installing the new drivers) - you should see only the iGPU and generic "Microsoft Display Adapter" GPUs there. If there is a Radeon GPU still recognized, DDU must be started again to finish the job before installing the new drivers.

   On a related note, you will need PhoenixMiner 5.1b for the latest AMD drivers 20.7.1 to work properly.

I'm getting a strange occurrence. It took me a while to troubleshoot and I just can't seem to figure out what's wrong. After a random amount of time (anywhere between 5 minutes to almost 2 hours), the miner will "pause" and indicates to press any key to continue at which point it just shuts off. There's no error message. It just says "pause Press any key to continue..." Does anyone know what might cause this? Thanks!

   Check if something emulates pressing 'p' in the console window (it may be some process that "feeds" text data to the standard input of PhoenixMiner and if 'p' occurs there, the miner will be paused).

[UnclWish]

Added support for latest AMD drivers 20.4.2 under Windows...

Here must be 20.7.1 I think.
Thanks for update!

[PhoenixMiner]

Added support for latest AMD drivers 20.4.2 under Windows...

Here must be 20.7.1 I think.
Thanks for update!

   Thank you, we fixed it.

[Twod]

Phoenix Miner 5.1b.
GTX 1070: unable to set straps:  error 31
Drivers Version: 442.19

[cikusa]

P106-100 are not supported either.

[PhoenixMiner]

Phoenix Miner 5.1b.
GTX 1070: unable to set straps:  error 31
Drivers Version: 442.19

P106-100 are not supported either.

  Most recent Nvidia drivers require running as administrator (or as root under Linux) to allow hardware control, so you need to run PhoenixMiner as administrator for the VRAM timing options to work.

[haliy-2017]

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

https://mega.nz/folder/XYkTQZiI#HT_dcKdLtsU26nwbE8pMBQ  (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.1b_Windows.zip
    ===================================
   SHA-1: b71a5b22bb9a6fbd26d4a85272f73defabad2b70
 SHA-256: 1592d04efa4ef427b6e42388d012ac6a68154f09848aaaa4f0418e3425e07155
 SHA-512: c543b8bc5d0c345e81fb2586b2807b842fc2b666bd033ceb78820d1732a61ef8529a228f9df8777029dfc9f7a8e90853fa65600c4d3b976787e1630f0ea03dfd

    File: PhoenixMiner_5.1b_Linux.tar.gz
    ====================================
   SHA-1: 9ba244a12698ca30015ef273c9f3cd9a9443c04f
 SHA-256: ade4a07bd0c738fb875b2a42b5153271fedd23c60ba4527655360a8f718be4de
 SHA-512: 860491408731c63bf42bb8288711de2f29534b4bac14313e376869d221a62a985ce4ea1a5a22cb39d875eb876016aa741275702665cc3ee1116c5cc3637ec21c

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

The new features in this release are:

• Added support for VRAM timing adjustments for Nvidia cards of 10x0 series (see the new command-line parameters -straps, -vmt1, -vmt2, -vmt3, and -vmr for more information)
• Added -ttli option to automatically decrease the mining speed to avoid overheating the GPUs over the target temperature (useful when -tmax option is not supported by the drivers)
• Added support for latest AMD drivers 20.7.1 under Windows and 20.20-1089974 under Linux
• Fixed long-standing problems with -gpow option, which now works properly
• Many other small improvements and fixes

Here are some additional notes about the VRAM timing adjustments of Nvidia 10x0 cards:

• Most recent Nvidia drivers require running as administrator (or as root under Linux) to allow hardware control, so you need to run PhoenixMiner as administrator for the VRAM timing options to work.
• The four independently adjustable VRAM timings are controlled by four different parameters: -vmt1, -vmt2, -vmt3, and -vmr. The last one controls the memory refresh rate, and the first three are other timings. The possible values for each of them are from 0 to 100, where 0 are the default timings, and 100 is the most aggressive timing (most GPUs probably wont work with 100).
• The -straps option gives an easy way to set one of the predefined levels of VRAM timing adjustment. The possible values are 0 to 6. 0 is the default value and uses the default timings from the VBIOS. Each strap level corresponds to a predefined set of memory timings ("-vmt1", "-vmt2", "-vmt3", "-vmr"). Strap level 3 is the fastest predefined level and may not work on most cards, 1 is the slowest (but still faster than the default timings). Strap levels 4 to 6 are the same as 1 to 3 but with less aggressive refresh rates (i.e. lower "-vmr" values).
• When using the VRAM timing options, start with lower values and make sure that the cards are stable before trying higher and more aggressive settings. You can use -straps along with the other options. For example -straps 1 -vmt1 60 will use the timings from 1st strap level but -vmt1 will be set to 60 instead of whatever value is specified by the 1st strap level. In such case the -straps option must be specified first.
• 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.1b.

I can’t achieve an increase in speed. Maybe an example of a body shirt for 6shi 1060 6g?

[cikusa]

P106-100 is showing as not supported gpu.

[Demented247]

@PhoenixMiner

Any chance you might be supporting KawPow algo??

[Arielle99]

My 1060TI increased from 20MH/s to 24MH/s, but also from 73W to 81W. Just used -straps 1. Maybe I will test higher levels tomorrow.

[zhihao4456]

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

https://mega.nz/folder/XYkTQZiI#HT_dcKdLtsU26nwbE8pMBQ  (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.1b_Windows.zip
    ===================================
   SHA-1: b71a5b22bb9a6fbd26d4a85272f73defabad2b70
 SHA-256: 1592d04efa4ef427b6e42388d012ac6a68154f09848aaaa4f0418e3425e07155
 SHA-512: c543b8bc5d0c345e81fb2586b2807b842fc2b666bd033ceb78820d1732a61ef8529a228f9df8777029dfc9f7a8e90853fa65600c4d3b976787e1630f0ea03dfd

    File: PhoenixMiner_5.1b_Linux.tar.gz
    ====================================
   SHA-1: 9ba244a12698ca30015ef273c9f3cd9a9443c04f
 SHA-256: ade4a07bd0c738fb875b2a42b5153271fedd23c60ba4527655360a8f718be4de
 SHA-512: 860491408731c63bf42bb8288711de2f29534b4bac14313e376869d221a62a985ce4ea1a5a22cb39d875eb876016aa741275702665cc3ee1116c5cc3637ec21c

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

The new features in this release are:

• Added support for VRAM timing adjustments for Nvidia cards of 10x0 series (see the new command-line parameters -straps, -vmt1, -vmt2, -vmt3, and -vmr for more information)
• Added -ttli option to automatically decrease the mining speed to avoid overheating the GPUs over the target temperature (useful when -tmax option is not supported by the drivers)
• Added support for latest AMD drivers 20.7.1 under Windows and 20.20-1089974 under Linux
• Fixed long-standing problems with -gpow option, which now works properly
• Many other small improvements and fixes

Here are some additional notes about the VRAM timing adjustments of Nvidia 10x0 cards:

• Most recent Nvidia drivers require running as administrator (or as root under Linux) to allow hardware control, so you need to run PhoenixMiner as administrator for the VRAM timing options to work.
• The four independently adjustable VRAM timings are controlled by four different parameters: -vmt1, -vmt2, -vmt3, and -vmr. The last one controls the memory refresh rate, and the first three are other timings. The possible values for each of them are from 0 to 100, where 0 are the default timings, and 100 is the most aggressive timing (most GPUs probably wont work with 100).
• The -straps option gives an easy way to set one of the predefined levels of VRAM timing adjustment. The possible values are 0 to 6. 0 is the default value and uses the default timings from the VBIOS. Each strap level corresponds to a predefined set of memory timings ("-vmt1", "-vmt2", "-vmt3", "-vmr"). Strap level 3 is the fastest predefined level and may not work on most cards, 1 is the slowest (but still faster than the default timings). Strap levels 4 to 6 are the same as 1 to 3 but with less aggressive refresh rates (i.e. lower "-vmr" values).
• When using the VRAM timing options, start with lower values and make sure that the cards are stable before trying higher and more aggressive settings. You can use -straps along with the other options. For example -straps 1 -vmt1 60 will use the timings from 1st strap level but -vmt1 will be set to 60 instead of whatever value is specified by the 1st strap level. In such case the -straps option must be specified first.
• 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.1b.

Tested with my GTX 1070 Ti, by using -straps 1, with +0 core and + 300 memory and 70% power limit, I was able to get 31.4MH/s...
I tried to played around with the VRAM timings, the best I could get was 31.9MH/s with -straps 1 -vmt1 25 -vmt2 100 -vmt3 100 -vmr 100
I can't even increase the -vmt1 at all, even when using default -straps 1 -vmt1 25 -vmt2 20 -vmt3 0 -vmr 33.
Each time I increase -vmt1 even just by 1 number, it crashes.....

Currently I'm using 441.87 Nvidia driver and CUDA - Force P2 State Off...
Couldn't get 33MH/s like what other miners can...

[Branko]

Crazy stuff, my single RX580 get recognized as two RX580 GPUs. and mining at 12MH/s each,
while fan stays at 0 rpm, until it crashes due to overheating

Does anyone have latest AMD driver and latest 2004 windows 10 version, and its working well?

  Probably a driver issue with two OpenCL drivers each reporting the same GPU. We had somewhat similar issue with DDU not removing the drivers completely -  to be sure, please check if all Radeon GPUs are missing from the Device Manager after DDU finishes and restarts the PC (and before installing the new drivers) - you should see only the iGPU and generic "Microsoft Display Adapter" GPUs there. If there is a Radeon GPU still recognized, DDU must be started again to finish the job before installing the new drivers.

   On a related note, you will need PhoenixMiner 5.1b for the latest AMD drivers 20.7.1 to work properly.

I'm getting a strange occurrence. It took me a while to troubleshoot and I just can't seem to figure out what's wrong. After a random amount of time (anywhere between 5 minutes to almost 2 hours), the miner will "pause" and indicates to press any key to continue at which point it just shuts off. There's no error message. It just says "pause Press any key to continue..." Does anyone know what might cause this? Thanks!

   Check if something emulates pressing 'p' in the console window (it may be some process that "feeds" text data to the standard input of PhoenixMiner and if 'p' occurs there, the miner will be paused).

I suspect something like that to be the problem, however nothing helped, tried to deinstall drivers in lots of ways. Guess complete
windows reinstall is needed

[fomkas]

claymore 15 strap 1 - 147
PM strap 1 - 145

it's "reported"
i will look on pool after 1 day passes ...or two

6x1066 SJS
2x570 RDragon

[br2459]

claymore 15 strap 1 - 147
PM strap 1 - 145

it's "reported"
i will look on pool after 1 day passes ...or two

What GPU's are you using?

[Arielle99]

My 1060TI increased from 20MH/s to 24MH/s, but also from 73W to 81W. Just used -straps 1. Maybe I will test higher levels tomorrow.

Did some tests with -straps 2 and 3. Without changing other settings, no changes in Hashrate.

With rising the allowed GPU Temp and power usage, Hashrate climbed up 26,6MH/s. But Power also up to 100W.

So I set back the GPU temp and power usage, but rised GPU clock. I now ended at the previous 24MH/s with 78W.