Bitcoin Forum
May 25, 2024, 04:00:17 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: SOLVED: New ETH rig dropping 25%-75% HR every so often  (Read 1065 times)
kisk (OP)
Full Member
***
Offline Offline

Activity: 126
Merit: 100


View Profile
May 07, 2017, 04:48:12 PM
Last edit: May 13, 2017, 04:01:55 PM by kisk
 #1

[UPDATE - Solution reply has been added]


New rig: Mining ETH with Claymore's 9.0 and I'm having an issue with HR dropping by 25%-75% for a second or two about every 10 seconds, sometimes less. NOTE: This is NOT the 9.x issue with dual mining where random cards drop 5-10Mh/s -- my problem happens with ETH only and 8.1 as well, and HR drops on ALL cards. I'll be a thorough as possible here. I hate when people post questions with little info:


Win10
AMD 16.12.2
CPU:  Athlon II 170u 2Ghz (single core)
MOBO: Gigabyte  990FXA-UD3 R5 (all unnecessary options turned off)
8GB DDR3 (timings set correctly)
25GB VRam
60GB SSD
3x Gigabyte RX480 8GB (1750 straps)
3x Powercolor Red Devil RX480 8gb (1750 straps)

EthDcrMiner64.exe -epool us-east.ethash-hub.miningpoolhub.com:20535 -ewal user.rig02 -epsw x -ethi 16 -esm 3 -asm 1 -allpools 1 -mport XXXX -r 1 -di 530142 -dcri 10 -cclock 1145,1145,1145,1156,1167,1167 -cvddc 1037,918,1087,1031,1043,1037 -mclock 2150,2150,2150,2175,2175,2175

180Mh/s

The logs don't show me anything in particular out of the ordinary except for the drop in HR. Sometimes from 180MH/s to 150. Sometimes to 130. Sometimes less than 100. It doesn't last long and then returns to 180. I though it might be a power issue so I distributed the rig with 2 PSU's which didn't change anything. Tried 8.1, 9.0, 9.3. Set cards to default clocks. Tried ASM 0,1,2. multiple ETHI/DCRI values. Same. I did disconnect all 3 red devils and that fixed the issue. As soon as I connect a 4th GPU it starts happening again.

Couple things I'm thinking:
1) Maybe the CPU is too weak to keep up with certain functions? I have an Athlon 3.0ghz dual core on the way to test.
2) This motherboard does not have any settings for changing PCI-e options, gen1/gen2/gen3/Lat/etc. Maybe the lane bandwidth is hiccuping somewhere? I would think even 4 cards should be fine though, which its not.
3) I hot swapped this Win10 install from another rig (intel) and let Win10 reconfigure everything. Installed new drivers, and fresh installed video drivers. Maybe I'll try a full reinstall, or linux.
4) I don't think its a riser issue and it effects all the cards..

Hoping someone may see something I don't. Thanks for your help!!

Here are some logs:

GPU-z:
http://pasteboard.co/3rTLmaN7W.png


Code:
[b]10:21:54:543	544	ETH - Total Speed: 180.803 Mh/s, Total Shares: 23, Rejected: 0, Time: 00:12
10:21:54:593 544 ETH: GPU0 29.793 Mh/s, GPU1 26.330 Mh/s, GPU2 26.394 Mh/s, GPU3 30.455 Mh/s, GPU4 30.157 Mh/s, GPU5 30.241 Mh/s[/b]
10:21:57:749 169c recv: 51
10:21:57:749 169c srv pck: 50
10:21:57:952 169c srv bs: 0
10:21:57:968 169c sent: 241
10:22:02:483 82c recv: 51
10:22:02:483 82c srv pck: 50
10:22:02:655 82c srv bs: 0
10:22:02:671 82c sent: 241
10:22:07:140 544 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xa074716", "0x00000000000000000000000000000000000000000000000000000000bf453132"]}

10:22:07:280 544 got 36 bytes
10:22:07:327 544 buf: {"id":6,"result":true,"error":null}

10:22:07:374 544 parse packet: 35
10:22:07:421 544 new buf size: 0
10:22:07:499 544 got 195 bytes
10:22:07:515 544 buf: {"id":null,"method":"mining.notify","params":["d70e","e586ce62651f6de0be923da595f6773a2d1bd9b41ca0ad927456061ed15c0a14","782e4b91007316a5d95c60f5fdba91557a12f49b5aeaf6b2699087d95feaa3da",false]}

10:22:07:515 544 parse packet: 194
10:22:07:530 544 ETH: job changed
10:22:07:530 544 new buf size: 0
10:22:07:546 544 ETH: 05/07/17-10:22:07 - New job from us-east.ethash-hub.miningpoolhub.com:20535
10:22:07:561 544 target: 0x0000000112dfaba1 (diff: 4000MH), epoch #122
[b]10:22:07:561 544 ETH - Total Speed: 139.031 Mh/s, Total Shares: 23, Rejected: 0, Time: 00:13
10:22:07:587 544 ETH: GPU0 21.107 Mh/s, GPU1 23.758 Mh/s, GPU2 23.802 Mh/s, GPU3 23.707 Mh/s, GPU4 23.303 Mh/s, GPU5 23.354 Mh/s[/b]
10:22:07:603 e3c recv: 51
10:22:07:634 730 ETH: put share nonce 22c0000a400e00
10:22:07:634 e3c srv pck: 50
10:22:07:650 730 ETH round found 1 shares
10:22:07:665 544 ETH:  Stale share found
10:22:07:712 544 ETH: 05/07/17-10:22:07 - SHARE FOUND - (GPU 4)
10:22:07:728 544 send: {"id": 4, "method": "mining.submit", "params": ["kisk.rig02","d70d","c0000a400e00"]}

10:22:07:806 544 got 36 bytes
10:22:07:806 544 buf: {"id":4,"result":true,"error":null}

10:22:07:821 544 parse packet: 35
10:22:07:821 544 ETH: Share accepted (94 ms)!
10:22:07:837 544 new buf size: 0
10:22:07:929 e3c srv bs: 0
10:22:07:929 e3c sent: 241
10:22:11:445 ff0 GPU0 t=64C fan=64%, GPU1 t=62C fan=65%, GPU2 t=68C fan=66%, GPU3 t=56C fan=63%, GPU4 t=60C fan=62%, GPU5 t=64C fan=65%
10:22:11:460 ff0 em hbt: 0, fm hbt: 16,
10:22:11:476 ff0 watchdog - thread 0, hb time 250
10:22:11:493 ff0 watchdog - thread 1, hb time 656
10:22:11:493 ff0 watchdog - thread 2, hb time 656
10:22:11:509 ff0 watchdog - thread 3, hb time 250
10:22:11:509 ff0 watchdog - thread 4, hb time 656
10:22:11:525 ff0 watchdog - thread 5, hb time 250
10:22:11:525 ff0 watchdog - thread 6, hb time 687
10:22:11:540 ff0 watchdog - thread 7, hb time 297
10:22:11:540 ff0 watchdog - thread 8, hb time 109
10:22:11:556 ff0 watchdog - thread 9, hb time 562
10:22:11:556 ff0 watchdog - thread 10, hb time 781
10:22:11:571 ff0 watchdog - thread 11, hb time 390
10:22:11:587 1104 ETH: put share nonce 22d55557ac76d5
10:22:11:587 1104 ETH round found 1 shares
10:22:11:603 544 ETH: 05/07/17-10:22:11 - SHARE FOUND - (GPU 5)
10:22:11:618 544 send: {"id": 4, "method": "mining.submit", "params": ["kisk.rig02","d70e","d55557ac76d5"]}

10:22:11:706 544 got 36 bytes
10:22:11:706 544 buf: {"id":4,"result":true,"error":null}

10:22:11:722 544 parse packet: 35
10:22:11:722 544 ETH: Share accepted (94 ms)!
10:22:11:738 544 new buf size: 0
10:22:12:964 a4c recv: 51
10:22:12:964 a4c srv pck: 50
10:22:13:152 a4c srv bs: 0
10:22:13:152 a4c sent: 241
10:22:14:277 544 got 195 bytes
10:22:14:277 544 buf: {"id":null,"method":"mining.notify","params":["d70f","e586ce62651f6de0be923da595f6773a2d1bd9b41ca0ad927456061ed15c0a14","565c37529fd81168f3f2488c2b99dfbc8ec533c1f4e2aaae613b73df1c71df88",false]}

10:22:14:292 544 parse packet: 194
10:22:14:292 544 ETH: job changed
10:22:14:308 544 new buf size: 0
10:22:14:323 544 ETH: 05/07/17-10:22:14 - New job from us-east.ethash-hub.miningpoolhub.com:20535
10:22:14:323 544 target: 0x0000000112dfaba1 (diff: 4000MH), epoch #122
[b]10:22:14:350 544 ETH - Total Speed: 180.698 Mh/s, Total Shares: 25, Rejected: 0, Time: 00:13
10:22:14:366 544 ETH: GPU0 29.070 Mh/s, GPU1 29.020 Mh/s, GPU2 28.926 Mh/s, GPU3 30.461 Mh/s, GPU4 29.413 Mh/s, GPU5 30.531 Mh/s[/b]
10:22:17:475 91c recv: 51
10:22:17:491 91c srv pck: 50
10:22:17:663 91c srv bs: 0
10:22:17:663 91c sent: 241
10:22:22:709 1404 recv: 51
10:22:22:725 1404 srv pck: 50
10:22:22:897 1404 srv bs: 0
10:22:22:897 1404 sent: 241
10:22:26:928 1108 ETH: put share nonce 2215555ff0ef45
10:22:26:944 1108 ETH round found 1 shares
10:22:26:959 544 ETH: 05/07/17-10:22:26 - SHARE FOUND - (GPU 0)
10:22:26:959 544 send: {"id": 4, "method": "mining.submit", "params": ["kisk.rig02","d70f","15555ff0ef45"]}

10:22:27:053 544 got 36 bytes
10:22:27:053 544 buf: {"id":4,"result":true,"error":null}

10:22:27:068 544 parse packet: 35
10:22:27:068 544 ETH: Share accepted (94 ms)!
10:22:27:084 544 new buf size: 0
10:22:27:162 544 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xaa1203c", "0x00000000000000000000000000000000000000000000000000000000bf453132"]}

10:22:27:240 544 got 36 bytes
10:22:27:240 544 buf: {"id":6,"result":true,"error":null}

10:22:27:256 544 parse packet: 35
Jamievs
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250


View Profile
May 07, 2017, 05:15:34 PM
 #2

I am gonna follow this thread. Some of my cards show the same odd behaviour.
dddrgonzooo
Newbie
*
Offline Offline

Activity: 58
Merit: 0


View Profile
May 07, 2017, 08:14:34 PM
 #3

I have had similar issues due to memory errors and heat. Have you ran hwinfo to check for errors? You might need to drop your memory a bit. Have you bumped the power limit up? I set my fans at a static speed so that the cards don't throttle when the fans slow down and the gpu heats up.
kisk (OP)
Full Member
***
Offline Offline

Activity: 126
Merit: 100


View Profile
May 07, 2017, 08:49:57 PM
 #4

I have had similar issues due to memory errors and heat. Have you ran hwinfo to check for errors? You might need to drop your memory a bit. Have you bumped the power limit up? I set my fans at a static speed so that the cards don't throttle when the fans slow down and the gpu heats up.

I don't think its mem errors or heat as this happens even when cards are set to stock speeds, core and mem. I have my minimum fan speed set to 2500rpm on all cards so temps rarely get past 70c. Setting power limits higher doesn't change anything. In my experience, not having sufficient power limit will cause the core to automatically underclock which you can see regularly go up and down in wattman. In my case all the clocks are stable. I'm undervolted anyway. Thanks for the suggestions though. I'm going to pull the plug on each card individually and see what I get. Maybe one card or slot is causing the others to fault somehow.
m0bilitee
Newbie
*
Offline Offline

Activity: 49
Merit: 0


View Profile
May 07, 2017, 09:30:25 PM
 #5

I can get all my cards on a rig to just drop mining to near zero for about 15 seconds by clicking in the Cortana search box on Windows 10. Solution, don't do that anymore. Smiley
philipma1957
Legendary
*
Online Online

Activity: 4130
Merit: 7925


'The right to privacy matters'


View Profile WWW
May 07, 2017, 11:38:35 PM
 #6

I have had similar issues due to memory errors and heat. Have you ran hwinfo to check for errors? You might need to drop your memory a bit. Have you bumped the power limit up? I set my fans at a static speed so that the cards don't throttle when the fans slow down and the gpu heats up.

drop all memory clocks by 50

drop all core by 25

lower

-ethi  to 7

that pulse in hash simply means the card clocks and intensity  setting is too high.



so hashrate throttles

I used to get single mode or dual mode on my msi gamer  rx 480 and asus  strix 480  all 8gb cards.

I simply lower everything a little at a time  til it stopped.

And I have all i5 intel cpus  and only 2 or 3 card rigs using 750 watt p2 evga  so it is not a psu or a cpu issue  the pulse is simply clock or intensity issue


▄▄███████▄▄
▄██████████████▄
▄██████████████████▄
▄████▀▀▀▀███▀▀▀▀█████▄
▄█████████████▄█▀████▄
███████████▄███████████
██████████▄█▀███████████
██████████▀████████████
▀█████▄█▀█████████████▀
▀████▄▄▄▄███▄▄▄▄████▀
▀██████████████████▀
▀███████████████▀
▀▀███████▀▀
.
 MΞTAWIN  THE FIRST WEB3 CASINO   
.
.. PLAY NOW ..
kisk (OP)
Full Member
***
Offline Offline

Activity: 126
Merit: 100


View Profile
May 08, 2017, 01:22:27 PM
 #7

I have had similar issues due to memory errors and heat. Have you ran hwinfo to check for errors? You might need to drop your memory a bit. Have you bumped the power limit up? I set my fans at a static speed so that the cards don't throttle when the fans slow down and the gpu heats up.

drop all memory clocks by 50

drop all core by 25

lower

-ethi  to 7

that pulse in hash simply means the card clocks and intensity  setting is too high.



so hashrate throttles

I used to get single mode or dual mode on my msi gamer  rx 480 and asus  strix 480  all 8gb cards.

I simply lower everything a little at a time  til it stopped.

And I have all i5 intel cpus  and only 2 or 3 card rigs using 750 watt p2 evga  so it is not a psu or a cpu issue  the pulse is simply clock or intensity issue



As stated above, my problem happens even at stock clocks and with intensity low. Lowering them has no effect.
xxcsu
Hero Member
*****
Offline Offline

Activity: 1498
Merit: 597


View Profile WWW
May 08, 2017, 03:23:19 PM
Last edit: May 08, 2017, 03:50:18 PM by xxcsu
 #8

As stated above, my problem happens even at stock clocks and with intensity low. Lowering them has no effect.

Is this happening with the original bios also with stock settings ? without any modification ? with original , unchanged mem straps ?
You did not said anything about what psu are u using. hashrate dropping can be a psu issue also ... ETH mining process use more power than zcash, xmr ...

Learn about Merit & new rank requirements , Learn how to use MERIT , make this community better
If you like the answer you got for your question from any member ,
If you find any post useful , informative use the +Merit button.
kisk (OP)
Full Member
***
Offline Offline

Activity: 126
Merit: 100


View Profile
May 13, 2017, 03:59:56 PM
 #9

SOLVED:

Just wanted to update the thread. It turns out it was the CPU. The 2GHz single core just couldn't keep up. Upgraded it to a 3.0Ghz dual core and no longer have any problems. Hash is stable!

Thanks to everyone that too a stab at the problem!!
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!