Sony gains RROD sized issue as PS3 stops "doing everything"

I

I am Penguin

Executive Member
Joined
Jan 26, 2009
Messages
7,712
Reaction score
38
Sony gains RROD sized issue as PS3 stops "doing everything"

Hmm, a 2K bug! Came a bit late?

March has been initially hampered by an inherent bug within Sony’s PlayStation 3 consoles.

With Sony remaining firmly tight lipped on the issue, speculation currently lies in the fact that the PlayStation 3’s clock chip – on all the older ‘fat’ models – is currently searching for February 29th within its 2010 calendar. As well all know, this doesn’t exist and so issues have now arisen in which users are unable to play games, sync trophy data or even connect to the PlayStation Network. It is the 8001050F error code, apparently, are indicative of the machine being locked off PSN and being susceptible to Trophy data corruption.

However, the issue may be able to be fixed. If it is indeed hardware based there is a chance that Sony will be able to re-write the binary codes of the clock chip so that it can ‘understand’ that 2010 and other years won’t have a February 29th. It may also correct itself overnight when it alters onto March 2nd, so maybe Sony are currently playing the waiting game.

However, those that can’t connect to PSN will be left unable to download the patch, if ever managed, that will save their consoles. Sony may be able to utilise a server that isn’t clock-based to counteract this, yet that means the only other option the company has is to release the patch via PlayStation.com to be installed with a USB Stick, or seek some form of distributing discs to retail stores and PlayStation 3 owners directly.

Worst case scenario is that the clock chip is such low level tech within the PlayStation 3 console that it is unable to be patched through firmware, which would mean that if it doesn’t correct itself tonight Sony could be looking at having a much larger issue on their hands.

Some of the techy members on GAF believe that if it is unable to be fixed then Sony will have to recall all affected consoles, creating a situation that will rival even that of Microsoft’s widespread RROD issue with the Xbox 360. With the majority of PS3 owners in possession of a ‘fat’ model, and even Debug units being reportedly affected, this could be an incredibly worrying time for Sony if the issue remains unresolved.
Click to expand...
 
bad just bad,

340x.gif
 
Nope.

I have a 40GB fat and its working fine.
In all areas.

Even checked clock manually, cannot be set to 29 Feb 2010.
It correctly displays date as 01 March 2010.

I think some people are playing others for a fool over the whole PSN problems being experienced atm.
 
from what i read it seem to be the bios clock, and as is normally not firmware upgradable it might be a big problem, and newer ps3 should not be effected as this will only be ps3 before they did changes to the motherboard.
 
Mine works just fine. One of the first 40GB models to come out btw.

If it was a hardware issue, why am I not experiencing it?
 
I have a problem. <sigh>

Turned on my ps3, all seemed fine.. but then I noticed my date had been reset.
So I went and set the date manually.

Tried to play a game off disk, worked fine.
Tried to play a game downloaded... I get "An error occurred during the start operation (8001050F)" Bleh
I try to go online I get "An error has occurred. You have been signed out of PlayStation Network (8001050F)"

:cries:
 
Official 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 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.
Click to expand...

:sniff: :sniff: :cry:
 
is currently searching for February 29th within its 2010 calendar.
Click to expand...
So they probably hard-coded the 2008 leap year...but then it should have shown in 2009 already. Weird & sizable fail.

Edit: How is this anything like RROD? Surely a simply software update can fix this...unlike RROD.
 
Yeah I this is small software glitch compared to the RRoD issue. It's more of a marketing disaster than a complete break down in quality control.
 
wheunis said:
Nope.

I have a 40GB fat and its working fine.
In all areas.

Even checked clock manually, cannot be set to 29 Feb 2010.
It correctly displays date as 01 March 2010.

I think some people are playing others for a fool over the whole PSN problems being experienced atm.
Click to expand...

Yep, we are fools. Our clocks reverted back to 01/01/2000 and we lost access to PSN. Yep a fools glitch alright, a serious one. Hopefully on the 2nd March it will go away.

playstation 3

More than 24-hours ago, PlayStation 3 owners around the world began reporting serious issues with their consoles. While some PS3s have been unable to play games and log into the PlayStation Network, other consoles haven’t experienced any problems. The question is: what is going on?

The first thing to note is that this is not a PlayStation Network issue. These errors and issues are directly related to the hardware side of the PlayStation 3 console. Specifically, the system and OS clocks are conflicting, which is causing erratic system behavior. The system clock is running at all times and only counts forward. When powered on, the system clock confirms what time it is to the OS Clock. On top of that, when a PlayStation 3 is on, a battery inside of the PlayStation 3 gets charged which runs the system clock in the background even when the PlayStation 3 is turned off.

What’s causing the problem?

The system clock thinks that today is a leap year dated February 29th, 2010. Meanwhile, the OS Clock doesn’t have that date available in its table since it doesn’t exist. What we have are two very conflicting dates which have caused the PlayStation 3 to change behavior. It’s hard to tell exactly why the date on many PS3s has been rolled back to 1999, but it could be a protocol set in place by Sony for situations like this.

Why does the system clock think it’s leap year?

Apparently, the older PlayStation 3s have been programmed to think that every even year is a leap year. You might be asking, “Well, why didn’t PS3 consoles face this issue in 2008 then?”. The answer is, because 2008 WAS a leap year. This is an unfortunate set of circumstances, because in reality leap year is every four years, but the console thinks that it is every two.

At this point, one of three things can happen.

1. The official GMT ticks over to March 2nd and the PlayStation 3 moves to March 1st instead of the leap year date which is causing the issues.

2. Sony finds a way to force the System Clock to move to the current date or at least behave properly.

3. There is no way fix the issue and Sony will have to find a plan b.

Some consumers are removing the internal battery to reset the System Clock which apparently has worked thus far. This isn’t a good idea, however, since it voids the warranty and might create more problems if Sony issues a fix. At any rate, in roughly 2-3 hours the official GMT will shift over to the next day, and hopefully the PlayStation 3 will begin working properly again. Until then, we recommend keeping the PlayStation 3 turned off while waiting for an official update from Sony
Click to expand...
 
Last edited:
As far as I know My PS3 doesn't show me a red circle and doesn't scratch my cd's, How is this even remotely as bad as a RROD.
 
I really don't think this is an issue. I'd much rather have this than RROD to be honest. Although I don't get why people still say RROD this and scratched DVD's that.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X