PS3 Error: 8001050F Caused By Clock Bug, Fix Within 24 Hours

Sony hopes to fix the PlayStation 3-stalling 8001050F error in a day. But, if you have a fat PS3, do not use it for 24 hours. The news came in Sony's first comprehensive statement about the error plaguing PS3s worldwide.

Today's statement came from Sony Computer Entertainment of America spokesman Patrick Seybold, who told Kotaku yesterday that Sony was on the case. The company's engineers in Japan and elsewhere are trying to resolve a problem that has left PS3s around the world in an unusable state. Original theories that this only affected online-connected consoles, has been disproven.

From Sony:

As you may be aware, some customers have been unable to connect to the PlayStation Network today. This problem affects the models other than the new slim PS3.

We believe we have identified that this problem is being caused by a bug in the clock functionality incorporated in the system.

Errors include:

* The date of the PS3 system may be re-set to Jan 1, 2000.

* When the user tries to sign-in to the PlayStation Network, the following message appears on the screen; "An error has occurred. You have been signed out of PlayStation Network (8001050F)".

* When the user tries to launch a game, the following error message appears on the screen and the trophy data may disappear; "Failed to install trophies. Please exit your game."

* When the user tries to set the time and date of the system via the Internet, the following message appears on the screen; "The current date and time could not be obtained. (8001050F)"

* Users are not able to playback certain rental video downloaded from the PlayStation Store before the expiration date.

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 apologise for any inconvenience caused.

For the latest status on this situation please check either the PlayStation blog ( or

- Show quoted text -

One possible fix suggested by some gamers has been a manipulation of the console's battery. Seybold could not confirm to Kotaku that this works and said that opening the PS3's shell would void the machine's warranty.

We will have more on this major story as it develops.


    This sucks...Yay pudding!

    Erm- the Sony warranty on almost ALL fat PS3 models would have expired. Unless you are unfortunate enough to have purchased in the 6 mths between March 1 and Sep 1 2009.

    I would imagine there will be a firmware update that corrects the phantom leap year issue. MW2 was painful last night as I was matching with mostly Americans, or American GIs in Japan. Either way the lag was spectacular. At least I seemed to identify that the grand majority of my PSN friends have fat consoles- there were only around 5 or so on at 11pm, normally 15 or 20.

    Please... please don't tell me this is because it is a leap year.

    The PS3 launched Nov 11 2006, meaning it just (well, by a fair few months) missed the last one. Therefore, this is it's first leap year out in the wild.

    The fact that the slims have survived but the fats haven't can only mean they changed something to fix this problem but perhaps they never got around to fixing it on the fats.

    Most annoying thing is that I can't even play some of my completely offline games like 'Monsters'. It thinks I haven't purchased the game! 'Shooter' also errors before it even leaves the XMB.

      its not a leap year this year o_0 2010/4=502.5

      I think you'll find 2008 was a leap year, and the next one is in 2012.........

      2010 is not a leap year...!

      It's not because it's a leap year.

      Want to know why?

      Because 2010 isn't a leap year.

    Man I got a lot of stuff done last night! Hooray for forced non gaming nights!

    That's a pretty serious problem if they're asking "we advise that you do not use your PS3 system"... :/

    I would say that yes it is the leap year that's causing it. Probably some sync-ing error between whatever server clock they have and the console internal clock.

    I guess it's time to get the 360 out :)

    I still love my fate whale of a ps3..

    Umm, it isn't a leap year this year. 2008, 2012 are leap years.

    So its already survived a leap year.

    Here's the secret that those corporate fat cats at Sony don't want you to know:

    All years are leap years! 2010/4 = LEAP YEAR!

      huh? All years are leap years? 2010/4 = LEAP YEAR?

      Maybe in your world but not in the real one.

        Towlson's logic is flawless. Surely it is you, Ema Nympton, who is in their own world of madness.

        Twilb Out

          That logic unfortunately isn't 100% correct either, there are a few exceptions...

          "Years that are evenly divisible by 100 are not leap years, unless they are also evenly divisible by 400, in which case they are leap years. For example, 1600 and 2000 were leap years, but 1700, 1800 and 1900 were not. Similarly, 2100, 2200, 2300, 2500, 2600, 2700, 2900 and 3000 will not be leap years, but 2400 and 2800 will be"

          So in 2100 (not that I'll be alive), it won't be a leap year!

    I gotta say I really appreciated having both consoles last night. I was able to jump into Bioshock2 on the 360 without missing a beat.
    I feel for you guys who only have the PS3. Here's hoping they can stick to the 24 hr turnaround.

    I really hope resetting the time/date manually last night didn't stuff anything up - I had no choice, I had PlayTV scheduled!!

      Where is rufus and what have you done with him?!!

      I never gave up hope. Give him my love, you bastard.

    Got a fatty bought in april last year so still have warranty. when i got home from work last night the ps3 was on and my bro was playing nba2k10 on it with no issues. the clock even had the right date, only thing was it had either adjusted for daylight savings early or never did at all cause it was 1 hour behind, but its been like that for at least the last few days.
    its been off the cable for the past week and is usually switched off at the power switch (ie never on red light standby) if that makes any difference

    Personally i wish this happened every year.
    It could be like a PS3 addicts time to consider some rehab.

    My only issue is why when i was at a climactic point in heavy rain did this have to happen =[.

    But to be honest this error is hilarious more than anything since it's world wide =P.

    Also lets question..
    If you could still return you ps3 even if you bought it at release (for 1000AUD why would you...) How much do you recon sony would loose?

    i didnt turn on my PS3 since sunday night (Feb. 28), didnt turn it on yesterday for i was doing something significant, trolling 'te internets..

    good thing that in my trolling i saw this news and now i still havent turned on my 60GB cause im a little paranoid, well for one cause i just got my refurbished PS3 a couple days ago (waited for a month or so for it to be fixed!!) and ill be dammned if that thing happens again!!

    dang hope they fix this problem before the plethora of games comes out, FFXIII, and a little game called GOD OF WAR 3!!!!!..poor Heavy Rain, its safe to assume that most players are itching to play it, good i got my Heavy Rain fix i played it straight for the whole 2 days prior :)

    Ouch...well, at least I got a slim. But, seriously, I hope they fix this soon, and that all will be well with PS3 owners and their systems.

    There was an error? I knew nothing about it whilst playing Heavy Rain all last night.

    Im really confused. Extremely confused, my mates PS3 slim......wont ign him into PSN, wont let him change times or dates, its got this bug?!
    Is this the only PS3 slim to have this problem, or are there more out there?
    His PS3 worked fine over the 28/2-4/3 time period, and today, 5/3, its decided not to work?!
    Any Ideas?

Join the discussion!

Trending Stories Right Now