PSN Crashed: 8001050F - Hardware Failure for PS3 Consoles!

[Andrew691]

Can confirm removing the internal battery works, was able to login fine and redownload the activation for Wipeout HD (was saying its a demo) looks like I need to redownload Fury addon tho. All PS Classics seemed to work anyway. I reckon this will be an easy software fix for Sony.

[rotaholic]

Originally Posted by CJPC Just finished talking with a buddy who ran into this issue on his PS3 TEST - he removed the RTC battery for about 10 minutes as I suggested earlier, stuck it back in and he is now back up and running, on PSN and everything! So, if you guys want to give it a try and your box has been opened / out of warranty - it should work! I'd just, for now, set it to today / tomorrow's (3/1/2010) date, to be safe!

CONFIRMED!!!

I'm from New Zealand, 40gb phat PS3. I just took the battery out (took 15mins easy as if your a bit techy) and it works pefect.

Time to get my MW2 fix :-)

[misterwiseguy]

i was investigating the matter of this error (8001050F) on playstation website, when i came across this http://boardsus.playstation.com/t5/P...e/m-p/30491999 dated 2007, someone posting for help on the same issue... so its happened before.

[Transient]

Really interesting that pulling the RTC battery serves as a workaround. Has anyone tried (after doing the battery fix) setting their clock to 28/02/2010 at 23:59 GMT and waiting a minute to see if the problem reoccurs?

I wonder if the RTC is going to an invalid date (29/02/2010) or possibly overflowing some sort of count (eg. something similar to epoch).

Last edited by Transient; 03-01-2010 at 03:24 AM.

[CompTronicsTec]

So i dont get it, granted im not as technical as many of the people here, but what exactly triggered this? What was so special about todays date? Why didnt this affect slims?

Had i not read this thread, i'd simply assume PSN was down, but from what i can gather it is up and running and the issue is actually some conflict with the date being set incorrectly because of some hardware glitch?

As for the notion that this was a planned or purposefully triggered event from Sony...i'm open to the idea but one major issue conflicts with that. If Sony had planned this, lets say hypothetically as a test to see if they could target just fat's for a future sneaky update... they wouldnt have let it last for so long. If anything theyd want it to last relatively short, long enough to get some attention but short enough to appear to be on top of fixing it (good PR). Last thing theyd want to do before a sneaky patch is aggravate the people they are about to upset.

Im interested to see what course of action is taken to fix this, will they;

• let it run its course/self correct
• fw update, possibly including some other unwanted tweak like otheros removed
• milder update that just resolves the issue

At this point i dont see them "recalling" any units either... it would make them look horribly bad if they had to recall what i will guess to be tens of thousands if not hundreds of thousands of units. Not to mention how many of us would not be willing to give up the fat for a slim.

[Transient]

Originally Posted by misterwiseguy i was investigating the matter of this error (8001050F) on playstation website, when i came across this http://boardsus.playstation.com/t5/P...e/m-p/30491999 dated 2007, someone posting for help on the same issue... so its happened before.

Probably the error code indicates an invalid date. I bet that guy either had a dead RTC battery or somehow changed the clock on his PS3 to something in the past.

Originally Posted by dvdesign So i dont get it, granted im not as technical as many of the people here, but what exactly triggered this? What was so special about todays date? Why didnt this affect slims? Had i not read this thread, i'd simply assume PSN was down, but from what i can gather it is up and running and the issue is actually some conflict with the date being set incorrectly because of some hardware glitch? As for the notion that this was a planned or purposefully triggered event from Sony...i'm open to the idea but one major issue conflicts with that. If Sony had planned this, lets say hypothetically as a test to see if they could target just fat's for a future sneaky update... they wouldnt have let it last for so long. If anything theyd want it to last relatively short, long enough to get some attention but short enough to appear to be on top of fixing it (good PR). Last thing theyd want to do before a sneaky patch is aggravate the people they are about to upset. Im interested to see what course of action is taken to fix this, will they; let it run its course/self correct fw update, possibly including some other unwanted tweak like otheros removed milder update that just resolves the issue At this point i dont see them "recalling" any units either... it would make them look horribly bad if they had to recall what i will guess to be tens of thousands if not hundreds of thousands of units. Not to mention how many of us would not be willing to give up the fat for a slim.

Considering the earlier posts from others confirming that resetting the RTC is a workaround for the problem, I imagine absolute worst case Sony will issue an update that does just that.

Also, the problem is affecting people with offline PS3's, so the idea that it has anything to do with some clandestine plan on Sony's part is just pure paranoia, IMO.

Last edited by Transient; 03-01-2010 at 03:31 AM. Reason: Automerged Doublepost

[grudge1981]

Originally Posted by dvdesign So i dont get it, granted im not as technical as many of the people here, but what exactly triggered this? What was so special about todays date? Why didnt this affect slims? Had i not read this thread, i'd simply assume PSN was down, but from what i can gather it is up and running and the issue is actually some conflict with the date being set incorrectly because of some hardware glitch? As for the notion that this was a planned or purposefully triggered event from Sony...i'm open to the idea but one major issue conflicts with that. If Sony had planned this, lets say hypothetically as a test to see if they could target just fat's for a future sneaky update... they wouldnt have let it last for so long. If anything theyd want it to last relatively short, long enough to get some attention but short enough to appear to be on top of fixing it (good PR). Last thing theyd want to do before a sneaky patch is aggravate the people they are about to upset. Im interested to see what course of action is taken to fix this, will they; let it run its course/self correct fw update, possibly including some other unwanted tweak like otheros removed milder update that just resolves the issue At this point i dont see them "recalling" any units either... it would make them look horribly bad if they had to recall what i will guess to be tens of thousands if not hundreds of thousands of units. Not to mention how many of us would not be willing to give up the fat for a slim.

Basically it seems to be a Y2K like bug of sorts. Possibly having something to do with leap year?

[iomega1972]

Originally Posted by grudge1981 Basically it seems to be a Y2K like bug of sorts. Possibly having something to do with leap year?

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 wrong, 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. Everything started to collapse around 4PM PDT, which I think is 12AM GMT.

And the PS3 launched in 2006; it’s hit four 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).

[cookie040]

Hey.

I got the trophy error that everyone's experiencing but I'm not playing online. I put another game in and it seemed to be ok.
Some thread advised formatting the drive. all that did was delete all my media. If the error problem is the psn then why would I be getting "registration of trophy information could not be completed" error 8001050f?

Its frustrating. I love that game. Any ideas how the system works in this situation?

Cheers,
cc

[f3itic3ira]

Originally Posted by iomega1972 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 wrong, 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. Everything started to collapse around 4PM PDT, which I think is 12AM GMT. And the PS3 launched in 2006; it’s hit four 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).

you do have a brilliant point, even though i was not plagued with this issue since i have a slim, i was concerned and up to date with what was going on, i totally agree with you.