Hard Light Productions Forums
Off-Topic Discussion => Gaming Discussion => Topic started by: aldo_14 on November 02, 2006, 08:09:06 am
-
http://news.spong.com/article/11055
Reports are emerging today of serious ‘fatal error’ faults with Microsoft’s new 360 dashboard update which is causing some 360 consoles to die completely.
The Dutch guys over at Fok! Games reported earlier that:
When you do the following with your new Xbox 360 you will be getting a fatal and permanent “System Error”. That means you should not do this!
• Boot the console.
• Select the language.
• Select “I am a member of Xbox Live”
• Mandatory dashboard update will download and install.
• The system will reboot and show the 360 logo.
• You’ll get “System Error E71″.
When you get this error the 360 is dead and cannot be revived anymore: you will need to take it back to your store for replacement or contact Xbox Customer Support.
Numerous similar complaints have already begun cropping up on forums across the Internet.
SPOnG put a call into Microsoft in the UK earlier this morning for clarification on the matter, plus for information on what gamers were to do should they experience these alarming problems.
Having a 360 that does little more than act as a doorstop or, for the culinary-minded, a nice kitchen chopping board/talking point, would certainly anger SPOnG.
We’ll bring you Microsoft’s account of the problem and what it is doing to resolve it as soon as possible.
In the meantime, if anybody out there has experienced problems with the new dashboard update – fatal or otherwise – please let us know in the forums.
I think there is a fix due, not sure. Best, er, watch out if you're part of the 360 crowd, though.
-
Title = Xbox260 <---- :wtf:
-
I have a better idea. Don't buy the 360. Either upgrade your current PC or save up some more money and buy a decent gaming PC.
-
Title = Xbox260 <---- :wtf:
no need for the wtf my good man, it was a typo.
-
Funny how everyone I know didn't have this problem. Including myself.
-
I have a better idea. Don't buy the 360. Either upgrade your current PC or save up some more money and buy a decent gaming PC.
...and that will help you play games made for the 360, how?
This seems like one of those problems that could either be a huge issue or just something a few unlucky bastards get stuck with. Either way, whenever I do wind up getting a next-gen system, I'm almost happy that I most likely won't have it networked. The Internet causes enough problems on a computer without having to worry about it on consoles. :p
-
Funny how everyone I know didn't have this problem. Including myself.
Well, it's probably pretty rare; but surely it's worth noting, AFAIK it's scarcely hard to hold off a couple of weeks for a tweaky-fix rather than risking knackering the console.
-
Well I've got to say I'm impressed with MS. First they managed to figure out a way to get a virus into a JPG and now they've figured out how to kill a console remotely (i.e without needing to be in the same room and hitting it).
Be warned geeks. The days when you could tell your technophobe friends that something bad was impossible are coming to an end :p
-
It seems to be very rare, and rumour has it affects modded consoles, and ones that were about to fail anyway (the ones with flaky power supplies or flaky gfx "cards").
The vast majority of people had no issues. Far fewer people were affected than say, the original 360 owners with gen 1 consoles with the initial hardware problems, which were, actually, not all that widespread to begin with (many more first rev consoles worked than not), and virtually non-existent in the second run consoles.
This is another"OMG, M$ SCREWED ME!!!111"
OS and Firmware updates occasionally kill systems. Happens on PC's, Mac's, routers, switches and even *Nix machines.
MS support has been excellent for people who HAVE had system issues, usually replacing them at no cost, in well under the 2-4 weeks they quote on the phone.
-
I know but bear in mind that most people who own an Xbox360 aren't exactly aware of how easily a firmware update can kill a system.
Not to mention that its pretty easy to get suspicious about an update that appears to hit modded consoles more often even if they would logically be the ones expected to fail.
-
My brother's 360 is actually broken, although with a different problem (the red circle thing). I think he sent it in for a replacement.
-
FYI, the 3 red lights of death aren't necessarily the end to your console...
Wasnt sure if this was listed anywhere...got it from AVS forums. Posted by CMR
Over on another forum they listed how to decipher what your Xbox360 is trying to tell you when you get the three rings of light. There is a code that will flash if you hold down the "Synch" button (White button near the memory slot) and press the DVD Eject button. You will notice the quadrant of lights illuminate and each time you press the eject button you will get a different code.
It breaks down to this:
All four lights illuminate = 0
One Light = 1
Two Lights = 2
Three Lights = 3
Example:
Turn on your "dead" xbox. Wait for the 3 red lights. Once you get them hold the "Synch" button and the eject button down simultaniously. All four lights flash. (0) Press the eject button again and only one light (1) press again and all four light up (0) press again and two lights (2). Error code is 0102. compare this code to the table below to find out what is wrong with your X360. Is it overheating? Power Cord? Hardware?
The Code I got is 0102 which means the computer does not know the problem as it is not hardware or heating or anything like that. Could be dust, loose solder or static! I use a can of compressed air and my X360 IS BACK!!!!!! I do not know for how long but I played last night for several hours and had not one Hiccup. This after a whole week of the dreaded RINGS OF DEATH!!
Here is the list ( Thank You to KILLTACULAR for posting this!!)
0001 power supply problem
0002 power supply problem
0003 (not yet known)
...
0010 over heating
0011 over heating
0012 over heating
0013 over heating
...
0020 (Not yet known, possibly overheating)
0021 (not yet known)
0022 GPU Error / GPU Overheating
...
0101 (not yet known)
0102 unknown error - literally means the console does not know what is wrong. Possibly a short or cold solder joint somewhere (2 reports of people repairing this, one was removing moisture build up inside the console, the other used a hot-air rework to reflow the BGA Ram chips)
...
0110 Memory Error / Memory Overheating
...
1003 Hard Drive Error... It could be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it
...
1010 Hard Drive Error, Can be caused buy a currupt or missing Eprom.
...
1013 (not yet known)
...
1020 (not yet known)
...
1022 AV cable error... There is a problem with the AV cable, try using a different AV cable. (could also be a problem with the encoder chip)
...
1030 (not yet known)
Here are some other codes they posted!!
=============================
Sections 1, 2, 3, and 4 are flashing red
- The AV cable cannot be detected
THINGS TO TRY
Make sure that the AV cable is correctly connected to the Xbox 360 console.
Disconnect the AV cable from the Xbox 360 console, and then reconnect the AV cable to the Xbox 360 console.
If the four flashing red lights continue to flash, try wiping the metal area of the AV pack with a dry cloth. The metal area is the end that plugs into the console. Wipe the metal area thoroughly, and then try the AV Pack again.
If the AV cable is correctly connected but the four red lights are still flashing, substitute a different AV cable if you have one available.
=============================
Sections 1, 3, and 4 are flashing red
- General Hardware Failure
Check the secondary Error Code per the instructions in the section below
THINGS TO TRY
Try restarting the console.
If restarting the console does not resolve the behavior, follow these steps:
Turn the console off.
Unplug all the power and AV cables from the console.
Unplug the power cord from the wall socket.
Firmly reconnect all the cables.
Turn on the console.
If these steps do not resolve the behavior, turn the console off, remove the hard drive, and then turn on the console. If the 3x Red LED error light is no longer displayed, turn the console off, re-attach the hard drive, and then turn on the console.
Also examine the lights on the power supply. When you turn on the console, the power supply light should illuminate green even if the three lights on the RoL flash red.
=============================
Sections 1, and 3 are flashing red
- Overheating
THINGS TO TRY
Let the Xbox 360 console cool.
Note You may have to wait several hours for the console to cool enough. Do not turn on the console when the console is hot.
Verify that the console has sufficient ventilation and that the fan is operating. For more information about ventilation, see the "More Information" section.
PREVENTION SUGGESTIONS
To try to prevent this problem, use the following precautions:
Do not block any ventilation openings on the Xbox 360 console.
Do not put the Xbox 360 console on a bed, on a sofa, or on any other soft surface that may block ventilation openings.
Do not put the Xbox 360 console in a confined space, such as a bookcase, a rack, or a stereo cabinet, unless the space is well-ventilated.
Do not put the Xbox 360 console near any heat source, such as a radiator, a heat register, a stove, or an amplifier.
DO NOT EVER PUT YOUR CONSOLE IN THE FREEZER OR OUT IN COLD WEATHER
Some people think that doing this might help "fix" an overheating console, in fact doing so could cause even bigger problems. Electronic devices like your console are made to function at and around room temperature, extreme cold temperatures can often cause just as many problems as extreme warm temperatures (such as overheating). Also if the console is located in a dramatically cold area while running, the difference in temperature between the hot console and cold air can create condensation which in turn will short out your console making the situation far worse. Condensation will happen more quickly if your console is overheating due to the greater difference in temperature. In short... DON'T DO IT.
=============================
Section 4 is flashing red
- Hardware Failure
The Specific Type of hardware failure can be determined by the error code displayed on the screen.
If the screen is blank or you would like additional information follow the instructions for determining the secondary error code in the section below
E64: (not yet known)
E65: DVD Drive Error.... DVD Timeout, Wrong firmware, dvd is without f/w chip, etc.
E67: Hard Drive Error... It could be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it
E68: Hard Drive Error... It could be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it, This can also be caused by a Hard Drive Eprom Error.
E69: Hard Drive Error... It could be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it
E71: (not yet known)
E73: (not yet known)
E74: AV cable error... There is a problem with the AV cable, try using a different AV cable. (could also be a problem with the encoder chip)
E76: (not yet known)
E79: Hard Drive Error... It could be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it"
So far mine has been problem free apart from the RSV demo freezing when I do something insane like telling my team to breach and clear while throwing a grenade into a room full of physics bound objects. That caused a lockup, but that's the software fault and the nature of old build demos.
-
Oh, and streaming HD vids over my network efin rawks.
So I <3 this update.
-
Oh, and streaming HD vids over my network efin rawks.
So I <3 this update.
Unless you want to watch 1080p on a Sony TV, apparently :)
-
**** Sony.
And I say this in no way as a defense for DB's whoring.
Having to choose between MS and Sony, it's MS for me. Ive not had any problems (legitimate) from Microsoft, and their products work relatively well for me.
Everything sony has died on me.
-
Oh, and streaming HD vids over my network efin rawks.
So I <3 this update.
That has to do with the VGA and what hz the Sony TV is expecting rather than what it is recieving. Something I'm sure will be fixed quickly.
Unless you want to watch 1080p on a Sony TV, apparently :)
-
Well, I don't honestly expect it'd be a deliberate mistake done out of spite..........
MS probably just don't have any Sony TVs in their testing offices. Shame for those affected peeps, really, my brother has a Bravia and it's pretty astonishing. For a TV.
AFAIK it's due for a hotfix soon anyways, isn't it? Ach well, the bonkers world of modern consoles.
-
Ive not had any problems (legitimate) from Microsoft, and their products work relatively well for me.
Install Windows ME and try to tell me that again with a straight face next week. :p
-
That, and try the RC build of Vista. Even if you're an administrator, windows wants to "confirm your actions" anytime you try to change something systemwide. Extremely annoying and problematic. This update to XP feels exactly like what they did after Windows 95. 98 felt more like a huge system update rather than a different OS. Sure, code-level there's a lot that's different, but there wasn't that much of a difference between the two OS's. Same with Vista and XP, because it's pretty much the same thing to the user, just a lot of pretty bells and whistles. Sure, there's the whole new way it handles booting and such, and Voice Command is much better.. but there's just not that much difference between XP and Vista IMO, right now.
If that's what I have to look forward to, I'm staying away from the console + future updates. No thanks, but I'd rather take my chances with something else.
-
mine works fine.
-
For now :D.
-
Erk (http://www.reghardware.co.uk/2006/11/09/xbox_update_blunder/)
Microsoft's Autumn Xbox 360 update is causing consoles to freeze at random intervals during play.
The snafu aparently affects all games. The update was bugled on the Xbox community site as "another 85 reasons why 360 rocks".
Microsoft sent us this statement:
We’re aware that a very small number of Xbox 360 customers have been experiencing some issues with their console after the Autumn Update has been applied. We’re working with each customer individually to resolve any problems. Any Xbox 360 customers who have any issues with their console should contact the customer service team on 0870 60 10 100.
So far Redmond's idea "working with each customer individually" has mostly been to demand $139 to pick up the console and have it repaired, which is odd considering Microsoft told The Register the problem is caused by its update.
More details from other gamers here in the official Xbox site forum. One user says he was told by Xbox tech support that part of the update was intended to freeze 360s with mod chips.
-
Isn't that just a reiteration of everything everyone has already said?
For it killing machines, there sure are thousands of people playing PSU... And Test Drive... And Ghost Recon...
And a few people seem to have survived long enough to show up on my friends list playing GoW...
I still call bull****. But I realize that anti-Microsoft sentiment is a fun game in and of itself, so it won't do any good.
-
Isn't that just a reiteration of everything everyone has already said?
For it killing machines, there sure are thousands of people playing PSU... And Test Drive... And Ghost Recon...
And a few people seem to have survived long enough to show up on my friends list playing GoW...
I still call bull****. But I realize that anti-Microsoft sentiment is a fun game in and of itself, so it won't do any good.
It's probably a 1, 2% or somesuch error (the machine killing error was reportedly ~1%), so I'm not surprised. I mean, if it was a common error, they'd kind of notice it testing the update, wouldn't they? I'd say it's inevitably you get machine ****ing-up updates with a patching system; just like for windows itself.
My understanding is that the quoted text refers to a different error, what with it actually describing a different error.
Surely it's rather ****ish to demand a repair fee for fixing something that you broke, though? Ableit if I wanted to really slag off MS, I'd focus on Aaron Greenberg justifying not bringing out a new large capacity HD because they can just buy more 20GB ones (http://www.eurogamer.net/article.php?article_id=69757).
-
Depends. I know a small number of folks who have returned their Xbox's after they have red-ringed. My box red-ringed after imoved back into the hosue after the accident, MS replaced it for free, I didn't even pay for shipping.
None of the others were charged for replacements. What they MIGHT do, is put a hold on a CC, if they find out say, that you actually hit it with a hammer or dropped it in the pool, and they figure that out when the get the RMA. That's a common hardware RMA tactic, Dell does it, Sun does it, HP does it. If everything is "kosher" then they don;t actually process the charge. MS didn't do that to me when I sent my box in, but that doesn't mean they won't or don;t do it in some circumstances.
I'd dig a little deeper into who was charged, it certianly isn't commonplace.
Slag MS for alot of things, sure, but this one is a lot of hooey and rooted in pure anti-MS sentiment for the sake of anti-MS sentiment. And thats crap. Re-posting is just contributing to a bull**** rumour as far as I can tell, and that doesn't help anyone.
-
Depends. I know a small number of folks who have returned their Xbox's after they have red-ringed. My box red-ringed after imoved back into the hosue after the accident, MS replaced it for free, I didn't even pay for shipping.
None of the others were charged for replacements. What they MIGHT do, is put a hold on a CC, if they find out say, that you actually hit it with a hammer or dropped it in the pool, and they figure that out when the get the RMA. That's a common hardware RMA tactic, Dell does it, Sun does it, HP does it. If everything is "kosher" then they don;t actually process the charge. MS didn't do that to me when I sent my box in, but that doesn't mean they won't or don;t do it in some circumstances.
I'd dig a little deeper into who was charged, it certianly isn't commonplace.
Slag MS for alot of things, sure, but this one is a lot of hooey and rooted in pure anti-MS sentiment for the sake of anti-MS sentiment. And thats crap. Re-posting is just contributing to a bull**** rumour as far as I can tell, and that doesn't help anyone.
Nitpick; wasn't a repost. It clearly describes a different issue.
-
I read fall update and unreviveable systems.
Seems like more "Fall update kills machines" what's new or different about it? The "its a tactic versus modchips" is something that's been circultaing since the first bricked box reports started showing up. Maybe I am mis-matching what I read elsewhere with what you have posted.
Colour me confused, apologies if I am misunderstanding something. It doesn't appear to me as new information.
-
I read fall update and unreviveable systems.
Seems like more "Fall update kills machines" what's new or different about it? The "its a tactic versus modchips" is something that's been circultaing since the first bricked box reports started showing up. Maybe I am mis-matching what I read elsewhere with what you have posted.
Colour me confused, apologies if I am misunderstanding something. It doesn't appear to me as new information.
Different error symptoms