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

[Gpumanijak]

Hi

Suddenly @ 13:30 GMT+2 on the 22 of August, my PhoenixMiner reports error while mining ETC on 3 GB cards

GPU1: Starting up… (0)
GPU1: Generating etchash light cache for epoch #223
Listening for CDM remote manager at port 3335 in read-only mode
Eth: New job #7e8cde29 from eu-etc.hiveon.net:8888; diff: 5000MH
Eth: New job #778ea926 from eu-etc.hiveon.net:8888; diff: 5000MH
Light cache generated in 4.3 s (10.2 MB/s)
GPU1: Free VRAM: 2.966 GB; used: 0.018 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #223 (2.74) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.

As far as I knwo we are far ( 1 year ) from being at epoch so DAG file size is over 3 GB

Other miners continue to work properly ( e.g. : lolminer )

I use 5.7b but also tried with 5.4c

Any idea ?

I have the same problem, anyone found solution ?

one card in system? miner card connect to monitor?

The number of cards does not matter. The same on 1 card. Two, four. Connecting the monitor also does not matter. It was working normally. It stopped working on all computers overnight. I am currently using lolminer and it works fine. But I'd rather go back to Phoenix Miner ... I just don't know how.

I'm mining ETC ...

Same problem with 280x 3gb, will anyone solve this??

[sleep0fox]

Hi, PhoenixMiner Dev

"-rmode 2" option does not work for non-GPU errors, it works only GPU errors.

Non-GPU errors are always fixed to "restart" by default.

I want to reboot on non-GPU errors with "-rmode 2" option.

--- Non-GPU errors are Stratum error, etc.


Make sure to chain all non-GPU errors to "-rmode <n>".
can fix it ?

[Bagge6]

Hello everyone

I am using Phoenix miner but -mi doesnt work for some reason, is there a button to set mining intensity? I tried numpads + and - but it gives me text "GPU tuning is disabled only optimized kernels" or something alike
In my config.cfg there is -mi 6 for example but it mines with 100% intensity still

Btw I managed to bios flash 2 cards (5700xt Gigabyte and PowerColor) from 49.7mh/s to 53.8mh/s so if anyone need help with this send me a pm

[relax69]

Guys when I want enable watchdog function for moments when my gpu crash, for automatical restart Phoenix miner, must I write manually into my bat file "-wdog 1" or watchdog function works automatically without any additional parametr in file?

In the miner's directory have readme.txt file. You could find this in there:

Code:

-wdog <n>
   Enable watchdog timer: 1 - yes, 0 - no (1 is the default). The
   watchdog timer checks periodically if any of the GPUs freezes and
   if it does, restarts the miner (see the "-rmode" command-line
   parameter for the restart modes)

-wdtimeout <n>
   Watchdog timeout (30 - 300; default 45 seconds). You can use this
   parameter to increase the default watchdog timeout in case it
   restarts the miner needlessly

-rmode <n>
   Selects the restart mode when a GPU crashes or freezes: :0:
   disabled - miner will shut down instead of restarting :1: restart
   with the same command line options - this is the default :2: reboot
   (shut down miner and execute "reboot.bat")

[micdee]

Well PM 5.7b is finally running.. with the AMD 21.1.8.1
I know I am an impatient person..
With 5.5c it was about 10-20 seconds I had to wait before I could see the openCL drivers were loaded and the rest of the config file was executed.

but waiting for 5-6 minutes to finally see that the miner is actually start to load the openCL drivers and read the rest of the config file...
Is the long waiting period all have to do with the extra setting features in PM?

I understand it has something to do with the pentium (3,3Ghz) CPU I use, but from 10-20 sec to 5-6 minutes waiting is a bit much in my opinion.. Anything I can do to shorten this? without upgrading my CPU..
I also use 16Gb of RAM..

any help much appreciated.

[m1chael]

Guys when I want enable watchdog function for moments when my gpu crash, for automatical restart Phoenix miner, must I write manually into my bat file "-wdog 1" or watchdog function works automatically without any additional parametr in file?

In the miner's directory have readme.txt file. You could find this in there:

Code:

-wdog <n>
   Enable watchdog timer: 1 - yes, 0 - no (1 is the default). The
   watchdog timer checks periodically if any of the GPUs freezes and
   if it does, restarts the miner (see the "-rmode" command-line
   parameter for the restart modes)

-wdtimeout <n>
   Watchdog timeout (30 - 300; default 45 seconds). You can use this
   parameter to increase the default watchdog timeout in case it
   restarts the miner needlessly

-rmode <n>
   Selects the restart mode when a GPU crashes or freezes: :0:
   disabled - miner will shut down instead of restarting :1: restart
   with the same command line options - this is the default :2: reboot
   (shut down miner and execute "reboot.bat")

Thank you for info. 👍
So I added into my bat file these parametres and looks it ok:  -log 0 -wdog 1 -rmode 1 -nvidia

[janding]

Well PM 5.7b is finally running.. with the AMD 21.1.8.1
I know I am an impatient person..
With 5.5c it was about 10-20 seconds I had to wait before I could see the openCL drivers were loaded and the rest of the config file was executed.

but waiting for 5-6 minutes to finally see that the miner is actually start to load the openCL drivers and read the rest of the config file...
Is the long waiting period all have to do with the extra setting features in PM?

I understand it has something to do with the pentium (3,3Ghz) CPU I use, but from 10-20 sec to 5-6 minutes waiting is a bit much in my opinion.. Anything I can do to shorten this? without upgrading my CPU..
I also use 16Gb of RAM..

any help much appreciated

I think is something else other than the CPU processor.
This is what I'm using and 5.7b comes up and runs in seconds for me.

Processor   Intel(R) Pentium(R) CPU G4400 @ 3.30GHz, 3312 Mhz, 2 Core(s), 2 Logical Processor(s)
Also same memory 16Gb

[relax69]

Well PM 5.7b is finally running.. with the AMD 21.1.8.1
I know I am an impatient person..
With 5.5c it was about 10-20 seconds I had to wait before I could see the openCL drivers were loaded and the rest of the config file was executed.

but waiting for 5-6 minutes to finally see that the miner is actually start to load the openCL drivers and read the rest of the config file...
Is the long waiting period all have to do with the extra setting features in PM?

I understand it has something to do with the pentium (3,3Ghz) CPU I use, but from 10-20 sec to 5-6 minutes waiting is a bit much in my opinion.. Anything I can do to shorten this? without upgrading my CPU..
I also use 16Gb of RAM..

any help much appreciated.

Most likely is nothing to do with the CPU or with the PM software. I had same issue after I try to find best drivers for me they did huge mess in the registry.

Best way to fix this is to do system restore to the point when the Windows was just installed or to do fresh install. Please note in this case you will lost all your files so do backup before instalation.
Another option to speed up could be to uninstall drivers and clean up registry manualy, but I would not recomend it because will speed up but not to the point of fresh installation.

Also you could gain little speed if you use hard disk, by replacing it with SSD.

[swogerino]

Well PM 5.7b is finally running.. with the AMD 21.1.8.1
I know I am an impatient person..
With 5.5c it was about 10-20 seconds I had to wait before I could see the openCL drivers were loaded and the rest of the config file was executed.

but waiting for 5-6 minutes to finally see that the miner is actually start to load the openCL drivers and read the rest of the config file...
Is the long waiting period all have to do with the extra setting features in PM?

I understand it has something to do with the pentium (3,3Ghz) CPU I use, but from 10-20 sec to 5-6 minutes waiting is a bit much in my opinion.. Anything I can do to shorten this? without upgrading my CPU..
I also use 16Gb of RAM..

any help much appreciated

I think is something else other than the CPU processor.
This is what I'm using and 5.7b comes up and runs in seconds for me.

Processor   Intel(R) Pentium(R) CPU G4400 @ 3.30GHz, 3312 Mhz, 2 Core(s), 2 Logical Processor(s)
Also same memory 16Gb

I have even a slower processor that I use which is G3900 Celeron which is the lowest of Gen 6 processors and it works perfectly well with the Rx 6800 XT cards I have.The processor is ruled out here and I think you need to uninstall drivers and reinstall them once again,installing a new version of driver like 21.8.1 over an old one does not always run smoothly so this is the first thing to check.Also the HDD is not a problem as the difference between an SSD and an HDD is big enough but surely not 6 minutes.

[dazmann]

Well PM 5.7b is finally running.. with the AMD 21.1.8.1
I know I am an impatient person..
With 5.5c it was about 10-20 seconds I had to wait before I could see the openCL drivers were loaded and the rest of the config file was executed.

but waiting for 5-6 minutes to finally see that the miner is actually start to load the openCL drivers and read the rest of the config file...
Is the long waiting period all have to do with the extra setting features in PM?

I understand it has something to do with the pentium (3,3Ghz) CPU I use, but from 10-20 sec to 5-6 minutes waiting is a bit much in my opinion.. Anything I can do to shorten this? without upgrading my CPU..
I also use 16Gb of RAM..

any help much appreciated.

Your HDD or SSD might be the culprit. Check the S.M.A.R.T. Try a chkdsk to check for errors or try a defrag. If not, try doing a clean installation of the GPU drivers using DDU (Display Driver Uninstaller) and download the full driver version from the release notes page, do not use the updater/downloader.

[Jonasuke]

Hello anyone can help me for thats problem.
Its my first try on windows 10 Pro 64

https://i.ibb.co/B2zBMWD/error-phoenix-start.jpg

best regards

[oleg_123]

Hi

Suddenly @ 13:30 GMT+2 on the 22 of August, my PhoenixMiner reports error while mining ETC on 3 GB cards

GPU1: Starting up… (0)
GPU1: Generating etchash light cache for epoch #223
Listening for CDM remote manager at port 3335 in read-only mode
Eth: New job #7e8cde29 from eu-etc.hiveon.net:8888; diff: 5000MH
Eth: New job #778ea926 from eu-etc.hiveon.net:8888; diff: 5000MH
Light cache generated in 4.3 s (10.2 MB/s)
GPU1: Free VRAM: 2.966 GB; used: 0.018 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #223 (2.74) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.

As far as I knwo we are far ( 1 year ) from being at epoch so DAG file size is over 3 GB

Other miners continue to work properly ( e.g. : lolminer )

I use 5.7b but also tried with 5.4c

Any idea ?

I have the same problem, anyone found solution ?

one card in system? miner card connect to monitor?

The number of cards does not matter. The same on 1 card. Two, four. Connecting the monitor also does not matter. It was working normally. It stopped working on all computers overnight. I am currently using lolminer and it works fine. But I'd rather go back to Phoenix Miner ... I just don't know how.

I'm mining ETC ...

Same problem with 280x 3gb, will anyone solve this??

Hello,
The same problem here with r9 280/280x. Is there any solution?

[janding]

Hi

Suddenly @ 13:30 GMT+2 on the 22 of August, my PhoenixMiner reports error while mining ETC on 3 GB cards

GPU1: Starting up… (0)
GPU1: Generating etchash light cache for epoch #223
Listening for CDM remote manager at port 3335 in read-only mode
Eth: New job #7e8cde29 from eu-etc.hiveon.net:8888; diff: 5000MH
Eth: New job #778ea926 from eu-etc.hiveon.net:8888; diff: 5000MH
Light cache generated in 4.3 s (10.2 MB/s)
GPU1: Free VRAM: 2.966 GB; used: 0.018 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #223 (2.74) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.

As far as I knwo we are far ( 1 year ) from being at epoch so DAG file size is over 3 GB

Other miners continue to work properly ( e.g. : lolminer )

I use 5.7b but also tried with 5.4c

Any idea ?

I have the same problem, anyone found solution ?

one card in system? miner card connect to monitor?

The number of cards does not matter. The same on 1 card. Two, four. Connecting the monitor also does not matter. It was working normally. It stopped working on all computers overnight. I am currently using lolminer and it works fine. But I'd rather go back to Phoenix Miner ... I just don't know how.

I'm mining ETC ...

Same problem with 280x 3gb, will anyone solve this??

Hello,
The same problem here with r9 280/280x. Is there any solution?

I'm going to assume that you have done this ?

 -rvram  -1

If not, then do that.

[relax69]

Hello anyone can help me for thats problem.
Its my first try on windows 10 Pro 64



best regards

Zombie mode for mining ETH with 4G cards stopped working more than 6 months ago. Try mining ETC or other coins.

[list1999]

Hi

Suddenly @ 13:30 GMT+2 on the 22 of August, my PhoenixMiner reports error while mining ETC on 3 GB cards

GPU1: Starting up… (0)
GPU1: Generating etchash light cache for epoch #223
Listening for CDM remote manager at port 3335 in read-only mode
Eth: New job #7e8cde29 from eu-etc.hiveon.net:8888; diff: 5000MH
Eth: New job #778ea926 from eu-etc.hiveon.net:8888; diff: 5000MH
Light cache generated in 4.3 s (10.2 MB/s)
GPU1: Free VRAM: 2.966 GB; used: 0.018 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #223 (2.74) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.

As far as I knwo we are far ( 1 year ) from being at epoch so DAG file size is over 3 GB

Other miners continue to work properly ( e.g. : lolminer )

I use 5.7b but also tried with 5.4c

Any idea ?

I have the same problem, anyone found solution ?

one card in system? miner card connect to monitor?

The number of cards does not matter. The same on 1 card. Two, four. Connecting the monitor also does not matter. It was working normally. It stopped working on all computers overnight. I am currently using lolminer and it works fine. But I'd rather go back to Phoenix Miner ... I just don't know how.

I'm mining ETC ...

Same problem with 280x 3gb, will anyone solve this??

Hello,
The same problem here with r9 280/280x. Is there any solution?

I'm going to assume that you have done this ?

 -rvram  -1

If not, then do that.

There is only one solution to the problem so far - lolminer. hd7950 3Gb - 9,8 mh/s etc

[iStarbuck]

Does PhoenixMiner have any planned implementations of the LHR workarounds like NBminer has implemented that restores up to 70% of hashing power for ETH? I've been using PheonixMiner exclusively and though I've tried a few out I keep coming back, but even though my new LHR 3080 is pulling way more than my 1080 that I replaced in my main gaming rig, it hurts knowing that there's potentially so much performance left on the table when compared to NBminer. I've toyed with it but haven't gotten it to work so for time and sanity I'm keeping up with the 50% hash and what I know best.

[oleg_123]

Hi

Suddenly @ 13:30 GMT+2 on the 22 of August, my PhoenixMiner reports error while mining ETC on 3 GB cards

GPU1: Starting up… (0)
GPU1: Generating etchash light cache for epoch #223
Listening for CDM remote manager at port 3335 in read-only mode
Eth: New job #7e8cde29 from eu-etc.hiveon.net:8888; diff: 5000MH
Eth: New job #778ea926 from eu-etc.hiveon.net:8888; diff: 5000MH
Light cache generated in 4.3 s (10.2 MB/s)
GPU1: Free VRAM: 2.966 GB; used: 0.018 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #223 (2.74) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.

As far as I knwo we are far ( 1 year ) from being at epoch so DAG file size is over 3 GB

Other miners continue to work properly ( e.g. : lolminer )

I use 5.7b but also tried with 5.4c

Any idea ?

I have the same problem, anyone found solution ?

one card in system? miner card connect to monitor?

The number of cards does not matter. The same on 1 card. Two, four. Connecting the monitor also does not matter. It was working normally. It stopped working on all computers overnight. I am currently using lolminer and it works fine. But I'd rather go back to Phoenix Miner ... I just don't know how.

I'm mining ETC ...

Same problem with 280x 3gb, will anyone solve this??

Hello,
The same problem here with r9 280/280x. Is there any solution?

I'm going to assume that you have done this ?

 -rvram  -1

If not, then do that.

There is only one solution to the problem so far - lolminer. hd7950 3Gb - 9,8 mh/s etc

"-rvram -1" doesn't help. The error is still the same.

[dastardlyman12]

this is the config.txt from one of our rigs

-pool eu1.ethermine.org:4444
-wal  0xXXXXXXXXXXXXXXXXXXXXXXXXXXXX.chippy
-proto 3
-eworker chippy
-lidag 1
-gser 1
-acm
-tt -90
-amd
-dbg -1
-hstats 2
-cdm 0
-rmode 2
-ttli 65
-dagrestart 1
-gpus 12345

-mclock 1760,1760,1750,1760,2040
-cclock 1200,1200,920,940,1120
-cvddc 830,830,830,830,875
-mvddc 800,815,815,830,875
-mi 12,12,11,11,11

the rig is rx5700, rx5600, rx5500 and rx570
everything in the config.txt does something useful
the readme.txt provided with phoenix miner will tell you what all the things in the config.txt do.
anybody who doesn't understand should read the readme.txt
once you understand you can look at my config.txt and decide what is right for your amd rig

we have a lot of rigs .our main issue this summer has been heat -ttli have saved us from a lot of headaches
everything we have is bios modded and was dialed back at the start of summer so for instance this rig can run with vram faster
during the winter.
we use windows 10 ghost spectre on every rig. no updates no bloat no telemetry.
we use dwagent for remote access
and yes every rig is also on raptoreum or turtle or monero ocean
you can cpu mine without affecting ethereum hashrate at all.
do some tests find out what works. ive found that cpus with onboard graphics
like xeon e3-1245-v3 or i5 4440 can have all threads on raptoreum at cpu priority 1 without affecting eth hash .
cpus without onboard graphics like ryzen 3600 - you need to mine on 11 threads - keep one for phoenixminer.

read the readme.txt get knowledge
best wishes to the community
im dastardlyman on youtube and the same on discord.
my videos are out of date

[janding]

One of the most important items you mentioned was READ THE readme.txt FILE.
I see so many that do not read it and many times their issues would be solved if they just would
Read and Study that information. Read that info dozens of times and let it sink in. Then
read it again.

[FineJuice]

LHR improvements like nbminer would be lovely if possible.