The game is using 8gig+ of memory. Definitely a memory leak somewhere in the code.
And yes, my system MORE than meets the recommended requirements
Definitely an engine issue or memory leak, went to all low, memory would still creep up to maximum in time. Going back to max settings 4k, resets at 80%. I think a refund is in order, doubt they will fix this by launch.
As an update to my last post on this thread I’ve been back in and stable for an hour after lowering my textures/settings to medium. Memory usage is stable at approx. 16 GB of RAM of my 32 GB. No crash since the last one.
I also updated to the most recent Nvidia graphics driver, which was released on 14 March.
Hope this helps!
1 Like
Thanks for the update! I also made sure to update my nvidia driver and was able to reduce my settings to Medium, but I got another crash though shortly after loading in.
Same, when I switch to a ‘cutscene’ my (V)RAM usage spikes up to 100% on my machine.
from the logs:
| E 2023.03.17 19:52:25.873744 | [Game] [Prism] Out of memory when creating texture |
|---|---|
| I 2023.03.17 19:52:25.996427 | [Game] Trying to allocate Texture2D again after purging |
| E 2023.03.17 19:52:34.009302 | [Game] pm_dx12::Device::InitTexture: CreateCommittedResource Failed - Error : OutOfMemory, SystemCode : 0x8007000E (E_OUTOFMEMORY) |
| I 2023.03.17 19:52:34.009311 | [Sigma] — OS memory stats ----- |
| I 2023.03.17 19:52:34.009316 | [Sigma] Virtual Mem Total: 40744.54 Mb |
| I 2023.03.17 19:52:34.009318 | [Sigma] Virtual Mem Used: 40739.39 Mb |
| I 2023.03.17 19:52:34.009320 | [Sigma] Virtual Mem Used by Process: 29322.14 Mb |
| I 2023.03.17 19:52:34.009321 | [Sigma] Phys Mem Total: 32552.54 Mb |
| I 2023.03.17 19:52:34.009323 | [Sigma] Phys Mem Used: 15275.97 Mb |
| I 2023.03.17 19:52:34.009325 | [Sigma] Phys Mem Used by Process: 7693.95 Mb |
| I 2023.03.17 19:52:34.009326 | [Sigma] — OS memory stats end----- |
2 Likes
AMD Ryzen 5 3600 3.6GHz Processor
Nvidia 3070
16GB DDR4-2666 RAM
500GB SSD
Is my processor to out dated?
BUMP. This needs to be fixed ASAP. Chit crashes other apps with it too.
Does your reply improve the conversation?
I had out of memory multiple times. 
16 GB RAM, running the game on HIGH settings on 1440p.
I would have thought that the Virtual memory set up in the OS (extra 8 GB) would also help, but apparently, it does not matter somehow.
Closing up anything unnecessary (e.g. browser) should help as far as I know, so I’ll just take my advice and minimize the number of running applications.
1 Like
Is this related to VRAM as well? Not seeing RAM leaks yet, but on a RTX 4090 I was shocked to see 21/24GB of VRAM in use by the game. Toggling to medium textures instantly cut it in half, set it back and it’s crept back up.
Just adding for more visibility for Blizzard.
D4 memory leak. Used up all 32gb before crashing.
Possible temp solution here.
https://www.reddit.com/r/Diablo/comments/11tvsxa/massive_memory_leak/
Specs:
Vid: RTX 4080
CPU: Threadripper
RAM: 32Gb Dominator (DDR4)
Settings:
Highest @4K
1 Like
Memory leak here when playing on High. I makes it somewhere between 10-15 mins, Cutscenes seems to be the quickest way to crash
AMD 5800X with 5.02.19.2221chipset drivers
AMD 6800XT with March 7th 2023 drivers
32Gb RAM
Windows 10 22H2
2560x1440
Switching to medium resolved the issue and played for several hours no crashes or disconnects.
Early testing seem to indicate it is the Shadows setting. Dropped from Highest to high and was able to play longer.
My most common error is running out of memory.
NVIDIA GeForce RTX 3070, 31.0.15.3129 Drivers
Win 10 64-bit, 22H2, Build 19045
Intel Core i9-10900KF 3.70 GHz
32 GB RAM
All settings as low as they go with vsync.
I’ve put my texture quality on LOW and it drastically dropped to 7-8GB of ram used from my 32GB available. No more crashs.
It is an awful combination of both VRAM and Ram leaks that is the root cause of all the technical issues the game suffers from. Even Textures at medium can nuke my 12 GB VRAM.
AMD 5900x
32 GB @ 3600 CL 14-14-14-14
3080 Ti
1 Tb NVM e Gen 4
I don’t know if it’ll help with this specific crash scenario or not but i was able to fix all of mine by limiting my fps to 60. specifically I lowered the refresh rate of my monitor from 240 down to 60hz and then I turned on vsync which limited the fps to 60. Haven’t had a crash since
Game crashed after 1-2 minutes of gameplay with the following error message:
"Diablo IV has run out of memory and the application needs to exit."
CPU: AMD Ryzen 7 3700X
GPU: Geforce RTX3070 8GB (driver version 531.29)
Memory: 32GB
Antivirus: ESET Internet Security 16.0.26.0
OS: Windows 11 Pro 22H2 22621.1412
As the recommended memory is 16GB (minimum is 8GB) it’s a possible memory leak bug.
Temporary workaround was to change the game settings to low.
I have the same issue… My game does not crash however…
Even in menu it uses 12gb of vram out of 16gb… and 15gb system ram out of 32gb…
Not to be that guy but thought I would post in case it helps any. I played both friday and sat all day long and crashed once in like the second hour the server opened and that was it. I do not recall any error code, the game just crashed.
I have a 5800x
32gb ram
1080ti 11gb vram
2 tb nvme (for games only game is installed here)
windows 10 22H2 build 19045
game is set on high
max fps in foreground was set to 150 and the next setting below it set to 8fps, I just changed that 150 fps to max at 70 fps
Playing on a 1080p 60hz tv, I checked via task manager and it shows my ram usage was at like 20 gb/32
Just to keep this alive for this next round of testing.
On system A under windows 10, I would crash every 5-10 mins when playing on High graphics setting with an error of out of memory. MSI Afterburner would show me hitting 32GB in use + the 16GB of Vram in use. This was at 1440P
Same system booted under Windows 11 22H2, Stayed around 22GB of memory use and no crashes.
A 2nd system running windows 10 with 32GB memory, but a video card with only 8GB of Vram, did not crash, though it had stutters as it seemed to be hitting the pagefile a lot. This was at 1080P
Both systems are AMD with AMD video cards running the AMD March 7th video drivers and March 3rd chipsets drives. Will be interested to see if the problem is still there. since I saw a software update applied today.