Exam lab with 4 GB RAM and a full antivirus scan
A government school computer lab has 20 Windows 10 desktop PCs, each with 4 GB RAM, a 500 GB 7200 rpm hard disk and Windows set to manage virtual memory automatically. During a 40-minute online examination, students open a browser with 8-10 tabs, a PDF viewer and LibreOffice, while the antivirus starts its scheduled full scan. Several PCs slow to a crawl; Task Manager shows 98% memory use, disk activity at 100% for minutes, and only 2 GB free on C:. A teacher suggests setting the page file to 16 GB and disabling the antivirus permanently. The lab technician wants a safer plan that keeps the machines usable for the exam and explains why the disk light stays on. The school cannot buy new hardware before the exam but may change settings and free space.
1. Explain the observed 98% memory use and 100% disk activity. Why does increasing the page file alone not restore responsiveness?
Read the worked answer
Windows itself, a browser with 8-10 tabs, a PDF viewer, LibreOffice and the antivirus can easily exceed 4 GB of private working set. When free RAM runs out, Windows trims pages and writes them to the page file. If the page file is on the same 7200 rpm HDD, every hard fault becomes a random read or write, and the disk queue grows. That is why memory is at 98% and disk activity stays at 100%: the system is thrashing, not CPU-bound. Increasing the page file adds backing store but not RAM, so it cannot reduce the fault rate; it may even make things worse because the file is on the same spindle and C: has only 2 GB free. The disk light stays on because the paging I/O is continuous.
2. Evaluate the teacher's two suggestions and give a safe, specific plan for the exam.
Read the worked answer
Reject both suggestions as stated. Disabling antivirus permanently is a security and exam-integrity risk and is not needed. A 16 GB page file is impossible with 2 GB free and would cause file-system pressure. Safe plan: free 10-15 GB with Disk Cleanup, remove temporary files and unused applications; set a custom page file of about 4096-8192 MB on C: (or on a second physical disk if one exists); reschedule the antivirus full scan to after the exam and keep real-time protection on; disable non-essential startup apps; ask students to use fewer tabs; run the exam in one browser window. After the exam, add RAM or an SSD. These changes reduce paging and I/O without weakening security.
3. The technician sees 100% disk but only 40% CPU. Which measurements would distinguish memory pressure from a failing disk, and what values would point to each?
Read the worked answer
Open Resource Monitor or Task Manager and compare memory and disk counters. Memory pressure: page file usage high, hard fault rate high, committed bytes near the commit limit, disk queue length high but disk response time moderate, and process working sets being trimmed. A failing disk: disk queue length high with very high average response time (for example above 100 ms on an HDD), SMART warnings, retries or events in Event Viewer, while memory and page file usage may be normal. CPU at 40% argues against a CPU-bound problem. The decisive pattern is whether paging and commit charge track the slowdown; if they do, it is memory pressure, not disk failure.