Bitcoin Forum
June 15, 2021, 07:56:51 AM *
News: Latest Bitcoin Core release: 0.21.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 [85] 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 ... 457 »
  Print  
Author Topic: PhoenixMiner 5.6d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)  (Read 662793 times)
roptix
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
May 02, 2018, 08:26:47 PM
 #1681

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?
1623743811
Hero Member
*
Offline Offline

Posts: 1623743811

View Profile Personal Message (Offline)

Ignore
1623743811
Reply with quote  #2

1623743811
Report to moderator
1623743811
Hero Member
*
Offline Offline

Posts: 1623743811

View Profile Personal Message (Offline)

Ignore
1623743811
Reply with quote  #2

1623743811
Report to moderator
1623743811
Hero Member
*
Offline Offline

Posts: 1623743811

View Profile Personal Message (Offline)

Ignore
1623743811
Reply with quote  #2

1623743811
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1623743811
Hero Member
*
Offline Offline

Posts: 1623743811

View Profile Personal Message (Offline)

Ignore
1623743811
Reply with quote  #2

1623743811
Report to moderator
alex_semi
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
May 02, 2018, 08:31:23 PM
 #1682


VirusTotal shows 14/16 AVs detecting malware in PhoenixMiner 2.9e.

Something to be concerned about? 2.9d was fine.

https://www.virustotal.com/en/file/a531b7b0bb925173d3ea2976b72f3d280f64751bdb094d5bb980553dfa85fb07/analysis/

lesjokolat
Jr. Member
*
Offline Offline

Activity: 115
Merit: 3


View Profile
May 02, 2018, 08:39:43 PM
 #1683

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

Likely just the overclock setting needs to be lowered...
Iamtutut
Full Member
***
Offline Offline

Activity: 1106
Merit: 128


View Profile
May 02, 2018, 08:46:31 PM
 #1684

Indeed, memory errors result in general from too much OC.
roptix
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
May 02, 2018, 08:58:03 PM
 #1685

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...
lesjokolat
Jr. Member
*
Offline Offline

Activity: 115
Merit: 3


View Profile
May 02, 2018, 09:11:17 PM
 #1686

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.
human75
Newbie
*
Offline Offline

Activity: 51
Merit: 0


View Profile
May 02, 2018, 09:41:47 PM
 #1687

One of my rigs stopped mining earlier today. Turned out it was Windows Defender that moved the PhoenixMiner.exe into the quarantine categorised as "Trojan:Win32/Tilken.B!cl"
Did restore the .exe and disabled Windows Defender. The threat in my opinion is Windows Defender, not the miner.

Windows Defender Details:
Trojan:Win32/Tilken.B!cl
Alert level: Severe
Status: Active
Date: 02/05/2018
Recommended action: Remove threat now.

Category: Trojan
Details: This program is dangerous and executes commands from an attacker.

Affected items:
file: C:\dev\Ethereum\PhoenixMiner_2.9e\PhoenixMiner.exe
process: pid:10100,ProcessStart:131683638871312779
You should not use any AV. included WD.
That's really bad advice.
Just configure your AV to exclude certain directories that your miners are located.

it is extremely good advice if your rig only for mining.but if you use your pc as a miner than yes.you should use av and exclude your miner.
Bigdrago
Newbie
*
Offline Offline

Activity: 312
Merit: 0


View Profile
May 02, 2018, 10:59:46 PM
 #1688

So... whats the best miner? This one or claymore 11.7 with nofee or fee enabled?
wtfonly16
Full Member
***
Offline Offline

Activity: 286
Merit: 105


View Profile
May 03, 2018, 12:07:25 AM
 #1689

this have claymore source in it i found it. it a timebomb that will mess with Gpu voltage to Blowed it
there is no phoenix, this was made by claymore to further his Strength in claymore miner monopoly.
after he explode all gpu, no one will ever use any other miner but claymore.

i will release my proof in 48 hours.

ye i aint bares
4ward
Member
**
Offline Offline

Activity: 476
Merit: 18


View Profile
May 03, 2018, 05:48:37 AM
 #1690

this have claymore source in it i found it. it a timebomb that will mess with Gpu voltage to Blowed it
there is no phoenix, this was made by claymore to further his Strength in claymore miner monopoly.
after he explode all gpu, no one will ever use any other miner but claymore.

i will release my proof in 48 hours.

No no no, it's the Russian Federal Security service planted a hidden virus to get rid of western capitalist miners!

I will not release a proof because I'm afraid of the Russian government!

PhoenixMiner
Member
**
Offline Offline

Activity: 338
Merit: 68


View Profile
May 03, 2018, 06:40:10 AM
 #1691

Hello all,
I'm trying my hand at Whale Coin mining, but I can't seem to connect to the server.  Please help.  Here's the config.txt, please let me know if you see anything funky.  The same general configuration seems to work on ethermine.org. (for eth, obviously.)  Thanks in advance.

config.txt:

-pool stratum+tcp://whale.minerpool.net:8008
-pool2 http://whale.minerpool.net:8888
-wal 0x51312ad92329C2887e0b14d24a5Ac8a9Bc21c80E
-worker Miner49er
-pass x
-coin whale
-proto 1
-cdmport 3333
-cdm 2
  Remove the -proto 1 from your config.txt - minerpool uses eth-proxy stratum protocol, which is the default protocol for PhoenixMiner.

Code:
2018.04.29:20:37:58.645: GPU2 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.29:20:37:58.645: GPU2 GPU2 search error: unspecified launch failure
2018.04.29:20:37:58.674: GPU1 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.29:20:37:58.674: GPU1 GPU1 search error: unspecified launch failure
2018.04.29:20:37:58.791: wdog Thread(s) not responding. Restarting.
2018.04.29:20:38:02.402: main Eth speed: 57.008 MH/s, shares: 21/0/0, time: 0:20
2018.04.29:20:38:02.402: main GPUs: 1: 24.358 MH/s (14) 2: 32.650 MH/s (7)

I got this error on Gigabyte WF OC 1070 every 5~20 minutes running 2.9e
Phoenix is 2.9e .3mh/s faster than Claymore 11.7, but claymore can run at least 5 hours before hit "unspecified launch failure" error.
Is it because Phoenix runs at higher intensity than claymore?
I cannot use -dcri option to tune nVidia cards in claymore? Can I fine tune nVidia card at the miner startup (command options)?
  Please try using -nvnew 0 in the command-line (or in config.txt file if you are using it). This will revert to the old CUDA kernels. Please let us know if this fixes the problem (it is not the best fix as it will lower the hashrate and increase the stale shares but we need to know if the problem persists with the old kernels). -gt (and -dcri) is only for AMD cards, at least until we implement dual mining.


hello,

i have to say, i like this miner very much, but have 1 problem.

i have rig with 12 x rx580 cards,

i set parameter -minfan 90  , but it doesnt work, fans still work as default

any advice ?

thanks
   If you are using the blockchain beta drivers (or any driver older than 18.x.x) all bets are off - these drivers has quite buggy ADL implementation. If you are using 18.x.x drivers, please check the log for set auto fan speed: message or Unable to set auto fan speed, or fanmin (xx) is bigger than fanmax warnings.


Hello, I'm using 2 RX 580 GPUs

When I use -clKernel 0
The hash rate moves up & down, most of time it is showing 64 MH/s, sometimes go down to 58 MH/s
The average 5 min. is just above 58 MH/s

When I use -clKernel 1
The hash rate is more stable, most of the time is 60 MH/s sometimes go down to 59.7 or so
The average 5 min. is about 59.8

With kernel 0, looking at it, the average appears to be over 62 MH/s
What I must believe the 5min. average or what I see on the screen?
Could the average 5 min. with kernel 0 be wrong?

& why just after starting miner it tell me the 5 min. average when I have been only mining for 1 min. or even less?

Thank you.
  The 5 min average obviously is not very accurate until at least 5 minutes have passed. If the DAG generation is slow then you should wait for at least 5 minutes after the DAGs are generated before checking the average speed. Finally, the 5 min average speed is better indicator for the speed than the momentary speed (which is also averaged but only over 15 seconds by default).


Uh ..

Eth: Accepted shares 49778 (276 stales), rejected shares 3 (0 stales)
Eth: Incorrect shares 4 (0.01%), est. stales percentage 0.55%
Eth: Maximum difficulty of found share: 33297.4 TH (!!!)


Max share difficulty of 33000?  So 10x the network difficulty of 3200 TH?
There is a very very very slim chance that rig found a block, but 33297 seems more like a software calculation error :/
  No, there is no error, you have found a block. The probability of finding solution with such difficulty is low but it isn't zero. You can check the logs and find when exactly you have submitted this share and then check with ETH blockchain explorer if a block has been found around this time - it should be by your pool.


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.
  We will check with the same driver. We only have Vega 56s but the error should be the same for both.


Hello Admin

-stales <n> not working in new version.

Reported Hashrate 0
  Please note that -stales is per-pool setting. If you have several pools in epools.txt, you have to specify STALES: 0 for each of them otherwise, it will submit stale shares as this is the default. The option to disable reporting hashrate to the pool is -rate 0 and it is global, i.e. it affects all pools.


hi,

there is one more problem,
for pausing a single gpu, i press 1..9, but what if i have more then 10 gpus, and i need to pause #12 ?

thanks
  Press 010 for GPU10, 011 for GPU11, etc. This is key 0, followed by key 1, followed by key 0.


Hi PM developers. I have caught 719 error again two times
...
I use PM 2.9e with the following params

set miner_params=-nvidia -cdm 2 -cdmport 3333 -cdmpass 123 -minRigSpeed 188 -rmode 2 -tstop 65 -tstart 40 -logsmaxsize 0

Rig configuration in my footer.
   Please try to use -nvnew 0 and see if the error happens with the old CUDA kernels. We have some suspicions what may be the reason but so far we were neither able to reproduce it, nor to pinpoint any definitive cause like job switching or something else that could cause these crashes.  If -nvnew 0 doesn't help, please try adding -nvf 2 (along with -nvnew 0).

  We have tried contacting the anti-virus makers about this, and one actually responded (Kasperski) and "un-flagged" the first release but it become apparent that we would need to go through this process every time, as their automated scanning algorithms doesn't like any program that uses advanced anti-debugging techniques. We don't have the time and resources to submit each new release for manual review and wait for the result, so it is what it is. You can be sure that the executable is clean if you have downloaded from the link in the first post, and if you want to be absolutely sure, check if the .zip checksums match these that are listed in the first post.


I think the "Every 5 seconds" shown speed or the average 5 min. are wrong.
With my 2 x RX580 & -clKernel 0
I have been looking carefully for some 15 min. periods, at the screen I see:

70 % of time 64+ MH/s (rarely up to 65)
15 % 62 MH/s
15 % 58.1-58.2

The average 5 min. shown is 57.9 to 58 after 15 min., lowest than the lowest 5 seconds speed.
Also the average goes lower within time while the 5 sec. are the same.
I think the same happens with Kernel 1 but differences are small & it is harder to know for sure, I have not tested it carefully yet.

Looks like the 5 min. average is metering the lowest H/s or I don't know what.

More:

I checked it again this time for more than 30 min.

The lowest 5 sec. have never been below 58.15 (Most of time between 58.2+ & 64.7+) while the highest average 5 min. have never reached 58.1 MH/s (58.08 at most, usually below 58).
So, something is not OK.
   -clkernel 0 is actually the slowest version of the kernels that aren't optimized for any particular GPU, so you should believe the average setting (and it is more accurate than the momentary most of the time). We haven't tested much with -clkernel 0 but such large discrepancies between the momentary and average speed are unusual and are indicators that your hashrate is quite unstable. Use the parameter -gswin 0 to see the real momentary hashrate (not averaged over 15 seconds as default) and you will probably see it jumping wildly with -clkernel 0.


One of my rigs stopped mining earlier today. Turned out it was Windows Defender that moved the PhoenixMiner.exe into the quarantine categorised as "Trojan:Win32/Tilken.B!cl"
Did restore the .exe and disabled Windows Defender. The threat in my opinion is Windows Defender, not the miner.

Windows Defender Details:
Trojan:Win32/Tilken.B!cl
Alert level: Severe
Status: Active
Date: 02/05/2018
Recommended action: Remove threat now.

Category: Trojan
Details: This program is dangerous and executes commands from an attacker.

Affected items:
file: C:\dev\Ethereum\PhoenixMiner_2.9e\PhoenixMiner.exe
process: pid:10100,ProcessStart:131683638871312779
  A less radical solution is to add the folder that contains PhoenixMiner.exe to the list of exclusions of Windows Defender. In this way you can both mine and have Windows Defender turned on.


when phoenix in hive os???
   Whenever we finish the long-awaited Linux version.


Who can say - why sometimes speed 1 of cards drops from 31M to 25M untill restarting miner?
   Sometimes it is just Windows messing with one GPU (probably the active one, if you have a display or display-emulating "plug" in it). In such cases the hashrate recovers within few minutes.


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?
  Please send us the log file from the start to the occurrence of the error (it should happen in the first minute or so when creating the DAG).


this have claymore source in it i found it. it a timebomb that will mess with Gpu voltage to Blowed it
there is no phoenix, this was made by claymore to further his Strength in claymore miner monopoly.
after he explode all gpu, no one will ever use any other miner but claymore.

i will release my proof in 48 hours.
   Dude, check your calendar, April 1th was two months ago.   Grin  While it is tempting to think that you are paid shill, the reality most probably is that you are too emotionally invested in Claymore's miner and you are posting this BS for free. Whatever the reason, please GTFO with your FUD.


cynug
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
May 03, 2018, 01:20:08 PM
 #1692

...

Hi PM developers. I have caught 719 error again two times
...
I use PM 2.9e with the following params

set miner_params=-nvidia -cdm 2 -cdmport 3333 -cdmpass 123 -minRigSpeed 188 -rmode 2 -tstop 65 -tstart 40 -logsmaxsize 0

Rig configuration in my footer.
  Please try to use -nvnew 0 and see if the error happens with the old CUDA kernels. We have some suspicions what may be the reason but so far we were neither able to reproduce it, nor to pinpoint any definitive cause like job switching or something else that could cause these crashes.  If -nvnew 0 doesn't help, please try adding -nvf 2 (along with -nvnew 0).

...

Hi All,

Got this error too using 2.9e while 2.7c and 2.8c were stable with same settings (nvidia rig 5 x 1060 6GB + 1 x 1080 ti / OhGodAnETHlargementPill).

It seems I solved it lowering mining intensity of new nvidia kernels back to 10 using -nvnew 1 -mi 10 -nvf 2 : 2.9e running stable for 24h now

-nvnew 1 -nvf 2 didn't solved it

-nvnew 1 -mi 11 -nvf 2 neither

-nvnew 1 -mi 10 -nvf 2 seems to be OK

Didn't tried -mi 10 alone but may be OK ...

Note: didn't noticed significant hashrate drop using -mi 10 vs default (-mi 12 AFAIK)


DireWolfM14
Legendary
*
Offline Offline

Activity: 1134
Merit: 2283


Join the world-leading crypto sportsbook NOW!


View Profile
May 03, 2018, 04:48:02 PM
 #1693

Dr. Phoenix,
Thanks a bunch, I'll try that tonight.  But mostly I want to thank you for the product.  Low fees, great hash rate, and it was easy enough for me to figure out, and I haven't messed with DOS or UNIX commands in years.  I won't say how many years, but suffice it to say it's been many.

Remove the -proto 1 from your config.txt - minerpool uses eth-proxy stratum protocol, which is the default protocol for PhoenixMiner.

UnclWish
Sr. Member
****
Offline Offline

Activity: 1414
Merit: 253


View Profile
May 03, 2018, 04:52:05 PM
 #1694

Who can say - why sometimes speed 1 of cards drops from 31M to 25M untill restarting miner?
  Sometimes it is just Windows messing with one GPU (probably the active one, if you have a display or display-emulating "plug" in it). In such cases the hashrate recovers within few minutes.
Yes, this is the active GPU with display connected in it. But speed didn't restores in 5 minutes... It's too long. Average speed drops significunt for me. It's need to do something with that. Until that I'll use Claymore miner, in wich no such problem...
gsrcrxsi314
Member
**
Offline Offline

Activity: 367
Merit: 34


View Profile
May 03, 2018, 08:08:08 PM
 #1695

still getting the random CUDA crashing on one of my nvidia rigs with anything newer than 2.8c. PM doesnt restart properly and just hangs with a windows error.

manual restart is possible, but hashrates on certain cards gets severly reduced.

only proper fix is full reboot.

works perfectly and will run hundreds of hours on 2.8c without an issue.
  Is there any difference in the behavior if you specify -nvnew 0 (i.e. using the old kernels) on PhoenixMiner 2.9e?

just had a chance to test this. it seemed better running -nvnew 0, however i did have an overnight crash, and one card seemed to have lost its OC, but at least the miner restarted itselt and didnt just hang in windows.

went back to 2.8c again.
sandbagger
Newbie
*
Offline Offline

Activity: 18
Merit: 0


View Profile
May 03, 2018, 08:18:08 PM
 #1696

Phoenix

still having crashes  719 error

I have narrowed it down to restarts after a crash, but the crash is actually a loss of power reboot as we have been having some storms in the area.

it always comes up with the dialog box saying miner has stopped working.  Some times even after clicking that it will still not close the window and some times it will but then it output a few more lines about to restart press any key

some times it will crash almost instantly like this log, other times it will run for 3-7minutes or so
reboot does not help and shutting down for 15+min wont get it to restart clean
only thing that I have found that will get it to restart and stay running is I need to start one instance up, let it build diag completely then start a 2nd instance once that starts building diag I then kill the first window

never had this problem with the older version
PhoenixMiner.exe -pool ssl://us1.ethermine.org:5555 -pool2 ssl://us2.ethermine.org:5555 -wal 0xXXXXXXXXXXX -proto 3 -nvidia -minRigSpeed 395



Code:
2018.05.03:16:02:56.673: main Phoenix Miner 2.9e Windows/msvc - Release
2018.05.03:16:02:56.673: main Cmd line: -pool ssl://us1.ethermine.org:5555 -pool2 ssl://us2.ethermine.org:5555 -wal 0xCccc952DF9570974f180501a90FA8f308e3ec5a9.sandbagger -proto 3 -nvidia -minRigSpeed 395
2018.05.03:16:02:59.233: main Available GPUs for mining:
2018.05.03:16:02:59.233: main GPU1: GeForce GTX 1070 (pcie 1), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2018.05.03:16:02:59.233: main GPU2: GeForce GTX 1070 (pcie 4), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2018.05.03:16:02:59.233: main GPU3: GeForce GTX 1070 (pcie 5), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2018.05.03:16:02:59.233: main GPU4: GeForce GTX 1070 (pcie 6), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2018.05.03:16:02:59.233: main GPU5: GeForce GTX 1070 (pcie 9), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2018.05.03:16:02:59.233: main GPU6: GeForce GTX 1070 (pcie 10), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2018.05.03:16:02:59.233: main GPU7: GeForce GTX 1070 (pcie 11), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2018.05.03:16:02:59.233: main GPU8: GeForce GTX 1070 (pcie 12), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2018.05.03:16:02:59.233: main GPU9: GeForce GTX 1070 (pcie 13), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2018.05.03:16:02:59.233: main GPU10: GeForce GTX 1070 (pcie 14), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2018.05.03:16:02:59.233: main GPU11: GeForce GTX 1070 (pcie 15), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2018.05.03:16:02:59.233: main GPU12: GeForce GTX 1070 (pcie 16), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2018.05.03:16:02:59.233: main GPU13: GeForce GTX 1070 (pcie 17), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2018.05.03:16:02:59.238: main NVML library initialized
2018.05.03:16:02:59.504: main Listening for CDM remote manager at port 3333 in read-only mode
2018.05.03:16:02:59.505: main Eth: the pool list contains 4 pools
2018.05.03:16:02:59.505: main Eth: primary pool: ssl://us1.ethermine.org:5555
2018.05.03:16:02:59.505: main Starting GPU mining
2018.05.03:16:02:59.506: wdog Starting watchdog thread
2018.05.03:16:02:59.665: main Eth: Connecting to ethash pool ssl://us1.ethermine.org:5555 (proto: QtMiner)
2018.05.03:16:02:59.727: eths Eth: Connected to SSL ethash pool us1.ethermine.org:5555 (18.219.59.155)
2018.05.03:16:02:59.810: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_login","params":["0xCccc952DF9570974f180501a90FA8f308e3ec5a9.sandbagger"]}

2018.05.03:16:02:59.844: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2018.05.03:16:02:59.844: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.05.03:16:02:59.870: main GPU1: 48C 38%, GPU2: 47C 37%, GPU3: 53C 48%, GPU4: 45C 34%, GPU5: 51C 44%, GPU6: 53C 48%, GPU7: 51C 46%, GPU8: 48C 37%, GPU9: 47C 35%, GPU10: 52C 46%, GPU11: 51C 44%, GPU12: 55C 50%, GPU13: 45C 32%
2018.05.03:16:02:59.879: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x851abe051d6e7059918f7e617bb9e936c60868a26c1cacbc29d9076f1a6f055b","0xad15d04b13b18ecbb6bc1c05cefa1e952fe584f2c79fb5f3dbc48656704b0f95","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x54b33f"]}
2018.05.03:16:02:59.879: eths Eth: New job #851abe05 from ssl://us1.ethermine.org:5555; diff: 4000MH
2018.05.03:16:02:59.879: GPU1 GPU1: Starting up... (0)
2018.05.03:16:02:59.879: GPU1 Eth: Generating light cache for epoch #185
2018.05.03:16:02:59.884: GPU2 GPU2: Starting up... (0)
2018.05.03:16:02:59.884: GPU3 GPU3: Starting up... (0)
2018.05.03:16:02:59.899: GPU4 GPU4: Starting up... (0)
2018.05.03:16:02:59.899: GPU5 GPU5: Starting up... (0)
2018.05.03:16:02:59.915: GPU6 GPU6: Starting up... (0)
2018.05.03:16:02:59.931: GPU7 GPU7: Starting up... (0)
2018.05.03:16:02:59.931: GPU8 GPU8: Starting up... (0)
2018.05.03:16:02:59.946: GPU9 GPU9: Starting up... (0)
2018.05.03:16:02:59.946: GPU10 GPU10: Starting up... (0)
2018.05.03:16:02:59.947: GPU11 GPU11: Starting up... (0)
2018.05.03:16:02:59.947: GPU12 GPU12: Starting up... (0)
2018.05.03:16:02:59.962: GPU13 GPU13: Starting up... (0)
2018.05.03:16:03:02.120: GPU1 GPU1: Allocating DAG (2.46) GB; good for epoch up to #187
2018.05.03:16:03:02.903: GPU1 GPU1: Allocating light cache buffer (39.4) MB; good for epoch up to #187
2018.05.03:16:03:03.051: GPU6 GPU6: Allocating DAG (2.46) GB; good for epoch up to #187
2018.05.03:16:03:03.131: GPU11 GPU11: Allocating DAG (2.46) GB; good for epoch up to #187
2018.05.03:16:03:03.157: GPU13 GPU13: Allocating DAG (2.46) GB; good for epoch up to #187
2018.05.03:16:03:03.239: GPU13 GPU13: Allocating light cache buffer (39.4) MB; good for epoch up to #187
2018.05.03:16:03:03.271: GPU6 GPU6: Allocating light cache buffer (39.4) MB; good for epoch up to #187
2018.05.03:16:03:03.275: GPU11 GPU11: Allocating light cache buffer (39.4) MB; good for epoch up to #187
2018.05.03:16:03:03.358: GPU9 GPU9: Allocating DAG (2.46) GB; good for epoch up to #187
2018.05.03:16:03:03.385: GPU12 GPU12: Allocating DAG (2.46) GB; good for epoch up to #187
2018.05.03:16:03:03.481: GPU13 GPU13: Generating DAG for epoch #185
2018.05.03:16:03:03.620: GPU2 GPU2: Allocating DAG (2.46) GB; good for epoch up to #187
2018.05.03:16:03:03.736: GPU6 GPU6: Generating DAG for epoch #185
2018.05.03:16:03:03.763: GPU9 GPU9: Allocating light cache buffer (39.4) MB; good for epoch up to #187
2018.05.03:16:03:03.764: GPU12 GPU12: Allocating light cache buffer (39.4) MB; good for epoch up to #187
2018.05.03:16:03:03.875: GPU8 GPU8: Allocating DAG (2.46) GB; good for epoch up to #187
2018.05.03:16:03:03.888: GPU7 GPU7: Allocating DAG (2.46) GB; good for epoch up to #187
2018.05.03:16:03:03.893: GPU3 GPU3: Allocating DAG (2.46) GB; good for epoch up to #187
2018.05.03:16:03:03.993: GPU1 GPU1: Generating DAG for epoch #185
2018.05.03:16:03:04.017: GPU2 GPU2: Allocating light cache buffer (39.4) MB; good for epoch up to #187
2018.05.03:16:03:04.018: GPU8 GPU8: Allocating light cache buffer (39.4) MB; good for epoch up to #187
2018.05.03:16:03:04.018: GPU7 GPU7: Allocating light cache buffer (39.4) MB; good for epoch up to #187
2018.05.03:16:03:04.018: GPU3 GPU3: Allocating light cache buffer (39.4) MB; good for epoch up to #187
2018.05.03:16:03:04.111: GPU5 GPU5: Allocating DAG (2.46) GB; good for epoch up to #187
2018.05.03:16:03:04.130: GPU4 GPU4: Allocating DAG (2.46) GB; good for epoch up to #187
2018.05.03:16:03:04.221: GPU9 GPU9: Generating DAG for epoch #185
2018.05.03:16:03:04.221: GPU11 GPU11: Generating DAG for epoch #185
2018.05.03:16:03:04.222: GPU12 GPU12: Generating DAG for epoch #185
2018.05.03:16:03:04.234: GPU5 GPU5: Allocating light cache buffer (39.4) MB; good for epoch up to #187
2018.05.03:16:03:04.234: GPU4 GPU4: Allocating light cache buffer (39.4) MB; good for epoch up to #187
2018.05.03:16:03:04.438: GPU7 GPU7: Generating DAG for epoch #185
2018.05.03:16:03:04.438: GPU8 GPU8: Generating DAG for epoch #185
2018.05.03:16:03:04.443: GPU10 GPU10: Allocating DAG (2.46) GB; good for epoch up to #187
2018.05.03:16:03:04.775: GPU3 GPU3: Generating DAG for epoch #185
2018.05.03:16:03:04.798: GPU5 GPU5: Generating DAG for epoch #185
2018.05.03:16:03:04.799: GPU10 GPU10: Allocating light cache buffer (39.4) MB; good for epoch up to #187
2018.05.03:16:03:04.855: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.05.03:16:03:04.855: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 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)
2018.05.03:16:03:05.007: GPU10 GPU10: Generating DAG for epoch #185
2018.05.03:16:03:05.058: GPU13 GPU13: DAG  19%
2018.05.03:16:03:05.083: GPU4 GPU4: Generating DAG for epoch #185
2018.05.03:16:03:05.085: GPU2 GPU2: Generating DAG for epoch #185
2018.05.03:16:03:05.329: GPU6 GPU6: DAG  19%
2018.05.03:16:03:05.677: GPU1 GPU1: DAG  22%
2018.05.03:16:03:05.727: GPU9 GPU9: DAG  19%
2018.05.03:16:03:05.757: GPU11 GPU11: DAG  19%
2018.05.03:16:03:05.790: GPU12 GPU12: DAG  19%
2018.05.03:16:03:05.979: GPU8 GPU8: DAG  19%
2018.05.03:16:03:06.011: GPU7 GPU7: DAG  19%
2018.05.03:16:03:06.334: GPU5 GPU5: DAG  19%
2018.05.03:16:03:06.481: GPU3 GPU3: DAG  22%
2018.05.03:16:03:06.555: GPU10 GPU10: DAG  19%
2018.05.03:16:03:06.767: GPU13 GPU13: DAG  44%
2018.05.03:16:03:06.773: GPU4 GPU4: DAG  22%
2018.05.03:16:03:06.776: GPU2 GPU2: DAG  22%
2018.05.03:16:03:06.894: GPU6 GPU6: DAG  41%
2018.05.03:16:03:07.290: GPU11 GPU11: DAG  41%
2018.05.03:16:03:07.327: GPU1 GPU1: DAG  47%
2018.05.03:16:03:07.344: GPU12 GPU12: DAG  41%
2018.05.03:16:03:07.439: GPU9 GPU9: DAG  44%
2018.05.03:16:03:07.491: GPU8 GPU8: DAG  41%
2018.05.03:16:03:07.574: GPU7 GPU7: DAG  41%
2018.05.03:16:03:07.849: GPU5 GPU5: DAG  41%
2018.05.03:16:03:08.103: GPU10 GPU10: DAG  41%
2018.05.03:16:03:08.175: GPU3 GPU3: DAG  47%
2018.05.03:16:03:08.447: GPU4 GPU4: DAG  47%
2018.05.03:16:03:08.450: GPU2 GPU2: DAG  47%
2018.05.03:16:03:08.457: GPU6 GPU6: DAG  63%
2018.05.03:16:03:08.469: GPU13 GPU13: DAG  69%
2018.05.03:16:03:08.825: GPU11 GPU11: DAG  63%
2018.05.03:16:03:08.894: GPU12 GPU12: DAG  63%
2018.05.03:16:03:08.977: GPU1 GPU1: DAG  72%
2018.05.03:16:03:09.006: GPU8 GPU8: DAG  63%
2018.05.03:16:03:09.135: GPU7 GPU7: DAG  63%
2018.05.03:16:03:09.150: GPU9 GPU9: DAG  69%
2018.05.03:16:03:09.367: GPU5 GPU5: DAG  63%
2018.05.03:16:03:09.648: GPU10 GPU10: DAG  63%
2018.05.03:16:03:09.822: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.05.03:16:03:09.857: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x851abe051d6e7059918f7e617bb9e936c60868a26c1cacbc29d9076f1a6f055b","0xad15d04b13b18ecbb6bc1c05cefa1e952fe584f2c79fb5f3dbc48656704b0f95","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x54b33f"]}
2018.05.03:16:03:09.866: GPU3 GPU3: DAG  72%
2018.05.03:16:03:09.949: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.05.03:16:03:09.949: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 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)
2018.05.03:16:03:10.019: GPU6 GPU6: DAG  84%
2018.05.03:16:03:10.126: GPU2 GPU2: DAG  72%
2018.05.03:16:03:10.173: GPU13 GPU13: DAG  94%
2018.05.03:16:03:10.361: GPU11 GPU11: DAG  84%
2018.05.03:16:03:10.364: GPU13 GPU13: DAG generated in 6.9 s (363.8 MB/s)
2018.05.03:16:03:10.448: GPU12 GPU12: DAG  84%
2018.05.03:16:03:10.518: GPU8 GPU8: DAG  84%
2018.05.03:16:03:10.606: GPU1 GPU1: DAG  97%
2018.05.03:16:03:10.606: GPU1 GPU1: DAG generated in 6.6 s (378.7 MB/s)
2018.05.03:16:03:10.697: GPU7 GPU7: DAG  84%
2018.05.03:16:03:10.863: GPU9 GPU9: DAG  94%
2018.05.03:16:03:10.881: GPU5 GPU5: DAG  84%
2018.05.03:16:03:10.891: GPU6 GPU6: DAG generated in 7.2 s (350.0 MB/s)
2018.05.03:16:03:11.055: GPU9 GPU9: DAG generated in 6.8 s (366.5 MB/s)
2018.05.03:16:03:11.196: GPU10 GPU10: DAG  84%
2018.05.03:16:03:11.197: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xdc166461fac91f0d30f4f7c455b83b844e89ffbda6fbca5356659d9de1e9a4e3","0xad15d04b13b18ecbb6bc1c05cefa1e952fe584f2c79fb5f3dbc48656704b0f95","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x54b340"]}
2018.05.03:16:03:11.197: eths Eth: New job #dc166461 from ssl://us1.ethermine.org:5555; diff: 4000MH
2018.05.03:16:03:11.215: GPU11 GPU11: DAG generated in 7.0 s (358.1 MB/s)
2018.05.03:16:03:11.313: GPU12 GPU12: DAG generated in 7.1 s (353.1 MB/s)
2018.05.03:16:03:11.365: GPU8 GPU8: DAG generated in 6.9 s (361.6 MB/s)
2018.05.03:16:03:11.520: GPU4 CUDART error in CudaProgram.cu:127 : unspecified launch failure (4)
2018.05.03:16:03:11.520: GPU4 GPU4 initMiner error: unspecified launch failure
2018.05.03:16:03:11.525: GPU3 CUDART error in CudaProgram.cu:127 : unspecified launch failure (4)
2018.05.03:16:03:11.525: GPU13 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.05.03:16:03:11.525: GPU3 GPU3 initMiner error: unspecified launch failure
2018.05.03:16:03:11.525: GPU13 GPU13 search error: unspecified launch failure
2018.05.03:16:03:11.532: GPU5 CUDART error in CudaProgram.cu:127 : unspecified launch failure (4)
2018.05.03:16:03:11.532: GPU5 GPU5 initMiner error: unspecified launch failure
2018.05.03:16:03:11.567: GPU7 CUDART error in CudaProgram.cu:127 : unspecified launch failure (4)
2018.05.03:16:03:11.567: GPU7 GPU7 initMiner error: unspecified launch failure
2018.05.03:16:03:11.572: GPU1 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.05.03:16:03:11.572: GPU1 GPU1 search error: unspecified launch failure
2018.05.03:16:03:11.588: wdog Thread(s) not responding. Restarting.
2018.05.03:16:03:11.588: GPU2 CUDART error in CudaProgram.cu:127 : unspecified launch failure (4)
2018.05.03:16:03:11.588: GPU2 GPU2 initMiner error: unspecified launch failure
2018.05.03:16:03:11.603: GPU10 CUDART error in CudaProgram.cu:127 : unspecified launch failure (4)
2018.05.03:16:03:11.603: GPU10 GPU10 initMiner error: unspecified launch failure
2018.05.03:16:03:11.641: GPU9 CUDA error in CudaProgram.cu:121 : unspecified launch failure (719)
2018.05.03:16:03:11.641: GPU11 CUDA error in CudaProgram.cu:121 : unspecified launch failure (719)
2018.05.03:16:03:11.641: GPU12 CUDA error in CudaProgram.cu:121 : unspecified launch failure (719)
2018.05.03:16:03:11.641: GPU11 GPU11: Failed to initialize search buffers: unspecified launch failure
2018.05.03:16:03:11.641: GPU12 GPU12: Failed to initialize search buffers: unspecified launch failure
2018.05.03:16:03:11.641: GPU11 GPU11 initMiner error: Unable to initialize CUDA miner
2018.05.03:16:03:11.641: GPU12 GPU12 initMiner error: Unable to initialize CUDA miner
2018.05.03:16:03:11.641: GPU9 GPU9: Failed to initialize search buffers: unspecified launch failure
2018.05.03:16:03:11.641: GPU9 GPU9 initMiner error: Unable to initialize CUDA miner
2018.05.03:16:03:11.641: GPU8 CUDA error in CudaProgram.cu:121 : unspecified launch failure (719)
2018.05.03:16:03:11.641: GPU8 GPU8: Failed to initialize search buffers: unspecified launch failure
2018.05.03:16:03:11.641: GPU8 GPU8 initMiner error: Unable to initialize CUDA miner
2018.05.03:16:03:11.642: GPU6 CUDA error in CudaProgram.cu:121 : the launch timed out and was terminated (702)
2018.05.03:16:03:11.642: GPU6 GPU6: Failed to initialize search buffers: the launch timed out and was terminated
2018.05.03:16:03:11.642: GPU6 GPU6 initMiner error: Unable to initialize CUDA miner
2018.05.03:16:03:15.060: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.05.03:16:03:15.060: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 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)

shuweee
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
May 03, 2018, 09:48:41 PM
 #1697

anyone expert in terms of batch file configuration? I'm attempting to use the following windows cmd commands to switch between different wallet address using one single batch file. However it seems to me that once the first phoenix process has started, the timeout command following is no longer working. Any suggestions as to why?

:wallet1
echo Starting Mining Process
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 us2.ethermine.org:4444 -pool2 us1.ethermine.org:14444 -wal <wallet.rigname> -gpus 1234567 -pass x -logfile *
timeout /t 60 <---stopped here>
taskkill /im PhoenixMiner.exe /f /t
goto wallet2

:wallet2
echo Starting Mining Process
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 us2.ethermine.org:4444 -pool2 us1.ethermine.org:14444 -wal <wallet.rigname> -gpus 1234567 -pass x -logfile *
timeout /t 60
taskkill /im PhoenixMiner.exe /f /t
goto wallet1
lesjokolat
Jr. Member
*
Offline Offline

Activity: 115
Merit: 3


View Profile
May 03, 2018, 10:42:43 PM
 #1698

anyone expert in terms of batch file configuration? I'm attempting to use the following windows cmd commands to switch between different wallet address using one single batch file. However it seems to me that once the first phoenix process has started, the timeout command following is no longer working. Any suggestions as to why?

:wallet1
echo Starting Mining Process
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 us2.ethermine.org:4444 -pool2 us1.ethermine.org:14444 -wal <wallet.rigname> -gpus 1234567 -pass x -logfile *
timeout /t 60 <---stopped here>
taskkill /im PhoenixMiner.exe /f /t
goto wallet2

:wallet2
echo Starting Mining Process
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 us2.ethermine.org:4444 -pool2 us1.ethermine.org:14444 -wal <wallet.rigname> -gpus 1234567 -pass x -logfile *
timeout /t 60
taskkill /im PhoenixMiner.exe /f /t
goto wallet1

you just need one bat file for a failover....

PhoenixMiner.exe -pool us2.ethermine.org:4444 -pool2 us1.ethermine.org:14444 -wal <wallet.rigname> -wal2 <wallet.rigname> -gpus 1234567 -pass x -pass2 x -logfile *



-pool2 <host:port>  Failover ethash pool address. Same as -pool but for the failover pool
  -wal2 <wallet> Failover ethash wallet (if missing -wal will be used for the failover pool too)
  -pass2 <password> Failover ethash password (if missing -pass will be used for the failover pool too)
  -worker2 <name> Failover ethash worker name (if missing -worker will be used for the failover pool too)
  -proto2 <n> Failover ethash stratum protocol (if missing -proto will be used for the failover pool too)
  -coin2 <coin> Failover devfee Ethash coin (if missing -coin will be used for the failover pool too)
  -stales2 <n> Submit stales to the failover pool: 1 - yes (default), 0 - no
shuweee
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
May 03, 2018, 11:11:41 PM
 #1699

Not looking for the failover purpose, instead I'm looking to split up the total mining durations into two chunks, 1) mining using first wallet address & when 60 mins is reached flip over to the wallet 2 and mine for x time and back. Sort of like a dev fee idea. Or there maybe a better way to achieve the same thing?

anyone expert in terms of batch file configuration? I'm attempting to use the following windows cmd commands to switch between different wallet address using one single batch file. However it seems to me that once the first phoenix process has started, the timeout command following is no longer working. Any suggestions as to why?

:wallet1
echo Starting Mining Process
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 us2.ethermine.org:4444 -pool2 us1.ethermine.org:14444 -wal <wallet.rigname> -gpus 1234567 -pass x -logfile *
timeout /t 60 <---stopped here>
taskkill /im PhoenixMiner.exe /f /t
goto wallet2

:wallet2
echo Starting Mining Process
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 us2.ethermine.org:4444 -pool2 us1.ethermine.org:14444 -wal <wallet.rigname> -gpus 1234567 -pass x -logfile *
timeout /t 60
taskkill /im PhoenixMiner.exe /f /t
goto wallet1

you just need one bat file for a failover....

PhoenixMiner.exe -pool us2.ethermine.org:4444 -pool2 us1.ethermine.org:14444 -wal <wallet.rigname> -wal2 <wallet.rigname> -gpus 1234567 -pass x -pass2 x -logfile *



-pool2 <host:port>  Failover ethash pool address. Same as -pool but for the failover pool
  -wal2 <wallet> Failover ethash wallet (if missing -wal will be used for the failover pool too)
  -pass2 <password> Failover ethash password (if missing -pass will be used for the failover pool too)
  -worker2 <name> Failover ethash worker name (if missing -worker will be used for the failover pool too)
  -proto2 <n> Failover ethash stratum protocol (if missing -proto will be used for the failover pool too)
  -coin2 <coin> Failover devfee Ethash coin (if missing -coin will be used for the failover pool too)
  -stales2 <n> Submit stales to the failover pool: 1 - yes (default), 0 - no
plastkort
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
May 04, 2018, 12:37:23 AM
 #1700

I am currently mining Callisto, and a self made app to control what coin i want to mine, switching between cryptonight and ethash, however some computers have less than 3gb of video graphics, they often go offline, does Phoenixminer crash if it starts devfee and the card wont support the devfee coin ?

would like an update or fix on this. preferably not a config settings, cause i dont want to update over 60 computers manually when i can update from a json config online Smiley
Pages: « 1 ... 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 [85] 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 ... 457 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!