That’s the 100 dollar question.
My guess is, when its important enough to finally address. At the moment, there really hasn’t even been any acknowledgment of a problem, much less a timeline of addressing it.
All the more frustrating.
1 Like
Are there any long term negative effects of increasing your page file size? This fix worked for me throughout TVOH but in December I started experiencing blue screens with lots of other games. It was repaired but not sure if the issues were linked.
I just started Season 7 after reinstalling Windows in December and just got my first blue screen without the page file increase fix. 
No.
If anything its a performance bump for the system as a whole. The problem you are describing may be unrelated.
So that would confirm it.
Blue screens are typical of a couple potential issues:
- Severe driver/OS conflicts or software conflicts
- Memory errors (with the RAM)
- Other hardware errors, including heat related, power related, or just plain going bad
Great, ill just increase it again as this worked for me throughout season 6 thanks to your help.
1 Like
I tried the solution in post #101 but didn’t solve my problem. I even tried 32 gb but no luck. I have a 2080 Super. I think it has 8gb of ram. Should I try 64gb swap file size?
No.
If increasing it to 32 didn’t help, any more won’t either.
Go to the tech forum and create a thread on your issue. Be sure to provide a copy of the FenrisDebug file (latest one for your most recent crash). You can use pastebin.com to share it.
I solved the issue with the game out of memory on my computer. I don’t normally have a large page file set because I have a lot of RAM and VRAM. 32GB, 24GB to be exact. However, once I changed the page file to system managed I see what the problem was. Between The GPU, MB RAM, and Page-file the game needs 80GB for loaded assets and shaders.
Page File is based on your storage drive / hard-drive. You can set it to any drive with space. Based on playing with 24GB VRAM you need an additional Page File of 42GB on the highest settings. To change your page file;
- Right click the windows icon then left click system.
- On the next page click “Advanced System Settings”.
- Then under the "performance section click settings.
- On the next window click the Advanced tab.
- Then at the bottom click change in the virtual memory section.
- I recommend setting it to system managed size on your main C: drive but if you don’t have room and have an acceptably fast second drive you can do it on that one instead.
- Reboot the computer for it to take affect and give it another whirl.
- I recommend that you have at least 50GB of space on the page file drive as it will dynamically size as you need it.
Now that that is fixed the game runs like a dream on the highest settings with my 7900XTX at 1080P. Still odd that the game itself only uses 50% of my physical RAM on the motherboard. I would think they would want to use as much of that as possible for its transfer speed alone. I think its more that current day game developers dont want to manage memory very well, its why consoles have so much RAM.
So the issue is out of memory but that’s because they are not using the primary motherboard RAM they are using the GPU VRAM and Page-File. I suspect other have insufficient page file allocation or the main drive doesn’t have sufficient room for the game to load this much into the page-file.
I’m going to adjust your post a bit, just so we are on the same page:
First off, in this very thread is this post by me a while back:
-Diablo IV has run out of memory - #103 by DTMAce-1687
Keep in mind, this was posted last year, before VoH dropped.
At this time, my most common suggestion is to set a 32GB paging file. That is sufficient for most setups.
Now. Those with 24GB or more on the video card AND less than 32GB of memory might want to set this to 40GB at best.
One thing I won’t suggest, is splitting the swap file across multiple drives, which I think we are on the same thought.
But yes, this game will eat swap memory. Windows automatic management settings just simply won’t allocate the space accurately or fast enough to compensate.
Your total VM space (committed) in task manager is the combination of your current swap file space and your physical memory installed.
Yes we are on the same page. My sizes given for how much you need are approx. This is why I suggested everyone use system managed and ensure they have around 50GB free space on the Page File drive chosen. Some people run separate game drives. Works great when you reset your OS and don’t have to redownload games. In those conditions the user might not have sufficient space on the main C drive. Which why I suggested that move it to an alternate appropriate faster or comparable drive if they have one. I would not recommend splitting the swap between drives either.
This sucks because it doesn’t use all of your actual MB RAM which is fast faster than most M.2 NVME drives. However, I just had a thought about RAID setups for swap to increase performance, but that’s for another discussion. Seems that D4 isn’t the only game doing this. The new Monster Hunter game is too of which I dropped the same post and people are saying it fixed everything for them. Where as before it would black screen and crash when you tried to enter the game.
I’m really surprised no one in either game development department knew this or posted it to the users. Kind of sad when they produce a product they don’t even fully understand themselves. Even worse to think the game takes up 80GB, correction 122GB of drive space and then needs another 40-60GB of swap which is not listed ANYWHERE on anything. Its obvious they took the easy route of Page-File instead of properly allocating more physical RAM. Its more difficult in coding so I get it but dang this issue is like years old, and now newer with all those that bought the XPac.
Blizzard if you are reading this let me get that ultimate upgrade for free for services rendered. 
Except.
I don’t suggest this, at all.
The reason is, the Windows system doesn’t compensate fast enough.
That is why I highly suggest setting it to a fixed size (by setting both min and max to the same value) providing you have the drive space.
On that front, when using an SSD, you want to keep those drives no fuller than 60-70%. More than that, can actually hurt the system overall performance when those drives are trying to use their wear leveling features.
1 Like
Agreed. Both very good suggestions. However, some non-technical individuals might not remember they did that and cause other issues by the swap not shrinking back down when not in games.
Yes the 50% SSD full is a real thing. I have a Samsung 990 PRO that loses 1/3rd its peak speed past 50% full. Kind of cheapy of the advertisements on these things these days.
1 Like
What issues?
There are no side effects, outside of space use.
1 Like
Yeah, I guess its not really a huge deal but working in IT engineering I have seen non-technical users do some wild things. I try not to recommend “permanent” changes such as this to prevent the possibly that someone dumb proves me wrong and finds a way to screw it up.
Well, I’m basing my opinion on the settings based on my 30+ year in the field, so its not going to harm anyone’s system.
Typically I used to run my systems with plenty of RAM and no swap set at all. Most of the time you don’t need them.
In fact, I used to play Diablo IV after launch with no swap file set. It worked fine, till I upgraded to the 4080S and started getting out of memory errors, because I had no swap file space since the game demanded more VM.
So I had set a 16GB fixed one. That fixed the issue, till more recently when VoH dropped. I had to up it again.
1 Like
Same, my page-file was hard set to 100kb. I stumbled upon the fix troubleshooting the Monster Hunter Beta release. So I gave it a whirl on D4 as well with the XPac and worked great so I figured I would share since it couldn’t directly find this suggestion in my 20 min of searching. Sorry I didn’t see your post. Wish they had a button for mark as solution.
1 Like
lol yeah, that would be nice.
1 Like
didn’t happened to me before… and Now it got me
For me modifying the swap file didn’t work at all. My game crashed randomly every few minutes whatever I did.
The newest NVDIA driver seems to help a lot and, if the game crashes (much more seldom these days), I delete the LocalPrefs file from \Documents\Diablo4.
This way, for the first time since the DLC launch, I can play few hours sessions without crashing.
For anyone that changed page file to a set limit, but are still running out of memory, are you running the -disableds in the command line to disable direct storage?
Those two things aren’t linked, FYI.
My page file is set and the Direct Storage is disabled, but I’m not running the command.
In fact, I’m not sure why Direct Storage is disabled in my case. lol
Not that it matters, mine has been running fine throughout the entire time.