Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 18. (Read 784985 times)

I have a potato Asus PCIe2.0 with a RX580 8g (I7 12g ram) (driver fixed)

I'm finally using W10 after 7 was only giving me 1/3 hash I should have for a year (yes, I'm stubborn)

now, I'm getting the 28+hash I should have had instead of 8-9 at least, but...

I'm on 5.9d AND 21.11.3, but still have to use ckernal 0 to get it to work and that gives me abt 7-10% stales!

Is this normal? Even with the low hash before I never had this high a stale rate, and didnt have to use the ck0 until recently (on my old miner version with no NEW win 7 updates or drivers this started happening out of the blue)

Thanks for any ideas or help!!

Sorry forgot to say it's Rx570 4GB mining ETC

maybe. what model card?

I'm back to mining after stopping for over 2 years, but I only getting max 14Mh/s hash tried modded bios and stock bios. Is this normal?
Edit: Sorry forgot to say it's Rx570 4GB mining ETC

The way to keep it from trying to put a new driver version back in is to go to device manager, go to display adapters, find yours, and then ROLL BACK to the previous driver version.   It won't update the driver again until there is a new version of Windows(going to Windows 10 or 11 22H1 for example).   My other question though, is why PhoenixMiner just breaks with new AMD driver versions.   If you intentionally install anything newer than Radeon Software 21.11.3 for RDNA 2 cards(including my Radeon 6800), the thing comes back with the unknown version issue and it won't mine without -clkernel 0.    So, is that a hardcoded "look for driver version" and then break as a result, because it should TRY to use the proper code path for these newer drivers, but it seems to be doing a fallback if it doesn't recognize the driver version.

Couple of days ago, my rigs stopped mining after a Windows Update, when the update replaced my AMD driver. In Device Manager, the driver is shown as 30.0.13023.1012. After restart, one of my rigs with newer GPUs is working fine with this driver, but my other rigs with Polaris cards are unstable or not working with it. I uninstalled this driver, DDU it, and installed the old drivers I had, disabled driver update in Windows Update, but that driver keeps coming back somehow. So check your driver version. I see yours and a couple more questions, are similar to my problem.

Also for your Radeon VII, read the first page of this treat. There were notes from the devs about specific drivers to use with Radeon Vega and Radeon VII.

Hello, I can't connect through the ssl protocol, how to set it up. can you help me? Thanks!

I have a rig with 6 x 6700s and 6 Nvidia cards. Windows 10 with latest updates

Has been working ok on 5.8 but has started causing me issues, generating errors on PM start:


No idea why, has been working and stable(ish) for months. Maybe windows update.

So, I thought it might be time to update, so updated gfx drivers and trying to update to 5.9d, but just starts and immediately exits 


Does the same on two of my other rigs, using both my config.txt and the default startminer.cmd


Am I missing something stupid?

Hi there,
Got the same error this morning when I woke up:
Tried adding -clkernel 0 - that worked, but noticed that avg hashrate dropped from 78-79 to 68-70
Updated the drivers to 21.10.2 and the miner from 5.5c to PhoenixMiner_5.9d_Windows.zip
Still doesn't work without -clkernel 0 and still loses around 10% of hashrate
Mining on my home gaming PC with Radeon VII, so "use linux" is not an option.
Config I'm using to keep the GPU a bit underutilized to avoid raping it to death:
This results in following temp/power which previously resulted in 78 avg hashrate:
Now it results in 64-70.

PC config:

• OS: Microsoft Windows [Version 10.0.19041.1415]
• GPU: Radeon VII with 21.10.2 drivers
• Miner: PhoenixMiner_5.9d_Windows.zip

Can anyone advise how to fix to avoid the requirement to use -clkernel 0 switch which apparently drops the hashrate?

PhoenixMiner doesn't support anything newer than 21.11.3.   I don't know if the drivers are so significantly different to cause this problem every three months, or if PM is just coded to look for specific driver versions and won't even TRY to use the AMD path with newer drivers than what it specifically looks for.   It's annoying, that's for sure.

Hey, thanks alot this got me running almost exactly at the wattage and MH/s i wanted. I believe i read in either the readme file or arguments page that you can set clocks per gpu. when my next card comes in a couple days I should specify GPU1 & GPU2 if i want them to run at different speeds. is it as simple as adding a parameter before what you gave me and then another after to specify the 2nd gpu, then simply adding the speeds for the 2nd?

Hey everyone! Hoping to troubleshoot a MATIC mining issue on my end. My graphic card( AMD Radeon RX 6600 XT ) is on the latest driver(22.1.1 released 1/7/2021 …10 days before this post). I seem to be running into an error and cannot move past 0Mh hashrate, along with the error no CUDA driver found, when using version “PhoenixMiner_5.9d_Windows”. I went downgrading version by version and had some success with version “PhoenixMiner_5.5c_Windows” with a 28.6Mh(people seem to be getting higher on newer versions) but thought I would at least illuminate the issue in hope to use a newer version 5.9. Not sure if this is impacting anyone else with an AMD Radeon RX 6600 XT for a graphics card, or because of the newer driver, but any help is appreciated!
-------------->MINER LOG START<--------------

Phoenix Miner 5.9d Windows/msvc - Release build
-----------------------------------------------

No CUDA driver found
Unknown OpenCL driver version! Hashrate and stale shares may suffer
OpenCL platform: OpenCL 2.1 AMD-APP (3354.13)
Available GPUs for mining:
GPU1: MSI AMD Radeon RX 6600 XT (pcie 9), OpenCL 2.0, 8 GB VRAM, 32 CUs
Eth: the pool list contains 1 pool (1 from command-line)
Eth: primary pool: etchash.unmineable.com:3333
Starting GPU mining
GPU1: AMD driver 22.1.1
Eth: Connecting to ethash pool etchash.unmineable.com:3333 (proto: EthProxy)
GPU1: 48C 0% 3W
GPUs power: 3.0 W
Eth: Connected to ethash pool etchash.unmineable.com:3333 (165.227.119.242)
Listening for CDM remote manager at port 60080 in read-only mode
Eth: New job #622207c1 from etchash.unmineable.com:3333; diff: 4000MH
GPU1: Starting up... (0)
GPU1: Generating etchash light cache for epoch #239
Light cache generated in 1.4 s (34.0 MB/s)
GPU1: Free VRAM: 7.922 GB; used: 0.063 GB
GPU1: Allocating DAG (2.88 GB); good for epoch up to #241
GPU1: Generating DAG for epoch #239
GPU1: DAG  24%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPU1: DAG  48%
GPU1: DAG  72%
GPU1: DAG  96%
GPU1: DAG generated in 6.4 s (457.8 MB/s)
GPU1: Using Ethash OCL kernels (gfx1032; -clkernel 1 -clnew 0)
GPU1: no -gt value specified, switching to auto-tune
GPU1: starting auto-tune process
GPU1: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00






Phoenix Miner 5.9d Windows/msvc - Release build
-----------------------------------------------

Waiting 15 s for previous instance to close



-------------->MINER LOG END<--------------

Forget about Afterburner and AMD's wattman. Just add -mt 1, -cclock 1000, -cvddc 670, -mclock 2150 for beginning. Test these numbers in 24 hours for stability. If runs stable, change 1 parameter by 10 and test for 24 hours. After you find the best value for this parameter, repeat the same with the next one.

---

First, please move the log file to a Code window.
I remember more than a year ago when 4G GPU's was about to phase out on ETH, my Nvidia cards stopped mining 2-3 months before my AMD cards. Then just before the AMD GPU's ran out of memory and stoped mining, was invented :


But I think this worked on AMD cards only. Check in the readme file if there is a solution for Nvidia.

 Sorry, but maybe is time for you to switch to another coin or upgrade the GPUs.

Hi all,

I posted this question couple of days before, but was deleted. I wonder why, since it's fully on-topic, and perhaps a simptom of a problem woth PhoenixMiner (or it's just me, but the question is honest).
Well, the cas is  I got an out of memory problem mining ETC (eth classic) with my 3GB nVidia GTX1060, since a couple of days ago.
Coincidentally with change to epoch #238 (5.9d say's to be good up to epoch #240 and 3gb cards should be able to mine etc until june/22 or so).
Any one with the same issue?

This is the command line:
./PhoenixMiner -pool us1-etc.ethermine.org:4444 -wal 0xblablabla -worker myworker -pass x -coin etc

This is the output:
Phoenix Miner 5.9d Linux/gcc - Release build
--------------------------------------------

CUDA version: 11.0, CUDA runtime: 8.0
NVML library initialized
Nvidia driver version: 470.86
OpenCL driver version: 20.40-1147287
Available GPUs for mining:
GPU1: ASUS NVIDIA GeForce GTX 1060 3GB (pcie 1), CUDA cap. 6.1, 3 GB VRAM, 9 CUs

GPU2: ASUS NVIDIA GeForce GTX 1060 3GB (pcie 2), CUDA cap. 6.1, 3 GB VRAM, 9 CUs

Eth: the pool list contains 1 pool (1 from command-line)
Eth: primary pool: us1-etc.ethermine.org:4444
Starting GPU mining
Eth: Connecting to ethash pool us1-etc.ethermine.org:4444 (proto: EthProxy)
GPU1: 35C 26% 7W, GPU2: 36C 27% 40W
GPUs power: 47.1 W
Eth: Connected to ethash pool us1-etc.ethermine.org:4444 (172.65.245.119)
Listening for CDM remote manager at port 3333 in read-only mode
Eth: New job #e801904e from us1-etc.ethermine.org:4444; diff: 4000MH
GPU1: Starting up... (0)
GPU1: Generating etchash light cache for epoch #238
GPU2: Starting up... (0)
Eth: New job #764e3116 from us1-etc.ethermine.org:4444; diff: 4000MH
Light cache generated in 2.0 s (22.7 MB/s)
GPU2: Allocating DAG (2.87) GB; good for epoch up to #240
GPU2: Generating DAG for epoch #238
GPU1: Allocating DAG (2.87) GB; good for epoch up to #240
CUDA error in CudaProgram.cu:393 : out of memory (2)
GPU1: CUDA memory: 2.95 GB total, 2.87 GB free
GPU1 initMiner error: out of memory
Fatal error detected. Restarting.
GPU2 initMiner error: Unable to initialize CUDA miner
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0)

Hope somebody could help, and thanks in advance for any hint,

use wattman for oc 6600s. Runs perfectly and i liked this : you dont need undervolt anymore you just decrease core clock to 1100mhs for example it is automaticaly undervolts the core.then hit fast memory and hit memory oc to the end and enjoy 51watts

Im using a rx 6600 xt hellhound, and the only way i can get it above 30 MH/s is without touching MSI afterburner. because i cant tune it, it is pulling 105w instead of what i hopped to be around 55.

Anytime I touch afterburner and try to open phoenix miner my DAG refuses to download & after a minute or two of mining @ 0 MH/s the whole computer freezes and i have to restart.

Any idea on what could be the issue here? I have the latest AMD drivers. I do not have the newest version of afterburner though, could that be a problem?

is there a parameter i should put in my bat or config files that could fix this? I currently only have the basics, my pools, wallet/name, proto 3, & cdm1.

[phoenix hiveos error, zetpool]

Hello, We found an issue during connecting to the zetpool, hiveos. Please fix? Any ideas?


Error:
GPU2: DAG  80%
Eth: New job #7f8641c5 from eth.zetpool.org:8005; diff: 4400MH
GPU3: DAG  72%
GPU4: DAG  66%
GPU1: DAG  59%
GPU2: DAG  87%
GPU3: DAG  80%
GPU1: DAG  66%
GPU4: DAG  72%
GPU2: DAG  95%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00                                                                               
GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0)                                                   
GPU1: 34C 49% 18W, GPU2: 37C 49% 46W, GPU3: 33C 49% 46W, GPU4: 34C 49% 44W                                                     
GPUs power: 154.0 W                                                                                                             
GPU3: DAG  87%                                                                                                                 
GPU4: DAG  80%                                                                                                                 
GPU1: DAG  72%                                                                                                                 
GPU2: DAG generated in 21.4 s (222.4 MB/s)                                                                                     
GPU2: Unable to prepare kernels: clCreateKernel (-46)                                                                           
Fatal error detected. Restarting.                                                                                               
Eth: New job #688897ef from eth.zetpool.org:8005; diff: 4400MH                                                                 
> Sending danger with payload to http://api.hiveos.farm
OK
phoenixminer exited (exitcode=1), waiting to cooldown a bit

How to restart Phoenixminer automatically after wifi is down?
I mine ETH with 2 x 3060ti using PhoenixMiner on Windows. I recently installed 1.1 kVA UPS as power cuts are frequent in my locality. When the power goes down, central WiFi of home is also down so no shares are received but GPUs run at full power (130 W each). This causes UPS to go down in approximately 5 minutes. However if miner gets restarted then GPUs consumed 20 W each and load on UPS is much less. This can extend UPS backup by 20-25 minutes.

Therefore, I want to tweak miner such that if no connection is there, miner should automatically restart after 30 second or something. I have been searching online but no such command line found so far. Explained my case so that any alternative may also be suggested. Please comment what can be done in this case?

I found out how to, spent few hours on it, I have started developing a monitoring program as a hobby and the way claymore have done this to work was insane, he was indeed crazy. Anyway, if you want to know more send me a PM, it will be fun to know, trust me ehhe

I guess you created this account only to know this, 2 posts.

I know what is the mods role and why we need them. I appreciate their work for us, but instead of acting like robots and taking action automatically, they need to read the content and decide what to do as humans.

For example, if I have a problem and ask for help, when I come back a few hours later, to seek for solution, probably I won't have time to read all the content after my posting, and will like to go directly to the possible answers.