I had/have 100 GB VM on my NVme and had constant crashes this season at world boss events.
For me it was the setting of max fps that stoped the crashing.
Also 24+32*0,5=40 and not 48.
Maybe it could also be the nvidia driver, that i updated the day i started the season and updated it during the season.
Only my feeling is/was, that the max fps setting fixed it.
80% of the time when fighting world bosses, D4 runs out of memory. This is insane and so frustrating. Itâs clearly an issue with D4. I have ZERO issues with other games. Actually, Iâve had ZERO issues with every season of D4. This started in the new season for me.
Itâs not a RAM leak or a VRAM/Pagefile issue. Itâs a Corrupt Data on RAM issue being caused by improper CPU Voltage issues, which directly affects RAM stability. It took me way too long to realize and learn that the game isnât the problem. The back and forth between Intel/AMD and respective Motherboard Manufacturers and their auto shipped settings is.
Source?
And it wouldnât explain why this issue is in this season and not in these before. 3 ctd before season 8 at my side. 1 before season 1 and 2 in season 3 or so. More or less my fault, forgot that another game was allready running.
This season at the beginning, 10-15 ctd. Without other games. 
I donât really care if you fix it since I resolved my own issues. I offered advice based on many factors. Look into it or donât.
As far as it not happening before. RAM instability doesnât really function how youâre thinking. Itâs not going to be âperform x task, x task always creates condition for crashâ. Unstable RAM/CPU/Voltages can function fine, until they donât.
Calm down please.
You wrote, that the ram issue is not related to the game or itâs settings. That is a strong argument and you provided no indicators as proof besides âi say soâ. There was no âit could beâ, you wrote âit isâ. See the difference?
Motherboard Manufacturers set their own default settings, which are not in line with Intel or AMD specifications. This is to quietly âboost performanceâ and therefor selling points (we perform better). In response, both companies pushed Motherboard Manufacturers to release new versions of BIOS with their recommended settings. However, even these settings are not correct, because they do not take into account the power specs of the Motherboardâs themselves. Which means, in both scenarios the CPU is being fed either too much, or too little voltage causing random scenarios of instability. Not always enough to crash your system (BSOD) or harm your CPU, but because CPU and RAM Voltage are shared, it creates instability in the data on the RAM. This leads to the RAM filling up with corrupt data it canât seem to get rid of, resulting in what looks like a RAM leak, but is in fact just corrupt data. Another factor in this is Motherboard RAM Settings (XMP 1 vs XMP II). I is the Motherboardâs recommended RAM timings, while II is from the RAM Manufacturer themselves, again causing instability.
Also, I am perfectly calm. Iâm just saying that if you donât want to listen to me, donât. Thatâs on you, but nothing else so far has resolved your issue right? Do whatever you want.
Itâs the other way around. Most modern GPUs are way too fast compared to the CPUs powering them in their rigs. Diablo 4 isnât that demanding unless you leave the frame rate uncapped. What happens then? The GPU renders frames much faster than the CPU can handle. When the CPU is at 100%, stability errors happen at some point.
There are two possible solutions to the problem:
I think most people having these problems are using highend Nvidia GPUs with underpowered CPUs.
What he proposes can actually help in both scenarios, thatâs because either way it takes weight off of the CPU, which means steadier Voltage to the CPU and less chances of improper Voltage leading to Data Corruption in the RAM.
However, at the end of the day you should really fix your rig properly if youâre willing to invest the time to understand how. Youâll be thankful for it in the long run.
In electronics, you never want any component at 100% all the time. 80% is the gold standard.
As I wrote, I no longer have an issue. Iâm not the op.
But thx for the answer. Sounds interessting.
My game runs at about 40% GPU usage and about 20% CPU usage. FPS locked to 120, Graphics on High/Custom. Temps fluctuate between 40-60c depending on the scene. RAM usage stays steady around 16GB of my 32GB Physical RAM. VRAM at 8.5GB of 12. Rock solid, no crashes, no stutters, buttery smooth.
And yes I realize that RAM usage looks high, but itâs more using based on whatâs available, the game doesnât need 16GB dedicated to it.
Lastly, in case anyone was wondering no, I do not use a Custom Pagefile setting.
I have exactly the same problem and it keeps coming back since the release. The game has a ton of performance issues, although according to the requirements it should work on any bucket of nuts, including a microwave timer. I go into the game and after about five minutes, everything starts to groan in my system unit, as if an Alien was eating it. Then the game freezes and after about five minutes it comes back to normal and so on every 10 minutes. Sometimes all the memory is simply eaten up and only the reset button helps. Itâs very funny that this is the only game that has any problems at all. Even Cyberpunk worked better on release. Anyway, I deleted Diablo and now I have no problems. Let Blizzard continue to build games around a store with skins, instead of making games for people.
I have a pretty new rig, 64GB Ram, Gforce 5090 and I had the same issues until I disabled the nvidia Overlay and never happened again. I never had this before though, it happened only in season 8.
I hate to burst your bubble but as my system predates the overvoltage issues, that puts this squarely on D4. The logs confirm that. Corrupt data wonât result in out of memory errors, but instead will present assertions/exceptions.
The errors from D4 where the logs clearly state out of memory errors is in fact caused by hiw D4 handles texture swaps.
There are an increasing number of issues also pertaining to the ongoing Intel issues and AMD systems wirh >2 year old BIOS w/ X3D CPUs, but the issue in this thread is purely VM related.
AMD Ryzen 9 7900X 12-Core Processor 4.70 GHz 32.0 GB (31.1 GB usable) Itâs good system and I update drivers via Armory Crate and Nvidea all the dang time so itâs not my system. Itâs them and they donât seem to be able to or want to fix anything.
Drivers have nothing to do with anything Iâve mentioned. Best of luck to you though.
I understand they donât but my system runs with EVERY other graphic heavy game, it also is the same pc I use for my work which uses an extremely cpu, graphic heavy programâŚhence the reason I spent so much money on a pc. So, everyone can TRY to sway and twist this into being everyone elseâs issue except Blizzards. Seems strange that zillions of other players are having the same issueâŚis everyoneâs pc a worthless piece of you know what? No. And after the maintenance yesterdayâŚthe game intensified in the rubber banding effects and now you get stuck in the walls of nmdâs and anything else. Give blaming everyone else for Diabloâs horrible game state a rest; blame the programmers and Blizzard.
Guess my season is over. Came back and cant play more than 10 min without crashing. Just like the last 2 seasons.
Did you tried fps capping? Via settings or v-synch?