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.

    HP DV7-4060us Blinking capslock? It's not Processor failure. Solution.

    Discussion in 'HP' started by billa48, Jun 7, 2013.

  1. billa48

    billa48 Notebook Enthusiast

    Reputations:
    17
    Messages:
    32
    Likes Received:
    0
    Trophy Points:
    15
    Now then. I picked up a DV7-4060us with the triple core AMD Phenom processor the other day for 20 bux without a hard drive or ram. Owner stated, doesnt work, had taken it to a computer shop, they said its the motherbaord. Okay.

    So I take it home, try usb bios reflash, no go. Capslock light blinks, no other lights, sounds, nothing.

    Ok. So I open it, get my harborfreight heating gun and heat up both the video chips. The AMD one and the ATi one. As shown in picture below.

    dv7.JPG

    As soon as I put it all together and plug it in, it starts working and has been, constantly since two weeks ago. This laptop has not been turned off, standby nothing. Works perfectly. Sound, video, HDMI port all alive. Still switches video cards when you unplug the power adapter.

    Hope this helps.

    Also, this same solution worked for a Compaq Presario CQ60. That laptop didnt pickup the bios reflash either no matter what I tried. Turned on immediately after heating the video chip.
     
  2. acadiel

    acadiel Notebook Enthusiast

    Reputations:
    0
    Messages:
    18
    Likes Received:
    1
    Trophy Points:
    6
    I had a similar model, which I sent off to have the same thing done... Lasted about six months, unfortunately, and the video chip is back to its antics again.

    Does anyone know the date range where HP was having this issue on consumer model systems, so I can avoid used ones with the issue? :)


    Sent from my iPad using Tapatalk HD