# Sony PS3 Error 8001050F

**URL:** <https://boards.straightdope.com/t/sony-ps3-error-8001050f/530900>\
**Category:** The Game Room\
**Created:** [March 1, 2010, 7:04pm UTC](https://boards.straightdope.com/t/sony-ps3-error-8001050f/530900 "2010-03-01T19:04:54Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Musicat](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/musicat/32/20189_2.png) [@Musicat](https://boards.straightdope.com/u/Musicat)\
**Post date:** [March 1, 2010, 7:04pm UTC](https://boards.straightdope.com/t/sony-ps3-error-8001050f/530900/1 "2010-03-01T19:04:54Z")

</div>

Anyone run across this latest error?

[http://www.buzzybloggers.com/headlines/8216/ps3-error-code-8001050f-sony-playstation-network-crash/](http://www.buzzybloggers.com/headlines/8216/ps3-error-code-8001050f-sony-playstation-network-crash/)

> **[PS3 crash fix due within 24 hours](https://www.gamespot.com/articles/ps3-crash-fix-due-within-24-hours/1100-6252585/)**
>
> \[UPDATE 2\] Sony says error affecting pre-Slim consoles likely related to system's internal time clock, urges owners to keep consoles turned off until fix arrives; problem beginning to abate, but trophy status unclear.

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?

---

<div class="post-metadata">

**Author:** ![Hamlet](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/hamlet/32/2818_2.png) [@Hamlet](https://boards.straightdope.com/u/Hamlet)\
**Post date:** [March 1, 2010, 7:56pm UTC](https://boards.straightdope.com/t/sony-ps3-error-8001050f/530900/2 "2010-03-01T19:56:12Z")

</div>

["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://PlayStation.com)."]([http://blog.us.playstation.com/2010/03/latest-info-on-playstation-network-status/](http://blog.us.playstation.com/2010/03/latest-info-on-playstation-network-status/))

---

<div class="post-metadata">

**Author:** ![enomaj](https://avatars.discourse-cdn.com/v4/letter/e/59ef9b/32.png) [@enomaj](https://boards.straightdope.com/u/enomaj)\
**Post date:** [March 2, 2010, 3:13pm UTC](https://boards.straightdope.com/t/sony-ps3-error-8001050f/530900/3 "2010-03-02T15:13:49Z")

</div>

So what exactly happened? Did Sony fix it or did it resolve itself after 24 hrs?

---

<div class="post-metadata">

**Author:** ![Hal\_Briston](https://avatars.discourse-cdn.com/v4/letter/h/a9a28c/32.png) [@Hal\_Briston](https://boards.straightdope.com/u/Hal_Briston)\
**Post date:** [March 2, 2010, 3:24pm UTC](https://boards.straightdope.com/t/sony-ps3-error-8001050f/530900/4 "2010-03-02T15:24:17Z")

</div>

I’m not quite certain if they put in a fix or not, but [Sony has given the all-clear](http://blog.us.playstation.com/2010/03/playstation-network-service-restored/).

---

<div class="post-metadata">

**Author:** ![Munch](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/munch/32/5281_2.png) [@Munch](https://boards.straightdope.com/u/Munch)\
**Post date:** [March 2, 2010, 3:30pm UTC](https://boards.straightdope.com/t/sony-ps3-error-8001050f/530900/5 "2010-03-02T15:30:29Z")

</div>

It fixed itself at about 7pm EST last night. It screwed up a number of trophies for me, but nothing irrepairable.

---

<div class="post-metadata">

**Author:** ![Rysto](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@Rysto](https://boards.straightdope.com/u/Rysto)\
**Post date:** [March 2, 2010, 5:58pm UTC](https://boards.straightdope.com/t/sony-ps3-error-8001050f/530900/6 "2010-03-02T17:58:08Z")

</div>

So their software somehow thought that 2010 was a leap year? How on earth did they manage that bug?

---

<div class="post-metadata">

**Author:** ![Musicat](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/musicat/32/20189_2.png) [@Musicat](https://boards.straightdope.com/u/Musicat)\
**Post date:** [March 2, 2010, 6:04pm UTC](https://boards.straightdope.com/t/sony-ps3-error-8001050f/530900/7 "2010-03-02T18:04:10Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Rysto](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@Rysto](https://boards.straightdope.com/u/Rysto)\
**Post date:** [March 2, 2010, 7:27pm UTC](https://boards.straightdope.com/t/sony-ps3-error-8001050f/530900/8 "2010-03-02T19:27:36Z")

</div>

> [@Musicat](#):
>
> 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.
