Quote:
|
Originally Posted by Shauk
however many people stated that in the video, they heard no beep codes or whatever.
|
Which makes me think they disabled the beep codes so that they could get more skewed – and thus, more newsworthy – results.
You know what industry is more underhanded than computer techs, car mechanics, plumbers, et. all? The TV media industry.
I bet you some of those techs who answered the call were thinking (at least, on a subconsious level), "Hmm... Is this due to a bad memory stick? But there are no beep codes. So, maybe it's something else... ?" And once you get off on a wrong path, as a computer tech diagnosing a problem with a PC, it could take you a lot of time and effort before you realize it and go back, looking for the correct path.
Oh, and the way the TV reporter went on and on about "it's a simple repair, with just a $25 part!": Replacing a $2 fuse is a simple repair, with a cheap part. But if you call an electrician out to your house, he's going to charge you a great deal more than $2 to diagnose and fix the problem.
Quote:
|
Originally Posted by Martian
A blown stick of RAM is diagnostically simple. There is absolutely no excuse for misdiagnosing.
|
But was that stick of RAM completely blown? After all, there appeared to be no beep codes. I've dealt with faulty sticks of RAM that allowed you to boot all the way into Windows, and even let you launch and run applications, but then all of a sudden an application would crash with a read memory error. (And a read memory error in Windows doesn't necessarily mean you have a bad memory stick.) The only way to find the cause of this problem was to boot off a floppy or CD, to a command prompt, and then run an exhaustive memory-checking program.