A calendar calculation trapped the player
The Zune 30’s clock depended on firmware: software built into the device that handles basic operations. At the end of 2008, that software had to move the calendar from December 31 to January 1. Because 2008 was a leap year, the calculation also had to account for February 29.
A bug in the clock driver—the software component responsible for that date calculation—sent the player into an infinite loop, repeating the same steps instead of finishing the transition. The device could no longer proceed normally, so its screen appeared frozen.
One shared flaw, many frozen devices
The problem was not that the players’ batteries or screens had all failed at once. Zune 30s were running the same faulty date-handling code, and the calendar reached the troublesome point at the same time. That is why the incident looked less like an ordinary hardware breakdown and more like a synchronized outage.
The loop stopped only when the battery ran down and the player shut off. By the time it was charged and restarted, the date had rolled into January 1, and the faulty year-end calculation no longer blocked startup. A single overlooked calendar edge case had effectively turned the passage of time into a device-wide switch: one day the players worked, and the next their shared software could not get past the clock.
