Hey all, I have a problem with Phoenix Miner. Every time it gets to the devfee part it gets stuck and won't do anything at that point anymore and I'm forced to manually restart the miner to get it working again. I'm using Phoenix Miner on Windows 10 and Nvidia 1000 and 2000 series cards with the latest drivers.
Not sure if this is important, but my .bat-file only contains this basic info (excluded the addresses):
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
PhoenixMiner.exe -pool <pool address> -worker <worker name> -wal <wallet address> -pass x -proto 4 -stales 0
And this is what's typically the latest on the miner window when it gets stuck:
DevFee: Connecting to ethash pool us2.ethermine.org:14444 (proto: EthProxy)
DevFee: Connected to ethash pool us2.ethermine.org:14444 (172.65.226.101)
DevFee: New job #060677c5 from us2.ethermine.org:14444; diff: 4000MH
Otherwise the miner is working fine without any problems.
EDIT: There's one other thing. It also does the devfee process very often, like every 15-20 mins or so. It varies, but much more often it's supposed to do it. I think it was 90 mins. intervals it's supposed to do it and for like 30-40 secs.
I
This is very strange. Make sure that you are using the real version (with the correct checksums). If this doesn't help, send us full log file for at least several hours, not just several lines.
Yeah same with me. Im also getting 35-36 and the straps option isnt helping.
Actually I noticed, that the miner reports something like this: In order to set straps you need to run phoenix miner as administrator. But when I try to run the .bat file as administrator the window closes immediately and nothing happens. Is there a solution to this? Thanks!
If you run the .bat file as administrator, it always starts in
C:\Windows\System32 and the PhoenixMiner.exe is not there, so it fails to start. There are two ways to fix the problem:
- Put your command-line options in the config.txt file, and then run as administrator the PhoenixMiner.exe itself.
- Or, edit your .bat file by adding a command to change the folder to where your PhoenixMiner.exe is. For example (assuming that PhoenixMiner is at C:\Miners\PhoenixMiner_5.5c):
cd C:\Miners\PhoenixMiner_5.5c
PhoenixMiner.exe -pool xxx -wal xxx ....
pause
hello, why do i get this error when i want to clock my memory?
GPU1: Unable to set memory clock delta to +1000 MHz - error -137
and what are the settings for a 3080? because I only have 70mh on my 3080?
thank you
This error is shown when the miner is not run as administrator. All recent Nvidia drivers do not allow programs to change the clocks unless they are run as administrator. See the answer to the question above on how to run PhoenixMiner as administrator.
Tnx. I will check the data and the logfiles.
When I run the miner in the console as far as I know it always starts with the card names.. (which GPU are found for mining) In this list it shows 6 times the same (type) cards RX 580
I even had fitted the RX 5700 as a single available GPU, but then I get the miner error "NO GPU for mining"
Is there any known hardware limit for getting the RX 5700 XT's to work in Phoenixminer, e.g. minimum of RAM used, or anything else, which we might have overlooked?
The rig is fitted with only 4 Gb RAM. (We use the Asrock H110 BTC Pro+ mobo)
Perhaps the driver version may be the issue. Do not use the latest AMD Linux drivers for anything other than RX6000 AMD cards.
Well we tried a different (lower version) driver but then we had to change the kernel and still it didnt want to see the 5700 and the additions in the setting didnot seem to work, so this morning I changed to Win10 and we did see all the different cards.. and even the card settings in the confiig file (the RX*580:1160) did work. But we had the 21.1.1 drivers installed and it was not stable. So I uninstalled these and installed the 20.11.
and forced the compute mode via the AMD driver software, but I do not get it stable after a few minutes I get black screens and AMD report of a driver issue and then it all stops???
Probably one of the cards is unable to run at the clocks and voltages that are set. Check the log to see if the proper clocks and voltages are applied to each card - if there is a mix-up and the setting for 5700XT is applied to one of the Polaris cards, or vice versa, it may lead to almost instant crash. The last resort is to check the cards one by one using the
-gpus command-line option. If all are running fine by themselves, you may have issues with your power supply, or the cables to the extenders.