Posted: 2/28/2010 6:02:29 PM EDT
|
I don't know if this is the right forum but here goes.
So I've had my PS3 since they first came out. It's the 60 gig version with all the goodies. It has always run like a champ. Tonight I threw MW2 in and fired it up. I get a message that says it can't import my trophies or something and makes me quit the game. I throw Dante's Inferno in and get the same type message. WTF? When I check my trophies folder everything is there. Last night I got Dead Air from Netflix. I stuck it in the machine and it wouldn't recognize the disk. I puleed it out and the disk was all busted, like someone stepped on it. I didn't look at it before I stuck it in, oops. So did a little piece of blu ray break off and fuck my shit up? If so, I'm assuming that netflix has no liability. The disk probably got broke in the mail. Fuck! Any ideas. |
|
The entire PSN network is down.
It's bizarre... the date/time shows 12/31/1999... it's like a retroactive Y2K problem!!! lol! Sony's competitor to X-box Live, the PlayStation Network, appears to be down across multiple countries including Australia, America and parts of Europe.
"We’re aware that many of you are having problems connecting to PSN, and yes, we’re looking into it," a Sony employee tweeted via the official Sony Twitter account. "Stay tuned for updates." The issue appears to resolve around the service not letting users login to their Playstation Network (PSN) account, but is also presenting some users with an 8001050F error code which usually occurs when user data has become corrupt. Of course, not being able to login to a PSN account also means some users are unable to play games at all which require you to be signed in. "When they [users] try to load up certain games — including the just-released Heavy Rain — they receive the error code and the following message: “Registration of the trophy information could not be completed. The game will now quit.” After the message, the system reboots," Mashable reports. "The problems seem to mostly affect older, “fat” models of the PS3. Slim models are either not impacted or affected far less frequently." Part of the problem, according to popular gaming blog Joystiq, apparently could lie in the fact that some PS3 console dates are for some unknown reason having their dates reset to 12/31/1999, throwing the PSN servers out of whack because the service didn't exist back then. A Sony spokesperson didn't respond to requests for a comment before this post was published, but either way, Sony seem to be assessing the situation, and we'll update once we know more or hear back. |
|
Quoted:
The entire PSN network is down. It's bizarre... the date/time shows 12/31/1999... it's like a retroactive Y2K problem!!! lol! Sony's competitor to X-box Live, the PlayStation Network, appears to be down across multiple countries including Australia, America and parts of Europe.
"We’re aware that many of you are having problems connecting to PSN, and yes, we’re looking into it," a Sony employee tweeted via the official Sony Twitter account. "Stay tuned for updates." The issue appears to resolve around the service not letting users login to their Playstation Network (PSN) account, but is also presenting some users with an 8001050F error code which usually occurs when user data has become corrupt. Of course, not being able to login to a PSN account also means some users are unable to play games at all which require you to be signed in. "When they [users] try to load up certain games — including the just-released Heavy Rain — they receive the error code and the following message: “Registration of the trophy information could not be completed. The game will now quit.” After the message, the system reboots," Mashable reports. "The problems seem to mostly affect older, “fat” models of the PS3. Slim models are either not impacted or affected far less frequently." Part of the problem, according to popular gaming blog Joystiq, apparently could lie in the fact that some PS3 console dates are for some unknown reason having their dates reset to 12/31/1999, throwing the PSN servers out of whack because the service didn't exist back then. A Sony spokesperson didn't respond to requests for a comment before this post was published, but either way, Sony seem to be assessing the situation, and we'll update once we know more or hear back. I know about the above quoted problem, involving signing into PSN, playing online and the trophy stuff......................but it still seems like the OP's situation isn't solved yet. What would any of the above have to do with him not being able to play a BluRay movie disc, and the PS3 not recognizing it? |
|
Quoted:
Quoted:
The entire PSN network is down. It's bizarre... the date/time shows 12/31/1999... it's like a retroactive Y2K problem!!! lol! Sony's competitor to X-box Live, the PlayStation Network, appears to be down across multiple countries including Australia, America and parts of Europe.
"We’re aware that many of you are having problems connecting to PSN, and yes, we’re looking into it," a Sony employee tweeted via the official Sony Twitter account. "Stay tuned for updates." The issue appears to resolve around the service not letting users login to their Playstation Network (PSN) account, but is also presenting some users with an 8001050F error code which usually occurs when user data has become corrupt. Of course, not being able to login to a PSN account also means some users are unable to play games at all which require you to be signed in. "When they [users] try to load up certain games — including the just-released Heavy Rain — they receive the error code and the following message: “Registration of the trophy information could not be completed. The game will now quit.” After the message, the system reboots," Mashable reports. "The problems seem to mostly affect older, “fat” models of the PS3. Slim models are either not impacted or affected far less frequently." Part of the problem, according to popular gaming blog Joystiq, apparently could lie in the fact that some PS3 console dates are for some unknown reason having their dates reset to 12/31/1999, throwing the PSN servers out of whack because the service didn't exist back then. A Sony spokesperson didn't respond to requests for a comment before this post was published, but either way, Sony seem to be assessing the situation, and we'll update once we know more or hear back. I know about the above quoted problem, involving signing into PSN, playing online and the trophy stuff......................but it still seems like the OP's situation isn't solved yet. What would any of the above have to do with him not being able to play a BluRay movie disc, and the PS3 not recognizing it? Two unrelated problems. I puleed it out and the disk was all busted, like someone stepped on it.
Does that sound like a playable disk to you? I would guess that non-busted disks still play fine. |
|
Sorry. I should have been more clear in my OP. I do believe that the posted problem is what I was experiencing. My date is, in fact, all screwed up nd it's a trophy issue. Hiopefully they get that fixed ASAP.
I was not aware of tht issue when I posted this. The reference to the blu-ray disk was purely me speculating on what mught have messed up my system. I never thought that my PS3 destroyed that disk or anything of the like. I screwed up by shoving a disk in my machine which had been damaged, probably in shipping. When I pulled it out, it was kind of cracked/shattered. A small piece could be floating around in my system. I have no idea what to do about that. The next day I tried to play some games and saw the trophy problem. My first thought was that I had broken my machine. Thanks to you guys, I know it's a PSN issue. |
|
Quoted:
Id say you got a splintered disc and the player finished it off. As for the PSN its down, I didnt get hit with the 12/31/1999 until this morning. Fing hackers if I were to guess. May they die a horrible death. Nah - not hackers. There is really no info anywhere to be had, but this is the best guess: The OS reads the date/time from the internal clock. The internal clock is telling the OS that Today is Feb 29, 2010. The OS is not programmed to handle leap year in 2010 so it craps out and gives a default date. The problem is this;
The internal clock was improperly programmed with the leap year(s). The OS is not designed to handle a leap year date on a non-leap year. So Sony will have to release a firmware update to handle leap year every 2 years for those consoles with faulty hardcoded programming. |
|
Quoted:
Quoted:
Id say you got a splintered disc and the player finished it off. As for the PSN its down, I didnt get hit with the 12/31/1999 until this morning. Fing hackers if I were to guess. May they die a horrible death. Nah - not hackers. There is really no info anywhere to be had, but this is the best guess: The OS reads the date/time from the internal clock. The internal clock is telling the OS that Today is Feb 29, 2010. The OS is not programmed to handle leap year in 2010 so it craps out and gives a default date. The problem is this;
The internal clock was improperly programmed with the leap year(s). The OS is not designed to handle a leap year date on a non-leap year. So Sony will have to release a firmware update to handle leap year every 2 years for those consoles with faulty hardcoded programming. so if the bug is preventing us from connecting to PSN how will we get that update? 
|
|
60GB user confirming it's fixed. My clock thought it's April 29th, 2020 when I turned it on, though, so you might want to hit Date & Time and have the clock set via the internet. Just signed back onto PSN.
Once again, problems fixed on the free service in 24 hours, XBL took over a month to fix when it went FUBAR over the holidays a couple years ago. Looks like that $50 a year ain't buying you gloaters much. 
|
|
Quoted:
Quoted:
Quoted:
Id say you got a splintered disc and the player finished it off. As for the PSN its down, I didnt get hit with the 12/31/1999 until this morning. Fing hackers if I were to guess. May they die a horrible death. Nah - not hackers. There is really no info anywhere to be had, but this is the best guess: The OS reads the date/time from the internal clock. The internal clock is telling the OS that Today is Feb 29, 2010. The OS is not programmed to handle leap year in 2010 so it craps out and gives a default date. The problem is this;
The internal clock was improperly programmed with the leap year(s). The OS is not designed to handle a leap year date on a non-leap year. So Sony will have to release a firmware update to handle leap year every 2 years for those consoles with faulty hardcoded programming. so if the bug is preventing us from connecting to PSN how will we get that update?
There was still Internet connectivity (I browsed earlier, as well as Netflix'd) but that "fix in 24hrs" was probably when their leap year mistake went to the next day (2/29/10 to 3/1/10). So they really didn't need to do anything... except wait. I tried to adjust the date manually prior to the 24hr period.. didn't work. I'm thinking it's their PSN servers that couldn't handle the erroneous leap year date incoming from some of the PS3s... I'm not really sure... probably if they could have fixed it server-side it would have happened faster. We'll probably get a patch to prevent this from happening again. |