See first post or readme.txt (-di command).

Which blockchain driver did you use?  I have not found any of them to be stable.  Also, I have had the same results with the Sapphire rx 580 8g cards when changing the bios.  I can't get them to hash as the 480 8g rates that I can get with a simple bios mod.  Always lower, and some of the cards are lower just because and I can't seem to do anything that affects them for the good, and any increase in clock speeds seems to just slow them down.

Hey Everyone,

After many failed attempts, I've run out of options that I currently comprehend and ask for your help.  I'm currently successfully mining Musicoin and unsuccessfully mining DCR out of curiosity and obviously not profit.  No matter what I seem to do, 100% of my DCR shares fail.  Here's what I've gathered and attempted based on reading here, watching YouTube, praying to every god I can think of, etc..

1) Turned off MSI Afterburner (I have 2-1070s)
2) Changed my intensity to 80
3) Tried changing port to 3344 as per other earlier posts
4) Changed back to what suprnova states is correct for Claymore 5) I'm running Claymore 10.0
6) I've tried it on 2 separate machines
7) Again, Musicoin mining is succesful
8 )....
9) Drink
10) Not profiting

Here's what I'm seeing on Claymore

This is my batch file

If there is something glaringly obvious or I've missed something somewhere back, I apologize in advance.  Thanks for your time.

*flame suit on*

Exact same problem here... My 580's are also sapphires.. I'm using latest Blockchain drivers. Anyone else here getting loss in hashing when turning settings up in AB?

Thank fo miner. I understand the potential Nvidia not yet been revealed?

Please, all that have a RX 480 8GB (Shappire Nitro + 8GB) can post the best values for "-dcri"? For now I set "-dcri 23" cause I think that when I increase it to 24, 25 or more Claymore seems unstable and sometimes my hashrate fluctuates. Many thanks in advance

Show us your bat and config files.

@Claymore: BUG REPORT.

TL;DR: please run reboot.bat by -minspeed if r>=1 (not only with r=1).


Win10, miner 10.0, latest blockchain drivers (23 Aug). It does not reboot if -minspeed not reached and -r X set (X>1), just restarts miner.
This, formally speaking, is not a bug (since README says it reboots if r=1). But by logic, if one sets r>1 (that is, wants reboot on either error or by timer), seems reasonable to reboot also by -minspeed.

The real use case: unstable rig instance after miner restart (first boot ok but any miner restart may fail).
1) pool drops connection every 24h (some pools)
2) miner reconnects, but system hangs and reboots
3) AMD driver resets clocks to default
4) miner starts with default clocks and has low hashrate (AMD driver changes it only after miner restarted)
5) miner restarts by -minspeed, rates set to ok, but unstable system hangs and reboots again...
6) loop to 3 (default clocks again)

If miner reboots on -minspeed instead of restart, all would be ok (since new clocks are already set, and reboot is by command, not by driver error).

Using AB/Trixx to preset clocks will resolve the issue, but I prefer to set rates in the miner.


ANOTHER ISSUE: does anybody have reboots on Linux with NVIDIA on OpenCL error? I set -r1 but even if some card has 0 H/s, and/or -minspeed is set, miner does not react and does not reboot neither restart. Anybody to confirm?

Higher clocks => higher power, yes.

To undervolt there are few ways:
- change powerplay table voltages (in BIOS or at runtime)
- change DPM states (use lower states = lover volts with high clocks)
- change VDDC voltage offsets (either fix BIOS tables, or patch VDDC offsets into BIOS tables, or use I2C at runtime)

The issue is that different drivers and platforms behave differently. Say, some ignore BIOS voltage tables, some use driver defaults, etc, etc. So there is no single "right" way to downvolt any card.

On Windows the best way could be to use WattTool to change VDDC offset, it uses i2c to update hardware voltage offset. But every voltage regulator requires own commands. WattTool was great and worked with many cards but its author disappeared. Still, even with latest drivers WattTool does not work with powerplay tables but can change VDDC offset. I2C method is better than -cvddc since it allows to set VDDC lesser than MVDDC. Changing VDDC sets it to max(MVDDC, VDDC).

Linux used by big farms, and no one wants to share the technology with public for free. They usually want 1-5-10 BTC for that (and actually different cards, different patches).

On Windows I use any tool (AB, Trixx, -mclock) to set memory clocks, and use WattTool to downvolt via VDDC offset. It gives best results but requires settings VDDC offset at runtime once after boot (not an issue). Linux tools similar to WattTool are not available freely, AFAIK.

On Linux the simplest way is to set higher clocks for lower DPM states (4, 5, 6, 7) and force lower state (4-6) to use lower voltages. All can be done at boot. Runtime voltage changes usually show successful changes, but actually do not change real wattage (from the wall). And BIOS changes ofter are ignored by Linux drivers.