Thursday, January 1st 2009
30GB Zunes Fail at Midnight on New Years Eve. Microsoft Releases a Fix
As the New Year began early this morning, Gizmodo started receiving lots of reports that people's 30GB Zune's were failing. What was happening, was that at 12:01am PST on 31st December 2008, a bug in one of the drivers unique to a 30GB Zune was not allowing the calendar to update properly. For players that were already on, this resulted in a hard reset at that exact moment. Upon restarting or for those who turned their Zune's on after midnight, they were presented with a locked up Zune which would simply stop at the end of the loading screen and stay there. Microsoft have now released an official statement for how to resolve this issue, which follows below.
Source:
Gizmodo
Early this morning we were alerted by our customers that there was a widespread issue affecting our 2006 model Zune 30GB devices (a large number of which are still actively being used). The technical team jumped on the problem immediately and isolated the issue: a bug in the internal clock driver related to the way the device handles a leap year. That being the case, the issue should be resolved over the next 24 hours as the time change moves to January 1, 2009. We expect the internal clock on the Zune 30GB devices will automatically reset tomorrow (noon, GMT). By tomorrow you should allow the battery to fully run out of power before the unit can restart successfully then simply ensure that your device is recharged, then turn it back on. If you're a Zune Pass subscriber, you may need to sync your device with your PC to refresh the rights to the subscription content you have downloaded to your device.
Customers can continue to stay informed via the support page on zune.net
We know this has been a big inconvenience to our customers and we are sorry for that, and want to thank them for their patience.
Q: Why is this issue isolated to the Zune 30 device?
It is a bug in a driver for a part that is only used in the Zune 30 device.
Q: What fixes or patches are you putting in place to resolve this situation?
This situation should remedy itself over the next 24 hours as the time flips to January 1st.
Q: What's the timeline on a fix?
The issue Zune 30GB customers are experiencing today will self resolve as time changes to January 1.
Q: Why did this occur at precisely 12:01 a.m. on December 31, 2008?
There is a bug in the internal clock driver causing the 30GB device to improperly handle the last day of a leap year.
Q: What is Zune doing to fix this issue?
The issue should resolve itself.
Q: Are you sure that this won't happen to all 80, 120 or other flash devices?
This issue is related to a part that is only used in Zune 30 devices.
Q: How many 30GB Zune devices are affected? How many Zune 30GB devices were sold?
All 30GB devices are potentially affected.
36 Comments on 30GB Zunes Fail at Midnight on New Years Eve. Microsoft Releases a Fix
I had to reinstall the firmware though, might "just work" for you guys, but just in case here is how you do it.
Either let the battery run flat, or disconnect the battery (google), then reconnect the battery/charge up. Then BEFORE the loading bar comes up on the startup screen press Back + Left + Centre. This will put the Zune into recovery mode, unfortunately this will wipe everything on the Zune.
That is what I had to do, because I'd already pulled the battery and tried to recover the firmware. I'm assuming anyone who didn't will have their Zune working fine, but at the same time in case it doesn't I posted that as help for anyone who might need it :)
Oh, and btw, you have your dates wrong. It was the 31st December at 12:01am PST, not January 1st. Also Microsoft said it should fix itself by 12pm GMT, it's 11:50am here and they are now working.
:toast:
Someone needs to fire the idiot who developed such a poor firmware/driver.
we were just having a little fun with it... :eek:
It has to do with the clock engines in the 30GB Zune. The 30GB Zune's clock engine isn't digitally regulated. The revisions after that are. It also had to do with the "leap second". lol.
Fly
While it was up to Microsoft to test the driver, and obviously this little bug slipped through testing, they didn't write or directly cause the bug.
My iPod is fine.