That's the problem. It doesn't reset. The max doesn't reset, the average doesn't reset and the minimum doesn't reset. The current value just keeps steadily climbing. If I close the whole application, delete the files, download them again and install it again it just picks up where it left off. the ONLY way to reset that sensor is a hard PC reset. The GPU I am using is an Asus R9 280. It's a custom PCB (not sure if that matters).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.
It's possible. Might be something Asus changed on the board design. A friend with an Asus 290 told me that for him this value was basically a random number generator.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.
All stockMartin 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 ?
I did ask a friend of mine who works in this field and he told me that any type of memory, be it HDDs or Flash, accumulates errors and that is the reason for algorithms being implemented to catch and correct them. I'm still not sure what the nature of these is but from what I've read in the only article I could find - GDDR5's EDC is a sensor that monitors the bus for corrupt data and requests a re-send when it encounters errors. Please correct me if I am wrong.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.
I doubt I can get an RMA when the system is working fine. I also tried an old DX8 game which requires compatibility mode to work fine on my system (if I don't use it I get a weird bar flickering in the middle of the screen) and the counter didn't notice that at all. Also, I tried to push the memory as hard as I could and got to 2.4GB/3GB usage and that didn't really affect the error rate in any way. And so far only 3 games have shown to trigger it - Witcher 3, CS:GO and Divinity Original Sin - all of which I run in borderless window. I did run Shogun 2 for 2 hours and it didn't register anything.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.