Technically they’re both the same thing. They can be called a swap file or a paging file but they’re both the same thing.
I thought swap was a smaller extension of the page… it’s been so long since I’ve messed with mine, getting old; just let windows manage since we have so much memory now-a-days.
Getting this stupid a$$ “unable to retrieve necessary data” error out of no-where and trying to solve it other than deleting the dstorage.dll files every time I want to play.
Tried like 100 different solutions and nothing is working and the freakin’ patcher just keeps putting the files back every time the game launches. Games playable, just GD annoying suddenly.
Dstorage.dll has caused other issues in the past too.
Ordinarily that is fine. But this is to just set a larger size and lock it to that size. The automatic method doesn’t seem to keep up with this for whatever reason.
You can use these instructions here, but use the value of 32768 for both min and max:
-Diablo IV has run out of memory - #103 by DTMAce-1687
There is a simple solution for that. You can directly disable Direct Storage from the game settings for Diablo IV in the launcher itself. You just hit the gear cog, go to game settings, and enable command line arguments. Then add this:
-disableds
That should fix that issue, no more needing to delete the DS dll files.
So I submitted 6 Debug files to support (2 separate tickets). Their response was “Check the forums for others that may have a fix”, or “Scan/Repair game files”, or “Reinstall the game”.
Garbage responses, I’ve got other games that I play that are way more intensive. 7 Days 2 Die is not optimized nearly as bad and it pushes my graphics card a lot harder, I can actually hear my 4080 super fans spinning up playing that game due to all of the enviornmental rendering that is happening. WoW is more graphics intensive than D4 and doesn’t cause any issues running at full ultra settings.
I thought about this also, I ran a lightning spear sorc last season in max gear, farming the crap out of everything. There is absolutely no way that my Spiritborn is causing more screen clutter, noise, or artifacts than my sorc was. Whatever this is definitely started up with Season 6.
Ran multiple benchmarks, free one from Unigine, not a single stutter, there’s no way this is a problem with my pc.
Unigine Heaven Benchmark 4.0
| FPS: | 138.6 |
|---|---|
| Score: | 3491 |
| Min FPS: | 44.4 |
| Max FPS: | 304.8 |
System
| Platform: | Windows NT 6.2 (build 9200) 64bit |
|---|---|
| CPU model: | Intel(R) Core™ i7-14700K (3417MHz) x20 |
| GPU model: | NVIDIA GeForce RTX 4080 SUPER 32.0.15.6590 (4095MB) x1 |
Settings
| Render: | Direct3D11 |
|---|---|
| Mode: | 3440x1440 8xAA fullscreen |
| Preset | Custom |
| Quality | Ultra |
| Tessellation: | Extreme |
I don’t think anyone is trying to say that exactly, but we might say there are things that can be done to get the PC to play it well.
Not what we should have to be doing any of it, but here we are.
Not us specifically, just the garbage responses from Blizz Support…
- Updating Windows and Graphical Drivers-
- Verify Game Files: Scan and Repair.
- Disable Background Applications
- Run as Administrator
- Adjust In-Game Settings: Lower in-game graphics settings
- Check for Overheating
For added troubleshooting steps, feel free to reach out to our Game exclusive technical support forums where Developers and Players alike share their input on several situations
And when all else fails, go somewhere else…
Should any of the above articles not solve the on-going situation, please consider contacting a local tech expert to perform a more in-depth analysis of your system and resolve any possible hardware or software issues.
When i play in Nahantu i crash. When i play elsewhere i dont
Yesterday I logged into my last season character to just get rid of some stuff, in Kyovashad and went into the stash, moved 3 Mythic Uniques into a different tab and immediately crashed out.
Ya it shouldn’t crash your machine. Mine is lower and I am not having issues. I also lowered my game settings. It is pretty widespread so there may be other issues. I hope it works out.
Error code crashed again
5E23DCEF-EC57-411C-8156-D4C606D31770
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.