 Show Posts
|
|
Pages: « 1 2 3 4 [5] 6 »
|
Hi,
I recently installed the PhoenixMiner 2.9e, moving from Claymore where I was mining ETH to now mine PIRL and am having some issues, hoping you all can help me resolve. I get a CUDA error 377 out of memory error on the nVidia cards (1060 3 GB), the AMD cards work fine.
Rig:
ASRosk HTC110 Mobo
3 AMD 570 gpus
8 nVidia 1060 3 GB GPUs
8 GB RAM
250 GB HD
nvidia driver 388.59 (I've tried an older 37X.xx version, did not help)
Virtual Memory - minimum set to 60,000, max set to 160,000.
Set to mine PIRL so that the DAG is not a problem
REM
REM Example bat file for starting PhoenixMiner.exe to mine ETH
REM PhoenixMiner.exe -pool pirl.minerpool.net:8002 -wal YourPirlWalletAddress -pass x -worker WorkerName
REM
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
REM IMPORTANT: Replace the ETH address with your own ETH wallet address in the -wal option (Rig001 is the name of the rig)
PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0xac1CbCB36704BD0BE0A773cDAFE98c72a70707e2.CocoSpency -eres 0 -lidag 3
pause
This rig has been successfully with claymore on ETH for several months. Then MS pushed the update that 'killed' the 1060's 3GB from being able to mine ETH. Switched to your miner and PIRL to keep using them.
Would welcome any thoughts, I can't seem to find any solutions online.
Seems your are using your ETH wallet to mine pirl, you must have a pirl wallet. The pool is an ETH pool, you must log in a PIRL pool PhoenixMiner.exe -pool pirl.minerpool.net:8002 -wal USE_YOUR_PIRL_WALLET_HERE.CocoSpency -eres 0 -lidag 3 IAMTUTU - Thanks for finding my additional error! In my haste of copying pasting between bat files, I jacked that all up. Got that part fixed, but am getting this error. 2018.05.02:13:15:40.936: GPU2 GPU2: Generating DAG for epoch #43 2018.05.02:13:15:40.971: GPU9 CUDA error in CudaProgram.cu:102 : an illegal memory access was encountered (700) 2018.05.02:13:15:40.971: GPU9 GPU9 initMiner error: an illegal memory access was encountered 2018.05.02:13:15:40.971: GPU10 CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77) 2018.05.02:13:15:40.971: GPU10 GPU10 initMiner error: an illegal memory access was encountered 2018.05.02:13:15:41.071: GPU11 CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77) 2018.05.02:13:15:41.071: GPU11 GPU11 initMiner error: an illegal memory access was encountered 2018.05.02:13:15:41.071: GPU4 CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77) 2018.05.02:13:15:41.071: GPU4 GPU4 initMiner error: an illegal memory access was encountered 2018.05.02:13:15:41.071: GPU5 CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77) 2018.05.02:13:15:41.071: GPU5 GPU5 initMiner error: an illegal memory access was encountered 2018.05.02:13:15:41.071: GPU2 CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77) 2018.05.02:13:15:41.071: GPU2 GPU2 initMiner error: an illegal memory access was encountered 2018.05.02:13:15:41.071: GPU7 CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77) 2018.05.02:13:15:41.071: GPU7 GPU7 initMiner error: an illegal memory access was encountered 2018.05.02:13:15:41.071: GPU3 CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77) 2018.05.02:13:15:41.071: GPU3 GPU3 initMiner error: an illegal memory access was encountered 2018.05.02:13:15:41.129: GPU1 GPU1: Using new optimized OpenCL kernels (device name 'Ellesmere') 2018.05.02:13:15:41.129: GPU1 GPU1: Allocating DAG for epoch #43 (1.34) GB 2018.05.02:13:15:41.129: GPU1 GPU1: Allocating light cache buffer (21.4) MB; good for epoch up to #43 2018.05.02:13:15:41.184: GPU1 GPU1: Generating DAG for epoch #43 Thoughts? See thread.. https://bitcointalk.org/index.php?topic=2647654.msg31966965#msg31966965Likely just the overclock setting needs to be lowered... |
|
|
|
|
Hi just tried new amd driver 18.4.1. I get error errors on vega 64;
windows 10 pro
2018.04.30:19:12:24.575: GPU1 build: Failed to GPU1 program: clBuildProgram (-11)
2018.04.30:19:12:24.575: GPU1 GPU1: Failed to load kernels: clCreateKernel (-46)
tried using
-clKernel 0 and 1 no luck.
|
|
|
|
|
To any Nvidia 1080 or 1080it owners check out OhgodETHlargement pill. its an app in background that supposedly can push you to around 54 mhs. I use amd so out of luck. Curious to see if it indeed affects PM hash rates. glta
|
|
|
|
I'm not being impatient... Really, just curious... I mean, been mining all day.
I'm just learning about all this. I kicked off a pair of GTX 1070s at 5:30 am (Pacific.) It's finding shares, but I don't see any action on my address. Am I doing something wrong, or just being impatient? TIA.
.bat looks like this:
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 ssl://us2.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0x7e67fb8270f7e6e0d20a9598905f7a336106c319.Miner49er -proto 3
pause
check pools file may have default in place that may override config file |
|
|
|
Need some help with this error. PhoenixMiner 2.9e main Available GPUs for mining: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 32 CUs main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 32 CUs main GPU4: Radeon (TM) RX 470 Graphics (pcie  , OpenCL 2.0, 4 GB VRAM, 32 CUs main ADL library initialized Fattal ERROR: Debugger detected Do you have the param -amd in your config? A view or your start bat or config may help troubleshoot. Yes i have -amd My bat: 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 eu1.ethermine.org:4444 -wal 0xd66a5 -worker Rig5 -tt 57 -fanmin 40 -fanmax 75 -coin eth -cdm 0 -pass x -amd pause Try and match the example more closely... ethermine.org (ETH): PhoenixMiner.exe -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal YourEthWalletAddress.WorkerName -proto 3 ethermine.org (ETH, secure connection): PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal YourEthWalletAddress.WorkerName -proto 3 ethpool.org (ETH): I would also use SSL version if available more secure. In your case then... PhoenixMiner.exe -pool eu1.ethermine.org:4444 -wal your_walletID.Rig5 -pass x -amd -tt 57 -fanmin 40 -fanmax 75 -cdm 0 Also cheek pools file isnt also messed up.(should match this) My first try was ssl but i thought maybe there is a problem so i tried without ssl but no luck. What ever i do there is always the same error. Fattal ERROR: Debugger detected. Thanks for helping me out to solve this. BTW Claymore is working fine on the same rig but i want to try Phoenix New bat same error 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 ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0xd66a.Rig5 -proto 3 -pass x -amd -coin eth -coin2 eth -tt 57 -fanmin 40 -fanmax 75 -cdm 0 I really think its the wallet ID format that is the issue. DO you not have a long string version? Like 0x78e371c6bd0a74c3255152d0418aa457cea5b784 as an example. use this format instead I have just removed it for the post. Don`t want to post my wallet id at seem counter intuitive but kill some of bat line.. PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -wal 0xd66a.Rig5 -proto 3 -pass x -amd -tt 57 -fanmin 40 -fanmax 75 -cdm 0 also what are your virtual memory settings like, could you be low I have tried with minimal bat settings but the error is still there. Virtual memory is at 32GB I am thinking its more a system issue with how its reacting to PM. What OS version, What AMD driver version? |
|
|
|
Need some help with this error. PhoenixMiner 2.9e main Available GPUs for mining: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 32 CUs main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 32 CUs main GPU4: Radeon (TM) RX 470 Graphics (pcie , OpenCL 2.0, 4 GB VRAM, 32 CUs main ADL library initialized Fattal ERROR: Debugger detected Do you have the param -amd in your config? A view or your start bat or config may help troubleshoot. Yes i have -amd My bat: 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 eu1.ethermine.org:4444 -wal 0xd66a5 -worker Rig5 -tt 57 -fanmin 40 -fanmax 75 -coin eth -cdm 0 -pass x -amd pause Try and match the example more closely... ethermine.org (ETH): PhoenixMiner.exe -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal YourEthWalletAddress.WorkerName -proto 3 ethermine.org (ETH, secure connection): PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal YourEthWalletAddress.WorkerName -proto 3 ethpool.org (ETH): I would also use SSL version if available more secure. In your case then... PhoenixMiner.exe -pool eu1.ethermine.org:4444 -wal your_walletID.Rig5 -pass x -amd -tt 57 -fanmin 40 -fanmax 75 -cdm 0 Also cheek pools file isnt also messed up.(should match this) My first try was ssl but i thought maybe there is a problem so i tried without ssl but no luck. What ever i do there is always the same error. Fattal ERROR: Debugger detected. Thanks for helping me out to solve this. BTW Claymore is working fine on the same rig but i want to try Phoenix New bat same error 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 ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0xd66a.Rig5 -proto 3 -pass x -amd -coin eth -coin2 eth -tt 57 -fanmin 40 -fanmax 75 -cdm 0 I really think its the wallet ID format that is the issue. DO you not have a long string version? Like 0x78e371c6bd0a74c3255152d0418aa457cea5b784 as an example. use this format instead I have just removed it for the post. Don`t want to post my wallet id at seem counter intuitive but kill some of bat line.. PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -wal 0xd66a.Rig5 -proto 3 -pass x -amd -tt 57 -fanmin 40 -fanmax 75 -cdm 0 also what are your virtual memory settings like, could you be low |
|
|
|
Need some help with this error. PhoenixMiner 2.9e main Available GPUs for mining: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 32 CUs main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 32 CUs main GPU4: Radeon (TM) RX 470 Graphics (pcie , OpenCL 2.0, 4 GB VRAM, 32 CUs main ADL library initialized Fattal ERROR: Debugger detected Do you have the param -amd in your config? A view or your start bat or config may help troubleshoot. Yes i have -amd My bat: 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 eu1.ethermine.org:4444 -wal 0xd66a5 -worker Rig5 -tt 57 -fanmin 40 -fanmax 75 -coin eth -cdm 0 -pass x -amd pause Try and match the example more closely... ethermine.org (ETH): PhoenixMiner.exe -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal YourEthWalletAddress.WorkerName -proto 3 ethermine.org (ETH, secure connection): PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal YourEthWalletAddress.WorkerName -proto 3 ethpool.org (ETH): I would also use SSL version if available more secure. In your case then... PhoenixMiner.exe -pool eu1.ethermine.org:4444 -wal your_walletID.Rig5 -pass x -amd -tt 57 -fanmin 40 -fanmax 75 -cdm 0 Also cheek pools file isnt also messed up.(should match this) My first try was ssl but i thought maybe there is a problem so i tried without ssl but no luck. What ever i do there is always the same error. Fattal ERROR: Debugger detected. Thanks for helping me out to solve this. BTW Claymore is working fine on the same rig but i want to try Phoenix New bat same error 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 ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0xd66a.Rig5 -proto 3 -pass x -amd -coin eth -coin2 eth -tt 57 -fanmin 40 -fanmax 75 -cdm 0 I really think its the wallet ID format that is the issue. DO you not have a long string version? Like 0x78e371c6bd0a74c3255152d0418aa457cea5b784 as an example. use this format instead |
|
|
|
Need some help with this error. PhoenixMiner 2.9e main Available GPUs for mining: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 32 CUs main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 32 CUs main GPU4: Radeon (TM) RX 470 Graphics (pcie , OpenCL 2.0, 4 GB VRAM, 32 CUs main ADL library initialized Fattal ERROR: Debugger detected Do you have the param -amd in your config? A view or your start bat or config may help troubleshoot. Yes i have -amd My bat: 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 eu1.ethermine.org:4444 -wal 0xd66a5 -worker Rig5 -tt 57 -fanmin 40 -fanmax 75 -coin eth -cdm 0 -pass x -amd pause Try and match the example more closely... ethermine.org (ETH): PhoenixMiner.exe -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal YourEthWalletAddress.WorkerName -proto 3 ethermine.org (ETH, secure connection): PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal YourEthWalletAddress.WorkerName -proto 3 ethpool.org (ETH): I would also use SSL version if available more secure. In your case then... PhoenixMiner.exe -pool eu1.ethermine.org:4444 -wal your_walletID.Rig5 -pass x -amd -tt 57 -fanmin 40 -fanmax 75 -cdm 0 Also cheek pools file isnt also messed up.(should match this) |
|
|
|
Need some help with this error. PhoenixMiner 2.9e main Available GPUs for mining: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 32 CUs main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 32 CUs main GPU4: Radeon (TM) RX 470 Graphics (pcie , OpenCL 2.0, 4 GB VRAM, 32 CUs main ADL library initialized Fattal ERROR: Debugger detected Do you have the param -amd in your config? A view or your start bat or config may help troubleshoot. |
|
|
|
Hi first time i try to switch from claymore for mining CLO (Callisto) (Ethash algorythm) and impossible to connected to the pool apparently...
Here's my logs :
2018.04.18:22:54:36.527: main Phoenix Miner 2.9e Windows/msvc - Release
2018.04.18:22:54:36.527: main Cmd line:
2018.04.18:22:54:36.527: main config.txt: -pool clo.2miners.com:3030 -wal 0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480
2018.04.18:22:54:36.527: main No CUDA driver found
2018.04.18:22:54:38.593: main Available GPUs for mining:
2018.04.18:22:54:38.593: main GPU1: Radeon (TM) RX 480 Graphics (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU2: Radeon (TM) RX 480 Graphics (pcie 3), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU3: Radeon (TM) RX 480 Graphics (pcie 4), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU4: Radeon (TM) RX 480 Graphics (pcie 5), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU5: Radeon (TM) RX 480 Graphics (pcie 6), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU6: Radeon (TM) RX 480 Graphics (pcie 7), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.681: main ADL library initialized
2018.04.18:22:54:39.035: main Listening for CDM remote manager at port 3333 in read-only mode
2018.04.18:22:54:39.035: main Eth: the pool list contains 2 pools
2018.04.18:22:54:39.035: main Eth: primary pool: clo.2miners.com:3030
2018.04.18:22:54:39.035: main Starting GPU mining
2018.04.18:22:54:39.035: main Matched GPU1 to ADL adapter index 64 (method 1)
2018.04.18:22:54:39.262: main GPU1: Created ADL monitor for adapter 64; overdrive version: 7
2018.04.18:22:54:39.262: main GPU1: using AMD driver ver 18.3.4
2018.04.18:22:54:39.262: main Matched GPU2 to ADL adapter index 16 (method 1)
2018.04.18:22:54:39.431: main GPU2: Created ADL monitor for adapter 16; overdrive version: 7
2018.04.18:22:54:39.431: main GPU2: using AMD driver ver 18.3.4
2018.04.18:22:54:39.431: main Matched GPU3 to ADL adapter index 32 (method 1)
2018.04.18:22:54:39.528: main GPU3: Created ADL monitor for adapter 32; overdrive version: 7
2018.04.18:22:54:39.528: main GPU3: using AMD driver ver 18.3.4
2018.04.18:22:54:39.529: main Matched GPU4 to ADL adapter index 48 (method 1)
2018.04.18:22:54:39.615: main GPU4: Created ADL monitor for adapter 48; overdrive version: 7
2018.04.18:22:54:39.615: main GPU4: using AMD driver ver 18.3.4
2018.04.18:22:54:39.615: main Matched GPU5 to ADL adapter index 80 (method 1)
2018.04.18:22:54:39.692: main GPU5: Created ADL monitor for adapter 80; overdrive version: 7
2018.04.18:22:54:39.692: main GPU5: using AMD driver ver 18.3.4
2018.04.18:22:54:39.692: main Matched GPU6 to ADL adapter index 0 (method 1)
2018.04.18:22:54:39.785: main GPU6: Created ADL monitor for adapter 0; overdrive version: 7
2018.04.18:22:54:39.785: main GPU6: using AMD driver ver 18.3.4
2018.04.18:22:54:39.786: wdog Starting watchdog thread
2018.04.18:22:54:39.786: main Eth: Connecting to ethash pool clo.2miners.com:3030 (proto: EthProxy)
2018.04.18:22:54:39.872: eths Eth: Connected to ethash pool clo.2miners.com:3030 (95.213.255.168)
2018.04.18:22:54:39.872: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480"]}
2018.04.18:22:54:39.940: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Invalid login"}}
2018.04.18:22:54:39.940: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2018.04.18:22:54:39.940: eths Eth: Connection closed by the pool
2018.04.18:22:54:39.940: eths Eth: Reconnecting in 20 seconds...
2018.04.18:22:54:39.987: main GPU1: 31C 66%, GPU2: 32C 66%, GPU3: 40C 73%, GPU4: 30C 66%, GPU5: 34C 66%, GPU6: 32C 66%
And this is my BAT start file :
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 clo.2miners.com:3030 -wal 0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480 -pass x -coin etc
Any help would be appreciated
Thanks.
Is it possible you have more than one rig trying to use the same login name? "-wal 0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480" Try changing it to -wal 0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480_1 |
|
|
|
Hey if any of you re interested check out
ETH.ethertrench.com
FREE mining pool. No pool fees. Low latency(few stales). If I compare my overall returns for the same hashrate as I had when I was on Supernova the payouts are almost double!!!
Pays out very quickly no hassles, also pays for valid uncle shares(stales) as well.
its a smaller pool so finds less often but has large miners come and go that help frequency of finds.
i ve used Phoenix on here for the last few weeks and its been great.
FYI disclosure. I have no affiliation to anyone running or on the pool.
Enjoy!
what is your bat file for phoenix miner? standard commands wont work.thx in advance What standard commands do you mean? Post your bat and can ref any potential issues for you. regards |
|
|
|
Hi all, have rig with x6 RX580 8GB(x3 XFX GTS and x3 STRIX TOP Gaming), when i start miner with parameter -tt 64, miner set only for 3 cards XFX (Claymore work fine for all gpu). Help pls( Screen: https://i.imgur.com/LPRmrWq.pngTry -tt 64,64,64,64,64,64 Normally should work one entry for all. |
|
|
|
|
Hey if any of you re interested check out
ETH.ethertrench.com
FREE mining pool. No pool fees. Low latency(few stales). If I compare my overall returns for the same hashrate as I had when I was on Supernova the payouts are almost double!!!
Pays out very quickly no hassles, also pays for valid uncle shares(stales) as well.
its a smaller pool so finds less often but has large miners come and go that help frequency of finds.
i ve used Phoenix on here for the last few weeks and its been great.
FYI disclosure. I have no affiliation to anyone running or on the pool.
Enjoy!
|
|
|
|
What are we still happy with phoenixminer 2.9.e the stale shares are back again, while it was with the 2.9 .d away the joy is so short-lived unfortunately.
I am going to guess its your system, I have less stale shares as well as fewer incorrect ones being generated. I will say its been only around 7 hrs so far. What cards and drivers are you running? |
|
|
|
Update and comparison
2.9d is actually a bit of a loss in hashrate. vega 64 virtually no change from 2.8c. fury x are lower than 2.8c 34.5 avg now
the best speed was 2.8b but stales now are virtually nil.
Regards
You can try higher -gt values with the Fury cards with the new kernels. We found optimal performance in some of our Fury cards at about -gt 150. I have tried from 50 to 300 for the furys, I am running fastest at -gt 225. I also found it faster running the -clf 2 The screen output for each line of the GPU summary you have a list of all GPUs and the shares found for each.(If and when a stale is found then beside each count you would have a secondary total.)
GPU 1 - (105/3) in this case the 105 is found shares, the 3 are the stales)
Make sense now?
Actually, these are the incorrect shares, not the stales. As stated above, the stales are not shown for each GPU (only as total number). ok thanks for clarifying. |
|
|
|
Phoenixminer is possible stale shares which GPU - >> total ?? and gpu 1 /? gpu2 /? gpu3 /? etc. It is easier to change settings of the GPU that causes the most stales. http://www.resimag.com/p1/e9d607fe24.jpegIt does this already. x,y,z are assigned stale shares per each GPU that caused it. GPU 1 shares 10/x, GPU 2 shares 10/y, GPU 3 shares 10/z I press the x / y / z keys but on the screen I get no info about STALE share per GPU unfortunately, please tell us a bit more efficiently The screen output for each line of the GPU summary you have a list of all GPUs and the shares found for each.(If and when a stale is found then beside each count you would have a secondary total.) GPU 1 - (105/3) in this case the 105 is found shares, the 3 are the stales) Make sense now? |
|
|
|
Phoenixminer is possible stale shares which GPU - >> total ?? and gpu 1 /? gpu2 /? gpu3 /? etc. It is easier to change settings of the GPU that causes the most stales.  It does this already. x,y,z are assigned stale shares per each GPU that caused it. GPU 1 shares 10/x, GPU 2 shares 10/y, GPU 3 shares 10/z |
|
|
|
2.8c has all but removed all stales i get reported on screen.
vega 64 impact, no difference in terms of speed mh wise from 2.8b.(ratio of found shares does seem to be lower though when looking at all shares found across all gpus in rig)
fury x the reported hash rates are more level but spikes to higher hashrates are gone. I was getting an avg 35.2 mh on them with spikes to 40.(2.8b) now avg is 34.5 with no spikes. 2.8c
thanks for PM
Update and comparison 2.9d is actually a bit of a loss in hashrate. vega 64 virtually no change from 2.8c. fury x are lower than 2.8c 34.5 avg now the best speed was 2.8b but stales now are virtually nil. Regards |
|
|
|
Hehe finally 2.9.d, with a lot of effort downloaded and started only, the miner runs after a few seconds and starts again, and with version 2.8.c it ran like a train.rarara how is that possible. my start. bat is like that I think it's all by the devfee who makes this software completely unbearable. software that has proven itself is ethminer + watchdog windows. ---------------------------------------------------------------------------------------------- Ethminer.exe crash and doesn't restart? Here is a fix! WiNETH,I will take care of your miner and you can relax 2018 WiNETHER is a program that will restart your ethminer everytime it has error. Links: readme : https://github.com/digitalpara/WiNETHdownloads https://mirrorace.com/m/1qiktDon't forget to click Watchdog options and set delay before monitoring for 0MH/s high (mine is 99) Ethminer is an ethereum miner without devfee Links: readme https://github.com/ethereum-mining/ethminerdownloads https://github.com/ethereum-mining/ethminer/releasesFunny Etherminer for me using Fury x and vega 64 is about 15 % slower than PM 2.8b or 2.8c(haven`t tried PM 2.9b) yet... So lets look at the math if we look at PM rate being 100%(inc dev fee)... Etherminer 100% - 15% = 85% total rate PhoenixMiner Miner 100% - .65% = 99.35% total rate If we look at top level total rate and assume the stale rates are the same(PM tends to lower for me) Then Using Etherminer will lose you around -14.35% of your total mining rate after the PM dev fee... Be interesting to see others comparisons if they have done it. |
|
|
|
Can anybody tell me why phoenix.exe above 2.7c crashes in 5 seconds when starting on one rig and on my other rig it runs perfect also with latest version.
Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
add to start.bat file in the end -rmode 1 -nvidia -log 0 -eres 2 -coin eth if u mine ether, save and start, try Thanks for your advice, but unfortunately phoenix keeps shuting down and don”t restart if something happens. Some times after 10 times starting Phoernix manualy, it runs untill an autorestart is needed because of some faillure and it says: phoenix.exe isn’t working anymore and shuts down. I had a similar behaviour one one of my rigs. I finally isolated it to one card running too hot after a while. Check your logs to see if one of the cards shuts itself off near the end of the log. Try reducing the overclocks and see if running a few degrees colder helps. Also check your Pagefile memory. Ensure its set high enough. good luck The shutdown of the miner is also from the start, even with a cold card. My cards never get hotter than 58 degrees. (49-58) The problem with shuting down appears with and without overclocking. I will try to re-install the rig soon and see what happens. If it is an almost instant no start then could be just bat file or epools settings is incorrect. Check wallet address, mining worker format, mining url and port. If you have copied it from another mining rig and when you start up it has for example the same worker number from another rig it may just need to be adjusted to be indeed a new worker.... |
|
|
|
|
