Start with a clean baseline
Test each user-facing subsystem independently—display, keyboard/pointer, camera, microphones, speakers, connectivity and battery-visible state—before running invasive OS repair or replacing the main device.
Live evidence
Relevant checks
First sequence
Do the high-signal checks before risky changes
- 1
Confirm exact laptop model power requirement
- 2
Check connector/cable and outlet
- 3
Compare a known-good manufacturer-approved adapter where possible
Decision points
What the result should change
If a component works in deviceok but one app failsKeep the diagnosis at the app/permission/routing layer.
If a component fails in the browser and the os/oem testMove toward driver/firmware, cable/module or service diagnosis.
If several unrelated components fail togetherLook for a shared dock, USB bus, power, recent update or physical event.
Browser can help check
- Compare entered wattage ratings
- Calculate power from documented voltage/current
Browser cannot prove
- Read charging-controller faults
- Verify proprietary adapter identification
- Measure cable voltage drop
Repair boundary
Know when to stop browser troubleshooting
- Battery swelling, liquid exposure, burning smell or abnormal heat needs physical service—not stress testing.
- Browser battery/status APIs do not provide manufacturer battery-health metrics.
- BIOS/firmware updates should come only from the OEM and should not be interrupted.
Used-device inspection
What to verify before paying or signing off a repair
- Full-screen display/pixel inspection
- Every key, pointer/trackpad, camera, microphone and speaker
- Ports, charger, battery-health screen and sleep/wake behavior