Service tag · 19 matching pages
Respond to a Windows stop-code crash by preserving the stop information, noting what the computer was doing, checking whether the crash repeats, reviewing recent changes, and protecting data before aggressive repair.
Diagnose unexpected computer restarts by separating Windows-directed reboots from hidden crashes, overheating, unstable power, memory problems, drivers, and other hardware faults.
Diagnose recurring low-memory warnings and heavy paging by checking installed RAM, process-level memory use, browser and application load, committed memory, and whether one program is growing abnormally.
Diagnose a computer that abruptly loses power during use by checking whether the event is thermal, battery-related, charger-related, external-power-related, or another hardware protection problem.
Diagnose performance that falls as a computer heats up by correlating temperature, clock or performance behavior, workload, airflow, fan operation, and recovery after cooling instead of assuming every warm computer is throttling.
Diagnose multitasking slowdown by reproducing the customer's normal workload and watching CPU, memory, paging, disk activity, background processes, and heat at the moment performance falls.
Diagnose a missing internal or external drive by finding the layer where it disappears: File Explorer, Disk Management, firmware, connection, enclosure, power, filesystem, or the storage hardware itself.
Diagnose a computer that reaches a manufacturer logo, Windows spinner, or other visible startup screen but never reaches normal login by identifying the exact stage before using recovery tools.
Diagnose a computer that was working acceptably and then became noticeably slow by checking what changed, current resource use, storage, updates, heat, and hardware warning signs before buying upgrades.
Diagnose a computer that has power but no usable image by separating monitor, cable, input, laptop-display, graphics, boot, memory, and deeper hardware causes before assuming the motherboard or screen is dead.
Diagnose a computer with no meaningful startup response by proving the external power source, cable or charger, connector condition, and documented power-reset options before moving to internal hardware diagnosis.
Decide whether to keep troubleshooting or stop by asking whether the next step risks important data, electrical or battery safety, account security, firmware recovery, or turning a small fault into a harder repair.
Confirm or rule out computer overheating by combining temperature readings with workload, fan behavior, throttling, instability, shutdown patterns, and airflow checks rather than relying on one universal temperature cutoff.
Separate a bad laptop battery from a failing, damaged, underpowered, or incompatible charger by comparing battery-health evidence, charger recognition, power behavior, and known-good exact-compatible substitutions.
Diagnose a laptop fan that runs most or all of the time by checking current workload, heat, airflow, charging or performance modes, dust, and fan condition before assuming the fan itself is defective.
Diagnose repeated application crashes by determining whether one program, one file or action, or many unrelated applications are failing, then checking compatibility, updates, settings, storage, RAM, heat, and broader system stability.
Diagnose intermittent computer freezes by first determining what actually stops responding, when the freeze happens, and whether heat, memory, storage, drivers, software, or hardware instability is involved.
Diagnose a concrete problem that began after Windows Update by first defining what actually broke, then checking update timing, drivers, recovery options, rollback availability, and data protection.
Diagnose a Windows update that repeatedly fails by identifying the exact update and error, then checking free space, connectivity, restart state, servicing integrity, drivers, and compatibility before using repair or reinstall options.