Question Adjusting paging file limits help.

instawookie

Reputable
Jun 13, 2021
184
26
4,610
Looking for some help with a single game issue occurring playing Red dead 2 , basically it says ERR_GFX_D3D_Deferred_Mem and it seems to be related to a virtual memory issue for this game in particular. The rig is a 14700k 32gb of ddr5 6000 and a 4090 so should have plenty of gas in the tank to run it. I've tried many solutions GPU drivers are up to date, Minimized back ground activity to running steam only basically, Adjusted in game to DX12 and made sure it wasn't on Vulkan etc... The main solution I've seen is adjust paging file limits, Currently everything has been set to Auto and it says I have 2048MB allocated to all of my drives, above that it says it recommends 4961. I did test it using custom allocation limits and setting all drives to 4961 and the game launched fine the first time, but reading around it says I could use larger values and recommends 1.5x my Ram capacity and no more than 3x my Ram capacity.

So I guess the question is am I slowing my machine setting my limit to 4961 like I did? and is there any gain to using higher values in the max limit for my ram capacity? I did run a benchmark through timespy when I set the initial limit and max limit to 4961 and it scored within 50 pts of where it normally does. I've also attached an img url to show you what I'm working with. https://ibb.co/DkL4CkJ

This is also the site that's throwing for a loop on paging file number size and makes me question my 4961 value, and if I should be running 65636 https://www.swooshtech.com/2023/05/09/solid-edge-page-file-sizes/

Thanks for any help or education in advance.
 
With 32GB there is no chance you are running out of physical memory on that game unless you are running TONS of mods and have tons of game loaders and other garbage automatically loading when you start Windows.

The first thing I'd do is go through your installed programs and get rid of anything you might have installed that you either really don't need or no longer use that might be starting with Windows and eating memory.

I'd also check to see that you have sufficient drive space remaining on any drive that might be used for virtual memory.

The next thing would likely be uninstalling and reinstalling RD2.

What Windows version are you running and do you have the latest Nvidia drivers installed?

Windows has been pretty damn good at managing virtual memory since the release of Windows 10 so unlike in the old days there really isn't any benefit to manually configuring a static or specific amount of it in 10 or 11. I doubt very much that is the problem regardless of the error you are seeing. It might be a symptom, but I believe the problem lies elsewhere.
 
Current driver is 546.29 and this was occurring on the previous driver as well. I'm also on Windows 11 23H2 that recently updated. As far as drive space all my drives have 250+ GB of storage available. As far as start programs, its pretty damn bare minimum this is my own build so any bloatware is stuff I only added. My running programs are Razor software for mouse/Logitech for KB/ Nvidia G-force experience/ Samsung magician/ Discord/ Steam. The game isn't modified either, I haven't tried a reinstall but the game just got installed.
 
I'm sure you've already searched for and tried the common solutions from the Google results, but I'll throw them out there just in case because surprisingly sometimes you get lucky and one of them actually IS the needed solution.

This link has MANY solutions, so it's worth looking further down the thread and not just as the first few posts.



Also, it should not be a problem if you DO want to manually configure the virtual memory just to see.

Simply uncheck the box for automatically manage paging file size for all drives, then select one of the other SSDs that has plenty of free space on it and then check the box next to custom size. I'd set it to maybe 8192 initial and 8192 maximum. That way it isn't constantly refreshing the page file with unnecessary writes. If that doesn't work you can try setting minimum to maybe 4096 and maximum to 8192.

Honestly though, with 32GB, the only way it should be using any virtual memory is for crash dumps, so I still think the problem is elsewhere, but it doesn't hurt really to try something simply so it can be eliminated as a potential solution. There is no way you should EVER need 1.5x your physical memory size. You should never need ANYWHERE NEAR your installed memory size. Page file should rarely see any use these days unless you run out of physical memory.

I'd install HWinfo, run it and choose "Sensors only" and with your game running look at the first section. See what it says for physical memory used, physical memory load, virtual memory load and page file usage.



KNzkvdZ.png
 
Last edited:
And for the record, virtual memory and page file are not the same thing. People, including myself sometimes when I don't catch myself, use the terminology interchangeably but they are not actually the same.

This post, is exactly right. Which is why I do not believe you actually HAVE a memory issue. It is far more likely that it is something else flagging that error.

 
And for the record, virtual memory and page file are not the same thing. People, including myself sometimes when I don't catch myself, use the terminology interchangeably but they are not actually the same.

This post, is exactly right. Which is why I do not believe you actually HAVE a memory issue. It is far more likely that it is something else flagging that error.

Thank you for the input and information provided, while it is frustrating to deal with just to play an older game, I do enjoy the learning curve and seeing something I never knew before. I'm pretty green when it comes to dealing with Ram/Virtual Memory/ Page file limits etc...

In good news, or maybe I got lucky on first boot. I created another steam folder on the same drive that my windows is on which is my 970 evo plus and the game booted up fine first try lol. While I prefer using my 980 pros for games if it works it works right? Doubt I would ever see any difference between the 970 vs 980.
 
BOOM!!!!

It just might be that you found the problem then. If recreating your folder on a different drive resolved the problem instantly, then it would be a VERY good idea to run some in depth health checks on that 980 Pro. You ARE aware that many of those drives had very serious problems requiring firmware updates just to not continue destroying themselves, right? And it doesn't fix whatever damage has already occurred, it just stops any further damage from happening. But even if THAT specific thing isn't the problem or isn't relevant, still doesn't mean it can't have some other regular old type problem.

 
BOOM!!!!

It just might be that you found the problem then. If recreating your folder on a different drive resolved the problem instantly, then it would be a VERY good idea to run some in depth health checks on that 980 Pro. You ARE aware that many of those drives had very serious problems requiring firmware updates just to not continue destroying themselves, right? And it doesn't fix whatever damage has already occurred, it just stops any further damage from happening. But even if THAT specific thing isn't the problem or isn't relevant, still doesn't mean it can't have some other regular old type problem.

lol yes sir, I do remember this. Headlines started popping up about 1 week after my purchase of both 980 pros and I have done all the firmware updates that had been provided. Maybe I'll use this as a sign to do more useless upgrades 🤣 . Time to do a z790 aorus master, Corsair titanium 64gb 7600, and 990pro swap I'm the sure the wife is gonna love that.
 
Yes, the Z790 Aorus master is a pretty damn good board. Much better VRM configuration than most of the other popular Gigabyte Z790 boards.

Might not be a bad idea too, now that you figured out what the actual problem was, to go ahead and restore your virtual memory setting to fully system managed or at least system managed for whichever drive you want it to use. I tend to not allow it to use the C: drive simply because I prefer it to not be creating unnecessary wear on my primary drive with unwanted writes to the drive.
 
Yes, the Z790 Aorus master is a pretty damn good board. Much better VRM configuration than most of the other popular Gigabyte Z790 boards.

Might not be a bad idea too, now that you figured out what the actual problem was, to go ahead and restore your virtual memory setting to fully system managed or at least system managed for whichever drive you want it to use. I tend to not allow it to use the C: drive simply because I prefer it to not be creating unnecessary wear on my primary drive with unwanted writes to the drive.
Yea I've went back and set everything to let Windows automatically handle it. I've put together 2 rigs the past month or so using the Z790 aorus master and master X board both make me a little jealous. I built my current rig last december and got the z690 Aorus ultra with memory for 199, its been a fairly solid board. It can be a little sensitive with XMP going past 6000 but overall find me a board with a digital debug port code for less than that price now days lol.
 
I've got the Aorus Elite AX and it handles my 12700k really well, but if that board hadn't been available for like 150 bucks at the time I'd have definitely gone with the Master instead as the direct/actual VRM phases are just too superior to the twinned VRMs for comparison. I may get a Z790 Aorus master myself at some point so that I can later pile a decent overclock on this CPU which I haven't done yet because I haven't felt a need to like almost all previous systems I've owned.