Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
And is UEFI where you change this virtual memory setting?
Windows allocates and released RAM all by itself. Increasing virtual memory won't give you better performance in general.
System ram is meaningless because some apps or games need high amount of pagefile regardless
It means 2 - things:
1. Increase swap. This should help with crashes.
2. Add more RAM. Because this means you are running aout of RAM and will have significantly reduced peformance, because swapping is slow.
Another option might be - is the game 32bit? In this case the limit on amount of (virtual)memory it can use will be ~4 GB on 64bit OS or 2-3(depending on settings) on 32bit.
Ok.
But without knowing how window's 10 scheduler works, I can't really say anything useful but that it should be left in the hands of the OS.
For your fallout 4 crash: Use stability mods. It's a bethesda game.
The poster told you that you don't need to tinker with those options. You agreed. And then proceed to explain how you tinker with the options.
You don't need to micromanage the pagefile at all. Set it to default and let Windows manage it, it's going to do a better job than you.
This make it more clear for you?
Also. With a spinner hard drive there is a good reason to manage the swap space better than Windows. You get fragmentation with a dynamic swap space. Which is why Motha suggested a fixed size. On an SSD it should not matter.
And ... Bugger off.
Windows is better managing it itself, like he said, just like defragging/TRIM of drives.
While Windows is ♥♥♥♥, and I would rather be using Linux, Windows does things much better than what people say it does, and doesn't need much help to run well. (The only help you can give it is not install a bunch of trash.)
Not just when you run out of physical memory, but when you're not using a program for a while and Windows decides ''hey, you're not using that now, but you may need to access it later, I'll save that'', and some programs need page files for caching even though there's enough space in RAM.
But, like you said, Windows knows what it's doing better than you, me, or anyone else.
Well you do you, it's still a waste of time. On either a HDD or a SSD. I think you overestimate how much the page file contributes to fragmentation on a HDD.
You clearly believe this is an important and valuable thing you're doing. But I think you're going to have a tough time substantiating that if asked to.
How to stop it fragmenting your os drive and actually have it run better?
Go to the pagefile settings.
Set it to None and click OK.
Reboot and defrag or trim your os drive.
Go back into pagefile settings and click C drive, now set the size manually to 8192 for both min and max, click set, click OK. Reboot.
Now the pagefile is recreated fresh on C drive all in one chunk that should be in order and not scattered all over the drive. It wont fragment now because you've locked in a min and max size to the same amount.