The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    W510 - Hardware fault - Speakers shorting out

    Discussion in 'Lenovo' started by Goodfellaslxa, Mar 17, 2010.

  1. Goodfellaslxa

    Goodfellaslxa Notebook Enthusiast

    Reputations:
    31
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    5
    After about 1 week of use, my new W510, 820, multitouch, is suffering from significant hardware problems.


    First it began locking up. Then crashing.

    It was sitting in a docking station, with the screen closed, with good ventilation and in a cold room. My W500 practically lived in the same spot.

    Last night I was watching a DVD, and it was working fine. The movie began stuttering. I restarted. The system locked up during boot. I reset, got into windows, and then had a hard-lock. Gave up and went to bed.

    This morning, every time a sound starts to play, the left speaker makes a loud popping sound (akin to some kind of short) and then all sound stops. I can listen to the first 3 seconds of an .mp3, during which there is repeated popping, and then all sound stops.

    It also makes a popping sound when I push the power button. I even reset the BIOS to factory defaults, and reloaded the system from the factory recovery CDs.

    I did not change anything between when the system worked fine and when this problem started.

    I am calling tech support later, but as there hasn't been a response from Lenovo regarding this apparent widespread problem, I am hoping to just return my new W510 and stick with my W500 until it seems that Lenovo has addressed this problem.

    For $2.5k, I expected a bit more in-house testing. Far too many users are reporting this issue for this to have been some kind of isolated issue.

    Not sure if it is due to improper wiring, faulty chips, always-on charging USB, but it is far too big an issue.
    ..