Skip to content

LOKI Wallet – Windows Installation

How-To guide for installing the LOKI Desktop Wallet

This is a guide to installing the Windows version of the Loki Desktop Wallet.  Save your Wallet Seed and Password in a secure place.  Do NOT keep them on the same computer as your wallet.

Download the Loki-Gui-Win64 wallet from

https://github.com/loki-project/

Unzip/Extract the zipped folder loki-gui-win64 to your Desktop

Navigate to the Desktop of your computer

Open the new loki-gui-win64 folder

Double click on the start-low-graphics-mode.bat file

Loki will start

Select your Language

Click Create a New Wallet

Copy down your wallet seed.  DO NOT LOSE THIS

Click the next Arrow

Create a strong Password.  DO NOT LOSE THIS

Click the next Arrow

Click the next Arrow again

Click Use LOKI

Your wallet is now installed

To find out your wallet address, click Receive.  Once you have that, you can use that in your miners to receive payments

 

 

Installing Teamviewer on Ubuntu Server

How-To guide for installing and running Teamviewer on your Ubuntu Mining Rig

This is the quick and dirty to get it up and running.  I find that running Teamviewer on my Ubuntu Mining Rigs helps me manage them on the fly.  For this guide you will replace the home directory named tacticalware with the name of your home directory.  The rest of the commands will work as they are listed.

From a command prompt run the following commands:

sudo bash

mkdir /home/tacticalware/teamviewer

cd /home/tacticalware/teamviewer

wget https://download.teamviewer.com/download/linux/teamviewer-host_amd64.deb

dpkg -i teamviewer-host_amd64.deb

The installation will fail

Now run:

apt-get -f install

y

After it installs then run

teamviewer setup

Enter your username

Enter your password

Log into your email, and find the Teamviewer email

Allow/Add the device

And now you can log into your server using Teamviewer

 

Installing XMR-STAK on Ubuntu with NVidia 1080TI

How-To guide for installing XMR-STAK on Ubuntu 16.04.04 for Mining LOKI

I prefer linux (more specifically Ubuntu) for mining, and have preferred linux since I began mining in 2012/2013.  I was finally fed up with Windows 10 mining of Loki after the most recent set of Windows updates broke several of my rigs.  So I used a small ubuntu rig that I used for testing, and was able to install the XMR-STAK app onto it.  As happy as ever to be able to mine Loki now with Ubuntu, I thought I should put together this quick guide and hope that it may be beneficial to others.  Some of the steps are from github, some are from other sites, some I had found myself.  This is a central place to get you up and running without having to look too far.

For this guide I am assuming you already have a mining rig built with the following:

Ubuntu 16.04.04

NVidia 1080TI Cards

Loki Wallet already downloaded, installed, and the wallet address ready

I am going to run the commands logged in as sudo to make this quick and easy

Now, onto the guide:

sudo bash

apt-get install libmicrohttpd-dev libssl-dev cmake build-essential libhwloc-dev screen

mkdir /miner && mkdir /miner/drivers

git clone https://github.com/fireice-uk/xmr-stak.git

mkdir xmr-stak/build

cd xmr-stak/build

cmake ..

make install

cd /miner/drivers/xmr-stak/build/bin/

./xmr-stak

You will need to insert a port for monitoring the progress.  I use port 30131 and press Enter

Next type in cryptonight_heavy and press Enter

For the pool address, I use loki.ingest.cryptoknight.cc:7733  press Enter

Your username will be your wallet address, for example

LChtjHqr29p5FojLdMtcUW5ApLWyQHH5j4366V78YECEjUkgK99Y7uLDVLpHjXpYM3UcZ39FFL5Gvd4debF95mcJHbnx5ke

The password will be your worker name.  For example mine is Miner23

Your Rig Identifier can be empty, so just press Enter

Input N for TLS and press Enter

Insert N for Nicehash and press Enter

Input N for multiple pools and press Enter

Select Yes when prompted

Mining will begin!

Once you see it mining properly, hit CTRL + C to cancel the mining.  You will want to run it in screen, so you can disconnect from the terminal and the miner will continue to run. To do that run:

screen ./xmr-stak

It will run and you can now disconnect from your putty session or whatever way you are logged in.  If you want to reconnect to your terminal at any time, run the following and you can see your miner running

screen -r

That’s it!  Thanks for reading!

The hardware that I used in this guide:
Gigabyte AORUS GeForce GTX 1080 Ti (QTY 6):
https://amzn.to/2JqvXC8

Motherboard (QTY 1): 
https://amzn.to/2JqGJZ7

CPU (QTY 1): 
https://amzn.to/3qevp2X

Memory (QTY 1): 
https://amzn.to/2JqHn8Z

Hard Drive (QTY 1):  
https://amzn.to/3lic3X5

Risers (QTY 6):  
https://amzn.to/33rIgVE

Power Supplies (QTY 2):
https://amzn.to/3fTRpLR

Add2PSU (QTY 1):
https://amzn.to/39s4URY

Power Switch (QTY 1):  
https://amzn.to/3ljmNVk

Mining with the Z270X Ultra-Gaming Motherboard

How-To Enable all 6 GPUs with the Z270X Ultra-Gaming Motherboard

I use a fair amount of the Gigabyte Z270X motherboards in my rigs, and have run into an issue where only 5 of the 6 GPUs will be seen by Microsoft Windows 10.  To get the 6th one to display there are a few steps, that I can list below.  The good news is your system will see the GPUs…Windows just doesnt know how to allow the OS to access them all.

First thing….install the latest BIOS for the motherboard.  You can get this from the Gigabyte manufacturer site.

Next, configure the bios by performing the following:

Reboot

Press DEL

Enter Setup

On the M.I.T Tab, navigate to Miscellaneous Settings and select it.

Then select Max Link Speed

Scroll down to Gen 2 and select that option

Next you want to Navigate to the BIOS tab

Scroll down to Windows 8/10 Features and select that option

Make sure Windows 8/10 is selected, not Other OS

Scroll down to CSM Support and select that option

Set it to Disabled

You can now Save and Exit your Bios, reboot your rig, and all of your video cards will be functional.  If you find that you cannot boot your Windows installation, it may be that you need to install the OS using UEFI support.  If that is the case and you do not want rebuild at this time, simply undo the changes above and you are back to where you began.

Hardware I used in this build:
Motherboard (QTY 1):
https://amzn.to/2JqGJZ7

CPU (QTY 1):
https://amzn.to/3qevp2X

Memory (QTY 1):
https://amzn.to/2JqHn8Z

Hard Drive (QTY 1):
https://amzn.to/3lic3X5

Risers (QTY 6):
https://amzn.to/33rIgVE

Power Supplies (QTY 2):
https://amzn.to/3fTRpLR

Add2PSU (QTY 1):
https://amzn.to/39s4URY

GPUs (QTY 6):
https://amzn.to/2JqvXC8

Power Switch (QTY 1):
https://amzn.to/3ljmNVk

XMR-STAK Error using NVidia 1080TI Cards

How-To fix NVidia 1080TI – XMR-STAK Thread Error

I have been seeing the following error pop-up when you run XMR-STAK for the first time while using NVidia 1080TI cards

[CUDA] Error gpu 1: <C:/xmr-stak/xmrstak/backend/nvidia/nvcc_code/cuda_extra.cu>:312
**suggestion: Try to reduce the value of the attribute ‘threads’ in the NVIDIA config file.**

There is a simple way to resolve this error.  Open up the directory that you used to launch xmr-stak.exe 

if you are mining with NVidia cards, open up the nvidia.txt file.

[AMD steps are similar to this.  You would just open the amd.txt file instead]

For each of the GPUs listed within the txt file, you will need to Lower the number of Threads on this line:

“threads” : 26, “blocks” : 84,

I would recommend lowering them in half for all of your GPUs

“threads” : 13, “blocks” : 84,

Save the file

Re-Launch xmr-stak.exe and try to mine with it.

If it works you will then incrementally raise the threads to the level which your mining rig can support.

That’s it!  Thanks for reading

6 GPU NVidia 1080TI / CUDA 10 / NVidia-410 Drivers / Hashcat 5.0.0 / Ubuntu 18.04

#hashcat -b

hashcat (v5.0.0-84-geec1fba4) starting in benchmark mode…

Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.

OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: GeForce GTX 1080 Ti, 2793/11175 MB allocatable, 28MCU
* Device #2: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #3: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #4: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #5: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #6: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU

Benchmark relevant options:
===========================
* –optimized-kernel-enable

Hashmode: 0 – MD5

Speed.#1………: 30812.1 MH/s (27.70ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Speed.#2………: 32529.5 MH/s (27.50ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Speed.#3………: 32031.3 MH/s (27.21ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Speed.#4………: 30324.8 MH/s (27.46ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Speed.#5………: 30532.0 MH/s (26.94ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Speed.#6………: 31141.3 MH/s (27.54ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Speed.#*………: 187.4 GH/s

Hashmode: 100 – SHA1

Speed.#1………: 11321.3 MH/s (80.12ms) @ Accel:128 Loops:1024 Thr:256 Vec:2
Speed.#2………: 11374.7 MH/s (79.01ms) @ Accel:128 Loops:1024 Thr:256 Vec:2
Speed.#3………: 11301.7 MH/s (79.01ms) @ Accel:128 Loops:1024 Thr:256 Vec:2
Speed.#4………: 11375.1 MH/s (79.39ms) @ Accel:128 Loops:1024 Thr:256 Vec:2
Speed.#5………: 11430.5 MH/s (78.09ms) @ Accel:128 Loops:1024 Thr:256 Vec:2
Speed.#6………: 11400.4 MH/s (79.69ms) @ Accel:128 Loops:1024 Thr:256 Vec:2
Speed.#*………: 68203.7 MH/s

Hashmode: 1400 – SHA2-256

Speed.#1………: 3965.3 MH/s (55.34ms) @ Accel:128 Loops:256 Thr:256 Vec:1
Speed.#2………: 4097.7 MH/s (54.66ms) @ Accel:128 Loops:256 Thr:256 Vec:1
Speed.#3………: 4069.8 MH/s (54.48ms) @ Accel:128 Loops:256 Thr:256 Vec:1
Speed.#4………: 3984.1 MH/s (54.84ms) @ Accel:128 Loops:256 Thr:256 Vec:1
Speed.#5………: 4082.5 MH/s (53.61ms) @ Accel:128 Loops:256 Thr:256 Vec:1
Speed.#6………: 4072.4 MH/s (55.04ms) @ Accel:128 Loops:256 Thr:256 Vec:1
Speed.#*………: 24271.7 MH/s

Hashmode: 1700 – SHA2-512

Speed.#1………: 1401.6 MH/s (81.58ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#2………: 1366.3 MH/s (80.19ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#3………: 1404.8 MH/s (80.03ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#4………: 1402.7 MH/s (80.86ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#5………: 1428.6 MH/s (79.17ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#6………: 1408.5 MH/s (81.21ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#*………: 8412.5 MH/s

Hashmode: 2500 – WPA-EAPOL-PBKDF2 (Iterations: 4096)

Speed.#1………: 503.9 kH/s (53.02ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#2………: 498.2 kH/s (52.76ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#3………: 500.2 kH/s (52.08ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#4………: 496.9 kH/s (52.66ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#5………: 510.6 kH/s (51.44ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#6………: 506.1 kH/s (52.54ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#*………: 3015.9 kH/s

Hashmode: 1000 – NTLM

Speed.#1………: 42210.1 MH/s (16.76ms) @ Accel:128 Loops:1024 Thr:256 Vec:2
Speed.#2………: 46847.2 MH/s (17.00ms) @ Accel:128 Loops:1024 Thr:256 Vec:2
Speed.#3………: 47071.9 MH/s (16.70ms) @ Accel:128 Loops:1024 Thr:256 Vec:2
Speed.#4………: 42154.1 MH/s (16.63ms) @ Accel:128 Loops:1024 Thr:256 Vec:2
Speed.#5………: 47066.0 MH/s (16.47ms) @ Accel:128 Loops:1024 Thr:256 Vec:2
Speed.#6………: 46836.9 MH/s (16.82ms) @ Accel:128 Loops:1024 Thr:256 Vec:2
Speed.#*………: 272.2 GH/s

Hashmode: 3000 – LM

Speed.#1………: 26691.9 MH/s (32.25ms) @ Accel:128 Loops:1024 Thr:256 Vec:1
Speed.#2………: 26740.0 MH/s (32.49ms) @ Accel:128 Loops:1024 Thr:256 Vec:1
Speed.#3………: 27078.6 MH/s (31.96ms) @ Accel:128 Loops:1024 Thr:256 Vec:1
Speed.#4………: 25743.8 MH/s (32.08ms) @ Accel:128 Loops:1024 Thr:256 Vec:1
Speed.#5………: 26966.5 MH/s (31.62ms) @ Accel:128 Loops:1024 Thr:256 Vec:1
Speed.#6………: 26687.1 MH/s (32.04ms) @ Accel:128 Loops:1024 Thr:256 Vec:1
Speed.#*………: 159.9 GH/s

Hashmode: 5500 – NetNTLMv1 / NetNTLMv1+ESS

Speed.#1………: 28072.5 MH/s (30.73ms) @ Accel:128 Loops:1024 Thr:256 Vec:1
Speed.#2………: 28575.4 MH/s (30.93ms) @ Accel:128 Loops:1024 Thr:256 Vec:1
Speed.#3………: 27606.5 MH/s (30.54ms) @ Accel:128 Loops:1024 Thr:256 Vec:1
Speed.#4………: 27665.4 MH/s (30.57ms) @ Accel:128 Loops:1024 Thr:256 Vec:1
Speed.#5………: 27995.9 MH/s (29.94ms) @ Accel:128 Loops:1024 Thr:256 Vec:1
Speed.#6………: 27669.8 MH/s (30.52ms) @ Accel:128 Loops:1024 Thr:256 Vec:1
Speed.#*………: 167.6 GH/s

Hashmode: 5600 – NetNTLMv2

Speed.#1………: 2184.6 MH/s (51.10ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#2………: 2196.9 MH/s (51.24ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#3………: 2162.2 MH/s (50.72ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#4………: 2227.9 MH/s (50.85ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#5………: 2251.7 MH/s (49.91ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#6………: 2234.8 MH/s (50.79ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#*………: 13257.9 MH/s

Hashmode: 1500 – descrypt, DES (Unix), Traditional DES

Speed.#1………: 1221.5 MH/s (93.28ms) @ Accel:16 Loops:1024 Thr:256 Vec:1
Speed.#2………: 1216.4 MH/s (92.77ms) @ Accel:16 Loops:1024 Thr:256 Vec:1
Speed.#3………: 1248.8 MH/s (92.56ms) @ Accel:16 Loops:1024 Thr:256 Vec:1
Speed.#4………: 1228.6 MH/s (92.82ms) @ Accel:16 Loops:1024 Thr:256 Vec:1
Speed.#5………: 1246.9 MH/s (91.64ms) @ Accel:16 Loops:1024 Thr:256 Vec:1
Speed.#6………: 1222.7 MH/s (92.94ms) @ Accel:16 Loops:1024 Thr:256 Vec:1
Speed.#*………: 7384.9 MH/s

Hashmode: 500 – md5crypt, MD5 (Unix), Cisco-IOS $1$ (MD5) (Iterations: 1000)

Speed.#1………: 11748.5 kH/s (62.83ms) @ Accel:1024 Loops:1000 Thr:32 Vec:1
Speed.#2………: 11433.8 kH/s (62.29ms) @ Accel:1024 Loops:1000 Thr:32 Vec:1
Speed.#3………: 9552.9 kH/s (61.38ms) @ Accel:1024 Loops:1000 Thr:32 Vec:1
Speed.#4………: 10466.3 kH/s (63.17ms) @ Accel:1024 Loops:1000 Thr:32 Vec:1
Speed.#5………: 11531.4 kH/s (59.97ms) @ Accel:1024 Loops:1000 Thr:32 Vec:1
Speed.#6………: 11995.0 kH/s (61.08ms) @ Accel:1024 Loops:1000 Thr:32 Vec:1
Speed.#*………: 66727.9 kH/s

Hashmode: 3200 – bcrypt $2*$, Blowfish (Unix) (Iterations: 32)

Speed.#1………: 21696 H/s (40.33ms) @ Accel:16 Loops:8 Thr:8 Vec:1
Speed.#2………: 21736 H/s (39.83ms) @ Accel:16 Loops:8 Thr:8 Vec:1
Speed.#3………: 20255 H/s (39.84ms) @ Accel:16 Loops:8 Thr:8 Vec:1
Speed.#4………: 17433 H/s (40.37ms) @ Accel:16 Loops:8 Thr:8 Vec:1
Speed.#5………: 20955 H/s (39.30ms) @ Accel:16 Loops:8 Thr:8 Vec:1
Speed.#6………: 19016 H/s (39.66ms) @ Accel:16 Loops:8 Thr:8 Vec:1
Speed.#*………: 121.1 kH/s

Hashmode: 1800 – sha512crypt $6$, SHA512 (Unix) (Iterations: 5000)

Speed.#1………: 195.2 kH/s (55.51ms) @ Accel:512 Loops:128 Thr:32 Vec:1
Speed.#2………: 194.7 kH/s (55.46ms) @ Accel:512 Loops:128 Thr:32 Vec:1
Speed.#3………: 196.3 kH/s (55.18ms) @ Accel:512 Loops:128 Thr:32 Vec:1
Speed.#4………: 190.7 kH/s (55.33ms) @ Accel:512 Loops:128 Thr:32 Vec:1
Speed.#5………: 194.9 kH/s (54.52ms) @ Accel:512 Loops:128 Thr:32 Vec:1
Speed.#6………: 193.5 kH/s (55.34ms) @ Accel:512 Loops:128 Thr:32 Vec:1
Speed.#*………: 1165.3 kH/s

Hashmode: 7500 – Kerberos 5 AS-REQ Pre-Auth etype 23

Speed.#1………: 409.9 MH/s (69.32ms) @ Accel:256 Loops:64 Thr:64 Vec:1
Speed.#2………: 418.1 MH/s (68.41ms) @ Accel:256 Loops:64 Thr:64 Vec:1
Speed.#3………: 416.4 MH/s (68.45ms) @ Accel:256 Loops:64 Thr:64 Vec:1
Speed.#4………: 414.2 MH/s (68.99ms) @ Accel:256 Loops:64 Thr:64 Vec:1
Speed.#5………: 419.6 MH/s (67.45ms) @ Accel:256 Loops:64 Thr:64 Vec:1
Speed.#6………: 424.2 MH/s (67.68ms) @ Accel:256 Loops:64 Thr:64 Vec:1
Speed.#*………: 2502.4 MH/s

Hashmode: 13100 – Kerberos 5 TGS-REP etype 23

Speed.#1………: 413.7 MH/s (69.08ms) @ Accel:256 Loops:64 Thr:64 Vec:1
Speed.#2………: 420.9 MH/s (68.00ms) @ Accel:256 Loops:64 Thr:64 Vec:1
Speed.#3………: 426.6 MH/s (67.45ms) @ Accel:256 Loops:64 Thr:64 Vec:1
Speed.#4………: 404.5 MH/s (68.06ms) @ Accel:256 Loops:64 Thr:64 Vec:1
Speed.#5………: 409.0 MH/s (66.63ms) @ Accel:256 Loops:64 Thr:64 Vec:1
Speed.#6………: 423.6 MH/s (67.36ms) @ Accel:256 Loops:64 Thr:64 Vec:1
Speed.#*………: 2498.3 MH/s

Hashmode: 15300 – DPAPI masterkey file v1 (Iterations: 23999)

Speed.#1………: 90607 H/s (51.98ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#2………: 89260 H/s (51.98ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#3………: 87394 H/s (51.33ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#4………: 90018 H/s (51.68ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#5………: 89189 H/s (50.61ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#6………: 90973 H/s (51.82ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#*………: 537.4 kH/s

Hashmode: 15900 – DPAPI masterkey file v2 (Iterations: 7999)

Speed.#1………: 53882 H/s (64.77ms) @ Accel:256 Loops:128 Thr:32 Vec:1
Speed.#2………: 55701 H/s (63.65ms) @ Accel:256 Loops:128 Thr:32 Vec:1
Speed.#3………: 55610 H/s (63.81ms) @ Accel:256 Loops:128 Thr:32 Vec:1
Speed.#4………: 53128 H/s (64.05ms) @ Accel:256 Loops:128 Thr:32 Vec:1
Speed.#5………: 55293 H/s (62.36ms) @ Accel:256 Loops:128 Thr:32 Vec:1
Speed.#6………: 56658 H/s (62.97ms) @ Accel:256 Loops:128 Thr:32 Vec:1
Speed.#*………: 330.3 kH/s

Hashmode: 7100 – macOS v10.8+ (PBKDF2-SHA512) (Iterations: 35000)

Speed.#1………: 15860 H/s (50.87ms) @ Accel:128 Loops:32 Thr:256 Vec:1
Speed.#2………: 15165 H/s (50.54ms) @ Accel:128 Loops:32 Thr:256 Vec:1
Speed.#3………: 15540 H/s (50.43ms) @ Accel:128 Loops:32 Thr:256 Vec:1
Speed.#4………: 15610 H/s (50.56ms) @ Accel:128 Loops:32 Thr:256 Vec:1
Speed.#5………: 16109 H/s (49.56ms) @ Accel:128 Loops:32 Thr:256 Vec:1
Speed.#6………: 15675 H/s (50.66ms) @ Accel:128 Loops:32 Thr:256 Vec:1
Speed.#*………: 93959 H/s

Hashmode: 11600 – 7-Zip (Iterations: 524288)

Speed.#1………: 11549 H/s (75.36ms) @ Accel:128 Loops:512 Thr:256 Vec:1
Speed.#2………: 11675 H/s (74.94ms) @ Accel:128 Loops:512 Thr:256 Vec:1
Speed.#3………: 11777 H/s (73.82ms) @ Accel:128 Loops:512 Thr:256 Vec:1
Speed.#4………: 11403 H/s (74.86ms) @ Accel:128 Loops:512 Thr:256 Vec:1
Speed.#5………: 11705 H/s (72.68ms) @ Accel:128 Loops:512 Thr:256 Vec:1
Speed.#6………: 11608 H/s (74.24ms) @ Accel:128 Loops:512 Thr:256 Vec:1
Speed.#*………: 69718 H/s

Hashmode: 12500 – RAR3-hp (Iterations: 262144)

Speed.#1………: 49474 H/s (69.97ms) @ Accel:8 Loops:16384 Thr:256 Vec:1
Speed.#2………: 49584 H/s (70.95ms) @ Accel:8 Loops:16384 Thr:256 Vec:1
Speed.#3………: 49425 H/s (70.62ms) @ Accel:8 Loops:16384 Thr:256 Vec:1
Speed.#4………: 46549 H/s (75.75ms) @ Accel:8 Loops:16384 Thr:256 Vec:1
Speed.#5………: 45534 H/s (75.60ms) @ Accel:8 Loops:16384 Thr:256 Vec:1
Speed.#6………: 45352 H/s (75.66ms) @ Accel:8 Loops:16384 Thr:256 Vec:1
Speed.#*………: 285.9 kH/s

Hashmode: 13000 – RAR5 (Iterations: 32767)

Speed.#1………: 49120 H/s (69.11ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#2………: 49563 H/s (68.76ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#3………: 50303 H/s (68.43ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#4………: 49116 H/s (68.85ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#5………: 51149 H/s (67.84ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#6………: 49402 H/s (68.68ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#*………: 298.7 kH/s

Hashmode: 6211 – TrueCrypt PBKDF2-HMAC-RIPEMD160 + XTS 512 bit (Iterations: 2000)

Speed.#1………: 389.0 kH/s (70.13ms) @ Accel:128 Loops:64 Thr:256 Vec:1
Speed.#2………: 387.5 kH/s (69.35ms) @ Accel:128 Loops:64 Thr:256 Vec:1
Speed.#3………: 395.3 kH/s (68.65ms) @ Accel:128 Loops:64 Thr:256 Vec:1
Speed.#4………: 389.9 kH/s (69.61ms) @ Accel:128 Loops:64 Thr:256 Vec:1
Speed.#5………: 399.8 kH/s (67.99ms) @ Accel:128 Loops:64 Thr:256 Vec:1
Speed.#6………: 387.1 kH/s (68.89ms) @ Accel:128 Loops:64 Thr:256 Vec:1
Speed.#*………: 2348.6 kH/s

Hashmode: 13400 – KeePass 1 (AES/Twofish) and KeePass 2 (AES) (Iterations: 6000)

Speed.#1………: 184.2 kH/s (99.94ms) @ Accel:512 Loops:256 Thr:32 Vec:1
Speed.#2………: 185.0 kH/s (99.64ms) @ Accel:512 Loops:256 Thr:32 Vec:1
Speed.#3………: 185.0 kH/s (99.25ms) @ Accel:512 Loops:256 Thr:32 Vec:1
Speed.#4………: 183.3 kH/s (101.08ms) @ Accel:512 Loops:256 Thr:32 Vec:1
Speed.#5………: 178.9 kH/s (100.66ms) @ Accel:512 Loops:256 Thr:32 Vec:1
Speed.#6………: 185.2 kH/s (101.18ms) @ Accel:512 Loops:256 Thr:32 Vec:1
Speed.#*………: 1101.6 kH/s

Hashmode: 6800 – LastPass + LastPass sniffed (Iterations: 500)

Speed.#1………: 3094.3 kH/s (66.77ms) @ Accel:128 Loops:125 Thr:256 Vec:1
Speed.#2………: 2945.4 kH/s (67.14ms) @ Accel:128 Loops:125 Thr:256 Vec:1
Speed.#3………: 2898.4 kH/s (67.05ms) @ Accel:128 Loops:125 Thr:256 Vec:1
Speed.#4………: 2703.0 kH/s (66.63ms) @ Accel:128 Loops:125 Thr:256 Vec:1
Speed.#5………: 2924.7 kH/s (65.91ms) @ Accel:128 Loops:125 Thr:256 Vec:1
Speed.#6………: 2901.5 kH/s (66.43ms) @ Accel:128 Loops:125 Thr:256 Vec:1
Speed.#*………: 17467.4 kH/s

Hashmode: 11300 – Bitcoin/Litecoin wallet.dat (Iterations: 199999)

Speed.#1………: 5931 H/s (96.58ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#2………: 5947 H/s (96.14ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#3………: 5935 H/s (95.93ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#4………: 5908 H/s (96.08ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#5………: 6076 H/s (94.35ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#6………: 5867 H/s (96.40ms) @ Accel:128 Loops:128 Thr:256 Vec:1
Speed.#*………: 35664 H/s

Started: Sat Nov 17 18:24:13 2018
Stopped: Sat Nov 17 18:37:12 2018

The hardware that I used in this guide:
Gigabyte AORUS GeForce GTX 1080 Ti (QTY 6):
https://amzn.to/2JqvXC8

Motherboard (QTY 1): 
https://amzn.to/2JqGJZ7

CPU (QTY 1): 
https://amzn.to/3qevp2X

Memory (QTY 1): 
https://amzn.to/2JqHn8Z

Hard Drive (QTY 1):
https://amzn.to/3nZ5pH4

Risers (QTY 6):  
https://amzn.to/33rIgVE

Power Supplies (QTY 2):
https://amzn.to/3fTRpLR

Add2PSU (QTY 1):
https://amzn.to/39s4URY

Power Switch (QTY 1):  
https://amzn.to/3ljmNVk

VCRUNTIME140.DLL Error When Running XMR-STAK

How-To fix the VCRUNTIME140.DLL error

The VCRUNTIME140.DLL error seems all too common when mining on Windows 10 computers.  I recently came across it on a system that I manage.  I was trying to install, configure, and run XMR-STAK so we could mine LOKI with it and figured that if it is affecting me, it is probably affecting others.

So here is the fix….

Download and install the Microsoft Visual C++ Redistributable package from here :

https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

And you can now run and install XMR-STAK

Mining using AMD RX480 Nitro & RX580 Nitro on Ubuntu

How-To Guide for mining with the AMD Series cards on Ubuntu Server 16.04.04

This guide assumes you already have the Rig built, and Ubuntu Server 16.04.04 installed on it.  Once the rig boots to the terminal, this guide begins.  I am going to install everything as root, yes there are reasons why you should and should not do it that way.  I just prefer to get it up and running as quickly as possible.  I do not store anything on my miners, and you should not either.  Keep your wallets off your mining rig.  Keep your coins secure.  Keep your miners with limited data on them, so you can wipe and reinstall on the fly if you need.

Once Install Ubuntu 16.04 Server is installed type the following in bold as they appear

sudo bash

ifconfig

apt-get install openssh-server

Now you can use your laptop/desktop and log into the server.  Download putty, and connect to the server via it’s IP or Server Name.  My Username Name is tacticalware, so you can change everywhere you see tacticalware listed, you will change that to the username of the account you are logged in as

sudo bash

apt-get update

apt-get upgrade

apt install git screen nmap ncdu busybox inxi clinfo links unzip python xorg xserver-xorg-legacy xserver-xorg-video-dummy libcurl3

systemctl disable lightdm.service

mkdir /miner && mkdir /miner/drivers && mkdir /miner/drivers/amd && cd /miner/drivers/amd

Download the drivers from on a laptop

Now use Winscp on the laptop to copy the drivers to the Ubuntu Server

cd /home/tacticalware/ && cp ./* /miner/drivers/amd/ && cd /miner/drivers/amd/

The version I downloaded and used was amdgpu-pro-17.30-458935.tar.xz … you will need to change that part of the name to the version you have

tar -Jxvf amdgpu-pro-17.30-458935.tar.xz && cd amdgpu-pro-17.30-458935 && ./amdgpu-pro-install -y

usermod -a -G video $LOGNAME

Download the SDK from here to your laptop

Winscp it to the server

Move the SDK from your home directory to /miner/drivers/amd

tar xf AMD-APP-SDKInstaller-v3.0.130.136-GA-linux64.tar.bz2 && ./AMD-APP-SDK-v3.0.130.136-GA-linux64.sh

reboot

Log back into the server now

sudo bash

clinfo

clinfo | grep compute

nano /etc/X11/Xwrapper.config

delete the last line:
allowed_users=console

insert at end of file:

allowed_users=anybody
needs_root_rights=yes

Create a new file for operating without a monitor:

nano /etc/X11/xorg.conf

Section “ServerLayout”
Identifier “X.org Configured”
Screen 0 “Screen8” 0 0
EndSection

Section “Files”
ModulePath “/usr/lib/xorg/modules”
FontPath “/usr/share/fonts/X11/misc”
FontPath “/usr/share/fonts/X11/cyrillic”
FontPath “/usr/share/fonts/X11/100dpi/:unscaled”
FontPath “/usr/share/fonts/X11/75dpi/:unscaled”
FontPath “/usr/share/fonts/X11/Type1”
FontPath “/usr/share/fonts/X11/100dpi”
FontPath “/usr/share/fonts/X11/75dpi”
FontPath “built-ins”
EndSection

Section “Device”
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: “True”/”False”,
### <string>: “String”, <freq>: “<f> Hz/kHz/MHz”,
### <percent>: “<f>%”
### [arg]: arg optional
#Option “ShadowFB” # [<bool>]
#Option “DefaultRefresh” # [<bool>]
#Option “ModeSetClearScreen” # [<bool>]
Identifier “Card8”
Driver “dummy”
VideoRam 16384
EndSection

Section “Monitor”
Identifier “Monitor8”
HorizSync 15.0-100.0
VertRefresh 15.0-200.0
Modeline “1600×900” 33.92 1600 1632 1760 1792 900 921 924 946
EndSection

Section “Screen”
Identifier “Screen8”
Device “Card8”
Monitor “Monitor8”
SubSection “Display”
Viewport 0 0
Depth 24
Virtual 1600 900
EndSubSection
EndSection

Save the file and exit

cd /home/tacticalware/

nano .bashrc

Add the following at end of .bashrc

export DISPLAY=:0

Save the file and exit

nano /etc/profile

Add the following at end of /etc/profile:
export XAUTHORITY=~/.Xauthority

Save the file and exit

nano .xinitrc

#!/bin/bash
DISPLAY=:0 && xterm -geometry +1+1 -n login

Save the file and exit

cd /miner/drivers/ && mkdir claymore && cd /miner/drivers/claymore

On your laptop download Claymore from

https://drive.google.com/drive/folders/0B69wv2iqszefdmJickl5MF9BOEE

Winscp it to the mining rig

Move it to /miner/drivers/claymore

tar zxvf the file

nano zec.sh

#!/bin/sh
xinit &
sleep 5
export GPU_FORCE_64BIT_PTR=1
export GPU_MAX_HEAP_SIZE=100
export GPU_USE_SYNC_OBJECTS=1
export GPU_MAX_ALLOC_PERCENT=100
export GPU_SINGLE_ALLOC_PERCENT=100

./zecminer64 -zpool us1-zcash.flypool.org:3333 -zwal t1QYSbLrnbECDu76KDcvoyjBbbhsuWxZXWm.miner20 -zpsw x

Save the file and exit

chmod +x zec.sh

Update config.txt file, also modify epool and dpool with your wallet info and remove default dev info

Save the files

screen ./zec.sh

Now you will want to watch for issues

You can close putty whenever, it does not need to be open for your miner to work, and if you want to reattach a screen, log back in using putty and type

screen -r

Installing TPRUVOT’s CCMiner on Ubuntu 16.04

How-to Guide for Installing the Linux version of ccminer (tpruvot) on Ubuntu 16.04.04

This is a quick guide that I created a few months back.  It gets the latest version of tpruvot’s ccminer installed and running on your Ubuntu mining rig.  There are a lot of algos which can use this, and since most of my rigs run on linux, I had to find a way to get it installed.  It is the general commands that I use from a terminal.  The assumption here is that you already have Ubuntu 16.04 installed and updated.  It is also assumed that you are running NVidia 1080Ti cards, and they are all functional.  I am going to run it all logged in as sudo to make it quick and easy.

From the terminal:

sudo bash

apt-get dist-upgade

apt-get purge nvidia*

reboot

mkdir /drivers && mkdir /drivers/nvidia

wget https://developer.nvidia.com/compute/cuda/9.1/Prod/local_installers/cuda_9.1.85_387.26_linux

mv cuda_9.1.85_387.26_linux cuda_9.1.85_387.26_linux.run

chmod +x cuda_9.1.85_387.26_linux cuda_9.1.85_387.26_linux.run

sh cuda_9.1.85_387.26_linux.run

Answer “yes” for installing the nvidia-drivers, the cuda tools and the symbolic link.

apt-get install git automake openssl libssl1.0.0 libssl-dev libcurl4-openssl-dev

cd /drivers/

git clone https://github.com/tpruvot/ccminer.git

cd ccminer

nano Makefile.am

CTRL & W

Search for 61

Remove comment at the beginning of the line which refers to “61”

CTRL & X

Y to save

nano /etc/ld.so.conf.d/cuda-9.1-x86_64

Put only one line:
/usr/local/cuda-9.1/lib64

CTRL & X

Y to save

ldconfig

cd /drivers/ccminer

./build.sh

make install

cd /home/miner/ && nano .bashrc

add this to the end:
export LD_LIBRARY_PATH=/usr/local/cuda-9.1/lib64:$LD_LIBRARY_PATH
export PATH=/usr/local/cuda-9.1/bin:$PATH

CTRL & X

Y to save

nano start.sh

Insert the following into the file:

nvidia-smi -pm 1
nvidia-smi -acp 0
nvidia-smi -pl 300
./ccminer -a x16r -i 20 -o stratum+tcp://us.bsod.pw:2176 -u RMzHAFgqgjV5qLkajBjLQ325V7HWBpG3d9 -p c=RVN

CTRL & X

Y to save

chmod +x start.sh

./start.sh

You are now up and mining.  I have chosen Raven for this one, only since I was mining it when I put it together.  You will want to remove my wallet address and insert your own.  Otherwise, the rest will get your rig up and running.

Happy Mining!

Mining LOKI on Windows 10 with NVidia 1080TI Cards

How-to Guide for Mining LOKI

Quick rundown on how to mine a new crypto named LOKI or LOK as some of you may know it as.  I mine it with both NVidia and AMD series cards.  This guide will walk you through mining it with NVidia Series cards.  You will find that the guide is a mirror of the AMD guide, except for how you fine tune it at the end.

The mining software will throw errors with your AV program.  You will need to whitelist the files when they are downloaded, or disable Realtime Protection..  Personally, I only use Windows Defender on my mining rigs, so I can keep the costs down, plus it is easy to wipe and reinstall the OS if need be.

For Windows Defender, you will need to open the program up, and disable Realtime Protection

If you are using Chrome as your Browser, you will also need to allow the download there as well.  To do this:

Open up Chrome

In your address bar type in chrome://settings and press Enter

Scroll to the bottom and select Advanced

De-Select “Protect your device from dangerous sites” 

Now you can download the software

Open up another chrome tab and download XMR-STAK to your Windows 10 computer from here:

https://github.com/fireice-uk/xmr-stak/releases

Once you have it downloaded, go ahead and unzip the file to your Desktop

Navigate to the unpacked files

Double click on xmr-stak and Run the file

You will need to insert a port for monitoring the progress.  I use port 30131 and press Enter

Next type in cryptonight_heavy and press Enter

For the pool address, I use loki.ingest.cryptoknight.cc:7733  press Enter

Your username will be your wallet address, for example

LChtjHqr29p5FojLdMtcUW5ApLWyQHH5j4366V78YECEjUkgK99Y7uLDVLpHjXpYM3UcZ39FFL5Gvd4debF95mcJHbnx5ke

Your password will be your worker name.  For example mine is Miner6

Your Rig Identifier can be empty, so just press Enter

Input N for TLS and press Enter

Insert N for Nicehash and press Enter

Input N for multiple pools and press Enter

Select Yes when prompted

and your miner will begin!

Now you can use the ipaddress:port/h of your miner to keep an eye on it’s progress from anywhere in the network.  For example, navigate to

Once you are mining, you can open up the nvidia.txt file in the same directory as your xmr-stak executable.  Within the nvidia.txt file, you will be able to modify your settings.  I have found that changing the threads setting it will yield the most results.  Each series of card can act differently, so spend some time, and fine tune this settings.  It will be worth the time invested.

Happy Mining!

The hardware that I used in this guide:
Gigabyte AORUS GeForce GTX 1080 Ti (QTY 6):
https://amzn.to/2JqvXC8

Motherboard (QTY 1): 
https://amzn.to/2JqGJZ7

CPU (QTY 1): 
https://amzn.to/3qevp2X

Memory (QTY 1): 
https://amzn.to/2JqHn8Z

Hard Drive (QTY 1):
https://amzn.to/3nZ5pH4

Risers (QTY 6):  
https://amzn.to/33rIgVE

Power Supplies (QTY 2):
https://amzn.to/3fTRpLR

Add2PSU (QTY 1):
https://amzn.to/39s4URY

Power Switch (QTY 1):  
https://amzn.to/3ljmNVk

Mining LOKI on Windows 10 with AMD RX Cards

How-to Guide for Mining LOKI

Quick rundown on how to mine a new crypto named LOKI or LOK as some of you may know it as.  I mine it with both NVidia and AMD series cards.  This guide will walk you through mining it with AMD RX Series cards

The mining software will throw errors with your AV program.  You will need to whitelist the files when they are downloaded, or disable Realtime Protection..  Personally, I only use Windows Defender on my mining rigs, so I can keep the costs down, plus it is easy to wipe and reinstall the OS if need be.

For Windows Defender, you will need to open the program up, and disable Realtime Protection

If you are using Chrome as your Browser, you will also need to allow the download there as well.  To do this:

Open up Chrome

In your address bar type in chrome://settings and press Enter

Scroll to the bottom and select Advanced

De-Select “Protect your device from dangerous sites” 

Now you can download the software

Open up another chrome tab and download XMR-STAK to your Windows 10 computer from here:

https://github.com/fireice-uk/xmr-stak/releases

Once you have it downloaded, go ahead and unzip the file to your Desktop

Navigate to the unpacked files

Double click on xmr-stak and Run the file

You will need to insert a port for monitoring the progress.  I use port 30131 and press Enter

Next type in cryptonight_heavy and press Enter

For the pool address, I use loki.ingest.cryptoknight.cc:7733  press Enter

Your username will be your wallet address, for example

LChtjHqr29p5FojLdMtcUW5ApLWyQHH5j4366V78YECEjUkgK99Y7uLDVLpHjXpYM3UcZ39FFL5Gvd4debF95mcJHbnx5ke

Your password will be your worker name.  For example mine is Miner6

Your Rig Identifier can be empty, so just press Enter

Input N for TLS and press Enter

Insert N for Nicehash and press Enter

Input N for multiple pools and press Enter

Select Yes when prompted

and your miner will begin!

Now you can use the ipaddress:port/h of your miner to keep an eye on it’s progress from anywhere in the network.  For example, navigate to

Once you are mining, you can open up the amd file in the same directory as your xmr-stak executable.  Within the amd file, you will be able to modify your settings.  I have found that changing the intensity setting and also the worksize will yield the most results.  Each series of card can act differently, so spend some time, and fine tune these settings.  It will be worth the time invested.

Happy Mining!