16 Gb VRAM and 32 Gb RAM not enough!

[Spam]

WTF, I have RX 6900 XT with 16 Gb VRAM (32 Gb RAM, R7 5700X3D), plays at 4K FSR Q no FG basically locks at 60 fps, and if I have runs Google Chrome while play the game It's crash with memory error at 13.3 Gb VRAM usage. Is it normal? NO!

[Nixxes_Community]

Out of memory crashes 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.

While we generally recommend that Windows manages the page file size automatically, there are documented cases where this can cause memory allocation errors. To troubleshoot this, you can fix the page file size.

You can find troubleshooting steps and more information here: https://support.nixxes.com/hc/en-us/articles/21441802890269-Video-Memory-Crash

[episoder]

Originally posted by Nixxes_Community:

Out of memory crashes 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.

While we generally recommend that Windows manages the page file size automatically, there are documented cases where this can cause memory allocation errors. To troubleshoot this, you can fix the page file size.

You can find troubleshooting steps and more information here: https://support.nixxes.com/hc/en-us/articles/21441802890269-Video-Memory-Crash

interesting. is this the same kinda behaviour as part 1? the day 1 shader compiler had the memory "leak" for 2 weeks. discarded memory pileup. a windows thing, afaik. i have the "janitor" running all day. page file of 8 GB should be enough safety for a craptop setup, right?

[Spam]

It seems that in Windows 11 the virtual memory function for non-system drives is disabled by default. In other words, if you install a game on a drive other than the system drive—which 95% of gamers do—when critical video memory thresholds are reached, an error occurs and the game crashes. After I enabled the virtual memory function manually, the crashes stopped.
Pin the thread or mark it so that other players also see it; I've seen several threads with the same problem and no solution was found anywhere.

[deranKING]

4K FSR Q will crash for me always on certain chapters - try dropping to balanced, it might mysteriously work...

[Spam]

Originally posted by sometimes orange:

4K FSR Q will crash for me always on certain chapters - try dropping to balanced, it might mysteriously work...

Because balanced lowering the resolution a little bit - 1260p instead of 1440p at FSR Q, so the VRAM usage is lower too.
By the way, I got my first crash after 3 hour session, not sure what cause, after enabling virtual memory game become much more stable with 13-14 Gb VRAM usage.

[sinephase]

The game uses a ton of virtual memory, I set mine to 64GB and it's still getting over 80% filled.

[d.vincenzo86]

Originally posted by Nixxes_Community:

Out of memory crashes 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.

While we generally recommend that Windows manages the page file size automatically, there are documented cases where this can cause memory allocation errors. To troubleshoot this, you can fix the page file size.

You can find troubleshooting steps and more information here: https://support.nixxes.com/hc/en-us/articles/21441802890269-Video-Memory-Crash

i dont want use file paging, my gpy have 16gb vram, and my ram is 32gb. please patch thi problem

[sinephase]

Originally posted by d.vincenzo86:

Originally posted by Nixxes_Community:

Out of memory crashes 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.

While we generally recommend that Windows manages the page file size automatically, there are documented cases where this can cause memory allocation errors. To troubleshoot this, you can fix the page file size.

You can find troubleshooting steps and more information here: https://support.nixxes.com/hc/en-us/articles/21441802890269-Video-Memory-Crash

i dont want use file paging, my gpy have 16gb vram, and my ram is 32gb. please patch thi problem

Yeah I suspect a lot of people who think they know better disable their virtual memory and wonder why they have problems.

"Windows itself also relies on the page file for certain system processes, like memory-mapped files, which don’t always scale with physical RAM."
"Windows is designed to use virtual memory as part of its memory management strategy. It preemtively moves less-used data to the page file, freeing up RAM for active tasks. Disabling virtual memory can force the system to keep everything in RAM, potentially leading to less efficient memory allocation and, in edge cases, slowdowns."

[emptyshell]

same here 32gb RAM 12vrm and same error so disappointing

[Dexter Morgan]

Originally posted by Nixxes_Community:

Out of memory crashes 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.

While we generally recommend that Windows manages the page file size automatically, there are documented cases where this can cause memory allocation errors. To troubleshoot this, you can fix the page file size.

You can find troubleshooting steps and more information here: https://support.nixxes.com/hc/en-us/articles/21441802890269-Video-Memory-Crash

Actually Nixxes, in your port of TLOU part 2 for pc, the game just crashes with a DX error when running out of VRAM. It does not touch my Page File at all. I know these crashes are VRAM related, because when they happen, your GPU driver resets. The game is either so VRAM heavy that it crashes before attempting to use the page file, or there's a memory leak somewhere in the game's code, and the game refuses to release used memory back into the memory pool. Either way, turning down LOD quality and Textures fixes all issues.

[Dexter Morgan]

Originally posted by Spam:

WTF, I have RX 6900 XT with 16 Gb VRAM (32 Gb RAM, R7 5700X3D), plays at 4K FSR Q no FG basically locks at 60 fps, and if I have runs Google Chrome while play the game It's crash with memory error at 13.3 Gb VRAM usage. Is it normal? NO!

AMD and Intel cards use 1-2GB more of VRAM for textures and LODs. This is why the issue is nonexistent on Nvidia cards. For the time being, either lower textures to high, or don't open browser tabs.

[WhiteSnake76]

Old rig at my Moms place:
R7 3700X, RX 6700XT 12GB, 16GB RAM, M.2 SSD's, Windows 10, everything maxed out, No Upscaling, No FrameGen, FSR Native AA, 1080p Vsync @60FPS no problem. (screen goes no further than 60Hz)

Main Rig at home:
R9 7900X, RX 7900XTX 24GB, 32GB RAM, M.2 SSD's Windows 10, everything maxed out, No Upscaling, No FrameGen, FSR Native AA, 4K Vsync @60FPS no problem.
Probably could get a lot higher FPS but my HDMI Receiver only has 4K 60Hz troughput.

Get crashes at random on my main rig, but hardware monitor doesnt show anything weird...

[WhiteSnake76]

Originally posted by Dexter Morgan:

Originally posted by Nixxes_Community:

Out of memory crashes 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.

While we generally recommend that Windows manages the page file size automatically, there are documented cases where this can cause memory allocation errors. To troubleshoot this, you can fix the page file size.

You can find troubleshooting steps and more information here: https://support.nixxes.com/hc/en-us/articles/21441802890269-Video-Memory-Crash

Actually Nixxes, in your port of TLOU part 2 for pc, the game just crashes with a DX error when running out of VRAM. It does not touch my Page File at all. I know these crashes are VRAM related, because when they happen, your GPU driver resets. The game is either so VRAM heavy that it crashes before attempting to use the page file, or there's a memory leak somewhere in the game's code, and the game refuses to release used memory back into the memory pool. Either way, turning down LOD quality and Textures fixes all issues.

If you got Xbox Gamebar installed just pust "Windows" key + "G" to bring up the Gamebar in Game, Pin the Hardwaremonitor somewhere its not covering a part of the HUD, Click on VRAM and watch, if its the VRAM filling up you see it no mather what, even if the whole system has frozen you can still see the last recorded data and the graph.

I bet its not VRAM or RAM but something else as wen mine crashes there is nothing weird giong on, i dont see a increase in CPU, GPU, RAM, VRAM or a drop in FPS untill the actual crash happens.
It crashes my GPU driver so bad that HDMI Audio no longer works (Dolby Athmos)
I have to go into the Audio settings, lower it to DVD quality, and than put it back on Dolby Athmos to get it to work again.

Could be a HDMI Audio issue, but... in 2 crashes the conversation went on with a frozen screen that went to black before the conversation stoped.
Most of my crashes happened wen a conversation was going on or a cut scene started.

[Zephyr]

Originally posted by episoder:

Originally posted by Nixxes_Community:

Out of memory crashes 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.

While we generally recommend that Windows manages the page file size automatically, there are documented cases where this can cause memory allocation errors. To troubleshoot this, you can fix the page file size.

You can find troubleshooting steps and more information here: https://support.nixxes.com/hc/en-us/articles/21441802890269-Video-Memory-Crash

interesting. is this the same kinda behaviour as part 1? the day 1 shader compiler had the memory "leak" for 2 weeks. discarded memory pileup. a windows thing, afaik. i have the "janitor" running all day. page file of 8 GB should be enough safety for a craptop setup, right?

TLOU part 1 also could crash when the pagefile was set to a small manual size. it needed a system controlled page file size or a large manual size. There are some games like this with a similar behavior believe it or not :).

[Vox Maximus]

Originally posted by Spam:

It seems that in Windows 11 the virtual memory function for non-system drives is disabled by default. In other words, if you install a game on a drive other than the system drive—which 95% of gamers do—when critical video memory thresholds are reached, an error occurs and the game crashes. After I enabled the virtual memory function manually, the crashes stopped.
Pin the thread or mark it so that other players also see it; I've seen several threads with the same problem and no solution was found anywhere.

No