HP Support Forums
Join in the conversation.
04-30-2012 10:45 AM
My dv6t froze while playing battlefield 3 and when I tried restarting, it would no longer POST (nothing on screen). When I press the power button, the caps lock LED lights up once, pauses, then lights up again before restarting. I checked the hp website at Computer Does Not Start and Emits an LED or Beep Code HP Pavilion dv5000 Notebook PC series - HP Cus... but I am a bit confused as to how many times it actually blinks since my computer doesn't really cycle through the indication multiple times. I tried hard resetting the BIOS by holding the power button for a minute with no AC power and even tried taking out the CMOS battery for about 3 hours to no avail. I have also tried reseating the RAM sticks and using one stick at a time, which didn't work either.
I recorded a video of the LED error code: Dv6t black screen - YouTube
The caps lock key lights up once 2 or 3 seconds after pressing the power button and then pauses for two seconds before lighting up again. After that the computer restarts right away. However, after the restart it does different things each time. Sometimes the light would light up and sometimes it wouldn't. By the way the computer is restarting itself whenever the touchpad light goes out and comes on again.
WIth the problem that the laptop is having, I am guessing its most likely a motherboard issue since the CPU isn't very likely to fail. But because I am 2 weeks out of warranty, I guess I don't really have any options but to fix it myself.
Anyone have any suggestions?
04-30-2012 11:42 AM
GOOD NEWS, i've seen this alot. A blink code that doesn't really match the pattern is actually a single blink code.
BAD NEWS, despite unlikelyhoood is indeed a CPU failure. I'm sorry to be the one to tell you this. it IS a CPU failure.
What you can do.
Since replacing this means replacing the systemboard (yes thats what it means). It's going to be expensive.
Are you POSITIVE your warranty is out? Some of these series have 2 year warranties instead of 1. Make sure you have the purchase date right, as thats how it goes by, purchase date. Even if HP has the wrong date you can despute it if you have the documentation. I suggest this because as I said...this repair's gonna cost you otherwise, so if it's free...try to get it free.
Otherwise you might (this is a big might) be able to find a small 3rd party mom and pop computer shop (Think "Bob's Speedy Computers") with the balls to open your case and might have a replacement processor or can install one if you can find it by itself.
Otherwise just buy a new notebook.
Probably not the best news but i've seen this before, and saw no one else hit with a reply
04-30-2012 12:03 PM
Thanks for the response.
I got this computer a bit over a year ago with a 1 year warranty but they replaced the laptop last year in May due to a constant BSOD that I was getting. However, when I checked the warranty date, it said that it had already expired.
If it is indeed a CPU problem, I wouldn't have to replace the motherboard right? I know that the motherboard can get pretty costly but if it is only a CPU problem, I'm sure the CPU can just be removed since they're not soldered onto the mainboard as far as I know.
04-30-2012 12:22 PM
I should have been more specific, it's possible to replace the CPU on a notebook however, as a repair through your warranty, this is done via systemboard replacement/repair. Now if it was replaced due to BSODs, who was it replaced by? If it was HP there's still a chance it could be covered by a new warranty, if the replacement was done before, as it often renews the warranty. Again I would call around local shops and see if someone is willing to get hands on with it and see what solutions they have that might be more cost effective.
04-30-2012 12:29 PM
The replacement was handled through HP but as far as I know, the website says that my notebook's warranty according to the serial # and product # has expired.
I might be able to remove the CPU and test it in someone else's laptop with compatible motherboard though so hopefully that'll give a better diagnosis of the problem, but I'd like to see if people here can make a better interpretation of the error code before I open another laptop.