Hello Blizz,
since yesterday afternoon D4 vessel of hatred crashing randomly - what’s wrong with your servers?
Nothing more than usual.
Care to provide more information? A copy of the Fenris crash log would be helpful.
here all my logs:
[_FenrisDebug-2.zip](https://1drv.ms/u/c/9e97ff9b81e53d55/ES_0CK6OodRBo6ngRts4GBYBhPOCEC0cgSG2s7032Rm8mg?e=flUntd)
Interesting. OneDrive flagged your file as having a virus and won’t let me open it.
Use pastebin.com to share your file contents. Just open the file, select all, copy and then use that site to paste it into, then create a new paste and share that URL it generates.
my onedrive have virus - don’t make me laugh
Wasn’t trying to.
It literally won’t let me open the file, says it contains a virus.
*shrug
I’m not taking any chances. You can share it on pastebin.com that will work fine.
What is your RAM size and what are your virtual memory settings in the system?
Run HWInfo app in a background (with log to file and save it on local disk) and launch Diablo. When game crush, check HWInfo log file or in app window the max value of virtual memory %, if it reaches above 90%, so, it indicates that you should increase it manually in system. You may find other devices values marked in red colour so that indicates another problem, e.g with too high temp of GPU causing a throttling system performance down.
In my case, the virtual memory size in Windows was too low, about 5 GB was managed automatically by Windows that most probably caused crushing the game. I changed these settings to custom option and then I was able to set manually the Initial and Maximum virtual memory size at least 1.5 times higher than my installed RAM size, i.e. 48 GB = 49152 MB and voila, the game stopped crashing, it runs even smoother, it doesn’t lag, or at least it is very rarely noticeable 
So, please check your virtual size and set it appropriately as reccomended by Microsoft 1.5 to 3 times higher than RAM.
Regards. In HWInfo app window, the Virtual memory usage (%) position was 99.9% shown in red text values colour, when game crushed, so, I have increased it and problem gone. No other red values in HWInfo.
Regards to all.
Device name DESKTOP-XXXXX
Processor 11th Gen Intel(R) Core(TM) i7-11700K @ 3.60GHz 3.60 GHz
Installed RAM 32,0 GB (31,9 GB usable)
System type 64-bit operating system, x64-based processor
BaseBoard Manufacturer Micro-Star International Co., Ltd.
BaseBoard Product MPG Z590 GAMING CARBON WIFI (MS-7D06)
System Model MS-7D06
BIOS Version/Date American Megatrends International, LLC. 1.A0, 14.10.2022
BIOS: 1.A0 (type: UEFI)
Edition Windows 11 Pro
Version 23H2
Installed on 05.12.2022
OS build 22631.4460
Experience Windows Feature Experience Pack 1000.22700.1047.0
Installed Physical Memory (RAM) 32,0 GB
Total Physical Memory 31,9 GB
Available Physical Memory 23,0 GB
Total Virtual Memory 79,9 GB
Available Virtual Memory 65,2 GB
Page File Space 48,0 GB
DirectX version: 12.0
GPU processor: NVIDIA GeForce RTX 4070 Ti SUPER
Driver version: 566.36
Driver Type: DCH
Direct3D feature level: 12_1
CUDA Cores: 8448
Resizable BAR Yes
Core clock: 2670 MHz
Memory data rate: 21.00 Gbps
Memory interface: 256-bit
Memory bandwidth: 672.06 GB/s
Total available graphics memory: 32700 MB
Dedicated video memory: 16376 MB GDDR6X
System video memory: 0 MB
Shared system memory: 16324 MB
Video BIOS version: 95.03.45.00.F8
IRQ: Not used
Bus: PCI Express x16 Gen4
This has been well documented on the forum here as a solution for some.
But you are setting to overkill. 32768 (32GB) is plenty for a swap as min and max.
Always use ONE drive and always set min and max to the same value to prevent dynamic changes which can impact performance. Exact steps for this are here from my post earlier this year:
-Diablo IV has run out of memory - #103 by DTMAce-1687
But use the 32768 value instead of what’s listed. The above was pre-VoH release.
Thank you for your response. Yea, you may be right, I was suggested in the article How Much Virtual Memory Should You Set? that I found in internet
The general rule of thumb is that you can set your virtual memory at 1.5 to 3 times the size of your RAM. So, [if your PC has 4GB or RAM], you can set the virtual memory between 6GB and 12GB.
It seems to high maybe, the rule is only general. I must test the game more days to see, wether it is too much or just fine. HWInfo should show me the max vbirtual memory used in % ruinning in the background and show me how much space is wasteing, and I be able to decrease its size more properly.
Cheers.
Well, that general rule of thumb they are quoting is antiquated from back in the early days of Windows 2000 and XP.
There is absolutely no need to be using 1.5-3x the amount of memory on modern systems. Considering today’s systems can have as much memory as an entire computer did for storage back then.
The rule of thumb now, is more along the lines of the more physical memory you have, the less swap file you need. However with Diablo IV, it seems the more memory the GPU has, the more you need to allocate despite how much physical RAM you have.
Someone with an 8-12GB of memory on their GPU can get by with less swap set than someone with a 4090 and 24GB, if both systems have the same amount of physical memory.
Anyway.
That’s been my take on it. And for the last decade and a half, I have ran my systems with enough physical memory that they actually had the swap file completely disabled.
It wasn’t till this current system that I had ever had to set a swap file. And that only had to happen after I had upgraded to a 4080 Super back in January as I was getting out of memory errors despite not using all the memory up. When I had a 3070 Ti that had 8GB, the swap file being disabled and having 32GB of system memory was sufficient to run the game.
But once the 4080 S got installed, that all changed. I then set a 16GB swap, and my problem was immediately resolved.
I had more recently expanded the swap to 32GB, not because of VoH, but because I was trying to run two instances of the game simultaneously on the same PC. Once from Battlenet and once from Steam. And yes, I was able to do it, but only after I increased the swap file size to 32GB.
Shortly after, the expansion launched and many people started having memory errors. I left mine set to 32GB and started suggesting to others to change theirs to fix issues.
And that is where we are now. The problem still remains (the game’s high usage of texture swapping and VM consumption) so having a swap file set is rather important.
The whole reason behind setting it manually and to a fixed size, is to prevent the system from trying to figure out what it should be and attempting to dynamically adjust it as it thinks it needs to. This has proven not to work out well and causes performance issues.
Anyway, that’s the thought process I have behind the suggestions for it.
I still maintain that this sort of configuring SHOULD NOT BE NEEDED. It’s ridiculous that we have to tweak and monkey with our systems this much for the game to run at all.
It would be understandable if you were trying to min/max the game performance. But not to just get the game to play properly.
Game on.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.