[ANN] TeamRedMiner v0.10.10 - Ironfish/Kaspa/ZIL/Kawpow/Etchash and More

[kerney666]

What are the settings for Vega 64  mining for ETHASH  (etherium) please?

ONT settings  (voltage) please advice.

We did include a short tuning guide in the release (ETHASH_GENERAL_TUNING.tx) that you can use as a base. It includes examples timings and clocks, check the section for Vega 64 and let us know if you still have issues.

I got it. Now one of my cards is not stable. Can you give me the link for Vega 64 section tuning please?

i got stable hash with no HW error.

core : 1150 mem : 1090  V:900m 50mh/s

amdmemorytweak --CL 20 --RAS 30 --RCDRD 14 --RCDWR 12 --RC 44 --RP 14 --RRDS 3 --RRDL 6 --RTP 5 --FAW 12 --CWL 8 --WTRS 4 --WTRL 9 --WR 14 --REF 17000 --RFC 249


but pool hash  very different .
i got 1020Mh/s in my system and in pool it's about 500Mh - 5% reject and no hw error.

Which pool is this? And, how many accepted shares when you had 500 MH/s poolside?

Read some more, and it really seems you can't connect to the dev fee server? Or, do you see a line with "Dev pool connected and ready." when starting up the miner?

The 5% reject is weird though, since we do cpu verification of all shares. And, you mean pool rejects, not stale shares?

[1714946430]

1714946430

[1714946430]

1714946430

[1714946430]

1714946430

[UnclWish]

Hi, kerney666!

Say, what difference in A and B configs except twice amount of vmem needed? On my RX 580 cards difference in speed is very low. About 100-150kH/s each card on 33+MH/s. Maybe I do something wrong? Or it must to be so little diff?

[UnclWish]

And another one thing:
I noticed that autotune process starts when speed on eth grows after generating DAG. But max speed became after about 20-30 secodns. Autotune process maybe incorrect due to growing speed.
It would be great if you did autotune by pressing key in any time during minning and changing A or B numbers by pressing keys during mining on the fly.

[kerney666]

Hi, kerney666!

Say, what difference in A and B configs except twice amount of vmem needed? On my RX 580 cards difference in speed is very low. About 100-150kH/s each card on 33+MH/s. Maybe I do something wrong? Or it must to be so little diff?

There is no other difference than we use more mem and a slightly different approach. +125 kh/s at 33 MH/s is about +0.4%, which is in the expected range (0.2-0.5%), and I think it's actually pretty great for being Polaris . The performance on these old workhorses has been pushed close to their maximum for years. On Radeon VIIs, the B mode usually gives you a +7-8% boost though, much more noticable of course.

But, for Polaris 8GBs, and as long as you have the swap space if you're a Windows miner, you get > 50% of our dev fee (0.75%) back pretty much for free.

[kerney666]

And another one thing:
I noticed that autotune process starts when speed on eth grows after generating DAG. But max speed became after about 20-30 secodns. Autotune process maybe incorrect due to growing speed.
It would be great if you did autotune by pressing key in any time during minning and changing A or B numbers by pressing keys during mining on the fly.

Yeah, we can add manual tuning mode if people want to play around. The auto-tuning should find the best value though, it doesn't matter that it's running as speed appears to increase, that's just an effect of the DAG rebuild. The auto-tune looks much more closely at the runtime for every separate run that we do on the gpu and not those increasing values.

[chimaeraa]

What are the settings for Vega 64  mining for ETHASH  (etherium) please?

ONT settings  (voltage) please advice.

We did include a short tuning guide in the release (ETHASH_GENERAL_TUNING.tx) that you can use as a base. It includes examples timings and clocks, check the section for Vega 64 and let us know if you still have issues.

I got it. Now one of my cards is not stable. Can you give me the link for Vega 64 section tuning please?

i got stable hash with no HW error.

core : 1150 mem : 1090  V:900m 50mh/s

amdmemorytweak --CL 20 --RAS 30 --RCDRD 14 --RCDWR 12 --RC 44 --RP 14 --RRDS 3 --RRDL 6 --RTP 5 --FAW 12 --CWL 8 --WTRS 4 --WTRL 9 --WR 14 --REF 17000 --RFC 249


but pool hash  very different .
i got 1020Mh/s in my system and in pool it's about 500Mh - 5% reject and no hw error.

Which pool is this? And, how many accepted shares when you had 500 MH/s poolside?

www.hpt.com/ - huobi pool.
about 4000 .
and now it's show zero.
https://i.imgur.com/ny5wJgC.png

[chimaeraa]

What are the settings for Vega 64  mining for ETHASH  (etherium) please?

ONT settings  (voltage) please advice.

We did include a short tuning guide in the release (ETHASH_GENERAL_TUNING.tx) that you can use as a base. It includes examples timings and clocks, check the section for Vega 64 and let us know if you still have issues.

I got it. Now one of my cards is not stable. Can you give me the link for Vega 64 section tuning please?

i got stable hash with no HW error.

core : 1150 mem : 1090  V:900m 50mh/s

amdmemorytweak --CL 20 --RAS 30 --RCDRD 14 --RCDWR 12 --RC 44 --RP 14 --RRDS 3 --RRDL 6 --RTP 5 --FAW 12 --CWL 8 --WTRS 4 --WTRL 9 --WR 14 --REF 17000 --RFC 249


but pool hash  very different .
i got 1020Mh/s in my system and in pool it's about 500Mh - 5% reject and no hw error.

Which pool is this? And, how many accepted shares when you had 500 MH/s poolside?

Read some more, and it really seems you can't connect to the dev fee server? Or, do you see a line with "Dev pool connected and ready." when starting up the miner?

The 5% reject is weird though, since we do cpu verification of all shares. And, you mean pool rejects, not stale shares?

yes it can't connect . no i don't see that.

i see this all the time

[2019-12-02 09:19:20] Dev pool connection was closed by remote side.
[2019-12-02 09:19:20] Mining will proceed at reduced rate while not connected to dev pool.


yes .pool rejects that.

and somthing more after 12 mining i see 1020Mh/s in my rige and pool side show zero for 2H.
after reset miner it's submit shares.

[UnclWish]

And another one thing:
I noticed that autotune process starts when speed on eth grows after generating DAG. But max speed became after about 20-30 secodns. Autotune process maybe incorrect due to growing speed.
It would be great if you did autotune by pressing key in any time during minning and changing A or B numbers by pressing keys during mining on the fly.

Yeah, we can add manual tuning mode if people want to play around. The auto-tuning should find the best value though, it doesn't matter that it's running as speed appears to increase, that's just an effect of the DAG rebuild. The auto-tune looks much more closely at the runtime for every separate run that we do on the gpu and not those increasing values.

Thanks for explaining. And another one question:
optimal config is the same for any DAG or different DAG can require new best config? If so maybe add option to enable autotune with generating avery new DAG?

[PIOUPIOU99]

TRM 0.6.0 ETH first test

My 4 vega 56 (samsung stock-bios ) is cool +49mh.
Vega 56 hynix(gpu-6) and 64 (gpu-7) bad hash but bad setting probably.

[shabbat]

guys. have an answer to the question?

https://bitcointalk.org/index.php?topic=5123724.msg53244888#msg53244888

How to apply an automatically saved profile?

example.
I have an ETH.xml profile file
How do I run AMDMemoryTweak so that it applies this profile at startup?
I tried to run through the bat file.
like this
AMDMemoryTweak.exe --ETH.xml

does not work.

to be
AMDMemoryTweak.exe ETH.xml

does not work.

how to run correctly Huh

Tell me please.

[ku4eto]

guys. have an answer to the question?

https://bitcointalk.org/index.php?topic=5123724.msg53244888#msg53244888

How to apply an automatically saved profile?

example.
I have an ETH.xml profile file
How do I run AMDMemoryTweak so that it applies this profile at startup?
I tried to run through the bat file.
like this
AMDMemoryTweak.exe --ETH.xml

does not work.

to be
AMDMemoryTweak.exe ETH.xml

does not work.

how to run correctly Huh

Tell me please.

Run the tool with --help and see what are the available commands...

[shabbat]

Run the tool with --help and see what are the available commands...

I did it.
I don’t see a solution there.
can you write an answer here?
you are welcome.

[shabbat]

when entering this command.
a program window appears.
no help.

but that’s not the point.
above I gave a direct question, can you answer it?
screenshot
https://i.ibb.co/dtdVc98/2019-12-03-22-45-36.png

[shabbat]

How to apply an automatically saved profile?

example.
I have an ETH.xml profile file
How do I run AMDMemoryTweak so that it applies this profile at startup?
I tried to run through the bat file.
like this
AMDMemoryTweak.exe --ETH.xml

does not work.

to be
AMDMemoryTweak.exe ETH.xml

does not work.

how to run correctly Huh

Tell me please.
 

[NCarter84]

How to apply an automatically saved profile?

example.
I have an ETH.xml profile file
How do I run AMDMemoryTweak so that it applies this profile at startup?
I tried to run through the bat file.
like this
AMDMemoryTweak.exe --ETH.xml

does not work.

to be
AMDMemoryTweak.exe ETH.xml

does not work.

how to run correctly Huh

Tell me please.
 

Use a .bat file instead. Something like:

WinAMDTweak.exe --gpu 0 --CL 19 --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --RTP 4 --FAW 18 --CWL 6 --WTRS 4 --WTRL 9 --WR 15 --WRRD 1 --RDWR 18 --REF 17000 --RFC 248


WinAMDTweak.exe --gpu 1 --ref 60
TIMEOUT /T 1

WinAMDTweak.exe --gpu 2 --CL 19 --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --RTP 4 --FAW 18 --CWL 6 --WTRS 4 --WTRL 9 --WR 15 --WRRD 1 --RDWR 18 --REF 17000 --RFC 248

TIMEOUT /T 1

WinAMDTweak.exe --gpu 3 --ref 60
TIMEOUT /T 1

WinAMDTweak.exe --gpu 4 --ref 60
TIMEOUT /T 1

WinAMDTweak.exe --gpu 5 --CL 19 --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --RTP 4 --FAW 18 --CWL 6 --WTRS 4 --WTRL 9 --WR 15 --WRRD 1 --RDWR 18 --REF 17000 --RFC 248

[kerney666]

How to apply an automatically saved profile?

example.
I have an ETH.xml profile file
How do I run AMDMemoryTweak so that it applies this profile at startup?
I tried to run through the bat file.
like this
AMDMemoryTweak.exe --ETH.xml

does not work.

to be
AMDMemoryTweak.exe ETH.xml

does not work.

how to run correctly Huh

Tell me please.
 

I honestly don't know. I don't work with profiles in xml files, I just run the command in a .bat file and set the timings I want after a reboot. I don't know (1) how you got the ETH.xml in the first place, (2) why you're running AMDMemoryTweak.exe, I've only seen it called WinAMDTweak.exe, (3) why you believe you can run a profile through the CLI tool? I don't see any option for it.

NCarter's suggestion is probably the way to go for you.

Cheers, K

[shabbat]

thank you my friend
but it doesn’t work for me

AMDMemoryTweak ( GUI ) and WinAMDTweak ( CLI ) are not the same thing.

the problem is that if I run the bat file for the WinAMDTweak program, timings do not apply. Hashrate does not rise.
That is, WinAMDTweak ( CLI )  does not work in my system
that just did not.
Does not work.
the program pretends that the timings have changed, but in fact not.
does not work.

And the AMDMemoryTweak  ( GUI ) program works.
Timings are changing.
But, each time, you need to manually open the profile and run it.

So the question arose - how to automatically launch AMDMemoryTweak with automatic loading of the desired profile?

[kerney666]

thank you my friend
but it doesn’t work for me

AMDMemoryTweak ( GUI ) and WinAMDTweak ( CLI ) are not the same thing.

the problem is that if I run the bat file for the WinAMDTweak program, timings do not apply. Hashrate does not rise.
That is, WinAMDTweak ( CLI )  does not work in my system
that just did not.
Does not work.
the program pretends that the timings have changed, but in fact not.
does not work.

And the AMDMemoryTweak  ( GUI ) program works.
Timings are changing.
But, each time, you need to manually open the profile and run it.

So the question arose - how to automatically launch AMDMemoryTweak with automatic loading of the desired profile?

Hi! I hear what you're saying, but I still don't have a solution for you, it's not our product. The AMDMemoryTweak tool thread is your best shot, and I know you've asked there as well.

Afaik the (non-XL) version of the GUI is just a wrapper around WinAMDTweak.exe but maybe there's something else as well. Since it's closed source we don't know. It doesn't response to /?, --help or any other standard call, it just opens the gui.

[primavera8989]

Hello. I started using TRM 0.61, Polaris. I really like the average hashrate, but I use a specific pool and get periodic errors and reboots. Help please. Here are some log data.

///
[2019-12-04 20:14:29] Stats Uptime: 0 days, 00:29:32
[2019-12-04 20:14:29] ----------------------------------------- GPU Status -------------------------------------------
[2019-12-04 20:14:29] GPU 0 [56C, fan 60%]       ethash: 32.93Mh/s, avg 32.69Mh/s, pool 36.15Mh/s a:16 r:0 hw:0
[2019-12-04 20:14:29] GPU 1 [53C, fan 55%]       ethash: 32.93Mh/s, avg 32.70Mh/s, pool 29.37Mh/s a:13 r:0 hw:0
[2019-12-04 20:14:29] GPU 2 [45C, fan 47%]       ethash: 30.45Mh/s, avg 30.25Mh/s, pool 27.12Mh/s a:12 r:0 hw:0
[2019-12-04 20:14:29] GPU 3 [52C, fan 53%]       ethash: 32.95Mh/s, avg 32.70Mh/s, pool 33.90Mh/s a:15 r:0 hw:0
[2019-12-04 20:14:29] GPU 4 [56C, fan 58%]       ethash: 30.19Mh/s, avg 29.92Mh/s, pool 13.56Mh/s a:6 r:0 hw:0
[2019-12-04 20:14:29] Total                      ethash: 159.4Mh/s, avg 158.3Mh/s, pool 140.1Mh/s a:62 r:0 hw:0
[2019-12-04 20:14:29] ----------------------------------------- Pool Status ------------------------------------------
[2019-12-04 20:14:29] eu.ezil.me                 ethash: 159.5Mh/s, avg 156.9Mh/s, pool 140.1Mh/s a:62 r:0
[2019-12-04 20:14:29] ------------------------------------------------------------------------------------------------
[2019-12-04 20:14:31] Pool eu.ezil.me received new job. (job_id: 0x05f63a5a5c2e12859fcb34e4d5e445bf567982e866a6167ccbe75a7abbde9270)
[2019-12-04 20:14:31] Pool eu.ezil.me share accepted. (GPU0) (a:63 r:0) (81 ms)
[2019-12-04 20:14:33] Pool eu.ezil.me received new job. (job_id: 0x1dea1d30bf0845fbcff3c7c0cfea803ed720982a9ea8aec2d79d9121988af292)
[2019-12-04 20:14:34] Pool eu.ezil.me share accepted. (GPU2) (a:64 r:0) (70 ms)
[2019-12-04 20:14:36] Pool eu.ezil.me received new job. (job_id: 0x144c0f13095c62e320bc90545a036d187ff477d13abc7b2023cf1fd269cb64c0)
[2019-12-04 20:14:36] Dev pool connection was closed due to an error.
[2019-12-04 20:14:36] Mining will proceed at reduced rate while not connected to dev pool.
[2019-12-04 20:14:36] Pool eu.ezil.me connection was closed due to an error.
[2019-12-04 20:14:36] Dev pool failed to connect.
[2019-12-04 20:14:36] Mining will proceed at reduced rate while not connected to dev pool.
[2019-12-04 20:14:36] Pool eu.ezil.me failed to resolve host address.
[2019-12-04 20:14:36] Pool eu.ezil.me switching to stratum mode.
[2019-12-04 20:20:50] Initializing GPU 0.
[2019-12-04 20:20:50] GPU 0 Starting tuning.
[2019-12-04 20:20:50] Initializing GPU 1.
[2019-12-04 20:20:51] GPU 1 Starting tuning.
[2019-12-04 20:20:51] Initializing GPU 2.
[2019-12-04 20:20:51] GPU 2 Starting tuning.
[2019-12-04 20:20:51] Initializing GPU 3.
[2019-12-04 20:20:51] GPU 3 Starting tuning.
[2019-12-04 20:20:51] Initializing GPU 4.
[2019-12-04 20:20:51] GPU 4 Starting tuning.
[2019-12-04 20:20:52] Successfully initialized GPU 0: Polaris with 36 CU (PCIe 08:00.0)
[2019-12-04 20:20:52] Successfully initialized GPU 1: Polaris with 36 CU (PCIe 06:00.0)
[2019-12-04 20:20:52] Successfully initialized GPU 2: Polaris with 36 CU (PCIe 03:00.0)
[2019-12-04 20:20:52] Successfully initialized GPU 3: Polaris with 36 CU (PCIe 04:00.0)
[2019-12-04 20:20:52] Successfully initialized GPU 4: Polaris with 32 CU (PCIe 01:00.0)
[2019-12-04 20:20:52] Watchdog thread starting.


......AND NEXT

[2019-12-04 20:43:22] Stats Uptime: 0 days, 00:22:32
[2019-12-04 20:43:22] ----------------------------------------- GPU Status -------------------------------------------
[2019-12-04 20:43:22] GPU 0 [56C, fan 60%]       ethash: 33.14Mh/s, avg 32.64Mh/s, pool 20.73Mh/s a:7 r:0 hw:0
[2019-12-04 20:43:22] GPU 1 [53C, fan 55%]       ethash: 33.13Mh/s, avg 32.67Mh/s, pool 42.21Mh/s a:13 r:0 hw:0
[2019-12-04 20:43:22] GPU 2 [45C, fan 47%]       ethash: 30.55Mh/s, avg 30.09Mh/s, pool 45.92Mh/s a:13 r:0 hw:0
[2019-12-04 20:43:22] GPU 3 [52C, fan 51%]       ethash: 33.15Mh/s, avg 32.69Mh/s, pool 32.60Mh/s a:11 r:0 hw:0
[2019-12-04 20:43:22] GPU 4 [55C, fan 58%]       ethash: 29.98Mh/s, avg 29.63Mh/s, pool 11.85Mh/s a:4 r:0 hw:0
[2019-12-04 20:43:22] Total                      ethash: 159.9Mh/s, avg 157.7Mh/s, pool 153.3Mh/s a:48 r:0 hw:0
[2019-12-04 20:43:22] ----------------------------------------- Pool Status ------------------------------------------
[2019-12-04 20:43:22] eu.ezil.me                 ethash: 166.1Mh/s, avg 156.5Mh/s, pool 153.3Mh/s a:48 r:0
[2019-12-04 20:43:22] ------------------------------------------------------------------------------------------------
[2019-12-04 20:43:39] Pool eu.ezil.me invalid RPC ID received.  (If this error repeats, try using the --pool_broken_rpc option.)
[2019-12-04 20:43:39] Pool eu.ezil.me failed to parse server rpc: {"id":1,"jsonrpc":"2.0","result":true}
[2019-12-04 20:43:40] Pool eu.ezil.me set difficulty to 0.931308
[2019-12-04 20:43:40] Pool eu.ezil.me received new job. (job_id: 0xf870642a49132c3938115fa37130f054bc38db41f97dadfb5d05b1eed6388c60)
[2019-12-04 20:43:40] GPU 4 Starting DAG generation for epoch 301.
[2019-12-04 20:43:40] GPU 3 Starting DAG generation for epoch 301.
[2019-12-04 20:43:40] GPU 0 Starting DAG generation for epoch 301.
[2019-12-04 20:43:40] GPU 1 Starting DAG generation for epoch 301.
[2019-12-04 20:43:40] GPU 2 Starting DAG generation for epoch 301.
[2019-12-04 20:43:43] Pool eu.ezil.me received new job. (job_id: 0x33c0babf5c529e966369efeab0c218a7f74a64e726353591df5e6d024961c8c0)
[2019-12-04 20:43:46] Pool eu.ezil.me received new job. (job_id: 0x0fe3d0b6710470fa410414ca57dd10e2cda5c290b36224a761c229a8508aa66e)
[2019-12-04 20:43:46] Pool eu.ezil.me received new job. (job_id: 0xc7969a2e92d6e2cd0fd059d1337bb66f432d52de1466deec5d563298e84929a2)

[kerney666]

Hello. I started using TRM 0.61, Polaris. I really like the average hashrate, but I use a specific pool and get periodic errors and reboots. Help please. Here are some log data.

///
[2019-12-04 20:14:29] Stats Uptime: 0 days, 00:29:32
[2019-12-04 20:14:29] ----------------------------------------- GPU Status -------------------------------------------
[2019-12-04 20:14:29] GPU 0 [56C, fan 60%]       ethash: 32.93Mh/s, avg 32.69Mh/s, pool 36.15Mh/s a:16 r:0 hw:0
[2019-12-04 20:14:29] GPU 1 [53C, fan 55%]       ethash: 32.93Mh/s, avg 32.70Mh/s, pool 29.37Mh/s a:13 r:0 hw:0
[2019-12-04 20:14:29] GPU 2 [45C, fan 47%]       ethash: 30.45Mh/s, avg 30.25Mh/s, pool 27.12Mh/s a:12 r:0 hw:0
[2019-12-04 20:14:29] GPU 3 [52C, fan 53%]       ethash: 32.95Mh/s, avg 32.70Mh/s, pool 33.90Mh/s a:15 r:0 hw:0
[2019-12-04 20:14:29] GPU 4 [56C, fan 58%]       ethash: 30.19Mh/s, avg 29.92Mh/s, pool 13.56Mh/s a:6 r:0 hw:0
[2019-12-04 20:14:29] Total                      ethash: 159.4Mh/s, avg 158.3Mh/s, pool 140.1Mh/s a:62 r:0 hw:0
[2019-12-04 20:14:29] ----------------------------------------- Pool Status ------------------------------------------
[2019-12-04 20:14:29] eu.ezil.me                 ethash: 159.5Mh/s, avg 156.9Mh/s, pool 140.1Mh/s a:62 r:0
[2019-12-04 20:14:29] ------------------------------------------------------------------------------------------------
[2019-12-04 20:14:31] Pool eu.ezil.me received new job. (job_id: 0x05f63a5a5c2e12859fcb34e4d5e445bf567982e866a6167ccbe75a7abbde9270)
[2019-12-04 20:14:31] Pool eu.ezil.me share accepted. (GPU0) (a:63 r:0) (81 ms)
[2019-12-04 20:14:33] Pool eu.ezil.me received new job. (job_id: 0x1dea1d30bf0845fbcff3c7c0cfea803ed720982a9ea8aec2d79d9121988af292)
[2019-12-04 20:14:34] Pool eu.ezil.me share accepted. (GPU2) (a:64 r:0) (70 ms)
[2019-12-04 20:14:36] Pool eu.ezil.me received new job. (job_id: 0x144c0f13095c62e320bc90545a036d187ff477d13abc7b2023cf1fd269cb64c0)
[2019-12-04 20:14:36] Dev pool connection was closed due to an error.
[2019-12-04 20:14:36] Mining will proceed at reduced rate while not connected to dev pool.
[2019-12-04 20:14:36] Pool eu.ezil.me connection was closed due to an error.
[2019-12-04 20:14:36] Dev pool failed to connect.
[2019-12-04 20:14:36] Mining will proceed at reduced rate while not connected to dev pool.
[2019-12-04 20:14:36] Pool eu.ezil.me failed to resolve host address.
[2019-12-04 20:14:36] Pool eu.ezil.me switching to stratum mode.
[2019-12-04 20:20:50] Initializing GPU 0.
[2019-12-04 20:20:50] GPU 0 Starting tuning.
[2019-12-04 20:20:50] Initializing GPU 1.
[2019-12-04 20:20:51] GPU 1 Starting tuning.
[2019-12-04 20:20:51] Initializing GPU 2.
[2019-12-04 20:20:51] GPU 2 Starting tuning.
[2019-12-04 20:20:51] Initializing GPU 3.
[2019-12-04 20:20:51] GPU 3 Starting tuning.
[2019-12-04 20:20:51] Initializing GPU 4.
[2019-12-04 20:20:51] GPU 4 Starting tuning.
[2019-12-04 20:20:52] Successfully initialized GPU 0: Polaris with 36 CU (PCIe 08:00.0)
[2019-12-04 20:20:52] Successfully initialized GPU 1: Polaris with 36 CU (PCIe 06:00.0)
[2019-12-04 20:20:52] Successfully initialized GPU 2: Polaris with 36 CU (PCIe 03:00.0)
[2019-12-04 20:20:52] Successfully initialized GPU 3: Polaris with 36 CU (PCIe 04:00.0)
[2019-12-04 20:20:52] Successfully initialized GPU 4: Polaris with 32 CU (PCIe 01:00.0)
[2019-12-04 20:20:52] Watchdog thread starting.


......AND NEXT

[2019-12-04 20:43:22] Stats Uptime: 0 days, 00:22:32
[2019-12-04 20:43:22] ----------------------------------------- GPU Status -------------------------------------------
[2019-12-04 20:43:22] GPU 0 [56C, fan 60%]       ethash: 33.14Mh/s, avg 32.64Mh/s, pool 20.73Mh/s a:7 r:0 hw:0
[2019-12-04 20:43:22] GPU 1 [53C, fan 55%]       ethash: 33.13Mh/s, avg 32.67Mh/s, pool 42.21Mh/s a:13 r:0 hw:0
[2019-12-04 20:43:22] GPU 2 [45C, fan 47%]       ethash: 30.55Mh/s, avg 30.09Mh/s, pool 45.92Mh/s a:13 r:0 hw:0
[2019-12-04 20:43:22] GPU 3 [52C, fan 51%]       ethash: 33.15Mh/s, avg 32.69Mh/s, pool 32.60Mh/s a:11 r:0 hw:0
[2019-12-04 20:43:22] GPU 4 [55C, fan 58%]       ethash: 29.98Mh/s, avg 29.63Mh/s, pool 11.85Mh/s a:4 r:0 hw:0
[2019-12-04 20:43:22] Total                      ethash: 159.9Mh/s, avg 157.7Mh/s, pool 153.3Mh/s a:48 r:0 hw:0
[2019-12-04 20:43:22] ----------------------------------------- Pool Status ------------------------------------------
[2019-12-04 20:43:22] eu.ezil.me                 ethash: 166.1Mh/s, avg 156.5Mh/s, pool 153.3Mh/s a:48 r:0
[2019-12-04 20:43:22] ------------------------------------------------------------------------------------------------
[2019-12-04 20:43:39] Pool eu.ezil.me invalid RPC ID received.  (If this error repeats, try using the --pool_broken_rpc option.)
[2019-12-04 20:43:39] Pool eu.ezil.me failed to parse server rpc: {"id":1,"jsonrpc":"2.0","result":true}
[2019-12-04 20:43:40] Pool eu.ezil.me set difficulty to 0.931308
[2019-12-04 20:43:40] Pool eu.ezil.me received new job. (job_id: 0xf870642a49132c3938115fa37130f054bc38db41f97dadfb5d05b1eed6388c60)
[2019-12-04 20:43:40] GPU 4 Starting DAG generation for epoch 301.
[2019-12-04 20:43:40] GPU 3 Starting DAG generation for epoch 301.
[2019-12-04 20:43:40] GPU 0 Starting DAG generation for epoch 301.
[2019-12-04 20:43:40] GPU 1 Starting DAG generation for epoch 301.
[2019-12-04 20:43:40] GPU 2 Starting DAG generation for epoch 301.
[2019-12-04 20:43:43] Pool eu.ezil.me received new job. (job_id: 0x33c0babf5c529e966369efeab0c218a7f74a64e726353591df5e6d024961c8c0)
[2019-12-04 20:43:46] Pool eu.ezil.me received new job. (job_id: 0x0fe3d0b6710470fa410414ca57dd10e2cda5c290b36224a761c229a8508aa66e)
[2019-12-04 20:43:46] Pool eu.ezil.me received new job. (job_id: 0xc7969a2e92d6e2cd0fd059d1337bb66f432d52de1466deec5d563298e84929a2)

Ah these ethash pools... We'll test it though and make sure it works, np!

That said, your errors at "2019-12-04 20:14:36" in the log indicate a general network issue. The dev pool connection went down and we can't resolve the IP for the hostname "eu.ezil.me". This really indicates your network connection was down hard at that time.