Hardware Troubleshooting Workflows

The laptop at Redbrook Engineering would not turn on, and the technician, who was thorough, spent forty minutes being thorough. That meant a different charger, a battery reset, a firmware menu, a long and interesting conversation with a vendor chatbot. The engineer whose laptop it was spent the same forty minutes watching, because her drawings were on it and the drawings were due. At minute forty-one a passing colleague pushed the power cable the last quarter-inch into the brick. The cable had been sitting slightly proud since the desk move. The machine woke up, and the technician learned something about order that no manual had thought worth printing.

This series is about order. It covers the diagnostic order for a sick laptop or desktop, which is cheapest first and always has been. It covers swap, repair or retire as decision rules in hours and years rather than feelings. It covers the loaner and spares strategy, because the fastest repair is the one the user does not wait for. Then come common faults by symptom, with the first check for each. It covers working with warranty and repair vendors without losing the ticket in the post. And it covers reducing hardware tickets with standards, a refresh cycle and the honest retirement of lemons. The cable comes before the motherboard. The working machine comes before the diagnosis. Everything else is detail, and the detail is here.

Articles in This Series

• The Diagnostic Order for a Sick Laptop or Desktop
  Cheapest first: power, cable, peripheral, software, operating system, hardware; the five questions before touching anything; what changed; reproducing before replacing; and the diagnostic order card.
• Swap, Repair or Retire: The Decision Rules
  The rules in hours and age, the user's downtime as the real cost, and the warranty path. Also covers the age at which repair stops making sense, the working machine first, and the decision table.
• The Loaner and Spares Strategy for a Small Desk
  How many spares for a fleet as a worked example, imaged and ready, and the loaner log. Also covers chasing loaners back, spares as the price of fast resolution, and the spares plan.
• Common Faults by Symptom, and the First Check for Each
  Will not power on, slow, overheating, battery, screen, keyboard and ports, intermittent. Covers what each usually is, the first check, when it is really the dock, and the symptom table.
• Working With Warranty and Repair Vendors
  Logging a claim, what the vendor needs, the ticket in a waiting state, chasing, the no-fault-found return, keeping the user informed, and the vendor claim note.
• Reducing Hardware Tickets: Standards, Refresh and Lemons
  Standard models, the refresh cycle, the lemon model, handling and care education, the dock standard, and the hardware standard sheet.

Explore More Topics

This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.