What the test was and wasn't
Hrnjicevic's machine kept an 8-core, 16-thread Ryzen 7 7700, a 2TB Crucial P3 Plus PCIe 4.0 NVMe SSD and a Radeon RX 9070 XT. The only change was the memory Windows could see. His 2x16GB DDR5 kit couldn't be physically cut down, so he limited memory in software.
He is open about the limits of this approach. The system kept dual-channel operation and DDR5 bandwidth. A real 8GB PC would more likely have a single DDR5 stick or two 4GB DDR4 modules, so its memory bandwidth could be lower. Treat his results as a best case for 8GB, not an exact stand-in.
How the memory limit works
He opened Command Prompt as administrator and made a separate boot entry:
bcdedit /copy {current} /d "Windows 11 - 8GB RAM test"
That command returns a GUID, which he used here:
bcdedit /set {GUID} removememory 24576
This removes 24,576MB (24GB) from what Windows can use.
Microsoft's documentation says you can simulate a low-memory environment without changing the physical memory, by using the truncatememory or removememory options with BCDEdit. Microsoft recommends removememory because it handles memory gaps better. The value is the installed memory minus the target, in megabytes. For 32GB installed and 8GB wanted, that is 32,768 − 8,192 = 24,576.
Some precautions apply:
- Use a separate boot entry, as the author did, so your normal boot stays untouched.
- Microsoft says BCDEdit needs administrative privileges, and some boot option changes could leave a computer inoperable.
- Microsoft also notes you might need to disable or suspend BitLocker and Secure Boot before setting BCDEdit options.
- After rebooting, Microsoft suggests confirming the available memory with a utility such as systeminfo.
- When you finish testing, remove the option with bcdedit /deletevalue.
This is an advanced diagnostic, not a tweak for a daily-driver PC.
Startup apps took a large share
On first boot into the limited entry, Task Manager's Performance tab showed 96% memory use. The author expected Windows to take a big share, but he says more than 2GB went to startup apps. He names Spotify, Slack, Asana, Discord and assorted hardware utilities. He gives only a combined figure, not per-app numbers, so don't read 2GB as a typical total for these programs.
His fix was to open the Startup apps tab in Task Manager and disable everything listed. He moved Slack and Asana to their browser versions, opened only when needed. He says this also cut down on notifications.
You can do the same on your own PC. Microsoft's guidance is to right-click Start, select Task Manager, open the Startup apps tab, and choose Disable to stop an app launching automatically. The same control is available under Settings > Apps > Startup, where you set an app's toggle to Off.
One caveat. Task Manager's "Startup impact" column is not a memory measurement. Microsoft describes it in terms of CPU and disk usage during startup. So a chat client that rates "Low" can still sit on a lot of RAM. To find memory hogs, check the Processes tab after boot.
Reading the 99% and 16.6GB figures
Later in the test, with three Chrome tabs, Slack, Spotify and Obsidian open, Task Manager showed 99% RAM use and 16.6GB of committed memory. These are two different measurements.
- Memory in use is physical RAM. At 99% on an 8GB limit, almost nothing is free.
- Committed memory is the total virtual memory Windows has promised to the system and apps. It can be far larger than physical RAM because the page file backs part of it.
Microsoft defines the system commit limit as physical memory plus all page files combined. If the commit charge reaches that limit, the system and processes might fail to get committed memory, which can cause freezing, crashing and other malfunctions. So 16.6GB committed on an 8GB-limited system doesn't mean 16.6GB was resident in RAM. It does mean the page file was likely carrying a lot of the load.
The practical lesson is that a high RAM percentage alone doesn't prove a PC is struggling, since Windows will happily use free memory for caching. The stronger signal here is the combination of near-full memory, browser tabs reloading, and multi-second delays when switching apps.
Chrome Memory Saver is a trade-off
The author also turned on Chrome's Memory Saver. Google says Chrome deactivates tabs you aren't using to save memory, and an inactive tab reloads automatically when you return to it. The setting is under Settings > Performance, with Moderate, Balanced and Maximum levels. Google lists several things that can stop a tab being deactivated, including active audio or video, screen sharing, page notifications, active downloads and partially filled forms.
On an 8GB limit this has a cost, as the author found. Memory pressure drops, but you wait while tabs reload. It is a workaround, not a substitute for more RAM.
What the author actually experienced
- The PC didn't suffer major hiccups, which he credits to the fast CPU and SSD.
- Switching back to a browser tab or opening an app took a few seconds.
- Even bringing a background app like Spotify to the foreground took several seconds, instead of being instant as it is with 32GB.
- He estimates these delays add up to several minutes lost per day. That is his own estimate, not a measured figure.
- His verdict is that 8GB is technically usable on a fast PC, but he is glad the experiment is over.
- He suspects that a slower CPU or SSD would have made things considerably worse. This is his supposition, not something he tested.
What this does and doesn't show
The test supports a modest conclusion. Windows 11 stayed workable for one person with a fast system, but multitasking got slower. It doesn't establish Windows 11's baseline memory needs, and it is not a controlled comparison. There were no repeat runs, no alternative drives, no integrated graphics, and no different Windows builds. The 2GB startup figure belongs to this author's app mix.
If you have an 8GB machine, or want to see how a PC behaves on less memory, a few checks are worth doing:
- Open Task Manager's Startup apps tab and disable anything you don't need at sign-in.
- After a fresh boot, look at the Processes tab to see what is actually holding memory.
- Watch both memory use and committed memory, along with whether you feel delays. Don't rely on the percentage alone.
- If you rely on a browser, test Memory Saver and see whether the tab reloads bother you.
- If the delays remain and your hardware allows it, adding RAM is the fix that addresses the cause.
References
- I ran Windows 11 on just 8GB of RAM for a month, and startup apps ate over 2GB How-To Geek · 2026-11-20T17:30:16+00:00
- Personalize Chrome performance - Google Chrome Help support.google.com
- Configure Startup applications in Windows support.microsoft.com