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

[adaseb]

Hi all I am New in this Forum Very Helpfull Forum Sry for my english it is not Good.
Dear PhoenixMiner Need your Help I have one Ring With 4 Gpu 2 RX 570 4GB & 2 RX 570 8 GB.
2 gpu Rx 570 4 gb before some days have 27-28MHs Now have 19Mhs Already Check
With PhoenixMiner_5.4b , PhoenixMiner_5.2a , PhoenixMiner_5.2b , PhoenixMiner_5.2c , PhoenixMiner_5.2e With AMD driver 20.5.1 All Have Enable Compute Mode

My Line is This Have Something Wrong ?
PhoenixMiner.exe -pool ssl://eth-eu1.nanopool.org:9433 -wal (HIDE) -amd -gt 15 -amd -rmode 2 -clkernel 1,3,3,1 -rxboost 1 -eres 0,2,2,0 -dagrestart 1 -daglim 1 -rvram -1,384,384,-1 -tt 53 -tstop 75

Already Use PhoenixMiner_5.2e With AMD driver 20.5.1
Eth speed: 101.053 MH/s, shares: 1/0/0, time: 0:01
main GPUs: 1: 19.430 MH/s (0) 2: 30.038 MH/s (0) 3: 32.162 MH/s (0) 4: 19.423 MH/s (1)
My Results Have any opinion Please For Fix 2 Cards Again to go to 27-28 Mhs?
Thanks A lot Guys Have A nice to meet you all...

It’s because your 4GB are reaching the dag limit on ETH. Basically you have 2 more days on epoch 381 and when epoch 382 will start they will no longer be able to mine at all. There is another miner that if you search lets you mine for another month or two but I don’t want to mention in this thread since it’s not phoenixminer specific.

I would just however remove those 2 GPUs from the rig and sell them on Craigslist. Then add some money and buy an 8gb version and you will get your 30mhs speed back. Nothing else to do. You can mine etc at half the profit however I don’t think you want to do that.

[1714118317]

1714118317

[1714118317]

1714118317

[1714118317]

1714118317

[1714118317]

1714118317

[1714118317]

1714118317

[Biterion]

I am very happy to see that there are new updates.
I'm going to try now and hope my rig can run mining again


update:

holaaaaa...
after 10 days left my RIG can't run with PM,
now with new update driver and PM its running without problem Allocating buffers failed with: clCreateBuffer (-61).

now run:
https://i.postimg.cc/VNxPgpZ0/Screenshot-3.jpg

thank you @PhoenixMiner

have done new install on my second (last) RIG
win10
AMD 20.5.1 driver                                             >>> for 1x RX480 PC 8Gb, 2X R9 390 HIS 8Gb
385.41-desktop-win10-64bit-international-whql      >>> for 3X EVGA P106-100 6Gb (mining version)
all in stock bios
atikmdag-patcher-1.4.8
AMD-Compute-Switcher


pic:
https://i.postimg.cc/kXh4ctfz/Screenshot-3a.jpg


watching for 24 hour to check

update:

my second RIG having problem with new setting
GPU 1 at first try my RX480 get 26mhs... now drop to 9 mhs
GPU 1,2,3 stop at random after a few minute after run and miner crash
try with other miner i get GPU 1 run normaly speed at 26Mhs without crash

my other rig with same setting run normaly after 9-10 hour

maybe there are new BUG from Phoenixminer 5.4b....??

first tes:
https://i.postimg.cc/kXh4ctfz/Screenshot-3a.jpg

after crash (logfile):
https://i.postimg.cc/wjyqDcMb/stop.jpg

[duplj30]

The new beta version is ready. You can download PhoenixMiner 5.4b

Some notes on the best (or at least some of the better) drivers for AMD cards:

• If you have 6GB or 8GB card that is at least Polaris (i.e. 470/480/570/580, Vega, Radeon VII, Navi), you should run at least driver 20.5.1 under Windows 10, or driver 20.10.x under Linux.
• If you have 4GB Polaris card (i.e. 470/480/570/580), ideally you should also run drivers 20.5.1 or later. At the very least the drivers should be either 18.12.1.1 to 19.7.5 (inclusive), or 19.12.2 and later. Under Linux, drivers 19.x.x or 20.x.x should be OK for 4GB cards.
• Avoid using the 20.40.x, and 20.45.x drivers under Linux.

Please let us know if you have any problems or questions related to PhoenixMiner 5.4b.

thx, the speed has slightly increased by 30-50 hashes (driver 20.5.1), and the power consumption has slightly decreased (RX580/5700)

[duplj30]

How are people overclocking and undervolting Navi gpus on Windows using PhoenixMiner_5.4b and windows driver 20.12.1 ?

OverdriveNTool doesn't work past 20.4.2 , and using the miner params '-cclock 1030 -cvddc 700' doesn't work either. 

using 'cclock' and 'cvddc' , the logs show:
2020.12.12:18:55:57.470: hwmc GPU0: set GPU clocks to 1030 MHz (Vddc 700 mV)

however, checking gpuz or hwinfo or even in the miner itself (hstats 2), none of the OC values are actually applied. 

use version OverdriveNTool 2.9 it works successfully on drivers version 20.5.1
https://forums.guru3d.com/threads/overdriventool-tool-for-amd-gpus.416116/

[Biterion]

I am very happy to see that there are new updates.
I'm going to try now and hope my rig can run mining again


update:

holaaaaa...
after 10 days left my RIG can't run with PM,
now with new update driver and PM its running without problem Allocating buffers failed with: clCreateBuffer (-61).

now run:
https://i.postimg.cc/VNxPgpZ0/Screenshot-3.jpg

thank you @PhoenixMiner

have done new install on my second (last) RIG
win10
AMD 20.5.1 driver                                             >>> for 1x RX480 PC 8Gb, 2X R9 390 HIS 8Gb
385.41-desktop-win10-64bit-international-whql      >>> for 3X EVGA P106-100 6Gb (mining version)
all in stock bios
atikmdag-patcher-1.4.8
AMD-Compute-Switcher


pic:
https://i.postimg.cc/kXh4ctfz/Screenshot-3a.jpg


watching for 24 hour to check

update:

my second RIG having problem with new setting
GPU 1 at first try my RX480 get 26mhs... now drop to 9 mhs
GPU 1,2,3 stop at random after a few minute after run and miner crash
try with other miner i get GPU 1 run normaly speed at 26Mhs without crash

my other rig with same setting run normaly after 9-10 hour

maybe there are new BUG from Phoenixminer 5.4b....??

first tes:
https://i.postimg.cc/kXh4ctfz/Screenshot-3a.jpg

after crash (logfile):
https://i.postimg.cc/wjyqDcMb/stop.jpg

update:

uninstall AMD 20.5.1 driver with latest DDU
new clean install AMD driver 20.12.1
atikmdag-patcher-1.4.8
AMD-Compute-Switcher

yeah... !! after 1 hour running without crash  

pic :
https://i.postimg.cc/x129kscf/Screenshot-1.jpg

still watching for 24 hour to check

[UselessGuru]

I doubt that 5700 will stay stable at 90w giving 54mhs ok lets say it is stable at 90w giving you.

Enough proof?

https://imgur.com/a/Gyv7gko

Could you please post all your clock & voltage settings? TIA

[batsonxl]

I doubt that 5700 will stay stable at 90w giving 54mhs ok lets say it is stable at 90w giving you.

Enough proof?

https://imgur.com/a/Gyv7gko

Could you please post all your clock & voltage settings? TIA

he will not post that. also he has bios modified. Dude i said ok lets say it is stable. besides i dont believe wattage that miner and gpu-z shows because one of my rx480 shows 62watts and hashing at 31mhs which impossible 62w.

[PhoenixMiner]

is there a fix for

Allocating buffers failed with: clCreateBuffer (-61).

 ?

   We only see this error with Hawaii cards (R9 290/390). If you have other (newer) cards and still see the problem, please let us know the PhoenixMiner version, the AMD driver version, and the exact type of the cards. Also at least part of the log file will be helpful, including the error and one-two screens before that.

HiveOS  latest build 181 10-12-2020, AMD drivers 19.50
Rig of 4 Radeons, first one 580 8GB (with display interface), others 470 4GB

command line - used "even"
-daglim 1 -eres 0 -rvram -1 -rmode 0

It started on 2nd december (epoch 379?) and here in the forum were other complaints from Polaris users.
log:

Code:

2020.12.12:15:43:47.097: main Phoenix Miner 5.3b Linux/gcc - Release build
2020.12.12:15:43:47.097: main Cmd line: -epool ru-eth.hiveon.net:4444 -ewal 0xe9.RX470 -epsw x -coin eth -cclock 1040 -cvddc 970 -mclock 1950 -tt 74 -daglim 0 -rmode 0 -wd 0 -eres 0 -rvram -1 
2020.12.12:15:43:47.100: main Unable to enum CUDA GPUs: no CUDA-capable device is detected
2020.12.12:15:43:47.279: main Unknown OpenCL driver version! Hashrate and stale shares may suffer
2020.12.12:15:43:47.279: main OpenCL platform: OpenCL 2.1 AMD-APP (3004.6)
2020.12.12:15:43:47.279: main Available GPUs for mining:
2020.12.12:15:43:47.279: main GPU1: Radeon RX 580 Series (pcie 1), OpenCL 1.2, 8 GB VRAM, 36 CUs
2020.12.12:15:43:47.279: main GPU2: AMD Radeon (TM) RX 470 Graphics (pcie 2), OpenCL 1.2, 4 GB VRAM, 32 CUs
2020.12.12:15:43:47.279: main GPU3: AMD Radeon (TM) RX 470 Graphics (pcie 4), OpenCL 1.2, 4 GB VRAM, 32 CUs
2020.12.12:15:43:47.279: main GPU4: Radeon RX 570 Series (pcie 5), OpenCL 1.2, 4 GB VRAM, 32 CUs
2020.12.12:15:43:47.280: main AMD sysfs monitor initialized
2020.12.12:15:43:47.280: main Eth: Loading pools from epools.txt
2020.12.12:15:43:47.280: main Eth: the pool list contains 5 pools (1 from command-line)
2020.12.12:15:43:47.280: main Eth: primary pool: ru-eth.hiveon.net:4444
2020.12.12:15:43:47.280: main Starting GPU mining
2020.12.12:15:43:47.280: main GPU1: fan PWM control mode 2, min 0, max 255
2020.12.12:15:43:47.280: main GPU2: fan PWM control mode 2, min 0, max 255
2020.12.12:15:43:47.280: main GPU3: fan PWM control mode 2, min 0, max 255
2020.12.12:15:43:47.280: main GPU4: fan PWM control mode 2, min 0, max 255
2020.12.12:15:43:47.330: hwmc GPU1: set auto fan: 74C target temp (min fan 0, max fan 100)
2020.12.12:15:43:47.331: hwmc GPU2: set auto fan: 74C target temp (min fan 0, max fan 100)
2020.12.12:15:43:47.331: hwmc GPU3: set auto fan: 74C target temp (min fan 0, max fan 100)
2020.12.12:15:43:47.331: hwmc GPU4: set auto fan: 74C target temp (min fan 0, max fan 100)
2020.12.12:15:43:47.381: main Eth: Connecting to ethash pool ru-eth.hiveon.net:4444 (proto: EthProxy)
2020.12.12:15:43:47.382: main GPU1: 49C 21% 37W, GPU2: 27C 20% 19W, GPU3: 25C 24% 13W, GPU4: 29C 34% 36W
GPUs power: 105.6 W
2020.12.12:15:43:47.482: eths Eth: Connected to ethash pool ru-eth.hiveon.net:4444 (185.22.235.97)
2020.12.12:15:43:47.482: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0xe9.RX470","x"]}

2020.12.12:15:43:47.553: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2020.12.12:15:43:47.553: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
...

2020.12.12:15:43:47.629: GPU1 GPU1: Starting up... (0)
2020.12.12:15:43:47.630: GPU1 GPU1: Generating ethash light cache for epoch #381
2020.12.12:15:43:47.630: GPU2 GPU2: Starting up... (0)
2020.12.12:15:43:47.630: GPU3 GPU3: Starting up... (0)
2020.12.12:15:43:47.630: GPU4 GPU4: Starting up... (0)
2020.12.12:15:43:49.078: eths Eth: Received: 
2020.12.12:15:43:49.078: eths Eth: New job #ae9927c8 from  diff: 5000MH
2020.12.12:15:43:51.029: GPU1 Light cache generated in 3.4 s (18.7 MB/s)
2020.12.12:15:43:51.164: GPU1 GPU1: Free VRAM: 7.960 GB; used: 0.019 GB
2020.12.12:15:43:51.172: GPU1 GPU1: Allocating DAG for epoch #381 (3.98) GB
2020.12.12:15:43:51.173: GPU1 GPU1: Allocating buffers failed with: clCreateBuffer (-61).
2020.12.12:15:43:51.173: GPU1 Fatal error detected. Restarting.
2020.12.12:15:43:51.300: GPU2 GPU2: Free VRAM: 3.968 GB; used: 0.019 GB
2020.12.12:15:43:51.308: GPU2 GPU2: Allocating DAG for epoch #381 (3.98) GB
2020.12.12:15:43:51.308: GPU2 GPU2: Allocating buffers failed with: clCreateBuffer (-61).
2020.12.12:15:43:51.435: GPU3 GPU3: Free VRAM: 3.968 GB; used: 0.019 GB
2020.12.12:15:43:51.438: GPU3 GPU3: Allocating DAG for epoch #381 (3.98) GB
2020.12.12:15:43:51.439: GPU3 GPU3: Allocating buffers failed with: clCreateBuffer (-61).
2020.12.12:15:43:51.582: GPU4 GPU4: Free VRAM: 3.968 GB; used: 0.019 GB
2020.12.12:15:43:51.582: GPU4 GPU4: Allocating DAG for epoch #381 (3.98) GB
2020.12.12:15:43:51.582: GPU4 GPU4: Allocating buffers failed with: clCreateBuffer (-61).

   Thank you for the amazing bug report! This is exactly how it is done The problem is here: Unknown OpenCL driver version! Hashrate and stale shares may suffer - this means that the miner can't recognize the driver and is forced to use the generic kernels, which doesn't support most DAG configs. The quick fix is to upgrade to driver 20.10-1048554 or downgrade to driver 19.50-967956. We suspect that you are using driver 19.50-1011208, which is not supported because somehow it "fell through the cracks" and was never even tested. We will add support for it in the 5.4c for sure.

I'm bashing my head against the wall, guys. Like what am I doing wrong?
The miner just won't start, instead, that's what I'm getting:

Code:

C:\Users\Admin\Downloads\PhoenixMiner_5.3b_Windows>PhoenixMiner.exe -nvidia -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0xAA478d95b2Ff426712fC5003404D0B6f4CEaBd4C.Rig0 -coin etc
Phoenix Miner 5.3b Windows/msvc - Release build
-----------------------------------------------
CUDA version: 11.0, CUDA runtime: 8.0
Available GPUs for mining:
GPU1: GeForce GTX 1070 (pcie 9), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU2: GeForce GTX 1070 (pcie 10), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
C:\Users\Admin\Downloads\PhoenixMiner_5.3b_Windows> 

Honestly tried googling, found nothing.
Win10 2004, latest NVidia drivers (downloaded and installed today)

   The problem is with the drivers - here is how to fix it.

Hi all I am New in this Forum Very Helpfull Forum Sry for my english it is not Good.
Dear PhoenixMiner Need your Help I have one Ring With 4 Gpu 2 RX 570 4GB & 2 RX 570 8 GB.
2 gpu Rx 570 4 gb before some days have 27-28MHs Now have 19Mhs Already Check
With PhoenixMiner_5.4b , PhoenixMiner_5.2a , PhoenixMiner_5.2b , PhoenixMiner_5.2c , PhoenixMiner_5.2e With AMD driver 20.5.1 All Have Enable Compute Mode

My Line is This Have Something Wrong ?
PhoenixMiner.exe -pool ssl://eth-eu1.nanopool.org:9433 -wal (HIDE) -amd -gt 15 -amd -rmode 2 -clkernel 1,3,3,1 -rxboost 1 -eres 0,2,2,0 -dagrestart 1 -daglim 1 -rvram -1,384,384,-1 -tt 53 -tstop 75

Already Use PhoenixMiner_5.2e With AMD driver 20.5.1
Eth speed: 101.053 MH/s, shares: 1/0/0, time: 0:01
main GPUs: 1: 19.430 MH/s (0) 2: 30.038 MH/s (0) 3: 32.162 MH/s (0) 4: 19.423 MH/s (1)
My Results Have any opinion Please For Fix 2 Cards Again to go to 27-28 Mhs?
Thanks A lot Guys Have A nice to meet you all...

It’s because your 4GB are reaching the dag limit on ETH. Basically you have 2 more days on epoch 381 and when epoch 382 will start they will no longer be able to mine at all. There is another miner that if you search lets you mine for another month or two but I don’t want to mention in this thread since it’s not phoenixminer specific.

I would just however remove those 2 GPUs from the rig and sell them on Craigslist. Then add some money and buy an 8gb version and you will get your 30mhs speed back. Nothing else to do. You can mine etc at half the profit however I don’t think you want to do that.

    PhoenixMiner will also work after epoch 381 but with speed decreasing with each DAG epoch - we also support "zombie" mode, we just do not call it this way (you need PhoenixMiner 5.2e or later for it to work). There is no "magic" that will keep 4GB cards working with the same hashrate as simply the DAG is becoming too big. Depending on the hashrate loss, you may be better of mining ETC with the 4GB AMD GPUs.






IMPORTANT! The latest Nvidia drivers for Windows 10 460.79 cause crash when PhoenixMiner starts. The problem is caused by a corrupted DLL file that is installed by the driver. You can see how to fix this problem in this post (it is an easy and quick fix).

[restless]

   Thank you for the amazing bug report! This is exactly how it is done The problem is here: Unknown OpenCL driver version! Hashrate and stale shares may suffer - this means that the miner can't recognize the driver and is forced to use the generic kernels, which doesn't support most DAG configs. The quick fix is to upgrade to driver 20.10-1048554 or downgrade to driver 19.50-967956. We suspect that you are using driver 19.50-1011208, which is not supported because somehow it "fell through the cracks" and was never even tested. We will add support for it in the 5.4c for sure.

thanks! updated to 20.30/latest from HiveOS/ it works again

[Nasareth]

Hi all I am New in this Forum Very Helpfull Forum Sry for my english it is not Good.
Dear PhoenixMiner Need your Help I have one Ring With 4 Gpu 2 RX 570 4GB & 2 RX 570 8 GB.
2 gpu Rx 570 4 gb before some days have 27-28MHs Now have 19Mhs Already Check
With PhoenixMiner_5.4b , PhoenixMiner_5.2a , PhoenixMiner_5.2b , PhoenixMiner_5.2c , PhoenixMiner_5.2e With AMD driver 20.5.1 All Have Enable Compute Mode

My Line is This Have Something Wrong ?
PhoenixMiner.exe -pool ssl://eth-eu1.nanopool.org:9433 -wal (HIDE) -amd -gt 15 -amd -rmode 2 -clkernel 1,3,3,1 -rxboost 1 -eres 0,2,2,0 -dagrestart 1 -daglim 1 -rvram -1,384,384,-1 -tt 53 -tstop 75

Already Use PhoenixMiner_5.2e With AMD driver 20.5.1
Eth speed: 101.053 MH/s, shares: 1/0/0, time: 0:01
main GPUs: 1: 19.430 MH/s (0) 2: 30.038 MH/s (0) 3: 32.162 MH/s (0) 4: 19.423 MH/s (1)
My Results Have any opinion Please For Fix 2 Cards Again to go to 27-28 Mhs?
Thanks A lot Guys Have A nice to meet you all...

It’s because your 4GB are reaching the dag limit on ETH. Basically you have 2 more days on epoch 381 and when epoch 382 will start they will no longer be able to mine at all. There is another miner that if you search lets you mine for another month or two but I don’t want to mention in this thread since it’s not phoenixminer specific.

I would just however remove those 2 GPUs from the rig and sell them on Craigslist. Then add some money and buy an 8gb version and you will get your 30mhs speed back. Nothing else to do. You can mine etc at half the profit however I don’t think you want to do that.

   PhoenixMiner will also work after epoch 381 but with speed decreasing with each DAG epoch - we also support "zombie" mode, we just do not call it this way (you need PhoenixMiner 5.2e or later for it to work). There is no "magic" that will keep 4GB cards working with the same hashrate as simply the DAG is becoming too big. Depending on the hashrate loss, you may be better of mining ETC with the 4GB AMD GPUs.






IMPORTANT! The latest Nvidia drivers for Windows 10 460.79 cause crash when PhoenixMiner starts. The problem is caused by a corrupted DLL file that is installed by the driver. You can see how to fix this problem in this post (it is an easy and quick fix).
[/quote]


Dear PhoenixMiner already use PhoenixMiner 5.2e with With AMD driver 20.5.1 How enable Zombie mode what must to be change in my line already have daglim -1 and working 4023

[ManuBBXX]

This post contains the instructions on how to fix the latest 460.79 Nvidia Windows driver. The reason for the problem is that one of the DLLs (nvml.dll) that the driver installs is corrupted. Here is what you have to do in order to fix the problem:

• Download nvml_460.79_win10.zip from here: https://mega.nz/#F!2VskDJrI!lsQsz1CdDe8x5cH3L8QaBw (MEGA)
  
  If you want to check the integrity of the downloaded file, please use the following hashes:

Code:

    File: nvml_460.79_win10.zip
    ---------------------------
   SHA-1: 749ae64e4a5044994bec61d6d94459aa4c4cc719
 SHA-256: 541ccdbd77c693d1de2919adab9eaa7e2b502c9ec2f722544002abbcf643539e
 SHA-512: 80562b59e0a4f3c47557abc8742d9af6b119102f6fecfb3aa38112084ba0edd06451a631f633b667d57ec0417eb0db551d4cc5df90e0b835bce212b3ee6b75ce
 

• Extract the file nvml.dll from the .zip archive you have downloaded in the previous step, and then copy it to the folder C:\Windows\System32. There will be a file with the same name here, so you have to overwrite it (you will be prompted by Windows are you sure, blah, blah, blah)

Note that this .dll is the original .dll from Nvidia (it is still digitally signed by them). If you are really paranoid, you can download 460.79 drivers from Nvidia, then use 7zip to open the .exe and extract the dll (you will find it at 460.79-desktop-win10-64bit-international-dch-whql.exe\Display.Driver\nvml.dll), and then copy it to the C:\Windows\System32 folder.

I can't extract the dll from archive to System32, win10 says file is already used by another process.
I killed nvidia controlPanel and MSI afterburner, but same result

Any ideas ?

[PhoenixMiner]

This post contains the instructions on how to fix the latest 460.79 Nvidia Windows driver. The reason for the problem is that one of the DLLs (nvml.dll) that the driver installs is corrupted. Here is what you have to do in order to fix the problem:

• Download nvml_460.79_win10.zip from here: https://mega.nz/#F!2VskDJrI!lsQsz1CdDe8x5cH3L8QaBw (MEGA)
  
  If you want to check the integrity of the downloaded file, please use the following hashes:

Code:

    File: nvml_460.79_win10.zip
    ---------------------------
   SHA-1: 749ae64e4a5044994bec61d6d94459aa4c4cc719
 SHA-256: 541ccdbd77c693d1de2919adab9eaa7e2b502c9ec2f722544002abbcf643539e
 SHA-512: 80562b59e0a4f3c47557abc8742d9af6b119102f6fecfb3aa38112084ba0edd06451a631f633b667d57ec0417eb0db551d4cc5df90e0b835bce212b3ee6b75ce
 

• Extract the file nvml.dll from the .zip archive you have downloaded in the previous step, and then copy it to the folder C:\Windows\System32. There will be a file with the same name here, so you have to overwrite it (you will be prompted by Windows are you sure, blah, blah, blah)

Note that this .dll is the original .dll from Nvidia (it is still digitally signed by them). If you are really paranoid, you can download 460.79 drivers from Nvidia, then use 7zip to open the .exe and extract the dll (you will find it at 460.79-desktop-win10-64bit-international-dch-whql.exe\Display.Driver\nvml.dll), and then copy it to the C:\Windows\System32 folder.

I can't extract the dll from archive to System32, win10 says file is already used by another process.
I killed nvidia controlPanel and MSI afterburner, but same result

Any ideas ?

Rename the existing nvml.dll in System32 to something else (e.g. nvml_old.dll) then copy the one from the archive in System32. After that restart Windows, and you should be able to delete the nvml_old.dll from System32.

[woodaxe]

with the dag being made smaller on the  etherium classic coin what hashrate  can i expect mining with a gtx 1060 3gb gpu

[miner1987]

Rename the existing nvml.dll in System32 to something else (e.g. nvml_old.dll) then copy the one from the archive in System32. After that restart Windows, and you should be able to delete the nvml_old.dll from System32.

Please add support for DAG epoch above 500 because I'll be calm and other mining programs have already done so.

+1
  Phoenix may stop mining after a certain amount of time, as it did with Claymore Miner.
Better to add large DAG support in advance.

[wtfonly16]

why some website that report 4gb card were almost 50% less are now almost as fast as etcHash ? Which miner do this now? it not phoenix cause it poor hashrate.

[ManuBBXX]

This post contains the instructions on how to fix the latest 460.79 Nvidia Windows driver. The reason for the problem is that one of the DLLs (nvml.dll) that the driver installs is corrupted. Here is what you have to do in order to fix the problem:

• Download nvml_460.79_win10.zip from here: https://mega.nz/#F!2VskDJrI!lsQsz1CdDe8x5cH3L8QaBw (MEGA)
  
  If you want to check the integrity of the downloaded file, please use the following hashes:

Code:

    File: nvml_460.79_win10.zip
    ---------------------------
   SHA-1: 749ae64e4a5044994bec61d6d94459aa4c4cc719
 SHA-256: 541ccdbd77c693d1de2919adab9eaa7e2b502c9ec2f722544002abbcf643539e
 SHA-512: 80562b59e0a4f3c47557abc8742d9af6b119102f6fecfb3aa38112084ba0edd06451a631f633b667d57ec0417eb0db551d4cc5df90e0b835bce212b3ee6b75ce
 

• Extract the file nvml.dll from the .zip archive you have downloaded in the previous step, and then copy it to the folder C:\Windows\System32. There will be a file with the same name here, so you have to overwrite it (you will be prompted by Windows are you sure, blah, blah, blah)

Note that this .dll is the original .dll from Nvidia (it is still digitally signed by them). If you are really paranoid, you can download 460.79 drivers from Nvidia, then use 7zip to open the .exe and extract the dll (you will find it at 460.79-desktop-win10-64bit-international-dch-whql.exe\Display.Driver\nvml.dll), and then copy it to the C:\Windows\System32 folder.

I can't extract the dll from archive to System32, win10 says file is already used by another process.
I killed nvidia controlPanel and MSI afterburner, but same result

Any ideas ?

Rename the existing nvml.dll in System32 to something else (e.g. nvml_old.dll) then copy the one from the archive in System32. After that restart Windows, and you should be able to delete the nvml_old.dll from System32.

Works like a charm !
Now I'm able to mine with latest driver with my 3060TI's rig
Thanks chief

[Zofrea1]

Thanks for all the information and fixes to get the Miner working again on the latest Nvidia driver. I did want to point out one minor issue I see with it on the latest driver - setting and resetting the memclock doesn't seem to work anymore. I can't seem to set it as low, and it throws error 137 when trying to set the desired value and also when attempting to reset it upon closing the miner. Maybe some new jank with the new driver? This is on a 3090. I understand the 30 series isn't officially supported in the latest revision, but perhaps something to keep an eye on if Nvidia has started making new tweaks/changes in their drivers.

[STSMiner]

This post contains the instructions on how to fix the latest 460.79 Nvidia Windows driver. The reason for the problem is that one of the DLLs (nvml.dll) that the driver installs is corrupted. Here is what you have to do in order to fix the problem:

• Download nvml_460.79_win10.zip from here: https://mega.nz/#F!2VskDJrI!lsQsz1CdDe8x5cH3L8QaBw (MEGA)
  
  If you want to check the integrity of the downloaded file, please use the following hashes:

Code:

    File: nvml_460.79_win10.zip
    ---------------------------
   SHA-1: 749ae64e4a5044994bec61d6d94459aa4c4cc719
 SHA-256: 541ccdbd77c693d1de2919adab9eaa7e2b502c9ec2f722544002abbcf643539e
 SHA-512: 80562b59e0a4f3c47557abc8742d9af6b119102f6fecfb3aa38112084ba0edd06451a631f633b667d57ec0417eb0db551d4cc5df90e0b835bce212b3ee6b75ce
 

• Extract the file nvml.dll from the .zip archive you have downloaded in the previous step, and then copy it to the folder C:\Windows\System32. There will be a file with the same name here, so you have to overwrite it (you will be prompted by Windows are you sure, blah, blah, blah)

Note that this .dll is the original .dll from Nvidia (it is still digitally signed by them). If you are really paranoid, you can download 460.79 drivers from Nvidia, then use 7zip to open the .exe and extract the dll (you will find it at 460.79-desktop-win10-64bit-international-dch-whql.exe\Display.Driver\nvml.dll), and then copy it to the C:\Windows\System32 folder.

I can't extract the dll from archive to System32, win10 says file is already used by another process.
I killed nvidia controlPanel and MSI afterburner, but same result

Any ideas ?

Rename the existing nvml.dll in System32 to something else (e.g. nvml_old.dll) then copy the one from the archive in System32. After that restart Windows, and you should be able to delete the nvml_old.dll from System32.

@PhoenixMiner,

This fix does not work for me using Awesome Miner with the latest drivers, PhoenixMiner app still crashes out, had to revert back to 457.51 drivers.

[Deafran]

Hello! Does Phoenixminer support the "zombie mode" which is implemented in another miners (like lolminer) so we will be able to mine with reduced speed even in early January 2021? I just upgraded from 5.1 to 5.3b using Linux (Ethos) and speed reduced from 28.5 MH to 26.5 MH per one 570RX 4GB card... Any solution for this how? Thanks a lot for your help!!

it happens to me to, see here ...
https://bitcointalk.org/index.php?topic=2647654.msg55800987#msg55800987


may i know your local config in ethos  pls

[oskoa]

Hello, ive a rig with 5 Cards (RX 570/470 all) and only the first main is 8 GB (the rest 4)

With rxboost 1 (or the vm comand in the correct number) without -Power + OC) i had in the past (before, in 2020 start) 26K in the main card, and 24/22/24/23 Mhz in the 4gb cards). Since the Epoch 384 and the last version of phonix, i have a lot fallen of hash rate (the 8 GB card no problem) but the rest 4 gb, all in 16K average.

I already read this was possible, so hard the fallen? can i do anything with some command?