Then follow the steps to setup your swap file. It should alleviate the issue, if not fix it outright. And it will give your system a small performance bump for other things. (not one you will notice directly, but it helps)
1 Like
Yes I did the specific setup for the swap file. I will test it from now on to see if the issue will occur again or not.
Thank you!
The way i read/interpret this message is that itâs not talking about your graphics card memory, but more likely about your RAM. Just curious how much RAM does your system have?
I have way too much RAM for any kind of game, so i have never had that message before.
Most computers are still only running 8 - 16 Gbâs of RAM. And when im playing D4, including the OS and some background programs, it says it has 21.8GB Ram in use. Of which D4 is using 9.4 GB.
So maybe upgrading your ram might be the solution for your issue. Or lowering your graphics settings. Especially shadows/textures/physics
I would advise against using a swapfile. Swapfiles are heavily dependant on the read/write speed of the drive its located on. Even with an NVME (m.2) drive, RAM is still the better solution. But a swap file is the âlow budgetâ solution.
1 Like
Thatâs not how VM works. Swap file space is your VM size. Thatâs the maximum amount of space your swap file(s) can take. VM page size is how large each swap file itself can be, with the maximum allowed being capped at the total virtual memory size. For this reason you ideally want your page size to be an even divisor of the total VM size. So if your VM size is 16384 MB, you want your page file size to be any of 16384 MB, 8192 MB, 4096 MB, or 2048 MB (the lowest Windows allows). Physical system RAM + total virtual memory allocation = total addressable RAM. On a system using Resizable BAR, which requires Above 4G Encoding enabled in BIOS, you should expect to set your total VM size 10-20% higher than without Resizable BAR enabled as that option allocates more system RAM to PCIe ROM/BIOS in system RAM by allowing more than just the first 4 GB of system RAM to be available to PCIe addressable space.
Ideally in a modern system you want your virtual memory size to be equal to GPU VRAM size + a minimum of 50% system RAM size. So if you have 32 GB system RAM and a 24 GB GPU, you want your VM size to be a minimum of 40 GB. You can, if need be, allocate up to 100% system RAM size + GPU size, but that will only be necessary for systems with less than 16 GB RAM, regardless of GPU VRAM size simply due to lack of physical RAM. This is why the old rule where you ideally had at least 2x system RAM vs. VRAM still applies. My current setup of 32 GB RAM vs. 24 GB VRAM goes against this and on a some occasions I can expect performance hits.
For the purposes of interacting with Diablo 4, your minimum VM page size needs to be at least as large as your total VRAM size. This is because unlike virtually every other piece of software on the planet, D4 dumps textures directly into VM instead of system RAM and letting the OS decide where to plop anything that exceeds the addressable space for physical RAM and if D4 decides to dump all textures from VRAM at once, which Iâve seen it do, not having enough room in a single page file for that can cause D4 to ârun out of memoryâ. For my 4090 that means my mimimum page size is 24 GB, meaning my minimum VM size is also 24 GB because you cannot have a lower VM size than page size.
In an ideal world, youâd have your OS, swap (where VM page files go), and games each on their own drives. However, you gain no benefit from such a setup on mainstream (i.e. non-EPYC/Xeon, or Intel HEDT X299 systems) because additional PCIe drives and all SATA drives go through the PCH, which ironically increases latency for VM use when using a dedicated swap drive. So it makes the most sense to have VM/swap assigned to the boot drive.
Fun fact: macOS dynamically allocates virtual memory and its page files are always 80 MB in size. For extreme VM usage you can see dozens, or even hundreds of page files on your boot drive. And you canât change that behaviour in macOS at all like you could back in the days of OS 7-9.
Oh, and the âD4 has run out of memoryâ is almost never due to being out of system RAM, itâs because it dumps so much into VM that it actually runs out of virtual memory to use.
2 Likes
Maybe thatâs the case. But hereâs how it presents:
If I look at the Virtual memory pool (committed) its a combination of both the Physical memory and the swap file size assigned.
That is how Iâm describing the virtual space. Its literally a total of both the physical and swap file combined.
Now, as an addition:
The other day I was testing for someone (this is unrelated to memory directly) the ability to group Battlenet PC players with Steam PC players.
And I was able to do so, that was answered. However I found out pretty quickly that 32GB of memory and 16GB of swap file with a 16GB video card was not enough to run two games simultaneously on the same system. I had to increase the swap file to 32GB and ended up with a 64GB Virtual space. (committed)
That worked, but you could see all the physical memory in use and even then there were performance hits.
I had left the space set at 32GB that day. Later I also noticed that while playing for over 2 hours last night, the VM hit about 40GB (committed) and hovered there. It would fluctuate maybe 1 or 2GB as you transversed different zones, etc, but it stayed around 40GB of total system usage. (that included the game, an anything else I was running including the OS) This is higher than it used to be pre-expansion.
I honestly think many of the problems people are having are directly tied to how much virtual memory they have, and the system isnât compensating fast enough.
So while the technical part of it may be described differently, Iâm describing it as it presents. Its a bit easier to understand if you are not as tech savvy. Thatâs all.
I was firmly in that camp prior to January of this year.
I ran this game with a 3070Ti, 32GB of memory and had the swap file disabled. Never had a single problem with anything.
Until.
I purchased a 4080 Super. This card has 16GB of memory vs the 8GB the 3070 Ti had.
Immediately after changing to that card, I was getting crashes and out of memory errors within minutes of playing the game!
Started to monitor the memory usage, found it was filling the Virtual memory and crashing, but I wasnât using all the physical memory. However the larger GPU memory demanded more virtual memory and the result was crash after crash.
So I enabled the swap file on the fastest drive which happens to be the OS and the game installation drive, set it to 16GB and voila! No more crashes, and the system was using between 32-36GB out of 48GB depending on what was running alongside the game.
Now Iâm running a 32GB swap file and seeing 40GB of usage as an average. So the expansion is requiring more VM.
I still cant play, have crash in game before login, and after that game close and bluescreenâŚ
It crashes non-stop after 1-30 minutes of gameplay and tried every advice in this thread without success. Itâs so annoying especially as i paid for the ultimate version of VoH.
Last one : 5ABFB898-7070-416F-83BA-37B4E4B57762
Thatâs Windowsâ wonky way of showing it. Just like it shows the CPU at 100% only once all cores are loaded instead of load % / # of cores like sane OSes do.
It isnât that it isnât compensating fast enough, itâs that D4 is dumping huge amounts of textures into VM. You can force this by doing nothing but pre-expansion zones for a while and then TPing into Nahantu. Itâll dump most, if not all of the textures so it can load Nahantuâs textures. This is why a user needs VMâs minimum size to be GPU VRAM size + at least 50% of physical RAM size. In my case that means the total VM size needs to be 40 GB, and since the page size needs to equal your GPUâs VRAM at a minimum, that means the page size needs to be 24 GB minimum for me. The optimal total for me right now is 48 GB VM size w/ a 24 GB page size. This way even if D4 dumps the entirety of my GPUâs VRAM into VM, it wonât crash the game client.
Youâll need to post this in the tech support forum and hope one of the support forum agents (SFAs) sees it as only Blizzard can see the internal logs generated with that crash report. Players canât since we canât get into their intranet (for obvious reasons).
I think itâs a vram issue.
I have bought ram, expanded up to 64 memtested, got bigger ssdâs everything, redid my windows 11 install.
The only thing that hasnât changed is my 3080.
Essentially we are in agreement, even if we donât agree on terminology. I know the specifics are different than how it presents, but lets be honest. Most of the players working with this configuration arenât going to be understanding all that anyway.
Right now, Iâm pretty much suggesting the following:
-
If you have 32GB or less memory and/or a video card with 16GB or more of memory, use a 32GB swap file.
-
If you have more than 32GB of memory, and/or 12GB or less of video memory, you can use a 24GB swap file.
-
But make sure both min/max are set to the same size. Make sure you use the fastest drive in your system. Make sure you use one drive only.
Thatâs pretty much it.
The page file size needs only to be as large as the GPU VRAM size, while also being evenly divisible into the total VM size (thatâs why with my 24 GB VRAM 4090 my optimal total VM size is 48 GB so the 24 GB page size is divisible into that VM size).
I donât think its that critical, but if it works for you, thatâs good.
Iâm trying to keep it simpler is all.
My VM size was 48GB, but when I tried to run two instances of Diablo IV, that didnât work so well. lol So I had increased it to 64GB. (32GB Swap file)
(I was running one Battlenet instance and one Steam instance simultaneously)
I donât need it that big, but I just left it at that setting for now. Has not impacted the system any differently though.
Incorrect. Had my page file with ample settings to run any amount of applications. Didnât matter. Changed it to normal windows controlled. Didnât matter. This is indeed a software issue with whatever Blizzard has coded.
1 Like
My husband and I have the exact same PCs, I crashed constantly every day since the expac came out, he has maybe 3x across the same amount of time. Definitely think it is software and not hardware personally.
so just buy a card with a bit more vram, where is the issue here? 6700 is only 12gb if i am not mistaken? better get an nvidia, you wont have any issue (apart from ray trac).
Yeah because throwing money at a problem fixes everything.
The only reason to change out hardware is if you are either:
- Having an actual issue with the current hardware
- Running on too old of hardware
There is no reason not to expect the game to run on a multitude of systems/hardware without having to be tweaked a LOT to play.
Sure, we can get the game stable if we tinker hard enough, but none of you should have to be doing ANY of this to this degree.
The only reason I make suggestions like the ones in this thread is because I want to see as many of you get to play as I can. But yes, ultimately there are some seriously finicky issues with this game, how it runs on hardware, how it uses the internet, etc.
And yes the builders of the game need to seriously look into some of these issues that keep haunting the gameâs performance and reliability. I can only suggest so much, and unfortunately, not every âfixâ will actually help every person.
1 Like
How does this work on a console? Does Blizzard cap the memory filing to make sure there is no overflow to a hard drive pagefile on consoles? Or did they use the pagefile on consoles as well?
So, for a system with 32GB system RAM and 12GB GPU, you need minimum 28GB VM size?
I can confirm this helped me, no more Out of Mem issues, no more crashing, nothing.
I gave 32GB of RAM and I used the 16384 Page approach on my Windows SSD Drive (C:)
1 Like
Yeah man, i honestly feel there is a serious optimization and cross component compatibility issue that is going on.
I hate to call it sloppy but that is what it feels like.
Sitting here thinking i need to upgrade a 3080 is not okay.