Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 594.

kkourmousis

member

Activity: 119

Merit: 10

Caution: LONG post ahead...

Regarding the freezing rigs after connection loss or after a gpu hang:

First of all, some of you may want to take a look at my previous posts, I have been trying to keep everything summed up for people with similar issues to be able to check them out all at once.
So here is my initial post and here, here and here are the ones that followed on that issue. For those of you guys that just want to read my conclusion, you can skip those.

My "verdict" is that sometimes when the miner starts it causes a power consumption spike, which may be above your rig's max power. For me it happened almost always after a connection loss and sometimes after a gpu hang.

First of all, here is a graph of my power consumption during my tests:

Keep in mind that I have 2x 750watt gold PSUs, so 1500 watts is my limit. Now take a look on those spikes.... yeah...

I will spare you from too much of big data and focus on the incident I have my cursor on in the above image (04:32 2017-09-17)

Here is a log from that connection loss:

Code:

04:20:08:606	760	ETH: 09/17/17-04:20:08 - SHARE FOUND - (GPU 1)
04:20:08:606	760	send: {"id":4,"method":"eth_submitWork","params":["0xddbeb830014986f8","0x5d1e56cff72d19a9789bdede097515ab9c81d5152aca3d900a4faf722574efa7","0x5bdeefa8e95c5eabeb33955d560cd8b5c6e0e21fd1517502c929be41108d8412"]}
04:20:08:809	858	GPU0 t=69C fan=48%, GPU1 t=67C fan=33%, GPU2 t=67C fan=48%, GPU3 t=64C fan=36%, GPU4 t=64C fan=33%, GPU5 t=66C fan=33%, GPU6 t=70C fan=35%, GPU7 t=69C fan=41%
04:20:08:809	858	em hbt: 0, dm hbt: 0, fm hbt: 63, 
04:20:08:809	858	watchdog - thread 0 (gpu0), hb time 125
04:20:08:809	858	watchdog - thread 1 (gpu0), hb time 47
04:20:08:809	858	watchdog - thread 2 (gpu1), hb time 141
04:20:08:809	858	watchdog - thread 3 (gpu1), hb time 63
04:20:08:809	858	watchdog - thread 4 (gpu2), hb time 110
04:20:08:809	858	watchdog - thread 5 (gpu2), hb time 16
04:20:08:809	858	watchdog - thread 6 (gpu3), hb time 78
04:20:08:809	858	watchdog - thread 7 (gpu3), hb time 0
04:20:08:809	858	watchdog - thread 8 (gpu4), hb time 78
04:20:08:825	858	watchdog - thread 9 (gpu4), hb time 15
04:20:08:825	858	watchdog - thread 10 (gpu5), hb time 140
04:20:08:825	858	watchdog - thread 11 (gpu5), hb time 15
04:20:08:825	858	watchdog - thread 12 (gpu6), hb time 125
04:20:08:825	858	watchdog - thread 13 (gpu6), hb time 46
04:20:08:825	858	watchdog - thread 14 (gpu7), hb time 171
04:20:08:825	858	watchdog - thread 15 (gpu7), hb time 78
04:20:09:075	760	Socket was closed remotely (by pool)
04:20:09:075	760	ETH: Connection lost, retry in 20 sec...
04:20:09:622	178c	recv: 66
04:20:09:622	178c	srv pck: 65
04:20:09:825	178c	srv bs: 0
04:20:09:825	178c	sent: 290
04:20:12:294	858	GPU 0 temp = 65, old fan speed = 49, new fan speed = 34 
04:20:12:341	858	GPU 1 temp = 62, old fan speed = 34, new fan speed = 25 
04:20:12:341	858	GPU 2 temp = 62, old fan speed = 49, new fan speed = 34 
04:20:12:357	858	GPU 3 temp = 59, old fan speed = 36, new fan speed = 25 
04:20:12:372	858	GPU 4 temp = 60, old fan speed = 33, new fan speed = 25 
04:20:12:388	858	GPU 5 temp = 63, old fan speed = 33, new fan speed = 25 
04:20:12:419	858	GPU 6 temp = 65, old fan speed = 35, new fan speed = 25 
04:20:12:419	858	GPU 7 temp = 64, old fan speed = 41, new fan speed = 27 
04:20:12:857	4b8	recv: 66
04:20:12:857	4b8	srv pck: 65
04:20:13:075	4b8	srv bs: 0
04:20:13:075	4b8	sent: 290
04:20:14:622	18e4	recv: 66
04:20:14:622	18e4	srv pck: 65
04:20:14:826	18e4	srv bs: 0
04:20:14:826	18e4	sent: 207
04:20:15:919	858	GPU 0 temp = 62, old fan speed = 47, new fan speed = 31 
04:20:15:935	858	GPU 1 temp = 59, old fan speed = 34, new fan speed = 25 
04:20:15:951	858	GPU 2 temp = 60, old fan speed = 46, new fan speed = 30 
04:20:15:951	858	GPU 3 temp = 55, old fan speed = 36, new fan speed = 25 
04:20:15:966	858	GPU 4 temp = 57, old fan speed = 33, new fan speed = 25 
04:20:15:982	858	GPU 5 temp = 60, old fan speed = 34, new fan speed = 25 
04:20:15:998	858	GPU 6 temp = 62, old fan speed = 35, new fan speed = 25 
04:20:15:998	858	GPU 7 temp = 62, old fan speed = 38, new fan speed = 25 
04:20:17:857	1150	recv: 66
04:20:17:857	1150	srv pck: 65
04:20:18:060	1150	srv bs: 0
04:20:18:060	1150	sent: 207
04:20:19:545	858	GPU 0 temp = 60, old fan speed = 43, new fan speed = 27 
04:20:19:576	858	GPU 1 temp = 58, old fan speed = 34, new fan speed = 25 
04:20:19:592	858	GPU 2 temp = 58, old fan speed = 41, new fan speed = 25 
04:20:19:592	858	GPU 3 temp = 54, old fan speed = 37, new fan speed = 25 
04:20:19:607	858	GPU 4 temp = 56, old fan speed = 33, new fan speed = 25 
04:20:19:623	858	GPU 5 temp = 59, old fan speed = 34, new fan speed = 25 
04:20:19:623	6ec	recv: 66
04:20:19:623	6ec	srv pck: 65
04:20:19:639	858	GPU 6 temp = 61, old fan speed = 36, new fan speed = 25 
04:20:19:639	858	GPU 7 temp = 60, old fan speed = 36, new fan speed = 25 
04:20:19:810	6ec	srv bs: 0
04:20:19:810	6ec	sent: 207
04:20:22:842	1740	recv: 66
04:20:22:842	1740	srv pck: 65
04:20:23:045	1740	srv bs: 0
04:20:23:045	1740	sent: 207
04:20:23:201	858	GPU 0 temp = 60, old fan speed = 38, new fan speed = 25 
04:20:23:217	858	GPU 1 temp = 57, old fan speed = 34, new fan speed = 25 
04:20:23:217	858	GPU 2 temp = 58, old fan speed = 34, new fan speed = 25 
04:20:23:233	858	GPU 3 temp = 53, old fan speed = 36, new fan speed = 25 
04:20:23:248	858	GPU 4 temp = 55, old fan speed = 33, new fan speed = 25 
04:20:23:264	858	GPU 5 temp = 58, old fan speed = 34, new fan speed = 25 
04:20:23:264	858	GPU 6 temp = 60, old fan speed = 36, new fan speed = 25 
04:20:23:280	858	GPU 7 temp = 60, old fan speed = 36, new fan speed = 25 
04:20:24:624	19ec	recv: 66
04:20:24:624	19ec	srv pck: 65
04:20:24:827	19ec	srv bs: 0
04:20:24:827	19ec	sent: 207
04:20:26:764	858	GPU 0 temp = 59, old fan speed = 36, new fan speed = 25 
04:20:26:780	858	GPU 1 temp = 56, old fan speed = 34, new fan speed = 25 
04:20:26:780	858	GPU 2 temp = 57, old fan speed = 33, new fan speed = 25 
04:20:26:796	858	GPU 3 temp = 52, old fan speed = 36, new fan speed = 25 
04:20:26:811	858	GPU 4 temp = 54, old fan speed = 33, new fan speed = 25 
04:20:26:811	858	GPU 5 temp = 57, old fan speed = 34, new fan speed = 25 
04:20:26:842	858	GPU 6 temp = 59, old fan speed = 36, new fan speed = 25 
04:20:26:858	858	GPU 7 temp = 58, old fan speed = 36, new fan speed = 25


===========================================================
here the miner hangs and it restarts after ~10 minutes, just for a while before it freeze my rig
===========================================================
 
04:31:41:962	5a4	
04:31:41:972	5a4	INNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN»
04:31:41:974	5a4	Ί     Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v10.0      Ί
04:31:41:977	5a4	ΘNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNΌ
04:31:41:980	5a4	
04:31:42:187	5a4	ETH: 1 pool is specified
04:31:42:190	5a4	Main Ethereum pool is eu2.ethermine.org:4444
04:31:42:192	5a4	DCR: 1 pool is specified
04:31:42:194	5a4	Main Decred pool is dcr-eu.coinmine.pl:2222
04:31:43:553	5a4	OpenCL platform: Intel(R) OpenCL
04:31:43:554	5a4	OpenCL platform: AMD Accelerated Parallel Processing
04:31:43:555	5a4	OpenCL initializing...
04:31:43:556	5a4	AMD Cards available: 8 
04:31:43:556	5a4	GPU #0: Ellesmere, 8192 MB available, 36 compute units
04:31:43:557	5a4	GPU #0 recognized as Radeon RX 480/580
04:31:43:558	5a4	GPU #1: Ellesmere, 8192 MB available, 36 compute units
04:31:43:559	5a4	GPU #1 recognized as Radeon RX 480/580
04:31:43:560	5a4	GPU #2: Ellesmere, 8192 MB available, 36 compute units
04:31:43:561	5a4	GPU #2 recognized as Radeon RX 480/580
04:31:43:561	5a4	GPU #3: Ellesmere, 8192 MB available, 36 compute units
04:31:43:562	5a4	GPU #3 recognized as Radeon RX 480/580
04:31:43:563	5a4	GPU #4: Ellesmere, 8192 MB available, 36 compute units
04:31:43:564	5a4	GPU #4 recognized as Radeon RX 480/580
04:31:43:565	5a4	GPU #5: Ellesmere, 8192 MB available, 36 compute units
04:31:43:565	5a4	GPU #5 recognized as Radeon RX 480/580
04:31:43:566	5a4	GPU #6: Ellesmere, 8192 MB available, 36 compute units
04:31:43:566	5a4	GPU #6 recognized as Radeon RX 480/580
04:31:43:567	5a4	GPU #7: Ellesmere, 8192 MB available, 36 compute units
04:31:43:567	5a4	GPU #7 recognized as Radeon RX 480/580
04:31:43:568	5a4	POOL/SOLO version
04:31:43:569	5a4	b415 
04:31:43:570	5a4	Platform: Windows
04:31:43:624	5a4	start building OpenCL program for GPU 0...
04:31:44:323	5a4	done
04:31:44:531	5a4	start building OpenCL program for GPU 1...
04:31:44:836	5a4	done
04:31:45:041	5a4	start building OpenCL program for GPU 2...
04:31:45:339	5a4	done
04:31:45:547	5a4	start building OpenCL program for GPU 3...
04:31:45:870	5a4	done
04:31:46:074	5a4	start building OpenCL program for GPU 4...
04:31:46:367	5a4	done
04:31:46:574	5a4	start building OpenCL program for GPU 5...
04:31:46:865	5a4	done
04:31:47:073	5a4	start building OpenCL program for GPU 6...
04:31:47:415	5a4	done
04:31:47:620	5a4	start building OpenCL program for GPU 7...
04:31:47:892	5a4	done
04:31:48:129	5a4	GPU #0: algorithm ASM
04:31:48:194	5a4	GPU #1: algorithm ASM
04:31:48:252	5a4	GPU #2: algorithm ASM
04:31:48:314	5a4	GPU #3: algorithm ASM
04:31:48:371	5a4	GPU #4: algorithm ASM
04:31:48:429	5a4	GPU #5: algorithm ASM
04:31:48:493	5a4	GPU #6: algorithm ASM
04:31:48:555	5a4	GPU #7: algorithm ASM
04:31:48:563	5a4	cudaGetDeviceCount failed (35, CUDA driver version is insufficient for CUDA runtime version), probably no CUDA devices
04:31:48:564	5a4	No NVIDIA CUDA GPUs detected.
04:31:48:565	5a4	Total cards: 8 
04:31:48:624	5a4	No NVIDIA cards in the list, NVML library will not be used.
04:31:48:708	548	ETH: Stratum - connecting to 'eu2.ethermine.org' <91.121.222.33> port 4444
04:31:48:734	5a4	DUAL MINING MODE ENABLED: ETHEREUM+DECRED
04:31:48:735	5a4	ETH: eth-proxy stratum mode
04:31:48:736	5a4	Watchdog enabled
04:31:48:737	5a4	Remote management is enabled on port 3333
04:31:48:737	5a4	
04:31:48:776	548	send: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0xBaDED68D916F207f6FE3DAb16D76fae6Be06b8EC.main", "x"], "id": 2, "method": "eth_submitLogin"}
04:31:48:777	548	ETH: Stratum - Connected (eu2.ethermine.org:4444)
04:31:48:803	5fc	 DCR: Stratum - connecting to 'dcr-eu.coinmine.pl' <147.135.221.191> port 2222
04:31:48:841	548	got 39 bytes
04:31:48:842	548	buf: {"id":2,"jsonrpc":"2.0","result":true}
04:31:48:843	548	parse packet: 38
04:31:48:844	548	ETH: Authorized
04:31:48:845	548	send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
04:31:48:846	548	new buf size: 0
04:31:48:868	5fc	send: {"id": 1, "method": "mining.subscribe", "params": ["dual 1.0"]}
04:31:48:869	5fc	send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}
04:31:48:869	5fc	send: {"id": 2, "method": "mining.authorize", "params": ["4KMiningRig.DCR_4KMiningRig","080462"]}
04:31:48:870	5fc	 DCR: Stratum - Connected (dcr-eu.coinmine.pl:2222)
04:31:48:910	548	got 248 bytes
04:31:48:910	548	buf: {"id":3,"jsonrpc":"2.0","result":["0x6a72463ccc51109fa0bdae7095fb8bdea009b7c502d2f827513f17e03f356ecd","0xa91b532dbccf95bab5809616107474f25559efebc2974e2b22acae346634b49a","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x41577e"]}
04:31:48:911	548	parse packet: 247
04:31:48:912	548	ETH: job changed
04:31:48:913	548	new buf size: 0
04:31:48:934	5fc	got 179 bytes
04:31:48:934	5fc	buf: {"id":1,"result":[[["mining.set_difficulty","deadbeefcafebabea367030000000000"],["mining.notify","deadbeefcafebabea367030000000000"]],"000000000000000077ff3d21",12],"error":null}
04:31:48:935	5fc	parse packet: 178
04:31:48:936	5fc	new buf size: 0
04:31:48:943	be0	Setting DAG epoch #142...
04:31:49:043	5fc	got 532 bytes
04:31:49:043	5fc	buf: {"id":null,"method":"mining.set_difficulty","params":[10]}
{"id":null,"method":"mining.notify","params":["e196","c1b2bdba0b38198ad24c8b82319b27a1a3791509bd7e6af20000008300000000","39947f745f573bd784b7def2b5e9c9d1f29cfaa753ba583d8db8136e0891a735ae7f464880e2c5bbbd7cca9fcabefc907ee65c4a601f3b21245266600cc0e9490100ab851a08a7e105000500ee9e000029c0001a7f85548201000000979502004015000082d0bd590000000000000000","04000000",[],"04000000","1a00c029","59bdd082",true]}
{"id":5,"result":true,"error":null}
{"id":2,"result":true,"error":null}
04:31:49:044	5fc	parse packet: 58
04:31:49:045	5fc	remove first packet 473
04:31:49:045	5fc	new buf size: 473
04:31:49:046	5fc	parse packet: 400
04:31:49:046	5fc	remove first packet 72
04:31:49:048	5fc	new buf size: 72
04:31:49:048	5fc	parse packet: 35
04:31:49:049	5fc	remove first packet 36
04:31:49:050	5fc	new buf size: 36
04:31:49:050	5fc	parse packet: 35
04:31:49:051	5fc	 DCR: Authorized
04:31:49:051	5fc	new buf size: 0
04:31:50:993	11a0	Setting DAG epoch #142 for GPU4
04:31:50:993	11a0	Create GPU buffer for GPU4
04:31:50:992	be0	Setting DAG epoch #142 for GPU1
04:31:50:993	564	Setting DAG epoch #142 for GPU7
04:31:50:993	1ef0	Setting DAG epoch #142 for GPU0
04:31:50:993	1b4c	Setting DAG epoch #142 for GPU5
04:31:50:994	1ab0	Setting DAG epoch #142 for GPU6
04:31:50:995	1608	Setting DAG epoch #142 for GPU2
04:31:50:996	564	Create GPU buffer for GPU7
04:31:50:997	1ef0	Create GPU buffer for GPU0
04:31:50:998	1c7c	Setting DAG epoch #142 for GPU3
04:31:51:003	1c7c	Create GPU buffer for GPU3
04:31:50:999	1ab0	Create GPU buffer for GPU6
04:31:50:998	1b4c	Create GPU buffer for GPU5
04:31:50:999	be0	Create GPU buffer for GPU1
04:31:51:010	1608	Create GPU buffer for GPU2
04:31:51:524	10f8	OC v7, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst 
04:31:51:579	10f8	OC v7, Reset control for GPU 1, close miner right now if you want to use default control from Catalyst 
04:31:51:634	10f8	OC v7, Reset control for GPU 2, close miner right now if you want to use default control from Catalyst 
04:31:51:689	10f8	OC v7, Reset control for GPU 3, close miner right now if you want to use default control from Catalyst 
04:31:51:741	10f8	OC v7, Reset control for GPU 4, close miner right now if you want to use default control from Catalyst 
04:31:51:795	10f8	OC v7, Reset control for GPU 5, close miner right now if you want to use default control from Catalyst 
04:31:51:852	10f8	OC v7, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst 
04:31:51:905	10f8	OC v7, Reset control for GPU 7, close miner right now if you want to use default control from Catalyst 
04:31:52:106	1a10	recv: 66
04:31:52:107	1a10	srv pck: 65
04:31:52:349	1a10	OC v7, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst 
04:31:52:402	1a10	OC v7, Reset control for GPU 1, close miner right now if you want to use default control from Catalyst 
04:31:52:457	1a10	OC v7, Reset control for GPU 2, close miner right now if you want to use default control from Catalyst 
04:31:52:513	1a10	OC v7, Reset control for GPU 3, close miner right now if you want to use default control from Catalyst 
04:31:52:569	1a10	OC v7, Reset control for GPU 4, close miner right now if you want to use default control from Catalyst 
04:31:52:624	1a10	OC v7, Reset control for GPU 5, close miner right now if you want to use default control from Catalyst 
04:31:52:680	1a10	OC v7, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst 
04:31:52:739	1a10	OC v7, Reset control for GPU 7, close miner right now if you want to use default control from Catalyst 
04:31:52:741	1a10	srv bs: 0
04:31:52:743	1a10	sent: 207
04:31:53:096	578	recv: 66
04:31:53:097	578	srv pck: 65
04:31:53:330	578	OC v7, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst 
04:31:53:384	578	OC v7, Reset control for GPU 1, close miner right now if you want to use default control from Catalyst 
04:31:53:440	578	OC v7, Reset control for GPU 2, close miner right now if you want to use default control from Catalyst 
04:31:53:494	578	OC v7, Reset control for GPU 3, close miner right now if you want to use default control from Catalyst 
04:31:53:551	578	OC v7, Reset control for GPU 4, close miner right now if you want to use default control from Catalyst 
04:31:53:606	578	OC v7, Reset control for GPU 5, close miner right now if you want to use default control from Catalyst 
04:31:53:661	578	OC v7, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst 
04:31:53:717	578	OC v7, Reset control for GPU 7, close miner right now if you want to use default control from Catalyst 
04:31:53:720	578	srv bs: 0
04:31:53:723	578	sent: 207
04:31:54:230	4b4	recv: 66
04:31:54:233	4b4	srv pck: 65
04:31:54:593	4b4	OC v7, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst 
04:31:54:645	4b4	OC v7, Reset control for GPU 1, close miner right now if you want to use default control from Catalyst 
04:31:54:701	4b4	OC v7, Reset control for GPU 2, close miner right now if you want to use default control from Catalyst 
04:31:54:756	4b4	OC v7, Reset control for GPU 3, close miner right now if you want to use default control from Catalyst 
04:31:54:814	4b4	OC v7, Reset control for GPU 4, close miner right now if you want to use default control from Catalyst 
04:31:54:868	4b4	OC v7, Reset control for GPU 5, close miner right now if you want to use default control from Catalyst 
04:31:54:925	4b4	OC v7, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst 
04:31:54:981	4b4	OC v7, Reset control for GPU 7, close miner right now if you want to use default control from Catalyst 
04:31:54:982	4b4	srv bs: 0
04:31:54:984	4b4	sent: 207
04:31:55:247	10f8	OC v7, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst 
04:31:55:301	10f8	OC v7, Reset control for GPU 1, close miner right now if you want to use default control from Catalyst 
04:31:55:355	10f8	OC v7, Reset control for GPU 2, close miner right now if you want to use default control from Catalyst 
04:31:55:410	10f8	OC v7, Reset control for GPU 3, close miner right now if you want to use default control from Catalyst 
04:31:55:465	10f8	OC v7, Reset control for GPU 4, close miner right now if you want to use default control from Catalyst 
04:31:55:521	10f8	OC v7, Reset control for GPU 5, close miner right now if you want to use default control from Catalyst 
04:31:55:576	10f8	OC v7, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst 
04:31:55:631	10f8	OC v7, Reset control for GPU 7, close miner right now if you want to use default control from Catalyst 
04:31:55:795	1ef0	GPU0 DAG creation time - 4746 ms
04:31:55:797	1ef0	Setting DAG epoch #142 for GPU0 done
04:31:55:825	1608	GPU2 DAG creation time - 4747 ms
04:31:55:828	1608	Setting DAG epoch #142 for GPU2 done
04:31:55:838	564	GPU7 DAG creation time - 4756 ms
04:31:55:838	be0	GPU1 DAG creation time - 4756 ms
04:31:55:843	564	Setting DAG epoch #142 for GPU7 done
04:31:55:843	be0	Setting DAG epoch #142 for GPU1 done
04:31:55:869	11a0	GPU4 DAG creation time - 4774 ms
04:31:55:871	11a0	Setting DAG epoch #142 for GPU4 done
04:31:55:927	1c7c	GPU3 DAG creation time - 4816 ms
04:31:55:928	1c7c	Setting DAG epoch #142 for GPU3 done
04:31:55:951	1b4c	GPU5 DAG creation time - 4835 ms
04:31:55:952	1b4c	Setting DAG epoch #142 for GPU5 done
04:31:55:961	1ab0	GPU6 DAG creation time - 4845 ms
04:31:55:963	1ab0	Setting DAG epoch #142 for GPU6 done
04:31:57:384	1480	DCR: put share nonce 3a8a723 enonce 34005d
04:31:57:386	1480	DCR round found 1 shares
04:31:57:388	5fc	 DCR: 09/17/17-04:31:57 - SHARE FOUND - (GPU 6)
04:31:57:391	5fc	send: {"params": ["4KMiningRig.DCR_4KMiningRig", "e196", "000000000034005d77ff3d21", "59bdd082", "23a7a803"], "id": 4, "method": "mining.submit"}
04:31:57:566	5fc	got 36 bytes
04:31:57:568	5fc	buf: {"id":4,"result":true,"error":null}
04:31:57:571	5fc	parse packet: 35
04:31:57:574	5fc	 DCR: Share accepted (171 ms)!
04:31:57:577	5fc	new buf size: 0
04:31:58:251	1eac	recv: 66
04:31:58:254	1eac	srv pck: 65
04:31:58:924	548	ETH: checking pool connection...
04:31:58:926	548	send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
04:31:58:987	548	got 248 bytes
04:31:58:989	548	buf: {"id":3,"jsonrpc":"2.0","result":["0x6a72463ccc51109fa0bdae7095fb8bdea009b7c502d2f827513f17e03f356ecd","0xa91b532dbccf95bab5809616107474f25559efebc2974e2b22acae346634b49a","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x41577e"]}
04:31:58:991	548	parse packet: 247
04:31:58:993	548	ETH: job is the same
04:31:58:996	548	new buf size: 0
04:31:59:097	1e88	recv: 66
04:31:59:099	1eac	srv bs: 0
04:31:59:100	1e88	srv pck: 65
04:31:59:103	1eac	sent: 298
04:31:59:141	1608	ETH: put share nonce 3eda4c0052dd620
04:31:59:145	1608	ETH round found 1 shares
04:31:59:148	548	ETH: 09/17/17-04:31:59 - SHARE FOUND - (GPU 2)
04:31:59:151	548	send: {"id":4,"method":"eth_submitWork","params":["0x03eda4c0052dd620","0x6a72463ccc51109fa0bdae7095fb8bdea009b7c502d2f827513f17e03f356ecd","0x8dbba7f47a537fd435a4cddbe2edbaed7ed0237677e6d56593c41cef7ad890d2"]}
04:31:59:215	548	got 39 bytes
04:31:59:215	548	buf: {"id":4,"jsonrpc":"2.0","result":true}
04:31:59:216	548	parse packet: 38
04:31:59:217	548	ETH: Share accepted (62 ms)!
04:31:59:218	548	new buf size: 0
04:31:59:430	10f8	GPU 0 temp = 50, old fan speed = 0, new fan speed = 53 
04:31:59:504	10f8	GPU 1 temp = 47, old fan speed = 0, new fan speed = 51 
04:31:59:575	10f8	GPU 2 temp = 47, old fan speed = 0, new fan speed = 51 
04:31:59:647	10f8	GPU 3 temp = 51, old fan speed = 0, new fan speed = 53 
04:31:59:721	10f8	GPU 4 temp = 45, old fan speed = 0, new fan speed = 50 
04:31:59:793	10f8	GPU 5 temp = 47, old fan speed = 0, new fan speed = 51 
04:31:59:864	10f8	GPU 6 temp = 46, old fan speed = 0, new fan speed = 51 
04:31:59:972	10f8	GPU 7 temp = 46, old fan speed = 0, new fan speed = 51 
04:32:00:631	1e88	srv bs: 0
04:32:00:632	1e88	sent: 298
04:32:01:398	548	got 248 bytes
04:32:01:400	548	buf: {"id":0,"jsonrpc":"2.0","result":["0x3f8c3e8c8903d472105f9eb4ea2456c020cc6f4826736fa4270b728b2476c027","0xa91b532dbccf95bab5809616107474f25559efebc2974e2b22acae346634b49a","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x41577f"]}
04:32:01:403	548	parse packet: 247
04:32:01:405	548	ETH: job changed
04:32:01:407	548	new buf size: 0
04:32:01:409	548	ETH: 09/17/17-04:32:01 - New job from eu2.ethermine.org:4444
04:32:01:411	548	target: 0x0000000112e0be82 (diff: 4000MH), epoch 142(2.11GB)
04:32:01:414	548	ETH - Total Speed: 221.731 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:00
04:32:01:416	548	ETH: GPU0 27.668 Mh/s, GPU1 27.555 Mh/s, GPU2 27.685 Mh/s, GPU3 27.633 Mh/s, GPU4 27.660 Mh/s, GPU5 27.706 Mh/s, GPU6 28.226 Mh/s, GPU7 27.597 Mh/s
04:32:01:419	548	 DCR - Total Speed: 6651.936 Mh/s, Total Shares: 1, Rejected: 0
04:32:01:423	548	 DCR: GPU0 830.035 Mh/s, GPU1 826.643 Mh/s, GPU2 830.563 Mh/s, GPU3 829.000 Mh/s, GPU4 829.814 Mh/s, GPU5 831.188 Mh/s, GPU6 846.773 Mh/s, GPU7 827.920 Mh/s
04:32:02:165	1640	DCR: put share nonce 60fd5dd enonce 42390220
04:32:02:177	1640	DCR round found 1 shares
04:32:02:179	5fc	 DCR: 09/17/17-04:32:02 - SHARE FOUND - (GPU 0)
04:32:02:182	5fc	send: {"params": ["4KMiningRig.DCR_4KMiningRig", "e196", "000000004239022077ff3d21", "59bdd082", "ddd50f06"], "id": 4, "method": "mining.submit"}
04:32:02:243	5fc	got 36 bytes
04:32:02:245	5fc	buf: {"id":4,"result":true,"error":null}
04:32:02:247	5fc	parse packet: 35
04:32:02:249	5fc	 DCR: Share accepted (62 ms)!
04:32:02:251	5fc	new buf size: 0
04:32:03:085	1bf8	recv: 66
04:32:03:085	1bf8	srv pck: 65
04:32:03:230	10f8	GPU 0 temp = 48, old fan speed = 0, new fan speed = 43 
04:32:03:295	10f8	GPU 1 temp = 45, old fan speed = 0, new fan speed = 39 
04:32:03:360	10f8	GPU 2 temp = 44, old fan speed = 0, new fan speed = 39 
04:32:03:423	10f8	GPU 3 temp = 49, old fan speed = 0, new fan speed = 43 
04:32:03:492	10f8	GPU 4 temp = 44, old fan speed = 0, new fan speed = 38 
04:32:03:556	10f8	GPU 5 temp = 46, old fan speed = 0, new fan speed = 40 
04:32:03:622	10f8	GPU 6 temp = 43, old fan speed = 0, new fan speed = 38 
04:32:03:692	10f8	GPU 7 temp = 44, old fan speed = 0, new fan speed = 39 
04:32:04:098	1ae4	recv: 66
04:32:04:099	1ae4	srv pck: 65
04:32:04:357	1bf8	srv bs: 0
04:32:04:358	1bf8	sent: 298
04:32:05:028	1ae4	srv bs: 0
04:32:05:030	1ae4	sent: 298
04:32:07:029	10f8	GPU 0 temp = 49, old fan speed = 0, new fan speed = 33 
04:32:07:093	10f8	GPU 1 temp = 46, old fan speed = 0, new fan speed = 28 
04:32:07:162	10f8	GPU 2 temp = 45, old fan speed = 0, new fan speed = 27 
04:32:07:228	10f8	GPU 3 temp = 50, old fan speed = 0, new fan speed = 34 
04:32:07:298	10f8	GPU 4 temp = 45, old fan speed = 0, new fan speed = 26 
04:32:07:367	10f8	GPU 5 temp = 47, old fan speed = 0, new fan speed = 29 
04:32:07:438	10f8	GPU 6 temp = 44, old fan speed = 0, new fan speed = 26 
04:32:07:508	10f8	GPU 7 temp = 45, old fan speed = 0, new fan speed = 27 
04:32:07:631	548	got 248 bytes
04:32:07:633	548	buf: {"id":0,"jsonrpc":"2.0","result":["0xcf790b6628b83cb981c91fdb2bfaf974ede48af767b6935bb7f6945e146bdbc4","0xa91b532dbccf95bab5809616107474f25559efebc2974e2b22acae346634b49a","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x415780"]}
04:32:07:635	548	parse packet: 247
04:32:07:637	548	ETH: job changed
04:32:07:640	548	new buf size: 0
04:32:07:642	548	ETH: 09/17/17-04:32:07 - New job from eu2.ethermine.org:4444
04:32:07:645	548	target: 0x0000000112e0be82 (diff: 4000MH), epoch 142(2.11GB)
04:32:07:648	548	ETH - Total Speed: 221.665 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:00
04:32:07:651	548	ETH: GPU0 27.644 Mh/s, GPU1 27.634 Mh/s, GPU2 27.566 Mh/s, GPU3 27.671 Mh/s, GPU4 27.698 Mh/s, GPU5 27.696 Mh/s, GPU6 28.140 Mh/s, GPU7 27.615 Mh/s
04:32:07:654	548	 DCR - Total Speed: 6649.959 Mh/s, Total Shares: 2, Rejected: 0
04:32:07:657	548	 DCR: GPU0 829.316 Mh/s, GPU1 829.029 Mh/s, GPU2 826.976 Mh/s, GPU3 830.121 Mh/s, GPU4 830.948 Mh/s, GPU5 830.890 Mh/s, GPU6 844.214 Mh/s, GPU7 828.465 Mh/s
04:32:08:088	1db0	recv: 66
04:32:08:091	1db0	srv pck: 65
04:32:08:761	1db0	srv bs: 0
04:32:08:761	1db0	sent: 298
04:32:08:924	548	send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xd452915", "0x00000000000000000000000000000000000000000000000000000000f2a045a4"]}
04:32:08:941	548	ETH: checking pool connection...
04:32:08:942	548	send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
04:32:08:982	548	got 39 bytes
04:32:08:983	548	buf: {"id":6,"jsonrpc":"2.0","result":true}
04:32:08:984	548	parse packet: 38
04:32:08:986	548	new buf size: 0
04:32:09:042	548	got 248 bytes
04:32:09:043	548	buf: {"id":3,"jsonrpc":"2.0","result":["0xcf790b6628b83cb981c91fdb2bfaf974ede48af767b6935bb7f6945e146bdbc4","0xa91b532dbccf95bab5809616107474f25559efebc2974e2b22acae346634b49a","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x415780"]}
04:32:09:045	548	parse packet: 247
04:32:09:046	548	ETH: job is the same
04:32:09:047	548	new buf size: 0
04:32:09:097	1dc0	recv: 66
04:32:09:098	1dc0	srv pck: 65
04:32:09:767	1dc0	srv bs: 0
04:32:09:769	1dc0	sent: 298
04:32:09:894	1640	DCR: put share nonce 7107310 enonce 423904e0
04:32:09:896	1640	DCR round found 1 shares
04:32:09:899	5fc	 DCR: 09/17/17-04:32:09 - SHARE FOUND - (GPU 0)
04:32:09:901	5fc	send: {"params": ["4KMiningRig.DCR_4KMiningRig", "e196", "00000000423904e077ff3d21", "59bdd082", "10731007"], "id": 4, "method": "mining.submit"}
04:32:09:965	5fc	got 36 bytes
04:32:09:967	5fc	buf: {"id":4,"result":true,"error":null}
04:32:09:969	5fc	parse packet: 35
04:32:09:972	5fc	 DCR: Share accepted (62 ms)!
04:32:09:974	5fc	new buf size: 0
04:32:10:644	be0	DCR: put share nonce 6523908 enonce 6a700532
04:32:10:644	be0	DCR round found 1 shares
04:32:10:646	5fc	 DCR: 09/17/17-04:32:10 - SHARE FOUND - (GPU 1)
04:32:10:646	5fc	send: {"params": ["4KMiningRig.DCR_4KMiningRig", "e196", "000000006a70053277ff3d21", "59bdd082", "08395206"], "id": 4, "method": "mining.submit"}
04:32:10:708	5fc	got 36 bytes
04:32:10:708	5fc	buf: {"id":4,"result":true,"error":null}
04:32:10:709	5fc	parse packet: 35
04:32:10:710	5fc	 DCR: Share accepted (62 ms)!
04:32:10:710	5fc	new buf size: 0
04:32:10:823	10f8	GPU 0 temp = 50, old fan speed = 0, new fan speed = 25 
04:32:10:890	10f8	GPU 1 temp = 47, old fan speed = 0, new fan speed = 25 
04:32:10:957	10f8	GPU 2 temp = 47, old fan speed = 0, new fan speed = 25 
04:32:11:028	10f8	GPU 3 temp = 51, old fan speed = 0, new fan speed = 25 
04:32:11:092	10f8	GPU 4 temp = 46, old fan speed = 0, new fan speed = 25 
04:32:11:161	10f8	GPU 5 temp = 48, old fan speed = 0, new fan speed = 25 
04:32:11:229	10f8	GPU 6 temp = 45, old fan speed = 0, new fan speed = 25 
04:32:11:298	10f8	GPU 7 temp = 46, old fan speed = 0, new fan speed = 25 
04:32:11:355	144c	DCR: put share nonce 33adbf3 enonce 95660575
04:32:11:357	144c	DCR round found 1 shares
04:32:11:359	5fc	 DCR: 09/17/17-04:32:11 - SHARE FOUND - (GPU 2)
04:32:11:362	5fc	send: {"params": ["4KMiningRig.DCR_4KMiningRig", "e196", "000000009566057577ff3d21", "59bdd082", "f3db3a03"], "id": 4, "method": "mining.submit"}
04:32:11:426	5fc	got 36 bytes
04:32:11:428	5fc	buf: {"id":4,"result":true,"error":null}
04:32:11:430	5fc	parse packet: 35
04:32:11:432	5fc	 DCR: Share accepted (63 ms)!
04:32:11:434	5fc	new buf size: 0
04:32:13:119	488	recv: 66
04:32:13:122	488	srv pck: 65
04:32:13:798	488	srv bs: 0
04:32:13:800	488	sent: 298
04:32:13:912	1e14	DCR: put share nonce 3bd2743 enonce f7c2064a
04:32:13:916	1e14	DCR round found 1 shares
04:32:13:919	5fc	 DCR: 09/17/17-04:32:13 - SHARE FOUND - (GPU 5)
04:32:13:921	5fc	send: {"params": ["4KMiningRig.DCR_4KMiningRig", "e196", "00000000f7c2064a77ff3d21", "59bdd082", "4327bd03"], "id": 4, "method": "mining.submit"}
04:32:14:011	5fc	got 36 bytes
04:32:14:011	5fc	buf: {"id":4,"result":true,"error":null}
04:32:14:012	5fc	parse packet: 35
04:32:14:012	5fc	 DCR: Share accepted (94 ms)!
04:32:14:013	5fc	new buf size: 0
04:32:14:112	1448	recv: 66
04:32:14:113	1448	srv pck: 65
04:32:14:765	1448	srv bs: 0
04:32:14:768	1448	sent: 298
04:32:15:096	10f8	GPU 0 temp = 51, old fan speed = 0, new fan speed = 25 
04:32:15:161	10f8	GPU 1 temp = 49, old fan speed = 0, new fan speed = 25 
04:32:15:226	10f8	GPU 2 temp = 49, old fan speed = 0, new fan speed = 25 
04:32:15:292	10f8	GPU 3 temp = 52, old fan speed = 0, new fan speed = 25 
04:32:15:357	10f8	GPU 4 temp = 47, old fan speed = 0, new fan speed = 25 
04:32:15:423	10f8	GPU 5 temp = 49, old fan speed = 0, new fan speed = 25 
04:32:15:487	10f8	GPU 6 temp = 45, old fan speed = 0, new fan speed = 25 
04:32:15:552	10f8	GPU 7 temp = 47, old fan speed = 0, new fan speed = 25 
04:32:15:876	1440	OC v7, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst 
04:32:15:931	1440	OC v7, Reset control for GPU 1, close miner right now if you want to use default control from Catalyst 
04:32:15:986	1440	OC v7, Reset control for GPU 2, close miner right now if you want to use default control from Catalyst 
04:32:16:041	1440	OC v7, Reset control for GPU 3, close miner right now if you want to use default control from Catalyst 
04:32:16:095	1440	OC v7, Reset control for GPU 4, close miner right now if you want to use default control from Catalyst 
04:32:16:149	1440	OC v7, Reset control for GPU 5, close miner right now if you want to use default control from Catalyst 
04:32:16:205	1440	OC v7, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst 
04:32:16:264	1440	OC v7, Reset control for GPU 7, close miner right now if you want to use default control from Catalyst

Since the above graph is too zoomed out, here you can see a zoomed in cut from that incident where you can see that after that spike, my rig froze:

The other spikes you see on the main graph on top are the same case (those 1800+watts made me skip a heart beat when I saw them).

So, in the end of the graph you see stability. This is the most continuous period I have managed to run my rig for with the blockchain drivers. The fun part is how I did it:
I changed:

Code:

-cvddc 875

into

Code:

-cvddc 850

........

Such a lame ending for such a big torture I have been through... I changed that in order to reduce my power consumption so my spikes would be withing my PSUs capabilities, and while I did that, no more spikes!

So that was it. I have been running stable since then, I sacrificed 10Mhz of my -cclock in order to keep up with the 25mV reduction on -cvddc so I lost a bit of speed, but at last I don't have to wake up every 2 hours or so to check on my baby-rig.....

Conclusion:
My "verdict" is that sometimes when the miner starts it causes a power consumption spike, which may be above your rig's max power. For me it happened almost always after a connection loss and sometimes after a gpu hang.
If you experience rig freezes with blockchain drivers and Claymore v.10.0, the miner could be causing spikes that are beyond your PSUs capabilities

P.S.1: In the graph you can see that in the middle of my "stable period" the power consumption got up a bit. This is because I initially dropped my -cvddc to 840 before I decide to step it up to 850.

P.S.2: The freeze issue was happening on the following equipment:

Quote from: kkourmousis on September 05, 2017, 02:10:55 AM

My rig:

ASUZ Prime Z270-P
8x RX 580 8GB Nitro+ (Hynix)
Windows 10
Blockchain Beta Official Drivers
Claymore Dual Miner v.10.0
Modded BIOS, OC through Claymore @162w from the wall per card
Dual mining ETH (233 Mh/s) +DCR (7000 Mh/s)

and with the following miner parameters:
-esm 0 -estale 0 -asm 1 -dcri 30 -cclock 1140 -cvddc 875 -mclock 2100 -mvddc 850 -tstop 80 -tt 70 -fanmin 15 -fanmax 85 -mode 0 (These are my parameters before I applied the solution I describe above. Also, -mclock 2100 was +/-30 for some of my gpus)

P.S.3. Sorry for the long post... Keep in mind that it was a hell of a lot longer for me Wink

eforius

newbie

Activity: 5

Merit: 0

@kkourmousis,
power doesnot seem to be the issue. I have the same thing with my rig and tested it with 2 and 3 GPUs and it still freezzes

kkourmousis

member

Activity: 119

Merit: 10

Quote from: Claymore on September 17, 2017, 03:09:09 PM

I need to know Windows version, GPU model and drivers version to be able to reproduce this issue.

Well you can have mine..

I am struggling on resolving both of the 2 listed problems below, I have found a solution for the second, I will post more info soon

Quote from: kkourmousis on September 05, 2017, 02:10:55 AM

So I have been using the latest Claymore version since it came out.

My rig:

ASUZ Prime Z270-P
8x RX 580 8GB Nitro+ (Hynix)
Windows 10
Blockchain Beta Official Drivers
Claymore Dual Miner v.10.0
Modded BIOS, OC through Claymore @162w from the wall per card
Dual mining ETH (233 Mh/s) +DCR (7000 Mh/s)

I am overall happy with the new update, but I have had some issues:

Sometimes miner can't reach maximum speed. I open the miner, clocks and voltages are being set properly but hashrate lies in the 225mh/s area. A simple miner restart resolves the issue
Computer freezes. This has happened 2 times in my rig and 1 time in my PC (same setup with 1 gpu only) in the last 2 days. Here is the last part of the log @Claymore in case you find something interesting here

Btw, the problem that miner does not reach maximum speed on first run after restart is PERMANENT for me, it happens on almost every restart.

Claymore

donator

Activity: 1610

Merit: 1325

Miners developer

Quote from: PPB on September 17, 2017, 08:04:36 AM

First post in this forum, just to say good job Claymore on the 10.0 version, it seems to take really well the clock and voltage options now if paired with AMD GPUs and the blockchain driver.

I would like to ask Claymore 2 questions:

- I have probably have run into a little issue in regards to core voltage settings with the miner. I have one GPU that when set to non-rounded voltage values (as the GPU only recognizes 6.25mv steps, this means all the voltage values that arent x25mv, x50mv, x75mv and x00mv) it misheaves pretty quickly and has OCL thread hang just a minute after starting mining (DAG is already loaded and no EDC errors are shown. If I use rounded values, it seems to take them better and if a OCL thread hang happens, it happens after several hours and probably blamed to memory clock instability.

- As you know, the clock and voltage control API from AMD has a mechanism built in that in the end reduces performance very time you touch any core/mem voltage/clock values if they were changed AFTER the GPU entered, even if for just a little moment, in maximum core and memory Pstate. I have seen when doing the OC/UV settings with your miner that the settings I put are enforced just before the DAG loads, but still with soft monitoring the GPUs enter for a brief period in max clock/voltages before that, causing that any clock/volt setting enforced by the miner, if it happens to change an existing value (this doesnt happen at all if the GPU had these values since last reboot), it enters in this "reduced performance mode" and thus hashrate is lower than you should. Is there any chance that the voltage/clock options are enforced first of all, so this behaviour doesnt happen? Because every time I have a OCL thead/hang, I have to do 2 reboots, the first one automatic from the miner and the second one to have the clock/volt dialed in a first time so the next reboot the GPUs dont enter in this "lower performance mode". i know i could just bios flash all the OC/UV/fan settings, but im still at finding the best OC/UV settings for each gpu, and I would like to nail them via driver changes rather than BIOS modding yet.

All in all very satisfied with this new version.

Thanks in advance!

Quote from: ivanpop on September 17, 2017, 01:57:21 PM

I'm running v10 and the overclocking and voltage control are pretty great features, but they need some more work.
I have a very strange problem. Most of the time, when I power on the rig and start Claymore, the cards appear to be clocked to the correct frequencies set in the .bat file, but they mine with the hashrate of stock clocks. I have to stop Claymore and start it again for the cards to mine properly. For example, at stock speeds (1265/1750mhz) they mine with 24mh and at 1100/2050 they mine with 29mh. On the first run, gpu-z shows 1100/2050 clocks but the cards mine at 24mh. When I restart Claymore, the cards are at 1100/2050 again but they mine with 29mh. Also, sometimes the voltages don't change accordingly, so every time I have to check the voltages with gpu-z, to see if everything is correct and this kinda blows the idea of having a fast way to restart a miner and have him up and running in no time. I know other people that have the same problems. Hope that this gets fixed soon, since this automatic overclocking from Claymore is an extremely helpful and easy way to overclock.

I need to know Windows version, GPU model and drivers version to be able to reproduce this issue.

DonCaffe

newbie

Activity: 3

Merit: 0

Excellent programming work Claymore. Keep it up.

Gordon Freid

newbie

Activity: 5

Merit: 0

suport ipv6 ?

Temporel

full member

Activity: 224

Merit: 100

Quote from: paagrio on September 17, 2017, 02:13:36 PM

Is anyone also has issues with forced Windows Update "NVIDIA - Display 23.21.13.8768"

It installs authomaticaly and breaks mining.
After that I need to manualy rollback to 385.41

disable autoupdate. If Windows 10, use gpedit.msc

ivanpop

newbie

Activity: 62

Merit: 0

Why do you have a running windows update on a mining rig on the first place?

paagrio

newbie

Activity: 4

Merit: 0

Is anyone also has issues with forced Windows Update "NVIDIA - Display 23.21.13.8768"

It installs authomaticaly and breaks mining.
After that I need to manualy rollback to 385.41

ivanpop

newbie

Activity: 62

Merit: 0

I'm running v10 and the overclocking and voltage control are pretty great features, but they need some more work.
I have a very strange problem. Most of the time, when I power on the rig and start Claymore, the cards appear to be clocked to the correct frequencies set in the .bat file, but they mine with the hashrate of stock clocks. I have to stop Claymore and start it again for the cards to mine properly. For example, at stock speeds (1265/1750mhz) they mine with 24mh and at 1100/2050 they mine with 29mh. On the first run, gpu-z shows 1100/2050 clocks but the cards mine at 24mh. When I restart Claymore, the cards are at 1100/2050 again but they mine with 29mh. Also, sometimes the voltages don't change accordingly, so every time I have to check the voltages with gpu-z, to see if everything is correct and this kinda blows the idea of having a fast way to restart a miner and have him up and running in no time. I know other people that have the same problems. Hope that this gets fixed soon, since this automatic overclocking from Claymore is an extremely helpful and easy way to overclock.

Bob_chemist

newbie

Activity: 28

Merit: 0

@Claymore,

is there a chance that EthMan running on another computer somehow affects miner?

Miner itself is not very stable, but I noticed that without monitoring it works for hours, but when monitoring is on, it crashes sometimes within minutes and never work more than 1.10 hour.
Or it's just a coincidence?

FaithlessCoinMob

newbie

Activity: 5

Merit: 0

Quote from: androstan1234 on September 16, 2017, 10:45:14 AM

I've been struggling to get my rig to work for two weeks. It was mining fine 24/7 for days at a time. Then it froze, and ever since then it'll mine for a minute, two cards will go to zero hash rate, and Windows freezes. Tried reinstalling drivers. Connecting them in various orders. No one card seems to be causing the problem. I'm at a loss here and this thing is sucking up all my time.

Win10, rx580s (one 480). 1000W evga psu. Biostar mobo

I've had rigs run for days or even weeks and then out of nowhere behave like that. Unplug all your sata cables from the psu and see if any of them are damaged/melted.

justinjja

newbie

Activity: 44

Merit: 0

Does everyone have issues with the blockchain dirvers where the miner sometimes gets stuck in 2D mode until claymore is restarted?
Lately, the eth mining speed with drop from 29.5 to about 7mh/s, sometimes it is all cards, but sometimes it is only one or 2 cards.

PPB

newbie

Activity: 3

Merit: 0

First post in this forum, just to say good job Claymore on the 10.0 version, it seems to take really well the clock and voltage options now if paired with AMD GPUs and the blockchain driver.

I would like to ask Claymore 2 questions:

- I have probably have run into a little issue in regards to core voltage settings with the miner. I have one GPU that when set to non-rounded voltage values (as the GPU only recognizes 6.25mv steps, this means all the voltage values that arent x25mv, x50mv, x75mv and x00mv) it misheaves pretty quickly and has OCL thread hang just a minute after starting mining (DAG is already loaded and no EDC errors are shown. If I use rounded values, it seems to take them better and if a OCL thread hang happens, it happens after several hours and probably blamed to memory clock instability.

- As you know, the clock and voltage control API from AMD has a mechanism built in that in the end reduces performance very time you touch any core/mem voltage/clock values if they were changed AFTER the GPU entered, even if for just a little moment, in maximum core and memory Pstate. I have seen when doing the OC/UV settings with your miner that the settings I put are enforced just before the DAG loads, but still with soft monitoring the GPUs enter for a brief period in max clock/voltages before that, causing that any clock/volt setting enforced by the miner, if it happens to change an existing value (this doesnt happen at all if the GPU had these values since last reboot), it enters in this "reduced performance mode" and thus hashrate is lower than you should. Is there any chance that the voltage/clock options are enforced first of all, so this behaviour doesnt happen? Because every time I have a OCL thead/hang, I have to do 2 reboots, the first one automatic from the miner and the second one to have the clock/volt dialed in a first time so the next reboot the GPUs dont enter in this "lower performance mode". i know i could just bios flash all the OC/UV/fan settings, but im still at finding the best OC/UV settings for each gpu, and I would like to nail them via driver changes rather than BIOS modding yet.

All in all very satisfied with this new version.

Thanks in advance!

redectro

jr. member

Activity: 51

Merit: 1

The main advantage of this miner is the stability of it's operation! One of my rigs is running two instances; two 270x are running with v2.0, and two 7950 are running with v3.1, 100% shares accepted on Dwarf's pool and a nice speed increment.

But just now, my two instances created the new DAG file (epoch #47) and none of them crashed! Amazing! With the other ETH miners, almost every DAG change was a problem, but with this miner it's just a minor bump for my rigs!Keep up the good work Claymore!

mycryptostats

full member

Activity: 185

Merit: 103

Hi everyone. I created a crypto dashboard for myself as I was tired of keeping track of all my coins on a spreadsheet. I have expanded it a bit so other people can use it too. Maybe it will add value for you.
Check it out at https://mycryptostats.com
Any bug reports or requests can be done on our forum https://bitcointalksearch.org/topic/my-crypto-stats-crypto-currency-dashboard-2183937

Marvell2

full member

Activity: 1148

Merit: 132

that might be the cuase of your problem , but i have a rig on a single 1300 watt gold psu that the cards go to
8mhz frim 29.7 after connection lost , only after i did the blockchain drivers, I dont think your cause affects all cases

kkourmousis

member

Activity: 119

Merit: 10

So we have more people with what I believe is the same problem

Quote from: thaelin on September 16, 2017, 06:41:51 AM

Hi all:
   I have been quiet and doing a bit of experimenting with many of the different versions of Claymore. I just did a test of a card that would run say for 6 hours and then lose connection and drop out. The other card with it would stay mining just fine. Did this 6 times to make sure what I was seeing to be true.
   I then took said card to a different miner and one of them to said miner. Now all works fine. I see that some cards just will not work together but will with others. So I feel strongly to say that if you have a rouge card, put it in a different machine and it may correct your problems. May not.
   My proof is in the puddin so to speak.

Quote from: androstan1234 on September 16, 2017, 10:45:14 AM

I've been struggling to get my rig to work for two weeks. It was mining fine 24/7 for days at a time. Then it froze, and ever since then it'll mine for a minute, two cards will go to zero hash rate, and Windows freezes. Tried reinstalling drivers. Connecting them in various orders. No one card seems to be causing the problem. I'm at a loss here and this thing is sucking up all my time.

Win10, rx580s (one 480). 1000W evga psu. Biostar mobo.

I am happy to let you know that I think I have found the cause of the problem. I yet have to test it for a few more hours, but it seems that the "Freeze problem" after connection lost and sometimes after a gpu hangs, it is all because of Power consumption

I myself have 2x750watt PSU and before blockchain drivers I was drawing 1330watts from the wall. With the blockchain drivers I was drawing 1400watts.

Now that I got physical access to my rig, I was able to perform some tests and what I found is that when the miner starts up, the power consumption skyrockets for a few seconds.

This will happen on the 1st time the miner starts, but it will also happen after a connection loss (when the connection gets restored I guess) or a miner restart due to a GPU hang

I saw that "freeze" happening in front of me and I was amazed to see that half of my GPUs that drew power from the same PSU were turned off while the others kept working!

I have graph data and logs to back this up, I will post later this day probably. For now I have to let it run in order to see if my solution works: lowering voltages just a tiny bit more, enough to get me back on the 1300watt consumption area.

So if you guys are like me, you like to have your PSU consumption close to its efficiency peak (90-92%) and you are experiencing freezes during startup or after connection loss, a 10% spike might be responsible for switching off your PSUs

FYI:
"Parent" post here

Ursul0

sr. member

Activity: 857

Merit: 262

Quote from: androstan1234 on September 16, 2017, 10:45:14 AM

I've been struggling to get my rig to work for two weeks. It was mining fine 24/7 for days at a time. Then it froze, and ever since then it'll mine for a minute, two cards will go to zero hash rate, and Windows freezes. Tried reinstalling drivers. Connecting them in various orders. No one card seems to be causing the problem. I'm at a loss here and this thing is sucking up all my time.

Win10, rx580s (one 480). 1000W evga psu. Biostar mobo.

1) DDU in safe mode
2) Power down, disconnect AC, turn on the power
3) install drv (point and click to driver dir on each device)
4) lower core and mem clocks to something very safe like 1080:1900@888mv
5) if still having issues, disconnect all connectors, and connect back, especially power in raisers (move molexes around)

also if you had it working changing the order of cards is something you should not do.

mikkowendell

newbie

Activity: 41

Merit: 0

Quote from: androstan1234 on September 16, 2017, 10:45:14 AM

I've been struggling to get my rig to work for two weeks. It was mining fine 24/7 for days at a time. Then it froze, and ever since then it'll mine for a minute, two cards will go to zero hash rate, and Windows freezes. Tried reinstalling drivers. Connecting them in various orders. No one card seems to be causing the problem. I'm at a loss here and this thing is sucking up all my time.

Win10, rx580s (one 480). 1000W evga psu. Biostar mobo.

hi there, just wanna ask, did you fix your problem? windows freeze? I got the same issue, my rig was working great two days ago but yesterday it just started to freeze. i know this is not the mobo, gpu, riser thing because I have been doing the troubleshoot since the problem starts, (changing of risers, exchanging pcie slots, changing the CM versions from v10 down to v6 but still no luck.

I hope we could help other here.

WIN10
MOBO z87 Deluxe
4x r9 290
1x r9 390
PSU 1050w + 750w
RAM 16gb

Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 594. (Read 6590757 times)