develsoftware / gminerrelease Goto Github PK

miner gives "share above target" error while mining on equihash150.5 and 150.5.3

I'm getting 10-12% less hashrate on a 2060 SUPER compared to miniZ on Beamhash.

On the other hand, a 1660 SUPER seems to yield roughly the same hashrate on both mining apps.

What gives? Does this mining app needs more CUDA optimizations?

It's kinda weird, because both cards use the Turing microarchitecture and I'd prefer to use gminer over miniZ (I get 17% CPU usage with that, for no apparent reason).

Ycash is a chain fork of Zcash that will launch at block height 570,000 of the Zcash blockchain (around July 18, 2019). A testnet will be available starting June 7, 2019. We are using Equihash(192,7).

We'd love for Ycash miners to be able to mine using GMiner.

Note that Ycash is changing the Zcash address formats. (For example, Sapling addresses start with "ys" instead of "zs".)

More information:

https://www.ycash.xyz/the_fork/

https://github.com/YcashFoundation/ycash

Card drivers are the latest, why one card works well, PCI-E wiring to another card is extremely low hashrate.
GPU0 and GPU 2 are Zotac GTX 1660TI cards.

The miner currently doesn't work on RTX 2060 without additional manipulations.

The explanation.

For RTX 2060 and Windows 10, NVIDIA driver is installed automatically (DCH driver).

This driver installs NVML.DLL to System32, not to NVSMI. You should look for the DLL in System32, too.

希望增加挖矿强度的功能 不然很不方便

Sometimes Gminer just stops at the startup and hangs (almost) idle. It looks like it tries to calculate something on the GPUs (MSI Afterburner shows active memory and core clock), but the temperature remains low.

This is what you get:

+----------------------------------------------------------------+
|                          GMiner v1.47                          |
+----------------------------------------------------------------+
Algorithm:          Equihash + Scrypt "VDS"
Stratum server:     
  host:             stratum://vds-eu.uupool.cn:13032
  user:             
  password:         x
Power calculator:   on
Color output:       on
Watchdog:           off
API:                http://127.0.0.1:32900
Log to file:        off
Selected devices:   GPU0
Intensity:          100 
Temperature limits: 90C 
------------------------------------------------------------------

(user address removed)

Then, the miner just waits forever and you need to Ctrl+C or kill it.

This is what I have tried:

• enabling watchdog did not help
• disabling power calculator did not help
• lower overclocking frequencies did not help
• start with/without admin privileges did not change a thing
• it happens for all algorithms
• no matter if only one GPU or multiple GPUs are in use.
• If I enable logfiles, the log file is being created, but remains empty.
• it happens more often, if you start miner.exe as subprocess (e.g. if using powershell's "Start-Process" command)
• gminer is the only miner, out of a bunch of others, that behaves like that
• now comes the weird thing: if miner.exe fails as subprocess in powershell and does not fail, when called by hand in a cmd window (using the exact same command line arguments), it then does not fail anymore when called as subprocess in powershell, afterwards.

Any idea, what is happening? Please fix this. Also, if you need assistance in debugging, please let me know.

Trying to get GMiner v1.52 working on linux for mining Grin on cuckatoo31 with my 1080 (non ti) 8gb card. It is not overclocked and wattage is at 150 (using SMOS OS). Upon starting up it gives me:

18:48:12 Error on GPU0: an illegal memory access was encountered
18:48:12 Stopped Mining on GPU0
System watchdog rebooted rig due to some problem. Lower OC and try less undervolting and if that will not help then most probably riser is broken.
18:48:13 Miner terminated, watchdog will restart process after 10 seconds

My miner config is as follows:

-a grin31 -s grin-us.luxor.tech -n 3000 -u myusername.myrigname -p x

I was able to get this card working on cuckatoo31 for Grin with bminer and lolminer but not gminer so far. Would like to just to compare how well it does with my card.

is there anything i'm missing here? Are 8gb cards not fully supported or should I change a configuration of some sort to get it to work?

Doka can't start the program, many algorithms can't start with multiple cards
----------------------------------------------------------------+
| GMiner v1.54 |
+----------------------------------------------------------------+
Algorithm: Equihash + Scrypt "VDS"
Stratum server:
host: stratum://vds.pandaminer.com:3035
user: VcZy7NKeNpLJqhgSE6fBHnjANwD4gMnccbx.2080S
password: x
Power calculator: on
Color output: on
Watchdog: on
API: http://127.0.0.1:10050
Log to file: C:\log\20190811_174946_VDS_log.txt
Selected devices: GPU0 GPU1 GPU2 GPU3 GPU4 GPU5 GPU6
Intensity: 100 100 100 100 100 100 100
Temperature limits: 90C 90C 90C 90C 90C 90C 90C

17:50:05 Connected to vds.pandaminer.com:3035
17:50:05 Subscribed to Stratum Server
17:50:05 Set Nonce: 0000088d
17:50:05 Authorized on Stratum Server
17:50:05 Set Target: 00000cccccccccccd00000000000000000000000000000000000000000000000
17:50:05 New Job: 5d4fe4c7
17:50:05 Started Mining on GPU0: GIGABYTE GeForce RTX 2080 SUPER 8GB
17:50:05 Started Mining on GPU1: GIGABYTE GeForce RTX 2080 SUPER 8GB
17:50:05 Started Mining on GPU2: GIGABYTE GeForce RTX 2080 SUPER 8GB
17:50:05 Started Mining on GPU3: GIGABYTE GeForce RTX 2080 SUPER 8GB
17:50:05 Started Mining on GPU4: GIGABYTE GeForce RTX 2080 SUPER 8GB
17:50:05 Started Mining on GPU5: GIGABYTE GeForce RTX 2080 SUPER 8GB
17:50:05 Started Mining on GPU6: GIGABYTE GeForce RTX 2080 SUPER 8GB
17:50:05 Error on GPU5: an illegal memory access was encountered
17:50:05 Stopped Mining on GPU0
17:50:05 Stopped Mining on GPU1
17:50:05 Stopped Mining on GPU2
17:50:05 Stopped Mining on GPU3
17:50:05 Stopped Mining on GPU4
17:50:05 Stopped Mining on GPU5
17:50:05 Stopped Mining on GPU6
17:50:07 Miner terminated, watchdog will restart process after 10 seconds
+----------------------------------------------------------------+
| GMiner v1.54 |
+----------------------------------------------------------------+
Algorithm: Equihash + Scrypt "VDS"
Stratum server:
host: stratum://vds.pandaminer.com:3035
user: VcZy7NKeNpLJqhgSE6fBHnjANwD4gMnccbx.2080S
password: x
Power calculator: on
Color output: on
Watchdog: on
API: http://127.0.0.1:10050
Log to file: C:\log\20190811_174946_VDS_log.txt
Selected devices: GPU0 GPU1 GPU2 GPU3 GPU4 GPU5 GPU6
Intensity: 100 100 100 100 100 100 100
Temperature limits: 90C 90C 90C 90C 90C 90C 90C

17:50:26 Connected to vds.pandaminer.com:3035
17:50:26 Subscribed to Stratum Server
17:50:26 Set Nonce: 0000088f
17:50:26 Authorized on Stratum Server
17:50:26 Set Target: 00000cccccccccccd00000000000000000000000000000000000000000000000
17:50:26 New Job: 5d4fe4c7
17:50:26 Started Mining on GPU0: GIGABYTE GeForce RTX 2080 SUPER 8GB
17:50:26 Started Mining on GPU1: GIGABYTE GeForce RTX 2080 SUPER 8GB
17:50:26 Started Mining on GPU2: GIGABYTE GeForce RTX 2080 SUPER 8GB
17:50:26 Started Mining on GPU3: GIGABYTE GeForce RTX 2080 SUPER 8GB
17:50:26 Started Mining on GPU4: GIGABYTE GeForce RTX 2080 SUPER 8GB
17:50:26 Started Mining on GPU5: GIGABYTE GeForce RTX 2080 SUPER 8GB
17:50:26 Started Mining on GPU6: GIGABYTE GeForce RTX 2080 SUPER 8GB
17:50:26 Error on GPU1: an illegal memory access was encountered
17:50:26 Stopped Mining on GPU0
17:50:26 Stopped Mining on GPU1
17:50:26 Stopped Mining on GPU2
17:50:26 Stopped Mining on GPU3
17:50:26 Stopped Mining on GPU4
17:50:26 Stopped Mining on GPU5
17:50:26 Stopped Mining on GPU6
17:50:28 Miner terminated, watchdog will restart process after 10 seconds

This prevents the miner from being integrated into mining solutions.

Can you add electron & Node.js as an exception to start the miner?

fixed bug with x2 hashare in miner output on eaglesong algorithm

It's true for mono mining Eaglesong. It shows still doubled hashrate, when dual mining.

Is there a way to reduce the intensity of the miner? System unusable when the miner is running.

I can't seem to mine EXCC with Gminer, even though it seems to be a typical 144,5 coin (it IS PoW and PoS but so is Snowgem...). It seems only LOL miner works with them, and LOL is slow as molasses.

Any way to get it to work with Gminer? They do over $1,000,000 in volume per day already, and their site is https://excc.co

Thanks!

Hello,

i am trying to run gminer 1.50 with the latest Nvidia driver 430.86 win10-64bit whql but this error appears at the screen "nvml.dll is eiher not designed to run with Windows or it contains an error".
I have four Nvidia 1080TI 11GB cards.

Could you please assist.

Looking forward to this enhancement , to switch over from bminer , unfortunately for now bminer is only one available with 1060 6gb support under win10.

Coin: VDS
Version: 1.47
GPU: P104 x 5

GMiner refuses to start when run by Node.js, emitting "Anti-hacking system detected". This is similar to bugs #12, #6. This prevents the miner from being integrated into mining solutions.

node run.js

run.js:

const { exec } = require("child_process")

exec('miner.exe --api 8888 --algo 150_5 --server beam-eu.leafpool.com --port 3333 --ssl 1 --user 18bdda8a95fa392e58ba67c72d642086715a8d0fc0fc4519442d77bddef9e3045c4.worker0 --logFile log.txt')

Are you goind to support the GRIN mid-July hard fork?

Since the last two versions, there seems to be a problem with dual mining Eth+CKB, at least when trying to connect to Sparkpool and mining with GTX1070.
NBminer works well with the same pools. As so did older revisions of Gminer. It now says: "[Eaglesong] Connection Error: Mailformed server message".

miner.exe --api 32900 --devices 0 1 2 3 4 5 --dual_intensity 1 1 1 1 1 1 --server daggerhashimoto.eu.nicehash.com --port 3353 --proto stratum --user xxxmybtcaddressxxx.rbm --pass x --cuda 1 --opencl 0 --dserver ckb-eu.sparkpool.com --dport 8888 --duser xxxmysparkpoolusernamexxx.rbm --dpass x --watchdog 0 --pec 0 --nvml 0 --algo ethash+eaglesong

16:45:36 [Ethash] GPU1: generating DAG for epoch #313
16:45:36 [Ethash] GPU2: generating DAG for epoch #313
16:45:36 [Ethash] GPU3: generating DAG for epoch #313
16:45:36 [Ethash] GPU4: generating DAG for epoch #313
16:45:36 [Ethash] GPU5: generating DAG for epoch #313
16:45:36 [Eaglesong] Connection Error: Mailformed server message
16:45:38 [Ethash] New Job: 0000000006dc4b86 Difficulty: 8.59G
16:45:41 [Eaglesong] Connected to ckb-eu.sparkpool.com:8888
16:45:41 [Eaglesong] Subscribed to Stratum Server
16:45:41 [Eaglesong] Set Nonce: f0b9d467
16:45:41 [Eaglesong] Authorized on Stratum Server
16:45:41 [Eaglesong] Connection Error: Mailformed server message
16:45:46 [Eaglesong] Connected to ckb-eu.sparkpool.com:8888
16:45:46 [Eaglesong] Subscribed to Stratum Server
16:45:46 [Eaglesong] Set Nonce: 3cef0038
16:45:46 [Eaglesong] Authorized on Stratum Server
16:45:46 [Eaglesong] Set Target: 000000001b7cdf00000000000000000000000000000000000000000000000000
16:45:46 [Eaglesong] Connection Error: Mailformed server message
16:45:47 [Ethash] New Job: 0000000006dd36e2 Difficulty: 8.59G

Please fix this

Thank you for adding dual mining ETH+CKB. Unfortunatly you might have forgotten to add the CKB statistics (hashrate, accepted/rejected shares) to your stats API. Please add this :)

I'm using rainbow miner and the miner window launches but doesn't start hashing. I have tried to split into multiple instances but this doesn't fix the problem. Both rainbow and gminer don't detect there is a problem until rainbow automatically disables the miner after a few minutes.

I've been chugging along mining Grin and did the responsible thing and upgraded to 1.5.1 Windows 64. On 1.5.0 I had no issues, but after upgrading it say's Failed to initialize miner on GPU0: SAPPHIRE Radeon RX 580 Series 8GB: Device not supported for this algorithm
No devices for mining

When i use Gminer directly the nicehash evrything is good, working.
When i use Gminer on miningrigrental.com, and i set the nicehash pool after i receive this message:

+----------------------------------------------------------------+
| GMiner v1.33 |
+----------------------------------------------------------------+
Algorithm: Cuckaroo 29 "Grin"
Stratum server:
host: stratum://eu-01.miningrigrentals.com:3322
user: XXXX.XXXXXX
password: XXXX
Power calculator: on
Color output: on
Watchdog: on
API: http://127.0.0.1:3333
Log to file: off
Selected devices: GPU0
Temperature limits: 90C

18:50:03 Connected to eu-01.miningrigrentals.com:3322
18:50:05 Authorized on Stratum Server
18:50:05 New Job: 1766548523417 Difficulty: 1
18:50:05 Started Mining on GPU0: ZOTAC GeForce GTX 1080 Ti 11GB
18:50:17 Connection Error: Write timed out
18:50:22 Connected to eu-01.miningrigrentals.com:3322
18:50:23 Authorized on Stratum Server

I test some version, 1.28, 1.33, 134 same error.
If i use BEAM evrything works perfectly

Zcash not mine on nanopool
Showing mine hashing power show but not update my account any rig or any power

I have been mining BeamhashII on a GTX1070 rig for 24h to find out, what is going on. It looks like, Gminer v1.69 crashes at least once every 90 minutes without an error message, when mining BeamhashII (on MiningRigRentals).
It says "09:53:15 Miner terminated, watchdog will restart process after 10 seconds", only.
It does not depend on overclocking - I have tried from under-clocking to no overclocking up to maximum overclocking. The result is always the same.

Legend: This image is a screen snip, out of RainbowMiner's Activity page. The columns are as follows:
| Status | Started | Last Seen | Minutes | Name | Algorithms | Devices |

Regarding the regularity and timing, I would suspect the miner fails to initialize (or switch) to developer fee mining.

@develsoftware please have a look into this. It's kind of annoying :)

please support Cuckarood29V pow.

it very similar to Cuckaroo29S (based on cuckaroo29; 32 cycle ; 4 noncebytes)

Cuckarood29V is a similar modification to Cuckarood29, but also 32 cycle and also 4 noncebytes.

https://pool.monerov.online/

Cuckaroo29: 42 cycle ; 8 noncebytes ; supported
Cuckaroo29S: 32 cycle ; 4 noncebytes ; supported
Cuckarood29: 42 cycle ; 8 noncebytes ; supported
Cuckarood29V: 32 cycle ; 4 noncebytes ; please support

reference miner: https://github.com/xmvdev/MoneroVMiner/releases

Thanks

here's my clinfo output

`clinfo
Number of platforms 2
Platform Name Clover
Platform Vendor Mesa
Platform Version OpenCL 1.1 Mesa 19.2.6
Platform Profile FULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions function suffix MESA

Platform Name Portable Computing Language
Platform Vendor The pocl project
Platform Version OpenCL 1.2 pocl 1.3 None+Asserts, LLVM 8.0.1, SLEEF, DISTRO, POCL_DEBUG
Platform Profile FULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions function suffix POCL

Platform Name Clover
Number of devices 1
Device Name AMD PITCAIRN (DRM 2.50.0, 5.4.0-2parrot1-amd64, LLVM 9.0.0)
Device Vendor AMD
Device Vendor ID 0x1002
Device Version OpenCL 1.1 Mesa 19.2.6
Driver Version 19.2.6
Device OpenCL C Version OpenCL C 1.1
Device Type GPU
Device Profile FULL_PROFILE
Device Available Yes
Compiler Available Yes
Max compute units 16
Max clock frequency 985MHz
Max work item dimensions 3
Max work item sizes 256x256x256
Max work group size 256
Preferred work group size multiple 64
Preferred / native vector sizes
char 16 / 16
short 8 / 8
int 4 / 4
long 2 / 2
half 8 / 8 (cl_khr_fp16)
float 4 / 4
double 2 / 2 (cl_khr_fp64)
Half-precision Floating-point support (cl_khr_fp16)
Denormals No
Infinity and NANs Yes
Round to nearest Yes
Round to zero No
Round to infinity No
IEEE754-2008 fused multiply-add No
Support is emulated in software No
Single-precision Floating-point support (core)
Denormals No
Infinity and NANs Yes
Round to nearest Yes
Round to zero No
Round to infinity No
IEEE754-2008 fused multiply-add No
Support is emulated in software No
Correctly-rounded divide and sqrt operations No
Double-precision Floating-point support (cl_khr_fp64)
Denormals Yes
Infinity and NANs Yes
Round to nearest Yes
Round to zero Yes
Round to infinity Yes
IEEE754-2008 fused multiply-add Yes
Support is emulated in software No
Address bits 64, Little-Endian
Global memory size 4294967296 (4GiB)
Error Correction support No
Max memory allocation 3006477107 (2.8GiB)
Unified memory for Host and Device No
Minimum alignment for any data type 128 bytes
Alignment of base address 32768 bits (4096 bytes)
Global Memory cache type None
Image support No
Local memory type Local
Local memory size 32768 (32KiB)
Max number of constant args 16
Max constant buffer size 2147483647 (2GiB)
Max size of kernel argument 1024
Queue properties
Out-of-order execution No
Profiling Yes
Profiling timer resolution 0ns
Execution capabilities
Run OpenCL kernels Yes
Run native kernels No
Device Extensions cl_khr_byte_addressable_store cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_fp64 cl_khr_fp16

Platform Name Portable Computing Language
Number of devices 1
Device Name pthread-AMD Phenom(tm) II X6 1055T Processor
Device Vendor AuthenticAMD
Device Vendor ID 0x6c636f70
Device Version OpenCL 1.2 pocl HSTR: pthread-x86_64-pc-linux-gnu-amdfam10
Driver Version 1.3
Device OpenCL C Version OpenCL C 1.2 pocl
Device Type CPU
Device Profile FULL_PROFILE
Device Available Yes
Compiler Available Yes
Linker Available Yes
Max compute units 6
Max clock frequency 2800MHz
Device Partition (core)
Max number of sub-devices 6
Supported partition types equally, by counts
Supported affinity domains (n/a)
Max work item dimensions 3
Max work item sizes 4096x4096x4096
Max work group size 4096
Preferred work group size multiple 8
Preferred / native vector sizes
char 16 / 16
short 8 / 8
int 4 / 4
long 2 / 2
half 0 / 0 (n/a)
float 4 / 4
double 2 / 2 (cl_khr_fp64)
Half-precision Floating-point support (n/a)
Single-precision Floating-point support (core)
Denormals Yes
Infinity and NANs Yes
Round to nearest Yes
Round to zero Yes
Round to infinity Yes
IEEE754-2008 fused multiply-add No
Support is emulated in software No
Correctly-rounded divide and sqrt operations Yes
Double-precision Floating-point support (cl_khr_fp64)
Denormals Yes
Infinity and NANs Yes
Round to nearest Yes
Round to zero Yes
Round to infinity Yes
IEEE754-2008 fused multiply-add Yes
Support is emulated in software No
Address bits 64, Little-Endian
Global memory size 3071966208 (2.861GiB)
Error Correction support No
Max memory allocation 1073741824 (1024MiB)
Unified memory for Host and Device Yes
Minimum alignment for any data type 128 bytes
Alignment of base address 1024 bits (128 bytes)
Global Memory cache type Read/Write
Global Memory cache size 6291456 (6MiB)
Global Memory cache line size 64 bytes
Image support Yes
Max number of samplers per kernel 16
Max size for 1D images from buffer 67108864 pixels
Max 1D or 2D image array size 2048 images
Max 2D image size 8192x8192 pixels
Max 3D image size 2048x2048x2048 pixels
Max number of read image args 128
Max number of write image args 128
Local memory type Global
Local memory size 4194304 (4MiB)
Max number of constant args 8
Max constant buffer size 4194304 (4MiB)
Max size of kernel argument 1024
Queue properties
Out-of-order execution No
Profiling Yes
Prefer user sync for interop Yes
Profiling timer resolution 1ns
Execution capabilities
Run OpenCL kernels Yes
Run native kernels Yes
printf() buffer size 16777216 (16MiB)
Built-in kernels (n/a)
Device Extensions cl_khr_byte_addressable_store cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_3d_image_writes cl_khr_fp64 cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_fp64

NULL platform behavior
clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...) Clover
clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...) Success [MESA]
clCreateContext(NULL, ...) [default] Success [MESA]
clCreateContext(NULL, ...) [other] Success [POCL]
clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT) Success (1)
Platform Name Clover
Device Name AMD PITCAIRN (DRM 2.50.0, 5.4.0-2parrot1-amd64, LLVM 9.0.0)
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU) Success (1)
Platform Name Clover
Device Name AMD PITCAIRN (DRM 2.50.0, 5.4.0-2parrot1-amd64, LLVM 9.0.0)
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM) No devices found in platform
clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL) Success (1)
Platform Name Clover
Device Name AMD PITCAIRN (DRM 2.50.0, 5.4.0-2parrot1-amd64, LLVM 9.0.0)

ICD loader properties
ICD loader Name OpenCL ICD Loader
ICD loader Vendor OCL Icd free software
ICD loader Version 2.2.12
ICD loader Profile OpenCL 2.2
`

i need help in getting these kind of cards work ( R9 370 or RX 470/480 )
please help

after sharing 30-40 packages in equihash144 (zergpool) miner gives red and says. "all devfee mining pools are unavailable", and restarts
equihash144.log

cmdline:
miner.exe -a ethash -s solo-etc.2miners.com:5050 -u 0xxxxxx.RIG1 -p x --api 42000 --pec 0 -w 0 --cuda 1 --nvml 0 --opencl 0
rigs are showed as 0 ID worker name, but must be a RIG1, ... etc

Currently Gminer sorts the devices by PCI busID.
Unfortunately the PCI BusID information is not available through the OpenCL API which, as a consequence, breaks proper integration on MultiPoolMiner based software (e.g. MultipoolMiner, Nemos Miner etc.).
Could you please add an option (e.g. --deviceOrder OpenCL) which will allow GMiner to sort the devices based on OpenCL device ID?

OpenCL device order in my case is:

GPU#00 GeForce GTX 1080 Ti
GPU#01 GeForce GTX 1060 6GB
GPU#02 Radeon RX 580 Series (Ellesmere)
GPU#03 AMD Radeon (TM) RX 560 (Baffin)

Gminer now:

miner.exe --list_devices
GPU0: ASUS GeForce GTX 1080 Ti 11GB PCI: 0000:01:00.0
GPU1: MSI GeForce GTX 1060 6GB      PCI: 0000:04:00.0
GPU2: AMD Radeon (TM) RX 560 2GB    PCI: 0000:05:00.0
GPU3: MSI Radeon RX 580 Series 8GB  PCI: 0000:09:00.0

Preferred result:

miner.exe --list_devices --deviceOrder OpenCL
GPU0: ASUS GeForce GTX 1080 Ti 11GB PCI: 0000:01:00.0
GPU1: MSI GeForce GTX 1060 6GB      PCI: 0000:04:00.0
GPU2: MSI Radeon RX 580 Series 8GB  PCI: 0000:09:00.0
GPU3: AMD Radeon (TM) RX 560 2GB    PCI: 0000:05:00.0

After updated Gminer to v1.33, I got lower hashrate compared to Gminer v1.31.
While I can get 8.0 ~ 8.2 G/s for GTX 1080Ti from Gminer v1.31 but
Gminer v1.33 only hashing between 7.7 ~ 7.9 G/s. Same overclock, same card.

please give me a solution to solve it

After I updated NVIDIA drivers to the latest version, I get the following message when I run the miner.

10:39:24 Anti-hacking system detected modification of the miner memory. If you using an antivirus, add miner to antivirus exceptions
10:39:24 Miner terminated, watchdog will restart process after 10 seconds

Tried disabling firewalls in Windows Defender but no success. Also tried Gminer v1.37 and v1.38. Any ideas?

NVIDIA Driver version: 430.39
OS: Microsoft Windows [Version 10.0.17763.437]
CPU: Intel Core i7-7700K
GPU cards: GTX 1080 Ti x1 and GTX 1060 x1

Hello , I am from www.mineros.cn, a miner system, when we run gminer by python shell，Error message "Anti-hacking".
![image](https://user-images.githubusercontent.com/43134488/58308439-30954980-7e34-11e9-936f-0ab774ca5874.png

17:29:05 Anti-hacking system detected modification of the miner memory. If you u sing an antivirus, add miner to antivirus exceptions.
17:29:05 Miner terminated, watchdog will restart process after 10 seconds
17:29:11 MINERSTAT.COM: Package Error. connect ECONNREFUSED 127.0.0.1:3333
17:29:11 (1) POSSILBE REASON => MINER/API NOT STARTED
17:29:11 (2) POSSILBE REASON => TOO MUCH OVERCLOCK / UNDERVOLT
17:29:11 (3) POSSILBE REASON => BAD CONFIG -> (1) MINER NOT STARTED [nvidia] Hardware Monitor: {"0":"GeForce GTX 1070, 36, 70 %, 11.00 W, 139 MHz, 4 05 MHz, 0 %, 00000000:01:00.0","1":"GeForce GTX 1070, 35, 70 %, 8.33 W, 139 MHz, 405 MHz, 0 %, 00000000:02:00.0","2":"GeForce GTX 1070, 36, 70 %, 11.32 W, 139 M Hz, 405 MHz, 0 %, 00000000:03:00.0","3":"GeForce GTX 1070, 36, 70 %, 8.58 W, 139 MHz, 405 MHz, 0 %, 00000000:04:00.0","4":"GeForce GTX 1070, 36, 70 %

Hello.

Is it possible to have a "classic" TCP API connection to read miner stats, hashrate, for example? Claymore miner style, JSON, or anything? This miner only has http interface and it's updated dynamically, I can't read anything from that...

thank you.

Many thanks to the creator of this great miner, I'm using it on 1080 Ti/1080/1070 and it delivers the best hashrate among any other miners. I've tried but I miss one feature: failover pools in pools.txt file

I will say it seems a little less forgiving of poor network conditions (high ping times, flaky wifi, etc.) and it would be really nice to have failover for pools

it would be really nice to have failover for pools in pools.txt file (Like Claymore's Miner)

Mining 150_5, GRIMM coin, on same rig, same overclocking settings, same pool Gminer v1.55 mines stable for days, but Gminer v1.56 crashes after a handful of found shares with "Illegal memory access".

It would be inconIt would be inconvenient to hope to increase the mining intensity.venient to hope to increase the mining intensity.

about a 5-10% performance degradation on equihash 144_5 and 192_7 since v1.39 on Linux (HiveOS). Same OC and PL as v1.38.

Is there a recommended change in OC or Config statement after 1.38 to achieve higher hash?

Seems like new version has decreased hashrate for beam on nvidia instead of increasing...
Here is hashrate before and after update (updated at 8:40). It is now lower on 5% or so...