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

[A62662]

Windows 10 gives this report; Trojan:Win32/Phoenix

5.6d

[swogerino]

Windows 10 gives this report; Trojan:Win32/Phoenix

5.6d

It is a false positive from Windows defender if you have it enabled.Open Task Manager go to Startup and disable Windows defender if you keep your computer only for mining.Download 5.6d again from the link in the first page of this topic and it should not give that report anymore.

Note:Do not download it from any other source than here the miner,https://phoenixminer.info/downloads/ or it might be a trojan for real then.

[xandry]

Hello, so I usually see phoenixminer’s console on windows or other with color or if i go to the miner log, but when ever i launch the HIVE SHELL and a type miner, everything is in black and white ?
Is there a way to see the normal color output in HiveOS?

It is not miner problem, it is Hive OS specific problem. You need to ask it on their support. But first of all, check your .bashrc file (home or root)
It can help: https://www.shellhacks.com/bash-colors/

[Hdom]

Hello, I am still running into an issue where my pheonixminer just shuts down by itself without any error messages after around 3 days, when the log messages file reaches around 110-120MB.

The miner is running fine and then all of a sudden

Code:

2021.06.27:18:33:56.022: unkn Quitting...

and all GPUs are reset and the program closes.

Here is what the logs look like, note the log sizes.
https://i.imgur.com/uBeax0R.png

System runs stable otherwise, I have the same situation on 4 different rigs all running different configuration of GPUs.

Any advice?

[Targonis]

Hello, I am still running into an issue where my pheonixminer just shuts down by itself without any error messages after around 3 days, when the log messages file reaches around 110-120MB.

The miner is running fine and then all of a sudden

Code:

2021.06.27:18:33:56.022: unkn Quitting...

and all GPUs are reset and the program closes.

Here is what the logs look like, note the log sizes.


System runs stable otherwise, I have the same situation on 4 different rigs all running different configuration of GPUs.

Any advice?

First, check temperatures, not just GPUs, but possibly the CPU itself.    Then, check the voltages you have set for your video cards.   While many can undervolt to a certain voltage and speed, other cards will have a problem if you don't give enough voltage to your video cards(both GPU and VRAM).   Many people mistake that what seems to be a perfectly good configuration has a SMALL amount of instability that only shows up after a certain amount of time.   One of your video cards may even be failing or having a problem, but I wouldn't jump to that conclusion just yet.   Now, what operating system are you running, since drivers can also be the source of a lot of headaches.

[deedeeranged]

Anyone that has a decent icon/image for PhoenixMiner I can use on Linux?
Would be appreciated.

[makipsee]

Does anyone know of a way to clear Overclocks in MSI afterburner when changing DAG files when using EZIL? I know this can kinda be done using Zilminer but they use Shardpool and want to keep everything in one place.

Thank you

[Targonis]

• Added support for AMD Windows drivers 21.5.1, 21.4.1, 21.3.2, and 21.3.1

Bugs or not supported 21.5.1?

1. After updating 5.6d and AMD drivers 21.5.1 all specified GPU commands not valid (example "-cclock 1:xxx,2:xxx etc").
2. Try to change all GPUS:s with the same value only 1 of 6 might apply. (example -cclock 1000) 5 of 6 keeps the old settings and not reading config file or something.

So weird. Also some of cards Memclock boosted to max and cause system failure.

Edit:
And 21.3.1 drivers it works just fine.
I like KIND of 21.5.1 when it works because slight 0.2MH/s increase in 5600XT

The real 5.6d works with Radeon Software 21.5.2 and earlier, but does NOT work with 21.6.1(which Windows Update keeps forcing down my throat with every check for updates).   Yes, I can go to the unoptimized kernel route, but I'd rather not have to do that when there SHOULD be a new version to support the new drivers.

[hustleman]

So mining with an earlier verson of phxminer.  If I start the miner with the overclocks applied on the 3070s and 3060ti, one of these cards gets nothing but invalid shares.  So i have to shut the miner down, set msi afterburner settings to default, restart the miner and let the DAGS build to 100%, then after this apply the overclockings.  This is a pain in the ass, especially if the miner faults and restarts.

My question is has this been fixed with the newest version of Phxminer?

[powvex]

How to dual mine eth + zil on shardpool+ethermine
and etc + zil on them?

[dastardlyman12]

Hello folks.
i recommend windows 10 ghost spectre
no bloat no updates no telemetry.
This is how all are rigs are done:

Setup a usb stick done with rufus and "MBR" with the ghost spectre iso.

get your rig with ssd - do a fresh (wipe the ssd) install of windows ghost spectre using the stick you have just prepared
take the ethernet out BEFORE you start.
make sure you have a copy of the amd driver - eg 20.9.1 or 21.3.1 and install it on the rig
when amd driver installed then plug the internet in.
thats it. you still need to do stuff like pixel patcher and compute mode and virtual memory but you only do it once
windows will not screw anything up afterwards.

we have 30 odd rigs none of them have updated or done anything at all to screw mining up.

do a test install of ghost spectre you will be amazed.

the only reason i unplug the internet is so can customise windows and make sure i get the right amd driver on there.
spectre will try and get the amd driver itself if you dont do it first. but spectre wont update after you have the base system
done.
we use phoenix cos of the -ttli feature and we have dwagent on each rig for remote access
no need for hiveos

[deedeeranged]

The real 5.6d works with Radeon Software 21.5.2 and earlier, but does NOT work with 21.6.1(which Windows Update keeps forcing down my throat with every check for updates).   Yes, I can go to the unoptimized kernel route, but I'd rather not have to do that when there SHOULD be a new version to support the new drivers.

Disable Windows driver update. Never used the Windows Driver update as I install the drivers I want and not
Windows.

[makipsee]

So mining with an earlier verson of phxminer.  If I start the miner with the overclocks applied on the 3070s and 3060ti, one of these cards gets nothing but invalid shares.  So i have to shut the miner down, set msi afterburner settings to default, restart the miner and let the DAGS build to 100%, then after this apply the overclockings.  This is a pain in the ass, especially if the miner faults and restarts.

My question is has this been fixed with the newest version of Phxminer?

I have this same problem. But I created some cmd/bat files that work on timers. So when I call up one file it calls up Phoenixminer and also opens another bat file with a timeout command until the DAGs are built then it calls up MSI afterburner to my set profile. But I wish there was a way to call up files when using EZIL so I can cancel the overclocks when it's switching coins.

[makipsee]

How to dual mine eth + zil on shardpool+ethermine
and etc + zil on them?

You can use EZIL to dual mine on their pools. Otherwise would need to use some thing like zilminer which can open the miner of your choosing and then close that miner during the ZIL period

[swogerino]

So mining with an earlier verson of phxminer.  If I start the miner with the overclocks applied on the 3070s and 3060ti, one of these cards gets nothing but invalid shares.  So i have to shut the miner down, set msi afterburner settings to default, restart the miner and let the DAGS build to 100%, then after this apply the overclockings.  This is a pain in the ass, especially if the miner faults and restarts.

My question is has this been fixed with the newest version of Phxminer?

I have this same problem. But I created some cmd/bat files that work on timers. So when I call up one file it calls up Phoenixminer and also opens another bat file with a timeout command until the DAGs are built then it calls up MSI afterburner to my set profile. But I wish there was a way to call up files when using EZIL so I can cancel the overclocks when it's switching coins.

I had the same exact problem with RX 6800 XT-s,any time the DAG were to be recreated while cards being overclocked it would stop mining or disable one of the cards,usually the card with the error.I fixed this by using the command line argument in start-miner bat file which adds up to 14 DAG-s to come mining without problems.The command is : -eres 2-14(number of Epochs) 14 is the maximum,I set it to 6 or 8 usually.No problems after applying this so far.

[makipsee]

So mining with an earlier verson of phxminer.  If I start the miner with the overclocks applied on the 3070s and 3060ti, one of these cards gets nothing but invalid shares.  So i have to shut the miner down, set msi afterburner settings to default, restart the miner and let the DAGS build to 100%, then after this apply the overclockings.  This is a pain in the ass, especially if the miner faults and restarts.

My question is has this been fixed with the newest version of Phxminer?

I have this same problem. But I created some cmd/bat files that work on timers. So when I call up one file it calls up Phoenixminer and also opens another bat file with a timeout command until the DAGs are built then it calls up MSI afterburner to my set profile. But I wish there was a way to call up files when using EZIL so I can cancel the overclocks when it's switching coins.

I had the same exact problem with RX 6800 XT-s,any time the DAG were to be recreated while cards being overclocked it would stop mining or disable one of the cards,usually the card with the error.I fixed this by using the command line argument in start-miner bat file which adds up to 14 DAG-s to come mining without problems.The command is : -eres 2-14(number of Epochs) 14 is the maximum,I set it to 6 or 8 usually.No problems after applying this so far.

But this only works as long as you have enough vram to store the DAG files. No?

[hustleman]

So mining with an earlier verson of phxminer.  If I start the miner with the overclocks applied on the 3070s and 3060ti, one of these cards gets nothing but invalid shares.  So i have to shut the miner down, set msi afterburner settings to default, restart the miner and let the DAGS build to 100%, then after this apply the overclockings.  This is a pain in the ass, especially if the miner faults and restarts.

My question is has this been fixed with the newest version of Phxminer?

I have this same problem. But I created some cmd/bat files that work on timers. So when I call up one file it calls up Phoenixminer and also opens another bat file with a timeout command until the DAGs are built then it calls up MSI afterburner to my set profile. But I wish there was a way to call up files when using EZIL so I can cancel the overclocks when it's switching coins.

I had the same exact problem with RX 6800 XT-s,any time the DAG were to be recreated while cards being overclocked it would stop mining or disable one of the cards,usually the card with the error.I fixed this by using the command line argument in start-miner bat file which adds up to 14 DAG-s to come mining without problems.The command is : -eres 2-14(number of Epochs) 14 is the maximum,I set it to 6 or 8 usually.No problems after applying this so far.

Looking again at the reread me file... It appears phx created a command of -mcdag that puts the overclocking to default till after the dag is built.  Will have to give this a try in the bat.file

[swogerino]

So mining with an earlier verson of phxminer.  If I start the miner with the overclocks applied on the 3070s and 3060ti, one of these cards gets nothing but invalid shares.  So i have to shut the miner down, set msi afterburner settings to default, restart the miner and let the DAGS build to 100%, then after this apply the overclockings.  This is a pain in the ass, especially if the miner faults and restarts.

My question is has this been fixed with the newest version of Phxminer?

I have this same problem. But I created some cmd/bat files that work on timers. So when I call up one file it calls up Phoenixminer and also opens another bat file with a timeout command until the DAGs are built then it calls up MSI afterburner to my set profile. But I wish there was a way to call up files when using EZIL so I can cancel the overclocks when it's switching coins.

I had the same exact problem with RX 6800 XT-s,any time the DAG were to be recreated while cards being overclocked it would stop mining or disable one of the cards,usually the card with the error.I fixed this by using the command line argument in start-miner bat file which adds up to 14 DAG-s to come mining without problems.The command is : -eres 2-14(number of Epochs) 14 is the maximum,I set it to 6 or 8 usually.No problems after applying this so far.

But this only works as long as you have enough vram to store the DAG files. No?

Yes but if you set it to 14 it will work for a few days so that boring work of restoring to default and then overclocking will be done only once in a few days.I think it will be fixed in future versions of the Phoenix miner but for the moment this is the only solution.

[makipsee]

So mining with an earlier verson of phxminer.  If I start the miner with the overclocks applied on the 3070s and 3060ti, one of these cards gets nothing but invalid shares.  So i have to shut the miner down, set msi afterburner settings to default, restart the miner and let the DAGS build to 100%, then after this apply the overclockings.  This is a pain in the ass, especially if the miner faults and restarts.

My question is has this been fixed with the newest version of Phxminer?

I have this same problem. But I created some cmd/bat files that work on timers. So when I call up one file it calls up Phoenixminer and also opens another bat file with a timeout command until the DAGs are built then it calls up MSI afterburner to my set profile. But I wish there was a way to call up files when using EZIL so I can cancel the overclocks when it's switching coins.

I had the same exact problem with RX 6800 XT-s,any time the DAG were to be recreated while cards being overclocked it would stop mining or disable one of the cards,usually the card with the error.I fixed this by using the command line argument in start-miner bat file which adds up to 14 DAG-s to come mining without problems.The command is : -eres 2-14(number of Epochs) 14 is the maximum,I set it to 6 or 8 usually.No problems after applying this so far.

Looking again at the reread me file... It appears phx created a command of -mcdag that puts the overclocking to default till after the dag is built.  Will have to give this a try in the bat.file

This only works If you are using the overclocking within phoenixminer. If you use an external program it won't work

[makipsee]

So mining with an earlier verson of phxminer.  If I start the miner with the overclocks applied on the 3070s and 3060ti, one of these cards gets nothing but invalid shares.  So i have to shut the miner down, set msi afterburner settings to default, restart the miner and let the DAGS build to 100%, then after this apply the overclockings.  This is a pain in the ass, especially if the miner faults and restarts.

My question is has this been fixed with the newest version of Phxminer?

I have this same problem. But I created some cmd/bat files that work on timers. So when I call up one file it calls up Phoenixminer and also opens another bat file with a timeout command until the DAGs are built then it calls up MSI afterburner to my set profile. But I wish there was a way to call up files when using EZIL so I can cancel the overclocks when it's switching coins.

I had the same exact problem with RX 6800 XT-s,any time the DAG were to be recreated while cards being overclocked it would stop mining or disable one of the cards,usually the card with the error.I fixed this by using the command line argument in start-miner bat file which adds up to 14 DAG-s to come mining without problems.The command is : -eres 2-14(number of Epochs) 14 is the maximum,I set it to 6 or 8 usually.No problems after applying this so far.

But this only works as long as you have enough vram to store the DAG files. No?

Yes but if you set it to 14 it will work for a few days so that boring work of restoring to default and then overclocking will be done only once in a few days.I think it will be fixed in future versions of the Phoenix miner but for the moment this is the only solution.

I tried setting it to 8 but I don't see any confirmation in the command when it's starting up. And it still get invalid shares.