I had this yesterday, spent 2 hours in the queue, got in for around 30 mins before beind disconnected, noticed how much RAM it was using and was like “thats not good” - to summerise, the game ate near enough 30GB RAM on my system
I had the same issue and a work-around for me is to increase the virtual memory of windows. I have 32GB RAM and set the virtual memory to 16GB respectively. Did a short system restart and tried to change the resolution back to high. I was standing afk in town for a while as well as going out of town and fighting some demons. So far no more disconnect or “running out of memory” message occured. Therefore, you should try to set the virtual memory to at least 50-75% of your installed RAM, maybe this will help you also.
1 Like
I resolved completly the issue by set my pagefile as “Managed by Windows”.
I set manage virtual memory by windows and no crash after 3 hours… usually happened within 30 mins. Seems to fix it for now.
Just to add on. I had so many crashes today and couldn’t figure out what the cause was. I even removed my Riser cable from the equation just to be sure. I believe I have found the solution.
My specs:
XFX RX 6800 16GB
R5 3600X
M.2 SSD x2
16GB DDR4 3200Mhz RAM
My Virtual Memory was set to 4GB per SSD, and this was clearly not enough for D4. I had this Warning in Event Viewer:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Diablo IV.exe (9060) consumed 13500731392 bytes, RadeonSoftware.exe (22324) consumed 470585344 bytes, and Battle.net.exe (4224) consumed 363700224 bytes.
If you don’t know where to check, search for Event Viewer, go to Windows Logs > System, and you should have a warning with above message after the crash.
I switched my Virtual Memory settings to System Managed size, rebooted, and Windows set it to 17GB.
If you don’t know how to change this:
- Hit Win+R to open Run
- Type sysdm.cpl and press Enter
- Advanced tab and Settings button under performance
- Advanced tab and Change button under Virtual Memory
- Set to System Managed size and click set
- Click ok and reboot PC.
When I look at my RAM usage in task manager, I have more or less 24/32GB allocated. This 32GB seems to be Physical RAM + Virtual RAM (Note that Virtual RAM and VRAM or Video RAM are different things). While playing D4, the 24GB seems to grow, and I have not encountered a crash yet, but haven’t been playing that long either.
If you switch your texture settings to Low and then back to Medium, the usage goes down as well.
Obviously the devs need to find a way to manage RAM better, but hopefully the above works for most people letting them play the game 
1 Like
The temporary solution for this is to enable a system-manged paging file. When the page-file is manged by the system, it dynamically scales in size as needed, meaning that a memory leak such as this one can page an infinitely growing amount of data to your SSD once your RAM is “full” (allocated).
The fact that the game crashes after 5 minutes with paging file disabled (as it should be for any sensible Windows user) is clearly a result of the memory leak. I’m not sure if the client is failing to purge old texture assets, or if it’s something related to telemetry, but whatever it is, my system is showing a LOT of writes from the client to my SSD - more than I would expect unless the telemetry is either crazy extensive, or there is a problem.
Actually it works the other way for me, Philmander. Fixed paging file (32768 MB = 32 GB) at least allowed me to start the game and play (out of memory error otherwise with system managed paging file). I have 16 GB of ram and diablo used like 8-10GB when crashed. System never auto-created paging file (as i keep it disabled most times). Maybe theres a problem when diablo tries to use virtual mem. (win10 enterprise 21h2)
UPDATE:
After 1h of playing i have no issues with the game. Memory usage - about 21-22GB total (including virtual). 5,6/6 GB VRAM usage with default settings, 1080p, runs smoothly with my old 1060 6gb.
Hello guys,
I had the same issue. To fix it i set my Pagefile to 40 GB Max, i was logged in and could play almost the whole day without an issue. I startet with the lowest graphic settings and i am now testing the highest settings with the page file set to 40 GB (so far no crashes either).
According to the Task Manager my Committed Memory was increasing slowly until it reached 30.9/ 36.2 GB on low settings and 32.7/37.2 GB on highest settings, then it stopped increasing and is now steady on those Numbers. Diablo 4 used constantly around 11-13 GB of my 16 GB RAM.
System Specs:
- AMD RYZEN 7 5800X
- 16 GB RAM 3200 Mhz
- AMD Radeon 6700 XT
- Game is running on an SSD with enough Space for the Page File (If that matters)
Please someone tell PezRadar and the tecs of Blizzard the MEMORY LEAK, is a heavy and gruesome issue, more important than the “queue”. Still with the same mistake at this minute.
1 Like
btw i figurred out that D4 usage is getting better for me, BUT 14 GB RAM + 3,6 GB system RAM and usage is showing me around 24 GB from my RAM…after closing D4 all is fine back to system 3,6 RAM…anyone else getting this?
The most annoying thing about all of this is that there is a hard requirement that it have access to a page file at all. I have 32GB of system RAM, so there is no reason for it spill over into a page file.
I’m playing at 1440p with max settings on a 3060ti and getting a smooth 120+ FPS. It does use 7.9GB of my 8GB of VRAM, but that’s not related to the system RAM, or the page file.
Looking at the logs, Diablo 4 starts writing to pagefile.sys once my system RAM commits 15.8GB - so there is some logic in the client specifically telling it to cache to the page file once it approaches 16GB of RAM. Now, there is no reason for the game to ever use 16GB of RAM, but even if it did, it should continue to use RAM as usual, not cache to your system storage. That’s bonkers.
1 Like
The vram usage is wild. I’m sitting at 7.5gb vram used with everything maxed out, dlss quality in 1440p with Low textures. Ram at 15gb.
i accidently pre order this game and gave it a chance because i dint mind it actually for beta but have the memory error can’t even play it since yesterday , lol get it together blizzard or close your studio down.
RTX 3070 AND 32M Ram with my VRAM set at optimal settings for win 11. Yesterday played great no issues before ya’ll did whatever to fix servers. Now Serious stuttering and then crash after being on. The last few hours constant stuttering every 20 sec0nds. So i turned all settings to medium and still stuttering. Then turned off sound also and its been playing with no stuttering.
I have 64gb of ram with a 3900x and a 7900xt and after 4 or so hours of play my system is taxed, using 61gb of ram. I’m on Win 11 with a 2 week old install and all drivers and updates… up to date.
Everything runs fine until then and it starts to stutter but not a ton. Enough to want to restart though.
Same for me,
MSI X570 Gaming Edge WiFI
Ryzen 7 3700x
RX 6800XT
32Gb RAM
File sent.
did you disable windows virtual memory? i fixed my problem by enable them and let window manage it
This usually occurs when you disabled “virtual memory”. Happens in other games as well, I’m not sure if it’s exactly the same issue but definitely try this;
Google; virtual memory set up
Very easy to do it, but click “let the system decide” option. Restart your pc and play.
same issue here new computer
| OS Name | Microsoft Windows 11 Home |
|---|---|
| Version | 10.0.22621 Build 22621 |
| System Type | x64-based PC |
| Processor | AMD Ryzen 9 7950X 16-Core Processor, 4501 Mhz, 16 Core(s), 32 Logical Processor(s) |
| BaseBoard Manufacturer | ASUSTeK COMPUTER INC. |
| BaseBoard Product | PRIME X670-P WIFI |
| Installed Physical Memory (RAM) | 32.0 GB |
| Total Physical Memory | 31.1 GB |
| Available Physical Memory | 22.6 GB |
| Total Virtual Memory | 34.0 GB |
| Available Virtual Memory | 21.8 GB |
| Name | NVIDIA GeForce RTX 4090 |
|---|---|
| Adapter Type | NVIDIA GeForce RTX 4090, NVIDIA compatible |
| Adapter Description | NVIDIA GeForce RTX 4090 |
| Adapter RAM | (1,048,576) bytes |
| Driver Version | 31.0.15.3129 |
| Resolution | 3840 x 2160 x 59 hertz |
The problem is that the usage of vram, shorts the life of your SSD. Why would I have to sacrifice my hardware because the bad optimization of blizzard