lolMiner v0.9.3 (AMD Nvidia GPUs miner) – Download and Configure for Windows

lolMiner 0.9.2 - Значительное улучшение производительности GRIN

GitHub: DOWNLOAD lolMiner v0.9.3

lolMiner v0.9.3 — this is the Equihash / Cuckatoo miner with a focus on AMD GPUs (based on OpenCL). Please note that the program will work on most Nvidia cards, but speed and stability may vary.

Supports Algorithms:

  • Equihash-96-5
  • Equihash-144-5
  • Equihash-150-5
  • Equihash-192-7
  • Equihash-210-9
  • ZelHash

Full list of available versions:

Changes v0.9.3:

  • Extended GRIN-AT31 compatibility with older drivers (18.x +)
  • Improved GRIN-AT31 performance on ROCm (RX 470/480/570/580 / Vega / VII)
  • Early termination introduced for GRIN-AT31 + (improves hash on the pool side, see further release notes)
  • Deeply redesigned kernel scheduler
  • GRIN-AT31 kernel bugs fixed (improved stability and accuracy)
  • Bug fixed: Vega FE loaded 8G instead of 16G GRIN-AT31 solver in Windows
  • Bug fixed: Watchdog did not call the necessary file in Windows
  • Added option –disablewatchdog 1 to disable detection of 0 sol / s / 0 g / s

Release Note

About Early Job Cancellation for GRIN

The GRIN proof of work is a compute intense and rather slow algorithm. Especially C31 often needs (at 1 g/s) about one second for each graph processed. In case a new job (for a new chain height) arrives, the current calculation effort is worthless, because the block that was mined on already got found.
lolMiner 0.9.3 now introduces an early cancellation for long lasting works: if a new work arrives that invalidates the current run calculations, they get canceled to start quicker on the fresh work. To demonstrate the effect see the example describing the 0.9.2 and 0.9.3 difference:
Assume you have a card running 1 g/s on GRIN-AT31. Then in 2 minutes (120 seconds) it will be able to process 120 graphs. On average – Grin has a 1 minute block time – two of these graphs are already obsolete when they got finished.
lolMiner 0.9.2 will display the 1 g/s, because of 120 processed graphs per 120 seconds. But two of the graphs are then filtered out in the stratum module, thus the pool can see at most 118 / 120 = 0.983 g/s (minus about 1 graph fee).
lolMiner 0.9.3 will cancel the running work before it gets completed. On average you will be able to process one more graph then 0.9.2 assuming both are canceled about half way through. Thus lolMiner 0.9.3 starts 121 graphs and completes 119 of them. The displayed hash rate is now 119 graphs /120 seconds = 0.991 g/s. This equals what the pool could see (minus one for fee), because the 119 completed are the ones that got not canceled early.
Conclusion: lolMiner 0.9.3 DISPLAYED hash rate may be a little lower then 0.9.2, but what arrives at pool is better. The slower the cards are, the more drastic is this effect, e.g. a 580 8G running at 0.65 g/s will benefit almost 2% on pool side, a VII with 1.75 g/s only half a percent.
Combined with the mostly on GPU cycle finder lolMiner achieves a stale share rate of less then 0.7% and thus gives you best displayed to pool hash rate ratio available for Grin Cuckatoo-31.

Configure lolMiner

For the quickest start, it will be enough:

  1. Download archive with the program
  2. Unzip to any convenient place
  3. Change wallet to your own in a file with the extension .bat
program files

Attention! The archive contains two versions of the program. The first is for the Beam coin, the second is for everyone else!

The archive with the program contains ready-made examples for Beam and other coins, a configuration file, as well as instructions in Russian.

Quick Launch Examples

The easiest way to start using lolMiner is to configure the program from the command line. Just open a terminal (Linux) or create / edit a finished .bat file (Windows)

lolMiner.exe --coin (название монеты) --pool (адрес пула) --port (порт пула) --user (кошелек или логин пула) --pass (пароль пула)

How to configure .bat file lolMiner

batch file setting
  1. lolMiner.exe – indicate the name of the program that will be launched
  2. –coin BEAM – the –coin parameter determines which coin to mine. lolMiner will select the internal settings as the desired algorithm.
  3. –pool – after the –pool key, specify the pool address.
  4. –port 3333 – specify the port of the pool. You need to find it on the page with the pool, or use the example of ready-made settings at the end of the article
  5. –user 2d1f865b393afa3ea…d0b21cfe5328b608ca5 – after the –user key, specify the wallet address or login on the pool. The wallet can be opened at any safe and convenient exchange, or put an official wallet from a coin.
  6. .rig0 – put a point and specify the farm identifier. It is only needed to track statistics on the pool.

We examined the simplest configuration to run the program.

Let’s see what we ended up with in a batch file:

Example for Beam coin:

lolMiner.exe --coin BEAM --pool --port 2222 --user 2d1f865b393afa3ead1e0dd0c0307c0cbcdb8412671c86fbd0b21cfe5328b608ca5.rig1

You can start mining by double-clicking on the .bat file with the desired coin. We start on a farm with Windows and AMD cards and see what the program console writes to us:

miner console
  1. Equihash 150/5 algorithm – the algorithm that we selected when setting up the batch file
  2. Warning: No user profile defined in command line (–profile (profileName> missing) – the program warns that we did not specify a profile through the configuration. But we configured through the .bat file, so the profile settings (config file) can be ignored
  3. Reading pool data from command line – the program prepares information about connecting to the pool, which we specified in the batch file
  4. lolMiner is configured to mine Beam(BEAM), Equihash 150/5 – BeamHash -the miner realized that we want to mine a Beam coin!
  5. Radeon RX 580 Series – Cards for mining cryptocurrency are determined. In our case, it is RX 580
  6. Memory: 8192 MByte (8138 MByte free) – 8138 MB of video memory available
  7. Active: true (Selected kernel: Equihash 150/5 (Beam), 4G memory) – the program chose the core for mining

We wait some time until all devices are detected and see the following:

pool connection
  1. Connecting to pool… – connect to the pool
  2. Connected to – successfully connected
  3. New job received: 1 Difficulty 100 – pool sent a job for video cards
  4. GPU 4: Submitting shareю Share accepted (35 ms) – the first ball is accepted (share of work). It must be understood that the miner receives the reward precisely for the sent balls.

After waiting a bit, the console will show us the hashrate and temperatures of all the GPUs.

Other versions of the miner:



  • Significant improvement in GRIN-AT31 performance on 8 / 16G cards (+ 5% on Polaris & Vega, +10 on Navi)
  • Experimental support for GRIN-AT31 and Polaris, Vega and VII using AMD ROCm drivers
  • Range checks added to GRIN-AT31 code (stability improved)
  • A function has been added to call external watchdog scripts in the event of a GPU failure during mining (see Release Notes)


  • Added GRIN-AT31 optimization for AMD 16G cards (Best performance on Radeon Vega FE, Radeon VII and Sapphire RX 570 16G)
  • Updated GRIN-AT31 optimization for 4G AMD cards (Best performance on Fiji based GPUs, Polaris 10 4G)
  • Fixed bug regarding too small hash on GRIN-AT31
  • Added experimental support for GRIN-AT31 for AMD Navi (8G), AMD Fiji (4G) and AMD Hawaii (4G / 8G) GPUs


  • Significant performance improvement for GRIN-AT31 on 8G AMD cards (+ 22% on Polaris to 30% on Radeon VII)
  • 16G solver disabled for GRIN-AT31 (8G is now faster)
  • Grin rejected balls reduced
  • At the command line, lolMiner now accepts the address--pool:address:port
  • Fixed API crash when accessing Chrome-based browsers
  • Fixed bug in stratum EXCC, due to which the number of sent ball was not transmitted to the API


  • The BEAM-I (Beam Hash I) algorithm has been removed since the fork has passed; BEAM-II and BEAM now both indicate a new consensus.
  • Improved driver detection and kernel selection mechanisms
  • On Nvidia: Beam Hash II performance needs to be improved (as it now uses the correct kernels)
  • Beta: Equihash 96/5 (–coin MNX) should now allow changing the personalization string (–overwritepersonal = newPers)


  • Added support for Beam Hash II on older AMD cards (R 9 200/300 4 and 8 GB; R 9 280 (X), HD 79×0 with 3 GB). Please note that the auto switch only works with at least 4GB, for 3GB cards use –coin BEAM-II manually after the fork.
  • Fixed missing Genesis Network (GENX) in lolMiner 0.8.x


  • Added support for BEAM hard fork on block 321321 (approximately July 15)
  • fixed bug with BEAM server side


Added support for the Grin Cuckarood-29 algorithm (–coin GRIN-AD29) for 4GB and 8GB AMD cards. The fork will happen on July 17th. 0.8.4

  • Fixed problem with 0 sol / s for Zelcash
  • Reduced memory usage for Zelcash to 2.9 GB
  • Fixed a bug with the stratum to Equihash 125/4, 144/5, 192/7 and 96/5 in case the pool sends a very poor job ID.


  • Added 16 GB solver for the Cuckatoo-31 (GRIN) algorithm.
  • Improved performance and reduced power consumption for Radeon VII, Radeon Pro Duo Polaris, Vega Frontier and RX 570 16 GB
  • Added support algorithm ZelHash (EquihashR 125/4/0) for hard-fork (2 July)


A new algorithm is available with the –coin ZEL command and replaces the old one. New parameters can already be used in the test network In version 0.7 5 alpha

  • Fixed a bug with many drivers, due to which the miner worked more slowly than alpha 2 (especially on Windows)
  • Nicehash support added
  • A switch has been added to enable / disable TLS (–tls 0 in cmd or “TLS”: 0 in the configuration file to disable it for BEAM). The default value will depend on the coins and enabled for BEAM.
  • A slight change to the mining core.
  • Added command –help.
  • Fixed internal bugs

0.7 alpha 4

  • Fixed bug of segmentation / crash when starting the miner and detecting GPUs
  • Reduced memory consumption by the 3G core to 2700 MB (*)
  • Reduced memory consumption by the 3G core to 2700 MB (*)
  • Fixed a bug where –shortaccept 1 now worked correctly with stratum Beam
  • Fixed a bug where –shortaccept 1 now worked correctly with stratum Beam

Recommended Related Articles:

Leave a Reply

Your email address will not be published. Required fields are marked *