When an 8 GB laptop freezes, people blame the CPU, the antivirus or Windows itself. Most of the time it is simpler: the machine ran out of physical memory and started swapping to disk. The fix is to stop filling memory, not to reinstall Windows.
These are the nine changes I measured on the test machine, ranked by how much they helped. All are reversible.
The result
Startup apps, browser tab discipline and a fixed page file removed most of the freezes. Sustained free RAM went from about 0.8 GB to 2.1 GB during normal work — without buying anything.
First, confirm the diagnosis
- Open Task Manager (
Ctrl+Shift+Esc). - Go to Performance → Memory.
- Look at In use (Compressed) and Committed.
If committed memory is consistently above your physical RAM (8 GB), you are paging. If it is below but the disk is at 100%, something else is wrong — often a failing drive or a runaway process.
Also check Startup apps and the Processes tab sorted by memory. The top three are usually the browser, the editor and something you forgot was running.
Do not “optimise” blindly
Registry cleaners, RAM “boosters” and debloat scripts often make things worse. Every change below is either a Windows setting or a habit, and each can be undone.
The nine fixes, ranked
1. Cut startup apps
Effect: +300–700 MB free at login.
Task Manager → Startup apps → disable everything you do not need immediately. Cloud sync clients, game launchers, update helpers and chat apps are the usual suspects.
Keep: your password manager, audio driver, and anything you genuinely use every session.
2. Cap browser tabs
Effect: +500 MB to 1.5 GB.
A browser is the largest memory consumer on most 8 GB machines. Ten tabs can take 1.5 GB; a video call tab can take another 500 MB.
Options:
- Use a tab suspender extension (auto-discard inactive tabs).
- Keep one browser window, not three.
- Close YouTube and long-lived dashboards when not in use.
- Use the browser's built-in “Memory Saver” if available.
3. Set a fixed page file
Effect: fewer hard freezes, not more speed.
Windows manages the page file dynamically, which can cause stalls when it resizes under pressure. A fixed size on the SSD is more predictable.
System Properties → Advanced → Performance Settings → Advanced → Virtual memory → Change:
- Custom size: initial 4096 MB, maximum 8192 MB (for 8 GB RAM).
- Keep it on the SSD, never on a mechanical drive.
This does not replace physical RAM. It prevents the worst “nothing responds for 30 seconds” behaviour.
4. Trim the editor
Effect: +180 MB and 5 seconds at startup.
VS Code with 18 extensions was using 780 MB. With six, it used about 600 MB and started in four seconds. The full breakdown is here.
5. Disable visual effects
Effect: small CPU/GPU gain, smoother window dragging.
System Properties → Advanced → Performance → Settings → “Adjust for best performance”. Then re-enable font smoothing and thumbnails if you want them.
The visual difference is minor; the responsiveness gain on integrated graphics is noticeable.
6. Remove duplicate background services
Effect: 100–300 MB.
Check Task Manager for:
- two antivirus products (never run two)
- vendor “assistant” apps from laptop makers
- multiple cloud drives (OneDrive + Dropbox + Google Drive)
- RGB and peripheral software
Uninstall what you do not use. Disable the rest at startup.
7. Use Storage Sense and keep 15% free
Effect: prevents SSD slowdown and failed updates.
A nearly full SSD writes more slowly and Windows struggles to update. Settings → System → Storage → Storage Sense: enable automatic cleanup of temporary files and the recycle bin.
Keep at least 15% of the drive free. On a 256 GB drive, that is about 38 GB.
8. Update the graphics driver and BIOS
Effect: fixes specific freezes, especially video playback.
A 2018 laptop may be running a five-year-old Intel graphics driver. Vendor update tools are often stale; get the driver from Intel's site or Windows Update.
BIOS updates fix power-management bugs that cause random hangs. Only update from the manufacturer's official page, and only if the changelog mentions stability.
9. Check the SSD's health
Effect: identifies a dying drive before it takes your data.
Run CrystalDiskInfo or the manufacturer's tool. Look for “Caution” or rising reallocated sectors. A failing SSD causes freezes that look like memory problems.
Back up before diagnosing further. If the drive is failing, no software fix will help.
What did not help
| “Fix” | Result |
|---|---|
| RAM booster / cleaner apps | Freed memory briefly, then made the system re-read from disk |
| Disabling the page file entirely | Made out-of-memory crashes more likely |
| Registry cleaners | No measurable effect |
| “Debloat” scripts | Removed useful components; no memory gain |
| Increasing the page file to 32 GB | Reduced crashes, but paging was still slow |
| Disabling Windows Defender | Not worth the risk; no meaningful gain |
The honest limit
After all nine fixes, the machine idles at about 3.2 GB used and has 2–3 GB free during normal work. That is enough for an editor, a browser with discipline, and a small language model — one at a time.
It is not enough for a browser with 30 tabs, a video call, Docker and a 7B model. No setting changes that. The RAM upgrade does, for about $40.
A five-minute weekly habit
- Reboot once a week. Sleep is not a reboot.
- Check startup apps after installing anything new.
- Close what you are not using.
- Keep 15% of the disk free.
- Watch Task Manager for a week; patterns are obvious by day three.
FAQ
Does readyboost or a USB drive help?
No. USB flash memory is far slower than an SSD and wears out. It was a Vista-era trick.
Will a cooling pad stop freezes?
Only if the freezes are thermal throttling. Check CPU temperature and clock speed in Task Manager or HWiNFO. If the CPU drops to 800 MHz under load, cooling is the issue.
Is Windows 11 heavier than Windows 10 on 8 GB?
Slightly, but the difference is small compared with browser and app usage. Do not downgrade to chase memory.
Should I switch to Linux?
A lightweight Linux distribution can idle at 700 MB instead of 3 GB, which is a real gain on 8 GB. The cost is software compatibility, especially for Office and vendor drivers. It is a legitimate option for a secondary machine.
Related reports
- 8 GB vs 16 GB: is the upgrade worth it?
- VS Code on a memory diet
- Python setup that stays fast
- Cheapest way to run local AI