Help-frozen zune!!!!

Woke up this morning to a FROZEN ZUNE, fell asleep listening to music, when I awoke after midnight Zune was FROZEN.

 Ne0Striker wrote:

 Melissamusic wrote:

 KarboMusic wrote:

 Melissamusic wrote:

Please forgive my ignorance, were is it getting an illogical time/date stamp?

 KarboMusic wrote:

 Melissamusic wrote:

 KarboMusic wrote:

 Melissamusic wrote:

I agree. Why would the Zune Player care what time or what day it is without any way to check the correct time? I would understand that the device could fail if there were a conflict in the times if connected to a computer but for it to fail on its own sounds kind of fishy. I think M$ is just buying themselves some time to come up with a fix.

Believe it or not... There was a time when a device could contain an internal clock all by itself... Thats not fishy...

So it has an internal clock, so if that clock is wrong then it would just show the wrong time. not crash a system.

Not really, if a single line of code attempts an operation (dealing with dates/timestamps) and gets back a time/date that isn't "logical" there is going to be an unexpected result. (IE: Freeze)

I'll try once more... There could be hundreds if not thousands of functions in the zune code and drivers that reference times and dates. It may be last modified timestamps on files, driver version times/dates, DRM, security, the list goes on and on. It only takes a single "operation" where a conversion, comparison etc. says "take the current time date and compare it to ____". When the code does this and there is suddenly a date that it doesn't expect to be possible, you have an error. Yes its simple to add code to prevent the freeze (could have been missed) but the scenario is completely plausible, more than plausible, its now a reality.

Thanks for trying to explain it to me. Maybe I am just not getting it. But if the code is asking for a time check then what is it checking against if not the internal clock itself. And if you are saying is correct, which I am not disputing, then waiting one day will not fix it.

The internal clock apparently doesn't know how to handle the extra day in a leap year. So when the internal clock reaches this 'strange day' it throws an error in the form of the freeze. once the internal clock goes back to a day it will recognize i.e. Jan 1 20XX then thigns to go back to normal operation

You have been very helpful and patient in explaining this to me, Thank you. I just still think that the problem is more serious than just waiting a day so that everything will be back in sync. Hopefully I am wrong and I can begin using my Zune again tomorrow.

i for one am in no way disappointed with my zune 30

have used it about non stop for about 2 years now

i am disappointed with this issue, and the way it seams to be being handled. an issue with leap year? after the y2k scare you wold think this would not be that big an issue

 

 Melissamusic wrote:

 KarboMusic wrote:

 Melissamusic wrote:

Please forgive my ignorance, were is it getting an illogical time/date stamp?

 KarboMusic wrote:

 Melissamusic wrote:

 KarboMusic wrote:

 Melissamusic wrote:

I agree. Why would the Zune Player care what time or what day it is without any way to check the correct time? I would understand that the device could fail if there were a conflict in the times if connected to a computer but for it to fail on its own sounds kind of fishy. I think M$ is just buying themselves some time to come up with a fix.

Believe it or not... There was a time when a device could contain an internal clock all by itself... Thats not fishy...

So it has an internal clock, so if that clock is wrong then it would just show the wrong time. not crash a system.

Not really, if a single line of code attempts an operation (dealing with dates/timestamps) and gets back a time/date that isn't "logical" there is going to be an unexpected result. (IE: Freeze)

I'll try once more... There could be hundreds if not thousands of functions in the zune code and drivers that reference times and dates. It may be last modified timestamps on files, driver version times/dates, DRM, security, the list goes on and on. It only takes a single "operation" where a conversion, comparison etc. says "take the current time date and compare it to ____". When the code does this and there is suddenly a date that it doesn't expect to be possible, you have an error. Yes its simple to add code to prevent the freeze (could have been missed) but the scenario is completely plausible, more than plausible, its now a reality.

Thanks for trying to explain it to me. Maybe I am just not getting it. But if the code is asking for a time check then what is it checking against if not the internal clock itself. And if you are saying is correct, which I am not disputing, then waiting one day will not fix it.

I am only giving examples of how it could happen and its not my code so I can't add much more.

But if the code is asking for a time check then what is it checking against if not the internal clock itself.

Precisely, the code doesn't care where the "bad" time came from, it is simply comparing A to B and crashing. In addition the actual internal clock may be running fine even though you cannot complete the entire boot process. If this were the case then tomorrow the internal clock will be sending the code dates/times it can understand again. These are just my representations of how things like this can happen. I have no idea what actually happened. Regards- kw

Wow mine did this today as well just read the 256 pages of this thread :o I still don't see how rebooting it tomorrow will correct this and all will be ok once again. Well if not I will ask Microsoft to replace mine or open a Class Action Lawsuit.

This whole thing had me worried today because I, like everyone else here, encountered this problem with my Zune.  I was charging it up for my long night of work and noticed that things didn't look right.  I tried all the usual stuff with the results that everyone knows about now. . . so my next step was. . . drain the thing.  I never even thought to jump over here on the forums because - heck, musta been something I did and I still have a few things to try.  Color me suprised when I saw one of the headlines on MSN's home page.  I read it and all of a sudden I could feel the sense of relief that it wasn't me and I was already halfway to the fix by draining my Zune.  Anyway, seeing that this thread made it in the story I had to come see if there was a sense of outrage or that of pure relief that this time tomorrow things should be back on track.  For me, I find it comfortably amusing because it's a temporary thing.  Sure, I don't have my music for a day - but with having one dog just recovered from surgery (eating rocks) and another dog almost dying at the vet getting his teeth cleaned - I'll take the Zune not working for a day.  This year has tried to go so terribly wrong so many times. . .  here's hoping that 2009 goes a lot smoother.    Happy New Year everyone! 

---

Live dangerously. . . turn shuffle on!

The news media seems to think that zune sucks and always has.  And the quility of the content avalible is horrible. I guess we all thought that  microsoft would be a supior product....guessed wrong

 Melissamusic wrote:

 Ne0Striker wrote:

 Melissamusic wrote:

 KarboMusic wrote:

 Melissamusic wrote:

Please forgive my ignorance, were is it getting an illogical time/date stamp?

 KarboMusic wrote:

 Melissamusic wrote:

 KarboMusic wrote:

 Melissamusic wrote:

I agree. Why would the Zune Player care what time or what day it is without any way to check the correct time? I would understand that the device could fail if there were a conflict in the times if connected to a computer but for it to fail on its own sounds kind of fishy. I think M$ is just buying themselves some time to come up with a fix.

Believe it or not... There was a time when a device could contain an internal clock all by itself... Thats not fishy...

So it has an internal clock, so if that clock is wrong then it would just show the wrong time. not crash a system.

Not really, if a single line of code attempts an operation (dealing with dates/timestamps) and gets back a time/date that isn't "logical" there is going to be an unexpected result. (IE: Freeze)

I'll try once more... There could be hundreds if not thousands of functions in the zune code and drivers that reference times and dates. It may be last modified timestamps on files, driver version times/dates, DRM, security, the list goes on and on. It only takes a single "operation" where a conversion, comparison etc. says "take the current time date and compare it to ____". When the code does this and there is suddenly a date that it doesn't expect to be possible, you have an error. Yes its simple to add code to prevent the freeze (could have been missed) but the scenario is completely plausible, more than plausible, its now a reality.

Thanks for trying to explain it to me. Maybe I am just not getting it. But if the code is asking for a time check then what is it checking against if not the internal clock itself. And if you are saying is correct, which I am not disputing, then waiting one day will not fix it.

The internal clock apparently doesn't know how to handle the extra day in a leap year. So when the internal clock reaches this 'strange day' it throws an error in the form of the freeze. once the internal clock goes back to a day it will recognize i.e. Jan 1 20XX then thigns to go back to normal operation

You have been very helpful and patient in explaining this to me, Thank you. I just still think that the problem is more serious than just waiting a day so that everything will be back in sync. Hopefully I am wrong and I can begin using my Zune again tomorrow.

 

Well, we will have an absolute answer once the clock hits 12:01 lol. either it will work or it wont, and there our answer will be :P

---

Army STRONG

i hope you have a baby and i hope someone punches him/her in the face.

My Zune has been doing that freeze for about 2 weeks ???  We let the battery die and that recharged and it was ok until I added more music then it did the freeze thing again.  So hopefully Microsoft's fix will work.  I will let you know if it does not.

My  zune has been doing this since summer. Not only does the zune freeze as soon as I plug it into a usb port my whole system locks up. I have to power down my PC and reboot the whole thing. I think M$ is full of bull, it's time to look into an i pod. I for one am sick and tired of this thing!

ur an ssshole