Bitcoin Forum
May 08, 2024, 08:27:49 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Does memory errors reported in HWINFO actually indicate a problem?  (Read 1438 times)
Toxicable (OP)
Newbie
*
Offline Offline

Activity: 53
Merit: 0


View Profile
May 09, 2017, 08:46:01 PM
 #1

So I've been overclocking my cards and i've noticed that once I go up to about 2100 on the memory frequency I start getting memory errors reporting on HWINFO, about 1000 errors over 5 minutes but claymores doesn't complain so I'm wondering if this is something to be concerned about?
The block chain is the main innovation of Bitcoin. It is the first distributed timestamping system.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
Vann
Hero Member
*****
Offline Offline

Activity: 1036
Merit: 606



View Profile
May 09, 2017, 09:04:18 PM
 #2

Yes, overclocking too much will cause hardware errors, which will cause the miner to report more valid shares than you are actually getting credit for. Older miners like sgminer and cgminer used to report HW errors. I don't know why miners like Claymore's stopped reporting them.
Toxicable (OP)
Newbie
*
Offline Offline

Activity: 53
Merit: 0


View Profile
May 09, 2017, 09:14:48 PM
 #3

Yes, overclocking too much will cause hardware errors, which will cause the miner to report more valid shares than you are actually getting credit for. Older miners like sgminer and cgminer used to report HW errors. I don't know why miners like Claymore's stopped reporting them.

Ahhh okay thanks. I've clocked it back to 2075 which reports about 1-5 errors over a 30 min period, do you think that's fine?
Vann
Hero Member
*****
Offline Offline

Activity: 1036
Merit: 606



View Profile
May 09, 2017, 09:36:41 PM
Last edit: May 09, 2017, 09:54:52 PM by Vann
 #4

Ideally you should overclock just to the point where it's stable and without HW errors. It's not just about getting the maximum possible hashrate out of your cards. Stability and power consumption are also a factor. Typically the more more you overclock, the more power is used, so there is a diminishing return point where overclocking is just pushing the cards over their capacity for little to no benefit in your bottom line.
miropp
Full Member
***
Offline Offline

Activity: 810
Merit: 101



View Profile
May 09, 2017, 09:57:57 PM
 #5

I have many rigs with the same cards (the same part number, the same series of serial numbers, the same memory chip) and the same settings (core / memory). Usually in one rig, 3-4 cards have 0 memory errors, 1-2 cards have about several hundreds errors and 0-1 has thousands errors (HWINFO64). What with this? Underclock this cards with memory errors or sell them and buy others?

Toxicable (OP)
Newbie
*
Offline Offline

Activity: 53
Merit: 0


View Profile
May 10, 2017, 01:12:35 AM
 #6

Ideally you should overclock just to the point where it's stable and without HW errors. It's not just about getting the maximum possible hashrate out of your cards. Stability and power consumption are also a factor. Typically the more more you overclock, the more power is used, so there is a diminishing return point where overclocking is just pushing the cards over their capacity for little to no benefit in your bottom line.

From the calculations i've done it's more profitable for me to get a higher hashrate rather than balance the power usage out, however stability is still important. As mentioned above with 2075 mem freq I get 29.6 MH on ETH and 860 MH on DRC at 150W which I think is reasonable enough aslong as those 1-5 errors per 30 min isn't an issue
Arthas30
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
January 24, 2018, 12:05:13 PM
 #7

I've got 2 Asus RX 560, one works without memory errors and second one has 9000 errors every second, both work on stock settings with modded bios at 13MH/s
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!