slowmo said:
theprof00 said:
slowmo said:
theprof00 said: I just think it's funny that I try to look at the bright side by mentioning that they may go through the coding line by line and people jump all over me. You don't know either. YLOD could be caused by several processors going idle, leaving one processor to handle everything. You have no idea, yet you are comfortable enough to insult someone else.
Seriously guys, chill out. For all we know, YLOD could be caused by a line of code simply saying "F" and the cell being confused by it. If a simple date problem can cause all this, maybe a programmer typed "teh cell" instead of "the cell" and it makes 'teh cell' go into overdrive lol. |
No, I do know what the YLOD is because we fix them all night long at work but I don't see the value in educating someone determind to be ignorant. I suggest you watch the Watchdog program regarding the PS3, its rather basic in its explanation but will give you some idea of how wrong you are.
|
... wow why don't you work for Sony? You know the exact cause for YLOD, maybe you shoudl be on their repair team because YLOD refurbs tend to be recitivists, didn't you know? If they had your information they could put an end to it once and for all!
On a serious note, I'm aware that you probably know what the "direct cause" is. Which I don't. Maybe it's a joint that broke due to excessive heat or something. But you don't know what the indirect cause is. Nobody does. Why does the heat build up in some cases and not in others. Why is it that a team put the release ps3 in a sealed van of 100+ degrees for 24 hours and nothing happened?
|
I will if you like write a basic explanation which covers both the 360 and PS3 for why it ocurs and why some models are affected and others aren't. Ever heard of manufacturing tolerances? I work in a repair centre that fixes all consoles so I see the worst of all of them, including handhelds.
|
Yes I have, and am already writing under the assumption of that and other posibilities. The difference, though, is that I'm keeping an open mind about the causes. There is a reason the saying "You never know" exists. Look, I'm not trying to make a serious point about anything. I'm not saying anything with a definitive intent. I simply made an observation that this problem was a pretty stupid one. Really? An error in the calendar system? Even the millennium got through Y2K with no problems. If this is an issue, maybe YLOD is a tiny problem that someone simply glossed over too. *sigh*