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

[roptix]

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

[1713920530]

1713920530

[1713920530]

1713920530

[lesjokolat]

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

do you have at least 19 gig virtual memory on your system, might be a reason if its too little.

[roptix]

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

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.

[singlass]

the legendary AMD 15.12 driver triggers the debuging error,make some sort of exception / fix in your next release

[crypper]

I've been using claymore for my RX X80s for over a year now. Decided to give phoenix a go...and I'm damn happy I did: slight improvement in hashrate at the same clocks and power and significant reduction in stale shares! I've been suffering from 5-15% stales (ethermine.org) since Byzantium fork in 2017. With phoenix I have <1% stales.
Great job, man.

Retraction of my previous statement: number of stale shares is marginally lower than claymore's. During the first few hours of running phoenix I indeed had <1% of stales; number increased with time though and as of now I'm back to 5-10% stales.
Bad job, man!

Your 5-10% stale share is arguably bad. With the PH 2.9e, migrated from Claymore 11.5 my stale share rate is slightly higher than on Claymore yet still in the range of 1-3% - varies from day to day.
Stale share is sensitive not only to the miner code but also on the quality of your network speed and latency. Shares are accepted in 40-42ms in my

could you please explain to a noob (me) the difference between network speed and network latency?

You will get the best answer if you Google: network latency definition.

Yeah... no, thanks, I will probably not google, but you should. It's always good to understand what you are talking about (even on the internet).

[cryptodunno]

after a few weeks tests i really like phoenixminer, stale shares are much less comparing the others.
IT would be great to see linux version in nearest future

[Erpelusas]

Will phoenix miner be implemented in hive os?

[En@Ble]

Dev when will new coins appear? such as Egem,Clo ?

[DireWolfM14]

I would love me some nice juicy and fat linux version

    Yes, but hopefully not that fat There is some progress on this but no ETA yet, sorry.

Yes, please keep it lean.    I love windows, shameless about it, too.  But for a "process pc" nothing beats a minimalist linux build.

[esunga903]

Hi phoenix, I have tried your miner and it is very good except for the one that I can't set a single GPU to 50% usage so I can still used it for editing and gaming. At claymore i can do that, any help would be greatly appreciated.

[janding]

Hi phoenix, I have tried your miner and it is very good except for the one that I can't set a single GPU to 50% usage so I can still used it for editing and gaming. At claymore i can do that, any help would be greatly appreciated.

Hilarious 

[gambera]

Hilarious 

Isn't it? 


My recommendation to that user would be, do your editing and gaming and then dedicate the card just for mining. 

[Metroid]

so how can we make the fans here to work the same as claymore? any ideas? if i set -tt 60 and -fanmax 90 in claymore, as long the temperature is higher than -tt 60, the -fanmax 90 will always be at 90%, if temperature is 50c then the fan in claymore is around 0% and jumps to 50% and then 0% again, so how this miner can work the same?

[esunga903]

Hilarious 

Isn't it? 


My recommendation to that user would be, do your editing and gaming and then dedicate the card just for mining. 

at claymore I can edit and do mining at the same time with only 3-5 Mh lost. I'm asking the developer if it possible in phoenix miner.

[nvmaxx]

Trying to get JsonRPC responses from Phoenix, having some serious issues, If someone could tell me what I did wrong on this I would greatly appreciate it, this code works perfectly fine for Claymore's but for PhoenixMiner it doesnt do anything.

Code:

			try
			{
				var clientSocket = new System.Net.Sockets.TcpClient();

				if (clientSocket.ConnectAsync("127.0.0.1", 3337).Wait(5000))
				{
					string get_menu_request = "{\"id\":0,\"jsonrpc\":\"2.0\",\"method\":\"miner_getstat1\"}\n";
					NetworkStream serverStream = clientSocket.GetStream();
					byte[] outStream = System.Text.Encoding.ASCII.GetBytes(get_menu_request);
					serverStream.Write(outStream, 0, outStream.Length);
					serverStream.Flush();

					byte[] inStream = new byte[clientSocket.ReceiveBufferSize];
					serverStream.Read(inStream, 0, (int)clientSocket.ReceiveBufferSize);
					string _returndata = System.Text.Encoding.ASCII.GetString(inStream);

					if (_returndata.Length == 0)
					{
						throw new Exception("Invalid data");
					}

					Console.WriteLine(_returndata);

						
				}
				else
				{

				}
			}
			catch (Exception ex)
			{
				Console.WriteLine(ex.Message);
				Console.WriteLine(ex.StackTrace);
				stats.ex = ex;
				logger.LogWrite("Host socket exception: " + ex.ToString());
			}

Appreciate the help.

[feNDer2k5]

In version 2.9e, after closing the miner such errors:

https://d.radikal.ru/d09/1805/62/a1e05b06891d.jpg

In version 2.8c everything is fine. Video cards 1070 and 1070 Ti.

[simcity4]

Hi
how to solve this
I`m using PhoenixMiner 2.9e and  have this error every 10 min
2018.05.17:19:27:32.267: eths Eth: Unable to read pool response: The semaphore timeout period has expired
2018.05.17:19:27:32.267: eths Eth: Reconnecting in 20 seconds...

[Denis1916]

how it works
-gpus <123 ..n> Use only the specified GPUs

write
-gpus <1235>

and "file not found"

[pinamalina]

how it works
-gpus <123 ..n> Use only the specified GPUs

write
-gpus <1235>

and "file not found"

Use as:
-gpus 1235
It will use only cards 1, 2, 3 and 5 and will ignore all other cards. e..g. card 4, 6, ...

The "<>" stands as a standard placeholder indicating a mandatory parameter/option.
For example "[]" would indicate an optional parameter.

[pinamalina]

Hi
how to solve this
I`m using PhoenixMiner 2.9e and  have this error every 10 min
2018.05.17:19:27:32.267: eths Eth: Unable to read pool response: The semaphore timeout period has expired
2018.05.17:19:27:32.267: eths Eth: Reconnecting in 20 seconds...

This would be a result of unstable internet connection. Make sure your router/access point is not rebooting periodically and your PC has a stable internet connection.
The miner connects to the pool and keeps a connection alive at all times. When your network drops the connection is lost and miner will not really reconnect but establish a new connection.
In some rare cases it could also be an ISP problem with the upstream network.
Check the event viewer, these should be a clear message from Windows indicating a connection drop.