How a Race Condition, Overconfidence in Code, and Systemic Failures Led to One of the Deadliest Chapters in Computer History.Continue reading on Coinmonks »How a Race Condition, Overconfidence in Code, and Systemic Failures Led to One of the Deadliest Chapters in Computer History.Continue reading on Coinmonks »

The Therac-25: The Software Bug That Killed Patients

2025/10/03 13:50

How a Race Condition, Overconfidence in Code, and Systemic Failures Led to One of the Deadliest Chapters in Computer History.

Tabish anwar
5 min read
·
Just now

--

Share

The Therac-25 Disasters: When Software Failure Turned Deadly

In the mid-1980s, at the dawn of the computer age in medicine, a machine called the Therac-25 was meant to be a marvel of modern technology. It was a radiation therapy linear accelerator, designed to destroy cancerous tumors with high-energy beams. It promised precision and efficiency. Instead, it became infamous for causing one of the most horrific and instructive tragedies in the history of software engineering.

Press enter or click to view image in full size
Photo by Growtika on Unsplash

Between 1985 and 1987, the Therac-25 massively overdosed at least six patients. Four of them died from their injuries. The victims weren’t just statistics; they were people like Ray Cox, a 58-year-old man undergoing treatment for a back lesion, who was left paralyzed, in agony, and eventually killed by the very machine meant to heal him.

The investigations that followed uncovered not a single “glitch,” but a perfect storm of software errors, flawed system design, and devastating human complacency. This is the story of the Therac-25, a catastrophe that forever…

Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact service@support.mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.