HP Pavillion dv6 laptop - 15 beeps on startup and a black screen?

Question

Usual story - girlfriend's step-brother's laptop is broken. I don't know a huge amount about what occurred before it broke, but I do know the following:

• When you try to turn the laptop on, it beeps 15 times exactly.
• The screen remains black.
• The LED on the Caps Lock key flashes continuously.
• If left on, the laptop never boots - as far as I can see.
• If left on, on a stable surface with decent ventilation for a relatively short period of time, the laptop (below keyboard, but not where the RAM/HDD are) gets very hot.

I've tried doing what most websites appear to recommend for similar problems, which is to disconnect AC and battery then hold the power button down for a minute before reconnecting the AC and trying to turn the laptop on - no difference.

I've also tried re-seating the RAM, to no avail.

Solution 1

I have encountered the same problem with a Compaq Presario CQ56. 15 beeps, 'CAPS LOCK' light flash, and blank screen.

Problem: Improperly seated keyboard cable, keyboard cable or keyboard is broken.

Solution: Make sure you tuck the cable deep into the slot for good contact. If this doesn't work, get a new keyboard.

Hope this helps.

Solution 2

That beep code means CMOS RAM checksum error. But like Dave M stated that does not match HP's beep codes. I would recommend removing the battery and power from the laptop. Then hold the power button for 15 seconds. Then reconnect the battery and power to the laptop and power it on. It the computer does the boot at this point then you will need to contact HP support. You can also use the following page to referance the flashing lights and beep codes - http://h10025.www1.hp.com/ewfrf/wc/document?docname=bph07107&lc=en&cc=de&dlc=en&product=5116406

Comments

[Daniel Andersson]

How old is it? Any warranty still valid? I suspect a failed CPU fan, but don't open the case if there is any warranty left.

[fixer1234]

@dunc: This is a 3 year old post, so I assume you solved the problem or it was overtaken by events. Can you update the post with what it turned out to be or how you resolved it (maybe post a short answer)? Your question has gotten almost 5,500 views, so anything you can add could be useful to a lot of people.

[turbonerd]

Hi Jeff, as per my post, I've tried this method but it appeared to make no difference.

[bertieb]

Can you describe how you reseated the RAM? it may not be obvious to someone else. Cheers!