The 10% may well be. In most other markets a high failure rate would mean consumers wouldn't buy the product, and would tell their friends not to buy the product. Why does the opposite happen in games consoles?
Yer how exactly do/did they test the falcon 360's to get that 10% figure?
Hell, how did they get the 30% figure???
Maybe all of the units still haven't reached critical mass
Hi everyone. I understand the questions you all have. I hope you understand that it's a bit overwhelming to try and answer everything in real time. After tonight, I'm going to ask Jake (or Jacob?) to field your questions and funnel them to me for answers. Then we can do that in an organized way. But for now, I'm going to try and answer some that I thought were most important.
First, why the secrecy?
MS knows who I am. That's why I'm not concerned about self identifying to them in these postings with details only they would know, as some here have pointed out. The people who founded Xbox hw number 10. 1 left to go be the VP of manufacturing at Qualcomm, 1 left to go be the GM of engineering at Zune, 1 left after only 2 months in ‘99 due to conflicts with toddhol. He works on Surface now. The rest still work on Xbox. I am the only one who left the company entirely.
I am not concerned about MS knowing who I am. They are worried about me revealing their problems. Not the other way around. Plus, I have contacted every single attorney who has filed a lawsuit against MS and offered to help. Some have accepted, and that work is in progress. We'll talk about that in another post. It's very interesting, I just don't want a bunch of fan boys trying to hack my home PC (that I use for work). Harass my kids, call my house, etc.
Second, why now?
Well, it's not just now. I've been reaching out since before the product went into manufacturing. I left before launch. But many employees continued to contact me about the problems with the product and its launch. I did my best to help them figure out how to mitigate the problems caused my bad management decisions, and test the boxes right. Sometimes my ideas worked, sometimes they didn't. I then started to contact reporters. Sometimes it went no where. Sometimes, it resulted in a spectacular thing, like the ambush interview with toddhol just before MS admitted guilt. But still, it happened too slowly for me. That's one reason I'm doing this now.
When those articles were posted last July, I chimed in as a commentator. That's when Jake invited me for an interview. But I didn't see it then. It was only recently when I goog'ed "xboxfounder" on a whim that I found that old invite. So I contacted him to see if he was still interested. I sent him a current resume from my current work email account, and he believed me. If you guys don't, then tell me what you need to see as proof. And I will provide that.
Last: My motivation.
I have always been in a position to stand up for the customer. MS stopped me from doing that. They need to pay the price now. If you guys won't get together and make that happen, you have no hope for the future with them. It's not my fight, but I am here fighting. You decide what you want to do. And then do it!
When a product is having critical failures at an astonishing rate yet users are still buying, re-buying and using it....
Well pardon my choice of words. But I would be "unhappy" and stop using the product. Alot of people seem "happy" and continue to use the product.
People buy game consoles for the games, not perceived reliability.
I mean.... besides the fact that the gaming media has been grilling Sony over and over again about most every minor descision while more or less ignoring the RRoD problem.....
What would be the rate of failure that would be acceptable? Is it subjective? 'Cause by the looks of it, if it's not a time bomb waitting to explode and take you and a city block with it, it's easy to say that 80% is just fine. As long as you don't have to pay for anything...
The fact that a faulty machine manages to sell well is strange to some of us though. Especially when the initial warranty used to be 3 months and most of the media aknowledged the problem only when MS did. (And to clarify, I'm not talking about a conspiracy either).
But it's easy to see that MS did everything they could to convince everyone that there was no problem whatsoever until they couldn't hide it anymore.
What would be the rate of failure that would be acceptable? Is it subjective? 'Cause by the looks of it, if it's not a time bomb waitting to explode and take you and a city block with it, it's easy to say that 80% is just fine. As long as you don't have to pay for anything...
What would be the rate of failure that would be acceptable? Is it subjective? 'Cause by the looks of it, if it's not a time bomb waitting to explode and take you and a city block with it, it's easy to say that 80% is just fine. As long as you don't have to pay for anything...
while the customer is trapped by the investment in software/games and his uwillingness to admit he was conned into buying a lemon.
Bunnie said:A while back I posted that I was looking for an RROD Xbox360; I actually sent it off to MEFAS to get digested for solder joint inspection on the GPU through a process called "dye and pry". In this process, the motherboard is flooded with red ink, and then the GPU is mechanically pried off the board. The red ink flows into any of the tiny cracks in the solder balls, and at least in theory, when you pry the GPU off the cracked regions will shear first so you will be left with visible red spots at the points of failure.
left: Below is what a normal ball looks like after the test
right: One of several balls on the GPU that exhibited signs of partial failure
I was a bit puzzled by these results because you didn't see any "catastrophic" failure -- pools of red ink over a connection interface -- just partial cracking. Partial cracking isn't terribly uncommon, and many products work quite well despite such artifacts. However, after reading the [SeattlePI RRoD] article, if Microsoft shorted safety margins around many of the design parameters to get the product out on time, it makes sense that the summation of many partial failures could lead to a total system failure -- failures that have symptoms that vaguely cluster together but are difficult to point to any single root cause. Heisenbugs. Yuck.