How to check your Windows PC's health and performance
A reliable way to assess a Windows computer is to test it in stages instead of guessing from one slow app. A slow desktop can have several causes: a failing SSD, overheating fan, overloaded memory, or startup software. Windows provides enough built-in tools to find the likely culprit before you buy parts.
Start under repeatable conditions: save work, restart, disconnect unnecessary USB devices, and watch normal tasks. Record startup time, fan noise, heat, and whether a program stays slow after closing. A consistent baseline makes gradual deterioration easier to spot.
Start with a clean baseline
A restart clears temporary memory, finishes pending updates, and gives startup programs a fair test. Wait for the desktop to settle, then open your usual apps. On a family PC, check whether browser tabs, calls, and cloud syncing compete for one drive.
Open Task Manager with Ctrl+Shift+Esc and select Performance. Let the graphs settle for a minute, then repeat during real work. CPU, memory, disk, network, and GPU activity tell different stories; a brief loading spike is less concerning than a maximum reading that persists.
Record the result in a note. If the machine feels “a bit crook” in the arvo, measurements can show whether cooling, storage, or software is responsible. Colloquial clues are not diagnoses.
Read the live performance counters
Use Task Manager as a diagnostic, not a scorecard. Open Resource Monitor with resmon to see which program is producing disk or network traffic. Compare copying a document with editing video or launching a game.
Focus on sustained pressure, not one busy second. These counters are the most useful:
- CPU: Brief spikes are normal; sustained 80–90% or more during one task deserves attention.
- Memory: Consistently above about 85% with heavy swapping indicates pressure.
- Disk: Active time near 100% for minutes points to a slow drive, scan, or synchronisation.
- Network: A full graph may mean a busy NBN connection or download, not a slow processor.
Read the counters together. High memory plus heavy disk activity often means paging; high disk activity with low CPU suggests a slow drive or scan. If slowdown appears only during mobile messaging, a WhatsApp troubleshooting guide may rule out a phone-side issue first.
Check storage health and free space
Open Settings, choose System, then Storage, or right-click C: in File Explorer to check free space. Keep 15–20% free on the system drive for updates, temporary files, and virtual memory. Storage Sense can clear downloads and the recycle bin, but check Downloads first.
Free space is not drive health. Use the maker’s utility or a reputable SMART tool to check failure warnings, bad sectors, and sudden response-time changes. Reliability Monitor also records some disk errors without a clear pop-up.
Use these storage checks:
- System drive: Keep 15–20% free and remove forgotten installers.
- SSD: Read the SMART or manufacturer health report.
- HDD: Run a full scan and investigate reallocated or pending sectors.
- Backup: Confirm that important files have a recent copy.
If an SSD is slow or warns of failure, back up before shopping. Compare price, warranty, and fit at JB Hi-Fi, Harvey Norman, or Officeworks, then read the Australian retailer’s warranty terms.
Verify memory, system files, and security
Windows Memory Diagnostic is a useful first pass for unstable RAM. Press Win+R, type mdsched.exe, choose to restart now, and let the test finish. It is not a full stress test, so a clean result is not absolute proof.
For damaged Windows components, open Terminal or Command Prompt as administrator. Run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, and restart. “No integrity violations” is good; “found corrupt files” means repair is needed. Neither command rescues a failing drive.
Check Windows Security, Windows Update, and device drivers. Run a full malware scan and use Reliability Monitor to find crashes near the slowdown. Temporarily disabling an extension, sync client, or startup app can reveal background interference.
If you use Android as a study companion, the coding apps for Android guide can keep practice separate from the Windows workload. Testing one realistic workflow at a time shows whether the PC or the surrounding setup is slowing you.
Inspect thermals, power, and hardware
A quiet fan does not prove a cool processor. Use HWiNFO64, Core Temp, or a hardware utility to watch CPU and GPU temperatures under load. Look for throttling, clock drops, and readings outside the maker’s guidance.
Australian conditions make this practical. Summer heat in Adelaide and inland areas can warm a small office quickly, while humid afternoons in Sydney and Melbourne can make a poorly ventilated room worse. Keep vents clear, clean filters, avoid a closed cupboard, and record room temperature in Celsius.
Check the power supply, cables, and surge protector. Consider a UPS suitable for Australian 230-volt mains if outages interrupt work. Rattling fans, shutdowns under load, or unusual heat deserve professional inspection. “She’ll be right” is reasonable for a minor glitch, not burning smells or arcing.
Test real workflows and network behaviour
Benchmarks help only when they resemble your day. Open your usual programs, copy a large folder, join a Teams meeting, stream video, and play a game for ten minutes. Compare warm and cold starts; consistent differences point toward heat, storage, or an application.
On many Australian connections, NBN speed depends on the router, Wi-Fi band, and local congestion as much as the plan. Test with Ethernet, compare ping with a speed test, and use Event Viewer for driver resets. A busy graph during a download is expected; on an idle desktop it is not.
For moving files between Android and the computer, the wireless Android transfers guide provides a cable-free workflow. If transfers are the only slow step, check phone Wi-Fi, the PC adapter, and storage before condemning the system.
Build a repeatable PC health routine
Run the baseline monthly and after major updates: restart, inspect Task Manager, check space and drive health, test memory after crashes, and confirm backups. Keeping results in one note makes deterioration easier to spot.
Match symptoms to evidence. Slow launches suggest startup software, low space, or a failing SSD; game stutter calls for a temperature check; freezes deserve memory and system-file results; slow pages need a network test. Fix one evidenced problem at a time.
Use this sequence now: open Task Manager, record CPU, memory, disk, and network figures under normal work, then check the system drive and Reliability Monitor. Address the first measured issue, and repeat the same test after the fix.
