Quote from: roptix on May 02, 2018, 08:58:03 PM

Quote from: lesjokolat on May 02, 2018, 08:39:43 PM

Quote from: roptix on May 02, 2018, 08:26:47 PM

Quote from: Iamtutut on May 02, 2018, 06:04:39 PM

Quote from: roptix on May 02, 2018, 04:48:53 PM

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#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...

I see you have both AMD and Nvidia may have to do -asm 1,3,4, etc then teh equivlaent for Nvidias. Maybe try different Kernels.. (check read me to try diff kernels..) Sometimes older kernels work vs new ones.. you can mix and match old and new as well.