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

[DUzP7sBr]

the reason is not important. do not use miner restart. AMD drivers is the major factor anyways. Instead do system reboot using "-r 1" flag and reboot.bat (in the same folder) with the following content: "shutdown /r /t 5 /f".

I have created reboot.sh with "reboot -f" command in Claymore's program folder.
But problem ist if I test it:
sudo reboot -f
or
sudo shutdown -r
the rig does not reboot but it freezes with black screen instead. I have to physically switch off the power to start it again.

[1714111680]

1714111680

[1714111680]

1714111680

[1714111680]

1714111680

[1714111680]

1714111680

[1714111680]

1714111680

[abhiseshakana]

I have noticed one of my mining rig stop or restart every so often and I was wondering if anyone could help me find a solution to this problem.

This is my bat file

Code:

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 us-east.ethash-hub.miningpoolhub.com:20535 -ewal arkalab.eth01 -eworker arkalab.eth01 -epsw x -esm 2 -mode 1 -platform 2 -cclock -200,-200,-200,-200,-200,-200 -mclock +650,+650,+650,+600,+600,+600 -powlim -30,-30,-30,-30,-30,-30 -tt -70,-70,-70,-70,-80,-85
pause

and this is my Log File for the issue

Code:

05:32:29:039	3d8	ETH: 05/13/18-05:32:29 - New job from us-east.ethash-hub.miningpoolhub.com:20535
05:32:29:041	3d8	target: 0x00000000ffb34c02 (diff: 4300MH), epoch 186(2.45GB)
05:32:29:043	3d8	ETH - Total Speed: 214.160 Mh/s, Total Shares: 6, Rejected: 0, Time: 00:02
05:32:29:045	3d8	ETH: GPU0 32.990 Mh/s, GPU1 33.097 Mh/s, GPU2 33.111 Mh/s, GPU3 31.570 Mh/s, GPU4 51.967 Mh/s, GPU5 31.426 Mh/s
05:32:29:473	212c	checked ETH share on CPU, spent 5ms
05:32:29:475	212c	sent: {"id": 12, "method": "mining.submit", "params": ["arkalab.eth01","e00e","0x855cbfac0099e783","0x8aa4b6811007cfcbcc6f3dce84fc9d2b67defc1c42c7a265a2be7f69ccc39de8","0x8ed1fe8e7a45e7cc250afd976c2b9ecb246f627904589cd8b1fd46920f7099ac"]}

05:32:29:477	212c	ETH: put share nonce 855cbfac0099e783
05:32:29:481	3d8	ETH: 05/13/18-05:32:29 - SHARE FOUND - (GPU 2)
05:32:29:721	3d8	buf: {"id":12,"result":true,"error":null}

05:32:29:722	3d8	ETH: Share accepted (250 ms)!

05:32:42:908	e7c	GPU 5, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:913	e7c	GPU 5, GpuMiner kx failed 1
05:32:42:915	e7c	Set global fail flag, failed GPU5
05:32:42:917	e7c	GPU 5 failed
05:32:42:919	252c	GPU 5, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:925	252c	GPU 5, GpuMiner kx failed 1
05:32:42:928	19c0	GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:930	212c	GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:927	252c	Set global fail flag, failed GPU5
05:32:42:937	252c	GPU 5 failed
05:32:42:941	212c	GPU 2, GpuMiner kx failed 1
05:32:42:948	19c0	GPU 0, GpuMiner kx failed 1
05:32:42:947	212c	Set global fail flag, failed GPU2
05:32:42:954	e8c	GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:952	19c0	Set global fail flag, failed GPU0
05:32:42:958	212c	GPU 2 failed
05:32:42:964	1b9c	GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:967	e8c	GPU 1, GpuMiner kx failed 1
05:32:42:970	19c0	GPU 0 failed
05:32:42:972	1f44	GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:974	1b9c	GPU 2, GpuMiner kx failed 1
05:32:42:976	2790	GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:980	2790	GPU 4, GpuMiner kx failed 1
05:32:42:985	2790	Set global fail flag, failed GPU4
05:32:42:988	2790	GPU 4 failed
05:32:42:976	1b9c	Set global fail flag, failed GPU2
05:32:42:979	3d8	sent: {"id":6,"worker":"arkalab.eth01","jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6f5f8bc", "0x0000000000000000000000000000000000000000000000000000000016477d18"]}

05:32:42:970	e8c	Set global fail flag, failed GPU1
05:32:42:995	e8c	GPU 1 failed
05:32:42:999	2494	GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:43:002	2328	GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:43:008	1b9c	GPU 2 failed
05:32:43:014	1f44	GPU 0, GpuMiner kx failed 1
05:32:43:020	1f44	Set global fail flag, failed GPU0
05:32:43:029	1f44	GPU 0 failed
05:32:43:032	2328	GPU 4, GpuMiner kx failed 1
05:32:43:039	2b4	GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:43:041	2494	GPU 3, GpuMiner kx failed 1
05:32:43:038	2328	Set global fail flag, failed GPU4
05:32:43:047	2328	GPU 4 failed
05:32:43:044	2494	Set global fail flag, failed GPU3
05:32:43:054	2b4	GPU 1, GpuMiner kx failed 1
05:32:43:063	2494	GPU 3 failed
05:32:43:070	2588	GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:43:062	2b4	Set global fail flag, failed GPU1
05:32:43:079	2588	GPU 3, GpuMiner kx failed 1
05:32:43:085	2b4	GPU 1 failed
05:32:43:085	2588	Set global fail flag, failed GPU3
05:32:43:089	2588	GPU 3 failed
05:32:43:221	3d8	buf: {"id":6,"result":true,"error":null}

05:32:43:934	bb0	em hbt: 0, fm hbt: 78, 
05:32:43:935	bb0	watchdog - thread 0 (gpu0), hb time 1188
05:32:43:936	bb0	watchdog - thread 1 (gpu0), hb time 1063
05:32:43:938	bb0	watchdog - thread 2 (gpu1), hb time 1110
05:32:43:939	bb0	watchdog - thread 3 (gpu1), hb time 1235
05:32:43:940	bb0	watchdog - thread 4 (gpu2), hb time 1172
05:32:43:942	bb0	watchdog - thread 5 (gpu2), hb time 1047
05:32:43:943	bb0	watchdog - thread 6 (gpu3), hb time 1063
05:32:43:945	bb0	watchdog - thread 7 (gpu3), hb time 1188
05:32:43:946	bb0	watchdog - thread 8 (gpu4), hb time 1188
05:32:43:947	bb0	watchdog - thread 9 (gpu4), hb time 1047
05:32:43:949	bb0	watchdog - thread 10 (gpu5), hb time 1406
05:32:43:950	bb0	watchdog - thread 11 (gpu5), hb time 1953
05:32:43:951	bb0	WATCHDOG: GPU error, you need to restart miner :( 
05:32:45:414	bb0	Restarting OK, exit...

And how to put the right value for -eres function.The default value is 2, but i dont know what the effect if i increase or decrease the value through this -eres command line

[DeDeRa]

6x Sapphire Nitro+ RX 580 8GB with Micron memory clocked at 1170/2200MHz with 850/850mv and -20% power limit doing 192.9 mhs eth at little under 810w. Using the nanopool i get average hashrates over the reported ones. (usually, 4 out of 7 days, in the rest, really close to reported, max 10 mhs less)
PS: Check the GPUz reported consumption. 80w... Also check my highest temps which are 51 and 52* degrees celcius with the fan at only 37% in a warm room, around 25* today, for example. One last thing, no incorrect shares, not even 1 memory error reported in hwinfo, not one.

https://image.ibb.co/bygsTy/32324939_1663807277070731_5687913318526746624_o.jpg
https://image.ibb.co/euOjad/32416549_1663806050404187_7786284067036594176_n.jpg
https://image.ibb.co/hQ2cvd/32423238_1663806450404147_7487452397338361856_n.jpg

[alizali]

why -cvddc does not effect on AMD cards in windows?

any reason

yes there is reason

if you know the reason say it
DO NOT SPAM

why -cvddc does not effect on AMD cards in windows?

any reason

Please be more specific. What Windows? What cards? What drivers?
On my Windows 10 x64 Pro AMD 18.3.4 on RX 580 cvddc works. On 270X didn't work.

windows 10 X64
AMD 22.19.695   (blockchain driver)
rx 470

[spyfly]

6x Sapphire Nitro+ RX 580 8GB with Micron memory clocked at 1170/2200MHz with 850/850mv and -20% power limit doing 192.9 mhs eth at little under 810w. Using the nanopool i get average hashrates over the reported ones. (usually, 4 out of 7 days, in the rest, really close to reported, max 10 mhs less)
PS: Check the GPUz reported consumption. 80w... Also check my highest temps which are 51 and 52* degrees celcius with the fan at only 37% in a warm room, around 25* today, for example. One last thing, no incorrect shares, not even 1 memory error reported in hwinfo, not one.

https://image.ibb.co/bygsTy/32324939_1663807277070731_5687913318526746624_o.jpg
https://image.ibb.co/euOjad/32416549_1663806050404187_7786284067036594176_n.jpg
https://image.ibb.co/hQ2cvd/32423238_1663806450404147_7487452397338361856_n.jpg

what device do you have to meassure de electrical power

[UnclWish]

why -cvddc does not effect on AMD cards in windows?

any reason

yes there is reason

if you know the reason say it
DO NOT SPAM

why -cvddc does not effect on AMD cards in windows?

any reason

Please be more specific. What Windows? What cards? What drivers?
On my Windows 10 x64 Pro AMD 18.3.4 on RX 580 cvddc works. On 270X didn't work.

windows 10 X64
AMD 22.19.695   (blockchain driver)
rx 470

Use 18.3.4. driver with ati dirvers patcher.

[DeDeRa]

TPLink HS110 dude.

[WhackOBill]

Claymore 11.7 has been running well for me with only the occasional slowdown of card for a couple of minutes only to pick back up to speed.

My only problem is that I can't reliably STOP the program.  I get a BSD from a driver fault whenever I try to stop.  I've tried most of this year's drivers from the 18.2 in Feb to the one before the latest.  I'm in no hurry to be current on my driver under Win10 but I am looking for that stability.  No memory errors and nothing crazy in the overclocking realm.  I'm about 28.5MHs on each of my 580s.

I do use DDU in Safe Mode when I switch drivers to get the cleanest possible install.

Any thoughts about where to look?

[spyfly]

TPLink HS110 dude.

thanks!
https://www.amazon.es/gp/product/B017X72IES/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1

[BS001]

Is it normal that the rig would crash after some time if I mix hynix and elpida GPUs?

I have 4 Sapphire Nitro+ 570 with elpida memory and 2 Sapphire Nitro+ 570 with hynix memory... if I run them separately then rig is stable, but as soon as I start to mix GPUs with different memory types on one rig... I would see crashes, reboots, etc...

is that normal? Any ideas? 

[AzzAz]

I have noticed one of my mining rig stop or restart every so often and I was wondering if anyone could help me find a solution to this problem.

This is my bat file

Code:

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 us-east.ethash-hub.miningpoolhub.com:20535 -ewal arkalab.eth01 -eworker arkalab.eth01 -epsw x -esm 2 -mode 1 -platform 2 -cclock -200,-200,-200,-200,-200,-200 -mclock +650,+650,+650,+600,+600,+600 -powlim -30,-30,-30,-30,-30,-30 -tt -70,-70,-70,-70,-80,-85
pause

and this is my Log File for the issue

Code:

05:32:29:039	3d8	ETH: 05/13/18-05:32:29 - New job from us-east.ethash-hub.miningpoolhub.com:20535
05:32:29:041	3d8	target: 0x00000000ffb34c02 (diff: 4300MH), epoch 186(2.45GB)
05:32:29:043	3d8	ETH - Total Speed: 214.160 Mh/s, Total Shares: 6, Rejected: 0, Time: 00:02
05:32:29:045	3d8	ETH: GPU0 32.990 Mh/s, GPU1 33.097 Mh/s, GPU2 33.111 Mh/s, GPU3 31.570 Mh/s, GPU4 51.967 Mh/s, GPU5 31.426 Mh/s
05:32:29:473	212c	checked ETH share on CPU, spent 5ms
05:32:29:475	212c	sent: {"id": 12, "method": "mining.submit", "params": ["arkalab.eth01","e00e","0x855cbfac0099e783","0x8aa4b6811007cfcbcc6f3dce84fc9d2b67defc1c42c7a265a2be7f69ccc39de8","0x8ed1fe8e7a45e7cc250afd976c2b9ecb246f627904589cd8b1fd46920f7099ac"]}

05:32:29:477	212c	ETH: put share nonce 855cbfac0099e783
05:32:29:481	3d8	ETH: 05/13/18-05:32:29 - SHARE FOUND - (GPU 2)
05:32:29:721	3d8	buf: {"id":12,"result":true,"error":null}

05:32:29:722	3d8	ETH: Share accepted (250 ms)!

05:32:42:908	e7c	GPU 5, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:913	e7c	GPU 5, GpuMiner kx failed 1
05:32:42:915	e7c	Set global fail flag, failed GPU5
05:32:42:917	e7c	GPU 5 failed
05:32:42:919	252c	GPU 5, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:925	252c	GPU 5, GpuMiner kx failed 1
05:32:42:928	19c0	GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:930	212c	GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:927	252c	Set global fail flag, failed GPU5
05:32:42:937	252c	GPU 5 failed
05:32:42:941	212c	GPU 2, GpuMiner kx failed 1
05:32:42:948	19c0	GPU 0, GpuMiner kx failed 1
05:32:42:947	212c	Set global fail flag, failed GPU2
05:32:42:954	e8c	GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:952	19c0	Set global fail flag, failed GPU0
05:32:42:958	212c	GPU 2 failed
05:32:42:964	1b9c	GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:967	e8c	GPU 1, GpuMiner kx failed 1
05:32:42:970	19c0	GPU 0 failed
05:32:42:972	1f44	GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:974	1b9c	GPU 2, GpuMiner kx failed 1
05:32:42:976	2790	GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:980	2790	GPU 4, GpuMiner kx failed 1
05:32:42:985	2790	Set global fail flag, failed GPU4
05:32:42:988	2790	GPU 4 failed
05:32:42:976	1b9c	Set global fail flag, failed GPU2
05:32:42:979	3d8	sent: {"id":6,"worker":"arkalab.eth01","jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6f5f8bc", "0x0000000000000000000000000000000000000000000000000000000016477d18"]}

05:32:42:970	e8c	Set global fail flag, failed GPU1
05:32:42:995	e8c	GPU 1 failed
05:32:42:999	2494	GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:43:002	2328	GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:43:008	1b9c	GPU 2 failed
05:32:43:014	1f44	GPU 0, GpuMiner kx failed 1
05:32:43:020	1f44	Set global fail flag, failed GPU0
05:32:43:029	1f44	GPU 0 failed
05:32:43:032	2328	GPU 4, GpuMiner kx failed 1
05:32:43:039	2b4	GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:43:041	2494	GPU 3, GpuMiner kx failed 1
05:32:43:038	2328	Set global fail flag, failed GPU4
05:32:43:047	2328	GPU 4 failed
05:32:43:044	2494	Set global fail flag, failed GPU3
05:32:43:054	2b4	GPU 1, GpuMiner kx failed 1
05:32:43:063	2494	GPU 3 failed
05:32:43:070	2588	GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:43:062	2b4	Set global fail flag, failed GPU1
05:32:43:079	2588	GPU 3, GpuMiner kx failed 1
05:32:43:085	2b4	GPU 1 failed
05:32:43:085	2588	Set global fail flag, failed GPU3
05:32:43:089	2588	GPU 3 failed
05:32:43:221	3d8	buf: {"id":6,"result":true,"error":null}

05:32:43:934	bb0	em hbt: 0, fm hbt: 78, 
05:32:43:935	bb0	watchdog - thread 0 (gpu0), hb time 1188
05:32:43:936	bb0	watchdog - thread 1 (gpu0), hb time 1063
05:32:43:938	bb0	watchdog - thread 2 (gpu1), hb time 1110
05:32:43:939	bb0	watchdog - thread 3 (gpu1), hb time 1235
05:32:43:940	bb0	watchdog - thread 4 (gpu2), hb time 1172
05:32:43:942	bb0	watchdog - thread 5 (gpu2), hb time 1047
05:32:43:943	bb0	watchdog - thread 6 (gpu3), hb time 1063
05:32:43:945	bb0	watchdog - thread 7 (gpu3), hb time 1188
05:32:43:946	bb0	watchdog - thread 8 (gpu4), hb time 1188
05:32:43:947	bb0	watchdog - thread 9 (gpu4), hb time 1047
05:32:43:949	bb0	watchdog - thread 10 (gpu5), hb time 1406
05:32:43:950	bb0	watchdog - thread 11 (gpu5), hb time 1953
05:32:43:951	bb0	WATCHDOG: GPU error, you need to restart miner :( 
05:32:45:414	bb0	Restarting OK, exit...

And how to put the right value for -eres function.The default value is 2, but i dont know what the effect if i increase or decrease the value through this -eres command line

start with -tt from 80, 85 to 70... than lower clocks a bit...

[AzzAz]

Claymore 11.7 has been running well for me with only the occasional slowdown of card for a couple of minutes only to pick back up to speed.

My only problem is that I can't reliably STOP the program.  I get a BSD from a driver fault whenever I try to stop.  I've tried most of this year's drivers from the 18.2 in Feb to the one before the latest.  I'm in no hurry to be current on my driver under Win10 but I am looking for that stability.  No memory errors and nothing crazy in the overclocking realm.  I'm about 28.5MHs on each of my 580s.

I do use DDU in Safe Mode when I switch drivers to get the cleanest possible install.

Any thoughts about where to look?

What bioses?

[AzzAz]

Is it normal that the rig would crash after some time if I mix hynix and elpida GPUs?

I have 4 Sapphire Nitro+ 570 with elpida memory and 2 Sapphire Nitro+ 570 with hynix memory... if I run them separately then rig is stable, but as soon as I start to mix GPUs with different memory types on one rig... I would see crashes, reboots, etc...

is that normal? Any ideas? 

Set clocks and voltages for each card, not same for elpida and hynix. Also what bioses you use?

[BS001]

Is it normal that the rig would crash after some time if I mix hynix and elpida GPUs?

I have 4 Sapphire Nitro+ 570 with elpida memory and 2 Sapphire Nitro+ 570 with hynix memory... if I run them separately then rig is stable, but as soon as I start to mix GPUs with different memory types on one rig... I would see crashes, reboots, etc...

is that normal? Any ideas? 

Set clocks and voltages for each card, not same for elpida and hynix. Also what bioses you use?

Original with timings from 1500.

I get 30 Mh on elpida and 29 on hynix, I tried running both down clocked to 1100 and 1800 and was getting 26 Mh but they still crashed after like 20 or 30 minutes. But as soon as I remove elpida GPUs or Hynix GPUs, the problems stop, had it running for 2 days without issues - only with one type of memory on one rig. Doesn't make any sense...

[bluspirit]

@claymore
can you maybe fix miner for gpu temp monitor
when i use MS remote desktop, and run miner .. only 1 gpu show temp
when i run minier via teamviver, show all gpu temp and fan %, or i run local .. via keyboard and monitor

but, teamviver is not free, and from time to time block conncection and you must wait for another.
And MS remote desktop is builed in, free and working great

It is not related to the miner, the reason is in Windows and AMD drivers.

@claymore
Hi, I have the same problem ... only GPU0 shows temp
Here I have win10 pro 1709 with drivers 18.3.4 and your miner v11.7:

Code:

00: 30: 39: 219 1e0c ETH: 05/14 / 18-00: 30: 39 - New job from eu1.ethermine.org:5555
00: 30: 39: 219 1e0c target: 0x0000000112e0be82 (diff: 4000MH), epoch 186 (2.45GB)
00: 30: 39: 219 1e0c gpu # 1 dt 0.15 (0%, good)
00: 30: 39: 219 1e0c ETH - Total Speed: 61.963 Mh / s, Total Shares: 122, Rejected: 0, Time: 02:17
00: 30: 39: 235 1e0c ETH: GPU0 30.854 Mh / s, GPU1 31.109 Mh / s
00: 30: 41: 829 d50 GPU 0 temp = 56, old fan speed = 53, new fan speed = 39
00: 30: 43: 438 1e0c ETH: checking pool connection ...

Windows remote desktop works well with other programs and also other miners I run from command ... they show temp of all GPUs. 

[AzzAz]

Is it normal that the rig would crash after some time if I mix hynix and elpida GPUs?

I have 4 Sapphire Nitro+ 570 with elpida memory and 2 Sapphire Nitro+ 570 with hynix memory... if I run them separately then rig is stable, but as soon as I start to mix GPUs with different memory types on one rig... I would see crashes, reboots, etc...

is that normal? Any ideas?  

Set clocks and voltages for each card, not same for elpida and hynix. Also what bioses you use?

Original with timings from 1500.

I get 30 Mh on elpida and 29 on hynix, I tried running both down clocked to 1100 and 1800 and was getting 26 Mh but they still crashed after like 20 or 30 minutes. But as soon as I remove elpida GPUs or Hynix GPUs, the problems stop, had it running for 2 days without issues - only with one type of memory on one rig. Doesn't make any sense...

4 cards work, 2 cards work, 6 not? Looks like latest windows update...If you can test 2 elpidas with 2 hynix to be shure

[svdinu]

@claymore
can you maybe fix miner for gpu temp monitor
when i use MS remote desktop, and run miner .. only 1 gpu show temp
when i run minier via teamviver, show all gpu temp and fan %, or i run local .. via keyboard and monitor

but, teamviver is not free, and from time to time block conncection and you must wait for another.
And MS remote desktop is builed in, free and working great

It is not related to the miner, the reason is in Windows and AMD drivers.

@claymore
Hi, I have the same problem ... only GPU0 shows temp
Here I have win10 pro 1709 with drivers 18.3.4 and your miner v11.7:

Code:

00: 30: 39: 219 1e0c ETH: 05/14 / 18-00: 30: 39 - New job from eu1.ethermine.org:5555
00: 30: 39: 219 1e0c target: 0x0000000112e0be82 (diff: 4000MH), epoch 186 (2.45GB)
00: 30: 39: 219 1e0c gpu # 1 dt 0.15 (0%, good)
00: 30: 39: 219 1e0c ETH - Total Speed: 61.963 Mh / s, Total Shares: 122, Rejected: 0, Time: 02:17
00: 30: 39: 235 1e0c ETH: GPU0 30.854 Mh / s, GPU1 31.109 Mh / s
00: 30: 41: 829 d50 GPU 0 temp = 56, old fan speed = 53, new fan speed = 39
00: 30: 43: 438 1e0c ETH: checking pool connection ...

Windows remote desktop works well with other programs and also other miners I run from command ... they show temp of all GPUs. 

Disable Crossfire

[SparkPool]

Good software.

[WhackOBill]

Claymore 11.7 has been running well for me with only the occasional slowdown of card for a couple of minutes only to pick back up to speed.

My only problem is that I can't reliably STOP the program.  I get a BSD from a driver fault whenever I try to stop.  I've tried most of this year's drivers from the 18.2 in Feb to the one before the latest.  I'm in no hurry to be current on my driver under Win10 but I am looking for that stability.  No memory errors and nothing crazy in the overclocking realm.  I'm about 28.5MHs on each of my 580s.

I do use DDU in Safe Mode when I switch drivers to get the cleanest possible install.

Any thoughts about where to look?

What bioses?

I'm running Ultramix 3.1 with Samsung memory and just a strap copy with the Hynix ... 1750 to 2000. All are at 2000MHz.  They really clip along fairly well.  I just can't reliably stop them.

I suppose it could be worse.

[AzzAz]

Claymore 11.7 has been running well for me with only the occasional slowdown of card for a couple of minutes only to pick back up to speed.

My only problem is that I can't reliably STOP the program.  I get a BSD from a driver fault whenever I try to stop.  I've tried most of this year's drivers from the 18.2 in Feb to the one before the latest.  I'm in no hurry to be current on my driver under Win10 but I am looking for that stability.  No memory errors and nothing crazy in the overclocking realm.  I'm about 28.5MHs on each of my 580s.

I do use DDU in Safe Mode when I switch drivers to get the cleanest possible install.

Any thoughts about where to look?

What bioses?

I'm running Ultramix 3.1 with Samsung memory and just a strap copy with the Hynix ... 1750 to 2000. All are at 2000MHz.  They really clip along fairly well.  I just can't reliably stop them.

I suppose it could be worse.

Well that happens with too much oc