Try:

- Disabling quickedit mode for console
- using -oldkernels 1
- using v11.0
- Do NOT run GPUZ or HWinfo while mining


- The newest drivers work fine you need to run pixel clock patcher
- Make sure the drivers are minimal install and you do custom install, unclick everything except the drivers


Single mining 10.6
Dual mining 11.0 (might fluctuate), 11.5, or 11.5 with -oldkernels 1

All are stable on my BIOS modded rx580s but each has different results


Use OverdrivenTool instead.  Far better solution


We hope so too!  Report back on testing.  Many are having problems with rx580s.

After installing the latest AMD drivers you need to run pixel clock patcher for any cards that are BIOS modded

Little update on testing my BIOS modded rx580 mini rig.  This is dual mining keccac and always the same bat file

v11.0 - 61.3 mhs with heavy fluctuation into the mid 50s
v11.5 - 61.9 mhs with heavy fluctuation as above -oldkernels 1 option used
v11.5 - 62.2 mhs fluctuation of a tenth at most(62.15 to 62.25), seems stable on the new kernels for some reason?

Heavy fluctuation would be down into the mid 50s.  Sometimes for a few minutes.  Each card would randomly drop 3-10%.

Here's the difference between when 11.5 was unstable (4%+ rejected no matter how much I slowed, plus freezing) with the new kernels and now:

- Not running HWinfo
- I didn't run GPUZ before, but it's important NOT to run it while mining
- updated to the new video drivers that came out march 19, minimal install which may be very important.  I had the bloat installed before.
- disabled QuickEdit mode in console
- Disabled all power states in the video card BIOS except the top

The card speeds and voltages are the same as before when I had instability.  I can't think of anything else that has changed.

Be careful updating to the new AMD drivers.  They will block all overdriving software until you run pixel clock patcher.  The patcher wasn't required before for all cards, now it will be.  I hope some here find this useful and Claymore as well.  Happy mining.  

PS will report back after running 24 hours on the new kernels.  I've only been running an hour but I can tell something has changed.

Your wallet will only be in the log a couple of times at the top.  It should literally take minutes for them to make a page.

Try disabling QuickEdit Mode for the console

Keccakc is different than keccak

I bet nicehash upgraded from v10.6

it's possible with the new kernels that modified ram timings aren't needed. Will report back in a few days on that.

This is exactly what I have found with my bios modded rx580s. I am glad I am not the only one. What version did you downgrade to 11.0?  Keep in mind what we are talking about is the fluctuation is in the miner or reported hashrate NOT effective hashrate which normally fluctuates due to luck.

So my options:
- try stock bios with new kernels
- wait for a fix
- use 11.0
- accept the fluctuation

Try uninstalling all of the AMD bloat especially Wattman.

I like to have the BIOS flashed with good fam and temp settings.  Then that becomes the default.

is your reported(mining rate in claymore not effective) hashrate fluctuating at all? Are you using oldkernels?

Try 1200/ 2170 for the hynix and the Samsung is able to do a lot of output with 2000.

Don't believe me but please try it yourself.  I am not talking about stales reported by the miner but rather by the pool. 

Miner can only change pools and find one that matches his hashrate.  I think it is mostly the pools fault.

I went from ethermine and 40 to 60 msec pings and tons of stales to anorak with 120 msec pings and no stales.  Zero.

For you guys having pool problems try anorak pool:

eth.anorak.tech:8002 2b difficulty less than 100 mhs
eth.anorak.tech:8004 4b difficulty 100 mhs to 1000
eth.anorak.tech:8009 9b difficulty 1000 and above

For SSL change the 8 to 9

I haven't had a single stale

Yes just make sure after install the cards are set to compute

Page 1

I thinj you are right.  This happened before the fall update but it is still there.  Try it both ways yourself.  Open task manager with QuickEdit enabled see what happens. It's possible claymore is now incompatible with QuickEdit mode?

Also I think you are having a different issue altogether.  I wish you luck in resolving.

Try disabling QuickEdit Mode in the properties of your batch file

What ram straps are you running?  I think that has everything to do with it.  Some work with new some don't.