Whenever I open gpuz the rig hangs or the SRBminer starts to show 0 h / s.
You may be overclocking on the limits maybe.
My experience with GPU-Z is that now I have to start it before I start SRB, or 1 out of 3-4 times one of the GPU's crashes.
With GPU-Z, the rig very quickly increases performance but it's stuck at it 95-96% performance.
Without GPU-Z, the rig can go full performance but it takes at least half an hour to do so (this is something that I recently discovered, will be doing more observations..)
@Doktor
Every once in a while, after an algo change, after the GPU's are initialized, the hashing does not begin, and the watchdog does not react at all so I have to manually restart:
[2018-09-10 16:08:34] GPU0: Radeon RX 580 Series [Ellesmere] [8192 MB][Intensity 56.0][W: 8][T: 2][K: 1][BUS: 4]
[2018-09-10 16:08:34] GPU1: Radeon RX 580 Series [Ellesmere] [8192 MB][Intensity 56.0][W: 8][T: 2][K: 1][BUS: 13]
[2018-09-10 16:08:34] GPU2: Radeon RX 580 Series [Ellesmere] [8192 MB][Intensity 56.0][W: 8][T: 2][K: 1][BUS: 12]
[2018-09-10 16:08:34] GPU3: Radeon RX 580 Series [Ellesmere] [8192 MB][Intensity 56.0][W: 8][T: 2][K: 1][BUS: 14]
[2018-09-10 16:08:34] GPU4: Radeon RX 580 Series [Ellesmere] [8192 MB][Intensity 56.0][W: 8][T: 2][K: 1][BUS: 1]
[2018-09-10 16:08:34] GPU5: Radeon RX 580 Series [Ellesmere] [8192 MB][Intensity 56.0][W: 8][T: 2][K: 1][BUS: 11]
[2018-09-10 16:08:34] GPU6: Radeon RX 580 Series [Ellesmere] [8192 MB][Intensity 56.0][W: 8][T: 2][K: 1][BUS: 16]
[2018-09-10 16:08:34] GPU7: Radeon RX 580 Series [Ellesmere] [8192 MB][Intensity 56.0][W: 8][T: 2][K: 1][BUS: 8]
[2018-09-10 16:08:34] ADL is enabled
[2018-09-10 16:08:34] Algo switching mode enabled
[2018-09-10 16:08:34] Algo switch minimum time : 600 seconds
[2018-09-10 16:08:34] You are not using the recommended Adrenalin 18.6.1 or 18.3.4 driver, hashing speed can be decreased.
[2018-09-10 16:08:34] Cryptonight BitTube V2 mode enabled
[2018-09-10 16:08:34] DevFee pool SET
[2018-09-10 16:08:34] DevFee address SET
[2018-09-10 16:08:34] Starting init of mining threads
[2018-09-10 16:08:34] Loading compiled kernel for DEVICE BUS ID 4 ...
[2018-09-10 16:08:35] Loading compiled kernel for DEVICE BUS ID 4 ...
[2018-09-10 16:08:36] Loading compiled kernel for DEVICE BUS ID 13 ...
[2018-09-10 16:08:37] Loading compiled kernel for DEVICE BUS ID 13 ...
[2018-09-10 16:08:39] Loading compiled kernel for DEVICE BUS ID 12 ...
[2018-09-10 16:08:40] Loading compiled kernel for DEVICE BUS ID 12 ...
[2018-09-10 16:08:41] Loading compiled kernel for DEVICE BUS ID 14 ...
[2018-09-10 16:08:42] Loading compiled kernel for DEVICE BUS ID 14 ...
[2018-09-10 16:08:43] Loading compiled kernel for DEVICE BUS ID 1 ...
[2018-09-10 16:08:45] Loading compiled kernel for DEVICE BUS ID 1 ...
[2018-09-10 16:08:46] Loading compiled kernel for DEVICE BUS ID 11 ...
[2018-09-10 16:08:47] Loading compiled kernel for DEVICE BUS ID 11 ...
[2018-09-10 16:08:48] Loading compiled kernel for DEVICE BUS ID 16 ...
[2018-09-10 16:08:49] Loading compiled kernel for DEVICE BUS ID 16 ...
[2018-09-10 16:09:20] DFP online load: SUCCESS
[2018-09-10 16:09:20] DevFee pool SET
[2018-09-10 16:09:20] DevFee address SET ------> The hashing does not begin
[2018-09-10 16:19:10] Stopping miner process ------> Here I'm manually stopping the miner, this could have been an hour and there still wouldn't be any hashes, with no intervention from Watchdog.
This happens once or twice a day.
I'm using the same tried and tested drivers from the good old times, so that's why there's a warning.