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 if you want tram set to highest expect the memory usage to go thrrough the roof
that isnt a leak its just resource intensive ,
if set to " high" and it is releasing memory ,well there you go (it is not a leak)
keep it set to high as your hardware isnt suited for "highest" setting + Nvidia graphics options
i will point out not everyone has weird memory usage
mainly those with 32gb ram/large pagefiles set up
-
Moglet
Can you elaborate on the pagefile?
I have 5 Drives the SSD the game is on I set Pagefile to 16-32000, on OS SSD I set pagefile to System Managed and on one HDD that is mostly inactive I set a pagefile of 32000-32000
The HDD Steam is on has no Pagefile at all.
Is it important where the pagefile is? xD
Before I started Crashing the only pagefile I had was the OS SSD one, after searching the www I stumbled upon Pagefile, but haven't tested if it resolves my issue.
Also, also my RAM is around 70% Gigs used while playing and to my understanding Pagefile get's only used when the RAM is full?
it dosnt matter where the page file is
yes page file gets used when ram is full
all theNvidia settings you have on " turfworks" especialy cause HUGE tram usage
add in TRAM set to Highest and it is not suprising your Tram usgae is so high
even a 1080 is not enough (i have 2 1080's)
i wouls suggest you lower tram to "high"
and turn off turfworks and the other nvidia settings and test again
im almost positive you will have better results
Better results as in less likely to crash? Could that actually be the issue that I overtax Vram?
Due to the inconsistency I would think the real issue lies somewhere else.
I love the Turf effect though xD Will try it out and see if I crash with my pagefiles that high and should I crash again I lower TRAM and see.
for gtx1080 i reccomend tram set to high and remove the nvidia options for the test
plz do let us know the results it would be itneresting to see :)
Will test soon with High TRAM, can't give up on my Grass yet xD it's the single most prominent feature...
Still I managed to play for 3 Hours previously with TRAM Highest so I wonder what gives with the shorter intervals now.
I left my Settings like they where in the beginning of Video.
So I disabled my XMP Profile on my RAM (I read in a big Steam post that one solved it with that and I gave it a try since my Undervolted CPU was the first issue related to OC) and just played the game for 6h and 40 Minutes non Stop with no Crash.
After 5-6 Hours the game started chocking and dropping fps and stutter severly down to 20FPS Occasionally.
It eventually seem to have stopped doing that. Had Core Temp and GPU-Z running, nothing weird was showing there, and the Temps where normal/the same as before.
I further test this, but I hope the sacrifice in Ram speed solves the crashing... never again will I buy OC Ram and just RAM with basic Mhz to save money and trouble.
I also figured out that my i7-4790k Bottlenecks my GPU in this game.
CPU Load is around 80% with 47fps sometimes weirdly enough ~56 with 90%+ load
while the GPU is around 60-70% at the same time.
It crashed with the Increased Pagefile, so I don't know if Pagefile even is necessary at all, but I guess I just keep it will work now.
You really don't need to manually tweak Windows 10 anymore, outside of disabling the tracking and monitoring.
The game will use as much memory as it can use, depending on your available memory. Generally, for system memory, it hits between 9 and 12 GB most of the time. I have 64GB of memory on my system.
Unless it's consuming ALL of your memory, then filling your page file, high memory usage isn't an issue. It's a 64 bit application, so it's expected that it will use as much memory as possible.
Anywho, even with the older hardware, I've never had a crash and the memory stays stable, usually at around 6GB of usage. Would have never played the game if it actually leaked, especially with a battle like Omega or Adamantoise; first time around with Omega it took me over an hour and a half to finish (wasn't prepared for it at all). I'd have never come back to the game if it had crashed then. Thankfully, SE actually built a good engine.
As the end-user, unless there really was a glaring issue with the application, you'd be hard pressed to ever find a memory leak by merely looking at its memory usage via task manager. If that were the case, I'm pretty sure people over at SE would themselves notice and fix it. Just looking at the game you can tell they're more than competent enough to easily notice if they've got a problem with their memory management.
If you're crashing. first thing to check, IMO, is your thermals. If they're good then ensure that if you're doing any overclocking, that your settings (e.g. voltages, timings, clocks) are well set. If you're not, then next thing to test is your memory; slap memtest86 onto a bootable disk and give that a run. If that passes, then you're probably running into configuration issues with Windows, drivers, 3rd party apps and the like... Best practice is to just leave things alone; a fresh install, with minimal changes is the way to go. GL!
I solved that before I realized the Game still Crashes.
The Undervolting was made 4 Years ago where I built this Rig, my first PC, to reduce the Temps, which is a viable thing you can do. It only started to act up in AC:Origins and this Game while Prime did not run in a BSOD.
So yeah Prime is unreliable to test CPU Stability after all.
So the hopefully FINAL solution to the Crashing (RAM) was unrelated to the BSOD.