Easy enough to imagine. Something improperly was judged to not need concencus, running the calculation twice, or some other software mitigation. Revise process to include mitigation.
"just run the calculation twice. surely the darned solar radiation will take care not to hit random parts of the memory or any critical registers in the cpu"
Best explanation I've seen (and claims to be from a published but not public report on it), is that their 3 way consensus didn't smooth over repeated wildly wrong outputs correctly. Concestency problem strikes again.
