Quote from: beastman on April 21, 2018, 01:33:37 PM

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!

Most probably the OC settings are OK even during these hash-rate dips. Please note if the hash-rate drops happen on the same GPU(s) or on different GPU(s), then try the following things to fix them:
  1. Try using -clf 2 or -clf 0.
  2. Try to change the -gt parameter (you can do this interactively with the + and - keys)
  3. Try using the alternative kenrles: -clkernel 2. Note that you will have to select the optimal -gt again as it will be different with these kernels
  4. If nothing else helps, lower the mining intensity (-mi). The default is 12. Note that you may be better off with the occasional hashrate drops instead of permanent hashrate drop because of the lower mining intensity.

Quote from: Soliqesh on April 21, 2018, 01:37:52 PM

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

Quote from: Soliqesh on April 19, 2018, 09: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

Thank you for the logs. It appears that ADL is actually working correctly even on the Strix cards. The messages for applying OC settings are missing because the cards are already at these settings (PhoenixMiner first checks if the settings are the same before applying them). We will add -resetoc option in the next version to reset all OC settings when the miner starts to start from "clean sheet" so to speak.
However the root cause of the problem that you are experiencing seems to be that the Strix cards are reporting too high minimal FAN rpms (1722 rpm), which are probably exactly these 41% that you are seeing. We will make some changes in the next release to avoid abiding by these limits if they are too low or too high.

Quote from: janding on April 22, 2018, 01:50:57 AM

@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

Thank you, this will be fixed in the next release.

Quote from: ibizastyler on April 22, 2018, 12:18:02 PM

Yesterday I changed all of my riser cards, usb cables, etc. and I increased the fan speed for all cards and lowered the mem clock to 700 as well. The rig is now running stable for about 19 hours. 1900 shares and ZERO stales!!! very nice!!! good job!!

thanks for your help!!!!!

...but I have another 2 questions:

1st: what is the correct command line for the reboot.bat and the command line for the miner, if I choose the -rmode 2 option?
- The first function should be, when not enough shares can be found, the miner should restart
- if the miner crashes "normal", the miner should restart
- if the crash happens again, the miner should restart the rig
-- is this possible?!

--- miner: "PhoenixMiner.exe -nvNew 1 -stales 1 -rmode 2 -wdog 1 -pool etc-eu1.nanopool.org:19999 -pool2 etc-eu2.nanopool.org:19999 -wal wallet.worker/email -pass x -ftime 10"
--- reboot.bat: "shutdown /r /t 1 /f"?

2nd: is it possible to show some kind of hardware monitor for nvidia cards? especially the watts of each gpu within the miner. I really really would love to have this function!! --- or is it the -qswin (i.e. 15) option?

1. What is the correct command line for reboot.bat? It depends on what you want but generally, you want to reboot your rig, so shutdown /r /t 1 /f is OK. Unfortunately there is no way to do different things if the restart reason is different - you decide what to do when the miner is restarted for any reason via the -rmode parameter.
2. is it possible to show some kind of hardware monitor for nvidia cards? We will add more HW monitoring for both Nvidia and AMD cards (and possibly some OC controls for Nvidia cards) in the future, however the power consumption that is reported by the cards can only be taken as a relative value because in reality the power is quite different.

Quote from: Digital_Seytan on April 22, 2018, 02:23:21 PM

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.

The -gswin option doesn't affect performance in any way. It just specifies how "smooth" you want your reported hashrate speed. The speed is calculated with a moving average window with size from 5 to 30 seconds (this is what is specified by -gswin). So for example, if you specify -gswin 30 the speed you see will be the average speed of the card for the last 30 seconds. You can also specify 0, which will turn off the moving average calculation and will show momentary values (for the last couple of seconds only). Note that the actual hashrate (and the average hashrate over time) is not affected at all by this option.

Quote from: vanlong on April 22, 2018, 02:47:47 PM

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

Please add pause after the PhoenixMiner.exe in your start_miner.bat file to see any eventual error messages shown by PhoenixMiner before exiting:

Code:

timeout/t 50
PhoenixMiner.exe
pause

If you can't make sense of the error message, send them to us and we will try to help.

Quote from: gsrcrxsi314 on April 22, 2018, 04:51:26 PM

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?

Quote from: j2james on April 23, 2018, 08:39:23 AM

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.

Probably has nothing to do with the power limit, especially if it is lower. Thank you for the log, we are trying to reproduce this here but without success so far. We will continue to work on this issue as it seems that it is recurrent on some rigs.

Quote from: sandbagger on April 23, 2018, 01:17:56 PM

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.

If you can, please send us the end of the log before the crash (the last few pages are enough). These are two separate issues: the error itself, which is probably because the new kernels are more demanding than the old ones, and the miner not restarting. We believed that the second one is solved but apparently not, so we will definitely benefit for some more logs with this problem occurring.

Quote from: djras1 on April 23, 2018, 05:40:12 PM

Love this miner but the -tt setting doesn't work to well. it will not keep the gpus at the temp I set. This is the only problem I have had with this miner.
Anyway to fix this or ideas?
Thanks

Please tell us what GPUs you have and what AMD drivers you are using? Also, how much is the temperature above the specified temperature (1-2 degrees or more)? A log would be helpful too if you can send it to us.

Quote from: Snake33 on April 23, 2018, 05:59:14 PM

Need some help with this error. PhoenixMiner 2.9e

main Available GPUs for mining:
main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs
main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 32 CUs
main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 32 CUs
main GPU4: Radeon (TM) RX 470 Graphics (pcie Cool

, OpenCL 2.0, 4 GB VRAM, 32 CUs
main ADL library initialized

Fattal ERROR: Debugger detected

Quote from: TeppiVietNam on April 24, 2018, 03:46:10 AM

I have a rig with 6 MSI RX470...my driver is beta blockchain version. I have error "debugger detected" when I uses Phoenix (claymore is ok). Please fix it. Here is my content of file config.txt
-pool ssl://asia1.ethermine.org:5555 -pool2 asia1.ethermine.org:4444
-wal 0xabcdxcxxxxxxxxxxxxxxxxxxxxxxx.RX470MSI
-proto 2
-coin eth
-cdm 1
-amd

Thanks you and god!

Hopefully, this will be solved in the next version.

Quote from: Soliqesh on April 23, 2018, 10:44:40 PM

@PhoenixMiner
Hi, is it possible to implement a command "-retrydelay"? Claymore/ethminer and other miners support this. Thanks.

Yes, we will implement it in the next release.

Quote from: NitriusX on April 23, 2018, 04:42:53 PM

Had the miner run for one day, and towards the end it lost connection to the pool and it tried to reconnect over and over again, and after some time it did manage to reconnect, but once it was connected again my hashrate got very low

Code:

2018.04.23:10:16:11.290: main Eth speed: 147.276 MH/s, shares: 2643/0/0, time: 20:38
2018.04.23:10:16:11.290: main GPUs: 1: 29.325 MH/s (549) 2: 29.489 MH/s (497) 3: 29.486 MH/s (537) 4: 29.488 MH/s (516) 5: 29.487 MH/s (544)
2018.04.23:10:16:16.368: main Eth speed: 147.435 MH/s, shares: 2643/0/0, time: 20:38
2018.04.23:10:16:16.368: main GPUs: 1: 29.484 MH/s (549) 2: 29.489 MH/s (497) 3: 29.486 MH/s (537) 4: 29.488 MH/s (516) 5: 29.488 MH/s (544)
2018.04.23:10:16:19.759: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.23:10:16:19.759: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x8c73706","0x930e7ab371861647a7fe1d91f42d4ec0a63adaa7cdb6b1f93bb0c7e7dfdc1d47"]}

2018.04.23:10:16:21.385: eths Eth: Unable to read pool response: The semaphore timeout period has expired
2018.04.23:10:16:21.385: eths Eth: Reconnecting in 20 seconds...
2018.04.23:10:16:24.494: main GPU1: 59C 23%, GPU2: 59C 28%, GPU3: 59C 36%, GPU4: 59C 30%, GPU5: 59C 35%
2018.04.23:10:16:41.390: unkn Eth: Connecting to ethash pool ssl://eu1.ethermine.org:5555 (proto: EthProxy)
2018.04.23:10:16:41.390: unkn Eth: Can't resolve host ssl://eu1.ethermine.org:5555 - No such host is known
2018.04.23:10:16:41.390: unkn Eth: Reconnecting in 20 seconds...
2018.04.23:10:16:49.076: GPU3 Unable to submit share - pool disconnected
2018.04.23:10:16:52.372: main GPU1: 59C 23%, GPU2: 59C 28%, GPU3: 59C 35%, GPU4: 60C 30%, GPU5: 59C 35%
2018.04.23:10:17:01.407: unkn Eth: Connecting to ethash pool ssl://eu1.ethermine.org:5555 (proto: EthProxy)
2018.04.23:10:17:01.408: unkn Eth: Can't resolve host ssl://eu1.ethermine.org:5555 - No such host is known
2018.04.23:10:17:01.408: unkn Eth: Giving up after 3 retries, switching to next pool
2018.04.23:10:17:01.408: unkn Eth: Reconnecting in 20 seconds...
2018.04.23:10:17:14.889: GPU5 Unable to submit share - pool disconnected
2018.04.23:10:17:20.407: main GPU1: 59C 23%, GPU2: 59C 29%, GPU3: 59C 35%, GPU4: 59C 30%, GPU5: 59C 36%
2018.04.23:10:17:21.422: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: EthProxy)
2018.04.23:10:17:21.423: unkn Eth: Can't resolve host eu1.ethermine.org:4444 - No such host is known
2018.04.23:10:17:21.423: unkn Eth: Reconnecting in 20 seconds...
2018.04.23:10:17:23.799: GPU2 Unable to submit share - pool disconnected
2018.04.23:10:17:27.703: GPU3 Unable to submit share - pool disconnected
2018.04.23:10:17:39.574: GPU4 Unable to submit share - pool disconnected
2018.04.23:10:17:41.425: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: EthProxy)
2018.04.23:10:17:41.425: unkn Eth: Can't resolve host eu1.ethermine.org:4444 - No such host is known
2018.04.23:10:17:41.425: unkn Eth: Reconnecting in 20 seconds...
2018.04.23:10:17:48.472: main GPU1: 59C 22%, GPU2: 59C 28%, GPU3: 59C 35%, GPU4: 59C 31%, GPU5: 59C 36%
2018.04.23:10:18:01.427: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: EthProxy)
2018.04.23:10:18:01.467: GPU4 Unable to submit share - pool disconnected
2018.04.23:10:18:12.459: unkn Eth: Can't resolve host eu1.ethermine.org:4444 - No such host is known
2018.04.23:10:18:12.459: unkn Eth: Giving up after 3 retries, switching to next pool
2018.04.23:10:18:12.459: unkn Eth: Reconnecting in 20 seconds...
2018.04.23:10:18:16.506: main GPU1: 59C 22%, GPU2: 59C 29%, GPU3: 59C 35%, GPU4: 59C 30%, GPU5: 59C 36%
2018.04.23:10:18:32.461: unkn Eth: Connecting to ethash pool us1.ethermine.org:4444 (proto: EthProxy)
2018.04.23:10:18:43.494: unkn Eth: Can't resolve host us1.ethermine.org:4444 - No such host is known
2018.04.23:10:18:43.494: unkn Eth: Reconnecting in 20 seconds...
2018.04.23:10:18:44.572: main GPU1: 59C 23%, GPU2: 59C 29%, GPU3: 59C 35%, GPU4: 59C 30%, GPU5: 59C 36%
2018.04.23:10:19:03.496: unkn Eth: Connecting to ethash pool us1.ethermine.org:4444 (proto: EthProxy)
2018.04.23:10:19:12.606: main GPU1: 59C 23%, GPU2: 59C 29%, GPU3: 59C 35%, GPU4: 59C 30%, GPU5: 59C 36%
2018.04.23:10:19:14.528: unkn Eth: Can't resolve host us1.ethermine.org:4444 - No such host is known
2018.04.23:10:19:14.528: unkn Eth: Reconnecting in 20 seconds...
2018.04.23:10:19:34.530: unkn Eth: Connecting to ethash pool us1.ethermine.org:4444 (proto: EthProxy)
2018.04.23:10:19:37.353: GPU4 Unable to submit share - pool disconnected
2018.04.23:10:19:39.940: GPU2 Unable to submit share - pool disconnected
2018.04.23:10:19:40.671: main GPU1: 59C 23%, GPU2: 59C 29%, GPU3: 59C 35%, GPU4: 59C 30%, GPU5: 59C 36%
2018.04.23:10:19:45.563: unkn Eth: Can't resolve host us1.ethermine.org:4444 - No such host is known
2018.04.23:10:19:47.875: unkn Eth: Giving up after 3 retries, switching to next pool
2018.04.23:10:19:47.875: unkn Eth: Reconnecting in 20 seconds...
2018.04.23:10:20:07.880: unkn Eth: Connecting to ethash pool ssl://eu1.ethermine.org:5555 (proto: EthProxy)
2018.04.23:10:20:08.706: main GPU1: 48C 19%, GPU2: 48C 25%, GPU3: 49C 30%, GPU4: 49C 27%, GPU5: 49C 32%
2018.04.23:10:20:18.910: unkn Eth: Can't resolve host ssl://eu1.ethermine.org:5555 - No such host is known
2018.04.23:10:20:18.910: unkn Eth: Reconnecting in 20 seconds...
2018.04.23:10:20:36.568: main GPU1: 45C 0%, GPU2: 44C 19%, GPU3: 44C 24%, GPU4: 45C 21%, GPU5: 45C 26%
2018.04.23:10:20:38.915: unkn Eth: Connecting to ethash pool ssl://eu1.ethermine.org:5555 (proto: EthProxy)
2018.04.23:10:20:38.915: unkn Eth: Can't resolve host ssl://eu1.ethermine.org:5555 - No such host is known
2018.04.23:10:20:38.915: unkn Eth: Reconnecting in 20 seconds...
2018.04.23:10:20:58.933: unkn Eth: Connecting to ethash pool ssl://eu1.ethermine.org:5555 (proto: EthProxy)
2018.04.23:10:21:04.602: main GPU1: 46C 0%, GPU2: 43C 0%, GPU3: 42C 19%, GPU4: 43C 0%, GPU5: 42C 20%
2018.04.23:10:21:09.962: unkn Eth: Can't resolve host ssl://eu1.ethermine.org:5555 - No such host is known
2018.04.23:10:21:09.962: unkn Eth: Giving up after 3 retries, switching to next pool
2018.04.23:10:21:09.962: unkn Eth: Reconnecting in 20 seconds...
2018.04.23:10:21:29.965: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: EthProxy)
2018.04.23:10:21:29.965: unkn Eth: Can't resolve host eu1.ethermine.org:4444 - No such host is known
2018.04.23:10:21:29.965: unkn Eth: Reconnecting in 20 seconds...
2018.04.23:10:21:32.668: main GPU1: 47C 0%, GPU2: 44C 0%, GPU3: 42C 0%, GPU4: 44C 0%, GPU5: 41C 0%
2018.04.23:10:21:49.967: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: EthProxy)
2018.04.23:10:22:00.704: main GPU1: 48C 0%, GPU2: 45C 0%, GPU3: 43C 0%, GPU4: 45C 0%, GPU5: 42C 0%
2018.04.23:10:22:00.999: unkn Eth: Can't resolve host eu1.ethermine.org:4444 - No such host is known
2018.04.23:10:22:00.999: unkn Eth: Reconnecting in 20 seconds...
2018.04.23:10:22:21.001: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: EthProxy)
2018.04.23:10:22:21.002: unkn Eth: Can't resolve host eu1.ethermine.org:4444 - No such host is known
2018.04.23:10:22:21.002: unkn Eth: Giving up after 3 retries, switching to next pool
2018.04.23:10:22:21.002: unkn Eth: Reconnecting in 20 seconds...
2018.04.23:10:22:28.767: main GPU1: 49C 0%, GPU2: 46C 0%, GPU3: 44C 0%, GPU4: 46C 0%, GPU5: 43C 0%
2018.04.23:10:22:41.003: unkn Eth: Connecting to ethash pool us1.ethermine.org:4444 (proto: EthProxy)
2018.04.23:10:22:48.201: eths Eth: Connected to ethash pool us1.ethermine.org:4444 (18.219.59.155)
2018.04.23:10:22:48.201: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["YourWallet.DESKTOP-RVF2V8O"]}

2018.04.23:10:22:48.330: eths Eth: Received: {"id":999,"jsonrpc": "2.0","result": false,"error": "Invalid user provided"}
2018.04.23:10:22:56.802: main GPU1: 49C 0%, GPU2: 47C 0%, GPU3: 45C 0%, GPU4: 47C 0%, GPU5: 44C 0%
2018.04.23:10:23:24.836: main GPU1: 50C 0%, GPU2: 47C 0%, GPU3: 46C 0%, GPU4: 47C 0%, GPU5: 45C 0%
2018.04.23:10:23:52.698: main GPU1: 50C 0%, GPU2: 48C 0%, GPU3: 47C 0%, GPU4: 48C 0%, GPU5: 46C 0%
2018.04.23:10:24:20.733: main GPU1: 51C 0%, GPU2: 48C 0%, GPU3: 47C 0%, GPU4: 49C 0%, GPU5: 47C 0%
2018.04.23:10:24:28.331: eths Eth: Connection closed by the pool
2018.04.23:10:24:28.331: eths Eth: Reconnecting in 20 seconds...
2018.04.23:10:24:48.338: unkn Eth: Connecting to ethash pool us1.ethermine.org:4444 (proto: EthProxy)
2018.04.23:10:24:48.527: eths Eth: Connected to ethash pool us1.ethermine.org:4444 (18.219.59.155)
2018.04.23:10:24:48.527: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["YourWallet.DESKTOP-RVF2V8O"]}

2018.04.23:10:24:48.657: eths Eth: Received: {"id":999,"jsonrpc": "2.0","result": false,"error": "Invalid user provided"}
2018.04.23:10:24:48.806: main GPU1: 51C 0%, GPU2: 49C 0%, GPU3: 48C 0%, GPU4: 49C 0%, GPU5: 47C 0%
2018.04.23:10:25:16.842: main GPU1: 51C 0%, GPU2: 49C 0%, GPU3: 48C 0%, GPU4: 49C 0%, GPU5: 48C 0%
2018.04.23:10:25:44.909: main GPU1: 52C 0%, GPU2: 49C 0%, GPU3: 49C 0%, GPU4: 49C 0%, GPU5: 49C 0%
2018.04.23:10:26:12.944: main GPU1: 52C 0%, GPU2: 50C 0%, GPU3: 49C 0%, GPU4: 50C 0%, GPU5: 49C 0%
2018.04.23:10:26:28.658: eths Eth: Connection closed by the pool
2018.04.23:10:26:28.658: eths Eth: Reconnecting in 20 seconds...
2018.04.23:10:26:40.809: main GPU1: 52C 0%, GPU2: 50C 0%, GPU3: 49C 0%, GPU4: 50C 0%, GPU5: 49C 0%
2018.04.23:10:26:48.669: unkn Eth: Connecting to ethash pool us1.ethermine.org:4444 (proto: EthProxy)
2018.04.23:10:26:48.850: eths Eth: Connected to ethash pool us1.ethermine.org:4444 (18.219.59.155)
2018.04.23:10:26:48.850: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["YourWallet.DESKTOP-RVF2V8O"]}

2018.04.23:10:26:48.984: eths Eth: Received: {"id":999,"jsonrpc": "2.0","result": false,"error": "Invalid user provided"}
2018.04.23:10:27:08.844: main GPU1: 52C 19%, GPU2: 51C 0%, GPU3: 50C 0%, GPU4: 50C 0%, GPU5: 50C 0%
2018.04.23:10:27:36.912: main GPU1: 46C 17%, GPU2: 51C 0%, GPU3: 50C 0%, GPU4: 50C 0%, GPU5: 50C 0%
2018.04.23:10:28:04.948: main GPU1: 46C 0%, GPU2: 51C 0%, GPU3: 50C 0%, GPU4: 51C 0%, GPU5: 51C 0%
2018.04.23:10:28:28.985: eths Eth: Connection closed by the pool
2018.04.23:10:28:28.985: eths Eth: Giving up after 3 retries, switching to next pool
2018.04.23:10:28:28.985: eths Eth: Reconnecting in 20 seconds...
2018.04.23:10:28:33.015: main GPU1: 46C 0%, GPU2: 51C 0%, GPU3: 50C 0%, GPU4: 51C 0%, GPU5: 50C 0%
2018.04.23:10:28:48.989: unkn Eth: Connecting to ethash pool ssl://eu1.ethermine.org:5555 (proto: EthProxy)
2018.04.23:10:28:49.072: eths Eth: Connected to SSL ethash pool eu1.ethermine.org:5555 (188.165.239.100)
2018.04.23:10:28:49.154: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0x8c5797Dcf773E84Cc89B21B5A679864b48588c1D.RT01"]}

2018.04.23:10:28:49.194: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2018.04.23:10:28:49.194: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.23:10:28:49.234: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xb9fc39ed84eb76af1c19e3a593fe90fe100ae4ef020498e4478e7cf260fd9107","0x3ffd591ffcc97fb5e4150c521510e446bb11563ff632ea15845332648cabc086","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x53c83b"]}
2018.04.23:10:28:49.234: eths Eth: New job #b9fc39ed from ssl://eu1.ethermine.org:5555; diff: 4000MH
2018.04.23:10:28:51.515: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x4aeb047a6538c1133d80078e5c31823ccd9141aa65c747ba910e8e40fd351ac4","0x3ffd591ffcc97fb5e4150c521510e446bb11563ff632ea15845332648cabc086","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x53c83c"]}
2018.04.23:10:28:51.515: eths Eth: New job #4aeb047a from ssl://eu1.ethermine.org:5555; diff: 4000MH
2018.04.23:10:28:53.533: main Eth speed: 121.243 MH/s, shares: 2643/0/0, time: 20:51
2018.04.23:10:28:53.533: main GPUs: 1: 16.083 MH/s (549) 2: 26.284 MH/s (497) 3: 26.301 MH/s (537) 4: 26.286 MH/s (516) 5: 26.290 MH/s (544)
2018.04.23:10:28:58.612: main Eth speed: 121.881 MH/s, shares: 2643/0/0, time: 20:51
2018.04.23:10:28:58.612: main GPUs: 1: 16.224 MH/s (549) 2: 26.410 MH/s (497) 3: 26.418 MH/s (537) 4: 26.413 MH/s (516) 5: 26.416 MH/s (544)
2018.04.23:10:28:59.159: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.23:10:28:59.199: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x4aeb047a6538c1133d80078e5c31823ccd9141aa65c747ba910e8e40fd351ac4","0x3ffd591ffcc97fb5e4150c521510e446bb11563ff632ea15845332648cabc086","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x53c83c"]}
2018.04.23:10:29:01.050: main GPU1: 51C 0%, GPU2: 55C 23%, GPU3: 55C 23%, GPU4: 56C 23%, GPU5: 55C 23%
2018.04.23:10:29:03.691: main Eth speed: 121.890 MH/s, shares: 2643/0/0, time: 20:51
2018.04.23:10:29:03.691: main GPUs: 1: 16.240 MH/s (549) 2: 26.444 MH/s (497) 3: 26.451 MH/s (537) 4: 26.449 MH/s (516) 5: 26.306 MH/s (544)
2018.04.23:10:29:08.769: main Eth speed: 122.084 MH/s, shares: 2643/0/0, time: 20:51
2018.04.23:10:29:08.769: main GPUs: 1: 16.268 MH/s (549) 2: 26.486 MH/s (497) 3: 26.490 MH/s (537) 4: 26.490 MH/s (516) 5: 26.350 MH/s (544)
2018.04.23:10:29:09.160: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.23:10:29:09.160: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x74537bd","0x930e7ab371861647a7fe1d91f42d4ec0a63adaa7cdb6b1f93bb0c7e7dfdc1d47"]}

2018.04.23:10:29:09.199: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x4aeb047a6538c1133d80078e5c31823ccd9141aa65c747ba910e8e40fd351ac4","0x3ffd591ffcc97fb5e4150c521510e446bb11563ff632ea15845332648cabc086","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x53c83c"]}
2018.04.23:10:29:09.707: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x263c91b1879b664571e9e8a6019515a64793372393625b990341c2504baf5ff6","0x3ffd591ffcc97fb5e4150c521510e446bb11563ff632ea15845332648cabc086","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x53c83d"]}
2018.04.23:10:29:09.707: eths Eth: New job #263c91b1 from ssl://eu1.ethermine.org:5555; diff: 4000MH
2018.04.23:10:29:10.907: GPU1 Eth: GPU1: ETH share found!
2018.04.23:10:29:10.907: eths Eth: Send: {"id":4,"jsonrpc":"2.0","method":"eth_submitWork","params":["0x15afa8c9719510af","0x263c91b1879b664571e9e8a6019515a64793372393625b990341c2504baf5ff6","0xcb03956db887a1778b735d61a4297714483e2f7ed14d9bc170048d5dd703ce01"]}

2018.04.23:10:29:10.907: eths Eth: Share actual difficulty: 15.6 GH (!)
2018.04.23:10:29:10.947: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
2018.04.23:10:29:10.947: eths Eth: Received: {"id":4,"jsonrpc":"2.0","result":true}
2018.04.23:10:29:10.947: eths Eth: Share accepted in 40 ms
2018.04.23:10:29:13.848: main Eth speed: 122.072 MH/s, shares: 2644/0/0, time: 20:51
2018.04.23:10:29:13.848: main GPUs: 1: 16.268 MH/s (550) 2: 26.489 MH/s (497) 3: 26.491 MH/s (537) 4: 26.491 MH/s (516) 5: 26.333 MH/s (544)

As you can see the avg. hashrate before the miner lost connection was 147, and after it ended up around 122 mh/s, anyone know why? Of course I only had to restart the miner and it was back to normal again. No big problem, but hoping it won't happen again.

You had connectivity issues for a few minutes - your Internet connection was down. However after it was restored, the first few attempts to connect to the next pool failed because you haven't specified your wallet address in the epools.txt file. Open the epools.txt file and change YourWalletAddress to your actual wallet address. The second problem - the lower hashrate after the connection was finally restored - is a driver problem that we can't fix in the miner. However you can use the -minrigspeed parameter to specify a minimal 5 min average speed. For example if you add -minrigspeed 140, PhoenixMiner will restart if the 5 min average speed is not >= 140 Mh/s.