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

[thameur]

Hi
is there any news for hashrate drop R9 390 8g please

[1713507751]

1713507751

[sernos]

I also have more than 10 pieces R9 390 8g and have a problem with hashrate mining ETH

[thameur]

I also have more than 10 pieces R9 390 8g and have a problem with hashrate mining ETH

claymore fix this problem with RX 580/570/480/470, but they said they have no support R9 390 8g for the moment

[sxemini]

I also have more than 10 pieces R9 390 8g and have a problem with hashrate mining ETH

Dudes read, it is a normal very old problem. Why so many people ask this question this days?  
R9 290 and R9 390 have DAG issue. There is no fix for this, only mining Coins with lower DAG (CLO, ETHO)

I also have more than 10 pieces R9 390 8g and have a problem with hashrate mining ETH

claymore fix this problem with RX 580/570/480/470, but they said they have no support R9 390 8g for the moment

claymore fix this problem? XD no this problem where not fixed by claymore. It was a driver bug, and amd fixed this problem.

[thameur]

I also have more than 10 pieces R9 390 8g and have a problem with hashrate mining ETH

Dudes read, it is a normal very old problem. Why so many people ask this question this days?  
R9 290 and R9 390 have DAG issue. There is no fix for this, only mining Coins with lower DAG (CLO, ETHO)

I also have more than 10 pieces R9 390 8g and have a problem with hashrate mining ETH

claymore fix this problem with RX 580/570/480/470, but they said they have no support R9 390 8g for the moment

claymore fix this problem? XD no this problem where not fixed by claymore. It was a driver bug, and amd fixed this problem.

You think the RX 480/470 is not an old GPU too? Claymore has fix this DAG file problem

[pinamalina]

PM 4.1c with 13xAMD RX580-8GB Fails using turbo mode kernel (-clkernel 3)

Error - immediately following DAG load; always exactly the same error. Switch back to 4.0b works great.

019.01.16:09:06:46.114: GPU7 GPU7: Using Ethash OCL kernels (Ellesmere; -clkernel 3)
2019.01.16:09:06:46.355: GPU10 GPU10: DAG 100%
2019.01.16:09:06:46.480: GPU8 GPU8: DAG 100%
2019.01.16:09:06:47.111: GPU11 GPU11: DAG 100%
2019.01.16:09:06:47.154: GPU12 GPU12: DAG 100%
2019.01.16:09:06:47.160: GPU9 GPU9: DAG 100%
2019.01.16:09:06:47.410: main  
2019.01.16:09:06:47.410: main *** 0:00 *** 1/16 09:06 **************************************
2019.01.16:09:06:47.410: main Eth: Mining ETH on eu1.ethermine.org:4444 for 0:00
2019.01.16:09:06:47.410: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2019.01.16:09:06:47.410: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2019.01.16:09:06:47.410: main Eth: Average speed (5 min): 86.233 MH/s
2019.01.16:09:06:47.410: main  
2019.01.16:09:06:47.867: GPU12 GPU12: clEnqueueCopyBuffer (-4)
2019.01.16:09:06:47.984: GPU11 GPU11: clEnqueueCopyBuffer (-4)
2019.01.16:09:06:47.988: GPU8 GPU8: clEnqueueCopyBuffer (-4)
2019.01.16:09:06:48.140: GPU10 GPU10: DAG generated in 39.1 s (74.3 MB/s)
2019.01.16:09:06:48.141: GPU10 GPU10: Using Ethash OCL kernels (Ellesmere; -clkernel 3)
2019.01.16:09:06:48.178: GPU9 GPU9: DAG generated in 39.6 s (73.4 MB/s)
2019.01.16:09:06:48.179: GPU9 GPU9: Using Ethash OCL kernels (Ellesmere; -clkernel 3)
2019.01.16:09:06:48.206: GPU13 GPU13: DAG 100%
2019.01.16:09:06:48.229: main Eth speed: 107.135 MH/s, shares: 0/0/0, time: 0:00
2019.01.16:09:06:48.229: main GPUs: 1: 28.986 MH/s (0) 2: 25.954 MH/s (0) 3: 0.000 MH/s (0) 4: 28.715 MH/s (0) 5: 23.481 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0) 8: 0.000 MH/s (0) 9: 0.000 MH/s (0) 10: 0.000 MH/s (0) 11: 0.000 MH/s (0) 12: 0.000 MH/s (0) 13: 0.000 MH/s (0)
2019.01.16:09:06:48.277: wdog Thread(s) not responding. Restarting.
2019.01.16:09:06:48.409: GPU13 GPU13: clEnqueueCopyBuffer (-4)
2019.01.16:09:06:49.658: eths Eth: New job #b21615c5 from eu1.ethermine.org:4444; diff: 4000MH
2019.01.16:09:06:49.673: GPU8 GPU8: Starting up... (0)
2019.01.16:09:06:49.686: GPU11 GPU11: Starting up... (0)
2019.01.16:09:06:49.706: GPU12 GPU12: Starting up... (0)
2019.01.16:09:06:49.711: GPU13 GPU13: Starting up... (0)
2019.01.16:09:06:49.752: GPU8 GPU8: Allocating DAG (2x 2.85) GB; good for epoch up to #237
2019.01.16:09:06:49.752: GPU8 GPU8: Allocating light cache buffer (45.6) MB; good for epoch up to #237
2019.01.16:09:06:49.832: GPU11 GPU11: Allocating DAG (2x 2.85) GB; good for epoch up to #237
2019.01.16:09:06:49.832: GPU11 GPU11: Allocating light cache buffer (45.6) MB; good for epoch up to #237
2019.01.16:09:06:49.909: GPU12 GPU12: Allocating DAG (2x 2.85) GB; good for epoch up to #237
2019.01.16:09:06:49.909: GPU12 GPU12: Allocating light cache buffer (45.6) MB; good for epoch up to #237
2019.01.16:09:06:49.974: GPU8 GPU8: Generating DAG for epoch #235
2019.01.16:09:06:49.982: GPU8 GPU8: clEnqueueNDRangeKernel (-4)
2019.01.16:09:06:49.995: GPU13 GPU13: Allocating DAG (2x 2.85) GB; good for epoch up to #237
2019.01.16:09:06:49.995: GPU13 GPU13: Allocating light cache buffer (45.6) MB; good for epoch up to #237
2019.01.16:09:06:50.053: GPU11 GPU11: Generating DAG for epoch #235
2019.01.16:09:06:50.068: GPU11 GPU11: clEnqueueNDRangeKernel (-4)
2019.01.16:09:06:50.130: GPU12 GPU12: Generating DAG for epoch #235
2019.01.16:09:06:50.145: GPU12 GPU12: clEnqueueNDRangeKernel (-4)
2019.01.16:09:06:50.215: GPU13 GPU13: Generating DAG for epoch #235
2019.01.16:09:06:50.230: GPU13 GPU13: clEnqueueNDRangeKernel (-4)
2019.01.16:09:06:50.927: eths Eth: New job #ba79b5f7 from eu1.ethermine.org:4444; diff: 4000MH
2019.01.16:09:06:50.941: GPU8 GPU8: Starting up... (0)
2019.01.16:09:06:50.945: GPU11 GPU11: Starting up... (0)
2019.01.16:09:06:50.964: GPU12 GPU12: Starting up... (0)
2019.01.16:09:06:50.967: GPU13 GPU13: Starting up... (0)
2019.01.16:09:06:51.015: GPU8 GPU8: Allocating DAG (2x 2.85) GB; good for epoch up to #237
2019.01.16:09:06:51.015: GPU8 GPU8: Allocating light cache buffer (45.6) MB; good for epoch up to #237
2019.01.16:09:06:51.093: GPU11 GPU11: Allocating DAG (2x 2.85) GB; good for epoch up to #237
2019.01.16:09:06:51.093: GPU11 GPU11: Allocating light cache buffer (45.6) MB; good for epoch up to #237
2019.01.16:09:06:51.175: GPU12 GPU12: Allocating DAG (2x 2.85) GB; good for epoch up to #237
2019.01.16:09:06:51.175: GPU12 GPU12: Allocating light cache buffer (45.6) MB; good for epoch up to #237

On a second mixed rig 7+6 (nvidia/amd) seeing 0-0.3 MH/s hash rate increase. Tried -lidag 3, same results.

Increase the virtual memory of your system to at least 82 GB (13 X 2 X 3GB for the dags + 4GB for OS and apps) in order 4.1 to work.

The VM increase does the trick. Thanks @bategojko74!

[Juniormkl]

PhoenixMiner 4.1a (Windows/Linux) added to https://www.minermonitoring.com/



Join our discord https://discord.gg/aGGaeqq



also, you can check the speed of the miner on different rigs using the benchmark page: https://minermonitoring.com/benchmark

[bitcoinminer0319]

2019.01.16:19:39:00.717: main Phoenix Miner 4.0b Windows/msvc - Release build
2019.01.16:19:39:00.717: main Cmd line: -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0x008c26f3a2Ca8bdC11e5891e0278c9436B6F5d1E.Rig001
2019.01.16:19:39:00.717: main No CUDA driver found
2019.01.16:19:39:06.406: main Unknown OpenCL driver version! Hashrate and stale shares may suffer
2019.01.16:19:39:06.406: main OpenCL platform: OpenCL 2.1 AMD-APP (2766.5)
2019.01.16:19:39:06.406: main Available GPUs for mining:
2019.01.16:19:39:06.406: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
2019.01.16:19:39:06.406: main GPU2: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
2019.01.16:19:39:06.406: main GPU3: Radeon RX 580 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 36 CUs
2019.01.16:19:39:06.406: main GPU4: Radeon RX 580 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 36 CUs
2019.01.16:19:39:06.406: main GPU5: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
2019.01.16:19:39:06.406: main GPU6: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
2019.01.16:19:39:06.406: main GPU7: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 8 GB VRAM, 32 CUs
2019.01.16:19:39:06.406: main GPU8: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 8 GB VRAM, 32 CUs
2019.01.16:19:39:06.406: main GPU9: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 8 GB VRAM, 32 CUs
2019.01.16:19:39:06.406: main GPU10: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 8 GB VRAM, 32 CUs
2019.01.16:19:39:06.406: main GPU11: Radeon RX 570 Series (pcie 7), OpenCL 2.0, 8 GB VRAM, 32 CUs
2019.01.16:19:39:06.406: main GPU12: Radeon RX 570 Series (pcie 7), OpenCL 2.0, 8 GB VRAM, 32 CUs
2019.01.16:19:39:06.504: main ADL library initialized
2019.01.16:19:39:08.568: main Eth: Loading pools from epools.txt
2019.01.16:19:39:08.568: main Eth: the pool list contains 3 pools (2 from command-line)
2019.01.16:19:39:08.568: main Eth: primary pool: ssl://eu1.ethermine.org:5555
2019.01.16:19:39:08.568: main Starting GPU mining
2019.01.16:19:39:08.568: main Matched GPU1 to ADL adapter index 80 (method 1)
2019.01.16:19:39:08.670: main GPU1: Created ADL monitor for adapter 80; overdrive version: 7
2019.01.16:19:39:08.670: main GPU1: using AMD driver ver 18.2.1
2019.01.16:19:39:08.670: main Matched GPU2 to ADL adapter index 80 (method 1)
2019.01.16:19:39:08.768: main GPU2: Created ADL monitor for adapter 80; overdrive version: 7
2019.01.16:19:39:08.768: main GPU2: using AMD driver ver 18.2.1
2019.01.16:19:39:08.768: main Matched GPU3 to ADL adapter index 16 (method 1)
2019.01.16:19:39:08.864: main GPU3: Created ADL monitor for adapter 16; overdrive version: 7
2019.01.16:19:39:08.865: main GPU3: using AMD driver ver 18.2.1
2019.01.16:19:39:08.865: main Matched GPU4 to ADL adapter index 16 (method 1)
2019.01.16:19:39:08.962: main GPU4: Created ADL monitor for adapter 16; overdrive version: 7
2019.01.16:19:39:08.962: main GPU4: using AMD driver ver 18.2.1
2019.01.16:19:39:08.962: main Matched GPU5 to ADL adapter index 32 (method 1)
2019.01.16:19:39:09.059: main GPU5: Created ADL monitor for adapter 32; overdrive version: 7
2019.01.16:19:39:09.059: main GPU5: using AMD driver ver 18.2.1
2019.01.16:19:39:09.059: main Matched GPU6 to ADL adapter index 32 (method 1)
2019.01.16:19:39:09.159: main GPU6: Created ADL monitor for adapter 32; overdrive version: 7
2019.01.16:19:39:09.159: main GPU6: using AMD driver ver 18.2.1
2019.01.16:19:39:09.159: main Matched GPU7 to ADL adapter index 64 (method 1)
2019.01.16:19:39:09.257: main GPU7: Created ADL monitor for adapter 64; overdrive version: 7
2019.01.16:19:39:09.257: main GPU7: using AMD driver ver 18.2.1
2019.01.16:19:39:09.257: main Matched GPU8 to ADL adapter index 64 (method 1)
2019.01.16:19:39:09.353: main GPU8: Created ADL monitor for adapter 64; overdrive version: 7
2019.01.16:19:39:09.353: main GPU8: using AMD driver ver 18.2.1
2019.01.16:19:39:09.353: main Matched GPU9 to ADL adapter index 48 (method 1)
2019.01.16:19:39:09.450: main GPU9: Created ADL monitor for adapter 48; overdrive version: 7
2019.01.16:19:39:09.450: main GPU9: using AMD driver ver 18.2.1
2019.01.16:19:39:09.450: main Matched GPU10 to ADL adapter index 48 (method 1)
2019.01.16:19:39:09.547: main GPU10: Created ADL monitor for adapter 48; overdrive version: 7
2019.01.16:19:39:09.547: main GPU10: using AMD driver ver 18.2.1
2019.01.16:19:39:09.547: main Matched GPU11 to ADL adapter index 0 (method 1)
2019.01.16:19:39:09.646: main GPU11: Created ADL monitor for adapter 0; overdrive version: 7
2019.01.16:19:39:09.646: main GPU11: using AMD driver ver 18.2.1
2019.01.16:19:39:09.646: main Matched GPU12 to ADL adapter index 0 (method 1)
2019.01.16:19:39:09.745: main GPU12: Created ADL monitor for adapter 0; overdrive version: 7
2019.01.16:19:39:09.745: main GPU12: using AMD driver ver 18.2.1
2019.01.16:19:39:09.745: wdog Starting watchdog thread
2019.01.16:19:39:10.202: main Eth: Connecting to ethash pool ssl://eu1.ethermine.org:5555 (proto: EthProxy)
2019.01.16:19:39:10.285: eths Eth: Connected to SSL ethash pool eu1.ethermine.org:5555 (2606:4700:90:0:bda0:4092:8f4f:4658)
2019.01.16:19:39:10.388: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0x008c26f3a2Ca8bdC11e5891e0278c9436B6F5d1E.Rig001"]}

2019.01.16:19:39:10.410: main Listening for CDM remote manager at port 3333 in read-only mode
2019.01.16:19:39:10.418: main GPU1: 46C 0%, GPU2: 46C 0%, GPU3: 47C 0%, GPU4: 47C 0%, GPU5: 40C 0%, GPU6: 40C 0%, GPU7: 39C 0%, GPU8: 39C 0%, GPU9: 27C 0%, GPU10: 27C 0%, GPU11: 47C 0%, GPU12: 47C 0%
2019.01.16:19:39:10.582: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2019.01.16:19:39:10.582: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.01.16:19:39:10.714: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x04b009445f9928514aacd491b25b811f1e6036026e7a609a2f6100b735fe5527","0x7e15c2d0250b2fcd9fe9b6c79ec091ea97591f8c5a4a69119655bb2090da375e","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6c045c"]}
2019.01.16:19:39:10.714: eths Eth: New job #04b00944 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2019.01.16:19:39:10.715: GPU1 GPU1: Starting up... (0)
2019.01.16:19:39:10.716: GPU1 GPU1: Generating ethash light cache for epoch #235
2019.01.16:19:39:10.722: GPU2 GPU2: Starting up... (0)
2019.01.16:19:39:10.737: GPU3 GPU3: Starting up... (0)
2019.01.16:19:39:10.753: GPU4 GPU4: Starting up... (0)
2019.01.16:19:39:10.768: GPU5 GPU5: Starting up... (0)
2019.01.16:19:39:10.784: GPU6 GPU6: Starting up... (0)
2019.01.16:19:39:10.801: GPU7 GPU7: Starting up... (0)
2019.01.16:19:39:10.816: GPU8 GPU8: Starting up... (0)
2019.01.16:19:39:10.831: GPU9 GPU9: Starting up... (0)
2019.01.16:19:39:10.847: GPU10 GPU10: Starting up... (0)
2019.01.16:19:39:10.862: GPU11 GPU11: Starting up... (0)
2019.01.16:19:39:10.878: GPU12 GPU12: Starting up... (0)
2019.01.16:19:39:13.079: GPU1 Light cache generated in 2.4 s (19.2 MB/s)
2019.01.16:19:39:13.395: GPU1 GPU1: Allocating DAG (2.85) GB; good for epoch up to #237
2019.01.16:19:39:13.403: GPU1 GPU1: Allocating light cache buffer (45.6) MB; good for epoch up to #237
2019.01.16:19:39:13.590: GPU1 GPU1: Generating DAG for epoch #235
2019.01.16:19:39:15.161: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x30a73b8693d5e30df1a640fb471b5638f85df145c7e40759f48c5efc17f4393a","0x7e15c2d0250b2fcd9fe9b6c79ec091ea97591f8c5a4a69119655bb2090da375e","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6c045d"]}
2019.01.16:19:39:15.161: eths Eth: New job #30a73b86 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2019.01.16:19:39:15.161: GPU1 GPU1: DAG   6%


how do i fix this problem?

[Batmaxpt]

hi

all good

[marko330]

hi

all good with PhoenixMiner until some hours ago i have more than one rig all nvidia and all with these error any idea with ?
http://i202.photobucket.com/albums/aa241/BatmaxPT/error.png

Have the same problem since 4 hours. My rig works pver year without problems but today i've seen error with CUDA.

CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77)
GPU1 initMiner error: an illegal memory access was encountered
CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77)
GPU2 initMiner error: an illegal memory access was encountered

or

CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77)
CUDA error in CudaProgram.cu:102 : an illegal memory access was encountered (700)
GPU2 initMiner error: an illegal memory access was encountered
GPU1 initMiner error: an illegal memory access was encountered


Anyone know what to do with this? Virtual memory is fine.

[MegaVlad]

CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77)
CUDA error in CudaProgram.cu:102 : an illegal memory access was encountered (700)
GPU2 initMiner error: an illegal memory access was encountered
GPU1 initMiner error: an illegal memory access was encountered


The same problem on all rigs, in one time, 6 hours ago. Still not working. Anyone knows it? Version - Phoenix 3.5D.
Pool - Ethermine.org

[Kreso75]

Happened to me, after upgrade to 4.0b it works again.

[marko330]

I confirm, after updating the software to the latest 4.0b - it is working correctly.

[Batmaxpt]

I confirm, after updating the software to the latest 4.0b - it is working correctly.

confirm too thanks al lot peace

[cmd_whoami]

I started getting crash on dag creation on one rig some time in the middle of the night running Phoenix Miner 2.8... Now today all my rigs running 2.8 crash... Would think it's something that Windows pushed, even tho I have Windows Update disabled... Hopefully someone can figure it out...

[MegaVlad]

I confirm, after updating the software to the latest 4.0b - it is working correctly.

Also 4.0b start working. But WTF it was with ver.3.5D & 3.0C ? Developers can explain?

[PhoenixMiner]

I confirm, after updating the software to the latest 4.0b - it is working correctly.

Also 4.0b start working. But WTF it was with ver.3.5D & 3.0C ? Developers can explain?

   (also to all miners experiencing problems with PhoenixMiner 3.5 and below versions when trying to create the DAG):

   The versions of PhoenixMiner before 4.0 only support DAG epoch up to 235. ETC passed epoch 235 a few weeks ago, and recently ETH also passed DAG epoch 235 and is now on 236. The unfortunate result is that the old version(s) of PhoenixMiner won't be able to create DAG or mine ETH or ETC any more - you must upgrade to PhoenixMiner 4.x.
   We have printed this warning here during the release of PhoenixMiner 4.0 but admittedly we could have done much better job with making it visible. We will pin this message in the first post too.

[MegaVlad]

 
   The versions of PhoenixMiner before 4.0 only support DAG epoch up to 235. ETC passed epoch 235 a few weeks ago, and recently ETH also passed DAG epoch 235 and is now on 236. The unfortunate result is that the old version(s) of PhoenixMiner won't be able to create DAG or mine ETH or ETC any more - you must upgrade to PhoenixMiner 4.x.
   We have printed this warning here during the release of PhoenixMiner 4.0 but admittedly we could have done much better job with making it visible. We will pin this message in the first post too.

Thank you for explanation!

[Batmaxpt]

Thanks Dev.

[pp55]

I can`t see if I can use -Kernel option per GPU. Is it impossible at all or it is miner limitation?
I have a rig with one RX580 8Gb and four RX570 4Gb and wanna try turbo kernels. Any suggestions?

Am I the only one who have mixed rigs and wanna try turbo kernels?