Search content
Sort by
Showing 20 of 36 results by MikeGR7
Re: PhoenixMiner 3.0c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Hi guys,
My Windows got updated automatically
I have updated AMD drivers to 18.5.1
Please help!!!
Have been getting this error -
My Windows got updated automatically
I have updated AMD drivers to 18.5.1
Please help!!!
Have been getting this error -
Code:
17734:13:29:53.886: main Phoneix Miner 2.8c Windows/msvc - Release
17734:13:29:53.886: main Cmd line: -epool asia1.ethermine.org:4444 -ewal 0xC34CA9A45F4db78e979F5D803d2a9B457824bCF3.axe -epsw x -mode 1 -ftime 10 -wd 0
17734:13:29:53.886: main The following options are not supported and are ignored:
17734:13:29:53.886: main -mode
17734:13:29:53.887: main No CUDA driver found
17734:13:29:56.661: main Available GPUs for mining:
17734:13:29:56.663: main GPU1: Radeon RX 580 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 36 CUs
17734:13:29:56.663: main GPU2: Radeon RX 580 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 36 CUs
17734:13:29:56.663: main GPU3: Radeon RX 580 Series (pcie 4), OpenCL 2.0, 8 GB VRAM, 36 CUs
17734:13:29:56.663: main GPU4: Radeon RX 580 Series (pcie 5), OpenCL 2.0, 4 GB VRAM, 36 CUs
17734:13:29:56.663: main GPU5: Radeon RX 580 Series (pcie 6), OpenCL 2.0, 4 GB VRAM, 36 CUs
17734:13:29:56.663: main GPU6: Radeon RX 580 Series (pcie 7), OpenCL 2.0, 4 GB VRAM, 36 CUs
17734:13:29:56.821: main ADL library initialized
17734:13:29:57.309: main Listening for CDM remote manager at port 3333 in read-only mode
17734:13:29:57.311: main Eth: the pool list contains 3 pools
17734:13:29:57.311: main Eth: primary pool: asia1.ethermine.org:4444
17734:13:29:57.311: main Starting GPU mining
17734:13:29:57.312: main Matched GPU1 to ADL adapter index 64 (method 1)
17734:13:29:57.465: main GPU1: Created ADL monitor for adapter 64; overdrive version: 7
17734:13:29:57.465: main Matched GPU2 to ADL adapter index 0 (method 1)
17734:13:29:57.618: main GPU2: Created ADL monitor for adapter 0; overdrive version: 7
17734:13:29:57.618: main Matched GPU3 to ADL adapter index 80 (method 1)
17734:13:29:57.773: main GPU3: Created ADL monitor for adapter 80; overdrive version: 7
17734:13:29:57.773: main Matched GPU4 to ADL adapter index 48 (method 1)
17734:13:29:57.928: main GPU4: Created ADL monitor for adapter 48; overdrive version: 7
17734:13:29:57.928: main Matched GPU5 to ADL adapter index 16 (method 1)
17734:13:29:58.142: main GPU5: Created ADL monitor for adapter 16; overdrive version: 7
17734:13:29:58.142: main Matched GPU6 to ADL adapter index 32 (method 1)
17734:13:29:58.297: main GPU6: Created ADL monitor for adapter 32; overdrive version: 7
17734:13:29:58.300: main Eth: Connecting to ethash pool asia1.ethermine.org:4444 (proto: EthProxy)
17734:13:29:58.420: eths Eth: Connected to ethash pool asia1.ethermine.org:4444 (54.179.172.226)
17734:13:29:58.420: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0xC34CA9A45F4db78e979F5D803d2a9B457824bCF3.axe","x"]}
17734:13:29:58.517: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
17734:13:29:58.519: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
17734:13:29:58.526: main GPU1: 46C 0%, GPU2: 52C 0%, GPU3: 49C 0%, GPU4: 46C 0%, GPU5: 51C 0%, GPU6: 49C 0%
17734:13:29:58.545: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x575909c317345e81fa3365b667c08332ae4c0f23f98bfb37bdfe11f34a12120e","0x8308d376eeb469b7ff84bd59c51988d9618b208dc3b951d1dc1918fa08306723","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5bafa5"]}
17734:13:29:58.546: eths Eth: New job #575909c3 from asia1.ethermine.org:4444; diff: 4000MH
17734:13:29:58.550: GPU1 GPU1: Starting up... (0)
17734:13:29:58.550: GPU1 Eth: Generating light cache for epoch #200
17734:13:29:58.577: GPU2 GPU2: Starting up... (0)
17734:13:29:58.588: GPU3 GPU3: Starting up... (0)
17734:13:29:58.608: GPU4 GPU4: Starting up... (0)
17734:13:29:58.622: GPU5 GPU5: Starting up... (0)
17734:13:29:58.635: GPU6 GPU6: Starting up... (0)
17734:13:29:58.682: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x575909c317345e81fa3365b667c08332ae4c0f23f98bfb37bdfe11f34a12120e","0x8308d376eeb469b7ff84bd59c51988d9618b208dc3b951d1dc1918fa08306723","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5bafa5"]}
17734:13:30:01.030: GPU1 GPU1: Using new optimized OpenCL kernels (device name 'Ellesmere')
17734:13:30:01.031: GPU1 GPU1: Allocating DAG (2.58) GB; good for epoch up to #202
17734:13:30:01.031: GPU1 GPU1: Allocating light cache buffer (41.2) MB; good for epoch up to #202
17734:13:30:01.134: GPU1 GPU1: Generating DAG for epoch #200
17734:13:30:01.367: GPU2 GPU2: Using new optimized OpenCL kernels (device name 'Ellesmere')
17734:13:30:01.367: GPU2 GPU2: Allocating DAG (2.58) GB; good for epoch up to #202
17734:13:30:01.367: GPU2 GPU2: Allocating light cache buffer (41.2) MB; good for epoch up to #202
17734:13:30:01.470: GPU2 GPU2: Generating DAG for epoch #200
17734:13:30:01.732: GPU3 GPU3: Using new optimized OpenCL kernels (device name 'Ellesmere')
17734:13:30:01.732: GPU3 GPU3: Allocating DAG (2.58) GB; good for epoch up to #202
17734:13:30:01.732: GPU3 GPU3: Allocating light cache buffer (41.2) MB; good for epoch up to #202
17734:13:30:01.834: GPU3 GPU3: Generating DAG for epoch #200
17734:13:30:02.096: GPU4 GPU4: Using new optimized OpenCL kernels (device name 'Ellesmere')
17734:13:30:02.096: GPU4 GPU4: Allocating DAG (2.58) GB; good for epoch up to #202
17734:13:30:02.096: GPU4 GPU4: Allocating light cache buffer (41.2) MB; good for epoch up to #202
17734:13:30:02.198: GPU4 GPU4: Generating DAG for epoch #200
17734:13:30:02.444: GPU5 GPU5: Using new optimized OpenCL kernels (device name 'Ellesmere')
17734:13:30:02.444: GPU5 GPU5: Allocating DAG (2.58) GB; good for epoch up to #202
17734:13:30:02.444: GPU5 GPU5: Allocating light cache buffer (41.2) MB; good for epoch up to #202
17734:13:30:02.561: GPU5 GPU5: Generating DAG for epoch #200
17734:13:30:02.576: GPU5 GPU5: clEnqueueNDRangeKernel (-4)
17734:13:30:02.658: GPU1 GPU1: DAG 19%
17734:13:30:02.796: GPU6 GPU6: Using new optimized OpenCL kernels (device name 'Ellesmere')
17734:13:30:02.796: GPU6 GPU6: Allocating DAG (2.58) GB; good for epoch up to #202
17734:13:30:02.796: GPU6 GPU6: Allocating light cache buffer (41.2) MB; good for epoch up to #202
17734:13:30:02.899: GPU6 GPU6: Generating DAG for epoch #200
17734:13:30:02.901: GPU6 GPU6: clEnqueueNDRangeKernel (-4)
17734:13:30:03.303: GPU2 GPU2: DAG 25%
17734:13:30:03.352: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17734:13:30:03.352: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
17734:13:30:03.556: GPU3 GPU3: DAG 31%
17734:13:30:03.708: GPU4 GPU4: DAG 19%
17734:13:30:04.476: GPU1 GPU1: DAG 50%
17734:13:30:05.136: GPU3 GPU3: DAG 63%
17734:13:30:05.143: GPU2 GPU2: DAG 56%
17734:13:30:05.548: GPU4 GPU4: DAG 50%
17734:13:30:06.293: GPU1 GPU1: DAG 81%
17734:13:30:06.655: GPU2 GPU2: DAG 81%
17734:13:30:06.710: GPU3 GPU3: DAG 94%
17734:13:30:07.026: GPU3 GPU3: DAG generated in 5.2 s (505.6 MB/s)
17734:13:30:07.358: GPU4 GPU4: DAG 81%
17734:13:30:07.384: GPU1 GPU1: DAG generated in 6.2 s (419.9 MB/s)
17734:13:30:07.843: GPU2 GPU2: DAG generated in 6.4 s (411.8 MB/s)
17734:13:30:08.422: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
17734:13:30:08.448: GPU4 GPU4: DAG generated in 6.2 s (419.9 MB/s)
17734:13:30:08.515: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x575909c317345e81fa3365b667c08332ae4c0f23f98bfb37bdfe11f34a12120e","0x8308d376eeb469b7ff84bd59c51988d9618b208dc3b951d1dc1918fa08306723","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5bafa5"]}
17734:13:30:08.740: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17734:13:30:08.740: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
17734:13:30:13.824: main Eth speed: 108.972 MH/s, shares: 0/0/0, time: 0:00
17734:13:30:13.824: main GPUs: 1: 26.156 MH/s (0) 2: 25.317 MH/s (0) 3: 31.333 MH/s (0) 4: 26.166 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
17734:13:30:18.431: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
17734:13:30:18.431: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0xc59c41a63f0da14970841cb14114f89d6f9be1a688a8a337f8b42638ec7e61eb"]}
17734:13:30:18.531: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x575909c317345e81fa3365b667c08332ae4c0f23f98bfb37bdfe11f34a12120e","0x8308d376eeb469b7ff84bd59c51988d9618b208dc3b951d1dc1918fa08306723","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5bafa5"]}
17734:13:30:18.535: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17734:13:30:18.978: main Eth speed: 112.757 MH/s, shares: 0/0/0, time: 0:00
17734:13:30:18.978: main GPUs: 1: 27.016 MH/s (0) 2: 26.699 MH/s (0) 3: 31.710 MH/s (0) 4: 27.331 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
17734:13:30:24.055: main Eth speed: 116.519 MH/s, shares: 0/0/0, time: 0:00
17734:13:30:24.055: main GPUs: 1: 28.089 MH/s (0) 2: 27.942 MH/s (0) 3: 32.104 MH/s (0) 4: 28.384 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
17734:13:30:24.477: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x1c69d6dd774d17b466970cb1ac8380e45293155345de1655d8671de47a8947ff","0x8308d376eeb469b7ff84bd59c51988d9618b208dc3b951d1dc1918fa08306723","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5bafa6"]}
17734:13:30:24.477: eths Eth: New job #1c69d6dd from asia1.ethermine.org:4444; diff: 4000MH
17734:13:30:24.508: GPU5 GPU5: Starting up... (0)
17734:13:30:24.539: GPU6 GPU6: Starting up... (0)
17734:13:30:24.561: GPU5 GPU5: Using new optimized OpenCL kernels (device name 'Ellesmere')
17734:13:30:24.561: GPU5 GPU5: Allocating DAG (2.58) GB; good for epoch up to #202
17734:13:30:24.561: GPU5 GPU5: Allocating light cache buffer (41.2) MB; good for epoch up to #202
17734:13:30:24.673: GPU5 GPU5: Generating DAG for epoch #200
17734:13:30:24.675: GPU5 GPU5: clEnqueueNDRangeKernel (-4)
17734:13:29:53.886: main Cmd line: -epool asia1.ethermine.org:4444 -ewal 0xC34CA9A45F4db78e979F5D803d2a9B457824bCF3.axe -epsw x -mode 1 -ftime 10 -wd 0
17734:13:29:53.886: main The following options are not supported and are ignored:
17734:13:29:53.886: main -mode
17734:13:29:53.887: main No CUDA driver found
17734:13:29:56.661: main Available GPUs for mining:
17734:13:29:56.663: main GPU1: Radeon RX 580 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 36 CUs
17734:13:29:56.663: main GPU2: Radeon RX 580 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 36 CUs
17734:13:29:56.663: main GPU3: Radeon RX 580 Series (pcie 4), OpenCL 2.0, 8 GB VRAM, 36 CUs
17734:13:29:56.663: main GPU4: Radeon RX 580 Series (pcie 5), OpenCL 2.0, 4 GB VRAM, 36 CUs
17734:13:29:56.663: main GPU5: Radeon RX 580 Series (pcie 6), OpenCL 2.0, 4 GB VRAM, 36 CUs
17734:13:29:56.663: main GPU6: Radeon RX 580 Series (pcie 7), OpenCL 2.0, 4 GB VRAM, 36 CUs
17734:13:29:56.821: main ADL library initialized
17734:13:29:57.309: main Listening for CDM remote manager at port 3333 in read-only mode
17734:13:29:57.311: main Eth: the pool list contains 3 pools
17734:13:29:57.311: main Eth: primary pool: asia1.ethermine.org:4444
17734:13:29:57.311: main Starting GPU mining
17734:13:29:57.312: main Matched GPU1 to ADL adapter index 64 (method 1)
17734:13:29:57.465: main GPU1: Created ADL monitor for adapter 64; overdrive version: 7
17734:13:29:57.465: main Matched GPU2 to ADL adapter index 0 (method 1)
17734:13:29:57.618: main GPU2: Created ADL monitor for adapter 0; overdrive version: 7
17734:13:29:57.618: main Matched GPU3 to ADL adapter index 80 (method 1)
17734:13:29:57.773: main GPU3: Created ADL monitor for adapter 80; overdrive version: 7
17734:13:29:57.773: main Matched GPU4 to ADL adapter index 48 (method 1)
17734:13:29:57.928: main GPU4: Created ADL monitor for adapter 48; overdrive version: 7
17734:13:29:57.928: main Matched GPU5 to ADL adapter index 16 (method 1)
17734:13:29:58.142: main GPU5: Created ADL monitor for adapter 16; overdrive version: 7
17734:13:29:58.142: main Matched GPU6 to ADL adapter index 32 (method 1)
17734:13:29:58.297: main GPU6: Created ADL monitor for adapter 32; overdrive version: 7
17734:13:29:58.300: main Eth: Connecting to ethash pool asia1.ethermine.org:4444 (proto: EthProxy)
17734:13:29:58.420: eths Eth: Connected to ethash pool asia1.ethermine.org:4444 (54.179.172.226)
17734:13:29:58.420: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0xC34CA9A45F4db78e979F5D803d2a9B457824bCF3.axe","x"]}
17734:13:29:58.517: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
17734:13:29:58.519: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
17734:13:29:58.526: main GPU1: 46C 0%, GPU2: 52C 0%, GPU3: 49C 0%, GPU4: 46C 0%, GPU5: 51C 0%, GPU6: 49C 0%
17734:13:29:58.545: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x575909c317345e81fa3365b667c08332ae4c0f23f98bfb37bdfe11f34a12120e","0x8308d376eeb469b7ff84bd59c51988d9618b208dc3b951d1dc1918fa08306723","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5bafa5"]}
17734:13:29:58.546: eths Eth: New job #575909c3 from asia1.ethermine.org:4444; diff: 4000MH
17734:13:29:58.550: GPU1 GPU1: Starting up... (0)
17734:13:29:58.550: GPU1 Eth: Generating light cache for epoch #200
17734:13:29:58.577: GPU2 GPU2: Starting up... (0)
17734:13:29:58.588: GPU3 GPU3: Starting up... (0)
17734:13:29:58.608: GPU4 GPU4: Starting up... (0)
17734:13:29:58.622: GPU5 GPU5: Starting up... (0)
17734:13:29:58.635: GPU6 GPU6: Starting up... (0)
17734:13:29:58.682: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x575909c317345e81fa3365b667c08332ae4c0f23f98bfb37bdfe11f34a12120e","0x8308d376eeb469b7ff84bd59c51988d9618b208dc3b951d1dc1918fa08306723","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5bafa5"]}
17734:13:30:01.030: GPU1 GPU1: Using new optimized OpenCL kernels (device name 'Ellesmere')
17734:13:30:01.031: GPU1 GPU1: Allocating DAG (2.58) GB; good for epoch up to #202
17734:13:30:01.031: GPU1 GPU1: Allocating light cache buffer (41.2) MB; good for epoch up to #202
17734:13:30:01.134: GPU1 GPU1: Generating DAG for epoch #200
17734:13:30:01.367: GPU2 GPU2: Using new optimized OpenCL kernels (device name 'Ellesmere')
17734:13:30:01.367: GPU2 GPU2: Allocating DAG (2.58) GB; good for epoch up to #202
17734:13:30:01.367: GPU2 GPU2: Allocating light cache buffer (41.2) MB; good for epoch up to #202
17734:13:30:01.470: GPU2 GPU2: Generating DAG for epoch #200
17734:13:30:01.732: GPU3 GPU3: Using new optimized OpenCL kernels (device name 'Ellesmere')
17734:13:30:01.732: GPU3 GPU3: Allocating DAG (2.58) GB; good for epoch up to #202
17734:13:30:01.732: GPU3 GPU3: Allocating light cache buffer (41.2) MB; good for epoch up to #202
17734:13:30:01.834: GPU3 GPU3: Generating DAG for epoch #200
17734:13:30:02.096: GPU4 GPU4: Using new optimized OpenCL kernels (device name 'Ellesmere')
17734:13:30:02.096: GPU4 GPU4: Allocating DAG (2.58) GB; good for epoch up to #202
17734:13:30:02.096: GPU4 GPU4: Allocating light cache buffer (41.2) MB; good for epoch up to #202
17734:13:30:02.198: GPU4 GPU4: Generating DAG for epoch #200
17734:13:30:02.444: GPU5 GPU5: Using new optimized OpenCL kernels (device name 'Ellesmere')
17734:13:30:02.444: GPU5 GPU5: Allocating DAG (2.58) GB; good for epoch up to #202
17734:13:30:02.444: GPU5 GPU5: Allocating light cache buffer (41.2) MB; good for epoch up to #202
17734:13:30:02.561: GPU5 GPU5: Generating DAG for epoch #200
17734:13:30:02.576: GPU5 GPU5: clEnqueueNDRangeKernel (-4)
17734:13:30:02.658: GPU1 GPU1: DAG 19%
17734:13:30:02.796: GPU6 GPU6: Using new optimized OpenCL kernels (device name 'Ellesmere')
17734:13:30:02.796: GPU6 GPU6: Allocating DAG (2.58) GB; good for epoch up to #202
17734:13:30:02.796: GPU6 GPU6: Allocating light cache buffer (41.2) MB; good for epoch up to #202
17734:13:30:02.899: GPU6 GPU6: Generating DAG for epoch #200
17734:13:30:02.901: GPU6 GPU6: clEnqueueNDRangeKernel (-4)
17734:13:30:03.303: GPU2 GPU2: DAG 25%
17734:13:30:03.352: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17734:13:30:03.352: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
17734:13:30:03.556: GPU3 GPU3: DAG 31%
17734:13:30:03.708: GPU4 GPU4: DAG 19%
17734:13:30:04.476: GPU1 GPU1: DAG 50%
17734:13:30:05.136: GPU3 GPU3: DAG 63%
17734:13:30:05.143: GPU2 GPU2: DAG 56%
17734:13:30:05.548: GPU4 GPU4: DAG 50%
17734:13:30:06.293: GPU1 GPU1: DAG 81%
17734:13:30:06.655: GPU2 GPU2: DAG 81%
17734:13:30:06.710: GPU3 GPU3: DAG 94%
17734:13:30:07.026: GPU3 GPU3: DAG generated in 5.2 s (505.6 MB/s)
17734:13:30:07.358: GPU4 GPU4: DAG 81%
17734:13:30:07.384: GPU1 GPU1: DAG generated in 6.2 s (419.9 MB/s)
17734:13:30:07.843: GPU2 GPU2: DAG generated in 6.4 s (411.8 MB/s)
17734:13:30:08.422: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
17734:13:30:08.448: GPU4 GPU4: DAG generated in 6.2 s (419.9 MB/s)
17734:13:30:08.515: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x575909c317345e81fa3365b667c08332ae4c0f23f98bfb37bdfe11f34a12120e","0x8308d376eeb469b7ff84bd59c51988d9618b208dc3b951d1dc1918fa08306723","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5bafa5"]}
17734:13:30:08.740: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17734:13:30:08.740: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
17734:13:30:13.824: main Eth speed: 108.972 MH/s, shares: 0/0/0, time: 0:00
17734:13:30:13.824: main GPUs: 1: 26.156 MH/s (0) 2: 25.317 MH/s (0) 3: 31.333 MH/s (0) 4: 26.166 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
17734:13:30:18.431: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
17734:13:30:18.431: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0xc59c41a63f0da14970841cb14114f89d6f9be1a688a8a337f8b42638ec7e61eb"]}
17734:13:30:18.531: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x575909c317345e81fa3365b667c08332ae4c0f23f98bfb37bdfe11f34a12120e","0x8308d376eeb469b7ff84bd59c51988d9618b208dc3b951d1dc1918fa08306723","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5bafa5"]}
17734:13:30:18.535: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17734:13:30:18.978: main Eth speed: 112.757 MH/s, shares: 0/0/0, time: 0:00
17734:13:30:18.978: main GPUs: 1: 27.016 MH/s (0) 2: 26.699 MH/s (0) 3: 31.710 MH/s (0) 4: 27.331 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
17734:13:30:24.055: main Eth speed: 116.519 MH/s, shares: 0/0/0, time: 0:00
17734:13:30:24.055: main GPUs: 1: 28.089 MH/s (0) 2: 27.942 MH/s (0) 3: 32.104 MH/s (0) 4: 28.384 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
17734:13:30:24.477: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x1c69d6dd774d17b466970cb1ac8380e45293155345de1655d8671de47a8947ff","0x8308d376eeb469b7ff84bd59c51988d9618b208dc3b951d1dc1918fa08306723","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x5bafa6"]}
17734:13:30:24.477: eths Eth: New job #1c69d6dd from asia1.ethermine.org:4444; diff: 4000MH
17734:13:30:24.508: GPU5 GPU5: Starting up... (0)
17734:13:30:24.539: GPU6 GPU6: Starting up... (0)
17734:13:30:24.561: GPU5 GPU5: Using new optimized OpenCL kernels (device name 'Ellesmere')
17734:13:30:24.561: GPU5 GPU5: Allocating DAG (2.58) GB; good for epoch up to #202
17734:13:30:24.561: GPU5 GPU5: Allocating light cache buffer (41.2) MB; good for epoch up to #202
17734:13:30:24.673: GPU5 GPU5: Generating DAG for epoch #200
17734:13:30:24.675: GPU5 GPU5: clEnqueueNDRangeKernel (-4)
There is a way to revert the update!
Use this bro:
https://www.howtogeek.com/235474/how-to-roll-back-builds-and-uninstall-updates-on-windows-10/
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.8 (Windows/Linux)
Don't expect much more from it.
I have several 570's ranging from 26,5 to 28,5Mhs.
I haven't seen more then 28.5 in any 570 to date, so yours is totaly normal performance wise.
really? even my old 470 refs are doing better then the numbers you state.I have several 570's ranging from 26,5 to 28,5Mhs.
I haven't seen more then 28.5 in any 570 to date, so yours is totaly normal performance wise.
rx570 can go up to 31. Normally however it hashes around 29.5-30.5
I've got a rig of rx570 4gb MSI gaming with Elpida doing mere 29.4. And the only slower 570 I've got is ASUS Expedition hashing at 28.8
Of course it's possible if you are willing to deal with memory errors in HWinfo.
GPUs can have hundreds of errors and seem to work fine but you have a steady higher stale shares percentage and the ocasional rejected share so i cannot accept 30mh as a 570s normal number.
https://s33.postimg.cc/hgv9pnzxb/dh31.jpg
Thank you very much for your post friend!
I seriously have no idea why i get such awful performance from my 570s... Most of them use combined memory chips from Elpida and Micron... I used one click timing patch and i cannot get more then 28,5 stable no way.
I have 7 of them from Asus and Gigabyte, all same shit, even have one that maxes at 1880MHZ mem.
What straps are you using? Maybe that's the deal.
also fyi mem errors in HwInfo are both those that were corrected and those that were not.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.8 (Windows/Linux)
Stale shares are shares for a block submitted after the next block is already being mined. Its result from network latency and fast block times and has nothing to do with memory errors or overclocking. Too much overclocking can definetlly cause memory errors and invalid/rejected shares though. Some of my Powercolor 4GB Red Dragon RX 570's run stable at 29.5-30.5 MH/s with a 1150 MHz core and 2075 MHz memory clock. I do have some that will only run at 1950-1975 MHz memory overclock at ~28.5 MH/s.
Aghh, yes man thanks for the correction Invalid is the correct term i tried to refer to.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.8 (Windows/Linux)
Don't expect much more from it.
I have several 570's ranging from 26,5 to 28,5Mhs.
I haven't seen more then 28.5 in any 570 to date, so yours is totaly normal performance wise.
really? even my old 470 refs are doing better then the numbers you state.I have several 570's ranging from 26,5 to 28,5Mhs.
I haven't seen more then 28.5 in any 570 to date, so yours is totaly normal performance wise.
rx570 can go up to 31. Normally however it hashes around 29.5-30.5
I've got a rig of rx570 4gb MSI gaming with Elpida doing mere 29.4. And the only slower 570 I've got is ASUS Expedition hashing at 28.8
Of course it's possible if you are willing to deal with memory errors in HWinfo.
GPUs can have hundreds of errors and seem to work fine but you have a steady higher stale shares percentage and the ocasional rejected share so i cannot accept 30mh as a 570s normal number.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.8 (Windows/Linux)
Don't expect much more from it.
I have several 570's ranging from 26,5 to 28,5Mhs.
I haven't seen more then 28.5 in any 570 to date, so yours is totaly normal performance wise.
I have several 570's ranging from 26,5 to 28,5Mhs.
I haven't seen more then 28.5 in any 570 to date, so yours is totaly normal performance wise.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.8 (Windows/Linux)
Can this miner run on 2GB of system memory?
I had 3 gb ddr2, but one ram stick stopped working so I'm left with only 2 gb of system memory.
I tried to start miner and I get message: ethdcrminer64.exe has stopped working
I didn't have any problems so far with 3 gb of RAM.
I had 3 gb ddr2, but one ram stick stopped working so I'm left with only 2 gb of system memory.
I tried to start miner and I get message: ethdcrminer64.exe has stopped working
I didn't have any problems so far with 3 gb of RAM.
Miner should run just fine on 2 GB of RAM. "Virtual memory" could be the issue here. It should be no less than 1.5x and no more than 3x the amount of system memory (RAM).
Just what the heck are you talking about? Virtual memory (pagefile) can be anything you want, there are no min or max, in fact the more cards you have the more Virtual ram you need, I have plenty or rigs running 50GB pagefiles.
You are confusing what Windows automatically sets with your 1.5x...
Please don't spread misinformation.
I remember I fixed that very same issue after I removed some RAM from my miner by decreasing the virtual memory. With 2 GB RAM, there should be a maximum of 6 GB virtual memory set according to Microsoft. In my opinion, up-to 8 GB virtual RAM should be fine as well for 2 GB RAM systems.
I'm pretty sure you've 4-8 GB RAM installed in your systems where you've set that much virtual memory.
EDIT: Here's what I'm talking about: https://www.ultraedit.com/support/tutorials-power-tips/ultracompare/increase-virtual-memory.html ... Read the last paragraph.
Ok, it is clear you are trying to help but please let this one go.
That source you posted is obviously outdated and clearly rookie targeted.
Mining is not the typical usage senario for desktop PC so please skip any article, guide whatever that is not specifically made for Cryptomining.
Anything below 20GB virtual memory will propably crash the miner. Even the OP states that VM should be 16GB or more.
I recommend he sets it to 25GB and try again.
Re: PhoenixMiner 3.0c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
It is safe, you can ignore the warning.
An honest advice though, better read and research more before starting to mine.
It is clear from your question that you can be an easy hack target or even destroy your hardware yourself.
Cheers
An honest advice though, better read and research more before starting to mine.
It is clear from your question that you can be an easy hack target or even destroy your hardware yourself.
Cheers
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.7 (Windows/Linux)
Hello,
Just set up Asus B250 board with 13 AMD RX 580's, this is my 4th miner and 2nd AMD rig exactly like this one.
Weird thing happening...when I start the CM miner, it gives me nothing past the start up screen:
Eth: 1 pool is specified
Main Ethereum pool is eth.suprnova.cc:5005
DCR: 0 pool is specified
Then after 5 minutes (apperently) it says:
Miner cannot initialize for 5 minutes, need to restart miner!
Here is command line:
ethdcrminer64.exe -epool eth.suprnova.cc:5005 -ewal ***.*** -epsw * -esm 3 -allpools 1 -dbg 1
I have a funny feeling it's to do with Windows Defender, because since I've been trying to get this thing working for the last few days, it never popped up and asked for me to Allow it through the firewall...but idk for sure. I shut it off and still no action.
I would post a pic to make it easier but I cannot figure out how to do that :-)
Just set up Asus B250 board with 13 AMD RX 580's, this is my 4th miner and 2nd AMD rig exactly like this one.
Weird thing happening...when I start the CM miner, it gives me nothing past the start up screen:
Eth: 1 pool is specified
Main Ethereum pool is eth.suprnova.cc:5005
DCR: 0 pool is specified
Then after 5 minutes (apperently) it says:
Miner cannot initialize for 5 minutes, need to restart miner!
Here is command line:
ethdcrminer64.exe -epool eth.suprnova.cc:5005 -ewal ***.*** -epsw * -esm 3 -allpools 1 -dbg 1
I have a funny feeling it's to do with Windows Defender, because since I've been trying to get this thing working for the last few days, it never popped up and asked for me to Allow it through the firewall...but idk for sure. I shut it off and still no action.
I would post a pic to make it easier but I cannot figure out how to do that :-)
Hey there,
So you have debug on, what do your logs tell you?
Try adding
-di 0
Start with GPU0 only, would be a good thing to try, as you could be overloading your PSUs.
If it's a new rig, never been running/stable, break it down, get through the init on one GPU, prove your config and basic hw/sw enviro, and take it from there.
jooi, what PSU are you using, and how many GPU on each, how many risers per cable?
Kudos on the 13gpu rig man, not so easy to get those stable.
Good luck.
footnote:
Try this.
setx GPU_FORCE_64BIT_PTR 1
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool ssl://eu1.ethermine.org:5555 -ewal wallet.rig -epsw x -di 0 -gser 1 -esm 0 -etha 0 -ethi 16 -eres 2 -erate 1 -estale 1 -asm 1 -platform 1 -y 1 -dcri 9 -wd 1 -ftime 5 -r 1440 -cclock 1200 -cvddc 900 -mclock 2100 -mvddc 850 -tstop 83 -tstart 50 -tt 60 -fanmin 40 -fanmax 100 -ttdcr 80 -ttli 80 -mode 1 -dbg 1 -altnum 3 -mport -3333 -mpsw whatever -logfile logs\
So that was a great idea taking the cards out and just doing 1, I should have tried that before posting. Unfortunately it didn't work, same result. Here is the last log file, the others say the exact same thing :-(
20:25:58:457 1460 Check and remove old log files...
20:25:58:457 1460 args: -epool eth.suprnova.cc:5005 -ewal ***.*** -epsw * -esm 3 -allpools 1 -dbg 1
20:25:58:457 1460
20:25:58:457 1460 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
20:25:58:457 1460 º Claymore's Dual GPU Miner - v11.7 º
20:25:58:457 1460 º ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK º
20:25:58:457 1460 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
20:25:58:457 1460
20:25:58:457 1460 b583
20:25:58:685 1460 ETH: 1 pool is specified
20:25:58:685 1460 Main Ethereum pool is eth.suprnova.cc:5005
20:25:58:685 1460 DCR: 0 pool is specified
20:26:31:509 d48
20:27:04:325 d48
20:27:37:141 d48
20:28:09:957 d48
20:28:42:541 d48
2x 1,200 watt gold psu's, even distrubuted as with my other one.
and only 2 risers per sata leg
Thank you for you help!
OK, will it sounds like your PSU and topology is thought through, so maybe leave that for now.
Could you post the debug log, from the batch file I added above?
(Just to rule out the pool angles, as I have no experience with suprnova, and Ethermine, being pretty much the biggest there is, makes for a good choice when testing, even if you don't plan on mining with those guys).
Now that said, what SHOULD be happening at this stage is the init of OpenCL, (or CUDA if you're using Nvidia).
OpenCL is managed via the AMD driver, so assuming you don't have a problem with the pool, I think you need to investigate if OpenCL is available.
One way to do that, (with a only single GPU in the rig), is you use GPU-z, and see if the OpenCL check box is populated.
Now, I have also seen perfectly good working rigs, where that checkbox is NOT populated, and clearly that is wrong, so to be absolutely sure, you (again with only 1 GPU in the rig), could boot to safe mode, DDU, reboot, install the AMD driver, set to compute, reboot, and check GPU-z, I have never seen that fail to confirm OpenCL.
From there, try my batch file again, and post the log if you're still stuck.
Good luck
Also, VM? Set to 48000GB if need be.
Foot note, in case anyone needs convincing of the single GPU method. If you do a clean AMD driver install with 13GPU, this alone can take hours, more so, if it fails, and AMD themselves STILL have an open bug on init fail with more than 12GPU.
Often when testing theories, working through troubleshooting etc, this is time consuming, and for sure you probably work at testing, (proving) some angles that were perfectly fine to start with. Time is not wasted of course, as you can cross those off the list, elimination of them, takes you closer to the answer.
But all the same, if you have multiple GPU, that's an exponential multiplier on the possibilities of fault, and means more time to troubleshoot is a given.
Breaking it down to basics, (you only need to pull the USB cables from the MB, for the most part), is pretty quick, you don't need to physically remove the GPUs etc, means you can run DDU, and reinstall the AMD driver with the minimum time consumed, and get back to starting Claymore as quickly as possible.
AMD driver install time, is pretty acceptable with a single GPU, but 12 and 13 is really nasty, and I have seen that fail many times, so working on proof of concept with a single GPU is by far the fastest, and most likely to provide solutions imho.
BTW 18.3.4 is a stable driver for mining.
Note: there is NOTHING mentioned in any release notes from AMD, on any mining related improvements in the drivers release since 18.3.4.
That is not to say the newer drivers are bad, (some are though), but simply, 18.3.4 has been out for a while, rolls up all the mining related things you probably need for RX570/580 hardware, and has proved itself far more than any of the drivers released since then. So, if you're going to DDU etc, I'd suggest 18.3.4 is a good choice, known good, known stable, well proven choice, and when you're troubleshooting, you need to focus on elimination of doubt. Go with what you know, (is good).
I was wondering why niether of the cuda opencl boxes were checked, and there has been an error that GPU-Z gives me when I open it or switch cards. I installed W10 1709 I believe then it updated to 1803, so I reverted back and have had strange things since. So I'mma do a fresh install and see what happens, I was able to flash the mod bios already so I don't really need atiflash to work anyway so I'll try 1803 fresh.
Thank you so much!
No worries, wow, that is a nasty situation with win updates. But before you roll back, it would be very helpful to know, if the DDU, clean install, or alternatively a manual driver install in devman as Ursul0 pointed out, gets you anywhere.
Because one would hope that DDU/clean install-driver option is an available solution.
But indeed, you could be right, I have seen some systems in a real mess after a OS roll back, and while that isn't to say that applies in your case, it's always one of those nasty things that sow the seeds of doubt later.
Also, you might like to set all your NICs to metered connection, that at least for the most part, prevents MS from updating your rig, or if nothing else, gives you some warning when they try to.
Regedit
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\DefaultMediaCost]
Grant your user "folder" permissions, and change all NICs to dword 2.
e.g.
"3G"=dword:00000002
"4G"=dword:00000002
"Default"=dword:00000002
"Ethernet"=dword:00000002
"WiFi"=dword:00000002
It won't help you with your current problem, but might be useful on your rigs
Good luck.
If this is actual bat then I see something missing
Here is command line:
ethdcrminer64.exe -epool eth.suprnova.cc:5005 -ewal ***.*** -epsw * -esm 3 -allpools 1 -dbg 1
Here is command line adding asm:
ethdcrminer64.exe -epool eth.suprnova.cc:5005 -ewal ***.*** -epsw * -asm 1 -esm 3 -allpools 1 -dbg 1
if you have a much longer script line like examples shown make sure its all 1 line and not hard return broken into multiple lines.
also not sure if it helps but I have my setx
setx GPU_FORCE_64BIT_PTR 0
not
setx GPU_FORCE_64BIT_PTR 1
as you are using 13 gpus the pagefile settings may need a lot more than 16 gig, can you bump it up to 32 or 48.
also check gpus are sitting well in risers I had one angled weird that caused me tons of grief.
gltu
as an aside i used to use suprnnova but switched to ethertrench.com no fees smaller pool but increased my eth ratio by 20%.
Just jumping in to clear and confirm that the:
setx GPU_FORCE_64BIT_PTR 1
Is totaly safe to use and in some cases might even solve incompatibilities and/or improve performance.
I was not surprised to see iSux using it cause he seems to be very knowledgable person regarding mining.
On another note, just download and use Win10 ver 1607 and install windows with Ethernet cable unplugged.
After the OS boots, go to computer management---> services and disable windows update service.
Restart, plug ethernet back and don't worry again about this kind of stuff.
Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
When 3.0 ? Not too soon because we have some big changes for this one.
Hello Nvidia GPU users today new update driver maby better try it
Version: 397.31 WHQL
Release Date: 2018.4.25
Operating System: Windows 10 64-bit
Language: English (US)
File Size: 471.06 MB
http://www.nvidia.com/download/driverResults.aspx/133648/en-us
PLEASE DO NOT TRY IT!
IT CAUSES BOOTLOOPS!
https://www.techpowerup.com/243684/nvidia-geforce-397-31-whql-drivers-put-gtx-1060-powered-systems-into-endless-restart-loop
Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Hello team,
Fast questions:
Is there a reason for this option to always be "0" ??
setx GPU_FORCE_64BIT_PTR 0
Are there any advantages if we set it to "1" instead?
Thank you for this excellent miner!
Fast questions:
Is there a reason for this option to always be "0" ??
setx GPU_FORCE_64BIT_PTR 0
Are there any advantages if we set it to "1" instead?
Thank you for this excellent miner!
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.5 (Windows/Linux)
Windows found a backdoor trojan in this miner download
https://www.microsoft.com/en-us/wdsi/threats/malware-encyclopedia-description?name=Trojan%3aWin32%2fCoinminer!bit&threatid=2147721766
https://www.microsoft.com/en-us/wdsi/threats/malware-encyclopedia-description?name=Trojan%3aWin32%2fCoinminer!bit&threatid=2147721766
You should not use a miner that shows positive for a virus
I cannot stress enough how dangerous this situation is!!
Thanks for telling us man!
Stop using this miner and use a registry cleaner after just in case!
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.5 (Windows/Linux)
Hey guys, have any of you had an issue with V11.5, where when connection was lost to the pool, the miner resumed when the connection was restored, but at a lower hashrate?
At ~1:45am this morning, my miner lost connection, and when the connection was restored, the AMD cards mined at less than 50% of their usual hash rate. Strangely though, the NVidia cards on the rig resumed at their normal hashrate.
At ~1:45am this morning, my miner lost connection, and when the connection was restored, the AMD cards mined at less than 50% of their usual hash rate. Strangely though, the NVidia cards on the rig resumed at their normal hashrate.
this happens to me as well for hardcoded bios.
temporary solution is disable p0-p6 in overdriventool. or hardcode your bios to use the same clocks on p0-p6.
this must be a bug, since this is not happening on previous versions.
See my previous response.
This bug is happening for me in any version of Claymore all the way back to June.
It appears to affect some people more than others.
Temporary solution is to use same clocks in every power state as you also mentioned.
I tried to lock states in Overdriventool but when i hit "apply" it just resets my settings, so i whould suggest the vBIOS modding until further findings/help from Claymore.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.5 (Windows/Linux)
Hey guys, have any of you had an issue with V11.5, where when connection was lost to the pool, the miner resumed when the connection was restored, but at a lower hashrate?
At ~1:45am this morning, my miner lost connection, and when the connection was restored, the AMD cards mined at less than 50% of their usual hash rate. Strangely though, the NVidia cards on the rig resumed at their normal hashrate.
AMD Cards: Powercolor RX470, MSI Armor RX480
NVidia Cards: 2 x GTX 1050Ti
At ~1:45am this morning, my miner lost connection, and when the connection was restored, the AMD cards mined at less than 50% of their usual hash rate. Strangely though, the NVidia cards on the rig resumed at their normal hashrate.
AMD Cards: Powercolor RX470, MSI Armor RX480
NVidia Cards: 2 x GTX 1050Ti
Hello man,
Unfortunately this very same problem strikes me from the very first day i started mining using Claymore (ANY VERSION).
I spent countless hours trying to beat this issue and here is what i found:
1. The problem is easily reproducible. Just start mining, remove ethernet cable---> reconnect ethernet cable---> BOOM stuck on lower hashrate.
2. Tried to use -minspeed parameter to no avail. The miner restarts but still remains stuck on lower frequencies.
3. Problem is related to PStates. Somehow after network reconnection, AMD drivers do not recognise the miner as a heavy enough load and apply a lower power state to the GPU that uses lower Core frequency.
4. -minspeed command being useless, the only way to restore full speed is to manually close and reopen Claymore.
5. As you too confirmed, Nvidia cards are not affected.
Temporary Solution i use myself:
Edit the vBIOS so that ALL power states use the SAME core frequency. That way you will be restored in full speed and be able run your rigs normally.
I hope this helped friend.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.2 (Windows/Linux)
Finally got my Claymore's Miner to launch and run properly but it looks like now i have an issue with my graphics card. Are my GPUs not powerful enough to mine? I have a NVidia GeForce 940M and an Intel HD Graphics 520. It looks like the Miner is only recognizing the NVidia. Here is an example of one of the logs below. Any suggestions would be appreciated.
Please read the OP next time.
It is clearly stated that Intel HD Graphics is NOT supported by this miner.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.1 (Windows/Linux)
Wondering if anyone can shed some light on my issue, im switching over to ETC and ive always used claymore.
my nvidia 1060 rigg pushes out the same hash rate 24.5 per card, my amds all went from 29.5 to 19.5. any idea what it can be?
my nvidia 1060 rigg pushes out the same hash rate 24.5 per card, my amds all went from 29.5 to 19.5. any idea what it can be?
Use amd blockchain drivers from 23 August or if you Use latest version of Windows 10 give a try to latest relive drivers with compute mode enabled.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.1 (Windows/Linux)
Im a beginner Miner.....whats a good GPU to start out with?
gtx 1070 or AMD 580
for the same budget buy 2 gtx 1060 3GB and earn 50% more ...
Yeah right... and gift them for 50 euros each in the second hand market after some months that 3GB won't be enough for dag files....
BONUS with 1060 3GB option: Crappy Hynix memory chips averaging 18MH/s....
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.1 (Windows/Linux)
Im a beginner Miner.....whats a good GPU to start out with?
gtx 1070 or AMD 580
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.1 (Windows/Linux)
Hi Guys
I'm wondering if you can help me with this.
my rig keeps rebooting shortly after the miner starts on this and I cant figure out why.
I'm using 4 x vegas
1200w PSU
latest blockchain drivers
32gb virtual mem
8gb ram
I've got the fans set manually it wattman to 3000rpm min
I've disabled all other over / underclocking and am just trying to run this as a baseline test before I start playing with the other settings
The miner starts up, runs for a few seconds and then the rig just resets and wattman resets everything.
The rig works brilliantly on cryptonote but I fancied giving some eth dual mining a try for a while.
Anything that would normally cause this type of behaviour?
I'm wondering if you can help me with this.
my rig keeps rebooting shortly after the miner starts on this and I cant figure out why.
I'm using 4 x vegas
1200w PSU
latest blockchain drivers
32gb virtual mem
8gb ram
I've got the fans set manually it wattman to 3000rpm min
I've disabled all other over / underclocking and am just trying to run this as a baseline test before I start playing with the other settings
The miner starts up, runs for a few seconds and then the rig just resets and wattman resets everything.
The rig works brilliantly on cryptonote but I fancied giving some eth dual mining a try for a while.
Anything that would normally cause this type of behaviour?
May i ask your PSU model?
Do not take for granted that since cryptonote runs fine so will Eth cause different algorithms have different electrical behavior and requirements.
I suggest you try to mine only Etherium without second coin.
If it's stable, please measure your power consumption in the wall and tell us how many watts it takes.
If it's not stable even with single Eth, then run Cryptonote and report the power consumption in that case.
We can draw better conclusions with the above data.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.1 (Windows/Linux)
Just tried the new AMD drivers (Crimson ReLive Edition 17.11.1) and saw a 20% drop off in speed. Went back to the blockchain drivers (23rd Aug) and speed back up. Not sure if this is isolated to my rig of RX480s but noticed drop was on both 8GB and 4GB models.
Propably you forgot enable compute mode in AMD control panel.
Still i advice you to stay where you are if your system is stable!
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.1 (Windows/Linux)
Ok, so I have 2 x AMD 290 cards and can't get it to work. Does anyone have a config/command line argument for that setup? I'll happily donate a Decred or two.
Edit the start.bat from the Claymore folder to look like this:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal 0xxxxxxxxYourWalletAddress.Rig1 -epsw x
Put your correct ether wallet address before .Rig1
Run it and if the windows firewall asks you press "Allow" so that it can connect to the Internet.
From there on tell me if there is an error.