The front-desk PC and a 150 USD upgrade
A reception desk runs Windows 10 (64-bit) on a Core i3-6100 with 4 GB of DDR4 RAM (two of four slots occupied by 2 GB modules), a 1 TB 5400 rpm hard disk with 60 GB free, and no separate graphics card. Staff keep 15-20 browser tabs open alongside Outlook and a 40 MB Excel workbook. Boot takes about three minutes, Task Manager shows disk activity pinned at 100% for several minutes after login, and the machine becomes unresponsive when switching between windows. The office manager has approved a single 150 USD upgrade, one hour of downtime, and insists the same PC must be kept for at least another year. A local shop sells a 500 GB SATA SSD for 45 USD and 8 GB DDR4 modules for 35 USD each.
1. Task Manager shows disk at 100% for several minutes after login. Rank the two possible upgrades by expected impact and state what additional evidence you would collect before deciding whether the RAM purchase is also justified.
Read the worked answer
SSD first, RAM second, but gather memory evidence before spending.
Reasoning. The symptom set (three-minute boot, disk saturated after login, freezing when switching windows) is dominated by random disk I/O. A 5400 rpm drive delivers roughly 80-120 random IOPS, and login, antivirus scanning and browser start-up all queue behind it. Any SATA SSD raises that by an order of magnitude for 45 USD, so it gives the largest, most predictable gain.
4 GB with 15-20 tabs is also tight, and when physical RAM runs out Windows pages to that same slow disk, which is why the two faults compound. Before buying, open Task Manager, Performance tab, and record committed memory versus physical memory and the hard-fault rate while the user works normally. If memory sits above roughly 90% with sustained hard faults, add RAM as well (2 x 8 GB = 70 USD, total 115 USD, inside the cap). If not, the SSD alone is the better spend and the remainder stays in reserve.
2. List the compatibility checks you would make before ordering the SSD and the RAM, and for each state the consequence of skipping it.
Read the worked answer
- Storage interface and bay. Confirm the board has a free 2.5-inch SATA bay and port, or an M.2 slot, and check whether an M.2 slot is SATA-only or supports NVMe. Skip this and you may buy an NVMe drive for a SATA-only slot, which will not be detected at all.
- Memory type. Confirm DDR4, unbuffered, non-ECC, correct speed and voltage. Skip this and a DDR3 module will not physically fit (different notch keying), while a registered or ECC server module will simply fail to boot.
- Board limits. Check the manual for maximum capacity, maximum per slot and slot count. Skip this and you may buy modules the board cannot address, or produce a mismatched 2 GB + 8 GB pairing where matched pairs would have been cheaper.
- Encryption and licensing before cloning. If BitLocker is on, obtain the recovery key and confirm the edition supports what you plan. Skip this and you finish with a cloned disk that asks for a key nobody has.
- Back up the user data first. A failed clone is a data-loss event, not just a delay.
3. Two days later the same PC again shows long periods at 100% disk, now in the middle of the day with no heavy user work. What should you investigate before recommending any further upgrade?
Read the worked answer
Treat this as a different symptom and rule out failing hardware before spending more money.
- Disk health. Read the SMART attributes for reallocated, pending and uncorrectable sectors, and check the event log for disk or controller errors (timeouts, bad-block resets). Reallocation or repeated resets means the drive is dying: stop buying RAM, back up immediately and replace the drive or bring the replacement PC forward.
- Background load. Use Resource Monitor to see which process and which files are generating the I/O. Candidates are a mid-day antivirus full scan, Windows Search re-indexing, update delivery, and a sync client retrying a large backlog.
- Memory pressure. Confirm whether the page file is thrashing, which would point back to RAM.
- Network shares. A disconnected mapped drive reconnecting or a large file open over Wi-Fi can stall the shell and look like a local disk problem.
Only if all of these are clean does a further upgrade make sense; if the disk is failing, the plan changes from upgrade to replacement.