• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Close this thread please, it's old and tired :)

Status
Not open for further replies.
Tinek said:
Exactly same issues (same freezing for over 10 seconds now and then) I had in Borderlands 3 on 2070S (8GB vRAM) - after about 20 minutes of playing. It started fine, then the longer I played the worse it got. No such issues on 6800 as much more vRAM to play around. And BL3 doesn't have DLSS nor RT and I played it in 1440p to that - still caused issues.

Problem with people testing vRAM use in games is that they load a map, look around for a minute and say "Not a problem, works great, 8GB still enough!". But it often happens after a bit longer session of at least said 20 minutes, when game loads more assets and textures and starts chocking. I had FPS drops in few other games but freezes only in BL3, on that 8GB card.
That said, textures are the easiest and one of the best options to increase fidelity in game - it doesn't lower FPS as long as one has enough vRAM, hence can be increased in new games even on older cards, unlike RT or similar. However, with just 8GB vRAM it'll be the opposite soon enough - one will have to lower them to keep up proper FPS. :/
Click to expand...
yeah if this problem occurs at 1080p in 1-2 more games, i will decide to sell the card :( such powerful and good gpu hindered by such low amount of vram. i cant even comprehend
 
neur0maniak said:
If you're going to report issues about disabling the pagefile, it's helpful if you reveal how much system ram you have and it's utilisation.

Every program crashes if it runs out of free system ram without a pagefile.
Click to expand...

This.
The only game I have which hammers my 8GB of VRAM is Cities:Skylines at 3440x1440. HBCC memory segment helps (set for 12GB) smooth things out, but if I disable the pagefile, it's a straight CTD as soon as the game loads.
Reporting around 10.5-11GB VRAM usage, and total asset load of 25.4GB. This is with 32GB RAM.

So yeah, depends what you're doing. I don't think disabling pagefiles is a good thing to do, generally...
 
Ok, we've all at some point said disabling the page file is generally unneeded / and generally a bad idea, well done everyone :)

Should a game crash if vram capacity is exceeded though, given that not everyone has their page file set to 1tb? (yes I'm exaggerating)

The point - it's using the page file to make up for insufficient VRAM.
 
I'd be pretty confident in that your GPU isn't using the pagefile. GPU system memory is a very specific kind of allocation, it's different from how general applications request memory.

Isn't this all coming from some people disabling the pagefile then getting game crashes? Has anyone here reported a crash with an automatically managed pagefile?
 
Roar of the lion. 3070 starts of strong with 4k ray tracing at 55 fps. nice and cool, huh.
hVg6Y11.png



Let's run for 2 meters. oh no. new assets are loaded.
oQnoubq.png



no problem!! 4k 40 fps is still okay, huh? it's practically equivalent to a ps5 now. no problems. still fine!! oh what's over there, a couple of enemies, let me run over there to fight those nasty enemies...

oh no... oh no! oh no no no no! no problem though, cinematic 24 fps is cool and all. still fine, am i rite?

IPAWThu.png



and the final killing blow. no 3070, you cant provide cinematic experience in godfall, how dare you!!

9UzvUmG.png



---

notice the performance drop/shared memory connection. the more game writes to shared memory, more frames it drop. also notice that it does not stutter, does not hitch. it literally stays at those frames.

ahaha so funny to experience this already. card clearly can power 4k 60 fps in this game with rt enabled, but unable to do so due to its vram. :D properly scammed.

i'm joking, but this probably will happen at 1440p as well, in a very near timeline
 
If you turn off the page file (then restart) and lower the VRAM consumption to ~4gb (might be fine up to 6gb) by lowering texture resolution, the game doesn't crash.

This is really just a 4k resolution problem, at least in WD: Legion. I might just play at 1440p at the highest possible settings instead, as this cuts VRAM usage a lot.
 
Joxeon said:
Not that much different to the 6800XT 16gb RT on and in an AMD sponsored title.

Click to expand...
it stays above 40+ fps in the majority of time, 3070 cant literally stay above 20 fps at completely same settings. that card with a bit tweaked settings can easily lock to 60 fps in that game. whereas 3070 cant run away from vram issue at even with medium settings at 4k. ray tracing itself adds 4-5 gb vram and there's no saving grace for it, for this particular game

i can provide evidence if you want to, and those pictures are with high textures (not epic). at epic textures, 3070 literally goes haywire, at 10-13 fps (not kidding)

i know that game is very bad, (i enjoy it myself tbh) but it maybe a demo representation of possible ray tracing performance future of 3070. if 3070 does not have additional vram required for ray tracing, i guess it's point of having higher rt performance becomes nullified. up to now, it is fine, of course it had to be fine, because developers didn't have access to highe vram cards.
 
Last edited:
Is there actually any way of checking what data is being transferred to the pagefile? Maybe it's just textures, that get passed to the VRAM and RAM?

For WD 1, there a command to disable the page file (or render it inactive in most cases), which apparently improves performance significantly.

My understanding of the pagefile, is that windows can use it to temporarily store non essential / non time critical tasks while running games, like background tasks. But it's main purpose is to prevent crashes if physical RAM is fully utilized. Windows crash logs also require a small page file to function.

No one has really answered why the game crashes with the pagefile off, shouldn't the game entirely use RAM and VRAM, rather than the page file to avoid this problem (unless RAM is fully utilized).
 
Last edited:
Hardware unboxed put out a new video talking about vram during which they said that VRAM testing is difficult because in some games when you reach the VRAM limit your performance will drop or the game will crash, while in other games when you reach the VRAM limit the game simply starts automatically reducing image quality settings.

And so because of how games handle VRAM differently, it becomes very difficult to determine when a card is running out of VRAM over a large suite of games for testing because each game can have a different issue when VRAM is reached, there is no single measure that works for all games like framerate that tells you when you don't have enough VRAM as some people seem to believe
 
Last edited:
I'm going to check the VRAM usage in GPUz next during gameplay, you can set it to report the max VRAM used during a session.

I'm sure the amount calculated in game is just a rough estimate, cause the game can crash still at ~7gb VRAM set, so even on high textures + 4k + medium ray tracing.
 
g67575 said:
No one has really answered why the game crashes with the pagefile off, shouldn't the game entirely use RAM and VRAM, rather than the page file to avoid this problem (unless RAM is fully utilized).
Click to expand...

I actually answered that on the previous page already. With zero debug information it's hard to say with 100% confidence, but it's fairly easy to take a good guess at why it happens (the system is OOM).

What are you checking and what are you expecting to see? "RAM is fully utilised" probably doesn't mean what you think it does. If you're expecting to see 100% physical memory usage in take manger then you won't, the system will have run out of memory without a page file long before that occurs because the task manager percentage on the memory tab isn't counting everything.
 
[QUOTE="... It's just best to leave it on Auto size, as Win10 will use it only when it really must and will keep size of it as low as possible too. Some people seem to be still throwing around "hacks" from WinXP times, which simply do not apply anymore.[/QUOTE]

Yeah one of the first things I tried when I installed 32GB. Turning off the pagefile is a bad idea, no matter how much RAM you have...things fall over!
 
DarkBahamut said:
What are you checking and what are you expecting to see? "RAM is fully utilised" probably doesn't mean what you think it does
Click to expand...

Utilizing most of the physical RAM shouldn't be an issue (difficult with 16GB for a game anyway). The problem is, the game requires a page file (with some game settings enabled) not to crash for some reason.

I think some of the performance issues might be addressed when they release more DLC (they have a season pass for future DLC).
 
Last edited:
g67575 said:
Utilizing the physical RAM shouldn't be an issue (difficult with 16GB for a game anyway). The problem is, the game requires a page file not to crash for some reason.
Click to expand...

A game using over 16GB isn't difficult at all. I've seen FS2020 commit over 22 GB memory all by it's self, it's pretty common. That's before you add in windows and the various other components that all require allocations. 16 GB with no page file is really not very much memory at all by modern standards, nor has it been for many years.

The reason why the game needs a page file not to crash is your system is running out of memory. You can confirm it by looking in event viewer because the application crashes will be logged, and Windows logs OOM events too.

You can see an example here: https://i.imgur.com/fUzpisW.png

That machine has 56 GB memory (32 GB RAM + 24 GB page file) and that machine still ran out of memory while gaming. You can see how 16 GB really isn't all that much to play with and why you very quickly run into application crashes.
 
I just drove around for about 20 mins in game, system RAM usage topped out at 12.023GB on 4K, ultra textures, RT medium.

VRAM usage was 7947MB, so it looks like it was probably running at full utilization.

Weirdly, the stuttering issue didn't occur this time, gonna do some more testing.
 
Status
Not open for further replies.
Back
Top Bottom