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

[Digital_Seytan]

i think my one nvidia based rig is having a similar issue. it's running 2.8c.

it will run fine for 5-50+hrs, then suddenly it crashes, gets the "unspecified launch failure" error, and doesnt auto-restart. i can see that the watchdog triggered, but then the pheonixminer.exe crashes in windows and it hangs until i manually close it. i usually just reboot the system and it's fine. i run all default parameters except only running the -coin eth command, everything else is defaults.

my AMD based system on 2.8c is rock steady. runs for 300+ hrs and never crashes.

this is what's happening.



normally something like this would just trigger the watchdog, but it crashes in windows and just hangs. so it cant restart itself.

lower the OC on GPU 7, i had the same issue working stable now

seems to be just the miner 2.8c version. been stable since the switch back to 2.8b

the same problem here, over from 2.8.c to 2.9.d only the phoenixminer downloaded nothing changed and becoming Crashes what now?

[j2james]

Funny Etherminer for me using Fury x and vega 64 is about 15 % slower than PM 2.8b or 2.8c(haven`t tried PM 2.9b) yet...

Agreed. PhoenixMiner is the best! I have 6x1070 rig. Etherminer gives me 185-188MH, Claymore 10.6 - up to 190.2, but requires 2 restarts of rig per day to have stable hashrate (using windows scheduler), 11.0 - 11.5 do not provide stable hashrate (170 - 190), 11.6 did not test and do not want, but PhoenixMiner 2.8c gives me stable 191.6!!!

[xunl]

What is the best version for nVidia driver to run PhoenixMiner 2.8c or 2.9d?
I open multiple instances to run claymore on RX580 and Phoenix on GTX1070/1060 on the same rig, right?

[rboer]

Hi,

just downloaded 2.9b and copied over my startup.bat but for some reason i am getting ID "0" in the mining pool overview instead of the worker name specified in the command.

http://beta-pirl.pool.sexy/#/account/0x7D7764c9D0EC722e246E1b717A7e11Aad08ACe9f

my start.bat file

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 100


PhoenixMiner.exe -pool beta-pirl.pool.sexy:10052 -wal 0x7D7764c9D0EC722e246E1b717A7e11Aad08ACe9f -worker miner1 -coin pirl -nvidia -minRigSpeed 120 -log 0 -cdm 1 -cdmport 3333 -rmode 2 -mi 14

pause

Thank you for reporting this, the problem is fixed and an updated beta (2.8d) has now replaced 2.8b. You can find it at the same location (see this post: https://bitcointalk.org/index.php?topic=2647654.msg34449237#msg34449237).

Could performance on Baffin (RX 460/560) be improved?

I have a system with a Baffin card and got around 11 Mh/s while Claymore's gives 14 Mh/s.

   Try to change the -gt parameter (the default is 15), or try using the command line option -clkernel 2 (only works with the latest beta version few posts above).

thanks man -worker name is resolved for me! now thats what i call support !!!

[rboer]

What is the best version for nVidia driver to run PhoenixMiner 2.8c or 2.9d?
I open multiple instances to run claymore on RX580 and Phoenix on GTX1070/1060 on the same rig, right?

Use two instances of Phoenix (or maybe you can specify which kernel for which GPU?) 1 for your AMD and another for your NVIDIA?

[lesjokolat]

2.8c has all but removed all stales i get reported on screen.

vega 64 impact, no difference in terms of speed mh wise from 2.8b.(ratio of found shares does seem to be lower though when looking at all shares found across all gpus in rig)

fury x the reported hash rates are more level but spikes to higher hashrates are gone. I was getting an avg 35.2 mh on them with spikes to 40.(2.8b) now avg is 34.5 with no spikes. 2.8c

thanks for PM

Update and comparison
2.9d is actually a bit of a loss in hashrate. vega 64 virtually no change from 2.8c. fury x are lower than 2.8c 34.5 avg now

the best speed was 2.8b but stales now are virtually nil.

Regards

[xunl]

What is the best version for nVidia driver to run PhoenixMiner 2.8c or 2.9d?
I open multiple instances to run claymore on RX580 and Phoenix on GTX1070/1060 on the same rig, right?

Use two instances of Phoenix (or maybe you can specify which kernel for which GPU?) 1 for your AMD and another for your NVIDIA?

Thanks, but I want to run 1 instance of Phoenix for nvidia and 1 instance of claymore for AMD on the same rig.
I don't have AMD 18.3 driver installed on the rig. I only have the blockchain beta which is not suitable for Phoenix miner. Claymore has run very stable on it for months and I don't want to upgrade the drivers to introduce unkown factor and downtime.
The nVidia driver on the rig is very stable as well. But if my nVidia driver is good enough for phoenix, I can start a separated instnace of cmd to run all GTX1070/1060 on the rig. Some unknown factors but no downtime. That's why I want to know what's a good version of nVidia driver to run Phoenix. I use afterburn to control OC/Voltage for nVidia cards. Thanks in advance.

[xunl]

Also I would like to know if I start 8 instances of command windows to run Phoenix miner on 8 gpus of the same rig, is there any performance penalty on that?
This is what I did for claymore right now. each miner takes -di # (# is a single digit between 0 to 7 representing 1 gpu)
8 instances of claymores, each mine to a unique eth addr.
If one gpu crashes the miner but didn't cause system hang, the other 7 conitnue working w/o restart. the crashed gpu would just restart automatically 30 second ~ 20 minutes late depending on how bad the situation is. If I start all 8 in one instance, it would restart all 8 gpus as many times as it could until the single crash one became stable.

[BennyT]

Also I would like to know if I start 8 instances of command windows to run Phoenix miner on 8 gpus of the same rig, is there any performance penalty on that?
This is what I did for claymore right now. each miner takes -di # (# is a single digit between 0 to 7 representing 1 gpu)
8 instances of claymores, each mine to a unique eth addr.
If one gpu crashes the miner but didn't cause system hang, the other 7 conitnue working w/o restart. the crashed gpu would just restart automatically 30 second ~ 20 minutes late depending on how bad the situation is. If I start all 8 in one instance, it would restart all 8 gpus as many times as it could until the single crash one became stable.

As long as you have enough ram and processing power there shouldn’t be a performance hit. If you don’t have enough resources then yes.

I’ll often run 2 instances of a miner on the same system. Four cards on claymore and four on Phoenix to test the differences over a few days. But I have more ram and processing power than a mining computer typically needs.

[xunl]

Also I would like to know if I start 8 instances of command windows to run Phoenix miner on 8 gpus of the same rig, is there any performance penalty on that?
This is what I did for claymore right now. each miner takes -di # (# is a single digit between 0 to 7 representing 1 gpu)
8 instances of claymores, each mine to a unique eth addr.
If one gpu crashes the miner but didn't cause system hang, the other 7 conitnue working w/o restart. the crashed gpu would just restart automatically 30 second ~ 20 minutes late depending on how bad the situation is. If I start all 8 in one instance, it would restart all 8 gpus as many times as it could until the single crash one became stable.

As long as you have enough ram and processing power there shouldn’t be a performance hit. If you don’t have enough resources then yes.

I’ll often run 2 instances of a miner on the same system. Four cards on claymore and four on Phoenix to test the differences over a few days. But I have more ram and processing power than a mining computer typically needs.

Thanks

Since I was able to run 8 instances of claymore in one computer, I assume I would have enough resource to do the same for phoenix then. I start 8 instance also for benchmark reason as well. Particularly I was able to measure the true output for different brand gtx 1070/1060 rx 580 gpus: eth/hour on a particular gpu.

Which nVidia driver version is consider to be good for Phoenix miner?

[fimatiku]

Agreed. PhoenixMiner is the best! I have 6x1070 rig. Etherminer gives me 185-188MH, Claymore 10.6 - up to 190.2, but requires 2 restarts of rig per day to have stable hashrate (using windows scheduler), 11.0 - 11.5 do not provide stable hashrate (170 - 190), 11.6 did not test and do not want, but PhoenixMiner 2.8c gives me stable 191.6!!!

I use CL uptime 20 days+++ flawless same hash no issues so speak for yourself. perhaps crap PC or crap gpu? nvidia ? I run RX580's

[fimatiku]

To the Developer:

For some reason phoenixminer will NOT AUTO RUN using regedit but Claymore does  ? what gives

I set up all my rigs to auto log on auto mine - in case power loss or windows update or some other bulsh*t etc.........

works fine with claymore.

If I input phoenixminer.exe absolutely NOTHING HAPPENS AFTER REBOOT ..................... WTF.......................................

[human75]

To the Developer:

For some reason phoenixminer will NOT AUTO RUN using regedit but Claymore does  ? what gives

I set up all my rigs to auto log on auto mine - in case power loss or windows update or some other bulsh*t etc.........

works fine with claymore.

If I input phoenixminer.exe absolutely NOTHING HAPPENS AFTER REBOOT ..................... WTF.......................................

Just create short cut on windows startup folder wi start just perfect. you don't need regedit at all.. WTF: -) You don't need to swear at all. just ask. :-)

[speed07]

i think my one nvidia based rig is having a similar issue. it's running 2.8c.

it will run fine for 5-50+hrs, then suddenly it crashes, gets the "unspecified launch failure" error, and doesnt auto-restart. i can see that the watchdog triggered, but then the pheonixminer.exe crashes in windows and it hangs until i manually close it. i usually just reboot the system and it's fine. i run all default parameters except only running the -coin eth command, everything else is defaults.

my AMD based system on 2.8c is rock steady. runs for 300+ hrs and never crashes.

this is what's happening.

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

normally something like this would just trigger the watchdog, but it crashes in windows and just hangs. so it cant restart itself.

same problem..

[Digital_Seytan]

Phoenixminer 2.9.d is really a difference much less stale shares compared with v2.8.c, hashrate with default -mi 12 for nvidia suddenly goes up with phoenixminer 2.9.d some rigs run fixed or 999 therefore with afterburner settings something back.Thank you phoenixminer developer 2.9.d is really super with far fewer stale shares, so far it has been a long-term problem with high stale shares on all previous versions of phoenixminer. and at phoenixminer 2.9.d almost 0 stales, I do not know what you have done with this version but is really applause.Phoenixminer starting with all those percentages on the screen takes much longer, would be very nice if it would start without that is just as with ETHMiNER, hopefully you get that in the next version for each other a quick start of phoenixminer. if you need testers for upcoming new versions I like to help.

Phoenix startbat config i use Nvidia cards is here

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 100
PhoenixMiner.exe -pool eu1.ethermine.org:4444 -pool2 eu1.ethermine.org:4444 -wal 0xXXXXXXXXXXXXXXXXXXXXXXXXXX.rig1 -pass x -nvidia -proto 3 -ftimeout 120 -cdm 0 -log 0 -minRigSpeed 130.000 -rmode 2 - coin eth -coin2 eth -timeout 2200 -tstop 80 -start 70



1:First beta of 1.4.4 is here - WiNETHER 1.4.4. It can be downloaded from:
https://github.com/digitalpara/WiNETH

2:First beta of 1.4.4 is here - WiNETHER 1.4.4. It can be downloaded from:
https://mirrorace.com/m/1qikt

[Iamtutut]

Thanks, but I want to run 1 instance of Phoenix for nvidia and 1 instance of claymore for AMD on the same rig.
I don't have AMD 18.3 driver installed on the rig. I only have the blockchain beta which is not suitable for Phoenix miner. Claymore has run very stable on it for months and I don't want to upgrade the drivers to introduce unkown factor and downtime.
The nVidia driver on the rig is very stable as well. But if my nVidia driver is good enough for phoenix, I can start a separated instnace of cmd to run all GTX1070/1060 on the rig. Some unknown factors but no downtime. That's why I want to know what's a good version of nVidia driver to run Phoenix. I use afterburn to control OC/Voltage for nVidia cards. Thanks in advance.

I have no stability issue with the blockchain drivers and have been using phoenix since 2.6 version. 3X RX570 with bios mod.

[BennyT]

Thanks

Since I was able to run 8 instances of claymore in one computer, I assume I would have enough resource to do the same for phoenix then. I start 8 instance also for benchmark reason as well. Particularly I was able to measure the true output for different brand gtx 1070/1060 rx 580 gpus: eth/hour on a particular gpu.

Which nVidia driver version is consider to be good for Phoenix miner?

I've had no problems with Phoenix or other miners using the latest drivers from nvidia. If there was ever an issue, you can roll back to older versions.

[terrya]

upgraded from 2.8c
stale share of 900MH/s mining rigs down from 3-4% to 1% now
share from 7XX to 8XX now

[fimatiku]

2.9d slightly higher  than 2.8c hashrate for cards with Micron memory
2.8c slightly higher than claymore 11.6

----

with cl I got 190
with 2.8c i got 191
with 2.9d i got 192

same rig same cards

but CL had it runing for 20 days no issues windows works fine
2.8c after 10 hours windows start menue non responsive had to close miner and all is working, runing 2.9d now

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


Wow I just noticed it shows how many shares each card got and if any incorrect etc... very nice

32.5 - 32.6 mhs very nice

[Digital_Seytan]

Phoenixminer is possible stale shares which GPU - >> total ?? and gpu 1 /? gpu2 /? gpu3 /? etc. It is easier to change settings of the GPU that causes the most stales.