Jump to content
The Unknown Ghosts

Recommended Posts

Latest info on PlayStation Network Status


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 or Dec 31, 1999.

* 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 play back 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 apologize for any inconvenience caused.


For the latest status on this situation please continue to check either the PlayStation.Blog or PlayStation.com.



Communtiy Responses



Here's what's going on right now: something with the PS3's internal clock has borked in some pre-slim models. This is not a PSN issue; it has to do with your PS3's clock. This clock is NOT related to the OS clock. It seems to be a leap year bug. Setting your clock ahead will do nothing. All PS3s around the world were affected at the exact same time.


Does this affect me?


-If you have a Slim PS3, you're good to go. Continue playing it as normal.

-If you have a "fat" PS3, you may be affected. Some fat PS3s have worked ok, but it seems a good majority have been bugged.


What does this bug mean?


-If affected, your date and time has been set to a random past date. This prevents you from signing into PSN, playing any PSN games, or using any DLC. Your trophies will also not display correctly or be able to sync.


How do I fix it?


-You can't. Even if you don't sign into PSN, it won't help. This is a hardware issue.


So, what do I do?


-Wait 24 hours. Other products that have had similar bugs have corrected themselves after the "bugged" day. On Monday around 6pm central time, all PS3s will automatically correct themselves...maybe.


-If that doesn't work, we'll need a firmware update from Sony, which should be a pretty important priority for them right now.


Did I lose my data/themes/etc?


Your save data/games/dlc/themes are fine. They'll be fixed when the PS3 is fixed. Trophies are uncertain right now, but they'll be fine if you've synced them before the PS3 was bugged. Unsynced trophies are an unknown right now.


If I have a bugged PS3, can I still use it?


It's probably not a good idea, as I have no idea what will happen to the trophies you earn during the bugged time. Movies/media will work fine.


So there ya go, my handy FAQ.


Possible explanation:


Originally Posted by iammeiam:

The going theory is that the PS3 is storing some form of date in GMT, then modifying that to get whatever you see in the on-screen clock. That modification process seems to be fine--the system can take 2/28/2010, 9PM GMT, add four hours, and get 3/1/2010, 1AM random time zone.


What's apparently effed, as speculation goes, is when the internal GMT-tracking rolls over to 3/1. It's either not rolling, or rolling to 2/29, at which point a system tries to add/subtract from 2/29, which it can't do because the front-end calendar doesn't have a 2/29/2010, and shit explodes. Seemed to happen around 4PM PDT, which I think is 12AM GMT, so.


And the PS3 launched in 2006; it's hit 4 2/28s so far. 2007 and 2009 were odd-numbered years; 2008 was an even, and a leap year. 2010 is the first even non-leap-year the system's been around for. If some sort of base-level math is choking on itself, it may have ruled out the odd 2007 and 2009 successfully, but is convinced the even 2010 is a leap year (this part I'm less sure of, but is why leap year could theoretically come into play at some point.)

Edited by .TuG.brok21k
Link to comment
Share on other sites

It's totally amazing how Sony's QA didn't catch this! A low Level date bug (Freescale make the motherboards).

Every two years a firmware patch will be needed to band aid this problem! Because flashing the BIOS won't be easy (recall or open it up and break the warranty, unless they find an alternative method). I've backed up my MW2 profile, which is what I'm worried about!


Bring on Midnight!


OR worse case!


RIP ps3 2006 to 1999

Edited by .TuG.brok21k
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in

Sign In Now
  • Create New...