Attack of the cosmic rays: Undetected memory errors can happen to you
blog.ksplice.com
blog.ksplice.com
This seems like a bit of a red flag that in reality something else is actually going wrong with his computer.
I'm sure that this can happen to me, that in any particular moment, my memory can get corrupted by these rays, or something else, and then, the computer can misbehave or crash. And if I really wanted to be sure that it will not, I'd need to have some kind of protection against it. But compared to many other possible faults, is it really anything more than a very very rare and minor reason of a computer failure that I simply can just discard on my laptop, which is nowhere near a "critical and vital" system?
I used to run 6x2GB at 1333MHz with an i7 920. I swapped the CPU with one that could properly drive my ECC memory (W3520), and quickly found my choices were either an unusable system, 3x2GB at 1333, or 6*2GB at 800.
Airplane avionics aren't radiation-hardened, but they work fine at altitude where the incidence of cosmic rays is about 1/4th that in space. Planes aren't dropping out of the sky from bit flips. People don't get tons of parity or ECC errors on their laptops while flying. Based on all this, I think the threat of cosmic rays is vastly overstated.
Avionics systems use ECC memory and other techniques to avoid being impacted by cosmic rays causing single event upsets. As far as parity and ECC errors on laptops, I don't believe ECC ram is common on laptops.
That being said, this particular article uses a gross overestimate of SEUs for memory, which is really only applicable if your 4GB of RAM fills an entire room in multiple full sized racks (the studies he bases these figures on come from the 80s and the author fails to adjust for physical size when extrapolating to modern memory sizes).
Microsoft's datacenters have a straightforward policy for dealing with software errors: first restart the service, if that doesn't fix it then restart the OS, and if that doesn't fix it then swap out the machine.
Of course, this is cosmic rays hitting the focal plane and not a memory corruption issue.
The Space Telescope Science Institute schedules multiple exposures so they can be stacked on the ground to eliminate the traces.
This reminded me of a number of random crashes that a client of my previous company had. Stackdumps just showed random errors. We had about a years worth of crash logs from a couple thousand of network switches (they were an ISP). We initially suggested that this might be a problem with cosmic rays. We even checked the frequency of the random crashes with sunspot cycles. No relationship found. Turns out it was due to another component failing due to a design error.
I learned about ECC RAM when I was trying to figure out why server lease deals were so inexpensive relative to others. For instance, the last I checked, hetzner.de's hardware does not support ECC RAM. I am of course not calling out hetzner, and there are other factors in such deals.
Although, becuase the protons are such high energy, I can't imagine how much material it would take. This stuff is very bhigh energy, and very nasty to stop. To get an idea of what kind of shielding you'd need, I'd look at the shielding used at the lhc, tevatron, and slac. they all produce particles of comparable energy.
I think ECC ram might be cheaper, up to a point, maybe shielding would be better for data centers.
It's really difficult to find lead that doesn't emit various particles itself. (Yup, lead has radioactive isotopes.)
IIRC, there have been memory/logic errors traced to radioactive particles from solder, perhaps even the lead. (This was back in the days when solder contained lead.)
sometimes a zebra is just a horse.