Updated: Playstation Network (PSN) Error 8001050F resolved
Finally, after 24 hours the weird 8001050F error, others call it as 8001050F bug was finally resolved. The speculations about the error is caused by the leap year problem were right.
More and more users left a comment in our first post about PS3 Error 8001050F claiming that they can now play with their PS3 and everything is back to normal.
This is a great news to everyone, specially to those who are ranting and saying that Playstation and Sony sucks. The wait is over and if you’re patient enough to wait for this moment, then good for you.
Your patience is now rewarded and now you can play with your favorite online games in the best and most awesome gaming console in the entire universe!
For those who are still encountering this weird bug, don’t hesitate to leave a comment below and share your thoughts about this resolved PSN error.
Update 03/01/10: Patrick Seybold released an official statement in the Playstation blog and he said that the error has been resolved.
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.