You cannot get 29-30 anymore with this card. You are 2 months late. That's because of the hashrate dropping for AMD cards on each epoch. The actual rate now is somewhere 27+. If someone else has better hashrate for this card, please share the bios.

Hello guys, I have GIGABYTE Radeon RX 580 GAMING 8GB Its def give 21 mhs after flash 26mhs. can someone help ? i would like got 28-30 mhs. what I Did: in flash/Bios 24 Mhs Memory MHz Mv 300 1000 1000 1000 2000 1000 Mhz | Timing Strap 1750 copy 2000 replace. in flash/Bios 26 mhs Memory MHz Mv 300 900 1000 900 2000 900 Mhz | Timing Strap 1750 copy 2000 replace. any ideas to get 28-30 mhs?

You cannot get 29-30 anymore with this card. You are 2 months late. That's because of the hashrate dropping for AMD cards on each epoch. The actual rate now is somewhere 27+. If someone else has better hashrate for this card, please share the bios.

Hello guys, I have GIGABYTE Radeon RX 580 GAMING 8GB Its def give 21 mhs after flash 26mhs. can someone help ? i would like got 28-30 mhs. what I Did: in flash/Bios 24 Mhs Memory MHz Mv 300 1000 1000 1000 2000 1000 Mhz | Timing Strap 1750 copy 2000 replace. in flash/Bios 26 mhs Memory MHz Mv 300 900 1000 900 2000 900 Mhz | Timing Strap 1750 copy 2000 replace. any ideas to get 28-30 mhs?

All of sudden my runner kept restarting. It has been stable in the last few days. Here is the log. Please help.I am using 9.7, 5x107022:51:32:758 18c0 GPU 0, GpuMiner cu_k01 failed 4, unspecified launch failure22:51:32:867 18c0 GPU 0, GpuMiner kx failed 122:51:32:868 2104 GPU 2, GpuMiner cu_k01 failed 4, unspecified launch failure22:51:32:870 2104 GPU 2, GpuMiner kx failed 122:51:32:871 20d0 GPU 1, GpuMiner cu_k01 failed 4, unspecified launch failure22:51:32:872 20d0 GPU 1, GpuMiner kx failed 122:51:32:868 18c0 Set global fail flag, failed GPU022:51:32:873 236c GPU 3, GpuMiner cu_k01 failed 4, unspecified launch failure22:51:32:874 236c GPU 3, GpuMiner kx failed 122:51:32:875 2398 GPU 4, GpuMiner cu_k01 failed 4, unspecified launch failure22:51:32:876 2398 GPU 4, GpuMiner kx failed 122:51:32:876 18c0 GPU 0 failed22:51:32:877 18b4 GPU 0, GpuMiner cu_k01 failed 4, unspecified launch failure22:51:32:878 18b4 GPU 0, GpuMiner kx failed 122:51:32:875 236c Set global fail flag, failed GPU322:51:32:872 20d0 Set global fail flag, failed GPU122:51:32:876 2398 Set global fail flag, failed GPU422:51:32:881 2398 GPU 4 failed22:51:32:879 18b4 Set global fail flag, failed GPU022:51:32:885 18b4 GPU 0 failed22:51:32:887 2370 GPU 3, GpuMiner cu_k01 failed 4, unspecified launch failure22:51:32:889 2370 GPU 3, GpuMiner kx failed 122:51:32:890 18c4 GPU 1, GpuMiner cu_k01 failed 4, unspecified launch failure22:51:32:891 18c4 GPU 1, GpuMiner kx failed 122:51:32:892 22bc GPU 4, GpuMiner cu_k01 failed 4, unspecified launch failure22:51:32:892 22bc GPU 4, GpuMiner kx failed 122:51:32:893 20d0 GPU 1 failed22:51:32:890 2370 Set global fail flag, failed GPU322:51:32:894 2370 GPU 3 failed22:51:32:892 18c4 Set global fail flag, failed GPU122:51:32:895 18c4 GPU 1 failed22:51:32:893 22bc Set global fail flag, failed GPU422:51:32:896 22bc GPU 4 failed22:51:32:897 236c GPU 3 failed22:51:32:871 2104 Set global fail flag, failed GPU222:51:32:899 2104 GPU 2 failed22:51:32:900 18b0 GPU 2, GpuMiner cu_k01 failed 4, unspecified launch failure22:51:32:901 18b0 GPU 2, GpuMiner kx failed 122:51:32:902 18b0 Set global fail flag, failed GPU222:51:32:902 18b0 GPU 2 failed22:51:33:053 1dbc ETH: checking pool connection...22:51:33:053 1dbc send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}22:51:33:223 1dbc got 243 bytes22:51:33:224 1dbc buf: {"jsonrpc":"2.0","id":0,"result":["0xa3ecfc51a01c250eeb38735fab8f61704cae68c8c482d88121d89578a3508fd0","0xcb5d57db3888696bcf7c9b09b0c77c3ba41955b53950b8197064dc9df81cda49","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}22:51:33:225 1dbc parse packet: 24222:51:33:225 1dbc ETH: job is the same22:51:33:226 1dbc new buf size: 022:51:33:861 b9c GPU0 t=71C fan=54%, GPU1 t=69C fan=51%, GPU2 t=76C fan=51%, GPU3 t=64C fan=49%, GPU4 t=73C fan=51%22:51:33:861 b9c em hbt: 0, dm hbt: 0, fm hbt: 0,22:51:33:861 b9c watchdog - thread 0 (gpu0), hb time 351622:51:33:861 b9c watchdog - thread 1 (gpu0), hb time 111022:51:33:861 b9c watchdog - thread 2 (gpu1), hb time 112522:51:33:861 b9c watchdog - thread 3 (gpu1), hb time 123522:51:33:861 b9c watchdog - thread 4 (gpu2), hb time 123522:51:33:861 b9c watchdog - thread 5 (gpu2), hb time 112522:51:33:861 b9c watchdog - thread 6 (gpu3), hb time 125022:51:33:861 b9c watchdog - thread 7 (gpu3), hb time 112522:51:33:861 b9c watchdog - thread 8 (gpu4), hb time 123522:51:33:861 b9c watchdog - thread 9 (gpu4), hb time 111022:51:33:861 b9c WATCHDOG: GPU error, you need to restart miner22:51:33:861 b9c Rebooting

Super off-topic, but any chance you would ever add support for Intel Xeon Phi? They are starting to come on the market affordably as data centers retire them, they take OpenCL, have large amounts of onboard RAM and can directly allocate system RAM via the IMC (I believe).

2 Claymore Is there any possibility that this "epoch rising" with loosing H\s on AMD cards will be fixed? Some driver fix by AMD or miner code change? I think this question reflect 10000+ more ppl, not only me. I saw before you post, that you working on it. Any info? That is really important for many of us. Thank you P\S I do not need any answers from anybody exept Claymore.

Quick question. Is changing/tweaking the -dcri always advised? Will it increase the revenue? And for instance, could changing the dcri value not effect Eth mining but does increase Sia/LBRY/DCR? Or will it always decrease Eth mining if one of the dual mined coins increases?

It changes both values. Lower dcri higher ETH speed but lower second coin speed. You try to find the value where your card is mining both at a reasonable level. You will lose some ETH speed to get higher second coin speed. Second coins are low so it might not be worth the extra power to dual mine. I stopped dual mining and only mine ETH now. Plus it is much harder on the cards and could burn them out faster than normal.

Quick question. Is changing/tweaking the -dcri always advised? Will it increase the revenue? And for instance, could changing the dcri value not effect Eth mining but does increase Sia/LBRY/DCR? Or will it always decrease Eth mining if one of the dual mined coins increases?

It changes both values. Lower dcri higher ETH speed but lower second coin speed. You try to find the value where your card is mining both at a reasonable level. You will lose some ETH speed to get higher second coin speed. Second coins are low so it might not be worth the extra power to dual mine. I stopped dual mining and only mine ETH now. Plus it is much harder on the cards and could burn them out faster than normal.

Quick question. Is changing/tweaking the -dcri always advised? Will it increase the revenue? And for instance, could changing the dcri value not effect Eth mining but does increase Sia/LBRY/DCR? Or will it always decrease Eth mining if one of the dual mined coins increases?

Hi, im mining on ethermine pool with 5x580 with 140 stable hash reported, but effective sometime goes up but some more goes down and average is 125. Its normal or I need to low memory or clock overclock? btw incorrect shares are made for too much memory OC or just core? I got about 1 / each hour (NOT REJECTED) Thanks

The effective hash rate varying quite a bit is normal as finding a share is based solely on luck. Over time it will average out to close to your real hash rate. Incorrect shares tend to be caused by memory overclocking. Overclocking the core too much will crash the gpu and/or your computer. Overclocking the memory too much can crash the gpu also. If you are getting incorrect shares a lot you are overclocking too much.

Hi, im mining on ethermine pool with 5x580 with 140 stable hash reported, but effective sometime goes up but some more goes down and average is 125. Its normal or I need to low memory or clock overclock? btw incorrect shares are made for too much memory OC or just core? I got about 1 / each hour (NOT REJECTED) Thanks

Anyone else loose an hour of mining earlier using ethos on nanopool? My windows rigs worked fine thru it, so I assume it's something with ethos? As only my ethos rigs went down.

The DAG epoch issue: it seems AMD fixed it for Vega in drivers and now they are working on Polaris. New drivers will be available soon, may be in two weeks or so.