Slashdot Mirror


Getting Gouged by Geeks

dottyslashdottydot writes "CBC Marketplace recently ran a sting operation and discovered that most home computer repair technicians failed miserably at diagnosing a simple RAM failure. Many techs tried to sell unneccessary software or upgrades. (or even a new computer!) However, the worst offender was one guy who claimed that the hard drive had failed, and that the only remedy was to pay $2,000 to have a special facility with a clean room recover the data."

6 of 581 comments (clear)

  1. Diagnosing memory failures is hard by DaleGlass · · Score: 5, Informative

    Memory affects pretty much everything, so it's hard to isolate it from everything else. Bad RAM can result in disk corruption, making it hard to determine it's the memory and not the disk that's broken.

    For example, take Nero, burn a CD, then verify it. If the RAM is bad it may well happen that a few bits you read from the CD got flipped, and now the verification fails. Obvious conclusion: The CD-R was bad. After a few of those, obvious conclusion: the drive is bad. That the computer crashes ocasionally can be attributed to spyware or viruses. A tech working for cheap isn't going to spend hours to test every possible case.

    RAM is also one of the most annoying things to try to diagnose. Disks at least have SMART, so if it got to the point where it's really broken, SMART will tell you about that quickly. And once it breaks it tends to do so very obviously. Now memory can pass tests and still be bad, and be marginal enough to work most of the time.

    I had several problems with RAM that firmly convinced me to always buy ECC.

    First one was when my Linux firewall, which ran for months without a hitch suddenly had a kernel panic. I thought it was strange, but oh well, nothing is perfect. Rebooted it, expecting that the new kernel installed weeks ago probably has a fix for that. A couple days later it crashed again. Rebooted it again making a note to investigate later. A day later it crashed yet again, but didn't boot this time due to disk corruption. Turns out the RAM was loose in the slot, and somehow stopped making proper contact. The module itself was good and passed memtest86 just fine when I set up the box.

    Second one was when I was buying a new shiny box, and started having strange crashes. This took me quite a while to diagnose, because memtest86 passed perfectly fine. Yet "memtester", an userspace tool did catch it finally, after running for 8 hours straight, and even then with about 50% accuracy. On repeated 8 hour runs sometimes it'd catch it, and sometimes not, while testing the whole memory several times during that period.

    Something like that probably won't be diagnosed correctly by tech support. Even if they do test the memory they're almost certainly not going to bother running it for a day straight, just to make really sure it's not a marginal case.

    1. Re:Diagnosing memory failures is hard by jollyreaper · · Score: 3, Informative

      Memory affects pretty much everything, so it's hard to isolate it from everything else. Bad RAM can result in disk corruption, making it hard to determine it's the memory and not the disk that's broken.

      For example, take Nero, burn a CD, then verify it. If the RAM is bad it may well happen that a few bits you read from the CD got flipped, and now the verification fails. Obvious conclusion: The CD-R was bad. After a few of those, obvious conclusion: the drive is bad. That the computer crashes ocasionally can be attributed to spyware or viruses. A tech working for cheap isn't going to spend hours to test every possible case.

      RAM is also one of the most annoying things to try to diagnose. Disks at least have SMART, so if it got to the point where it's really broken, SMART will tell you about that quickly. And once it breaks it tends to do so very obviously. Now memory can pass tests and still be bad, and be marginal enough to work most of the time.

      I had several problems with RAM that firmly convinced me to always buy ECC. Have you ever used Memtest386? At my job I've only ever encountered two or three instances of bad ram and this is the tool that's done it. Replace the ram, perfect functionality. I've had very good luck with it. For servers everyone says don't dick around, make sure you get ECC, so that seems like smart advice.
      --
      Kwisatz Haderach
      Sell the spice to CHOAM
      This Mahdi took Shaddam's Throne
  2. Re:getting gouged by whom? by cloricus · · Score: 4, Informative

    We have that in Australia. It's called 'The Chasers WAR on Everything' and you can check it out on YouTube, abc.net.au/chaser, or your favourite BT network. One of the better segments is 'What have we learnt from current affairs this week?' in which they make a mockery of Australia's nightly rubbish news shows. Have a look at it, get a group of crazies in your country to start up a similar show. If it doesn't clean up the trash on those sorts of shows at least it will let you laugh at the sorry state of affairs.

    We also have a semi-funny-semi-serious show called MediaWatch which is a 15 minute show that goes over all of the illegal, stupid, dangerous, and bad things the media did that week. You can also find copies of it at abc.net.au/mediawatch.

    --
    I ate your fish.
  3. It wasn't hard in this case by Vainglorious+Coward · · Score: 4, Informative

    You can't have seen the show - they inserted RAM that had been "blown" (I think they'd dropped a blob of solder on some crucial area) so the machine wouldn't even POST. It's not hard to diagnose why a machine won't even get to post - RAM or motherboard or CPU or an external card. (Indeed all four of those reasons were given by various different techs).

    --
    My next sig will be ready soon, but subscribers can beat the rush
  4. Re:getting gouged by whom? by mallie_mcg · · Score: 3, Informative

    Try the actual site http://abc.net.au/tv/chaser/ You can even podcast full episodes.

    --


    Do the following really mean anything? SCSA MCP CCSA CCNA
    --I'm not actually after an answer!
  5. Lies, Damn Lies and Editing Video... From Toronto by Anonymous Coward · · Score: 5, Informative
    Well I'm in the computer repair business AND in Toronto and my mom called yesterday to tell me this was on, so I tuned in, as an 'expert' as it were. Watching the show and then rewatching the first part I missed from the web, it becomes obvious that parts of the recorded sessions with their tech help were edited to make it seem over the top.

    Here's a bunch of points and the text from the show:

    The presenter says that blown ram is a "simple problem" ?? WTF ... Also the price they quote for the 512MB DDR ram at $25 really lowballing it. 512MB of DDR-184 may be $29 to $35 at the "in store" for good cheap parts in Toronto, but where any average person would shop at Staples.ca it's $79.92... And of course there is installation, and more importantly diagnosing which can be nasty, so stating $25 gives the viewer the impression that A) it's easy, and B) total cost _should_ be $25... (see end for URLs)

    They show three of the in-home techs at work, again just snippits.

    "Grade A Students": he supposedly, remember the video is heavily edited, tells them they need a new motherboard. Well with an older computer, the chances are just about even that its the ram or the motherboard. The guy may not be the best repair tech in the world, but it's not over the top to suggest that. The one fault I find with him is telling the customer to "go buy a motherboard" as there's no way an average user could do that. The show points out A) he charged $80 which seems fair for in-home visit to diagnose something, and B) reiterating it's a motherboard "don't need" thus making the diagnosis seem rediculous.

    "Nerds On Site": this is the fellow they make to look the worst, but from the few edits they do have of him, he seems to ask some good questions off the bat, "Is the hard drive making different sort of sounds?" That is the best question to ask a user since the CLICK CLICK CLICK of a bad drive most people do hear and they know "it didn't sound like that before". So this guy guesses it's the HD before he opens the case, which is actually a bad diagnosis since we can only assume the box didn't even POST with the bad ram (if it did POST with flakey RAM well it could be anything right?). Their expert tells the viewers, "you can't make any kind of diagnosis that quickly", when in fact yes you can with a bad HD or even bad ram/mb...

    "Geek Squad": So they show the guy saying "My professional advice is the motherboard. You have to have it taken in and you have to replace the motherboard", which is perfectly reasonable. On-site it's almost impossible to figure out if it's the mb or not, and if you don't carry spare ram, figuring out if its the ram is also best done in the shop. At this point the show states "Remember the problem's a broken ram part. So far we've heard it was the motherboard, the cpu, and the hard drive. All wrong." But those are their guesses and all are reasonable for being in the field guesses, so they're not wrong, save the HD guess, but that guy is not necessarily the most adept diagnostician... Continuing, "Out of 10 techs we call in, only these 3 can figure out what the problem is." So these three guys try pulling out the ram and try one at a time. Again, since it's an old system, guessing that's the the MB is not that off base, though not trying the ram is a shame but not over the top.

    Taking Advantage of "most of us"

    "we track down 3 techs who used to work for big name retailers, Rob, Macolm, and Shawn confess that taking advantage of most of us is easy"... um 'taking advantage' of most people who often don't know much more than 10 things about using the computer, when a seasoned pro may know and encounterd say 1,000 to even 10,000 things. Well how easy would be for a doctor to say to a patient, "look's like you've got a dwarf living in your belly" and that person believe them??

    On the average customer

    Presenter: "When people come in with a crashed computer, how much do they actually know about what was wrong