So what size should I set of pagefile for 8gb vram and 32 gb ram ddr4?
24576MB (24GB)
That should be sufficient. Make sure to use the OS drive only.
2 Likes
Ok, but I cannot use OS drive, not enough space.
Ooof.
Do you have a second SSD in your system? This needs to be on as fast a drive as it can be.
Might be time to upgrade the main one to a larger size.
Wait, the same drive not partition?
Itās a programming issue in the software.
Faulting application name: Diablo IV.exe, version: 2.0.2.58657, time stamp: 0x670748f9
Faulting module name: Diablo IV.exe, version: 2.0.2.58657, time stamp: 0x670748f9
Exception code: 0xc0000409
Something in the program is writing past the current stack frame, corrupting data on the stack. The program has detected this and rather than let it continue, has thrown an exception.
Iāve not had any crashes for this game until the VoH expansion. Along with the crashes, Iāve experienced heavy stuttering every few seconds in game without my resources being anywhere near its limitations or max utilization.
Specs:
Ryzen 7 5800x
64 GB DDR4
RTX 4070 Super
2 Likes
Please tell me you arenāt running multiple data partitions on the same driveā¦
But yes, if you have a partition with enough space on the same drive, you can use that.
But in the future you should not be partitioning drives, at least not on SSD drives.
Crashed to fenris after 2 h.
Blizz must be making some progress on this. Now when I crash it goes to desktop and I get the error reporter, no more computer restarts. And my crashes are less frequent. The first crash to desktop it said Diablo 4 had run out of memory but since then it just crashes and opens the reporter.
these random crashes leading to bsod suck i havent had much luck getting them to stop or improve. heres my fenrisdebug from the most recent crash
i have the same problem. but i have notice most time it during using town portals, kicks me almost every time. never happen before patch , same computer.
The same thing is happening to me. No warning. Just crash. There is no rhyme or reason as to when. It has happened during infernal hordes or parked in town. I do have suggested video settings enabled. Last season, no issues. This season, constant crashing every couple of hours. Last season I played Rogue. This season, spiritborn. I do notice in logs there is alot of missing cosmetic (spiritborn) errors. Not sure if a rank in battlepass would cause this error. If it stops when I max battlepass I guess its safe to say thats causing an issue.
Everything is maxed. FPS is capped at ~150
- Processor: Intel i9 - 14900KF
- RAM: 32GB DDR5 @5600 MHz
- Motherboard: Alienware
- GPU: NVIDIA RTX 4090
Try monitoring your memory usage while playing.
Specifically, you want to use the Task Manager.
Open Task Manager, then click on Performance, then on Memory.
Under here toward the bottom under the graphs, there should be a section labeled āCommittedā.
While playing, watch this part closely. If you see the committed in use amount get near the available amount (as an example, 30.3/31.8 GB), then you need to make adjustments to the swap file.
You can follow steps here, but use a setting of 32768 for your setup:
-Diablo IV has run out of memory - #103 by DTMAce-1687
Keep in mind, this has been helping some players, but its not a fix for everything. But if you notice your virtual memory (Committed) being filled up near the limit, you may want to make this adjustment to alleviate the problem. It will not hurt your system, other than require potentially more drive space on your C: drive. And be sure to only use one drive, do not put it on other drives or use a drive other than your OS C: drive.
As an example, when gaming D4, mine has been showing numbers of 36-38/63.8 GB
2 Likes
Framegen is disabled by Blizzard right now, thatās why itās throwing those messages. Itās not a misconfiguration, itās intentional at the moment; once the host is changed to enable it, itāll poll this again on launch and update as needed and allow them to be enabled.
For my own crashes, theyāve varied a bit.
| E 2024.10.14 08:04:33.102080 642499 | [Crash] Thread āSNOFilesAsyncLoadā handling fatal error |
|---|---|
| E 2024.10.14 08:04:33.102645 642499 | [Crash] UnhandledExceptionFilter |
| E 2024.10.14 08:04:33.102772 642499 | [Crash] Crashed thread: āSNOFilesAsyncLoadā (0x1428) |
| I 2024.10.14 08:04:33.102865 642499 | [Sigma] ā OS memory stats ----- |
| I 2024.10.14 08:04:33.102952 642499 | [Sigma] Virtual Mem Total: 49327.69 MB |
| I 2024.10.14 08:04:33.103035 642499 | [Sigma] Virtual Mem Used: 43764.88 MB |
| I 2024.10.14 08:04:33.103117 642499 | [Sigma] Virtual Mem Used by Process: 31728.70 MB |
| I 2024.10.14 08:04:33.103212 642499 | [Sigma] Phys Mem Total: 31893.89 MB |
| I 2024.10.14 08:04:33.103294 642499 | [Sigma] Phys Mem Used: 24348.39 MB |
| I 2024.10.14 08:04:33.103357 642499 | [Sigma] Phys Mem Used by Process: 11842.38 MB |
My latest was a crash with the renderer:
| E 2024.10.15 04:03:29.317330 585764 | [Crash] Thread āRenderThreadā handling fatal error |
|---|---|
| E 2024.10.15 04:03:29.317898 585764 | [Crash] UnhandledExceptionFilter |
| E 2024.10.15 04:03:29.318040 585764 | [Crash] Crashed thread: āRenderThreadā (0x6d8c) |
| I 2024.10.15 04:03:29.318138 585764 | [Sigma] ā OS memory stats ----- |
| I 2024.10.15 04:03:29.318224 585764 | [Sigma] Virtual Mem Total: 50368.84 MB |
| I 2024.10.15 04:03:29.318311 585764 | [Sigma] Virtual Mem Used: 43802.15 MB |
| I 2024.10.15 04:03:29.318402 585764 | [Sigma] Virtual Mem Used by Process: 31650.08 MB |
| I 2024.10.15 04:03:29.318504 585764 | [Sigma] Phys Mem Total: 31893.89 MB |
| I 2024.10.15 04:03:29.318591 585764 | [Sigma] Phys Mem Used: 24061.71 MB |
| I 2024.10.15 04:03:29.318676 585764 | [Sigma] Phys Mem Used by Process: 10716.82 MB |
Thereās nothing wrong with partitioning drives as needed by usage, SSD or otherwise.
Same here - every ingame interaction freezes around 1 min sometimes longer.
Nothing happens clicking on vendors.
Geez blizz canāt you do your job proper for once?
Heyday Blizz produces well polished games - not anymore.
1 Like
Your system uses a fair amount of your Virtual memory, for sure. Mine actually uses less, but it could be background things that are running. I donāt run many other apps or programs alongside most of the time.
But looking at that, you are within 6.5ish GB of hitting your VM limit and crashing.
I suppose for some cases there isnāt, but the point is, when you do that, you can handicap your space that you may not realize you need, which is what it sounded like.
I used to partition stuff back a decade or more ago, but I just donāt bother anymore when I can have multiple physical drives to accomplish the same thing. 
I am trying to dig into this problem, as it seems to be happening to a lot of you.
Heās just in the camp of those fanatics who donāt partition their drives. Thatās also an option, but itās funny how they make it such an important topic.
I donāt know that I would consider it being a fanatic. I just donāt see the point in doing it anymore. And I used to do it all the time many many years ago. *shrug
Has anyone looked into disabling āSoundā in the game? I disabled my sound and the game hasnāt crashed since (last two days, even while playing Evade build).
Interesting.
I donāt run the music in my game actually. Maybe I should? lol
Will try this when I go home tonight.