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

[PhoenixMiner]

OpenCL 19.20 AMD Driver
OS: HiveOS 0.6-142@200528
linux Ядpo 5.0.21-hiveos
4Gb AMD Asus Cards STRIX
Phoenix 5.0b

after epoch 350 in Nicehash Ethash I have low hashrates ~ 10-15 mhs from card.  after creation ETC DAG
-dagrestart 1, dont solve the problem. ((
What I am doing wrong?  Thx a lot

    We have tested with the same Linux drivers 19.20-812932 on Ubuntu 18.04 LTS (slightly older kernel but still 5.x) and everything works fine. Please check your other settings (i.e. clocks), and make sure that you are using auto-tune to find the best -gt values (they could be very different than before DAG epoch 350). Also, sometimes just restart of the rig solves such strange problems.

NO I DIDNT SEE THAT
AND IAM USUING THE BLOCK CHAIN DRIVER FROM 2017 "22.19.659.0"

    The blockchain driver is not tested with the new big DAG kernels and probably is not working properly. Install newer drivers (anything from 18.12.1.1 to 19.7.5) and make sure that you have switched the GPU Workload to Compute mode (by default they are in Graphics) in the AMD Control Center.

Dear Phoenix,

Do you have any plans to add the DAG-split feature to your miner?

For AMD - to allow 8-gig cards to continue mining ETH after the DAG exceeds 4GB
For NVIDIA - to fix the ETH speed reduction because of the raising DAG (on 10xx cards)

    We will definitely continue to support AMD 8 GB cards in the future. However this approach probably won't solve the Nvidia slow degradation of hashrate with each new DAG epoch.

I did some testing and it appears that there is a problem with -clkernel 3 on 8GB cards, the turbo kernel does not work anymore, changing back to -clkernel 1 did the job but it gives a little less hashpower.
PhoenixMiner or someone, could you please verify and confirm the same problem.
PhoenixMiner tnx and keep up the good work.

    There are no changes in -clkernel 3 - it is working as it was before. The problem is in the AMD drivers, which start to partially allocate shared memory (i.e. the mainboard RAM) as part of the DAG buffer as the used VRAM approaches 7.4-7.5 GB, which leads to sharp decrease in the hashrate. So, unless they fix it in the future drivers, -clkernel 3 is not viable for epoch 350 and above.

I tried both versions of the miner 5b-5c and at least 5 types of drivers and the maximum speed I achieved is 10.4m per card. The cards are RX 580 4G. I will be happy if someone shares if this problem can be fixed.

    Please check if your cards are switched to Compute mode in AMD control center. It is easy to miss if you are coming from the blockchain drivers, where there wasn't such option.

Hi all,
Fairly new here to mining (as of 2 hours ago),

Can anyone help me with this please ?


Eth: Giving up after 3 retries, switching to next pool
Eth: Reconnecting in 5 seconds...
Eth: Connecting to ethash pool us2.ethermine.org:14444 (proto: EthProxy)
Eth: Connected to ethash pool us2.ethermine.org:14444 (172.65.226.101)
Eth: New job #c02829d6 from us2.ethermine.org:14444; diff: 4000MH
GPU1: Starting up... (0)
GPU1: Generating ethash light cache for epoch #339
Eth: New job #89396b4b from us2.ethermine.org:14444; diff: 4000MH
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01
Light cache generated in 3.8 s (15.6 MB/s)
GPU1: Allocating DAG (3.66) GB; good for epoch up to #341
CUDA error in CudaProgram.cu:373 : out of memory (2)
GPU1: CUDA memory: 4.00 GB total, 3.33 GB free
GPU1 initMiner error: out of memory
Fatal error detected. Restarting.


Error 2 while trying to restart

I have a Nvidia GeForce GTX960 4gb ddr4 on a AMD FX8320 rig with 32gb ddr3 running win10

    The problem is that your video card is probably used by Windows and there are only 3.33 GB free VRAM, while the Ethereum DAG buffer requires 3.66 GB VRAM as you can see the the log file. So, you have either mine another coin with lower DAG epoch, or mine on another video card, with more free VRAM.

[PhoenixMiner]

PhoenixMiner 5.0c is officially released. You can find the download link and the checksums in the first post of this thread. This is a minor update over 5.9b with support for the latest AMD Windows driver.

The new features in this release are:

• Added support for latest AMD Windows driver 20.5.1
• Added SO_REUSEPORT option on the remote control port (default 3333) under Linux to prevent problems when the miner is restarting

If you are already running PhoenixMiner 5.0b, there is no need to update to 5.0c unless you want to run AMD Windows drivers 20.5.1, or need the small improvement for the Linux version.

[BradT]

Dear Phoenix,

Do you have any plans to add the DAG-split feature to your miner?

For AMD - to allow 8-gig cards to continue mining ETH after the DAG exceeds 4GB
For NVIDIA - to fix the ETH speed reduction because of the raising DAG (on 10xx cards)

   We will definitely continue to support AMD 8 GB cards in the future. However this approach probably won't solve the Nvidia slow degradation of hashrate with each new DAG epoch.

Maybe WDDM 2.7 technology would help to resolve the degradation?
It's supported in NVIDIA beta drivers 450.99 and will be included in final 451.13

https://www.reddit.com/r/intel/comments/f9ztf8/wddm_27_provides_better_performance_for_intel/

[denialo]

I have crashes with 5.0b and GTX1080Ti (11GB VRAM), driver 446.14.

CUDA error in CudaProgram.cu:456 : unknown error (999)
GPU1 search error: unknown error
Fatal error detected. Restarting.

Display driver nvlddmkm stopped responding and has successfully recovered.

This was not happening with older versions.
Could you please advise.

[booze]

I have crashes with 5.0b and GTX1080Ti (11GB VRAM), driver 446.14.

CUDA error in CudaProgram.cu:456 : unknown error (999)
GPU1 search error: unknown error
Fatal error detected. Restarting.

Display driver nvlddmkm stopped responding and has successfully recovered.

This was not happening with older versions.
Could you please advise.

What hash rate were you getting with your 1080ti? Im currently getting around 44mhs. With claymore i would get up to 48mhs using the OhGodAnETHlargementPill script. Not sure what hashrate to expect with Phoenix? Phooenix seems to run a bit more stable.

Thanks

[denialo]

Phoenix Miner 5.0c Windows/msvc - Release build
CUDA version: 11.0, CUDA runtime: 8.0
No OpenCL platforms found
Available GPUs for mining:
GPU1: GeForce GTX 1080 Ti (pcie 1), CUDA cap. 6.1, 11 GB VRAM, 28 CUs
NVML error in CudaProgram.cu:83 : Unknown Error (999)
Unable to initialize NVML


I'm getting 33 MH/s ... what i have wrong?

[jgonzi]

I have crashes with 5.0b and GTX1080Ti (11GB VRAM), driver 446.14.

CUDA error in CudaProgram.cu:456 : unknown error (999)
GPU1 search error: unknown error
Fatal error detected. Restarting.

Display driver nvlddmkm stopped responding and has successfully recovered.

This was not happening with older versions.
Could you please advise.

The problem is not the version... there are the new Nvidia Drivers. The best drivers Nvidia drivera are 442.59 ... de 445.87 are also really good they allow more overclock but hangs the computer.

[abg00]

plz help. have stable trouble on different version/

miner crash then switch to main pool
different drivers different windows version 1703 1709 1607 drivers 18.3.4 18.6.1 18.12.1.1
different amd card 470 480 570 580 4\8 gb different vendor. stable work on claymore without restart and crash....

check log. all ok but crash on switch
run as admin

[bategojko74]

plz help. have stable trouble on different version/

miner crash then switch to main pool
different drivers different windows version 1703 1709 1607 drivers 18.3.4 18.6.1 18.12.1.1
different amd card 470 480 570 580 4\8 gb different vendor. stable work on claymore without restart and crash....

check log. all ok but crash on switch
run as admin

Does it crash on epoch change switch or on Devfee mining switch? If it is on epoch change use -dagrestart 1. DO you mine ETC or ETH? What is your pool?

[abg00]

plz help. have stable trouble on different version/

miner crash then switch to main pool
different drivers different windows version 1703 1709 1607 drivers 18.3.4 18.6.1 18.12.1.1
different amd card 470 480 570 580 4\8 gb different vendor. stable work on claymore without restart and crash....

check log. all ok but crash on switch
run as admin

Does it crash on epoch change switch or on Devfee mining switch? If it is on epoch change use -dagrestart 1. DO you mine ETC or ETH? What is your pool?

use nicehash
no devfee change. return to main pool. dont know what coin before crash

[abg00]

manual pool switch same trouble. miner crash. dagrestart options add in bat file. add logs

2020.06.06:08:48:40.048: main
2020.06.06:08:48:40.048: main Eth: Select pool (press key from 1 to 6)
2020.06.06:08:48:40.048: main * 1. daggerhashimoto.eu.nicehash.com:3353
2020.06.06:08:48:40.048: main   2. daggerhashimoto.usa.nicehash.com:3353
2020.06.06:08:48:40.048: main   3. ssl://eu1.ethermine.org:5555
2020.06.06:08:48:40.048: main   4. ssl://eu1.whalesburg.com:7777
2020.06.06:08:48:40.048: main   5. eth-eu1.nanopool.org:9999
2020.06.06:08:48:40.048: main   6. eth-eu2.nanopool.org:9999
2020.06.06:08:48:40.048: main
2020.06.06:08:48:41.254: main Eth: Switching to pool: ssl://eu1.ethermine.org:5555

and crash without log record

[jgonzi]

I have change to PPS+ ETH, but I cannot connect, where I'm making the mistake…

 -pool eu.crazypool.org:3333 -wal <MyWallet>.<RigName>/<Referral> -pass x -proto 4 -tstop 75 -ttli 73 -tstart 55


It was working perfect before on the PPS+ ETC:

 -pool eu.crazypool.org:7000 -wal <MyWallet>.<RigName>/<Referral> -pass x -proto 4  -tstop 75 -tstart 55



Many thanks in advance...

[abg00]

I have change to PPS+ ETH, but I cannot connect, where I'm making the mistake…

 -pool eu.crazypool.org:3333 -wal <MyWallet>.<RigName>/<Referral> -pass x -proto 4 -tstop 75 -ttli 73 -tstart 55


It was working perfect before on the PPS+ ETC:

 -pool eu.crazypool.org:7000 -wal <MyWallet>.<RigName>/<Referral> -pass x -proto 4  -tstop 75 -tstart 55



Many thanks in advance...

add -coin ETH

[Aloki]

After upgrading to version 5.0c I also ran into a problem. I have cards with 4 GB of VRAM, the worker has 4 GB of RAM and runs on Linux, and I mine Ethash on NiceHash. During the switching from ETC to ETH the miner process is killed by OOM killer. On version 4.9c this doesn't happen.

[bategojko74]

After upgrading to version 5.0c I also ran into a problem. I have cards with 4 GB of VRAM, the worker has 4 GB of RAM and runs on Linux, and I mine Ethash on NiceHash. During the switching from ETC to ETH the miner process is killed by OOM killer. On version 4.9c this doesn't happen.

Smells like bug in 5.0X. Maybe PhoenixMiner should restart when switching the pools or coin and -dagrestart 1 is specified.

[jgonzi]

I have change to PPS+ ETH, but I cannot connect, where I'm making the mistake…

 -pool eu.crazypool.org:3333 -wal <MyWallet>.<RigName>/<Referral> -pass x -proto 4 -tstop 75 -ttli 73 -tstart 55


It was working perfect before on the PPS+ ETC:

 -pool eu.crazypool.org:7000 -wal <MyWallet>.<RigName>/<Referral> -pass x -proto 4  -tstop 75 -tstart 55



Many thanks in advance...

add -coin ETH

Many thanks for your answer

[Johnm2017]

After upgrading to version 5.0c I also ran into a problem. I have cards with 4 GB of VRAM, the worker has 4 GB of RAM and runs on Linux, and I mine Ethash on NiceHash. During the switching from ETC to ETH the miner process is killed by OOM killer. On version 4.9c this doesn't happen.

Smells like bug in 5.0X. Maybe PhoenixMiner should restart when switching the pools or coin and -dagrestart 1 is specified.

Having the same issue with restarts using version 5.0c.  All my 34 rigs are restarting after DEVFee disconnects. Never had these kind of issues with 4.9c
I'm using simplemining ( linux ) with amd18.20 drivers


DevFee: GPU6: DevFee share found!
DevFee: Share actual difficulty: 5672 MH
DevFee: Share accepted in 43 ms
DevFee: Disconnected and stopped
GPU5: Starting up... (0)
GPU3: Starting up... (0)
GPU2: Starting up... (0)
GPU4: Starting up... (0)
GPU6: Starting up... (0)
GPU1: Starting up... (0)
GPU5: Allocating DAG for epoch #340 (3.66) GB
GPU5: Generating DAG for epoch #340
GPU3: Allocating DAG for epoch #340 (3.66) GB
GPU3: Generating DAG for epoch #340
GPU2: Allocating DAG for epoch #340 (3.66) GB
GPU2: Generating DAG for epoch #340
GPU4: Allocating DAG for epoch #340 (3.66) GB
GPU4: Generating DAG for epoch #340
=======and here it crashes =========


and here it is the last part from the DEBUG Dmesg data :


 1159.100648] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
[ 1159.100649] Node 0 hugepages_total=128 hugepages_free=128 hugepages_surp=0 hugepages_size=2048kB
[ 1159.100649] 97718 total pagecache pages
[ 1159.100650] 0 pages in swap cache
[ 1159.100650] Swap cache stats: add 0, delete 0, find 0/0
[ 1159.100651] Free swap = 0kB
[ 1159.100651] Total swap = 0kB
[ 1159.100651] 967180 pages RAM
[ 1159.100652] 0 pages HighMem/MovableOnly
[ 1159.100652] 37451 pages reserved
[ 1159.100652] 0 pages cma reserved
[ 1159.100652] 0 pages hwpoisoned
[ 1159.127897] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.
[ 1159.127932] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.
[ 1159.127984] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.
[ 1159.128012] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.
[ 1159.128040] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.
[ 1159.128068] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.

[TeamCyr]

Man could you have used a crappier download site than MEGA? It failed four times and takes 25 minutes to download 5MB file. So dumb.

[TeamCyr]

After hearing all the issues with 5.0c I figured I work with 4.9c. But I am having the same errors as the 4.8c I was using for a while:

Can someone please help me??

All starts great:

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

Then two minutes later 3 out of 4 GPUs get disabled:

CudaProgram.cu:271 unknown error

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

[PhoenixMiner]

We have just released PhoenixMiner 5.0d that should fix the problem that some are experiencing when switching from ETC to ETH mining. You can find the download link and the checksums in the first post of this thread.

The new features in this release are:

• Fixed problem with crashing or slowing down when switching from ETC to ETH mining