Martin said:The reset value is valid only for min/max/average values. Current value is not reset and HWiNFO accumulates this counter because whenever the GPU goes idle, the counter is switched off.
It's sufficient to restart HWiNFO (or close the sensors window) to reset the current value.
Martin said:Then it must be the GPU hardware counter that doesn't reset. It should do when the GPU goes idle and you restart HWiNFO. If not, then I'm afraid I can't do anything.
Martin said:Hard to say exactly, but I don't think OEMs can change the way how those errors are measured, they can only do something that causes those errors (bad memory, high timings, etc.).
Are you getting the errors at stock settings (clocks+voltages) ?
How many errors are you getting, does it rise constantly ?
Do you observe screen artifacts ?
Martin said:That's a very low amount of errors, though it should not happen at all with stock settings. Users pushing memory clock too high or with artifacts are getting hundreds to thousands of errors per second.
You might try with a single monitor when the memory clock drops to lowest state and then restart HWiNFO whether the counter resets to 0.
Martin said:Yes, that's right. This EDC counter doesn't differentiate between correctable and uncorrectable errors, so we don't know what kind the reported ones are.
Since there are only so few of them, I wouldn't worry about it. If you do, you might try to RMA the GPU.
Running with a single display confirms that the hardware counter works properly and resets when the memory clock drops to low state.