Skip to main content

Free Shipping on Domestic Orders $75+

My laptop doesn't turn on

When I tried with another adapter and plug it in, the LEDs from power and caps lock turned for 1 second on, but when I tried to power it on, it doesn't turned on

Answer this question I have this problem too

Is this a good question?

Score 0
Add a comment

1 Answer

Most Helpful Answer

SM can be found here: https://www.ifixit.com/Guide/Document/pd...

Don't spend a ton on this as these will not run W11, but it might be an easy fix. I have seen these HP laptops be difficult over low CMOS batteries corrupting the CMOS RAM does this. The solution for those is to pull the CMOS and primary battery and hold the power button for 30 seconds, then reconnect the CMOS first, then primary

IMPORTANT: SureStart machines are notorious for a longer then average delay when you clear the CMOS with a battery disconnect (on the G11/G1X series, no CMOS battery, the primary pack is the CMOS battery, G10 and older use both) but these early ProBooks lack SureStart, but MIGHT carry on the characteristic delay. If it does it on yours, it also happens a lot on the older RSA signed UEFI BIOSes. The delay is usually 3-5 minutes, but can be faster pre SureStart.

If it comes back, remove the primary battery and run with the adapter - it might be a bad battery shorting the startup and the machine is going into protection mode. 95% of the time HPs fail out by bricking the BMS or blocking it on the commercial line but a bad short will bypass that.

If those do not help (and you verified BOTH adapters with a DMM, should be ~19-19.5V off load, 18.5-19V under load - some high spec configs like i7/Ryzen 7 with a dGPU+onboard do not like weak adapters and you need to buy a new one to get them to run), it's the motherboard - buy a newer machine, like the 600 series G9 or G11, or any recent 800 series (G9, 10, 11 and G1X). If it comes up with a different code, run that by us and we can see but if the 1 blink and shutdown continues the board has a problem.

Now if you want to try one last thing, remove BOTH RAM sticks and watch for a RAM code (3 caps lock blinks and an audible tone of 1, 2). If the code changes, the RAM is bad. If not, put the RAM back in and do the same for the SATA drive - a bad drive will POST error it with a "no drive detected" error when it is removed if a bad drive is hanging it up.

Was this answer helpful?

Score 1
Add a comment

Add your answer

Danutz_6 Vericu_11 will be eternally grateful.
View Statistics:

Past 24 Hours: 1

Past 7 Days: 56

Past 30 Days: 56

All Time: 56