Bitcoin Forum

Alternate cryptocurrencies => Mining (Altcoins) => Topic started by: Wananavu99 on June 24, 2018, 12:08:14 AM



Title: Help with AMD Vega GPU Hashing Issues
Post by: Wananavu99 on June 24, 2018, 12:08:14 AM
Hello there,

I was doing some testing on my GPUs and realized that for one of my cards I'm only getting (GPU3) 200-300h/s, whereas the others are hashing around (GPU0) 1600-1700h/s. 

Here's what I found, wondering if anyone has a fix for this.  Both cards are updated with the same drivers and I'm still not sure what's going on.   

This is on Cast XMR mining. 

GPU0

[16:59:45] Initializing GPU, loading kernel ...
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2580.6)
Driver Version OK.
GPU0: Radeon RX Vega (gfx900) | 56 Compute Units | Memory (MB): 8176 | Intensity: 7 / 10
[16:59:56] Connecting to 52.168.91.103:5555 ...
[16:59:56] Connected to pool.
[16:59:56] New Job received (CryptoNightV7).
[16:59:56] Difficulty changed. Now: 10000.
[17:00:00] GPU0 | 39°C | Fan 0 RPM | 1671.6 H/s
[17:00:02] GPU0 Found Nonce, submitting...
[17:00:02] Share Accepted -> +1
[17:00:02] Shares: 1 Accepted, 0 Errors | Hash Rate Avg: 1671.6 H/s | Avg Search Time: 0.0 sec
[17:00:04] GPU0 | 41°C | Fan 0 RPM | 1734.8 H/s
[17:00:08] GPU0 | 43°C | Fan 0 RPM | 1734.8 H/s
[17:00:13] GPU0 | 44°C | Fan 0 RPM | 1733.9 H/s
[17:00:17] GPU0 | 46°C | Fan 0 RPM | 1734.3 H/s
[17:00:18] New Job received (CryptoNightV7). Avg Job Time: 22.0 sec
[17:00:18] Difficulty changed. Now: 15000.

GPU3

[16:57:59] Initializing GPU, loading kernel ...
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2580.6)
Driver Version OK.
GPU3: Radeon RX Vega (gfx900) | 56 Compute Units | Memory (MB): 8176 | Intensity: 7 / 10
[16:58:11] Connecting to 52.168.91.103:5555 ...
[16:58:11] Connected to pool.
[16:58:11] New Job received (CryptoNightV7).
[16:58:11] Difficulty changed. Now: 10000.
[16:58:12] New Job received (CryptoNightV7). Avg Job Time: 1.0 sec
                                                      [16:58:28] GPU3 | 37°C | Fan 0 RPM | 206.3 H/s
[16:58:46] GPU3 | 42°C | Fan 0 RPM | 206.2 H/s
[16:59:03] GPU3 | 47°C | Fan 0 RPM | 205.1 H/s
[16:59:03] GPU3 Found Nonce, submitting...
[16:59:03] Share Accepted -> +1
[16:59:03] Shares: 1 Accepted, 0 Errors | Hash Rate Avg: 205.9 H/s | Avg Search Time: 0.0 sec
[16:59:03] GPU3 Found Nonce, submitting...
[16:59:04] Share Accepted -> +1
[16:59:04] Shares: 2 Accepted, 0 Errors | Hash Rate Avg: 205.9 H/s | Avg Search Time: 26.0 sec
[16:59:18] New Job received (CryptoNightV7). Avg Job Time: 33.5 sec
[16:59:18] Difficulty changed. Now: 15000.
[16:59:21] GPU3 | 51°C | Fan 0 RPM | 203.8 H/s


Title: Re: Help with AMD Vega GPU Hashing Issues
Post by: OgNasty on June 24, 2018, 03:24:22 AM
When you check the AMD app, what does it say the usage % of GPU3 is?


Title: Re: Help with AMD Vega GPU Hashing Issues
Post by: aleksej996 on June 24, 2018, 03:45:09 PM
One time I was experiencing issues with my GPU being too slow it turned out I didn't connect it well to my motherboard.
Make sure all the cables are connected first of all before you start banging your head on what could be the problem.


Title: Re: Help with AMD Vega GPU Hashing Issues
Post by: Wananavu99 on June 25, 2018, 02:01:53 AM
Hi Guys, figured it out, Vegas are very sensitive.  So what I finally did after spending hours on this was to add an Nvidia card.  This is an old Nvidia card from an old PC and now I'm hashing 1800 h/s per card.  Just took forever trying to figure it out. 


Title: Re: Help with AMD Vega GPU Hashing Issues
Post by: jmigdlc99 on June 25, 2018, 06:45:31 AM
Hi Guys, figured it out, Vegas are very sensitive.  So what I finally did after spending hours on this was to add an Nvidia card.  This is an old Nvidia card from an old PC and now I'm hashing 1800 h/s per card.  Just took forever trying to figure it out. 

Pretty weird that your solution to fix an issue with your AMD GPU is to install an NVIDIA GPU.

Your problem probably had to do with AMD driver's compute mode settings. Possibly, you were using a driver version that required you to manually turn on "compute mode" but then this was automatically done for you because when you installed a new GPU, the AMD driver settings also screwed themselves up in a way that made your GPU run on different drivers (do you have the aug. 23 blockchain driver also installed?).


Title: Re: Help with AMD Vega GPU Hashing Issues
Post by: Specialist1 on June 25, 2018, 06:29:01 PM
Take a look at my channel. It may answer many of your questions moving forward. I talk a lot about this in a few of my videos. Best of luck. https://www.youtube.com/channel/UCrIMbomEyfV-EyKfVokfNiw



Hello there,

I was doing some testing on my GPUs and realized that for one of my cards I'm only getting (GPU3) 200-300h/s, whereas the others are hashing around (GPU0) 1600-1700h/s. 

Here's what I found, wondering if anyone has a fix for this.  Both cards are updated with the same drivers and I'm still not sure what's going on.   

This is on Cast XMR mining. 

GPU0

[16:59:45] Initializing GPU, loading kernel ...
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2580.6)
Driver Version OK.
GPU0: Radeon RX Vega (gfx900) | 56 Compute Units | Memory (MB): 8176 | Intensity: 7 / 10
[16:59:56] Connecting to 52.168.91.103:5555 ...
[16:59:56] Connected to pool.
[16:59:56] New Job received (CryptoNightV7).
[16:59:56] Difficulty changed. Now: 10000.
[17:00:00] GPU0 | 39°C | Fan 0 RPM | 1671.6 H/s
[17:00:02] GPU0 Found Nonce, submitting...
[17:00:02] Share Accepted -> +1
[17:00:02] Shares: 1 Accepted, 0 Errors | Hash Rate Avg: 1671.6 H/s | Avg Search Time: 0.0 sec
[17:00:04] GPU0 | 41°C | Fan 0 RPM | 1734.8 H/s
[17:00:08] GPU0 | 43°C | Fan 0 RPM | 1734.8 H/s
[17:00:13] GPU0 | 44°C | Fan 0 RPM | 1733.9 H/s
[17:00:17] GPU0 | 46°C | Fan 0 RPM | 1734.3 H/s
[17:00:18] New Job received (CryptoNightV7). Avg Job Time: 22.0 sec
[17:00:18] Difficulty changed. Now: 15000.

GPU3

[16:57:59] Initializing GPU, loading kernel ...
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2580.6)
Driver Version OK.
GPU3: Radeon RX Vega (gfx900) | 56 Compute Units | Memory (MB): 8176 | Intensity: 7 / 10
[16:58:11] Connecting to 52.168.91.103:5555 ...
[16:58:11] Connected to pool.
[16:58:11] New Job received (CryptoNightV7).
[16:58:11] Difficulty changed. Now: 10000.
[16:58:12] New Job received (CryptoNightV7). Avg Job Time: 1.0 sec
                                                      [16:58:28] GPU3 | 37°C | Fan 0 RPM | 206.3 H/s
[16:58:46] GPU3 | 42°C | Fan 0 RPM | 206.2 H/s
[16:59:03] GPU3 | 47°C | Fan 0 RPM | 205.1 H/s
[16:59:03] GPU3 Found Nonce, submitting...
[16:59:03] Share Accepted -> +1
[16:59:03] Shares: 1 Accepted, 0 Errors | Hash Rate Avg: 205.9 H/s | Avg Search Time: 0.0 sec
[16:59:03] GPU3 Found Nonce, submitting...
[16:59:04] Share Accepted -> +1
[16:59:04] Shares: 2 Accepted, 0 Errors | Hash Rate Avg: 205.9 H/s | Avg Search Time: 26.0 sec
[16:59:18] New Job received (CryptoNightV7). Avg Job Time: 33.5 sec
[16:59:18] Difficulty changed. Now: 15000.
[16:59:21] GPU3 | 51°C | Fan 0 RPM | 203.8 H/s


Title: Re: Help with AMD Vega GPU Hashing Issues
Post by: Shnikes101 on June 25, 2018, 09:16:37 PM
Hi Guys, figured it out, Vegas are very sensitive.  So what I finally did after spending hours on this was to add an Nvidia card.  This is an old Nvidia card from an old PC and now I'm hashing 1800 h/s per card.  Just took forever trying to figure it out. 

Pretty weird that your solution to fix an issue with your AMD GPU is to install an NVIDIA GPU.

Your problem probably had to do with AMD driver's compute mode settings. Possibly, you were using a driver version that required you to manually turn on "compute mode" but then this was automatically done for you because when you installed a new GPU, the AMD driver settings also screwed themselves up in a way that made your GPU run on different drivers (do you have the aug. 23 blockchain driver also installed?).

Most likely he added the older nvidia card to handle the machines display output.

If you're not using onboard video and relying on one of the Vegas to power display output, then you're going to see hashrate drops and will need to lower intensity on the card driving the video to prevent crashes.
Just guessing from experience - though I don't use Cast.

Now if he is feeling adventurous flash them to 64s, tweak the powertables a bit and hit 1950-2000 hash/card