Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

COMPUTE ERROR in 2.9.3 on AMD VEGA 56 persists... #213

Closed
vasssek opened this issue Jan 17, 2019 · 6 comments
Closed

COMPUTE ERROR in 2.9.3 on AMD VEGA 56 persists... #213

vasssek opened this issue Jan 17, 2019 · 6 comments

Comments

@vasssek
Copy link

vasssek commented Jan 17, 2019

Hi, please could you check why I have sometimes compute error even in 2.9.3 ver ? It behaves same as on 2.9.1 version.
@vasssek
Copy link
Author

vasssek commented Jan 17, 2019 •
edited
Loading

Same issue also on RX560 - I tried it also without overclocking. Some jobs are accepted but sometimes THREAD COMPUTE ERROR has been appeared.

I have tried AMD windows drivers: 18.5.2, 18.6.1, 18.8.2, 18.10.2 but this issue is still there.

@Unnameless
Copy link

I have the same problem with Vega 56 but this also occurs with the RX580, stock, not OCed and not undervolted with Hynix VRAM.

@420coupe
Copy link

has anyone tried with AMD 17.40 drivers?

@vasssek
Copy link
Author

vasssek commented Jan 27, 2019 •
edited
Loading

Hi,

Today I tried to unistall my current drivers through amd DRIVER cleanuputility-x64.exe, then install AMD Win driver v. 18.5.2, and xmrig-amd starts to work without COMPUTE ERRORS. It looks like I have two drivers mixed in windows cache...

Good work @xmrig :-)

@vasssek vasssek closed this as completed Jan 27, 2019
@tttony
Copy link

tttony commented Feb 2, 2019

@vasssek I also have 560s, I have always use 17.4.4 drivers with no problems, with this driver I get ~315 h/s per thread, 2 threads, so ~630 h/s per card, 1000 clock / mem 1750 ~60º temps, the config per thread is: intensity: 416, worksize: 32, unroll: 8, would like to know what's your config and h/s

@vasssek
Copy link
Author

vasssek commented Feb 4, 2019 •
edited
Loading

It depends on coin which you mine. I prefer XTL, XMR or ETH.
XTL:
{
"algo": "cn/half",
"background": false,
"colors": true,
"donate-level": 1,
"log-file": null,
"print-time": 60,
"retries": 5,
"retry-pause": 5,
"opencl-platform": 1,
"threads": [

{ "index" : 0,
"intensity" : 416, "worksize" : 8,
"affine_to_cpu" : false, "strided_index" : 2
},
{ "index" : 0,
"intensity" : 416, "worksize" : 8,
"affine_to_cpu" : false, "strided_index" : 2
} ],

2019-02-04 11:45:40] speed 10s/60s/15m 880.4 n/a n/a H/s max 881.2 H/s
| THREAD | GPU | 10s H/s | 60s H/s | 15m H/s |
| 0 | 0 | 439.7 | n/a | n/a |
| 1 | 0 | 440.1 | n/a | n/a |

XMR:
{
"algo": "cryptonight",
"background": false,
"colors": true,
"donate-level": 1,
"log-file": null,
"print-time": 60,
"retries": 10,
"retry-pause": 10,
"opencl-platform": 1,
"threads": [

{ "index" : 0,
"intensity" : 1024, "worksize" : 32,
"affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 2,
"unroll" : 16, "comp_mode" : true
} ],

[2019-02-04 11:46:35] speed 10s/60s/15m 438.9 n/a n/a H/s max n/a H/s
| THREAD | GPU | 10s H/s | 60s H/s | 15m H/s |
| 0 | 0 | 438.9 | n/a | n/a |

ETH: 14,8Mh/s

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tttony @vasssek @420coupe @Unnameless