While there hasn't been any official word from Sony, forums all over the net are showing many users have seen the end of their problems with error 8001050F. I can report that my PS3 is working just fine now, though the date reads 2/28 instead of 3/1. I signed successfully into the Playstation Network and booted up Heavy Rain with no problems. If you haven't seen a change yet, hold out! All will be well soon.
This problem has lasted just over a day, and there's no word if Sony
actually did anything. As both Josh and I posted, there was always the possibility that this problem would fix itself when we got to 12:00am March 2nd GMT. And, while that time hasn't quite arrived yet (the problem started for me shortly before 12:00am GMT anyway, so the 24 hours could still be intact), it's possible that the internal clock is done with all its shenanigans of a 2/29/2010, and has reset itself. Of course, the fact that my date still reads 2/28 also points to an update from Sony, so the issue is puzzling. Since I didn't have to download any system updates, the latter doesn't seem likely.
More to come once there's anything official on the matter.
Update: Official word has come down from Sony on the end of these PS3 issues. And the issue is pretty much as everyone theorized. Full post from Playstation.Blog:
We are aware that the internal clock functionality in the PS3 units other than the slim model, recognized the year 2010 as a leap year. Having the internal clock date change from February 29 to March 1 (both GMT), we have verified that the symptoms are now resolved and that users are able to use their PS3 normally. If the time displayed on the XMB is still incorrect, users are able to adjust time settings manually or via the internet. If we have new information, we will update you through the PlayStation.Blog or PlayStation.com. We apologize for any inconvenience this may have caused.
So...they figured out the same thing we all did, but much later (or wanted to confirm it technically somehow before saying anything) and then apparently waited around for the GMT time to change to March 1/March 2 (depending on how you look at it).
I'm sure they are or have been working on a fix. We don't need this happening again in 2014. But, at least until then, it's smooth sailing.
How could I not pick this up as soon as it came out? One of my most anticipated sequels, regardless of whether or not there was really a need for it.
Loading comment data
