A user whose 16GB PC exceeded 80% memory usage and froze during document and Docker work examined processes and hardware-reserved memory with Process Explorer and Resource Monitor. Application totals did not explain the whole footprint. The browser’s own task manager then revealed a CMS tab using about 1GB and a LinkedIn tab using about 875MB; closing heavy tabs brought usage into the 60% range. This is one person’s result, and high utilization alone is not an error. The reusable approach is to reproduce the slowdown and distinguish standby cache, reserved memory, and individual tab usage.