Anyone run across this latest error?
http://www.buzzybloggers.com/headlines/8216/ps3-error-code-8001050f-sony-playstation-network-crash/
No reason has yet been given, but since it happened on or about February 28/March 1, it looks suspiciously like a calendar error to me. Maybe some cluck…er, clock is confused about whether this is leap year or not?
["We hope to resolve this problem within the next 24 hours. In the meantime, if you have a model other than the new slim PS3, we advise that you do not use your PS3 system, as doing so may result in errors in some functionality, such as recording obtained trophies, and not being able to restore certain data.
As mentioned above, please be advised that the new slim PS3 is not affected with this error. We are doing our best to resolve the issue and do apologize for any inconvenience caused.
For the latest status on this situation please continue to check either the PlayStation.Blog or PlayStation.com."](http://blog.us.playstation.com/2010/03/latest-info-on-playstation-network-status/)
So what exactly happened? Did Sony fix it or did it resolve itself after 24 hrs?
I’m not quite certain if they put in a fix or not, but Sony has given the all-clear.
It fixed itself at about 7pm EST last night. It screwed up a number of trophies for me, but nothing irrepairable.
So their software somehow thought that 2010 was a leap year? How on earth did they manage that bug?
Looks like I was right, and it was a leap year error. But what kind of algorithm is being used that would identify 2010 as a leap year?
I’ve heard a theory that it may have been interpreting 10 as hex value instead of as decimal, which means that the PS3 may have thought that it was the year 2016 instead.