A laptop with a black screen and a lit power LED is usually holding residual charge in a confused embedded controller. The fix is a specific sequence of holds and waits, not another reboot attempt.
Unplug, hold the power button for **30 seconds**, release, reconnect and try again. Many models have a **pinhole reset**; both drain the embedded controller without opening the case.
A lit **LED**, a spinning fan or a charging indicator means power arrives; a completely dark machine with a cold charger brick is a supply problem.
:: observe power LED, fan, charger LED, and try an external monitor via HDMI
get-wmiobject Win32_Battery -ErrorAction SilentlyContinue | Select-Object BatteryStatus,EstimatedChargeRemainingUnplug the charger, hold the power button for thirty seconds, then reconnect and press it once. The hold drains the capacitors that keep the embedded controller in a stuck state.
:: 1. unplug the charger
:: 2. hold power for 30 seconds
:: 3. reconnect the charger, wait 10 seconds
:: 4. press power once and waitBusiness laptops often expose a reset hole or a recessed button on the bottom. A paperclip for a few seconds does the same job with the battery disconnected from the logic board.
:: typical locations: bottom cover, near the battery latch, or beside a USB port
:: hold for 5 seconds with the charger unpluggedA charger that lights up can still deliver no voltage. Check the connector, try another charger of the same rating, and read the battery state once the machine is on.
powercfg /batteryreport /output C:\Temp\battery.html
Get-CimInstance Win32_Battery | Select-Object Name,EstimatedChargeRemaining,BatteryStatus,DesignVoltageOnce it boots, the previous session is still in the log. Power and bugcheck events tell you whether this was a crash, a thermal event or a real power loss.
Get-WinEvent -FilterHashtable @{LogName='System'; Id=41,6008,1001} -MaxEvents 5 |
Select-Object TimeCreated,Id,ProviderName,@{n='M';e={($_.Message -split "`n")[0]}}Repeat offenders are firmware, a failing battery or a driver that keeps the controller busy. Update firmware from the vendor, and check sleep behaviour with the power report.
powercfg /a
powercfg /sleepstudy /output C:\Temp\sleep.html
Get-CimInstance Win32_BIOS | Select-Object SMBIOSBIOSVersion,ReleaseDateThe supply or the DC jack. Try another charger and another outlet before assuming the board is dead.
The battery is deeply discharged or has failed. Read the battery report for the design capacity against the full charge capacity.
Display or backlight, not power. Connect an external monitor and press the display toggle key combination.
Treat it as a hardware or firmware fault. Update the BIOS and chipset drivers, and check the thermal readings under load.
No. It cuts power to the embedded controller; storage and settings are untouched. Unsaved work from the frozen session is gone either way.
Only on models with an easily removable battery. Sealed laptops are reset through the hold or the pinhole.
There is nothing to undo. The machine simply starts with the controller in its default state; the only side effect is the lost unsaved work from the session that froze.
Free · no account needed · tracks your progress