Post: Playstation 3s Struck By PSN Error
Options
03-01-2010, 01:15 PM
#1
Paul
Edwards
Today, many Playstation owners have reported having difficulty getting online to 'PSN', the global PlaystationNetwork required to play games online.
People struck with the error received this:
Originally posted by another user
"An error has occurred. You have been signed out of PlayStation Network (8001050F)"
This means a corrupted data problem has occured on the PS3. Many users are also claiming that they have lost saved games and trophies for many games.
On February 28, the calendar on original PS3 systems was reset to January 1, 2000, blocking access to online content. It has been confirmed that Slim PS3 systems have not been affected.
The consoles will not play games with trophies, will fail to log on to PSN and will not play classic games or use premium themes.
The error has been identified to strike offline systems.
Sony have said this about the issue:
Originally posted by another user
We're aware that many of you are having difficulty connecting to the PlayStation Network this evening. Those of you with "slim" PS3s (the 120/250 GB models) appear to be unaffected.
Know that we have narrowed down the issue and have engineers working to restore service even as you read this. We apologize for any inconvenience this may cause you, and genuinely appreciate your patience while we work to resolve this.
Know that we have narrowed down the issue and have engineers working to restore service even as you read this. We apologize for any inconvenience this may cause you, and genuinely appreciate your patience while we work to resolve this.
The problem is not with PSN as only certain models are affected, this leads to suspicions about a problem with the transfer between February and March leading to a leap year problem with the firmware.
If you are concerned and wish to get updates as soon as they come, follow Sony's Twitter by clicking You must login or register to view this content..
EDIT:
TO ALL PS3 SLIM USERS, PLEASE DO AVOID USING YOUR CONSOLES UNTIL SONY HAS RELEASED A FIX.
USING YOUR CONSOLE CAN CAUSE ERRORS UPON CONNECTING TO PSN INCLUDING FAULTY TROPHY RECORDING AND NOT BEING ABLE TO RESTORE CERTAIN DATA.
Last edited by
Paul ; 03-01-2010 at 06:19 PM.
The following 29 users say thank you to Paul for this useful post:
AbusedTampon, bertieboy7, Darkdonut, Elder Legendah, Helios, Jayy, Killer372, King RAM, little_legz, longjohnsilver, Marioman, mason1985, muman, Newfie, ninjamike, Paschendale, SAS_Racer, JimErased, Steve, Stub Hero, Tom1210, Waq1, willshadyy_187, Winters37, xFutterr, xXM@DM@RCXx, ZachFean, ziiJEEZYiiz
03-01-2010, 06:29 PM
#38
callofduty07
Keeper
my slims working , ive only got 3 friends online ( of out 100 )
03-01-2010, 06:49 PM
#40
Gr8-1-84
Guest
Going by mine which broke sometime after 3:00am GMT and before 11:00am... I reckon it's probably set to american time zone as america are behind the uk, so 12:00 am us time is well after 3:00 am GMT what time did the american models stop working? I would say depending on your time zone 12:00am or within a 2 hours of?
03-01-2010, 06:54 PM
#41
iRunThis2010
Bounty hunter
This sucks! -.-"
---------- Post added at 01:54 PM ---------- Previous post was at 01:50 PM ----------
Question: Do you think formatting the system will solve this problem.?
---------- Post added at 01:54 PM ---------- Previous post was at 01:50 PM ----------
Question: Do you think formatting the system will solve this problem.?
03-01-2010, 07:54 PM
#43
xXM@DM@RCXx
Maggbot timeout!
its been doing my nutt in all day i thought it was because i changed my broadband supplier and i was trying to sign in with a different ISP...
HOW DULL AM I.. LMFAO
HOW DULL AM I.. LMFAO
03-01-2010, 08:22 PM
#44
Pizzaiolo
Guest
My 80 GB PS3 had this problem and I just now went in and changed the date and time manually on my PS3 from the menu. It's 3/01/2010 at 15:18 EST, and now it connects just fine.
As someone speculated, it's most likely a bug in their code that thinks it's 2/29. So don't reformat or anything else, just set the time manually and hopefully it'll be fine (until the next time it encounters sloppy Sony code).
As someone speculated, it's most likely a bug in their code that thinks it's 2/29. So don't reformat or anything else, just set the time manually and hopefully it'll be fine (until the next time it encounters sloppy Sony code).
Copyright © 2024, NextGenUpdate.
All Rights Reserved.
