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

sandbagger

newbie

Activity: 18

Merit: 0

since updating to 2.9E I have gotten a random CUDA error on my nvidia 1070 rig, doesnt restart properly and just hangs with a windows error.

I didnt have time this morning to look hard at the log file but a close of the window and relaunch was all it needed

it had been running about 4days(lost power due to storms) with no issues and seems that a few people have had the same problem.

j2james

newbie

Activity: 80

Merit: 0

Hi. I also have error "unspecified launch failure (719)".

I have never seen that before.

Code:

2018.04.22:18:14:02.410: main Eth speed: 192.457 MH/s, shares: 9720/9/1, time: 143:42
2018.04.22:18:14:02.410: main GPUs: 1: 32.082 MH/s (1634) 2: 32.079 MH/s (1632/1) 3: 32.071 MH/s (1621) 4: 32.079 MH/s (1616) 5: 32.079 MH/s (1629) 6: 32.067 MH/s (1597)
2018.04.22:18:14:07.511: main Eth speed: 192.456 MH/s, shares: 9720/9/1, time: 143:42
2018.04.22:18:14:07.511: main GPUs: 1: 32.082 MH/s (1634) 2: 32.080 MH/s (1632/1) 3: 32.071 MH/s (1621) 4: 32.079 MH/s (1616) 5: 32.078 MH/s (1629) 6: 32.067 MH/s (1597)
2018.04.22:18:14:07.714: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.22:18:14:07.750: GPU3 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.22:18:14:07.769: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xfeea3f97d27b908fa7b3322ae0f78c59b58a2c719acfcfb9a808c481d318a843","0x5683748fa7f53897f1e1a80a8a321d3693761838135be37d1d132c0cd3d7d937","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.22:18:14:07.791: GPU1 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.22:18:14:07.801: GPU3 GPU3 search error: unspecified launch failure
2018.04.22:18:14:07.801: GPU1 GPU1 search error: unspecified launch failure
2018.04.22:18:14:07.807: GPU4 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.22:18:14:07.807: GPU4 GPU4 search error: unspecified launch failure
2018.04.22:18:14:07.807: GPU5 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.22:18:14:07.807: GPU5 GPU5 search error: unspecified launch failure
2018.04.22:18:14:07.855: GPU2 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.22:18:14:07.855: GPU2 GPU2 search error: unspecified launch failure
2018.04.22:18:14:07.855: GPU6 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.22:18:14:07.856: GPU6 GPU6 search error: unspecified launch failure
2018.04.22:18:14:08.275: wdog Thread(s) not responding. Restarting.

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

I have done one small change some days ago: changed power limit from 65% to 64%. May be it is a problem.

vanlong

newbie

Activity: 13

Merit: 0

Quote from: Iamtutut on April 22, 2018, 09:54:40 AM

Quote from: vanlong on April 22, 2018, 09:47:47 AM

Hello
i can't run this program Sad

i already choose " run this program as administrator"...
pls looking video and help to me.
thank you
https://drive.google.com/open?id=1q6nGl0w8WB9mqIwJ1NeT7kW0at20-fFB

Your star.bat is empty
No pool, no wallet, nothing...

I using config.txt
other Rig run ok

gsrcrxsi314

member

Activity: 367

Merit: 34

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.

Falconnn

newbie

Activity: 10

Merit: 0

Quote from: Iamtutut on April 22, 2018, 09:54:40 AM

Quote from: vanlong on April 22, 2018, 09:47:47 AM

Hello
i can't run this program Sad

i already choose " run this program as administrator"...
pls looking video and help to me.
thank you
https://drive.google.com/open?id=1q6nGl0w8WB9mqIwJ1NeT7kW0at20-fFB

Your star.bat is empty
No pool, no wallet, nothing...

Make sure start.bat file looks like this:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
PhoenixMiner.exe -epool eth-eu1.nanopool.org:9999 -ewal YOUR_ETH_ADDRESS/YOUR_WORKER_NAME/YOUR_EMAIL -mode 1

YOUR_ETH/ETC_ADDRESS - your valid eth address
YOUR_WORKER - simple short worker name (like worker01). Optional.
YOUR_EMAIL - your email address for notifications. Optional.
Don`t forget to set wallet, worker and email address to correct values.
Read the pool Help how to set, this is for nanopool etr pool

Iamtutut

full member

Activity: 1120

Merit: 131

Quote from: vanlong on April 22, 2018, 09:47:47 AM

Hello
i can't run this program Sad

i already choose " run this program as administrator"...
pls looking video and help to me.
thank you
https://drive.google.com/open?id=1q6nGl0w8WB9mqIwJ1NeT7kW0at20-fFB

Your star.bat is empty
No pool, no wallet, nothing...

vanlong

newbie

Activity: 13

Merit: 0

Hello
i can't run this program Sad

i already choose " run this program as administrator"...
pls looking video and help to me.
thank you
https://drive.google.com/open?id=1q6nGl0w8WB9mqIwJ1NeT7kW0at20-fFB

Digital_Seytan

jr. member

Activity: 222

Merit: 2

[email protected]

who knows what the performance of -qswin 30 or -qswin 15 or a gteal between 1 and 30 at -qswin effect is on the Nvidia GPU?
would like a clear explanation of what extras this brings to the NVidia GPU. I myself have placed -gswin 15 or 30 on the start.bat but no extra information on the miner screen. Thank you phoenix dev.

janding

jr. member

Activity: 170

Merit: 6

@PhoenixMiner

The Readme states:
-fanmin Set fan control min speed in % (-1 for default)
-fanmax Set fan control max speed in % (-1 for default)

This creates an error if I actually set the -fanmin -1 or -fanmax -1
Miner will not load

Miner Dispalys

Out of range -fanmin value: -1 (must be between 0 and 100)
Invalid value in -fanmin option: -1

Out of range -fanmax value: -1 (must be between 0 and 100)
Invalid value in -fanmax option: -1

Soliqesh

newbie

Activity: 48

Merit: 0

Quote from: PhoenixMiner on April 21, 2018, 02:10:57 AM

Quote from: Soliqesh on April 19, 2018, 04:59:52 AM

Hi all, have rig with x6 RX580 8GB(x3 XFX GTS and x3 STRIX TOP Gaming), when i start miner with parameter -tt 64, miner set only for 3 cards XFX (Claymore work fine for all gpu). Help pls( Screen: https://i.imgur.com/LPRmrWq.png

Please send us the log file (the first few minutes after starting are enough). Obviously there is some problem when initializing ADL on your STRIX cards. We had similar problem with an MSI card that wouldn't accept any overclocking settings via ADL calls but we have to see to log to be sure.

Hi, when i set -tt 63 it works, but not correctly(miner set target temperature - 63C for x3 STRIX TOP RX580 8G but in the process of mining cards keep a static 41% fan speed(Screen https://i.imgur.com/dYyZza4.png), if -tt 64 it doesnt work for these cards anymore.
Logs:
1)When i set -tt 63 - https://drive.google.com/open?id=1E_Cnx0W2MQWU5qCwffkaWYK9LpTQvF2F
2)When i set -tt 64 - https://drive.google.com/open?id=1oHTf0yeRxXtfysoFEC_lrfKM22zufbBa
3)When i set -tt 63 but cards have static fan speed 41% - https://drive.google.com/open?id=1yw-5bvCOyN-Vi9ppqVkYdvFAEQ-GDaMa

beastman

newbie

Activity: 9

Merit: 0

I'm having an issue with OC/UV settings not sticking for a few minutes, ie: Mhs will go from 30 to 25 for a couple of minutes then bounce back to 30.

I think I saw something about this being mentioned in another post (2.9d release) but can't seem to find a permanent fix, this doesn't happen with claymore's miner.

Here is my setup:
- 4 Rx 580 4Gb and 4 Rx 580 8Gb
- latest Adrenalin March 23rd drivers
- only timing strap bios mod applied to cards
- OC/UV applied via Phoenix settings

This has a direct impact on the effective speeds, is anyone else experiencing this issue?

Thanks in advance!

BTW, love the Phoenix miner!!! Keep up the great work, cheers!

PhoenixMiner

full member

Activity: 357

Merit: 101

Quote from: bitcoin.dbi on April 18, 2018, 03:18:40 PM

1063 problem is dag file for ETH on windows10. Claymore fixed this problem for few next epochs. So my question: is it possible to mine eth on 2.9e with 1063 on windows 10 or no? Huh

No, there are no "tricks" in 2.9 for 1060 3GB under Windows 10. We decided that there is no point because you will hit the same memory "wall" in a few weeks. The only real solution is to install Window 7, which will give you almost a year more of ETH mining. Obviously this may not be an option if the GPU is not used exclusively for mining but in that case you can mine an alternative ethash based coin like pirl, exp, etc. (or dual-boot between Win7 and Win 10).

Quote from: cmd_whoami on April 18, 2018, 03:36:38 PM

Still having issue with 2.9e with Nvidia 1070 not rebooting with reboot .bat when miner crashes

Code:

2018.04.18:12:26:33.440: gps0 CUDA error in CudaProgram.cu:168 : unknown error (999)
2018.04.18:12:26:33.440: GPU1 CUDA error in CudaProgram.cu:264 : unknown error (999)
2018.04.18:12:26:33.446: GPU1 GPU1 search error: unknown error
2018.04.18:12:26:33.462: GPU8 CUDA error in CudaProgram.cu:264 : unknown error (999)
2018.04.18:12:26:33.462: GPU8 GPU8 search error: unknown error
2018.04.18:12:26:33.462: GPU7 CUDA error in CudaProgram.cu:264 : unknown error (999)
2018.04.18:12:26:33.462: GPU7 GPU7 search error: unknown error
2018.04.18:12:26:33.468: GPU9 CUDA error in CudaProgram.cu:264 : unknown error (999)
2018.04.18:12:26:33.468: GPU9 GPU9 search error: unknown error
2018.04.18:12:26:33.482: GPU3 CUDA error in CudaProgram.cu:264 : unknown error (999)
2018.04.18:12:26:33.482: GPU3 GPU3 search error: unknown error
2018.04.18:12:26:33.482: GPU6 CUDA error in CudaProgram.cu:264 : unknown error (999)
2018.04.18:12:26:33.482: GPU6 GPU6 search error: unknown error
2018.04.18:12:26:33.494: GPU5 CUDA error in CudaProgram.cu:264 : unknown error (999)
2018.04.18:12:26:33.494: GPU5 GPU5 search error: unknown error
2018.04.18:12:26:33.495: GPU2 CUDA error in CudaProgram.cu:264 : unknown error (999)
2018.04.18:12:26:33.495: GPU2 GPU2 search error: unknown error
2018.04.18:12:26:33.535: GPU4 CUDA error in CudaProgram.cu:264 : unknown error (999)
2018.04.18:12:26:33.535: GPU4 GPU4 search error: unknown error
2018.04.18:12:26:34.158: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.18:12:26:34.204: wdog Thread(s) not responding. Restarting.
2018.04.18:12:26:34.296: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x8cc4101785c8e5f40e72a0abf5651c3711a3cafd57475f8ba5c2059146633adc","0x5683748fa7f53897f1e1a80a8a321d3693761838135be37d1d132c0cd3d7d937","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

Thank you for the log, we will try to reproduce it here and fix it for the next release. It would be helpful if you tell us what happens after the program crashes - do you see a Windows error dialog or it just disappears without any messages.

Quote from: ?? on ??

Hi Guys,

can someone of you please assist?
My rig doesn't run stable at all.

sys:
win 10 pro
8x GTX 1070 from msi, evga and palit
2x PSU - 1000W and 850W
page file is set to min. 17000MB and max to 57000MB.

Thanks a lot in advance!!

thats my command line:

Code:

:restart
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 -nvidia -rmode 1 -wdog 1 -pool eth-eu1.nanopool.org:9999 -pool2 eth-eu2.nanopool.org:9999 -wal wallet.worker/email -pass x -ftime 10
goto :restart

--- Error message:

Code:

2018.04.18:22:35:18.778: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xfb36ccc","0x833075af975ab8559540aabf67696685bcb2ef98724ba75a312e1b545c049307"]}

2018.04.18:22:35:18.815: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xaadf04a2431360f4228b2d28ab2fec416f0f508c514f75a095dc22e41a5aa0d3","0x5683748fa7f53897f1e1a80a8a321d3693761838135be37d1d132c0cd3d7d937","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.18:22:35:19.387: main Eth speed: 263.421 MH/s, shares: 17/0/0, time: 0:06
2018.04.18:22:35:19.387: main GPUs: 1: 32.685 MH/s (3) 2: 32.685 MH/s (3) 3: 32.677 MH/s (2) 4: 32.686 MH/s (1) 5: 32.684 MH/s (0) 6: 32.676 MH/s (3) 7: 34.652 MH/s (1) 8: 32.677 MH/s (4)
2018.04.18:22:35:24.466: main Eth speed: 263.422 MH/s, shares: 17/0/0, time: 0:06
2018.04.18:22:35:24.466: main GPUs: 1: 32.685 MH/s (3) 2: 32.687 MH/s (3) 3: 32.676 MH/s (2) 4: 32.686 MH/s (1) 5: 32.685 MH/s (0) 6: 32.676 MH/s (3) 7: 34.651 MH/s (1) 8: 32.677 MH/s (4)
2018.04.18:22:35:25.426: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x169cf1c7d1e89f771cc626178603a4c89647bdd91bf2c762b63cce1cf1e0eca4","0x5683748fa7f53897f1e1a80a8a321d3693761838135be37d1d132c0cd3d7d937","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.18:22:35:25.426: eths Eth: New job #169cf1c7 from eth-eu1.nanopool.org:9999; diff: 10000MH
2018.04.18:22:35:26.163: GPU3 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.173: GPU3 GPU3 search error: unspecified launch failure
2018.04.18:22:35:26.185: GPU1 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.185: GPU1 GPU1 search error: unspecified launch failure
2018.04.18:22:35:26.200: GPU7 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.200: GPU7 GPU7 search error: unspecified launch failure
2018.04.18:22:35:26.201: GPU5 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.201: GPU5 GPU5 search error: unspecified launch failure
2018.04.18:22:35:26.216: GPU4 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.216: GPU4 GPU4 search error: unspecified launch failure
2018.04.18:22:35:26.216: GPU6 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.216: GPU6 GPU6 search error: unspecified launch failure
2018.04.18:22:35:26.232: GPU8 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.232: GPU8 GPU8 search error: unspecified launch failure
2018.04.18:22:35:26.263: GPU2 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.18:22:35:26.263: GPU2 GPU2 search error: unspecified launch failure
2018.04.18:22:35:26.404: wdog Thread(s) not responding. Restarting.
2018.04.18:22:35:28.779: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

First, if the first GPU to fail is (almost) always the same, lower its memory overclock (your hasrates are pretty high for 1070). Also, the restart loop your .bat file is not a good idea when using anything else than -rmode 0 because if PhoenixMiner.exe restarts by itself, your .bat file will start another instance of the miner and you will have two instances of PhoenixMiner trying to mine using the same GPUs, which obviously will lead to problems. So, either remove goto :restart or use -rmode 0 in your .bat file.

Quote from: FlexiN on April 18, 2018, 03:57:51 PM

Hi first time i try to switch from claymore for mining CLO (Callisto) (Ethash algorythm) and impossible to connected to the pool apparently...

Here's my logs :

Code:

2018.04.18:22:54:36.527: main Phoenix Miner 2.9e Windows/msvc - Release
2018.04.18:22:54:36.527: main Cmd line:
2018.04.18:22:54:36.527: main config.txt: -pool clo.2miners.com:3030 -wal 0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480
2018.04.18:22:54:36.527: main No CUDA driver found
2018.04.18:22:54:38.593: main Available GPUs for mining:
2018.04.18:22:54:38.593: main GPU1: Radeon (TM) RX 480 Graphics (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU2: Radeon (TM) RX 480 Graphics (pcie 3), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU3: Radeon (TM) RX 480 Graphics (pcie 4), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU4: Radeon (TM) RX 480 Graphics (pcie 5), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU5: Radeon (TM) RX 480 Graphics (pcie 6), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU6: Radeon (TM) RX 480 Graphics (pcie 7), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.681: main ADL library initialized
2018.04.18:22:54:39.035: main Listening for CDM remote manager at port 3333 in read-only mode
2018.04.18:22:54:39.035: main Eth: the pool list contains 2 pools
2018.04.18:22:54:39.035: main Eth: primary pool: clo.2miners.com:3030
2018.04.18:22:54:39.035: main Starting GPU mining
2018.04.18:22:54:39.035: main Matched GPU1 to ADL adapter index 64 (method 1)
2018.04.18:22:54:39.262: main GPU1: Created ADL monitor for adapter 64; overdrive version: 7
2018.04.18:22:54:39.262: main GPU1: using AMD driver ver 18.3.4
2018.04.18:22:54:39.262: main Matched GPU2 to ADL adapter index 16 (method 1)
2018.04.18:22:54:39.431: main GPU2: Created ADL monitor for adapter 16; overdrive version: 7
2018.04.18:22:54:39.431: main GPU2: using AMD driver ver 18.3.4
2018.04.18:22:54:39.431: main Matched GPU3 to ADL adapter index 32 (method 1)
2018.04.18:22:54:39.528: main GPU3: Created ADL monitor for adapter 32; overdrive version: 7
2018.04.18:22:54:39.528: main GPU3: using AMD driver ver 18.3.4
2018.04.18:22:54:39.529: main Matched GPU4 to ADL adapter index 48 (method 1)
2018.04.18:22:54:39.615: main GPU4: Created ADL monitor for adapter 48; overdrive version: 7
2018.04.18:22:54:39.615: main GPU4: using AMD driver ver 18.3.4
2018.04.18:22:54:39.615: main Matched GPU5 to ADL adapter index 80 (method 1)
2018.04.18:22:54:39.692: main GPU5: Created ADL monitor for adapter 80; overdrive version: 7
2018.04.18:22:54:39.692: main GPU5: using AMD driver ver 18.3.4
2018.04.18:22:54:39.692: main Matched GPU6 to ADL adapter index 0 (method 1)
2018.04.18:22:54:39.785: main GPU6: Created ADL monitor for adapter 0; overdrive version: 7
2018.04.18:22:54:39.785: main GPU6: using AMD driver ver 18.3.4
2018.04.18:22:54:39.786: wdog Starting watchdog thread
2018.04.18:22:54:39.786: main Eth: Connecting to ethash pool clo.2miners.com:3030 (proto: EthProxy)
2018.04.18:22:54:39.872: eths Eth: Connected to ethash pool clo.2miners.com:3030 (95.213.255.168)
2018.04.18:22:54:39.872: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480"]}

2018.04.18:22:54:39.940: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Invalid login"}}
2018.04.18:22:54:39.940: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.18:22:54:39.940: eths Eth: Connection closed by the pool
2018.04.18:22:54:39.940: eths Eth: Reconnecting in 20 seconds...
2018.04.18:22:54:39.987: main GPU1: 31C 66%, GPU2: 32C 66%, GPU3: 40C 73%, GPU4: 30C 66%, GPU5: 34C 66%, GPU6: 32C 66%

And this is my BAT start file :

Code:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

PhoenixMiner.exe -pool clo.2miners.com:3030 -wal 0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480 -pass x -coin etc

Any help would be appreciated

Thanks.

The pool doesn't like your wallet address. Remove the worker name from the wallet address and use the same command line:

Code:

PhoenixMiner.exe -pool clo.2miners.com:3030 -wal 0x4C79A838Eb620E22218A77a2bDc5651b549ea77e -worker RX480 -pass x -coin ubq

Note that the worker name is specified separately in -worker, and the -coin is changed to ubq because it has much smaller DAG than ETC.

Quote from: Soliqesh on April 19, 2018, 04:59:52 AM

Hi all, have rig with x6 RX580 8GB(x3 XFX GTS and x3 STRIX TOP Gaming), when i start miner with parameter -tt 64, miner set only for 3 cards XFX (Claymore work fine for all gpu). Help pls( Screen: https://i.imgur.com/LPRmrWq.png

Please send us the log file (the first few minutes after starting are enough). Obviously there is some problem when initializing ADL on your STRIX cards. We had similar problem with an MSI card that wouldn't accept any overclocking settings via ADL calls but we have to see to log to be sure.

Quote from: pinamalina on April 20, 2018, 03:24:51 AM

Defect Description: reboot.bat fails to load config file

Command Output:
GPU7 not responding
Thread(s) not responding. Restarting.
Eth speed: 215.464 MH/s, shares: 216/0/0, time: 1:00
GPUs: 1: 31.246 MH/s (24) 2: 30.626 MH/s (34) 3: 30.510 MH/s (34) 4: 31.255 MH/s (33) 5: 30.694 MH/s (27) 6: 31.212 MH/s (21) 7: 0.000 MH/s (24) 8: 29.920 MH/s (19)

C:\dev\Ethereum\PhoenixMiner_2.9e>PhoenixMiner.exe config-ms05.bat
Phoenix Miner 2.9e Windows/msvc - Release
-----------------------------------------

Unable to open configuration file config-ms05.bat

C:\dev\Ethereum\PhoenixMiner_2.9e>pause
Press any key to continue . . .

reboot.bat:
----
PhoenixMiner.exe config-ms05.bat

pause
----

The initial startup of the miner is started using the same command: PhoenixMiner.exe config-ms05.bat

Workaround: Updated reboot.bat to:
----
echo Last miner reboot at: %DATE% %TIME% >>reboot.log
copy config-ms05.txt config-ms05-reboot.txt
PhoenixMiner.exe config-ms05-reboot.txt

pause
----

Thank you for the report. We will try to reproduce it and fix it for the next release.

pinamalina

jr. member

Activity: 47

Merit: 1

Defect Description: reboot.bat fails to load config file

Command Output:
GPU7 not responding
Thread(s) not responding. Restarting.
Eth speed: 215.464 MH/s, shares: 216/0/0, time: 1:00
GPUs: 1: 31.246 MH/s (24) 2: 30.626 MH/s (34) 3: 30.510 MH/s (34) 4: 31.255 MH/s (33) 5: 30.694 MH/s (27) 6: 31.212 MH/s (21) 7: 0.000 MH/s (24) 8: 29.920 MH/s (19)

C:\dev\Ethereum\PhoenixMiner_2.9e>PhoenixMiner.exe config-ms05.bat
Phoenix Miner 2.9e Windows/msvc - Release
-----------------------------------------

Unable to open configuration file config-ms05.bat

C:\dev\Ethereum\PhoenixMiner_2.9e>pause
Press any key to continue . . .

reboot.bat:
----
PhoenixMiner.exe config-ms05.bat

pause
----

The initial startup of the miner is started using the same command: PhoenixMiner.exe config-ms05.bat

Workaround: Updated reboot.bat to:
----
echo Last miner reboot at: %DATE% %TIME% >>reboot.log
copy config-ms05.txt config-ms05-reboot.txt
PhoenixMiner.exe config-ms05-reboot.txt

pause
----

janding

jr. member

Activity: 170

Merit: 6

I was pretty hard on PhoenixMiner about their Stale Share rate.
The latest version 2.9e is really good.
The image shows from the pool's point of view that I get between 0 and 3% ( and 3% is the max I get and that isn't often )
Average is 2%. A lot of 0% in there too !!
Great job Phoenix.

cmd_whoami

newbie

Activity: 14

Merit: 0

@ PhoenixMiner

Had another crash were reboot.bat wasnt executed using 2.9e with Nvidia 1070 x9 rig.

Code:

2018.04.19:17:05:58.117: GPU8 GPU8: DAG generated in 6.6 s (376.4 MB/s)
2018.04.19:17:05:58.156: GPU9 GPU9: DAG 97%
2018.04.19:17:05:58.156: GPU9 GPU9: DAG generated in 6.4 s (388.9 MB/s)
2018.04.19:17:05:58.185: GPU9 CUDA error in CudaProgram.cu:246 : unspecified launch failure (719)
2018.04.19:17:05:58.191: GPU9 GPU9 search error: unspecified launch failure
2018.04.19:17:05:58.193: GPU1 CUDART error in CudaProgram.cu:127 : unspecified launch failure (4)
2018.04.19:17:05:58.193: GPU1 GPU1 initMiner error: unspecified launch failure
2018.04.19:17:05:58.193: GPU8 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.19:17:05:58.193: GPU8 GPU8 search error: unspecified launch failure
2018.04.19:17:05:58.193: GPU2 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.19:17:05:58.193: GPU2 GPU2 search error: unspecified launch failure
2018.04.19:17:05:58.193: GPU7 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.19:17:05:58.193: GPU7 GPU7 search error: unspecified launch failure
2018.04.19:17:05:58.209: GPU3 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.19:17:05:58.209: GPU3 GPU3 search error: unspecified launch failure
2018.04.19:17:05:58.224: GPU6 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.19:17:05:58.224: GPU6 GPU6 search error: unspecified launch failure
2018.04.19:17:05:58.271: GPU4 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.19:17:05:58.271: GPU4 GPU4 search error: unspecified launch failure
2018.04.19:17:05:58.287: GPU5 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.19:17:05:58.287: GPU5 GPU5 search error: unspecified launch failure
2018.04.19:17:05:58.599: wdog Thread(s) not responding. Restarting.

start.bat

Code:

@echo off
echo PhoenixMiner will wait 2 seconds before continuing
timeout /t 2
PhoenixMiner.exe -pool eth-us-east1.nanopool.org:9999 -wal ETH Address.miner01/email [email protected] -pass x -coin eth -cdm 0 -nvidia -nvNew 1 -minRigSpeed 287 -tstop 78 -tstart 68 -rmode 2
pause

reboot.bat

Code:

shutdown /r /t 00 /f

anoraknophobia

newbie

Activity: 24

Merit: 0

Quote from: FlexiN on April 18, 2018, 03:57:51 PM

Hi first time i try to switch from claymore for mining CLO (Callisto) (Ethash algorythm) and impossible to connected to the pool apparently...

Here's my logs :

2018.04.18:22:54:36.527: main Phoenix Miner 2.9e Windows/msvc - Release
2018.04.18:22:54:36.527: main Cmd line:
2018.04.18:22:54:36.527: main config.txt: -pool clo.2miners.com:3030 -wal 0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480
2018.04.18:22:54:36.527: main No CUDA driver found
2018.04.18:22:54:38.593: main Available GPUs for mining:
2018.04.18:22:54:38.593: main GPU1: Radeon (TM) RX 480 Graphics (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU2: Radeon (TM) RX 480 Graphics (pcie 3), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU3: Radeon (TM) RX 480 Graphics (pcie 4), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU4: Radeon (TM) RX 480 Graphics (pcie 5), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU5: Radeon (TM) RX 480 Graphics (pcie 6), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU6: Radeon (TM) RX 480 Graphics (pcie 7), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.681: main ADL library initialized
2018.04.18:22:54:39.035: main Listening for CDM remote manager at port 3333 in read-only mode
2018.04.18:22:54:39.035: main Eth: the pool list contains 2 pools
2018.04.18:22:54:39.035: main Eth: primary pool: clo.2miners.com:3030
2018.04.18:22:54:39.035: main Starting GPU mining
2018.04.18:22:54:39.035: main Matched GPU1 to ADL adapter index 64 (method 1)
2018.04.18:22:54:39.262: main GPU1: Created ADL monitor for adapter 64; overdrive version: 7
2018.04.18:22:54:39.262: main GPU1: using AMD driver ver 18.3.4
2018.04.18:22:54:39.262: main Matched GPU2 to ADL adapter index 16 (method 1)
2018.04.18:22:54:39.431: main GPU2: Created ADL monitor for adapter 16; overdrive version: 7
2018.04.18:22:54:39.431: main GPU2: using AMD driver ver 18.3.4
2018.04.18:22:54:39.431: main Matched GPU3 to ADL adapter index 32 (method 1)
2018.04.18:22:54:39.528: main GPU3: Created ADL monitor for adapter 32; overdrive version: 7
2018.04.18:22:54:39.528: main GPU3: using AMD driver ver 18.3.4
2018.04.18:22:54:39.529: main Matched GPU4 to ADL adapter index 48 (method 1)
2018.04.18:22:54:39.615: main GPU4: Created ADL monitor for adapter 48; overdrive version: 7
2018.04.18:22:54:39.615: main GPU4: using AMD driver ver 18.3.4
2018.04.18:22:54:39.615: main Matched GPU5 to ADL adapter index 80 (method 1)
2018.04.18:22:54:39.692: main GPU5: Created ADL monitor for adapter 80; overdrive version: 7
2018.04.18:22:54:39.692: main GPU5: using AMD driver ver 18.3.4
2018.04.18:22:54:39.692: main Matched GPU6 to ADL adapter index 0 (method 1)
2018.04.18:22:54:39.785: main GPU6: Created ADL monitor for adapter 0; overdrive version: 7
2018.04.18:22:54:39.785: main GPU6: using AMD driver ver 18.3.4
2018.04.18:22:54:39.786: wdog Starting watchdog thread
2018.04.18:22:54:39.786: main Eth: Connecting to ethash pool clo.2miners.com:3030 (proto: EthProxy)
2018.04.18:22:54:39.872: eths Eth: Connected to ethash pool clo.2miners.com:3030 (95.213.255.168)
2018.04.18:22:54:39.872: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480"]}

2018.04.18:22:54:39.940: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Invalid login"}}
2018.04.18:22:54:39.940: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.18:22:54:39.940: eths Eth: Connection closed by the pool
2018.04.18:22:54:39.940: eths Eth: Reconnecting in 20 seconds...
2018.04.18:22:54:39.987: main GPU1: 31C 66%, GPU2: 32C 66%, GPU3: 40C 73%, GPU4: 30C 66%, GPU5: 34C 66%, GPU6: 32C 66%

And this is my BAT start file :

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

PhoenixMiner.exe -pool clo.2miners.com:3030 -wal 0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480 -pass x -coin etc

Any help would be appreciated

Thanks.

Just use the following
-wal 0x4C79A838Eb620E22218A77a2bDc5651b549ea77e -worker RX480

anoraknophobia

newbie

Activity: 24

Merit: 0

Quote from: sxemini on April 19, 2018, 06:35:31 AM

If you want to mine CLO, no worker after the wallet. wallet.worker don´t work, but only wallet without worker works perfect.

you can use -wal 0x... -worker Rig1
this way it works.

lesjokolat

jr. member

Activity: 117

Merit: 3

Quote from: FlexiN on April 18, 2018, 03:57:51 PM

Hi first time i try to switch from claymore for mining CLO (Callisto) (Ethash algorythm) and impossible to connected to the pool apparently...

Here's my logs :

2018.04.18:22:54:36.527: main Phoenix Miner 2.9e Windows/msvc - Release
2018.04.18:22:54:36.527: main Cmd line:
2018.04.18:22:54:36.527: main config.txt: -pool clo.2miners.com:3030 -wal 0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480
2018.04.18:22:54:36.527: main No CUDA driver found
2018.04.18:22:54:38.593: main Available GPUs for mining:
2018.04.18:22:54:38.593: main GPU1: Radeon (TM) RX 480 Graphics (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU2: Radeon (TM) RX 480 Graphics (pcie 3), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU3: Radeon (TM) RX 480 Graphics (pcie 4), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU4: Radeon (TM) RX 480 Graphics (pcie 5), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU5: Radeon (TM) RX 480 Graphics (pcie 6), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.593: main GPU6: Radeon (TM) RX 480 Graphics (pcie 7), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.04.18:22:54:38.681: main ADL library initialized
2018.04.18:22:54:39.035: main Listening for CDM remote manager at port 3333 in read-only mode
2018.04.18:22:54:39.035: main Eth: the pool list contains 2 pools
2018.04.18:22:54:39.035: main Eth: primary pool: clo.2miners.com:3030
2018.04.18:22:54:39.035: main Starting GPU mining
2018.04.18:22:54:39.035: main Matched GPU1 to ADL adapter index 64 (method 1)
2018.04.18:22:54:39.262: main GPU1: Created ADL monitor for adapter 64; overdrive version: 7
2018.04.18:22:54:39.262: main GPU1: using AMD driver ver 18.3.4
2018.04.18:22:54:39.262: main Matched GPU2 to ADL adapter index 16 (method 1)
2018.04.18:22:54:39.431: main GPU2: Created ADL monitor for adapter 16; overdrive version: 7
2018.04.18:22:54:39.431: main GPU2: using AMD driver ver 18.3.4
2018.04.18:22:54:39.431: main Matched GPU3 to ADL adapter index 32 (method 1)
2018.04.18:22:54:39.528: main GPU3: Created ADL monitor for adapter 32; overdrive version: 7
2018.04.18:22:54:39.528: main GPU3: using AMD driver ver 18.3.4
2018.04.18:22:54:39.529: main Matched GPU4 to ADL adapter index 48 (method 1)
2018.04.18:22:54:39.615: main GPU4: Created ADL monitor for adapter 48; overdrive version: 7
2018.04.18:22:54:39.615: main GPU4: using AMD driver ver 18.3.4
2018.04.18:22:54:39.615: main Matched GPU5 to ADL adapter index 80 (method 1)
2018.04.18:22:54:39.692: main GPU5: Created ADL monitor for adapter 80; overdrive version: 7
2018.04.18:22:54:39.692: main GPU5: using AMD driver ver 18.3.4
2018.04.18:22:54:39.692: main Matched GPU6 to ADL adapter index 0 (method 1)
2018.04.18:22:54:39.785: main GPU6: Created ADL monitor for adapter 0; overdrive version: 7
2018.04.18:22:54:39.785: main GPU6: using AMD driver ver 18.3.4
2018.04.18:22:54:39.786: wdog Starting watchdog thread
2018.04.18:22:54:39.786: main Eth: Connecting to ethash pool clo.2miners.com:3030 (proto: EthProxy)
2018.04.18:22:54:39.872: eths Eth: Connected to ethash pool clo.2miners.com:3030 (95.213.255.168)
2018.04.18:22:54:39.872: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480"]}

2018.04.18:22:54:39.940: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Invalid login"}}
2018.04.18:22:54:39.940: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.18:22:54:39.940: eths Eth: Connection closed by the pool
2018.04.18:22:54:39.940: eths Eth: Reconnecting in 20 seconds...
2018.04.18:22:54:39.987: main GPU1: 31C 66%, GPU2: 32C 66%, GPU3: 40C 73%, GPU4: 30C 66%, GPU5: 34C 66%, GPU6: 32C 66%

And this is my BAT start file :

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

PhoenixMiner.exe -pool clo.2miners.com:3030 -wal 0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480 -pass x -coin etc

Any help would be appreciated

Thanks.

Is it possible you have more than one rig trying to use the same login name?

"-wal 0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480"

Try changing it to
-wal 0x4C79A838Eb620E22218A77a2bDc5651b549ea77e.RX480_1

lesjokolat

jr. member

Activity: 117

Merit: 3

Quote from: human75 on April 18, 2018, 03:46:02 PM

Quote from: lesjokolat on April 18, 2018, 10:21:19 AM

Hey if any of you re interested check out

ETH.ethertrench.com

FREE mining pool. No pool fees. Low latency(few stales). If I compare my overall returns for the same hashrate as I had when I was on Supernova the payouts are almost double!!!

Pays out very quickly no hassles, also pays for valid uncle shares(stales) as well.

its a smaller pool so finds less often but has large miners come and go that help frequency of finds.

i ve used Phoenix on here for the last few weeks and its been great.

FYI disclosure. I have no affiliation to anyone running or on the pool.

Enjoy!

what is your bat file for phoenix miner? standard commands wont work.thx in advance

What standard commands do you mean? Post your bat and can ref any potential issues for you.
regards

lesjokolat

jr. member

Activity: 117

Merit: 3

Quote from: Soliqesh on April 19, 2018, 04:59:52 AM

Hi all, have rig with x6 RX580 8GB(x3 XFX GTS and x3 STRIX TOP Gaming), when i start miner with parameter -tt 64, miner set only for 3 cards XFX (Claymore work fine for all gpu). Help pls( Screen: https://i.imgur.com/LPRmrWq.png

Try
-tt 64,64,64,64,64,64

Normally should work one entry for all.

Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 422. (Read 784958 times)