Found the reason why vram usage error comes up.

[IchigoMait]

It's because of paging file aka virtual ram, not vram aka video ram.
I had used overprovisioning on my ssd, aka it creates unallocated space at the end of the partition, but it took that from the partition that had my paging file and search index, so had to increase the partition again to what I had before.
So yeah either get 32GB DRAM or increase your paging file partition to till you have in total 32GB RAm or so, then you can max out the game.
For some reason 16GB DRAM and 10GB or below page file wasn't enough for this game when going for the highest settings.

[p R o X y m o R o N]

Thanks, I ran into the same crap today.
I'm running it on an SSD which I also set up with overprovisioning enabled...my takeaway from this is clearing up storage will solve the issue?

[Nixxes_Community]

This error can occur on systems with high-end hardware, when the Windows page file does not offer enough space to allocate VRAM budget. We recommend letting Windows automatically manage the virtual memory size.

If you have an older computer, a low-end GPU or laptop, this crash might occur because the available VRAM and system memory is not enough for the selected graphical settings. Choosing a lower resolution, a lower graphics preset, or tuning the settings to lower the video memory usage can help in that case.

More details here: https://support.insomniac.games/hc/en-us/articles/8397966739341-Video-Memory-Crash

[IchigoMait]

Originally posted by p R o X y m o R o N:

Thanks, I ran into the same crap today.
I'm running it on an SSD which I also set up with overprovisioning enabled...my takeaway from this is clearing up storage will solve the issue?

Just make sure to have enough page file (virtual ram), I also set it to be at 15000-15000MB. Overprovisioning itself is basically having unallocated space after the partition of where you have page file, if you do it manually, then ssd software will detect that you have overprovisioning (dunno what the min amount is for it though).

So far I haven't had a single crash anymore.
When my page file was too small, then it was prone to crashing, and if the page file didn't have enough space to expand, it wouldn't even boot up on medium settings (dunno about low, very low was able to run).
Now I can enjoy my game with RTX enabled (high won't bother), just have to make sure texture quality is not at max, otherwise 8GB gpu ram (video ram) won't be enough.

The only minor annoyance in the game is that no matter what settings I use rtx or not, min or max whatever else, reflection distance is too low, it always pops in suddenly from mid distance, it ain't gradual. No reflection, and then suddenly full on reflection, but it's only for some random stuff, mostly small and narrow stuff that have reflective surface. Otherwise reflection is okay for the rest of the stuff, for big surfaces.

[IchigoMait]

Originally posted by Nixxes_Community:

We recommend letting Windows automatically manage the virtual memory size.

That's is a bad suggestion as that leads to random crashes, windows doesn't know ♥♥♥♥ how optimize it for games, hags is useless, game mode is useless. While ironically hags is needed now for dlss 3.0. (hags is useless because in most cases it does nothing, in some very rare cases you get up to 10% performance gain, but in some other rare cases your performance drops by 50%, or if it does something in a minor way, it just increases the min and max fps range, aka min fps gets lower too).

Anyway paging file doesn't consider how much dram you have, so system managed is pointless, plus if you don't have enough free space, the result is the same as not having paging file.
So you have to manually adjust this, and the last time I managed it manually was for Spider-Man 3, because the audio would cut out because of not having enough dram, so increasing paging file was the fix.

Point being data streaming is badly managed in this game. Only other game that had such serious issues was an adult chinese 3d game, first time it launched was fine at max settings, and later on after few patches, you could only get it to run for new game on lowest settings including resolution, and if you wanted to load the save file, it was literally impossible, and some peeps found the fix by on their own, by manually adjusting the game config files.

I was the one who forced nvidia to fix Monster Hunter World nvidia profile, because they themselves aren't capable of finding obvious performance losses where the fps drops by 3 times. And the fix was just disabling some unknown profiles through nvidia inspector, as I can easily see the difference from default settings, no idea why they even bothered making those settings, when they didn't bother to test it in all game areas where you spend a long time playing.
That is my way of finding a solution when someone says this nvidia driver sucks compared to the previous one, I don't go back to the previous one, if I can just fix the one game having the issue, and risk losing all the other performance benefits from any other game that was released for the newest game ready driver.

[-0.0001x]

yeah its weird. i usually have 2-3 gb free on my ssd, game crashes, i delete some games, free up ~10GB, then game runs okay again...