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

She has reasons! Why did you buy Vegas? Nobody has said that they are any good in mining. Gamer's edition and proper drivers will be available in a few months.

PCI-E_4096Mb GeForce GTX1050Ti Palit StormX DDR5,128bit,DVI,HDMI,DP oem
 PCI-E_4096Mb GeForce GTX1050Ti MSI Gaming  DDR5,128bit,DVI,HDMI,DP rtl
 PCI-E_4096Mb GeForce GTX1050Ti Gigabyte OC,DDR5,128bit,DVI,HDMI,DP (GV-N105TOC-4GD) ret
 PCI-E_4096Mb GeForce GTX1050Ti Gigabyte DDR5,128bit,DVI,HDMI,DP(GV-N105TG1 GAMING-4D) ret
 PCI-E_4096Mb GeForce GTX1050Ti Gigabyte DDR5,128bit,DVI,HDMI,DP (GV-N105TD5-4GD) ret

Someone use this card? How much mh/s by Claymore 9.7 ? what bestest ?

You can disconnect it, but press "N" on keyboard during first start after disconnecting.

If you are using powered risers, then you dont need the molex cables plugged into the motherboard.

Does anyone have Asrock h81 btc pro ?
i have connected the 2 molex Cables on the motherboard aswell as having powered risers (sata to molex ).
Is this correct or should i remove the 2 molex on the motherboard?

V 9.7 as you mentioned, looks improved for my GTX 1060s. I get 25+ MH/s per GPU. It is now in par with the new improved ethminer. Thanks Claymore.

 PCI-E_4096Mb GeForce GTX1050Ti Palit StormX DDR5,128bit,DVI,HDMI,DP oem
 PCI-E_4096Mb GeForce GTX1050Ti MSI Gaming  DDR5,128bit,DVI,HDMI,DP rtl
 PCI-E_4096Mb GeForce GTX1050Ti Gigabyte OC,DDR5,128bit,DVI,HDMI,DP (GV-N105TOC-4GD) ret
 PCI-E_4096Mb GeForce GTX1050Ti Gigabyte DDR5,128bit,DVI,HDMI,DP(GV-N105TG1 GAMING-4D) ret
 PCI-E_4096Mb GeForce GTX1050Ti Gigabyte DDR5,128bit,DVI,HDMI,DP (GV-N105TD5-4GD) ret

Someone use this card? How much mh/s by Claymore 9.7 ? what bestest ?

Khm... is it still supported after version 9.6?

Thanks for the 9.7 version, nice work here.

Try to use  -dcri value between 15 and 20.   75 is TOO high.

Add switch "-di 2345" to the start.bat file. Cards 0 and 1 will not be mined.

May be it is simple...
But HOW to exclude first two of six cards from mining in latest versions of miner (v. 9.6 & more)?

Why my rig have 6 Colorful P106-100 (GDDR5 Samsung(GPU-Z info)) can't increase memory clock higher than 270? if i try to increase to 300 or more Claymore tool will give me error:
my PSU is 1600w

Also, I my power graphs on this rig are way way different than my other Windows 10 desktop that only has 4 cards.  This one the power graphs go all over the place and the other machine they are a rock solid line.  Is this normal or does this indicate a problem?  Thanks again

https://drive.google.com/open?id=0B7yTVsE3BqDWRjQ2c1dCTWVEemM

Edit:  ^^^ That is a link to a screenshot picture.  I guess I can't figure out how to insert a picture in my post

Hello.  Excuse my newbish question but I am trying to learn how to interpret the log files to diagnose stability issues I am having.  Does this mean GPU 2 is the GPU I should be questioning?  They all go out, but GPU 2 always leads the pack.  Any help is much appreciated!

21:48:57:240   2168   ETH: job is the same
21:48:57:240   2168   new buf size: 0
21:48:58:319   1434   recv: 51
21:48:58:319   1434   srv pck: 50
21:48:58:319   1434   srv bs: 0
21:48:58:334   1434   sent: 326
21:49:02:866   2138   GPU 2, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:866   2138   GPU 2, GpuMiner kx failed 1
21:49:02:866   2138   Set global fail flag, failed GPU2
21:49:02:866   213c   GPU 2, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:866   2138   GPU 2 failed
21:49:02:882   214c   GPU 4, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:882   2128   GPU 0, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:882   213c   GPU 2, GpuMiner kx failed 1
21:49:02:897   213c   Set global fail flag, failed GPU2
21:49:02:897   2158   GPU 6, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:897   2164   GPU 7, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:897   2140   GPU 3, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:913   214c   GPU 4, GpuMiner kx failed 1
21:49:02:913   2128   GPU 0, GpuMiner kx failed 1
21:49:02:913   2128   Set global fail flag, failed GPU0
21:49:02:913   213c   GPU 2 failed
21:49:02:928   2158   GPU 6, GpuMiner kx failed 1
21:49:02:928   2164   GPU 7, GpuMiner kx failed 1
21:49:02:928   2140   GPU 3, GpuMiner kx failed 1
21:49:02:913   214c   Set global fail flag, failed GPU4
21:49:02:944   2154   GPU 5, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:944   2128   GPU 0 failed
21:49:02:944   212c   GPU 0, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:928   2158   Set global fail flag, failed GPU6
21:49:02:960   2158   GPU 6 failed
21:49:02:960   2130   GPU 1, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:928   2140   Set global fail flag, failed GPU3
21:49:02:960   2148   GPU 4, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:975   214c   GPU 4 failed
21:49:02:975   2154   GPU 5, GpuMiner kx failed 1
21:49:02:975   212c   GPU 0, GpuMiner kx failed 1
21:49:02:928   2164   Set global fail flag, failed GPU7
21:49:02:991   215c   GPU 6, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:02:991   2130   GPU 1, GpuMiner kx failed 1
21:49:02:991   2144   GPU 3, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:03:007   2140   GPU 3 failed
21:49:03:007   2148   GPU 4, GpuMiner kx failed 1
21:49:02:975   2154   Set global fail flag, failed GPU5
21:49:03:007   2154   GPU 5 failed
21:49:03:007   2160   GPU 7, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:03:022   2164   GPU 7 failed
21:49:03:022   215c   GPU 6, GpuMiner kx failed 1
21:49:02:991   2130   Set global fail flag, failed GPU1
21:49:03:038   2144   GPU 3, GpuMiner kx failed 1
21:49:02:991   212c   Set global fail flag, failed GPU0
21:49:03:007   2148   Set global fail flag, failed GPU4
21:49:03:053   2148   GPU 4 failed
21:49:03:053   2160   GPU 7, GpuMiner kx failed 1
21:49:03:038   215c   Set global fail flag, failed GPU6
21:49:03:053   215c   GPU 6 failed
21:49:03:069   2130   GPU 1 failed
21:49:03:038   2144   Set global fail flag, failed GPU3
21:49:03:069   2144   GPU 3 failed
21:49:03:069   2150   GPU 5, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:03:053   2160   Set global fail flag, failed GPU7
21:49:03:085   2134   GPU 1, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
21:49:03:085   212c   GPU 0 failed
21:49:03:085   2150   GPU 5, GpuMiner kx failed 1
21:49:03:085   2160   GPU 7 failed
21:49:03:100   2134   GPU 1, GpuMiner kx failed 1
21:49:03:085   2150   Set global fail flag, failed GPU5
21:49:03:100   2150   GPU 5 failed
21:49:03:100   2134   Set global fail flag, failed GPU1
21:49:03:116   2134   GPU 1 failed
21:49:03:335   1f94   recv: 51
21:49:03:335   1f94   srv pck: 50
21:49:03:335   1f94   srv bs: 0
21:49:03:335   1f94   sent: 243
21:49:05:616   1c48   GPU0 t=60C fan=100%, GPU1 t=50C fan=70%, GPU2 t=58C fan=100%, GPU3 t=55C fan=100%, GPU4 t=63C fan=100%, GPU5 t=58C fan=100%, GPU6 t=59C fan=100%, GPU7 t=59C fan=100%
21:49:05:616   1c48   em hbt: 0, dm hbt: 0, fm hbt: 16,
21:49:05:616   1c48   watchdog - thread 0 (gpu0), hb time 2922
21:49:05:616   1c48   watchdog - thread 1 (gpu0), hb time 2813
21:49:05:632   1c48   watchdog - thread 2 (gpu1), hb time 2938
21:49:05:632   1c48   watchdog - thread 3 (gpu1), hb time 2829
21:49:05:632   1c48   watchdog - thread 4 (gpu2), hb time 2954
21:49:05:632   1c48   watchdog - thread 5 (gpu2), hb time 2875
21:49:05:632   1c48   watchdog - thread 6 (gpu3), hb time 2954
21:49:05:647   1c48   watchdog - thread 7 (gpu3), hb time 2859
21:49:05:647   1c48   watchdog - thread 8 (gpu4), hb time 2797
21:49:05:647   1c48   watchdog - thread 9 (gpu4), hb time 2906
21:49:05:647   1c48   watchdog - thread 10 (gpu5), hb time 2875
21:49:05:647   1c48   watchdog - thread 11 (gpu5), hb time 2969
21:49:05:663   1c48   watchdog - thread 12 (gpu6), hb time 2985
21:49:05:663   1c48   watchdog - thread 13 (gpu6), hb time 2891
21:49:05:663   1c48   watchdog - thread 14 (gpu7), hb time 2875
21:49:05:663   1c48   watchdog - thread 15 (gpu7), hb time 2985
21:49:05:663   1c48   WATCHDOG: GPU error, you need to restart miner
21:49:06:851   1c48   Restarting OK, exit...

Im using windows yeah but most of the times it stops without even me being there to press anything.

NICEHASH MINES NEWER DAGGERHASHIMOTO COINS--

Buyers of hashrate on NiceHash may direct your miner at alt-Ethereum coins that may be at very low Epochs.  That is, not all hashrate is directed at ETH, or at ETC.  If you mine on NiceHash, you cannot avoid the low Epoch coins.       --scryptr

My MSI GTX 1070 Gaming X cards went up 1.2 M/H each card with 9.7 version (no change in clock settings)!

@Claymore  Nice Job!

Are you using Windows, and have you clicked on the command window? cmd.exe stops scrolling new text when you select even one character. If you push enter, it will scroll again.

Thanks, but no luck there either. Same issue as before.

I think it's really weird that I get the "SC - Stratum: connected" line but never get a "SC Authorized" line. Would there be any weird firewall stuff that could be causing this that would let through ETH but not SC?


Everything in config.txt appears to be commented out already, and dpools and epools contain consistent info with what I'm putting into my startup script.