Czhurnies1 wrote:
While overall I have been happy with the DEVICE, ( I maintain a LOVE / HATE relationship with thte software and Microsoft in general ) I just experienced this for the second time on my 80Gb device. I have never seen this occur on my 30Gb piece. I have owned Zunes since the Original Release in Nov x years ago.
Both times the symptoms are the same. The unit FREEZES during playback and then after the battery runs down, I'll hook it up to power and walah!
Nothing is accessable on the Zune. It says there is nothing, but if you hook it up to a computer, the information bar looks normal. PICs, VIDs, MUSIC, etc,,,, you just can't access it.
The only thing that has worked successfully for me is to completely start over. Until it happens again... and again?
This is a problem - it would be nice if there were some way to trouble shoot this without wiping the device. If it's a Table on the device - it'd be nice to have a tool for correction. At a nearly full 80Gb device - and the esoteric issues with album info on the device ( wrong album pics etc.. ) the act of replentishing everything back on the device takes DAYS - not hours........
The issue is most likely data corruption on the disk. The question is what is causing this...if the music sync's over and plays OK even once, then it's not the Zune Software and not the USB drivers or your PC. It could be a firmware glitch (theoretically...) on the device, so a firmware reinstall could fix it. Most likely though, is a head crash...usually caused by a shake or mechanical shock to the unit at just the right time (i.e., the disk read/write head is flying...) What happens when the head crashes is that you lose some data. If it was flying over a song track, that song gets messed up and that could cause errors and freezing, etc. If your zune then says nothing is accessible, it means something happened to the file directory itself on the disk (which tells the disk where to seek to access any particular file.) And don't forget that the device firmware, games, etc. are also probably stored on the disk and read into RAM when you boot up the device.
The trick is to figure out what's causing this. It's not at all likely to be a firmware bug, or it would be rampant and affecting a very big portion of the users, in my opinion...