Do the results talked about in this article scale down to small systems?<p>&quot;Jaguar had 360 terabytes of main memory, all protected by ECC. I and others at the lab set it up to log every time a bit was flipped incorrectly in main memory. When I asked my computing colleagues elsewhere to guess how often Jaguar saw such a bit spontaneously change state, the typical estimate was about a hundred times a day. In fact, Jaguar was logging ECC errors at a rate of 350 per minute.&quot;<p>If I take the 360 TB and scale it down to a laptop with 16 GB of RAM am I seeing errors at a proportional rate?<p>350 errors &#x2F; 368 640 GB * 16 GB * 60 minutes * 24 hours = 21.875 memory bits changed per day on a 16 GB laptop<p>That just seems way too high for average users to have not noticed the lack of ECC, and especially for the Jeff Atwood-type non-ECC server crowd (<a href="http:&#x2F;&#x2F;blog.codinghorror.com&#x2F;to-ecc-or-not-to-ecc&#x2F;" rel="nofollow">http:&#x2F;&#x2F;blog.codinghorror.com&#x2F;to-ecc-or-not-to-ecc&#x2F;</a>). What am I missing?