Steam'i Yükleyin
giriş
|
dil
简体中文 (Basitleştirilmiş Çince)
繁體中文 (Geleneksel Çince)
日本語 (Japonca)
한국어 (Korece)
ไทย (Tayca)
Български (Bulgarca)
Čeština (Çekçe)
Dansk (Danca)
Deutsch (Almanca)
English (İngilizce)
Español - España (İspanyolca - İspanya)
Español - Latinoamérica (İspanyolca - Latin Amerika)
Ελληνικά (Yunanca)
Français (Fransızca)
Italiano (İtalyanca)
Bahasa Indonesia (Endonezce)
Magyar (Macarca)
Nederlands (Hollandaca)
Norsk (Norveççe)
Polski (Lehçe)
Português (Portekizce - Portekiz)
Português - Brasil (Portekizce - Brezilya)
Română (Rumence)
Русский (Rusça)
Suomi (Fince)
Svenska (İsveççe)
Tiếng Việt (Vietnamca)
Українська (Ukraynaca)
Bir çeviri sorunu bildirin
Bu başlığın sahibi kendi sorularının cevabı olarak bir gönderiyi seçti.
Tartışma Kuralları ve Yönergeleri
Bu iletiyi bildir
Just a little update, i just formatted a new 1tb ssd. Im i gonna have to change the virtual memory settings to be the same on that drive?
If you didnt install windows again, than no. A new drive does not need a page file. However, you can still add if you want. Or, if your other page file was on a HDD, you can now move it to the SSD. So it will be faster.
So it was that only one drive i need to edit in order to get last of us to stop crashing?
You can add a pagefile to whatever drive you want. Having a pagefile on an SSD will be better than on a HDD.
To properly setup a pagefile it should be 1.5 * RAM. So if you have 16GB of RAM. Your pagefile should = 24GB. If you have 3 drives with enough space available. You can set each drive to 8GB.
If you only have 2 drives, 1 HDD and 1 SSD, than set all your pagefile to the SSD. It just needs to have 24GB free space.
You should also do a clean boot. A clean boot will remove any potential conflicts with other software running in background. So disable all non essential services, programs and tasks from starting with PC. So use services (services app or system configuration app), tasks (task scheduler app, select task scheduler library), and startup items (task manager) to disable them.
Check all 3 areas. If anyone is enabled that software will run and could be causing conflicts with the game. This will also help free up system resources in general so the system will have more RAM available. As well as alleviate background processes to help the CPU have less strain.
IMO your system is very old. Your CPU is well over 13 years old now. Your GPU is well over 7 years old and a low tier 4GB card. If you are still having issues than my advice is to buy a whole new PC. As it will only become more problematic with each modern game you try to play on it. What worked for this game may not work for another.
Since your game was still crashing even after adjusting the pagefile. There is obviously other issues causing the game to crash. Thats why at this point. I think its time to move on from this system and buy something a little more modern. Because overall you are very limited on what you can do with this system. Especially since it is also under the min requirement to run this game for the CPU.
Hey again, ive installed the game on my other ssd now that i got it, im i going to have to increase the virtual memory on my other drive?
what is the other drive? like an hdd? then you should remove the pagefile from it, reboot and allocate the virtual memory on the ssd. the fastest drive you got. also the 24 GB animal recommends is a lil overkill. don't take that advice. 8-10 GB should be enough to run the game.
https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/how-to-determine-the-appropriate-page-file-size-for-64-bit-versions-of-windows
Lastly, the OP is using a 13 year old system. There really is no point fussing around with it.
No. Just because you added a new storage drive. Does not mean you also need to increase the page file.
come on. stop doing this generic tech support answer crap. that office rubbish is your recommendation? 24 GB for a full memory crash dump? wth. if the OS crashes that hard to require a full memory dump to debug it, it should probably be reinstalled. a regular OS crash should not exceed 2 GB of dumped OS memory. apps and drivers not included. the minimum is 256 + header MB of kernel memory. also... you can run a system without pagefile, even, if it is stable and you don't consume more than what ram you got. the pages are just spare memory. should only be used in rare cases, cause it's slow memory and wastes the drive.
Oh boy, you really havent been following along have you? If you bothered to read the whole thread. OP already stated they removed their HDD/s, and increased the page file back in December based on your reply marked answered. Which they said fixed their crashing.
Now, since that has already been set. There is no need to increase it further just because they are adding a new storage drive.
To increase the page file on the other SSD would be totally pointless. Hence is why I said to not fuss over it.
Page file has multiple functions. Its to prevent programs from crashing when the physical commit charge is almost at its limit by moving infrequently accessed modified pages to a storage drive. Not just create crash dumps or error logs.
Since MSFT has made 64-bit OS streamlined since Win 7. Page file is really now used for logs and dumps. Because RAM is now so much greater than what it used to be with a 64-bit OS. Where before 64-bit the system RAM may have only had up to 4GB total physical memory. So by that. There really should not be a need to use a page file on today's systems but it is still required just in case and should be set properly.
If a user does need to use the page file, and they have 16GB of physical memory like OP. Than yes. It should be set high so other programs do not crash. MSFT recommends a min of 2GB for 16GB and a max of 48GB. Since 2GB is quite low I said to use 24GB so they dont have to really worry about the size and will have more room if needed. Set it and forget it. Especially since the drive is 1TB. So to use 24GB is nothing.
I have another computer that I used for gaming but mostly use as a server now. Its an AMD Ryzen 5 3600, with 16GB RAM, and a GTX 1080 Ti. Not once did I ever have issues with RAM allocation for the system, programs, or games. Because I maintained it properly and didnt let 14 years of programs hog up memory. Which is why I told OP to do a clean boot which would surely help them free up resources.
To sum this thread up. OP has removed their HDD/s, and installed the game on an SSD. Along with increasing the page file. Which helped their original issue of crashing.
To answer their new question some hours ago about increasing the page file on their other SSD. No, it is not needed.
so... game was already on ssd. page file allocated on ssd aswell. so it should be good. just in case the new ssd is a different sata version and is faster, the page file should actually be relocated to the faster drive for faster paging, when required.
and well... @animal i monitored the game since release day. and helped people make it run on "mediocre" hardware, for weeks. i know how it ticks and how it interacts with windows. and how trashy some windows versions can be with memory. resmon exposed that day one, when i compiled shaders and crashed in the main menu, mid compile. i said hello to emptystandbylist and still had to increase the page file, later. i dialed in the size over a couple days. if you don't have tons of background apps and close big consumers like web browsers it runs fine with 8 GB page pool. and i think i finished it the first time on 16 GB and this page pool. i don't remember exactly. but... i have "field experience". hmmhmm...
anyway... if no question need to be answered about the faster ssd, this thread should be put to rest now. yep. :)
I just needed to change the virtual memory on the d drive and reset the c drive to no paging.
Everything's good, everythings sorted we can put this to rest.
Hmm, I never had an issue with RAM usage in any Windows OS I used since Win 98. So not sure what you mean by that. As whenever I closed a program or game. RAM usage went down and was freed up by the system. You most likely just had too many programs open on boot that cached the memory.
Also, compiling shaders doesnt really effect RAM usage. It mainly affects CPU/GPU. That is why when they are compiled my RAM usage stayed at ~12GB used the whole time. When it was finished the amount did not go down or up. When in game it used the same as well.
As also shown here by others from these random youtube videos I pulled. RAM usage stayed the same even after shaders were done.
https://www.youtube.com/watch?v=0apFUCy0cfk
https://www.youtube.com/watch?v=YUwDPAZMhvs
https://www.youtube.com/watch?v=PH163ZdFLsI
Empty standby list is actually bad to use. Because every so often it removes the commited/cached memory. Which I think is every 5 minutes it does this or what the norm was to set it to. Which will cause slow downs and even possible crashes because other programs are using that cache or looking for free space. It will cause more issues that you do not want.
For example. You are playing a game, and that game is using 5GB of RAM for world data. Empty standby list comes along and clears it. The OS may think it just ran out of physical memory because a game that is actively using it is saying, hey, where did my cache just go. So windows may than decide to move things to the page file due to this conflict just created. So instead of using RAM, you are now using the much slower storage drive or cause a crash due to the confusion just caused.
If you were using that I can see why you had issues and still had to increase the page file. As when the memory was being cleared by empty standby list the OS was moving things back into it along with the pages needed to be cached again.
So it was probably having a pretty bad conflict during this time. So increasing your page file finally made enough head room to mitigate all the confusion being caused. You never want to clear memory when programs are actually running and using RAM.
If you crashed during shader compilation at main menu. Even before using empty standby list. It was most likely a heat or power issue with CPU or instability from the BIOS.
As almost all threads posted about crashing during this time fixed it by either swapping to a better cooler, or lowering clocks until it was finished.
Empty standby list is also no longer supported and very outdated software. Mostly used around Win 7. I would never advise anyone to use it. Even during its active lifespan.