It looks like I selected the wrong delivery type so my new 480s devils are not coming to Monday.
So started looking at memory errors.
I noticed on watttool info it said if you are overclocking memory check for memory errors using HWINFO
now not used this before so downloaded it and fired it up, I'm only interested in the sensor info so ticked the box sensor info only.
So I'm currently running my 31.25 mod across my 480s so how are they doing
well it seems a bit of a mix.
1 card is producing almost no memory errors at 2250/920
1 card is showing a very big number and climbing a lot.
the others are climbing but showing around 1mill errors
The number is a total so climbs per tick.
I found on some cards changing the settings and applying in watttool reset the number to 0 which was handy and other didn't which was odd and inconsistent.
now being new to this info I'm not actually sue what number is a good number, but I'm going with errors in memory can be corrected but poss not at the very high rate I was seeing on one card.
So seeing a few over a second say 30-50 was prob going to be ok but ones that are climbing at a rate of over this per sec are prob not doing the work you want it to do , despite the hash rate showing on claymore.
So a small adjustment of the mem speed 1 as low as 2190 now gives me lower or similar to 30-50 a sec errors. I found some wanted a lower speed and other just a tine amt more power.
my expectation here is that if a gpu is producing GH's and 1million errors per sec its unlikely to be doing the work you think it should be and while not logging errors at the app layer doesn't mean the hashes are correct...not really sure this is accurate but with out much info to go on it seems a reasonable assumption.
I'll keep an eye on pool side and see if a more inline with expected hash rate is seen after ironing out the memory errors seen and if the odd gpu hang which seems to happen with the 480s goes away or lessens.
Boysie
So started looking at memory errors.
I noticed on watttool info it said if you are overclocking memory check for memory errors using HWINFO
now not used this before so downloaded it and fired it up, I'm only interested in the sensor info so ticked the box sensor info only.
So I'm currently running my 31.25 mod across my 480s so how are they doing
well it seems a bit of a mix.
1 card is producing almost no memory errors at 2250/920
1 card is showing a very big number and climbing a lot.
the others are climbing but showing around 1mill errors
The number is a total so climbs per tick.
I found on some cards changing the settings and applying in watttool reset the number to 0 which was handy and other didn't which was odd and inconsistent.
now being new to this info I'm not actually sue what number is a good number, but I'm going with errors in memory can be corrected but poss not at the very high rate I was seeing on one card.
So seeing a few over a second say 30-50 was prob going to be ok but ones that are climbing at a rate of over this per sec are prob not doing the work you want it to do , despite the hash rate showing on claymore.
So a small adjustment of the mem speed 1 as low as 2190 now gives me lower or similar to 30-50 a sec errors. I found some wanted a lower speed and other just a tine amt more power.
my expectation here is that if a gpu is producing GH's and 1million errors per sec its unlikely to be doing the work you think it should be and while not logging errors at the app layer doesn't mean the hashes are correct...not really sure this is accurate but with out much info to go on it seems a reasonable assumption.
I'll keep an eye on pool side and see if a more inline with expected hash rate is seen after ironing out the memory errors seen and if the odd gpu hang which seems to happen with the 480s goes away or lessens.
Boysie