Search content
Sort by
Showing 6 of 6 results by roptix
Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Hello all - could really use some help here.
I switched from Claymore 11.6 to PhoenixMiner 2.9e due to the DAG and MSWindows 10 issues that prevent the nVidia 1060 3GB cards from working. However for the last 3 weeks I have been getting an illegal memory error:
GPU10 CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77)
2018.05.15:15:13:00.328: GPU11 CUDA error in CudaProgram.cu:102 : an illegal memory access was encountered (700)
To be clear, I can no longer get the nVidia 1060 cards to work with Claymore or PhoenixMiner on ETH or PIRL....
OC'ing the cards seems to be a common cause, but I'm not OCing the cards, I can't even get to the point of doing that...
Would welcome any thoughts, I can't seem to find any solutions online.
Russell
I switched from Claymore 11.6 to PhoenixMiner 2.9e due to the DAG and MSWindows 10 issues that prevent the nVidia 1060 3GB cards from working. However for the last 3 weeks I have been getting an illegal memory error:
GPU10 CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77)
2018.05.15:15:13:00.328: GPU11 CUDA error in CudaProgram.cu:102 : an illegal memory access was encountered (700)
To be clear, I can no longer get the nVidia 1060 cards to work with Claymore or PhoenixMiner on ETH or PIRL....
OC'ing the cards seems to be a common cause, but I'm not OCing the cards, I can't even get to the point of doing that...
Would welcome any thoughts, I can't seem to find any solutions online.
Russell
do you have at least 19 gig virtual memory on your system, might be a reason if its too little.
I've actually set Virtual Memory as: - minimum set to 60,000, max set to 160,000
And I'm fine not mining ETH, I can't mine PIRL either right now, which is the real conundrum as it's DAG should easily be supported by the 3GB cards.
Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Hello all - could really use some help here.
I switched from Claymore 11.6 to PhoenixMiner 2.9e due to the DAG and MSWindows 10 issues that prevent the nVidia 1060 3GB cards from working. However for the last 3 weeks I have been getting an illegal memory error:
GPU10 CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77)
2018.05.15:15:13:00.328: GPU11 CUDA error in CudaProgram.cu:102 : an illegal memory access was encountered (700)
To be clear, I can no longer get the nVidia 1060 cards to work with Claymore or PhoenixMiner on ETH or PIRL....
OC'ing the cards seems to be a common cause, but I'm not OCing the cards, I can't even get to the point of doing that...
Rig:
ASRosk HTC110 Mobo
3 AMD 570 gpus
8 nVidia 1060 3 GB GPUs
8 GB RAM
250 GB HD
nvidia driver 376.09 (I've tried 397.64, 397.31 and 388.59)
Virtual Memory - minimum set to 60,000, max set to 160,000.
Set to mine PIRL
2018.05.15:15:12:51.882: main Phoenix Miner 2.9e Windows/msvc - Release
2018.05.15:15:12:51.882: main Cmd line: -pool stratum+tcp://us-west.pirlpool.eu:8002 -wal 0xac1CbCB36704BD0BE0A773cDAFE98c72a70707e2 -pass x -worker CocoSpency -eres 0 -lidag 2
2018.05.15:15:12:56.054: main Available GPUs for mining:
2018.05.15:15:12:56.056: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
2018.05.15:15:12:56.056: main GPU2: GeForce GTX 1060 3GB (pcie 2), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
2018.05.15:15:12:56.056: main GPU3: GeForce GTX 1060 3GB (pcie 3), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
2018.05.15:15:12:56.056: main GPU4: GeForce GTX 1060 3GB (pcie 4), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
2018.05.15:15:12:56.056: main GPU5: GeForce GTX 1060 3GB (pcie 5), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
2018.05.15:15:12:56.056: main GPU6: Radeon RX 570 Series (pcie
, OpenCL 2.0, 4 GB VRAM, 32 CUs
2018.05.15:15:12:56.056: main GPU7: GeForce GTX 1060 3GB (pcie 9), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
2018.05.15:15:12:56.056: main GPU8: Radeon RX 570 Series (pcie 11), OpenCL 2.0, 4 GB VRAM, 32 CUs
2018.05.15:15:12:56.056: main GPU9: GeForce GTX 1060 3GB (pcie 12), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
2018.05.15:15:12:56.056: main GPU10: GeForce GTX 1060 3GB (pcie 13), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
2018.05.15:15:12:56.056: main GPU11: GeForce GTX 1060 3GB (pcie 14), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
....
2018.05.15:15:12:57.540: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba59fa1663dc115be208375f438f043e803c155ca857d96f214b11bf619d853f","0xd6a8400b7f4cc5e082e8239662ed0ee7162892f74016107a7586195f4d591efb","0x0225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"]}
2018.05.15:15:12:57.541: eths Eth: New job #ba59fa16 from us-west.pirlpool.eu:8002; diff: 2000MH
2018.05.15:15:12:57.542: GPU2 GPU2: Starting up... (0)
2018.05.15:15:12:57.542: GPU2 Eth: Generating light cache for epoch #46
2018.05.15:15:12:57.544: GPU3 GPU3: Starting up... (0)
2018.05.15:15:12:57.546: GPU4 GPU4: Starting up... (0)
2018.05.15:15:12:57.548: GPU5 GPU5: Starting up... (0)
2018.05.15:15:12:57.550: GPU7 GPU7: Starting up... (0)
2018.05.15:15:12:57.552: GPU9 GPU9: Starting up... (0)
2018.05.15:15:12:57.554: GPU10 GPU10: Starting up... (0)
2018.05.15:15:12:57.556: GPU11 GPU11: Starting up... (0)
2018.05.15:15:12:57.558: GPU1 GPU1: Starting up... (0)
2018.05.15:15:12:57.560: GPU6 GPU6: Starting up... (0)
2018.05.15:15:12:57.562: GPU8 GPU8: Starting up... (0)
2018.05.15:15:12:59.482: GPU4 GPU4: Allocating DAG for epoch #46 (1.36) GB
2018.05.15:15:12:59.608: GPU4 GPU4: Allocating light cache buffer (21.7) MB; good for epoch up to #46
2018.05.15:15:12:59.652: GPU2 GPU2: Allocating DAG for epoch #46 (1.36) GB
2018.05.15:15:12:59.716: GPU2 GPU2: Allocating light cache buffer (21.7) MB; good for epoch up to #46
2018.05.15:15:12:59.874: GPU9 GPU9: Allocating DAG for epoch #46 (1.36) GB
2018.05.15:15:12:59.894: GPU10 GPU10: Allocating DAG for epoch #46 (1.36) GB
2018.05.15:15:12:59.949: GPU2 GPU2: Generating DAG for epoch #46
2018.05.15:15:12:59.958: GPU10 GPU10: Allocating light cache buffer (21.7) MB; good for epoch up to #46
2018.05.15:15:12:59.959: GPU9 GPU9: Allocating light cache buffer (21.7) MB; good for epoch up to #46
2018.05.15:15:13:00.111: GPU11 GPU11: Allocating DAG for epoch #46 (1.36) GB
2018.05.15:15:13:00.113: GPU4 GPU4: Generating DAG for epoch #46
2018.05.15:15:13:00.130: GPU7 GPU7: Allocating DAG for epoch #46 (1.36) GB
2018.05.15:15:13:00.158: GPU11 GPU11: Allocating light cache buffer (21.7) MB; good for epoch up to #46
2018.05.15:15:13:00.226: GPU10 GPU10: Generating DAG for epoch #46
2018.05.15:15:13:00.276: GPU9 GPU9: Generating DAG for epoch #46
2018.05.15:15:13:00.285: GPU7 GPU7: Allocating light cache buffer (21.7) MB; good for epoch up to #46
2018.05.15:15:13:00.328: GPU10 CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77)
2018.05.15:15:13:00.328: GPU11 CUDA error in CudaProgram.cu:102 : an illegal memory access was encountered (700)
2018.05.15:15:13:00.329: GPU10 GPU10 initMiner error: an illegal memory access was encountered
2018.05.15:15:13:00.329: GPU11 GPU11 initMiner error: an illegal memory access was encountered
2018.05.15:15:13:00.332: GPU7 CUDA error in CudaProgram.cu:102 : an illegal memory access was encountered (700)
2018.05.15:15:13:00.332: GPU7 GPU7 initMiner error: an illegal memory access was encountered
2018.05.15:15:13:00.347: GPU2 CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77)
Would welcome any thoughts, I can't seem to find any solutions online.
Russell
I switched from Claymore 11.6 to PhoenixMiner 2.9e due to the DAG and MSWindows 10 issues that prevent the nVidia 1060 3GB cards from working. However for the last 3 weeks I have been getting an illegal memory error:
GPU10 CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77)
2018.05.15:15:13:00.328: GPU11 CUDA error in CudaProgram.cu:102 : an illegal memory access was encountered (700)
To be clear, I can no longer get the nVidia 1060 cards to work with Claymore or PhoenixMiner on ETH or PIRL....
OC'ing the cards seems to be a common cause, but I'm not OCing the cards, I can't even get to the point of doing that...
Rig:
ASRosk HTC110 Mobo
3 AMD 570 gpus
8 nVidia 1060 3 GB GPUs
8 GB RAM
250 GB HD
nvidia driver 376.09 (I've tried 397.64, 397.31 and 388.59)
Virtual Memory - minimum set to 60,000, max set to 160,000.
Set to mine PIRL
2018.05.15:15:12:51.882: main Phoenix Miner 2.9e Windows/msvc - Release
2018.05.15:15:12:51.882: main Cmd line: -pool stratum+tcp://us-west.pirlpool.eu:8002 -wal 0xac1CbCB36704BD0BE0A773cDAFE98c72a70707e2 -pass x -worker CocoSpency -eres 0 -lidag 2
2018.05.15:15:12:56.054: main Available GPUs for mining:
2018.05.15:15:12:56.056: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
2018.05.15:15:12:56.056: main GPU2: GeForce GTX 1060 3GB (pcie 2), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
2018.05.15:15:12:56.056: main GPU3: GeForce GTX 1060 3GB (pcie 3), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
2018.05.15:15:12:56.056: main GPU4: GeForce GTX 1060 3GB (pcie 4), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
2018.05.15:15:12:56.056: main GPU5: GeForce GTX 1060 3GB (pcie 5), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
2018.05.15:15:12:56.056: main GPU6: Radeon RX 570 Series (pcie
, OpenCL 2.0, 4 GB VRAM, 32 CUs2018.05.15:15:12:56.056: main GPU7: GeForce GTX 1060 3GB (pcie 9), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
2018.05.15:15:12:56.056: main GPU8: Radeon RX 570 Series (pcie 11), OpenCL 2.0, 4 GB VRAM, 32 CUs
2018.05.15:15:12:56.056: main GPU9: GeForce GTX 1060 3GB (pcie 12), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
2018.05.15:15:12:56.056: main GPU10: GeForce GTX 1060 3GB (pcie 13), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
2018.05.15:15:12:56.056: main GPU11: GeForce GTX 1060 3GB (pcie 14), CUDA cap. 6.1, 3 GB VRAM, 9 CUs
....
2018.05.15:15:12:57.540: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xba59fa1663dc115be208375f438f043e803c155ca857d96f214b11bf619d853f","0xd6a8400b7f4cc5e082e8239662ed0ee7162892f74016107a7586195f4d591efb","0x0225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"]}
2018.05.15:15:12:57.541: eths Eth: New job #ba59fa16 from us-west.pirlpool.eu:8002; diff: 2000MH
2018.05.15:15:12:57.542: GPU2 GPU2: Starting up... (0)
2018.05.15:15:12:57.542: GPU2 Eth: Generating light cache for epoch #46
2018.05.15:15:12:57.544: GPU3 GPU3: Starting up... (0)
2018.05.15:15:12:57.546: GPU4 GPU4: Starting up... (0)
2018.05.15:15:12:57.548: GPU5 GPU5: Starting up... (0)
2018.05.15:15:12:57.550: GPU7 GPU7: Starting up... (0)
2018.05.15:15:12:57.552: GPU9 GPU9: Starting up... (0)
2018.05.15:15:12:57.554: GPU10 GPU10: Starting up... (0)
2018.05.15:15:12:57.556: GPU11 GPU11: Starting up... (0)
2018.05.15:15:12:57.558: GPU1 GPU1: Starting up... (0)
2018.05.15:15:12:57.560: GPU6 GPU6: Starting up... (0)
2018.05.15:15:12:57.562: GPU8 GPU8: Starting up... (0)
2018.05.15:15:12:59.482: GPU4 GPU4: Allocating DAG for epoch #46 (1.36) GB
2018.05.15:15:12:59.608: GPU4 GPU4: Allocating light cache buffer (21.7) MB; good for epoch up to #46
2018.05.15:15:12:59.652: GPU2 GPU2: Allocating DAG for epoch #46 (1.36) GB
2018.05.15:15:12:59.716: GPU2 GPU2: Allocating light cache buffer (21.7) MB; good for epoch up to #46
2018.05.15:15:12:59.874: GPU9 GPU9: Allocating DAG for epoch #46 (1.36) GB
2018.05.15:15:12:59.894: GPU10 GPU10: Allocating DAG for epoch #46 (1.36) GB
2018.05.15:15:12:59.949: GPU2 GPU2: Generating DAG for epoch #46
2018.05.15:15:12:59.958: GPU10 GPU10: Allocating light cache buffer (21.7) MB; good for epoch up to #46
2018.05.15:15:12:59.959: GPU9 GPU9: Allocating light cache buffer (21.7) MB; good for epoch up to #46
2018.05.15:15:13:00.111: GPU11 GPU11: Allocating DAG for epoch #46 (1.36) GB
2018.05.15:15:13:00.113: GPU4 GPU4: Generating DAG for epoch #46
2018.05.15:15:13:00.130: GPU7 GPU7: Allocating DAG for epoch #46 (1.36) GB
2018.05.15:15:13:00.158: GPU11 GPU11: Allocating light cache buffer (21.7) MB; good for epoch up to #46
2018.05.15:15:13:00.226: GPU10 GPU10: Generating DAG for epoch #46
2018.05.15:15:13:00.276: GPU9 GPU9: Generating DAG for epoch #46
2018.05.15:15:13:00.285: GPU7 GPU7: Allocating light cache buffer (21.7) MB; good for epoch up to #46
2018.05.15:15:13:00.328: GPU10 CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77)
2018.05.15:15:13:00.328: GPU11 CUDA error in CudaProgram.cu:102 : an illegal memory access was encountered (700)
2018.05.15:15:13:00.329: GPU10 GPU10 initMiner error: an illegal memory access was encountered
2018.05.15:15:13:00.329: GPU11 GPU11 initMiner error: an illegal memory access was encountered
2018.05.15:15:13:00.332: GPU7 CUDA error in CudaProgram.cu:102 : an illegal memory access was encountered (700)
2018.05.15:15:13:00.332: GPU7 GPU7 initMiner error: an illegal memory access was encountered
2018.05.15:15:13:00.347: GPU2 CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77)
Would welcome any thoughts, I can't seem to find any solutions online.
Russell
Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
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.
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#msg31966965
Appreciate the thought - I've reviewed that thread. The problem here is that the GPUs are not OC'ed at all and the errors are thrown right after starting the miner, so the nvidia GPUs never have a chance to start mining.
Likely just the overclock setting needs to be lowered...
Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
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.
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?
Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
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.
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.
All - The following is my email exchange with ASRock support. Thought it may be helpful to others. The 'hack' below did NOT work for me. I had to roll back to an earlier build AND had to do the hack.
Rig:
H110ProBTC+
Trying to build 12 GPU rig, can only get 7 cards running
8 - 1060 EVGA GTX GPUs
8 GB RAM
Windows 10 Pro 1709
I am still having issues with this motherboard. I have a somewhat bizarre situation.
Regardless of the number of GPUs I have installed in the MB, device manager throws a code 43 on the 3rd from the bottom in the device manager list. Meaning, if I have 10 cards installed, the 8th card is not working and shows code 43. If I only have 6 cards installed, then the 4 the card throws the code.
I've used DDU to uninstall and then reinstall Nvidia's drivers at least 4 times.
Thoughts?
ASRock Support:
This issue is related to newer OS version, Windows 10 RS3 (1709) 16299 build.
If using previous Windows OS version, RS2 (1703) or RS1 (1607), the issue would not exist.
May also try work around with registry trick (see below for detail) to check. Otherwise, please use previous Windows version.
However, we recommend user to use previous Windows 10 version for their system.
(work around with regedit) code 12/43
However, may give it a try with registry trick below to check if it worked. Otherwise, please use Windows 10 RS2 or RS1.
Click the Start button, type regedit in the Start Search box, and then click regedit in the Programs list.
User Access Control permission If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
Locate the following registry subkey, and then click it:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PnP\Pci
If the HackFlags registry entry is not present, follow these steps:
On the Edit menu, point to New, and then click DWORD (32-bit) Value.
Type HackFlags, and then press ENTER.
On the Edit menu, click Modify.
In the Value data box, type 0x600, click Hexadecimal in the Base area, and then click OK.
Exit Registry Editor.
If the HackFlags registry entry is present, follow these steps:
Right-click HackFlags, and then click Modify.
In the Value data box, type 0x600, click Hexadecimal in the Base area, and then click OK.
Exit Registry Editor.
Rig:
H110ProBTC+
Trying to build 12 GPU rig, can only get 7 cards running
8 - 1060 EVGA GTX GPUs
8 GB RAM
Windows 10 Pro 1709
I am still having issues with this motherboard. I have a somewhat bizarre situation.
Regardless of the number of GPUs I have installed in the MB, device manager throws a code 43 on the 3rd from the bottom in the device manager list. Meaning, if I have 10 cards installed, the 8th card is not working and shows code 43. If I only have 6 cards installed, then the 4 the card throws the code.
I've used DDU to uninstall and then reinstall Nvidia's drivers at least 4 times.
Thoughts?
ASRock Support:
This issue is related to newer OS version, Windows 10 RS3 (1709) 16299 build.
If using previous Windows OS version, RS2 (1703) or RS1 (1607), the issue would not exist.
May also try work around with registry trick (see below for detail) to check. Otherwise, please use previous Windows version.
However, we recommend user to use previous Windows 10 version for their system.
(work around with regedit) code 12/43
However, may give it a try with registry trick below to check if it worked. Otherwise, please use Windows 10 RS2 or RS1.
Click the Start button, type regedit in the Start Search box, and then click regedit in the Programs list.
User Access Control permission If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
Locate the following registry subkey, and then click it:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PnP\Pci
If the HackFlags registry entry is not present, follow these steps:
On the Edit menu, point to New, and then click DWORD (32-bit) Value.
Type HackFlags, and then press ENTER.
On the Edit menu, click Modify.
In the Value data box, type 0x600, click Hexadecimal in the Base area, and then click OK.
Exit Registry Editor.
If the HackFlags registry entry is present, follow these steps:
Right-click HackFlags, and then click Modify.
In the Value data box, type 0x600, click Hexadecimal in the Base area, and then click OK.
Exit Registry Editor.