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

[crypper]

Hi there, i basically got the same problem with my 1070s rig (11x) on Win10. Since DAG 200 Phönixminer fails to start some of the GPUs...

Im Using win10 with several 1070 and 1070ti's overclocked with nvidiaInspector. Overclocks did work for the last 7 months. And Claymore 11.9 works perfectly fine (less hashrate though).

Would be happy to get some help on this. Will post the solution.

For one thing overclock are not necessarily transferable from one miner to another. Try lower clocks (and don't use phoenix to set clocks and voltages; use AB or Nvidiainspector (my choice))
Another reason might be in you PSU: try -gser parameter (see OP for details)
And finally you can always run two instances of phoenix with 6 cards each.

 

[lankyman]

Well, I'm not sure I qualify as "security expert" but I certainly am a "full-time security paranoic"  And as no one else seem to risk it, I downloaded and tested the miner as well as I could.

First, I used an online virus scanner to check the file.
The results are: 2/67 detected (https://www.virustotal.com/#/file/74cfd6a34e158c2f5fe1b8422d6b8daee304394eeaf85992b117bf5de315d569/detection), which is actually an excellent result, given that the Claymore's miner gives 41/68 positives (https://www.virustotal.com/#/file/7852c50c835d7110ab8d055cccad06674e94d85324414f91366852bed9be29cc/detection).

And even the open-source ethminer 0.12.0 gives 26/67 positives, which is ridiculous (https://www.virustotal.com/#/file/4aa1082b5581540eced3acb18ee52cd06ee062772a5d386cf7501b2a8b7af094/detection) 

So, I prepared a backup image of the SSD of my rig (in case that this new miner turn out to be malicious) and then ran it for about 18 hours while monitoring the PhoenixMiner.exe network, file system, and registry activity with Wireshark and some advanced system calls monitors. It connected to my mining pool as it should and then opened port 3333, which turned out to be the port for remote control similar to Claymore's miner. I disabled to remote port with the "-cdm 0" commnad-line switch and restarted the miner. Sure enough, this time port 3333 wasn't opened and the only connection was the one to my pool.

The first new connection was observed after 16 minutes of mining, which connected to another pool (ehtermine.org) and the miner showed that it was mining for developer fee. It disconnected after 35 seconds as advertised. After that I left the rig alone and analyzed the Wireshark and the other logs the next day.

The miner connected to the devfee pool every 90 minutes, with one exception when it wasn't able to connect to the ehtermine.org. It then tried again after 13 minutes and then resumed the normal 90 minutes period between devfee connections. No other network activity was recorded. The registry activity was also normal (no keys were created and no suspicious registry key reading was detected). Also, no files outside the current folder were opened or touched.

As for the mining speed, my rig has 6x ASUS Strix 570 OC (with BIOS mod) and under Claymore's miner it makes about 173 mhs. With Phoenix the speed was about 174.5 mhs, which is not much better but I guess is still something. The power consumption from the wall was about the same (755-765W). According the the pool, the speed was even better (169 vs 166 with claymore) but this doesn't mean much as I've seen this numbers change a lot without any apparent reason, so it would take some more time before declaring PhoenixMiner to be faster.

Of course, there is no guarantee that the PhoenixMiner won't "decide to go bad" at some point of the future, but right now it seems legit. 

Some suggestions for the devs: the share difficulty is a nice touch but it would be better to directly show the number of blocks found. Most pools doesn't report this and even when they do, I'm always suspicions. Also, your miner does seem to be compatible with Claymore's manager, which is nice, but I hope that you will produce a better manager (and maybe even a mobile app for Android), because the claymore's manager is rather simplistic and I miss a lot of features.

Love this man, i need to learn what you do did here cause there are so many fking hackers and phisher out there its scary.
Ive been hacked at Nicehash and Bittrex my own fault, for not enabling 2FA and who knows how guys get your e-mail account passwords and things.
You are the smallest fish and people still f u over for any small amounts of reward.
Feel too scared of wallets and miners, you never know what the hell code is written in there to extort you

[ciprianpt]

Hey guys, i made a quick review and benchmark on hashrate side for rx 470 4gb and rx 580 8gb, here you can find the results https://1stminingrig.com/phoenixminer-review-and-benchmark/, ill have better results/test soon.

[FedorSumkin]

Hello! on 1080 for some reason does not work ??

[okiesmokie]

Hello! on 1080 for some reason does not work ??

Wait for 3.1 version soon™

[Call_Me_Bambi]

What about Linux? Soon?

Add a +1 to that, it would be nice if there was a Linux version available, this would then definatively give Claymore a run for its money.

[ganzocrypt]

Hello,

new here!
What is a good intensity mi/gt for RX 580 8Gb and RX 580 4G?

.................. -stales 0 -amd -acm -mi 12 -gt 15 -gser 2 -wdog 1 -tt 75 -tmax 82 -fanmin 70 -fanmax 90 -powlim -4 -cclock 1200 -mclock 2000 -cvddc 960 -mvddc 960

Any suggestion on tuning to get max hashrate?


I was trying to use +/- but I do not see the increase of intensity

[bitcoin.dbi]

Hello. Is it possible to make more then 2 pools in batfile? Using -pool and -pool2 command but -pool3 looks like unknown command for miner ;(
P.S. Can't use epool.txt.

[BRacing]

The miner does not start. 4pcs 280x cards, -amd option included. Windows 7 x64, the swap file more than 16GB. Drivers 15.12. Debugger detected error.

[Stargatesgx]

hello ive had some stability issues and using the -nvf 3 command line

is it supposed to affect individual gpu hashrate or overall effective hashrate at the pool

i seem to experiencing the latter

thanks
regards

[4ward]

Try Forager - Multi-algo switching miner for AMD/NVIDIA/CPU

Continuously developed, with largest selection and latest versions of miners and algos.
Highly configurable, Integrated Afterburner support for power usage and profit calculation


Phoenix miner support included

[Haruderty]

The miner does not start. 4pcs 280x cards, -amd option included. Windows 7 x64, the swap file more than 16GB. Drivers 15.12. Debugger detected error.

I have similar problem.

[prier]

Interesting indeed.

Move the GPU with that error to a different slot with different cables, and see what GPU has the error. If the GPU you moved has the error again, I would assume it could be failing, it's the luck of the silicon lottery..

Sorry for the late reply. I tried to disable GPU 12 and the miner works with GPUs 1-11. Then I tried to disable GPU9 and re-enable GPU 12 and the miner also works with GPU12 now working and GPU9 idle. I swapped the cards a bit too just to rule out hardware.

It appears only 11 GPUs can run at any given time. So this confirms it is not a GPU hardware problem.

I raised the VRAM to min 40GB and max 56GB and all 12 GPUs were humming along just fine. Thank you PhoenixMiner devs for the tip.

Hi there, i basically got the same problem with my 1070s rig (11x) on Win10. Since DAG 200 Phönixminer fails to start some of the GPUs (usually 1-5 are ok, 6-12 failed). In Claymore 11.9 everything is working fine. I tested the hardware and everything is fine.

I did:
- test the graphic cards (no issues in other rig with linux)
- raise the VRAM to 40GB (min) and 56GB (max)
- update Nvidia driver to latest update

Still i got this errors:

Code:

2018.08.10:13:37:38.055: wdog GPU6 not responding
2018.08.10:13:37:38.055: wdog GPU7 not responding
2018.08.10:13:37:38.055: wdog GPU8 not responding
2018.08.10:13:37:38.055: wdog GPU9 not responding
2018.08.10:13:37:38.055: wdog GPU10 not responding
2018.08.10:13:37:38.055: wdog GPU11 not responding
2018.08.10:13:37:38.055: wdog Thread(s) not responding. Restarting.

Im Using win10 with several 1070 and 1070ti's overclocked with nvidiaInspector. Overclocks did work for the last 7 months. And Claymore 11.9 works perfectly fine (less hashrate though).

Would be happy to get some help on this. Will post the solution.

Same problem here, since no recent update i had to switch back to claymore

[Merkle_Tree]

Anyone who has a claymore miner? What miner is faster for you?

I downloaded different claymore versions at max setting still pheonix is faster. Is this always true or its just me?

[Merkle_Tree]

The miner does not start. 4pcs 280x cards, -amd option included. Windows 7 x64, the swap file more than 16GB. Drivers 15.12. Debugger detected error.

Try using AMD blockchain driver.

Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23

[Merkle_Tree]

The miner does not start. 4pcs 280x cards, -amd option included. Windows 7 x64, the swap file more than 16GB. Drivers 15.12. Debugger detected error.

I have similar problem.

Yours too true using blockchain driver.

Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23

[Triforcebg]

Anyone who has a claymore miner? What miner is faster for you?

I downloaded different claymore versions at max setting still pheonix is faster. Is this always true or its just me?

I have Phoenix & Claymore, from 2 days teting Phoenix and see a little difference. Maybe Phoenix is better. But I need one more week to be sure.
Not sure about -mi & - gt tweaks. What are the best for rx580?

[yobigd20]

has anyone ever had an issue where when they upgrade to newer amd driver versions (tried 18.1.1, 18.2.1, 18.5.1, 18.8.1), that it takes FOREVER to start the mining software?  

I'm talking about 5-15 minutes between when phoenix miner says 'starting gpu mining' to when it actually starts mining.  This affects other windows stuff too, , such as right clicking the desktop background it takes like 60 seconds to pop up the right click menu, or clicking the windows start menu takes like 60-120 seconds to show.  

When I revert back to aug23 blockchain beta driver, everything works fine/quickly, no delays, miner starts right up immediately (same params, nothing changed other than windows driver version), right clicking desktop background displays pop up menu immediately, etc.    

I've tried this on multiple rigs, all the same result with the v18.x.x drivers basically crippling everything.    I've DDU'd multiple times too to make sure system was clean.  I have no explanation for this, can't pinpoint the reason for this...stuck on this and want to upgrade drivers (I hate having to bios mod to undervolt, which doesn't even seem to work right on blockchain driver version anyway).

any help or suggestions?

fyi also my rigs each are win10 prof, core i3/i5/i7, have 8gb ram, and 120 or 240gb ssd with virtual memory page file set to 64gb, and I use onboard graphics for display with commercial kvm plugged into hdmi or dvi on the mobo.

[MrTDHP]

Anybody else having issue when mining on Nicehash?
My bat file follows the provided example. But after a while it seems to be rebuilding DAG and then looks like it just stops then >pause and >Press any key to continue...
Never happens when mining on other pools (i.e. ethermine) though

[damba_]

has anyone ever had an issue where when they upgrade to newer amd driver versions (tried 18.1.1, 18.2.1, 18.5.1, 18.8.1), that it takes FOREVER to start the mining software?  

I'm talking about 5-15 minutes between when phoenix miner says 'starting gpu mining' to when it actually starts mining.  This affects other windows stuff too, , such as right clicking the desktop background it takes like 60 seconds to pop up the right click menu, or clicking the windows start menu takes like 60-120 seconds to show.  

When I revert back to aug23 blockchain beta driver, everything works fine/quickly, no delays, miner starts right up immediately (same params, nothing changed other than windows driver version), right clicking desktop background displays pop up menu immediately, etc.    

I've tried this on multiple rigs, all the same result with the v18.x.x drivers basically crippling everything.    I've DDU'd multiple times too to make sure system was clean.  I have no explanation for this, can't pinpoint the reason for this...stuck on this and want to upgrade drivers (I hate having to bios mod to undervolt, which doesn't even seem to work right on blockchain driver version anyway).

any help or suggestions?

fyi also my rigs each are win10 prof, core i3/i5/i7, have 8gb ram, and 120 or 240gb ssd with virtual memory page file set to 64gb, and I use onboard graphics for display with commercial kvm plugged into hdmi or dvi on the mobo.

I am using 18.3.4. drivers and the miner start mining immediately.
Before I used blockchain beta driver, but versions 18.3.4. turned out more stable for me than beta blockchain drivers.