4 ms·

What I think it will do for me? Correct single bit errors and alert me to them.

gambiting 3y ago
Like, in what way - you get a windows popup saying "hey, just detected a bit error, but it was corrected, all good"? Because if yes, you'd get such a popup daily, and I'm not sure what the actual value of it is. And I'm not being funny, I literally don't see the value of it(of the notification, not the correcting).
- dale_glass 3y ago
  You don't get a popup. In Linux, it's logged in dmesg. In Windows I imagine it goes in the system log. The system keeps on running. The value of the notification is that if most days you get nothing and suddenly 5000 corrected errors pop up, you know something is not quite right as of late. Maybe you're overdoing the overclocking. Maybe the module isn't sitting quite well in the slot. Maybe a solder joint is failing. If you have a 2 bit memory error, the typical result is a BSOD/kernel oops. Which is a good thing actually. It means you know for sure your RAM is bad, and it prevents any faulty data from being written anywhere. So rather than possibly propagating the error is just stopped. I believe there have been systems that try to handle it more elegantly. Kill the process the memory belongs to if it's a non-essential one then permanently blacklist that block to ensure it's not used again.
  - deleted 3y ago
    [deleted]
- CTDOCodebases 3y ago
  > Like, in what way - you get a windows popup saying "hey, just detected a bit error, but it was corrected, all good"? No I've set it up so I get an email. > Because if yes, you'd get such a popup daily I doubt that. There was a study done at Google that reported 8% of DIMMs encountered at least one memory error per year[0]. > I'm not sure what the actual value of it is. I like my PC to be as deterministic as possible[1] so if my programs crash I don't want to have to turn it off and test the memory which takes hours[2]. [0] - https://www.cs.toronto.edu/~bianca/papers/sigmetrics09.pdf https://www.cs.toronto.edu/~bianca/papers/sigmetrics09.pdf [1] - https://blog.cskr.dev/posts/corrupt-backup/ https://blog.cskr.dev/posts/corrupt-backup/ [2] - https://www.youtube.com/watch?v=0itrM7t4l34 https://www.youtube.com/watch?v=0itrM7t4l34

Like, in what way - you get a windows popup saying "hey, just detected a bit error, but it was corrected, all good"? Because if yes, you'd get such a popup daily, and I'm not sure what the actual value of it is. And I'm not being funny, I literally don't see the value of it(of the notification, not the correcting).

dale_glass 3y ago
You don't get a popup. In Linux, it's logged in dmesg. In Windows I imagine it goes in the system log. The system keeps on running. The value of the notification is that if most days you get nothing and suddenly 5000 corrected errors pop up, you know something is not quite right as of late. Maybe you're overdoing the overclocking. Maybe the module isn't sitting quite well in the slot. Maybe a solder joint is failing. If you have a 2 bit memory error, the typical result is a BSOD/kernel oops. Which is a good thing actually. It means you know for sure your RAM is bad, and it prevents any faulty data from being written anywhere. So rather than possibly propagating the error is just stopped. I believe there have been systems that try to handle it more elegantly. Kill the process the memory belongs to if it's a non-essential one then permanently blacklist that block to ensure it's not used again.
- deleted 3y ago
  [deleted]
CTDOCodebases 3y ago
> Like, in what way - you get a windows popup saying "hey, just detected a bit error, but it was corrected, all good"? No I've set it up so I get an email. > Because if yes, you'd get such a popup daily I doubt that. There was a study done at Google that reported 8% of DIMMs encountered at least one memory error per year[0]. > I'm not sure what the actual value of it is. I like my PC to be as deterministic as possible[1] so if my programs crash I don't want to have to turn it off and test the memory which takes hours[2]. [0] - https://www.cs.toronto.edu/~bianca/papers/sigmetrics09.pdf https://www.cs.toronto.edu/~bianca/papers/sigmetrics09.pdf [1] - https://blog.cskr.dev/posts/corrupt-backup/ https://blog.cskr.dev/posts/corrupt-backup/ [2] - https://www.youtube.com/watch?v=0itrM7t4l34 https://www.youtube.com/watch?v=0itrM7t4l34