|
0.31f is brilliant! got my 8 vega 56 to 15.06k h/s; slightly besting srbminer.
FWIW the max multi_hash setting that could be used is 1872. Anymore and i would get random thread failures after compilation
|
|
|
|
Initialize diagnostics (10)
Starting Diagnostics. Awesome Miner Remote Agent version: 5.3.1
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: JceCpuMiner, Auto Download: False, EnginePath: C:\miners\jce_cn_gpu_miner.prototype.031d\jce_cn_gpu_miner64.exe, Subtype: Disabled, CustomExecutable:
C:\miners\jce_cn_gpu_miner.prototype.031d\jce_cn_gpu_miner64.exe --no-cpu --variation 3 -o stratum+tcp://cryptonightv7.usa.nicehash.com:3363 -u 33ACrF8FUvFnBGGPRP1q6URLxxxxxzpZ.Miner08 -p x --auto --any --forever --low --mport 4028 (WindowMode: ConsoleFormat, EngineType: JceCpuMiner, IsProfitMiner: True)
Configuration:
Configured command line:
--no-cpu
Mining Engine Process started, PID: 2116
====================================================================================================
>
> +------------------------------------------+
> | JC Expert Cryptonote CPU+GPU Miner 0.31d |
> +------------------------------------------+
>
>
> For Windows 64-bits
> Detecting OpenCL-capable GPUs...
> Found GPU 0, with:
> Vendor: Unknown
> Processor: Intel(R) UHD Graphics 610
> Device: ff:ff
> Compute-Units: 12
> Cache Memory: 256 KB
> Local Memory: 64 KB
> Global Memory: 1589 MB
> Addressing: 64-bits
> Found GPU 1, with:
> Vendor: AMD
> Processor: gfx900
> Device: 06:00
> Compute-Units: 56
> Cache Memory: 16 KB
> Local Memory: 32 KB
> Global Memory: 8176 MB
> Addressing: 64-bits
> Found GPU 2, with:
> Vendor: AMD
> Processor: gfx900
> Device: 1c:00
> Compute-Units: 56
> Cache Memory: 16 KB
> Local Memory: 32 KB
> Global Memory: 8176 MB
> Addressing: 64-bits
> Found GPU 3, with:
> Vendor: AMD
> Processor: gfx900
> Device: 03:00
> Compute-Units: 56
> Cache Memory: 16 KB
> Local Memory: 32 KB
> Global Memory: 8176 MB
> Addressing: 64-bits
> Found GPU 4, with:
> Vendor: AMD
> Processor: gfx900
> Device: 19:00
> Compute-Units: 56
> Cache Memory: 16 KB
> Local Memory: 32 KB
> Global Memory: 8176 MB
> Addressing: 64-bits
> Found GPU 5, with:
> Vendor: AMD
> Processor: gfx900
> Device: 12:00
> Compute-Units: 56
> Cache Memory: 16 KB
> Local Memory: 32 KB
> Global Memory: 8176 MB
> Addressing: 64-bits
> Found GPU 6, with:
> Vendor: AMD
> Processor: gfx900
> Device: 16:00
> Compute-Units: 64
> Cache Memory: 16 KB
> Local Memory: 32 KB
> Global Memory: 8176 MB
> Addressing: 64-bits
> Found GPU 7, with:
> Vendor: AMD
> Processor: gfx900
> Device: 0f:00
> Compute-Units: 56
> Cache Memory: 16 KB
> Local Memory: 32 KB
> Global Memory: 8176 MB
> Addressing: 64-bits
> Found GPU 8, with:
> Vendor: AMD
> Processor: gfx900
> Device: 0b:00
> Compute-Units: 56
> Cache Memory: 16 KB
> Local Memory: 32 KB
> Global Memory: 8176 MB
> Addressing: 64-bits
>
> HTTP Local Server on port 4028
>
> Preparing 18 Mining Threads...
>
> +-- Thread 0 config -----------------------+
> | Run on GPU: 0 |
> | Multi-hash: 335 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 1 config -----------------------+
> | Run on GPU: 0 |
> | Multi-hash: 335 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 2 config -----------------------+
> | Run on GPU: 1 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 3 config -----------------------+
> | Run on GPU: 1 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 4 config -----------------------+
> | Run on GPU: 2 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 5 config -----------------------+
> | Run on GPU: 2 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 6 config -----------------------+
> | Run on GPU: 3 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 7 config -----------------------+
> | Run on GPU: 3 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 8 config -----------------------+
> | Run on GPU: 4 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 9 config -----------------------+
> | Run on GPU: 4 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 10 config ----------------------+
> | Run on GPU: 5 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 11 config ----------------------+
> | Run on GPU: 5 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 12 config ----------------------+
> | Run on GPU: 6 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 13 config ----------------------+
> | Run on GPU: 6 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 14 config ----------------------+
> | Run on GPU: 7 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 15 config ----------------------+
> | Run on GPU: 7 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 16 config ----------------------+
> | Run on GPU: 8 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> +-- Thread 17 config ----------------------+
> | Run on GPU: 8 |
> | Multi-hash: 1724 |
> | Worksize: 8 |
> | Factor Alpha 0 |
> | Factor Beta 0 |
> | Factor Gamma 4 |
> | Factor Delta 4 |
> | Factor Epsilon 4 |
> | Factor Zeta 4 |
> +------------------------------------------+
>
> Cryptonight Variation: Cryptonight V7 fork of April-2018
>
> Low intensity.
> Nicehash mining detected, auto-enabling Nicehash mode.
>
> Starting GPU Mining thread 0, on GPU 0
> Created OpenCL Context for GPU 0 at 0000020729cb5f10
> Created OpenCL Thread 0 Command-Queue for GPU 0 at 0000020728ee2210
> Allocating big 670MB scratchpad for OpenCL Thread 0...
> Scratchpad Allocation success for OpenCL Thread 0
> Compiling kernels of OpenCL Thread 0, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 1, on GPU 0
> Created OpenCL Thread 1 Command-Queue for GPU 0 at 0000020729f16450
> Allocating big 670MB scratchpad for OpenCL Thread 1...
> Scratchpad Allocation success for OpenCL Thread 1
> Compiling kernels of OpenCL Thread 1, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 2, on GPU 1
> Created OpenCL Context for GPU 1 at 0000020729cb6070
> Created OpenCL Thread 2 Command-Queue for GPU 1 at 0000020729f165a0
> Allocating big 3448MB scratchpad for OpenCL Thread 2...
> Scratchpad Allocation success for OpenCL Thread 2
> Compiling kernels of OpenCL Thread 2, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 3, on GPU 1
> Created OpenCL Thread 3 Command-Queue for GPU 1 at 0000020729f166f0
> Allocating big 3448MB scratchpad for OpenCL Thread 3...
> Scratchpad Allocation success for OpenCL Thread 3
> Compiling kernels of OpenCL Thread 3, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 4, on GPU 2
> Created OpenCL Context for GPU 2 at 0000020729cb6b70
> Created OpenCL Thread 4 Command-Queue for GPU 2 at 0000020729f16ed0
> Allocating big 3448MB scratchpad for OpenCL Thread 4...
> Scratchpad Allocation success for OpenCL Thread 4
> Compiling kernels of OpenCL Thread 4, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 5, on GPU 2
> Created OpenCL Thread 5 Command-Queue for GPU 2 at 0000020729f16d80
> Allocating big 3448MB scratchpad for OpenCL Thread 5...
> Scratchpad Allocation success for OpenCL Thread 5
> Compiling kernels of OpenCL Thread 5, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 6, on GPU 3
> Created OpenCL Context for GPU 3 at 0000020729cb6a10
> Created OpenCL Thread 6 Command-Queue for GPU 3 at 000002072a466630
> Allocating big 3448MB scratchpad for OpenCL Thread 6...
> Scratchpad Allocation success for OpenCL Thread 6
> Compiling kernels of OpenCL Thread 6, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 7, on GPU 3
> Created OpenCL Thread 7 Command-Queue for GPU 3 at 000002072a465e50
> Allocating big 3448MB scratchpad for OpenCL Thread 7...
> Scratchpad Allocation success for OpenCL Thread 7
> Compiling kernels of OpenCL Thread 7, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 8, on GPU 4
> Created OpenCL Context for GPU 4 at 000002072a00d620
> Created OpenCL Thread 8 Command-Queue for GPU 4 at 000002072a465bb0
> Allocating big 3448MB scratchpad for OpenCL Thread 8...
> Scratchpad Allocation success for OpenCL Thread 8
> Compiling kernels of OpenCL Thread 8, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 9, on GPU 4
> Created OpenCL Thread 9 Command-Queue for GPU 4 at 000002072a466f60
> Allocating big 3448MB scratchpad for OpenCL Thread 9...
> Scratchpad Allocation success for OpenCL Thread 9
> Compiling kernels of OpenCL Thread 9, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 10, on GPU 5
> Created OpenCL Context for GPU 5 at 000002072a00d360
> Created OpenCL Thread 10 Command-Queue for GPU 5 at 000002072a465d00
> Allocating big 3448MB scratchpad for OpenCL Thread 10...
> Scratchpad Allocation success for OpenCL Thread 10
> Compiling kernels of OpenCL Thread 10, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 11, on GPU 5
> Created OpenCL Thread 11 Command-Queue for GPU 5 at 000002072a466390
> Allocating big 3448MB scratchpad for OpenCL Thread 11...
> Scratchpad Allocation success for OpenCL Thread 11
> Compiling kernels of OpenCL Thread 11, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 12, on GPU 6
> Created OpenCL Context for GPU 6 at 000002072a00e120
> Created OpenCL Thread 12 Command-Queue for GPU 6 at 000002072a4679e0
> Allocating big 3448MB scratchpad for OpenCL Thread 12...
> Scratchpad Allocation success for OpenCL Thread 12
> Compiling kernels of OpenCL Thread 12, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 13, on GPU 6
> Created OpenCL Thread 13 Command-Queue for GPU 6 at 000002072a467200
> Allocating big 3448MB scratchpad for OpenCL Thread 13...
> Scratchpad Allocation success for OpenCL Thread 13
> Compiling kernels of OpenCL Thread 13, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 14, on GPU 7
> Created OpenCL Context for GPU 7 at 000002072a00dd00
> Created OpenCL Thread 14 Command-Queue for GPU 7 at 000002072a4674a0
> Allocating big 3448MB scratchpad for OpenCL Thread 14...
> Scratchpad Allocation success for OpenCL Thread 14
> Compiling kernels of OpenCL Thread 14, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 15, on GPU 7
> Created OpenCL Thread 15 Command-Queue for GPU 7 at 000002072a467890
> Allocating big 3448MB scratchpad for OpenCL Thread 15...
> Scratchpad Allocation success for OpenCL Thread 15
> Compiling kernels of OpenCL Thread 15, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 16, on GPU 8
> Created OpenCL Context for GPU 8 at 0000020755205e30
> Created OpenCL Thread 16 Command-Queue for GPU 8 at 0000020754bdf780
> Allocating big 3448MB scratchpad for OpenCL Thread 16...
> Scratchpad Allocation success for OpenCL Thread 16
> Compiling kernels of OpenCL Thread 16, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
>
> Starting GPU Mining thread 17, on GPU 8
> Created OpenCL Thread 17 Command-Queue for GPU 8 at 0000020754be0350
> Allocating big 3448MB scratchpad for OpenCL Thread 17...
> Scratchpad Allocation success for OpenCL Thread 17
> Compiling kernels of OpenCL Thread 17, it will be long...
> Compilation of OpenCL kernels failed.
> Error: CL_BUILD_PROGRAM_FAILURE Code: s-1035.16
> GPU Devfee is 0.9%
>
> 09:39:38 | OpenCL Thread 16 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 16
> 09:39:38 | Released OpenCL Thread 16 Scratchpad at 00000207550b1790
> 09:39:38 | OpenCL Thread 5 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 5
> 09:39:38 | Released OpenCL Thread 5 Scratchpad at 00000207547ec8b0
> 09:39:38 | OpenCL Thread 12 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 12
> 09:39:38 | Released OpenCL Thread 12 Scratchpad at 0000020754d68500
> 09:39:38 | OpenCL Thread 8 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 8
> 09:39:38 | Released OpenCL Thread 8 Scratchpad at 000002072a2c3310
> 09:39:38 | OpenCL Thread 14 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 14
> 09:39:38 | Released OpenCL Thread 14 Scratchpad at 0000020754cb2ef0
> 09:39:38 | OpenCL Thread 17 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 17
> 09:39:38 | Released OpenCL Thread 17 Scratchpad at 00000207550b3590
> 09:39:38 | OpenCL Thread 4 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 4
> 09:39:38 | Released OpenCL Thread 4 Scratchpad at 00000207299fdb60
> 09:39:38 | OpenCL Thread 6 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 6
> 09:39:38 | Released OpenCL Thread 6 Scratchpad at 000002072a03fe00
> 09:39:38 | Nicehash Mining session starts!
>
> During mining time, press:
> h display hashrate for each mining thread.
> r display full report.
> p pause all.
> u pause CPUs.
> 0-F pause GPU 0-15.
> q quit.
>
> 09:39:38 | GPU Compute allocation starts at 80% and reaches 100% after 5min
> 09:39:38 | Let the miner warm-up if you're tuning for performance.
> 09:39:38 | OpenCL Thread 0 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 0
> 09:39:38 | OpenCL Thread 15 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 15
> 09:39:38 | Released OpenCL Thread 15 Scratchpad at 0000020754cb82f0
> 09:39:38 | OpenCL Thread 10 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 10
> 09:39:38 | Released OpenCL Thread 10 Scratchpad at 0000020729fff0c0
> 09:39:38 | OpenCL Thread 1 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 1
> 09:39:38 | OpenCL Thread 11 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 11
> 09:39:38 | Released OpenCL Thread 11 Scratchpad at 0000020754d6a900
> 09:39:38 | OpenCL Thread 9 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 9
> 09:39:38 | Released OpenCL Thread 9 Scratchpad at 0000020754743e30
> 09:39:38 | OpenCL Thread 3 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 3
> 09:39:38 | Released OpenCL Thread 3 Scratchpad at 000002072a4ad4f0
> 09:39:38 | OpenCL Thread 7 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 7
> 09:39:38 | Released OpenCL Thread 7 Scratchpad at 000002072a0acf00
> 09:39:38 | OpenCL Thread 2 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 2
> 09:39:38 | Released OpenCL Thread 2 Scratchpad at 0000020729eff2e0
> 09:39:38 | OpenCL Thread 13 failed, Stop.
> 09:39:38 | Unloaded OpenCL kernels of GPU Thread 13
> 09:39:38 | Released OpenCL Thread 13 Scratchpad at 0000020754d6b200
> 09:39:38 | Connecting to mining pool cryptonightv7.usa.nicehash.com:3363 ...
> 09:39:38 | Released OpenCL Thread 0 Scratchpad at 0000020728f9d650
> 09:39:38 | Released OpenCL Thread 0 Command-Queue of GPU 0 at 0000020728ee2210
> 09:39:38 | Released OpenCL Thread 1 Scratchpad at 0000020728f9c4d0
> 09:39:38 | Released OpenCL Thread 1 Command-Queue of GPU 0 at 0000020729f16450
> 09:39:38 | Released OpenCL Thread 16 Command-Queue of GPU 8 at 0000020754bdf780
> 09:39:38 | Released OpenCL Thread 8 Command-Queue of GPU 4 at 000002072a465bb0
> 09:39:38 | Released OpenCL Thread 12 Command-Queue of GPU 6 at 000002072a4679e0
> 09:39:38 | Released OpenCL Thread 10 Command-Queue of GPU 5 at 000002072a465d00
> 09:39:38 | Released OpenCL Thread 5 Command-Queue of GPU 2 at 0000020729f16d80
> 09:39:38 | Released OpenCL Thread 6 Command-Queue of GPU 3 at 000002072a466630
> 09:39:38 | Released OpenCL Thread 3 Command-Queue of GPU 1 at 0000020729f166f0
> 09:39:38 | Released OpenCL Thread 14 Command-Queue of GPU 7 at 000002072a4674a0
> 09:39:38 | Released OpenCL Thread 7 Command-Queue of GPU 3 at 000002072a465e50
> 09:39:38 | Released OpenCL Thread 13 Command-Queue of GPU 6 at 000002072a467200
> 09:39:38 | Released OpenCL Thread 4 Command-Queue of GPU 2 at 0000020729f16ed0
> 09:39:38 | Released OpenCL Thread 9 Command-Queue of GPU 4 at 000002072a466f60
> 09:39:38 | Released OpenCL Thread 15 Command-Queue of GPU 7 at 000002072a467890
> 09:39:38 | Released OpenCL Thread 17 Command-Queue of GPU 8 at 0000020754be0350
> 09:39:38 | Released OpenCL Thread 2 Command-Queue of GPU 1 at 0000020729f165a0
> 09:39:38 | Released OpenCL Thread 11 Command-Queue of GPU 5 at 000002072a466390
> 09:39:38 | Released OpenCL Context 000002072a00d360 of GPU 5
> 09:39:38 | Released OpenCL Context 0000020755205e30 of GPU 8
> 09:39:38 | Released OpenCL Context 000002072a00d620 of GPU 4
> 09:39:38 | Released OpenCL Context 000002072a00e120 of GPU 6
> 09:39:38 | Released OpenCL Context 0000020729cb6b70 of GPU 2
> 09:39:38 | Released OpenCL Context 0000020729cb6a10 of GPU 3
> 09:39:38 | Released OpenCL Context 0000020729cb5f10 of GPU 0
> 09:39:38 | Released OpenCL Context 0000020729cb6070 of GPU 1
> 09:39:38 | Released OpenCL Context 000002072a00dd00 of GPU 7
> 09:39:38 | Connected to pool. Now logging in...
> 09:39:39 | Successfuly logged as 33ACrF8FUvFnBGGPRP1q6URLEEgqadCzpZ.Miner08
> 09:39:39 | Pool connection socket closed.
> 09:39:39 | Mining thread 0 stopped.
> 09:39:39 | Mining thread 1 stopped.
> 09:39:39 | Mining thread 2 stopped.
> 09:39:39 | Mining thread 3 stopped.
> 09:39:39 | Mining thread 4 stopped.
> 09:39:39 | Mining thread 5 stopped.
> 09:39:39 | Mining thread 6 stopped.
> 09:39:39 | Mining thread 7 stopped.
> 09:39:39 | Mining thread 8 stopped.
> 09:39:39 | Mining thread 9 stopped.
> 09:39:39 | Mining thread 10 stopped.
> 09:39:39 | Mining thread 11 stopped.
> 09:39:39 | Mining thread 12 stopped.
> 09:39:39 | Mining thread 13 stopped.
> 09:39:39 | Mining thread 14 stopped.
> 09:39:39 | Mining thread 15 stopped.
> 09:39:39 | Mining thread 16 stopped.
> 09:39:39 | Mining thread 17 stopped.
====================================================================================================
Unexpected exit of mining software. Possible cause: Incorrect configuration
Diagnostics completed
0.31d failing on my 8x vega rig any ideas? |
|
|
|
Hi,
I've just started dabbling with a baikal x10 and awesomeminer. I've setup the api port and such and can see what it is mining and the hashrate, but it is not able to do any profit switching.
Would appreciate it if someone could give me some pointers. Thanks!
Add all the pools/algorithms to your miner itself, even if its 30+ entries, and make sure every one of them is listed in the online services. (All the default pools Awesome miner uses should be listed if enabled globally) If they aren't, add them as user defined online services. Create a profit profile for the miner. Add all the algorithms the X10 uses, deselect any others. Don't select any mining software. Look up how much power the X10 uses on each algorithm, and respective hashrate, and add it in (use custom) you'll make a little bit more that way. That's pretty much all you need to get started. Have fun, and good luck! Thanks! I've done all those, but the bk-x is only mining the nicehash algos (even though awesomeminer says other pools are more profitable). I assume this is because i have not disabled the "nicehashsma" option? |
|
|
|
|
Hi,
I've just started dabbling with a baikal x10 and awesomeminer. I've setup the api port and such and can see what it is mining and the hashrate, but it is not able to do any profit switching.
Would appreciate it if someone could give me some pointers. Thanks!
|
|
|
|
UPDATE.
1. VERGE clearnet version was installed to reduce amount of orphans blocks found. It is safe to mine with less orphans now.
Hopefully it will improve accuracy as well!
Does it mean that orphan rate is not included in profit prediction? This would explain a lot, as suggested before. Hope clearnet helps, because these orphans are anoying. However, I thought that ist due to relatively low hashrate in comparison to whole network, am I wrong? I think wrong estimates were caused by worsen connectivity via darknet, hence orphans, hence lower end result. Now have fixed it, see it is much better already for last blocks in x17 Verge. The issue is not fixed at all. There are 10 Orphan blocks on zergpool for the past 10 hours and each block is found every 45 minutes and this means a loss of 10% caused by orphan blocks and because of the terrible "DARKNET" network you are using. Because you actually pay 30% less and 10% of the loss is caused by orphans it means you are stealing the rest of 20% from miners. Miners should be aware that advertised 0,5% is a scam because you are located in Russia and using DARKNET to hide you is actually hurting mining process but you want to be hidden and untraceable because of the DARK-ACTIVITY you are doing by stealing. AHashPoll does not have orphan blocks like you and because they are not hackers like you and they are not stealing from miners like you do, because you pay 30% less and this is shown in Awesome Miner. Even so, ahashpool is also paying 30% less for x17 |
|
|
|
Zerg Pool is a complete scam. I mined afor 24 hours using multi-algos with 12 GTX 1080s and got 0.00005 btc. All the while my miner said I was cranking out between 300-400 MH/s on Lyra2v2. I was mining on Verge today using Zerg Pool when it was 10 times more than all the other coins and I made less in 12 hours than I did in 2 hours using zpool. Don’t fall for 0.5% fee gimmick and go to a better pool.
Now Awesome Miner just introduced a feature from Options-> "Statistics" called "Adjust reported revenue for actual payout performance". After you enable that feature you will notice that for many algos zergpool is at 60%-70% payout compared to advertised. You will find for the same algo much better payout for other pools. When you compare using Awesome Miner zergpool payout of 70% for the same algo from other pools and you see that other pools pay 90% of the amount they advertise, you will very easy understand that it is somehow better pay 1% pool fee than being scamed and have 30% being stolen from you by zergpool and advertising it as 0% fee when it is actually 30% fee. Do some tests with real BTC wallets and you will see that is is not fair to have 30% of your revenue stolen from you. no one is forcing you to mine at zergpool, so it is not right to say it is not fair. Yes the payout for x17 at zergpool is hovering around 70%, but that is comparable to ahashpool's x17 payout. zpool's x17 started at around 88% for me and it has steadily dropped to 83% over the course of a few days. You have also conveniently not included the fact that x16r on zergpool has an actual pay out of 92.71% and xevan is at 98.53%. |
|
|
|
I've been testing the version 3 yesterday and I have an issue to report. It might be something I overlooked because of the new design, but let me start by explaining how I work the version 2 atm.
I have 2 different kinds of cards on my rig, so each kind of card is more profitable in different algos. Because of that, I don't want to run an average of all my cards on every algo and instead I've made 2 folders of NemosMiner, each folder with different data inside the "stats" folder and I run 2 instances at the same time, one for each group of cards.
At first the benchmark would get confused when two ccminers were running and it'd update the hashrate incorrectly. In order to fix that, I run the benchmark on the 1st group and then turned the "*HashRate.txt" files into read-only. I then benchmarked the 2nd group of cards and again locked their hashrate files into read-only. Since then, running 2 instances at the same time works like charm, the only drawback is that the hashrates are not being updated automatically but if you don't change anything in your system, the hashrate rarely changes because of an updated miner... and of course you can just run the benchmark again!
I believe the above trick would help people with more cards than the miner can handle? Maybe?
Anyway to be honest I posted the above long explanation in case someone wants to try it, the issue I have with version 3 with the above setup is pretty simple... I can't setup specific cards for each instance OR I'm doing it wrong and there's no documentary to help me!
You could setup if you switch to manual edition of the config files. However, NPlusMiner now supports running multiple instances. I guess that might ease your life  https://github.com/MrPlusGH/NPlusMiner/releasesMultiple instances doesn't fully work for me. If i start the second after the first instance is running, the second instance would close the miner for the first instance until the sleep cycle is over. Also if i do not make the hashrate files read-only, there is a chance that it will get overwritten. What i have done for now is to benchmark separately, making the hash-rate files read-only, then starting both instances simultaneously. The other thing i noticed is, and i'm not sure if its a bug, is i have about 10 different instances running at the same time. All 10 would have different btc/gh/day values. The difference is about a couple of percent, but this means on the same rig with the same cards, i would have two instances mining different algos. Is this normal? |
|
|
|
just installed it and love the new features! Would it be possible to put in an actual BTC/day column in the balance page? Awesome Miner version 4.5
- Pool Balance to display unpaid balance and recent payouts for the mining pools supported by the profit switcher
- New pool for Managed Profit Switcher and profitability information: Zergpool
- New pool for Managed Profit Switcher and profitability information: Mining Dutch
- New pool for profitability information: D3pool
- New mining software support: Bminer for Equihash
- New mining software support: PhoenixMiner for Ethereum
- New mining software support: Claymore NeoScrypt AMD Miner for Neoscrypt
- Awesome Miner HTTP API for adding, updating and removing user defined coins with profit information
- Awesome Miner HTTP API for adding, updating and removing pools
- Avalon 8 ASIC support
- Performance improvements to the Options dialog
- Added CORS support for built-in web server
- New rule action to apply a Profit Profile to a miner
- Support for wallet balance for Verge and Digibyte
- Coin exchange rates in the status bar will always use the current exchange rate, independent from the coin statistics settings in the Options dialog
- Czech Koruna added as display currency
- Notification messages related to mining software crashes includes information about mining software and algorithm to improve troubleshooting
- Updated WhatToMine integration, to adjust to their latest change of Myriad-Groestl algorithm naming
- Ccminer KlausT 8.20 added
- CastXMR 0.8.5
- DSTM ZCash miner 0.6
- CpuMiner-Opt 3.8.2.1
- Corrections to the profit switcher to correctly ignore dual mining algorithms if disabled in the profit profile and to reload settings correctly when the restart operation is performed
- Minor corrections
|
|
|
|
Have anybody tested latest version with GTX 980 and 980 Ti ?
not working with my 980ti |
|
|
|
I have the same problem with 2.5 - the pool mbtc/gh/day values does not change. Ran it overnight and the values were still the same |
|
|
|
|
Hi,
Would it be possible to get excavator added? Thanks!
|
|
|
|
|
I have been checking out awesomeminer and like what i see.
However, the implementation for Excavator is not optimal. For all the supported excavator algos, except neoscrypt, excavator should run with two threads. The current implementation only runs with one thread leading to lower than optimal hashrates.
Is there a way for me to edit the way awesomeminer generates the .json file for excavator?
|
|
|
|
so this is the continuation of that graph (starting points are where the other one ended)  So after a little more than 24 hours, I can tell that ahashpool is still the most profitable, but the differences aren't as great as I thought. We now see some small drops on ahash as well, I think those are caused by actual exchange rates not being as high as I initially predicted, and these should probably not apear when mining with no autoexchange. About comparing estimated vs actual profit, that is a bit harder to do because it has to factor in your hashrate. While MegaMiner does this, it just shows instant estimated income, and it doesn't log anything. For me to include it in the tool I've made, I'll need to interface with ccminer as well, and use its api, it's a lot more work. Awesome thanks! Saves me the trouble of comparing the pools. Could i trouble you to drop hash refinery and compare ahashpool and nicehash? I'm sure a lot of people would love to know. I tried compiling your poolapitocsv but i got errors (i must admit i can't code or use the computer to save my life  ) else i would have done it BTW, Could megaminer implement this function (logging wallet total to csv)? |
|
|
|
Why Removed delay close miner option ??
I was very happy with this option.
I even set this to 40 sec, to insure no downtime on switching.
And it's work very well!
too unstable can we have a switch to enable this for those who didn't have instability? I agree this is/was an awesome function Also, could the stats update function be modified to not accept new values outside of a range? Sometimes i don't get enough shares for the proper hashrate to be updated, causing the stats file to have abnormally low value. Perhaps values outside of 10% will be considered abnormal, and not be updated to the benchmark file? |
|
|
|
|
Finally got it working.
You are right, default bios is all that is needed.
I cleared the cmos, reinstalled windows and started plugging in my cards (without installing nvidia drivers yet) one at a time
Found one faulty riser card instantly (riser got too hot to touch, mosfet failure probably).
Replaced another riser that was causing a card to be working intermittently.
5 gpus working now; 2x1080ti, 2x1070ti and 1x1070. Going to call it a day with this rig until volta comes along
|
|
|
|
Bought another gpu, so rearranged the existing gpus to fit, and changed the slots. Now only 3 cards are detectable. 4th one if detected throws up a code 43 error  hackflags, uninstalling using ddu, swapping cards, resetting bios, adjust bios settings to no avail. Going to try reinstalling windows now I hope the asus z270-a board for my 2nd rig isn't going to be such a pita |
|
|
|
hi Guys,
Today,
I tried to clean installation again on this MOBO. (BIOS 1.20, Using default settings)
The successful procedure is below.
1. Using "Media Creation Tool", prepare the latest USB installation media. (Version 1709)
2. Install the OS without connecting to the network.
3. Please still be offline after installation. Make sure that all of your GPUs are visible in Device Manager. (The NVIDIA driver has not been installed yet.)
4. Disable all HD audio devices. (Optionally, set HackFlags and reboot.)
5. Connect to the network. Install the driver automatically in device manager, or install Nvidia genuine. (Keep all HD audio devices disabled even after driver installation.)
6. If HackFlags does not set and Code12 still indicated, try HackFlags and reboot.
But I do not know if this is effective with AMD's GPU.
Can anyone verify it.
ty
Followed your steps to the T with th exception of installing 1703 and all 4 gpus were detected. I also did not install the intel graphics driver and have left the pci-e 16x slot vacant. I have a feeling i am going to have troubles when my fifth and sixth card arrives. Will probably need to disable the igpu but this would be troublesome as the cards are inside a server case. But we will cross that bridge when i get ther 😬 Thanks so much for taking the time to write it all down! |
|
|
|
|
been testing 5.1 all day today and everything seems great!
no errors or crashes yet. *fingers crossed*
|
|
|
|
I'm testing the master-copy on github and it seems to be working.
btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?
Switching threshold will be in next release, I wnat to close 5.0 stable release before. What is Auto speed updating? Auto speed updating is updating hashrate stat files while in mining process , either implement second value or simply overwrite initial profiling value periodically. Inital profiling isnt particulary accurate , it shaves off quite some margin using 200 sec profiling. So when profiling rig i have to manually enter actual values and usualy thos are quite a bit higher , than written after profiling period. yes and don't update (give an error message) if the hash rate is outside of the tolerance |
|
|
|
|
I'm testing the master-copy on github and it seems to be working.
btw would it be possible to add back the auto speed updating feature found in the original MPM?
Also would it be possible to set a profit switching threshold (in %)?
|
|
|
|
|
Show Posts
