Tag Archives: repair

It’s official: something went severely wrong with the Sylvania G netbook I bought in October.  The keyboard AND POWER BUTTON will completely “lock up” at random and QUICKLY, yet the computer itself still runs in the background, and the hard drive developed a couple of bad sectors (which I remedied by doing a zero fill–more on that in another post).  It’s fairly unusable now, and it’s still within the warranty period, so I called up Sylvania’s support number for help.  The company that actually makes these netbooks is called Digital Gadgets, and it is them who I have dealt with.  So, how did it go?

I haven’t been this happy about a customer service experience EVER.

I explained to the tech that I bought the netbook in October 2008, that I run a computer service shop, and detailed heavily what was wrong and the evidence that I had gathered to make my judgment call that the netbook was screwed up.  Apparently the ink used for the serial number sticker is poor, because it had smudged off to the point that it was unreadable, which I made very clear early on in the call.  This is about where you would expect me to spew off about the run-around I was given and the stupid hoops I had to jump through to prove to the person that it was indeed screwed up, because 99.9% of service and support agents have almost no authority to help customers and are usually in the business of preventing warranty returns at any cost.

But that didn’t happen, not even a tiny little bit.  No run-around?  Surely I jest, right?  WRONG!

The tech support agent, named William Lee, promptly started the process of generating an RMA and took my shipping address to send a totally free return shipping box to.  About eight hours later (and after business hours, no less) I had an RMA number in my email inbox, with instructions on what to do when the box arrived.  As of this writing, the box hasn’t yet appeared, but that’s because I only called them a couple of days ago.

It is astonishingly refreshing to be able to deal with someone like William.  He did everything exactly right, without a single flaw in his procedure.  He LISTENED TO THE CUSTOMER’S PROBLEM, taking the time to ensure he understood exactly what was going on from my perspective.  He also BELIEVED THE CUSTOMER’S STORY AND EXHIBITED BELIEF IN THE CUSTOMER’S GOOD FAITH, which is the exact opposite of what most suppot agents do: showing a lack of faith and general distrust of the customer right off the bat.  Because he LISTENED and BELIEVED, this brought about the UNDERSTANDING  that there was a clear issue covered under the warranty which needed to be resolved quickly as possible.  Within a reasonable time frame, he PROVIDED A SPEEDY RESOLUTION TO THE CUSTOMER’S PROBLEM.

Let me explain exactly why I am writing in this fashion.  William’s example should be followed by all companies, and sadly it is almost nonexistent in the corporate customer service landscape of today.  The benefits to the customer (in this case, myself) are fairly obvious: the problem was resolved quickly and the customer’s precious time was not wasted to achieve that resolution.  But what about the benefits of William’s actions to the BUSINESS?

  1. William spent as little time as possible chatting it up on the telephone.  This left William free to service other customers, reducing overall load on the customer service department at Digital Gadgets.  It also made William a much more valuable asset to the company, because William is able to service more customers than an agent who is given no authority and is required by the company to simply  toss customers through hoops.
  2. On the flip side, William did not abbreviate our conversation.  He spent the time required to understand my situation, but did not ask me to perform senseless exercises when it was quite clear that the problem was hardware-related and not fixable over the phone.
  3. I was heard but not patronized, AND a SIMPLE solution was presented QUICKLY.  This greatly increases my faith in Digital Gadgets as one of their customers, increasing the chances that I will purchase from them in the future AND RECOMMEND THEIR PRODUCTS TO OTHERS  AS WELL.  Over time and across many customers who are similarly situated, this leads to MORE SALES, which can quickly and easily exceed the cost of a warranty repair on my one individual netbook.

William is doing it right.  Other businesses could take a few lessons from how he handled my situation.  I can’t wait to get my fixed toy back in good working order, and I’m very happy to have bought a computer from a company that treats me like a customer should be treated.

Remember our post about receiving a STOP 0×0000007E error after moving to an AMD processor from an Intel one?  It turns out that the plot has thickened a bit more, and Windows XP SP3 can sometimes cause the same problem–and do so for the exact same reason: intelppm.sys!  We’ve also figured out new ways to fix the problem that are easier than in our original post, which we’ll divulge now.

Boot from your Windows XP CD and hit “R” at the “Welcome to Setup” screen to reach a recovery console, then log into the Windows installation in question, as in the instructions from the previous article.  The next step, once you get to a command prompt (i.e. “C:\WINDOWS>”) is far more simple, elegant, and easily understood!  Type this command, without quotes:

“disable intelppm”

Type “exit” after that and it’s all done and over with.  Sometimes us techies get so used to doing things the hard way that we forget the simpler solutions.  If you’re prepping a system for a change away from an Intel processor platform and want to avoid this problem, go to Start > Run… and type in the following command to pre-emptively disable intelppm.sys from loading:

“sc config intelppm start=disabled”

Sometimes the STOP error is accompanied by the text SYSTEM_THREAD_EXCEPTION_NOT_HANDLED as well, though I’ve never personally seen that, it’s technically what that STOP number means.  In general, it’s a waste of time to screw around with Microsoft’s update that handles the problem, because intelppm.sys shouldn’t be there at all anyway for AMD platforms; it’s the Intel CPU microcode update driver that sends new downloadable microcode into the processor, usually to fix errata (bugs) or to improve performance, and it is only logical that Intel’s microcode update software would make an AMD processor freak out and throw a wacky exception.  The problem is that apparently Intel’s driver doesn’t check to ensure that the CPU in use is actually an Intel chip, which is either bad programming at Intel or intentionally done to make it look like AMD makes really glitchy chips.  Either way, Intel is wholly to blame for the issue and could have avoided the problem with a very simple check that would have taken all of 30 minutes to code!

Be aware that other programs frequently cause STOP 0×0000007e errors as well, primarily security software.  I’ve seen reports that ZoneAlarm getting damaged has caused this before, and the Zone Labs engine is used in some other security software we’ve come across, such as the CA Internet Security suite.  (ZoneAlarm sucks, so you shouldn’t be running it anyway.)  What I’ve written here ONLY applies to systems with a non-Intel processor trying to execute a driver that is hostile towards non-Intel CPUs.