Visit Website →
← Back to blog

Game Stutter? Test Windows 11 Memory Compression Before Disabling It

October 16, 2026
Game Stutter? Test Windows 11 Memory Compression Before Disabling It

Memory compression is enabled by default in Windows 11, and for most PCs it is best left on. It trades a little CPU time for more usable RAM. If you see CPU spikes or game stutter, update your drivers and diagnose first, then test disabling it temporarily with PowerShell. The change needs a reboot to take effect.

TL;DR:

  • Task Manager’s compressed memory value is not a diagnosis: a few hundred megabytes can be normal, while stutter alongside a rising figure suggests memory pressure.
  • Before testing, update GPU, chipset, and storage drivers, sort processes by memory, and check for leaks or runaway background apps.
  • Disable compression only if CPU use is traceable to it and an identical workload test shows less stutter; turning it off can increase pagefile activity.
  • A change takes effect only after a reboot; verify the result with PowerShell, since the toggle commands may return without a confirmation message.
Tempered
Diagnose Stutter Before Changing Settings
Tempered identifies real performance constraints and explains user-approved changes, with an undo path to help you stay in control.
Explore Tempered

Table of Contents

What is memory compression and why does Windows use it?

Memory compression is a Windows feature that squeezes rarely used pages of RAM into a smaller footprint instead of writing them out to disk. Those pages stay in memory, just packed tighter, which means your PC can hold more working data before it runs short. Windows 11 turns it on by default, according to HowToGeek's walkthrough.

Why bother? Reading a compressed page back from RAM is far faster than fetching the same data from the pagefile on a drive, even a fast SSD. So Windows prefers to compress first and page to disk only when it has to.

This also explains why Task Manager can look alarming. The memory graph mixes active data, compressed data and cached pages that Windows can drop instantly. As one Microsoft Q&A thread on how Task Manager reports memory explains, those metrics don't always account for shared memory or the standby list, so a high percentage is not automatically a problem. How your PC actually feels matters more than the number.

How does memory compression work, and what does it cost?

The core trade is simple: Windows spends some CPU cycles compressing and decompressing pages so it can avoid much slower pagefile I/O. Microsoft community experts describe it as a CPU-for-RAM trade-off, and they note that most complaints blamed on compression are really symptoms of memory pressure.

When compression is working hard, you may notice:

  • A moderate bump in CPU use, usually from the System process
  • A growing "Compressed" value in Task Manager's memory view
  • Stutters or hitches when RAM is nearly full and Windows starts shuffling pages

Here is the part people miss. Compression being busy usually means your system is short on free memory, not that compression itself is the culprit. A leaking application, a misbehaving driver or too many background programs can all push RAM to its limit. Compression just shows up in the middle of the scene and takes the blame.

That's why "memory hog" reports so often turn out to be something else entirely. Before you touch the setting, work out what is actually eating your RAM. If you want a refresher on reading those numbers, our guide to checking RAM usage in Windows walks through it.

How do you check memory compression in Windows 11?

Measure first. These two checks are quick.

  • Task Manager: Press Ctrl+Shift+Esc, open the Performance tab, and select Memory. Look at "In use (Compressed)," then hover over the Memory composition bar for a breakdown of in-use, modified, standby and free memory.
  • PowerShell: Right-click Start, choose Terminal (Admin) or Windows PowerShell (Admin), and run Get-MMAgent. Find the MemoryCompression line. True means it is on, False means it is off.

To interpret what you see, compare the compressed figure with your total RAM and with how the PC behaves. A few hundred megabytes compressed on a machine that feels fast is normal. A large compressed value paired with stutter points to memory pressure, so look at which processes hold the most RAM. Note your baseline now, because you'll want it later. Responsiveness during your real workload beats any single percentage.

How do you disable or re-enable memory compression?

You control the feature with two PowerShell commands, both documented by HowToGeek. Here is the sequence:

  1. Open PowerShell as administrator.
  2. To turn compression off, run Disable-MMAgent -mc. To turn it back on, run Enable-MMAgent -mc.
  3. Expect no confirmation message. The commands often return silently, which makes people think nothing happened.
  4. Restart your PC so the kernel applies the change.
  5. Run Get-MMAgent again and confirm the MemoryCompression value.

A sensible test plan looks like this: record a baseline first, such as frame rate and frame-time consistency in a game, or how quickly your usual apps respond. Then disable compression and reboot, repeat the exact same workload, and compare. If stutter or pagefile activity gets worse, re-enable it.

Pro Tip: Change one thing at a time and reboot between tests, so you know which change made the difference.

Should you disable memory compression? A checklist for gamers and heavy users

For most client PCs, no. Disabling makes sense only when the evidence points that way. Disabling is reasonable when:

  • You have confirmed that compression is burning measurable CPU
  • A controlled test shows less stutter with it off
  • You have enough RAM headroom to accept more pagefile activity

The trade-offs are real. Turning compression off can increase pagefile I/O, and if your RAM actually fills up, stutters can get worse rather than better. Servers commonly run without it, but typical desktops and laptops tend to benefit. Many experts still recommend leaving it on unless your tests show a benefit.

If you're chasing high memory use or stutter, work through this order:

  • Update your GPU, chipset and storage drivers
  • Sort processes by memory to spot leaks or runaway apps
  • Check that your paging file is configured sensibly (our article on increasing virtual memory covers it)
  • Close or disable problem background apps, which you can do safely without registry edits
  • Only then test disabling compression briefly, rebooting between steps

One common mix-up: memory integrity, also called Core isolation, is a separate security feature. Microsoft describes it in Windows Security's device security settings, and incompatible drivers can block you from toggling it. It has nothing to do with compression, and our piece on testing before you disable memory integrity explains why.

Pro Tip: If a test makes things worse, re-enable compression right away. A quick revert costs one command and one reboot.

Why should you diagnose before you toggle?

Practitioners keep landing on the same point: compression is typically a symptom of memory pressure, not the root cause. Community experts describe a CPU-for-RAM trade-off and warn that users often misidentify compression as the problem when leaks or drivers are the real issue. Switching it off without a diagnosis can swap a small CPU cost for pagefile-induced stutters that feel worse.

So put the priorities in order. Update drivers first. Check how the standby cache behaves, since cached pages can make "used" memory look scarier than it is. Confirm whether a genuine memory leak exists by watching a process's memory climb over time without ever falling.

Then follow a short verify-and-revert protocol: measure, disable, measure again, and re-enable if the numbers or the feel get worse. Keep the whole thing reversible and you lose nothing by trying.

Does hardware or third-party software change how well compression works?

Yes, in a few predictable ways. Your RAM capacity matters most. On a PC with limited RAM, compression is working in tight quarters, and it may help keep a browser, a chat app and a game from pushing you into the pagefile. On a machine with ample RAM, you may rarely fill memory at all, so compression stays mostly idle and its effect is hard to notice either way.

CPU speed matters too. A fast modern processor handles compression with little visible cost, while an older or low-power chip feels the overhead more, especially on battery. Storage type changes the other side of the equation: if your pagefile sits on a slow hard drive, avoiding disk I/O is worth more, so compression tends to earn its keep there.

Third-party software enters through drivers and background services. A flawed GPU, chipset or storage driver can leak memory or hold pages, which makes compression look busy. Overlays, capture tools, RGB utilities and aggressive "optimizer" apps can all add pressure on the same RAM you're trying to protect. Security tools that scan memory can also spike CPU use at the same moment compression is active, which makes the two easy to confuse.

The practical takeaway: before blaming compression, note what else is running, update drivers, and retest with the extras closed. If the symptom disappears, you found the real cause. If you'd rather not do that detective work by hand, we built Tempered to read your live CPU, RAM and disk metrics and propose changes you approve one at a time.

How does memory compression interact with ReadyBoost and Superfetch?

These features all try to make memory and disk work smarter, but they do different jobs, so they coexist rather than compete.

Superfetch, now called SysMain, watches which apps you launch and preloads their data into spare RAM so they open faster. That preloaded data lives on the standby list, which Windows can release the moment an app needs real memory. It's a big reason Task Manager shows high usage on a healthy PC. Compression works on a different problem: it shrinks pages that are already in memory and rarely touched. Both can be active at once, and neither blocks the other.

ReadyBoost used a USB drive or flash storage as extra cache to speed up reads on slow disks. It was built for an era of hard drives and small amounts of RAM. On a modern PC with an SSD, it offers little, and Windows often won't enable it at all because the system drive is already fast. It is not a replacement for compression, and compression doesn't depend on it.

The simple mental model: SysMain predicts what you'll need and caches it, compression packs the idle stuff tighter, and the pagefile is the slow last resort. Switching compression off leaves SysMain and the standby list intact, but it removes the middle step, so Windows reaches for the pagefile sooner when memory runs tight.

How caching, compression, and the pagefile interact

That's one more reason to test rather than assume. If you disable compression and the pagefile suddenly gets busier, you've seen the middle layer's value firsthand.

How should you monitor memory compression over time?

A single snapshot tells you very little. Compression behaves differently at idle, during a game and after the PC has been up for days, so watch it across normal use.

Start by recording the same few readings at consistent moments: right after boot, during your usual work, and during your heaviest task. Task Manager's Memory view gives you compressed memory, in-use memory and the composition bar. Resource Monitor adds a view of hard faults, which are page reads from disk. Rising hard faults alongside high compression suggest real memory pressure.

Look for patterns, not numbers. A compressed value that stays steady while the PC feels snappy is fine. One that climbs for hours and never drops usually means a process is leaking, so find it before you touch any setting. Our guide to finding CPU hogs in Windows 11 helps with the CPU side of that hunt.

Reconsider the enabled state only when several things line up: a repeatable stutter, CPU time you can tie to compression, drivers already updated, and a controlled test where disabling helped. Also revisit the decision after big changes, like adding RAM, moving the pagefile to a faster drive, or upgrading your CPU, since each shifts the trade-off.

Write down your results. A short note of what you changed, what you measured and what happened saves you from repeating the same test months later.

What does memory compression actually do to performance?

The honest answer is that effects vary by machine, and we won't invent benchmark figures to make it sound tidier. What you can observe are the mechanisms.

When RAM is plentiful, compression barely registers. The CPU cost is small, nothing is waiting on the disk, and your system feels the same with the feature on or off. When RAM gets tight, the picture changes. With compression on, Windows packs idle pages and keeps them in memory, so switching back to a background app is quick. With it off, those same pages may be written to the pagefile, and bringing them back means a disk read, which is the kind of delay you feel as a hitch.

A simple example: imagine a game, a browser with many tabs and a voice chat app running together on a 16 GB machine that is close to full. With compression on, alt-tabbing to the browser tends to feel instant because its pages were compressed in RAM. With it off, the first return to a long-idle tab may pause while data loads from disk. On the other side, if the same game is CPU-bound on a modest processor, the small compression overhead might shave a little off frame-time consistency, and that's the case where disabling can help.

Measure what you care about: frame-time variance in games, app switch speed, and CPU use during your real workload. Compare before and after on identical tasks. The measured difference, not the theory, should decide your setting.

What does memory compression actually do to performance? — overview diagram

What do I think about testing memory compression?

I treat this setting like any tweak: try it briefly, measure with clear metrics such as frame rate, frame-time variance and how fast apps respond, and keep the change reversible. Chasing a lower Task Manager percentage is a trap, because a PC that feels smooth beats one that merely reports less memory used. If you're still hunting the cause of slowdowns, read our guides on finding CPU and RAM hogs next.

— Ian

FAQ

Does disabling memory compression improve performance?

Usually not. Compression trades a little CPU for avoiding slower pagefile reads, so turning it off can make stutters worse when RAM fills. It can help in specific cases where compression overhead is confirmed, so test briefly and re-enable it if things get worse.

How do I check if memory compression is enabled?

Open PowerShell as administrator and run Get-MMAgent. The MemoryCompression line shows True when it's on and False when it's off. You can also see compressed memory under Task Manager's Performance tab, in the Memory view.

I can't turn off memory integrity. What should I do?

Memory integrity is a separate security feature from memory compression. Microsoft notes that incompatible drivers can prevent you from toggling it, so update or remove the flagged drivers first.

How do I fix memory issues on Windows 11?

Diagnose before changing settings. Update your GPU, chipset and storage drivers, sort processes by memory to find leaks, and review your paging file. Only then test disabling compression briefly and revert if it doesn't help.

Sources