Troubleshooting Playbook

Structured troubleshooting workflows from repair work, support, and hands-on diagnostics.

A practical playbook for turning symptoms into evidence, tests, documentation, and clear customer explanations.

Playbook Entries

Repair and Support Workflows

Windows Won’t Boot

Symptoms: Startup repair loops, black screen, failed updates, blue screens, or boot device errors.

Likely Causes: Corrupted system files, failed updates, drive issues, bootloader problems, malware, or hardware failure.

Tools Used: Windows Recovery Environment, DISM, SFC, backup tools, bootable USB, drive diagnostics.

Diagnostic Steps: Check boot behavior, attempt recovery options, verify drive health, run repair commands when appropriate, preserve user data before destructive repair.

Documentation Notes: Record symptoms, error messages, repair attempts, data risk, and recommended next steps.

Customer Explanation: Explain whether the issue appears software-related, storage-related, or hardware-related and whether data backup is needed before repair.

Display Issue vs GPU Issue

Symptoms: No image, external display behavior differences, backlight issues, artifacts, cracked LCD, intermittent display.

Likely Causes: LCD failure, display cable issue, backlight failure, graphics issue, board-level issue.

Tools Used: External monitor, visual inspection, known-good display behavior, diagnostic notes, photos where appropriate.

Diagnostic Steps: Compare internal and external output, inspect physical damage, check backlight/image behavior, document evidence, avoid overclaiming certainty.

Documentation Notes: Clearly distinguish observed evidence from conclusions.

Customer Explanation: Explain why the evidence points more toward a display assembly issue, cable issue, or graphics-related fault.

macOS Migration Issues

Symptoms: Missing files, apps not opening, sleep/lock behavior changes, Dropbox/photo sync changes, permissions issues.

Likely Causes: Migration Assistant quirks, app compatibility, login items, privacy permissions, cloud sync settings, system settings.

Tools Used: System Settings, Migration Assistant, Dropbox settings, privacy permissions, Activity Monitor, user account settings.

Diagnostic Steps: Verify data transfer, check login items, confirm sync settings, review sleep/lock options, test workflow with customer-specific apps.

Documentation Notes: Document what transferred, what still needs setup, and what settings changed.

Customer Explanation: Explain that migrations often move data successfully but may require app-specific settings and permissions to be reconfigured.

Offline Email Access Setup

Symptoms: Old emails missing from webmail, local archive requested, attachments need preservation, multiple email accounts involved.

Likely Causes: Webmail search limitations, account sync settings, provider retention, local client configuration, folder visibility.

Tools Used: Mail client, account settings, IMAP/POP settings, export/archive tools, backup storage.

Diagnostic Steps: Identify accounts, verify webmail access, configure mail client, sync folders, confirm old messages/attachments, back up local mail data when possible.

Documentation Notes: Record accounts configured, sync method, local storage location, and limitations.

Customer Explanation: Explain the difference between online access, synced local access, and true offline archives.

Random Gaming Crashes

Symptoms: Game crashes, driver errors, system instability, overheating, power issues, controller/input issues.

Likely Causes: GPU driver problems, overheating, unstable RAM, PSU issues, corrupted game files, background software conflicts, controller firmware/input bugs.

Tools Used: Event Viewer, temperature monitoring, driver tools, Windows updates, stress tests, game file verification.

Diagnostic Steps: Update drivers, check temps, review crash logs, test hardware stability, isolate peripherals, verify game files.

Documentation Notes: Record when crashes happen, temperatures, error messages, drivers installed, and test results.

Customer Explanation: Explain whether the issue looks software, thermal, driver, hardware, or peripheral-related.

Wi-Fi Adapter Not Appearing

Symptoms: No Wi-Fi option, missing adapter, unknown network devices, Ethernet works but Wi-Fi does not.

Likely Causes: Missing driver, disabled adapter, Windows update issue, BIOS setting, failed Wi-Fi card, conflicting network software.

Tools Used: Device Manager, Windows Update, manufacturer drivers, BIOS settings, USB Wi-Fi test adapter.

Diagnostic Steps: Check Device Manager, install correct drivers, verify BIOS, test with external adapter, inspect hardware if needed.

Documentation Notes: Record driver versions, device status, and whether hardware appears detected.

Customer Explanation: Explain whether the system appears to have a driver issue or a possible hardware failure.