There was another incident recently with garbled data[1]. The issue then was Voyager was trying to use a processor that was supposed to have been turned off. It

There was another incident recently with garbled data[1]. The issue then was Voyager was trying to use a processor that was supposed to have been turned off. It either turned the malfunctioning unit or thought that the disabled unit was turned on when it wasn't. But the flaw is similar to the current problem which a malfunction in managing its internal state. [1] https://www.nasa.gov/missions/voyager-program/voyager-2/engineers-solve-data-glitch-on-nasas-voyager-1/ https://www.nasa.gov/missions/voyager-program/voyager-2/engi...