PhoenixMiner
Changes in version 2.8c (since 2.7c):
New kernels for all supported AMD GPUs, providing higher hashrate and lower percentage of stale shares. The new kernels are used by default for AMD GPUs. You can also revert to using the old kernels with -clnew 0
When using the new kernels, the mining intensity is 12 by default instead of 10
The mining intensity range is now up to 14. Use high -mi only with the new AMD kernels as for the other kernels the stale shares will increase too much
Small CUDA kernel stability improvements that also may (very) slightly increase the speed of Nvidia cards
CPU utilization during normal operation is lowered by about a factor of 10 regardless of the number of GPUs
Added support for -tstop and -tstart options to stop mining on given GPU if the temperature rise above specified value and restart it after it cools down below -tstart temperature
Fixed the problem with console window freezing after scrolling
Implemented new -gpow n option to lower the GPU utilization (default: 100, the value is the desired GPU utilization in percent)
Implemented the -li option to lower the intensity (use this instead of -gpow if you are already using -mi with low values)
Improved GPU speed statistics, using moving average window for each GPU. You can change the size of the window with the -gswin option (5-30 seconds; default 15; use 0 to revert to the old way of using 5 second "quants" which are independent of each other)
Specify GPU number above 9 by typing three-digit sequence at the console (e.g. type 011 to pause or resume GPU11)
Other small improvements and changes
Added support for the miner_getstat2 remote monitoring request

PhoenixMiner is fast (arguably the fastest) Ethash (ETH, ETC, Muiscoin, EXP, UBQ, etc.) miner that supports
both AMD and Nvidia cards (including in mixed mining rigs). It runs under Windows x64
and has a developer fee of 0.65% (the lowest in the industry). This means that every 90
minutes the miner will mine for us, its developers, for 35 seconds.

The speed is generally faster than Claymore's Ethereum miner in eth only mode
(we have measured about 0.4-1.3% speed improvement but your results may be slightly lower or
higher depending on the GPUs). To achieve highest possible speed on AMD cards it may be needed
to manually adjust the GPU tune factor (a number from 8 to about 400, which can be changed
interactively with the + and - keys while the miner is running).

If you have used Claymore's Dual Ethereum miner, you can switch to PhoenixMiner with
minimal hassle as we support most of Claymore's command-line options and confirguration
files with the notable exception of the dual mining feature (yet).

Please note that PhoenixMiner is extensively tested on many mining rigs but this is the
first public release and there still may be some bugs. Additionally, we are actively working on
bringing many new features in the future releases. If you encounter any problems or have
feature requests, please post them here (in this thread). We will do our best to answer in timely
fashion.



1. Quick start

You can download PhoenixMiner 2.8c from here:
https://goo.gl/zrLcsS

If you want to check the integrity of the downloaded file, please use the following hashes:
Code:
File: PhoenixMiner_2.8c.zip
SHA-1: 6ca71cda4936e096c4a3070134a0978a8fac4aa4
SHA-256: 921a53fbb21fb37735108e48efaa5d600c4e7bbe9da6661b832ace97d29a5efc
SHA-512: 31eeccffe9816e3493531852a8ec7e7868fa8e113237ec538349e6d18c925673a718f561b625b7cce31c994f28a18bd2cf23d6b299a53e69fb74135175f0b499

Here are the command line parameters for some of the more popular pools and coins:

ethermine.org (ETH):
PhoenixMiner.exe -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal YourEthWalletAddress.WorkerName -proto 3
ethermine.org (ETH, secure connection):
PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal YourEthWalletAddress.WorkerName -proto 3
ethpool.org (ETH):
PhoenixMiner.exe -pool eu1.ethpool.org:3333 -pool2 us1.ethpool.org:3333 -wal YourEthWalletAddress.WorkerName -proto 3
dwarfpool.com (ETH):
PhoenixMiner.exe -pool eth-eu.dwarfpool.com:8008 -wal YourEthWalletAddress/WorkerName -pass x
nanopool.org (ETH):
PhoenixMiner.exe -pool eu1.nanopool.org:9999 -wal YourEthWalletAddress/WorkerName -pass x
nicehash (ethash):
PhoenixMiner.exe -pool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -wal YourBtcWalletAddress -pass x -proto 4 -stales 0
f2pool (ETH):
PhoenixMiner.exe -epool eth.f2pool.com:8008 -ewal YourEthWalletAddress -pass x -worker WorkerName
miningpoolhub (ETH):
PhoenixMiner.exe -pool us-east.ethash-hub.miningpoolhub.com:20535 -wal YourLoginName.WorkerName -pass x -proto 1
coinotron.com (ETH):
PhoenixMiner.exe -pool coinotron.com:3344 -wal YourLoginName.WorkerName -pass x -proto 1
ethermine.org (ETC):
PhoenixMiner.exe -pool eu1-etc.ethermine.org:4444 -wal YourEtcWalletAddress.WorkerName
dwarfpool.com (EXP):
PhoenixMiner.exe -pool exp-eu.dwarfpool.com:8018 -wal YourExpWalletAddress/WorkerName
miningpoolhub (MUSIC):
PhoenixMiner.exe -pool europe.ethash-hub.miningpoolhub.com:20585 -wal YourLoginName.WorkerName -pass x -proto 1
ubiqpool (UBIQ):
PhoenixMiner.exe -pool stratum+tcp://eu.ubiqpool.io:8008 -wal YourUbiqWalletAddress -pass x -worker WorkerName
minerpool.net (PIRL):
PhoenixMiner.exe -pool pirl.minerpool.net:8002 -wal YourPirlWalletAddress -pass x -worker WorkerName
dodopool.com (Metaverse ETP):
PhoenixMiner.exe -pool etp.dodopool.com:8008 -wal YourMetaverseETPWalletAddress -worker Rig1 -pass x
minerpool.net (Ellaism):
PhoenixMiner.exe -pool ella.minerpool.net:8002 -wal YourEllaismWalletAddress -worker Rig1 -pass x

2. Features, requirements, and limitations

* Supports AMD Vega, 580/570/480/470, 460/560, Fury, 390/290 and older AMD GPUs with enough VRAM
* Supports Nvidia 10x0 and 9x0 series as well as older cards with enough VRAM
* Highly optimized OpenCL and CUDA cores for maximum ethash mining speed
* Lowest developer fee of 0.65% (35 seconds defvee mining per each 90 minutes)
* Advanced statistics: actual difficulty of each share as well as effective hashrate at the pool
* DAG file generation in the GPU for faster start-up and DAG epoch switches
* Supports all ethash mining pools and stratum protocols
* Supports secure pool connections (e.g. ssl://eu1.ethermine.org:5555) to prevent IP hijacking attacks
* Detailed statistics, including the individual cards hashrate, shares, temperature and fan speed
* Unlimited number of fail-over pools in epools.txt configuration file (or two on the command line)
* GPU tuning for the AMD GPUs to achieve maximum performance with your rig
* Supports devfee on alternative ethash currencies like ETC, EXP, Music, UBQ, Pirl, Ellaism, and Metaverse ETP. This allows you to use older cards with small VRAM or low hashate on current DAG epochs (e.g. GTX970).
* Full compatibility with the industry standard Claymore's Dual Ethereum miner, including most of command-line options, configuration files, and remote monitoring and management.
* More features coming soon!

PhoenixMiner requires Windows x64 (Windows 7, Windows 10, etc.). We are planning a Linux version in
the future but it may take some time.

PhenixMiner does not support dual mining. However we are working on this feature and will introduce it
soon. Solo mining is supported since version 2.7c.

While the miner is running, you can use some interactive commands. Press the key 'h' while the
miner's console window has the keyboard focus to see the list of the available commands. The
interactive commands are also listed at the end of the following section.

3. Command-line arguments

Note that PhoenixMiner supports most of the command-line options of Claymore's dual Ethereum miner
so you can use the same command line options as the ones you would have used with Claymore's miner.

Pool options:
-pool Ethash pool address (prepend the host name with ssl:// for SSL pool, or http:// for solo mining)
-wal Ethash wallet (some pools require user name and/or worker)
-pass Ethash password (most pools don't require it, use 'x' as password if unsure)
-worker Ethash worker name (most pools accept it as part of wallet)
-proto Selects the kind of stratum protocol for the ethash pool:
1: miner-proxy stratum spec (e.g. coinotron)
2: eth-proxy (e.g. dwarfpool, nanopool) - this is the default, works for most pools
3: qtminer (e.g. ethpool)
4: EthereumStratum/1.0.0 (e.g. nicehash)
-coin Ethash coin to use for devfee to avoid switching DAGs:
auto: Try to determine from the pool address (default)
eth: Ethereum
etc: Ethereum Classic
exp: Expanse
music: Musicoin
ubq: UBIQ
pirl: Pirl
ella: Ellaism
etp: Metaverse ETP
pgc: Pegascoin
akroma: Akroma
whale: WhaleCoin
vic: Victorium
-stales Submit stales to ethash pool: 1 - yes (default), 0 - no
-pool2 Failover ethash pool address. Same as -pool but for the failover pool
-wal2 Failover ethash wallet (if missing -wal will be used for the failover pool too)
-pass2 Failover ethash password (if missing -pass will be used for the failover pool too)
-worker2 Failover ethash worker name (if missing -worker will be used for the failover pool too)
-proto2 Failover ethash stratum protocol (if missing -proto will be used for the failover pool too)
-coin2 Failover devfee Ethash coin (if missing -coin will be used for the failover pool too)
-stales2 Submit stales to the failover pool: 1 - yes (default), 0 - no
General pool options:
-fret Switch to next pool afer N failed connection attempts (default: 3)
-ftimeout Reconnect if no new ethash job is receved for n seconds (default: 600)
-ptimeout Switch back to primary pool after n minutes. This setting is 30 minutes by default;
set to 0 to disable automatic switch back to primary pool.
-rate Report hashrate to the pool: 1 - yes, 0 - no (1 is the default)
Benchmark mode:
-bench [],-benchmark [] Benchmark mode, optionally specify DAG epoch. Use this to test your rig.
Remote control options:
-cdm Selects the level of support of the CDM remote monitoring:
0: disabled
1: read-only - this is the default
2: full (only use on secure connections)
-cdmport Set the CDM remote monitoring port (default is 3333). You can also specify
if you have a secure VPN connection and want to bind the CDM port to it
-cdmpass Set the CDM remote monitoring password
Mining options:
-amd Use only AMD cards
-nvidia Use only Nvidia cards
-gpus <123 ..n> Use only the specified GPUs (if more than 10, separate the indexes with comma)
-mi Set the mining intensity (0 to 14; 12 is the default for the new kernels on AMD GPUs; 10 is the default for Nvidia GPUs)
-gt Set the GPU tuning parameter (8 to 400). The default is 15. You can change the
tuning parameter interactively with the '+' and '-' keys in the miner's console window
-clKernel Type of OpenCL kernel: 0 - generic, 1 - optimized, 2 - alternative (1 is the default)
-clNew Use the new AMD kernels (0: no, 1: yes; default: 1)
-list List the detected GPUs devices and exit
-minRigSpeed Restart the miner if avg 5 min speed is below MH/s
-eres Allocate DAG buffers big enough for n epochs ahead (default: 2) to
avoid allocating new buffers on each DAG epoch switch, which should improve DAG switch stability
-lidag Slow down DAG generation to avoid crashes when swiching DAG epochs
(0-3, default: 0 - fastest, 3 - slowest). This option works only on AMD cards
-altinit Use alternative way to initialize AMD cards to prevent startup crashes
-wdog Enable watchdog timer: 1 - yes, 0 - no (1 is the default). The watchdog timer checks
periodically if any of the GPUs freezes and if it does, restarts the miner (see the -rmode
command-line parameter for the restart modes)
-rmode Selects the restart mode when a GPU crashes or freezes:
0: disabled - miner will shut down instead of restarting
1: restart with the same command line options - this is the default
2: reboot (shut down miner and execute reboot.bat)
-log Selects the log file mode:
0: disabled - no log file will be written
1: write log file but don't show debug messages on screen (default)
2: write log file and show debug messages on screen
-timeout Restart miner according to -rmode after n minutes
-gswin GPU stats time window (5-30 sec; default: 15; use 0 to revert to pre-2.8 way of showing momentary stats)
-gpow Lower the GPU usage to n% of maximum (default: 100). If you already use -mi 0 (or other low value) use -li instead
-li Another way to lower the GPU usage. Bigger n values mean less GPU utilization; the default is 0.
Hardware control options (most are for AMD cards only, only tt 0-4, tstop, and tstart are supported on Nvidia GPUs), use comma to specify different values for each GPU:
-tt Set fan control target temperature (special values: 0 - no HW monitoring on ALL cards,
1-4 - only monitoring on all cards with 30-120 seconds interval, negative - fixed fan speed at n %)
-fanmin Set fan control min speed in % (-1 for default)
-fanmax Set fan control max speed in % (-1 for default)
-tmax Set fan control max temperature (0 for default)
-powlim Set GPU power limit in % (from -75 to 75, 0 for default)
-cclock Set GPU core clock in MHz (0 for default)
-cvddc Set GPU core voltage in mV (0 for default)
-mclock Set GPU memory clock in MHz (0 for default)
-mvddc Set GPU memory voltage in mV (0 for default)
-tstop Pause a GPU when temp is >= n deg C (0 for default; i.e. off)
-tstart Resume a GPU when temp is <= n deg C (0 for default; i.e. off)
General Options:
-v,--version Show the version and exit
-h,--help Show information about the command-line options and exit

Additionally, while the miner is running, you can use the following interactive commands
in the console window by pressing one of these keys:
s Print detailed statistics
1-9 Pause/resume GPU1 ... GPU9
p Pause/resume the whole miner
+,- Increase/decrease GPU tuning parameter
g Reset the GPU tuning parameter
r Reload epools.txt and switch to primary ethash pool
e Select the current ethash pool
h Print this short help

4. Configuration files

Note that PhoenixMiner supports the same configuration files as Claymore's dual Ethereum miner
so you can use your existing configuration files without any changes.

Instead of using command-line options, you can also control PhoenixMiner with configuration
files. If you run PhoenixMiner.exe without any options, it will search for the file config.txt
in the current directory and will read its command-line options from it. If you want, you can
use file with another name by specifying its name as the only command-line option
when running PhoenixMiner.exe.

You will find an example config.txt file in the PhoenixMiner's directory.

Instead of specifying the pool(s) directly on the command line, you can use another configuration
file for this, named epools.txt. There you can specify one pool per line (you will find an example
epools.txt file in the PhoenixMiner's directory).

The advantages of using config.txt and epools.txt files are:
- If you have multiple rigs, you can copy and paste all settings with these files
- If you control your rigs via remote control, you can change pools and even the miner options by
uploading new epools.txt files to the miner, or by uploading new config.txt file and restarting
the miner.

5. Remote monitoring and management

Phoenix miner is fully compatible with Claymore's dual miner protocol for remote monitoring and
management. This means that you can use any tools that are build to support Claymore's dual miner,
including the "Remote manager" application that is part of Claymore's dual miner package.

We are working on much more powerful and secure remote monitoring and control functionality and
control center application, which will allow better control over your remote or local rigs and some
unique features to increase your mining profits.

6. Hardware control options

Here are some important notes about the hardware control options:
If you specify a single value (e.g. -cvddc 1150), it will be used on all cards. Specify different values for each card like this (separate with comma): -cvddc 1100,1100,1150,1120,1090 If the specified values are less than the number of GPUs, the rest of GPUs will use the default values.
We have tested only on relatively recent AMD GPUs (RX460/470/480/560/570/580 and Vega). Your results may vary with older GPUs.
The blockchain beta drivers from AMD show quite unstable results - often the voltages don't stick at all or revert back to the default after some time. For best results use the newest drivers from AMD: 18.1.1 or 18.2.1, where most of the bugs are fixed.
-tmax specifies the temperature at which the GPU should start to throttle (because the fans can't keep up).
If you use other programs for hardware control, conflicts are possible and quite likely. Use something like GPU-Z to monitor the voltages, etc. MSI Afterburner also seems to behave OK (so you can use it to control the Nvidia cards while AMD cards are controller by PhoenixMiner).
This should be obvious but still: if given clocks/voltages are causing crahses/freezes/incorrect shares when set with third-party program, they will be just as much unstable when set via PhoenixMiner hardware control options.
If you have problems with hardware control options of PhoenixMiner and you were using something else to control clocks, fans, and voltages (MSI Aftrerburner, OverdriveNTool, etc.), which you were happy with, it is probably best to keep using it and ignore the hardware control options of PhoenixMiner (or use only some of them and continue tweaking the rest with your third-party tools).

7. FAQ

Q001: Why another miner?
A: We feel that the competition is good for the end user. In the first releases of PhoenixMiner
we focused on the basic features and on the mining speed but we are now working on making our
miner easier to use and even faster.

Q002: Can I run several instances of PhoenixMiner on the same rig?
A: Yes, but make sure that each GPU is used by a single miner (use the -gpus, -amd, or -nvidia
command-line options to limit the GPUs that given instance of PhoenixMiner actually uses).
Another possible problem is that all instances will use the default CDM remote port 3333,
which will prevent proper remote control for all but the first instance. To fix this problem,
use the -cdmport command-line option to change the CDM remote port form its default value.

Q003: Can I run PhoenixMiner simultaneously on the same rig with other miners?
A: Yes, but see the answer to the previous question for how to avoid problems.

Q004: What is a stale share?
A: The ethash coins usually have very small average block time (15 seconds in most instances).
On the other hand, to achieve high mining speed we must keep the GPUs busy so we can't switch
the current job too often. If our rigs finds a share just after the someone else has found a
solution for the current block, our share is a stale share. Ideally, the stale shares should be
minimal as same pools do not give any reward for stale shares, and even these that do reward
stall shares, give only partial reward for these shares. If the share is submitted too long
after the block has ended, the pool may even fully reject it.

Q005: Why is the percentage of stale shares reported by PhoenixMiner smaller than the one shown
by the pool?
A: PhonixMiner can only detect the stale shares that were discovered after it has received a
new job (i.e. the "very stale") shares. There is additional latency in the pool itself, and in
the network connection, which makes a share stall even if it was technically found before the
end of the block from the miner's point of view. As pools only reports the shares as accepted
or rejected, there is no way for the miner to determine the stale shares from the pool's
point of view.

Q006: What is the meaning of the "actual share difficulty" shown by PhoenixMiner when a share is
found?
A: It allows you to see how close you were to finding an actual block (a rare event these days
for the most miners with reasonable-sized mining rigs). You can find the current difficulty for
given coin on sites like whattomine.com and then check to see if you have exceeded it with your
maximum share difficulty. If you did, you have found a block (which is what the mining is all
about).

Q007: What is the meaning of "effective speed" shown by PhoenixMiner's statistics?
A: This is a measure of the actually found shares, which determines how the pool sees your
miner hashrate. This number should be close to the average hashrate of your rig (usually a 2-4%
lower than it) depending you your current luck in finding shares. This statistic is meaningless
in the first few hours after the miner is started and will level off to the real value with
time.

Q008: Why is the effective hashrate shown by the pool lower than the one shown by PhoenixMiner?
A: There are two reasons for this: stale shares and luck. The stale shares are rewarded at only
about 50-70% by most pools. The luck factor should level itself off over time but it may take
a few days before it does. If your effective hashrate reported by the pool is consistently lower
than the hashrate of your rig by more than 5-7% than you should look at the number of stale shares
and the average share acceptance time - if it is higher than 100 ms, try to find a pool that is
near to you geographically to lower the network latency. You can also restart your rig, or
try another pool.

8. Troubleshooting

P001: I'm using AMD RX470/480/570/580 or similar card and my hashrate dropped significantly in the past
few months for Ethereum and Ethereum classic!
S: This is known problem with some cards. For the newer cards (RX470/480/570/580), this can be
solved by using the special blockchain driver from AMD (or try the latest drivers, they may
incorporate the fix). For the older cards there is no workaround but you still can mine EXP,
Musicoin, UBQ or PIRL with the same speed that you mined ETH before the drop.

P002: My Nvidia GTX9x0 card is showing very low hashrate under Windows 10!
S: While there is a (convoluted) workaround, the best solution is to avoid Windows 10
for these cards - use Windows 7 instead.

P003: I'm using Nvidia GTX970 (or similar) card and my hashrate dropped dramatically for Ethereum or
Ethereum classic!
S: GTX970 has enough VRAM for larger DAGs but its hashate drops when the DAG size starts
to exceed 2 GB or so. Unlike the AMD Polaris-based cards, there is no workaround for this
problem. We recommend using these cards to mine EXP, Musicoin, UBQ or PIRL with the same speed
that you used to ETH before the drop.

P004: I can't see some of my cards (or their fan speed and temperature) when using Windows Remote Desktop (RDP)!
S: This is a known problem with RDP. Use VNC or TeamViewer instead.

P005: On Windows 10, if you click inside the PhoenixMiner console, it freezes!
S: This is a known problem on Windows 10, related to so called "Quick Edit" feature of the command
prompt window. From PhoenixMiner 2.6, the QuickMode is disabled by default, so you shouldn't experience
this problem. If you still, do, read here how to solve it: https://stackoverflow.com/q/33883530

P006: Immediately after starting, PhoenixMiner stops working and the last message is "debugger detected"
S: If you have only Nvidia cards, add the option -nvidia to the PhoenixMiner.exe command line.
If you have only AMD cards, add the option -amd to the command line.

P007: PhoenixMiner shows an error after allocating DAG buffer and shuts down.
S: If you have more than one GPU, make sure that your Windows page file minimal size is set to at
least 16 GB. If this doesn't help, start PhoenixMiner by running the start_miner.bat that is in the
miner's folder. You MUST change the wallet address that is specified in start_miner.bat to make
sure that the miner mines to your address. Also, make sure that all lines, starting with setx are
not commented (i.e. they doesn't start with REM command).

P008: The miner sometimes crashes when the DAG epoch change.
S: During DAG generation, the GPUs are loaded more than during the normal operation. If you have
overclocked or undervolted the GPUs "to the edge", the DAG generation ofter pushes them "over the
edge". Another possible reason for the crash (especially if the whole rig crashes) is the higher
power usage during this process. You can lower the DAG generation speed by specifying the -lidag
command-line option. The possible values are 0 (no slow down), 1, 2, and 3 (max slowdown).
In order to check if your rig would be stable during DAG generation, run it in benchmark mode
by specifying the -bench 170 command line option. Then every time when you press the key 'd'
the miner will advance to the next DAG epoch, and you will be able to see if it is stable during
multiple DAG generations. If it isn't you can try to alter the -lidag and -eres command line options
until the desired stability is achieved.


Download/Link mega> https://mega.nz/#!FKAD1JpS!grJ3eE7M7Tv4nA6TqmujM7Mm0LL55Zed8p9AgWEXXG8

SRBPolaris BIOS EDITOR

BIOS editor for AMD RX 460/470/480, RX 550/560/570/580 video cards

- Pimp my straps - speed up your factory bios with custom straps
- Copy memory straps fast and easy
- Memory timing strap editor - make your own custom straps
- Unlock RX460 additional shaders
- Set default GPU and MEM clocks
- Set GPU voltage
- Lot's of useful stuff


Mega : https://goo.gl/nTJy4D


Latest ver. : V3.5

- Pimp my straps - give wings to your factory bios
- Added power control limit
- Added fan mode selection
- Med-High temp and PWM is now editable
- Added fan sensitivity and acoustic limit
- Bug fixes

Donations accepted!

BTC : 15nK4XRb6PZzXMoxyuEMnDm1oyx92pUqZY
ETH : 0x1ac47bac4f9bc9a91c47841dbe36ae5e0b21135e

AMD ATIFlash is used to flash the graphics card BIOS on AMD Radeon RX Vega, RX 580, RX 480, and older cards. It runs under Windows.

Download>https://goo.gl/pveiq5

Micron
Elpida
Hynix
Samsung

Download
https://mega.nz/#!bWQRCQ4J!XqPQBNpa2_aHfEttoh8MmOYmzaJBxB45qd-ynEJaSxk

atikmdag-patcher 1.5.0


compatibility:
Download> https://goo.gl/A6mrn8

Version 1.5.0 is compatible with Catalyst 11.9-15.9 to Crimson 17.11-19.4 It can be used with future versions if it finds the limits you need.
Getting started:
Run atikmdag-patcher.exe.
If all limits are found, click "Yes" to patch and sign. If a limit is not found or if multiple matches are found, the patcher needs to be updated.
Reboot.
To restore the unpatched driver, run the patcher again and click "Yes" to restore from backup.

Known issues:
Legacy drivers may have issues with HDCP and video acceleration with the patch.
Workarounds for video playback issues with legacy drivers:
Disable hardware acceleration in the Flash Player settings (right-click on any Flash video and click "Settings...").
Use the Codec Tweak Tool to disable DXVA hardware acceleration under "Various Tweaks" (in the "Miscellaneous" section).
AMD/ATI cards have a design limitation unrelated to the patch that causes video acceleration to scramble the screen if the vertical blanking/total is below standard with the video card's memory overclocked or with multiple monitors connected. Skype is known to trigger this problem. Either don't overclock the video card's memory, or use the "LCD standard" vertical blanking/total in CRU.
AMD/ATI cards require the "LCD standard" vertical blanking/total to reduce the memory clock when idle. Horizontal values can still be reduced if necessary.
Recent changes:
1.5.0: Find new HDMI-DVI limit.

Using Polaris Bios Editor, we modify the original BIOS by pressing just one button "one click" software.
Before updating, always save the original BIOS!

Download
https://mega.nz/#!GHgEDJzR!6hudR_IqDG5FdqmSLiRVxkPLgNC9yZtBIKhjtbBKh30

A GUI frontend for Windows. Developed in cooperation with bitcoin pool 50BTC

50Miner advantages
Only username and password to start mining on 50BTC pool.
Miner automatically detects video cards and other OpenCL platforms installed on your computer.
If there is no necessary OpenCL platform, you will get a download link.
Automatic start of mining with the optimal hardware settings.
Ability to work in the advanced mode so you can customize all mining settings.
Widget contains basic information: speed, accepted and rejected shares.

50Miner

Instant payments from 50BTC pool to:
- Bitcoin address
- Mobile phone numbers
- Yandex.Money
- QIWI
- Webmoney (RUB)
- VISA


Supported languages
English
Russian
German

The latest update to the Bminer Equihash Nvidia miner brings a number of useful improvements for users that are mining ZCash (ZEC) or other Equihash-based crypto coins on Nvidia GPUs. The newest version 6.0.0 of the miner brings slight performance improvement in the hashrate, faster startup time and reduced CPU usage, comes with a failover server support, provides reduced reject rate caused by stale shares and a simple GUI launcher for Windows to make it even easier for novice users to set thing up. There are of course a number of other smaller improvements and fixes also available in this update to help you get better results and give you more flexibility.

For those of you that have not yet tried this Equihash miner, do note that it also has a simple web-based status interface that shows useful information like uptime, speed, power consumption and efficiency as well as some graphs for temperature and hashrate variation. So all in all a very nice list of improvements in the latest version of Bminer that makes it an even better alternative to more popular and widely used alternatives such as EWBF’s miner or dstm’s ZCash CUDA Miner. If you have not tried this miner the last time we talked about it when it was still new and getting up to speed, now might be a good time to give it a go.


Bminer is a relatively new miner for Nvidia GPUs for mining cryptocurrencies using the Equihash algorithm such as Zcash (ZEC). It is a closed source miner, available for both Windows and Linux operating systems and comes with a 2% dev fee included (optional, though disabling it apparently removes some optimizations). Bminer comes as an alternative to the popular EWBF miner, the development of which has been stalled for a while already, as well as the more recent dstm ZCash CUDA Miner that looks promising and is actively being developed, but still lacks some features such as failover pool support for example. So any new alternatives such as Bminer that are being actively improved and developed are more than welcome for the users and the crypto community as well.

According to its developers and most users that have tried the Bminer already it is the fastest publicly available Equihash miner for Nvidia GPUs and we can confirm that our initial impressions are showing a better local hashrate compared to the alternatives mentioned. So if you have a Compute Capability 5.0 or newer Nvidia GPU used for mining you might want to give Bminer a go and see if it will work better for you. The miner does come with SSL support as well as Nicehash support, has some interesting extra features, though it is still very easy to use. There is also an API and a web-based interface available for monitoring of your mining rigs that can be quite useful, so go and give it a try and report your results.

6.0.0 (Current)¶
Failover server supports. Supply multiple uris (separated by commas) via the -uri option to enable the failover support.
A launcher GUI for Windows.
Reduce reject rate caused by stale shares.
0.3-0.5% performance improvement depending on card models.
Fix inaccurate metrics at the start of Bminer.
Reduce CPU usage the start of bminer.
Support miner.reconnect().
Experimental support for miningrigrentals.
A new option -no-runtime-info to disable runtime information collection.

There is a new Monero (XMR) CryptoNight miner out for AMD Radeon Rx Vega GPUs called Cast XMR that claims to be capable of reaching hashrates of more than 2050 CryptoNight H/s on an single RX Vega 56 or Vega 64 GPU (with a high power consumption). The miner is designed to support CryptoNight/CryptoNote based currencies such as Monereo (XMR), Bytecoin (BCN), DigitalNote (XDN) and Intense (ITNS) to be used with RX Vega GPUs and. There is a 1.5% dev fee included and currently is is available only for Windows OS (binary), no source code due to the developer fee, though apparently a Linux version is also coming soon.

According to the author of the miner is should be capable of providing you with about 1900 H/s at about 200W or over 2000 H/s at 250W of power usage, so if power and cooling is not an issue you might try to get the most out of your RX Vega GPU with this miner. To get the best performance you will need to use the AMD Blochchain Compute Driver (version is 17.30.1029) as well as to toggle the HBCC Memory Segment. While AMD’s new Radeon RX Vega GPUs are a bit buggy as far as mining goes and cause some headaches they are still doing great in terms of CryptoNight mining performance (when they work) and are also interesting option for Ethash dual mining as well, if you manage to keep them cool. Squeezing the best performance out of the RX Vega GPUs requires a lot of power usage and thus a lot of heat being generated, also getting more than 4 of these cards in a single mining rig is still a problem.

Update to version 0.9.2
Monero (XMR) CryptoNight miner version 0.9.2

Cast XMR reaches hash rates of more then 2050 CryptoNight Hashes/s on an single RX Vega 56 or Vega 64 GPU.



Features

- Full support for CryptoNight/CryptoNote based currencies:
Monero (XMR)
supports Monero V7 network upgrade
Bytecoin (BCN)
DigitalNote (XDN)
Intense (ITNS)
Electroneum (ETN)
LeviarCoin (XLC)
Karbo (KRB)
- Fastest miner for AMD Radeon RX Vega GPU series (more then 2KHash/s)
- Fastest miner for AMD Radeon Vega Frontier Edition GPU (more then 2.1KHash/s)
- Optimized cores for RX Vega Blockchain driver
- RX Vega Blockchain driver detection
- Multiple GPU support for upto 8 Vega GPUs
- Monitor temperature and fan speed of each GPU
- Full pool support
- Nicehash support
- Fast Job Switch option to minimize outdated shares
- Remote http access for statistics in JSON format
- only 1.5% dev fee

Requirements

- Windows 8/8.1/10 64 bit
- AMD Radeon RX Vega 56/64 GPU with at least 8GB RAM
- or AMD Radeon RX Vega Frontier Edition with 16GB RAM
- or AMD Radeon RX 480/RX 580 GPU with a least 4GB RAM
- For about 50% higher hash rates the Radeon Beta for Blockchain Compute Driver Version 17.30.1029 or the standard Radeon Driver 18.3.4 has to be installed

How To
cast_xmr has a command line interface. For a minimal configuration run:

cast_xmr -S [pool server] -u [username or wallet address]

To select which GPU to use the -G switch, e.g. for using the 2nd card use:

cast_xmr -S [pool server] -u [username or wallet address] -G 1

To select multiple GPU to use the -G switch and list comma separated the GPUs which should be used, e.g. for using the 1st and 3rd card use:

cast_xmr -S [pool server] -u [username or wallet address] -G 0,2

In case you have multiple OpenCL implementation installed or mixed GPUs (Nvidia, Intel, AMD), the correct OpenCL implemenation can be selected with the “–opencl” switch:

cast_xmr -S [pool server] -u [username or wallet address] --opencl 1 -G 0

For a complete list of configuration options run:

cast_xmr --help

Read here how to get the best mining performance with a Radeon RX Vega 56/64 GPU

Raven (RVN) is an interesting coin that has been under the radar for many people up until recently when it got hyped and the interest in it has grown seriously in the past days. Initially the coin was only CPU mineable, then a ccMiner version with support for the X16r algorithm used by the coin was introduced for Nvidia miners by tpruvot however that miner has been a bit troublesome for many users due to power spikes and mining systems rebooting, so people had to reduce TDP or downclock and suffer performance loss in order to mine stable. Fortunately there is a new improved miner available now – ccMiner Enemy 1.03 that offers better performance and more stable mining with higher TDP and clocks (still depending on your hardware).

The ccMiner Enemy 1.03 fork for Raven (RVN) mining is available only as a 32-bit Windows binary for the moment and is compiled for CUDA 8, it supports the X16r algorithm used by RVN as well as X17. For better performance the latest 390.xx drivers from Nvidia are recommended, so make sure you are up to date. If you are mining Raven (RVN) or had plans to do so, but were set back by the problems from the initial miner you should definitely try the new release as it should handle much better. AMD miners are still unable to mine Raven as there is no compatible X16r miner available yet, though there is a substantial bounty for anyone willing to make one.

To download and try the new ccMiner Enemy 1.03 fork for Raven (RVN) mining on Nvidia GPUs

Claymore is extending his coverage on the different mining algorithms with a new NeoScrypt AMD GPU miner that ahs been available for a few days already and we’ve played a bit with it to see what it can deliver. Do note that even Claymore warns that the NeoScrypt algorithm is VERY HOT, so yo uneed to make sure you have powerful PSU and good GPU cooling. Also to get the best hashrate you need to set your GPUs to use “-powlim 50” option in the miner (+50% Power Limiter), though you cans till play with the voltages of the GPUs lowering them to reduce the power usage. o note that like other miners from Claymore this one comes with a dev fee included, the Claymore NeoScrypt AMD GPU miner has a developer fee of 2%, so every hour the miner mines for 72 seconds for developer.

AMD’s RX 4xx/5xx series of GPUs do manage to provde a hashrate of up to about 900 KHS, but the old 280X GPUs are also quite interesting with about 800 KHS as well as 290X/390X at 1100 KHS. Owners of AMD Radeon RX VEGA 56/64 could be the ones with the most benefit as the miner is capable of delivering up to about 2200 KHS and that is a lot. Of course in order to maximize the performance in terms of hashrate you need to unlock the GPU power limiter and increase the clocks and see how low the GPU voltage can go stable. With settings optimized for CryptoNight a VEGA 64 can do just about 1400 KHS (that is with low GPU frequency, high memory and -20% power limit), at stock settings you can get about 1700 KHS from a VEGA 64 and for 2200 KHS you need +50% power limit. So again make sure you can cool down the GPUs properly and that your power supply is powerful enough to handle the extra load. Profitability wise fClaymore's NeoScrypt AMD GPU Miner.


Latest version is v1.2:

- improved stratum routines to support more pools.
- added RX550 card support.


WARNING: NeoScrypt algorithm is VERY HOT, make sure you have powerful PSU and good GPU cooling, use "-powlim 50" option to get full hashrate.or VEGA GPUs mining NeoScrypt at 2200 KHS per card can be better than optimized settings for CryptoNight for about 2000 H/s.

This is POOL version. Use any recent drivers. Miner requires up to 1.1GB of GPU memory.
For multi-GPU systems, set Virtual Memory size in Windows at least 16 GB (better more):
"Computer Properties / Advanced System Settings / Performance / Advanced / Virtual Memory".

This miner is free-to-use, however, current developer fee is 2%, every hour the miner mines for 72 seconds for developer.
If you don't agree with the dev fee - don't use this miner, or use "-nofee" option.
Attempts to cheat and remove dev fee will cause a bit slower mining speed (same as "-nofee 1") though miner will show same hashrate.
Miner cannot just stop if cheat is detected because creators of cheats would know that the cheat does not work and they would find new tricks. If miner does not show any errors or slowdowns, they are happy.

This miner is heavily optimized and therefore supports only most popular AMD GPU chips: Pitcairn, Tahiti, Hawaii, Tonga, Fiji, Ellesmere, Baffin, Vega.

Only Windows x64 is supported currently. No Linux support. No 32-bit support. No NVidia support.

Claymore's NeoScrypt AMD GPU Miner latest version v1.2

Claymore's ZCash/BTG AMD GPU Miner.


Latest version v12.6:

- added Vega cards support (ASM mode).
- added ASM mode for RX460/560 cards (+20% speed).
- new GPU sorting method for AMD cards. Now GPUs are sorted by physical bus index (it matches AfterBurner list of GPUs). Also the list of temperatures/fans matches the list of GPUs automatically.
Therefore "-di detect" and "-gmap" options are not necessary and not supported anymore.
WARNING: be careful if you use use separate overclock/temperature settings for every card, due to new sorting method GPUs can get different indexes!
- added fan/OC support for 17.7.2 (and higher) drivers.
- improved support for systems with more than 10 GPUs, check readme for "-di" option description for details.
- added pool selection in runtime ("e" key).
- a few minor improvements.


NOTES:
1. Reduce intensity ("-i" option) if miner is unstable or if you see bad speed.
2. It seems there is no way to get full speed on latest drivers for Fiji cards, at least in Windows. So don't use latest drivers for Fury, use 15.12 or 16.3.2, or use "-asm 0" for them if you use newer drivers.


Claymore's ZCash/BTG AMD GPU Miner latest version v12.6



This version is for pools.

Catalyst (Crimson) 15.12 is required for best performance and compatibility.
15.12 does not support some Fiji cards, use 16.3.2 for them.
For 4xx cards (Polaris) Crimson 16.12.2 is recommended.
NOTE: For best performance on Fiji cards you must use 15.12 or 16.3.2 drivers. For newest drivers speed will be slower!
You can get bad results for non-recommended drivers, or miner can fail on startup.
Set the following environment variables, especially if you have 1-2GB cards:

GPU_FORCE_64BIT_PTR 1
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100

For multi-GPU systems, set Virtual Memory size in Windows at least 16 GB:
"Computer Properties / Advanced System Settings / Performance / Advanced / Virtual Memory".

This miner is free-to-use, however, current developer fee is 2% if you use secure SSL/TLS connection to mining pool, every hour the miner mines for 72 seconds for developer.
If you use unsecure connection to mining pool, current developer fee is 2.5%, every hour the miner mines for 90 seconds for developer.
If you don't agree with the dev fee - don't use this miner, or use "-nofee" option.
Attempts to cheat and remove dev fee will cause a bit slower mining speed (same as "-nofee 1") though miner will show same hashrate.
Miner cannot just stop if cheat is detected because creators of cheats would know that the cheat does not work and they would find new tricks. If miner does not show any errors or slowdowns, they are happy.

This version is for recent AMD videocards only: 7xxx, 2xx, 3xx and 4xx, 1GB or more.

There are builds for Windows x64 and Linux x64. No 32-bit support. No NVidia support.

TROUBLESHOOTING

1. Install Catalyst v15.12.
2. Disable overclocking.
3. Reduce intensity ("-i" option).
4. Set environment variables as described above.
5. Set Virtual Memory 16 GB or more.
6. Try "-old 1" option.
7. Reboot computer.
8. Check hardware, risers.

New version v0.6.1-RC2 Released; Added free cloud service and many useful updates.

Changes:
Cloud service feature; You can create free account from https://cloud.eminer.net and get useful statistics and alerts for your all rigs.
Intensity improved
Linux hashrate improved
NVIDIA support improved
DAG intensity added
Devfee coins selectable now
Better stabilisation
Reported bugs fixed

Cloud service
Test the service features via https://cloud.eminer.net with cloud key "8a5a89685dd881a87b71ecc1584f5e8ecfaa63a8"

Optimized, high performance multiworker ethash miner written in Go language. That has been nice performanse compare with other miners. It's release candidate version, need more tests and comments so we can improve the miner.

Features:

Support Windows, Linux and MacOS
Fully support AMD and NVIDIA OpenCL devices
Free cloud monitoring and statistics service via https://cloud.eminer.net
Improved and optimized three OpenCL kernels
Asynchronous multiworker mode (windows only)
Support for Stratum and RPC clients with failover
Useful web dashboard
Historical metrics for last 24 hours, shares, hashrate and other informations
JSON API for stats and metrics
Support for AMD and NVIDIA hardware management (Temperature, fan speed, clock and other useful hw informations)
Support for nicehash stratum

And much more.

Multiworker Mode (windows only); search shares with multiple instances, this can be increase 1% ~ 2% share luck.

Download:
Eminer ETHASH miner v0.6.1-RC2

New version


List Devices:
$ eminer -L

Benchmark mode:
$ eminer -B deviceid

Stratum mode:
$ eminer -S server:port -U yourwallet -P password
(for nicehash or other stratum servers use -S stratum+tcp://server:port)

We just gave a try of the latest NiceHash Excavator 1.2.10 alpha miner (source) that includes new algorithms and some performance improvements. It has been a while since we have played with last, so there are some changes that we wanted to try out. Excavator supports both AMD and Nvidia GPUs and works with some of the more popular mining algorithms, though performance wise it may not be the fastest on all of them.

Nvidia CUDA supported algorithms: equihash, pascal, decred, sia, lbry, blake2s, daggerhashimoto
AMD OpenCL supported algorithms: daggerhashimoto, equihash, pascal, sia, decred

More notable is the performance improvement from the latest ethminer for Nvidia GTX 1060 and GTX 1070 GPUs that has also apparently been implemented in Excavator, so you might want to try that as well and see what results you are going to get if you are mining coins using the (Ethash) Dagger-Hashimoto algorithm such as Ethereum and others. Below you can find a 64-bit Windows binary that you can download and try will all of the supported algorithms, just modify the sample config files provided. Do note that Nvidia supports two more algorithms that have not yet been implemented on AMD GPUs!

Latest NiceHash Excavator 1.2.10 alpha miner

If you have GPU mining rigs using more recent Nvidia GPUs and are interested in mining NeoScrypt based crypto coins, then you might want to check out the new hsrminer for Neoscrypt. This is a new closed source miner being developed by palgin & alexkap that is currently available as a Windows-only binary with 1% developer fee built-in. Currently the hsminer software is under development with a version available for Neoscrypt as well as for HSR mining support with other crypto algorithms coming later on as well. The currently available hsrminer version for Neoscrypt does offer a good improvement in terms of performance as compared to the previously available fastest ccMiner releases, so definitely worth checking it out.

Before trying this miner software just make sure that your Nvidia GPU is with Compute Capability 5.0 supported as minimum (though currently only Pascal GPUs seem to work) as well that are using a driver version 388.3x or later. Also it is advised to make sure that the amount of virtual memory you have set under Windows is pretty high as the miner does require a lot of memory, especially for more powerful GPUs. If using Windows 10 you might want to be sure that you have all the latest updates installed including the Creators Update as otherwise you might have issues with the miner.

This is a new miner with a closed ref. code, which is developed by palgin & alexkap, currently has 1% commission to the developer.

You need:
Cards with CC 5.0+ only.
Nvidia driver 388.3x+ only.
Только windows

(HSR):
1060 3Gb - 8.3+ Mh/s
1080 - 16.2+ Mh/s

(Neoscrypt):
1060 3Gb - 740+ kh/s (non-OC)
1080 - 1280-1300 kh/s (non-OC)
1080Ti - 1850+ kh/s (user report)


It is necessary to increase virtual memory (for example 6x1080, on each core 6260 MB of memory is allocated, therefore the sum should be more than 6260 * 6 = 37560).

While only for windows, for linux in the future will appear.

The batch file must be created manually, example
hsrminer -o URL -u USERNAME -p PASSWORD

Neoscrypt Nvidia GPU Miner v.2.0.1

We have received some requests for the fastest public fork of ccMiner for the Keccak algorithm and it seems that the version from alexis78 (source) is giving one of the best performances out there from the popular open source forks. There seems to be even more optimized version available as a private miner being sold, though we have not tested that one and cannot comment on the performance it offers. Alternatively the ccMiner fork from KlausT (source) also does seem to offer very similar performance as far as Keccak mining goes.

We have prepared a 64-bit Windows binary compiled from the alexis78’s source using CUDA 8.0 and compiled with VC 2013 that you can download and try if you want to mine Keccak on NiceHash or directly mine a specific crypto coin using this mining algorithm for its Proof of Work (PoW). The default intensity might be a bit high for some cards, so you might want to dial it down a bit if the miner is unstable on your mining rigs. If you are interested how much a GTX 1080 Ti does using this miner for Keccak, well it can do 1200-1300 MH/s with optimized settings for lower power usage. If you are wondering which altcoin is driving the demand and profitability for Keccak lately it is apparently SmartCash (SMART), prior to that there was also a short peak for MaxCoin (MAX) as well a couple of weeks ago.

lolMiner-mnx is a new miner for Mining MinexCoin (MNX) or any other coin that uses the Equihash 96/5 algorithm. Do note that the this is not the same algorithm used by ZCash (ZEC), there it is Equihash 200/9, so this miner is not compatible for mining traditional Equihash coins. The lolMiner-mnx is a closed source OpenCL miner being developed from scratch, so it is not based on existing opensource code. Currently it is available as 64-bit binary releases for both Linux and Windows, although it uses OpenCL it should compatible with pretty much any GPU including Intel and Nvidia and not only AMD.

The miner still needs some work, especially on Nvidia GPUs where by default it is pretty heavy on the CPU load and memory usage as well. It is recommended that Nvidia users add the parameter --enable-nv-hotfix in order to reduce the CPU load a bit, but still running the miner on the main GPU may make the system a bit unresponsive even with that parameter. Still if you are interested in mining MNX (even with the high hashrate and low block reward at the moment) or any other Equihash 96/5 coin you might want to check the lolMiner-mnx out.

Linux users can also use the Optiminer/Equihash miner as a solution for mining different variations of the Equihash algorithm (Equihash 200/9, Equihash 192/7, Equihash 96/5). A Windows version is supposed to come out at some point, but it is still not available for the moment.


lolMiner-mnx

Hi folks,
this is the thread for announcing lolMiner-mnx for mining MinexCoin (MNX) based on the Equihash 96/5 algorithm (please do not confuse this with Zcash / BitcoinGolds Equihash 200/9).

The current version of the miner is 0.33 beta (March 23, 2018)

Download Links:
lolMiner-mnx


What is new (0.32) / (0.33) ?
- 0.33 fixes an other bug in stratum code of 0.32.

- On startup the miner will now wait until the stratum connection is fully established. This fixes one segmentation fault bug we observed the last days when some pools were under ddos attacks.

- When using the failover support the miner will now slowly reset the number of attempts to connect to one pool. For example when it required 3 attempts to connect to a certain pool after 15 minutes of successful connection the miner will decrease the internal counter by one. So after 45 minutes the counters are in a state similar to the situation when it connected fine at the first attempt. This prevents the miner to swap over to the failover pool when not required.

- New parameter: --set-reconnection-timer . If this parameter is set and the miner is connected to a fail-over pool, it will do a single retry to connect to the primary pool after minutes. The minimum possible is 5 minutes, the default is 30 minutes. If is set to 0 the reconnection feature will be disabled and the miner will continue to mine of the fail-over pool.

FAQ:
What coins can I mine with the miner?
lolMiner-mnx is a software for stratum pool mining with the Equihash 96/5 algorithm (MARS). At the moment the only coin featuring this algorithm is MinexCoin (Symbol: MNX).

How to use the miner and what parameters it features?
The miner comes with a detailed description of all parameters in PDF form "lolMiner_readme.pdf". Since it is 4 pages long (0.32) I won't cite it all here.

Is this miner for CPU / GPU, and for which vendors?
It can be run on any device that can execute OpenCL 1.1 code. So CPU (Intel / AMD) as well as GPU (Intel / Nvidia / AMD). We have to admit that our testing systems are mainly Intel CPU with Nvidia graphics machines, so this is the best tested situation.

Is there any fee on the miner?
Yes, on version 0.3 the dev fee of the miner was lowered to 1.5% that its mining in background. The hash-rate displayed by the miner is netto hash, so you see what you get. The promise is to lower the fee once MNX increases much in price. Also if in any future time the support and development of the miner stops I promise to do a fee-free build and maybe also release the sources.

What are the system requirements for lolMiner-mnx?
You will need an 64 bit system running any Linux distribution or Windows 7 / 8 / 10.
Moreover the miner requires that an OpenCL driver for the devices you want to mine one is installed on your system.
Note that lolMiner utilizes the hardware very well and stresses it a lot.

What hash-rate can I expect from device x?
This massively depends on OS, driver, the hardware itself. Here are some numbers from our testing systems that we collected when testing the miner. If you run it successfully please report in this thread so we can extend the list.

New Claymore Dual Ethereum + DecredSiacoinLbryPascalBlake2sKeccak AMD+NVIDIA GPU Miner

Claymore has updated his dual Ethereum plus DCR, SC, LBRY, PASC, Blake2s and Keccak AMD and Nvidia GPU miner to version 11.6 bringing some performance improvements for slower Nvidia GPUS as well as increasing the usability of older GPUs with less VRAM along with new features and bug fixes. You can read what is the full list of changes in the latest version 11.6 below:

– improved hashrate for weak Nvidia cards by about 1%.
– zero devfee for 3GB cards in Windows 10, same as for all 2GB cards.
– applied some tricks to increase available memory for 3GB cards in Windows 10 so you can mine ETH a bit longer.
– now you can press “y” key to turn on “Compute Mode” in AMD drivers for all cards (Windows only).
– Linux version: removed openssl library dependency.
– improved “-logfile” option, now you can use it to specify a folder for log files, use slash at the end to do it, for example, “-logfile logs\”.
– added “-epoolsfile” and “-dpoolsfile” options.
– remote management: now “miner_getstat2” command also returns PCI bus index for every GPU.
– a few minor bug fixes and improvements.

New Claymore Dual Ethereum + DecredSiacoinLbryPascalBlake2sKeccak AMD+NVIDIA GPU Miner

improved hashrate for weak Nvidia cards by about 1%.
zero devfee for 3GB cards in Windows 10, same as for all 2GB cards.
applied some tricks to increase available memory for 3GB cards in Windows 10 so you can mine ETH a bit longer.
now you can press “y” key to turn on “Compute Mode” in AMD drivers for all cards (Windows only).
Linux version: removed openssl library dependency.
improved “-logfile” option, now you can use it to specify a folder for log files, use slash at the end to do it, for example, “-logfile logs\”.
added “-epoolsfile” and “-dpoolsfile” options.
remote management: now “miner_getstat2” command also returns PCI bus index for every GPU.
a few minor bug fixes and improvements.


There’s an important update for those of us who is dual mining Ethereum and other coins on 2-3 GB cards.

Today, Claymore has released an update for his dual Ethereum plus DCR, SC, LBRY, PASC, Blake2s and Keccak GPU miner (both for AMD and Nvidia).

The new version 11.6 brings some new important features as well as bug fixes. Eventually, the focus is on weaker cards. Weaker Nvidia cards now enjoy about 1% hashrate improvement; moreover, 2GB and 3GB cards now have zero devfee when running under Windows 10.

In addition to that, 3GB cards now also have their ETH mining lifespan slightly increased – Claymore states that he has improved memory handling so those cards can work with a larger DAG file than they used to.

There are also some interface improvements (new commands) as well as some optimizations for the Linux version of the miner.

MSI-GTX-1060-3GB





Sapphire-Nitro-RX-580-8GB

The latest version of the XMR-stak miner (source) now comes in an all-in-one solution that can work on both CPU as well as GPU, together or separately and supports both AMD and Nvidia GPUs. XMR-stak supports tthe Cryptonight for Monero (XMR) and Cryptonight-light for AEON as algorithms and offers some of the best hashrates in terms of performance competing with Cast-XMR for the best AMD hashrate, especially on AMD RX VEGA GPUs. Do note that by default the developer fee for this miner is set to 2%, though the you can change that in the source code and recompile with different percentage should you wish to do so. There are binaries available for Linux and Windows ready for download and of course you will need to run the miner and configure depending on your mining hardware for best performance (there is autoconfig, but not the best performance).

Changelog to 2.4.1:
CUDA backend
fix sumokoin for CUDA #1300
fix sm_20
fix wrong results if bfactor is used
fix wrong CUDA architecture detection #1299

Config files from 2.3.0+ are compatible. Older config files are NOT compatible.

latest version of the XMR-stak miner

Version 2.0.2.0 - Alpha
Released 29 March, 2018
Download NiceHash Miner 2.0.2.0 - Alpha
Changes
Updated excavator to v1.5.1a
Dropped support for CUDA 8 excavator
Added algorithm CryptoNightV7 for NVIDIA cards
Updated CPU miner
Added algorithm CryptoNightV7 for CPU
Various bug fixes and improvements

Version 2.0.2.0 - Alpha

Version 2.0.2.1 - Beta (Recommended)
Released 05 April, 2018
Download NiceHash Miner 2.0.2.1 - Beta
Changes
Various bug fixes and improvements


Version 2.0.2.1 - Beta (Recommended)