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

[PhoenixMiner]

  We tested on a similar rig (RX570 + RX5700, Windows 10 1709, AMD driver 19.9.1) and we didn't encounter any problems. Does PhoenixMiner 4.5c work on the same rig? What is the version of the drivers? Also, please try to run PhoenixMiner 4.6b only with -list (i.e. Phoenixminer.exe -list) and see if it shows the list of GPUs properly. A possible but unlikely reason - Windows defender may be blocking or even deleting PhoenixMiner.exe.

...
Edit3: Turns out Windows Defender was blocking the miner... Haven't seen it block something like that before....

  Thank you for finding the cause of the problem on your rig. We were scratching our heads because even with latest Windows updates we couldn't reproduce the problem. Frankly, the behviour of Windows Defender is becoming really idiotic. We are already disabled it permanently on all our test rigs (and even on developer PCs) from the start but we will stop short from recommending this for everyone. Just keep in mind that whenever you see strange behavior or unexplained errors, just try with disabled Windows Defender to be sure that it is not causing problems.

[sergioheadache]

hi,

some of my cards are rx570 with moded bios so they need the pixel patcher
after update to amd driver 19.9.1 - the patcher doesnt work, just gives the error "File too large"

any solution for this? or do i have to go back to older driver ?

[Bathmat]

  We tested on a similar rig (RX570 + RX5700, Windows 10 1709, AMD driver 19.9.1) and we didn't encounter any problems. Does PhoenixMiner 4.5c work on the same rig? What is the version of the drivers? Also, please try to run PhoenixMiner 4.6b only with -list (i.e. Phoenixminer.exe -list) and see if it shows the list of GPUs properly. A possible but unlikely reason - Windows defender may be blocking or even deleting PhoenixMiner.exe.

...
Edit3: Turns out Windows Defender was blocking the miner... Haven't seen it block something like that before....

 Thank you for finding the cause of the problem on your rig. We were scratching our heads because even with latest Windows updates we couldn't reproduce the problem. Frankly, the behviour of Windows Defender is becoming really idiotic. We are already disabled it permanently on all our test rigs (and even on developer PCs) from the start but we will stop short from recommending this for everyone. Just keep in mind that whenever you see strange behavior or unexplained errors, just try with disabled Windows Defender to be sure that it is not causing problems.

Yeah, I disabled Windows Defender completely and discovered it was blocking the actual process. In the past, as long as it didn't delete the miner when I downloaded it, and was able to move it to my folder with my exception it wasn't a problem. Now, I've added an exception for the miner process to Windows Defender and all is working fine.

[PhoenixMiner]

hi,

some of my cards are rx570 with moded bios so they need the pixel patcher
after update to amd driver 19.9.1 - the patcher doesnt work, just gives the error "File too large"

any solution for this? or do i have to go back to older driver ?

   The latest version of the patcher (atikmdag-patcher-1.4.7.zip) works fine with 19.9.1 drivers. It appears that the official thread for it is here: https://www.monitortests.com/forum/Thread-AMD-ATI-Pixel-Clock-Patcher (note that aren't affiliated with its creator in any way, so decide for yourself, we just use it with our modded cards and it works fine). Going back to the older drivers is also an option because RX570 doesn't benefit from the latest drivers.

[UnclWish]

AMD released 19.9.2 driver. Is anyone tried? Miner supports them or not?

[aknataga]

AMD released 19.9.2 driver. Is anyone tried? Miner supports them or not?

Have updated today to 19.9.2 version. Same hashrate.

[sergioheadache]

is there a direct connection between card power draw reported and real "off the wall" power draw ?

[Bathmat]

is there a direct connection between card power draw reported and real "off the wall" power draw ?

I estimate wall power as 35-40% higher than reported GPU power in software (such as HWInfo, GPU-z, ect.). That accounts for the extra system draw, and it's been pretty close in my experience. It's actually even high in some cases with multiple gpus, and 30% over reported can be accurate.

[laik2]

is there a direct connection between card power draw reported and real "off the wall" power draw ?

I estimate wall power as 35-40% higher than reported GPU power in software (such as HWInfo, GPU-z, ect.). That accounts for the extra system draw, and it's been pretty close in my experience. It's actually even high in some cases with multiple gpus, and 30% over reported can be accurate.

AMD reports GPU-Only powerdraw, means you have to add additional watts(PCIe power consumption). Some GPUs(won't get into details) also report less powerdraw than actual, its not a bug, its VRM specific.

[UnclWish]

AMD released 19.9.2 driver. Is anyone tried? Miner supports them or not?

Have updated today to 19.9.2 version. Same hashrate.

Confirm. 4.6c supports 19.9.2 AMD driver version.

[sergioheadache]

hi,

if i use at least one command line parameter, it completely ignores the config.txt

so i cant use both options together? i have to choose either config or command line ?

[NCarter84]

Got my 5700xt up and running last night.

Windows 1903, Driver 19.9.1 -- Running, -cclock 1300 -cvddc 800 -mclock 900 -hstats 2 - Getting roughly 52 mhs.

Seems like after some hours, (3-8 hours) threads stop responding and drops to 0 mhs.

[tale01]

Please support any ProgPOW such as SERO, ZANO, EPIC 

[bategojko74]

Got my 5700xt up and running last night.

Windows 1903, Driver 19.9.1 -- Running, -cclock 1300 -cvddc 800 -mclock 900 -hstats 2 - Getting roughly 52 mhs.

Seems like after some hours, (3-8 hours) threads stop responding and drops to 0 mhs.

Lower -cvddc to 750. If it continuous start lowering -tt

[NCarter84]

I own now 2x Sapphire 5700XT.

I have used Adrenaline 1.9.2.2 and classic setting posted on this topic; -tt 62  -cclock 1300 -cvddc 800 -mclock 900 -hstats 2 it gives 52,x MH but it fails in minutes.

I have tried lower or bigger -cvvdc between 750 and 900mV, even lower/higher -tt, it fails randomly showing 0.00MH.

I tried also to keep memory stock (875MHz), it fails randomly, same problem and miner stays locked, mouse too, just hard reset works.

When I have removed -hstats 2 command, keeping just  -tt 62  -cclock 1300 -cvddc 800 -mclock 900, it worked fine 12 hours but I just tried last sollution: I have deleted all commands -tt 62  -cclock 1300 -cvddc 800 -mclock 900 -hstats 2 from ,bat file and I have used just Msi Afterburner 4.6.2 beta 2           https://www.guru3d.com/files-details/msi-afterburner-beta-download.html        wich full controls power limit, voltage and frequency, now I left voltage unattended (1187mV), GPU frequency stock, memory increased at 900MHz and power limit down to -43 or even -44%.

Works flawless.

It looks as the much commands gived to the miner (tt 62  -cclock 1300 -cvddc 800 -mclock 900 -hstats 2), especially -hstats 2,  gives driver error (atimtag.dll) and locks the miner...

So, I keept settings as in picture attached and .bat file as simple, without extra commands ex:  PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal your wallet adress.rig name, and is rock solid.

https://i.postimg.cc/RhtKXjtg/Best-settings.jpg

Been having the same exact problem.... Most of the time, my mining watchdog wouldn't catch the reboot of the miner since it does it fairly quickly. But, I noticed a ton of log build up... After opening several, I saw the same thing (I already knew it was going to 0 mhs and locking up the rig, but I didn't know it was doing it 20 times a day)

I went ahead and trying out the AB way...

[NCarter84]

Try it, it works good, with those settings:

https://postimg.cc/2Lz1592W

https://i.postimg.cc/RhtKXjtg/Best-settings.jpg

It went watch dog and rebooted an hour in.

[PhoenixMiner]

hi,

if i use at least one command line parameter, it completely ignores the config.txt

so i cant use both options together? i have to choose either config or command line ?

   Currently there can be only one config.txt file (or command-line options). We will probably add ability to use both config.txt file and command-line options in the next release, as it can be useful in some cases.

I own now 2x Sapphire 5700XT.

I have used Adrenaline 1.9.2.2 and classic setting posted on this topic; -tt 62  -cclock 1300 -cvddc 800 -mclock 900 -hstats 2 it gives 52,x MH but it fails in minutes.

I have tried lower or bigger -cvvdc between 750 and 900mV, even lower/higher -tt, it fails randomly showing 0.00MH.

I tried also to keep memory stock (875MHz), it fails randomly, same problem and miner stays locked, mouse too, just hard reset works.

When I have removed -hstats 2 command, keeping just  -tt 62  -cclock 1300 -cvddc 800 -mclock 900, it worked fine 12 hours but I just tried last sollution: I have deleted all commands -tt 62  -cclock 1300 -cvddc 800 -mclock 900 -hstats 2 from ,bat file and I have used just Msi Afterburner 4.6.2 beta 2           https://www.guru3d.com/files-details/msi-afterburner-beta-download.html        wich full controls power limit, voltage and frequency, now I left voltage unattended (1187mV), GPU frequency stock, memory increased at 900MHz and power limit down to -43 or even -44%.

Works flawless.

It looks as the much commands gived to the miner (tt 62  -cclock 1300 -cvddc 800 -mclock 900 -hstats 2), especially -hstats 2,  gives driver error (atimtag.dll) and locks the miner...

So, I keept settings as in picture attached and .bat file as simple, without extra commands ex:  PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal your wallet adress.rig name, and is rock solid.

https://i.postimg.cc/RhtKXjtg/Best-settings.jpg

  It is important to avoid using both the PhoenixMiner hardware control options and third party programs (e.g. Afterburner) at the same time. While we use the AMD provided API to do most of the hardware control and monitoring, most of these programs use lower-level undocumented access and doing both at the same time can lead to driver lock ups. Note that Afterburner must be completely closed, not only minimized to tray in order to stop interacting with the GPUs. Or, alternatively, you should use only Afterburner (or other third party program) and none of PhoenixMiner hardware control options.

[NCarter84]

I own now 2x Sapphire 5700XT.

I have used Adrenaline 1.9.2.2 and classic setting posted on this topic; -tt 62  -cclock 1300 -cvddc 800 -mclock 900 -hstats 2 it gives 52,x MH but it fails in minutes.

I have tried lower or bigger -cvvdc between 750 and 900mV, even lower/higher -tt, it fails randomly showing 0.00MH.

I tried also to keep memory stock (875MHz), it fails randomly, same problem and miner stays locked, mouse too, just hard reset works.

When I have removed -hstats 2 command, keeping just  -tt 62  -cclock 1300 -cvddc 800 -mclock 900, it worked fine 12 hours but I just tried last sollution: I have deleted all commands -tt 62  -cclock 1300 -cvddc 800 -mclock 900 -hstats 2 from ,bat file and I have used just Msi Afterburner 4.6.2 beta 2           https://www.guru3d.com/files-details/msi-afterburner-beta-download.html        wich full controls power limit, voltage and frequency, now I left voltage unattended (1187mV), GPU frequency stock, memory increased at 900MHz and power limit down to -43 or even -44%.

Works flawless.

It looks as the much commands gived to the miner (tt 62  -cclock 1300 -cvddc 800 -mclock 900 -hstats 2), especially -hstats 2,  gives driver error (atimtag.dll) and locks the miner...

So, I keept settings as in picture attached and .bat file as simple, without extra commands ex:  PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal your wallet adress.rig name, and is rock solid.

https://i.postimg.cc/RhtKXjtg/Best-settings.jpg

  It is important to avoid using both the PhoenixMiner hardware control options and third party programs (e.g. Afterburner) at the same time. While we use the AMD provided API to do most of the hardware control and monitoring, most of these programs use lower-level undocumented access and doing both at the same time can lead to driver lock ups. Note that Afterburner must be completely closed, not only minimized to tray in order to stop interacting with the GPUs. Or, alternatively, you should use only Afterburner (or other third party program) and none of PhoenixMiner hardware control options.

I tried both ways, and still would get hashrate drops to 0 mhs and a miner restart... After sometime, it would just lock the rig up. I was mining Ubiq, so there might be some issues there.... However, I did switch to Nicehash/Claymore for a test and haven't had any miner restarts/rig locks in 18 hours... I'm going to come back to PM after 24 hours and connect to NH and see how it performs.

[motomart]

I own now 2x Sapphire 5700XT.

I have used Adrenaline 1.9.2.2 and classic setting posted on this topic; -tt 62  -cclock 1300 -cvddc 800 -mclock 900 -hstats 2 it gives 52,x MH but it fails in minutes.

I have tried lower or bigger -cvvdc between 750 and 900mV, even lower/higher -tt, it fails randomly showing 0.00MH.

I tried also to keep memory stock (875MHz), it fails randomly, same problem and miner stays locked, mouse too, just hard reset works.

When I have removed -hstats 2 command, keeping just  -tt 62  -cclock 1300 -cvddc 800 -mclock 900, it worked fine 12 hours but I just tried last sollution: I have deleted all commands -tt 62  -cclock 1300 -cvddc 800 -mclock 900 -hstats 2 from ,bat file and I have used just Msi Afterburner 4.6.2 beta 2           https://www.guru3d.com/files-details/msi-afterburner-beta-download.html        wich full controls power limit, voltage and frequency, now I left voltage unattended (1187mV), GPU frequency stock, memory increased at 900MHz and power limit down to -43 or even -44%.

Works flawless.

It looks as the much commands gived to the miner (tt 62  -cclock 1300 -cvddc 800 -mclock 900 -hstats 2), especially -hstats 2,  gives driver error (atimtag.dll) and locks the miner...

So, I keept settings as in picture attached and .bat file as simple, without extra commands ex:  PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal your wallet adress.rig name, and is rock solid.

https://i.postimg.cc/RhtKXjtg/Best-settings.jpg

  It is important to avoid using both the PhoenixMiner hardware control options and third party programs (e.g. Afterburner) at the same time. While we use the AMD provided API to do most of the hardware control and monitoring, most of these programs use lower-level undocumented access and doing both at the same time can lead to driver lock ups. Note that Afterburner must be completely closed, not only minimized to tray in order to stop interacting with the GPUs. Or, alternatively, you should use only Afterburner (or other third party program) and none of PhoenixMiner hardware control options.

I tried both ways, and still would get hashrate drops to 0 mhs and a miner restart... After sometime, it would just lock the rig up. I was mining Ubiq, so there might be some issues there.... However, I did switch to Nicehash/Claymore for a test and haven't had any miner restarts/rig locks in 18 hours... I'm going to come back to PM after 24 hours and connect to NH and see how it performs.

Same here. I tried every possible combination of -tt -cvddc and -mclock for RX5700 but one card would go down to 0 Mhs followed by the second card after some time. Claymore is a bit slower but it's stable with  -cvddc 800 -cclock 1300 -mclock +910 -powlim -25,-25 -tt 58,58 settings (hashing at 50.2 - 50.5 Mhs).
I'm not using 3rd party hardware control but I also have 2 vii's and 2 1060's in the same rig which are working well with phoenix.

[motomart]

Wow... Someone posted on Claymore thread that following config is getting 60 MHs with Phoenix 4.6c, I have it running for 10 min and it's true. I'm getting 59.7 at 104-110 Watt. I only hope it stays stable without lockup.

-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -acm -mi 12 -gt 126 -mode 1 -clKernel 1 -clNew 1 -clf 0 -lidag 1 -openclLocalWork 128 -openclGlobalMultiplier 4096