If a computer is failing, it is tempting to focus on the one scary symptom (it will not boot, it is "slow", it keeps crashing). A safer approach is triage: capture the symptoms, protect the data, and write down what was already tried so the next person does not repeat it.
1. Write down the symptoms in a way a technician can use
"It is broken" is not useful. The useful version is: what changed, when it started, what error appears, and whether it is consistent.
- When did the problem start? Was anything installed or updated right before it?
- Is it constant or intermittent? Does it fail after sleep, after a reboot, or only on Wi-Fi?
- What exact error message appears? Take a photo of the error screen.
- Does the same problem happen on another user account or another device?
2. Protect the data first
Many repairs are safe, but "safe" changes when a drive is failing. If data matters, treat a backup as the first task.
What must be saved
List the business-critical folders: documents, photos, accounting data, customer files, browser passwords, email archives.
Where is it stored
Confirm whether files live locally, in OneDrive/Google Drive, on an external drive, or on a NAS.
Backup method
If the PC still boots, copy data to external storage. If it does not, avoid repeated boots and consider a recovery-first approach.
Account access
If cloud sync is involved, confirm the login email and recovery options so files can be reconnected after repair.
Backup and recovery checks before risky steps
Before reinstalling Windows, changing storage, resetting accounts, or running aggressive repair tools, confirm what can be restored. A backup is useful only if someone has checked that the important files can actually be opened from another device.
Restore test
Open a sample of important files from the backup destination. If the backup cannot be read, pause the repair path and fix that first.
Cloud sync trap
OneDrive or Google Drive may not contain everything. Check desktop folders, downloads, browser profiles, accounting exports, and app-specific data.
Encryption keys
If BitLocker is enabled, confirm recovery-key access before firmware, boot, storage, or Windows recovery changes.
Old drive handling
Keep the old drive intact until the repaired or replacement device has been tested under normal use.
3. Capture the access details (without oversharing)
A technician cannot test properly if they cannot sign in. You can still protect privacy by creating a temporary test account where appropriate.
- Confirm whether the device uses a local Windows account or a Microsoft account sign-in.
- Record whether BitLocker/FileVault is enabled and whether recovery keys exist.
- If needed, create a temporary local admin test account and remove it after the work is complete.
- Write down critical apps that require licensing or logins (accounting software, POS, VPN clients).
Official reference points for safer triage
These references are useful when the repair touches backups, encryption, Windows recovery, or repair-vs-replace decisions. They do not replace hands-on diagnosis, but they help keep the repair order conservative.
Backups
NCSC's backup guidance highlights that backups should be protected, monitored, and tested so restoration is not assumed.
BitLocker
Microsoft explains where BitLocker recovery keys may be stored and why losing the key can force a device reset.
Windows recovery
Microsoft's Startup Settings page covers recovery options such as Safe Mode when Windows will not start normally.
NZ consumer context
Consumer Protection explains repair, replacement, and refund context under the Consumer Guarantees Act. Treat it as general background, not legal advice.
4. Quick, low-risk tests that narrow the fault domain
The goal is not to "fix it yourself", it is to isolate whether this looks like storage failure, overheating, malware, software corruption, or a simple misconfiguration.
Disk space
Check free space. A nearly full drive can look like a hardware problem but behaves like a software one.
Safe Mode
If it boots, try Safe Mode. If the problem disappears, suspect startup apps, drivers, or software.
Heat and fans
Random shutdowns and throttling often come from overheating. Note whether fans are loud or vents are blocked.
Power
Swap the power supply (or charger) if possible. Unstable power can mimic disk or motherboard issues.
5. Hardware notes that matter
Repair decisions change if it is a 10-year-old spinning disk laptop versus a newer SSD system with a warranty. Even rough details help set expectations.
- Device model (laptop/desktop, brand/model, approximate age).
- Storage type if known (SSD/HDD) and size. If you have a "clicking" HDD, stop repeated power cycles.
- Any recent drops, liquid spills, or travel damage.
- Any external devices attached when the issue occurs (USB drives, docks, external monitors).
Repair handover packet
A short repair packet stops the same problem bouncing between repair, IT support, account recovery, and provider support. It also helps decide whether the next step is repair, rebuild, replacement, warranty, or data recovery.
Symptom timeline
When it started, exact errors, recent updates or drops, whether the problem is repeatable, and whether it affects one user or everyone.
Data and access state
Backup location, restore-test result, BitLocker/FileVault state, account type, MFA status, and essential app licenses.
Tests already tried
Restart, Safe Mode, wired versus Wi-Fi, another user account, another charger, free-space check, and any error screenshots.
Decision note
Whether the current path is repair-first, recovery-first, rebuild-first, or replace-first, and what would change that decision.
Professional context
Where this connects on the main site
Computer repair work often overlaps with identity and business email. If the machine is tied to Microsoft 365, it helps to confirm tenant access and mailbox flow at the same time.
Current profile
About John Finnerty links this checklist to the broader support and software work across the main site.
Project evidence
The project hub collects public project notes and case studies that use the same evidence-first approach.
Computer repair service page
The computer repair Christchurch page describes typical fixes and the handover info that keeps risk low.
IT support scope
IT support Christchurch covers SME troubleshooting, devices, Microsoft 365 basics, and handover notes.
Domains and email basics
When email access is involved, use the DNS and email checklist to confirm the real control points.
Services overview
The services hub links the relevant support areas without making you chase menus.
Related services
Computer repair and SME IT support
If a computer is down, the best path is usually: protect data, restore access, document what was changed, then harden the system so it does not repeat.