Here’s another thread hoping blizzard takes this seriously eventually.
Just the ones I got today alone
70F1DD0E-5382-4E3D-9651-5486CD06928D
EFF25F5A-C9BB-453D-849C-5042B1C6E2D2
AA80B11A-1E78-4205-82B0-482196F8BF6F
5EADE68D-8D63-4440-8236-0D4C238A362F
89E0EECB-9AAD-41C5-88E4-6C857AFA3B70
Can you provide a copy of one of your more recent Fenris reports?
Though I have a feeling I know what I will see in it.
Go to pastebin.com and copy/paste the text inside the file there, and it can create a URL that we can then view.
I hope I’m not distracting from OP’s issue, but I am having the same problem. I copied all lines in the “FenrisDebug” file up to a few minutes before the crash and pasted them here: D4 crash - Pastebin.com
Would really appreciate any help here.
Well a few things stand out here:
| I 2024.11.04 00:01:56.011933 481645 | [Sigma] — OS memory stats ----- |
|---|---|
| I 2024.11.04 00:01:56.012032 481645 | [Sigma] Virtual Mem Total: 38049.58 MB |
| I 2024.11.04 00:01:56.012139 481645 | [Sigma] Virtual Mem Used: 32893.50 MB |
| I 2024.11.04 00:01:56.012237 481645 | [Sigma] Virtual Mem Used by Process: 22286.00 MB |
| I 2024.11.04 00:01:56.012384 481645 | [Sigma] Phys Mem Total: 31887.46 MB |
| I 2024.11.04 00:01:56.012504 481645 | [Sigma] Phys Mem Used: 20144.04 MB |
| I 2024.11.04 00:01:56.012599 481645 | [Sigma] Phys Mem Used by Process: 7587.52 MB |
Your virtual memory total is showing its allocating approximately 6GB with the swap file. I would go in and manually set the swap file to 16384. (16GB). If you have plenty of drive space on your C: you can use 32768 (32GB) instead. Only use one drive for the page file, either C: or the fastest drive you have.
Instructions are found here, but use one of the page sizes above and make sure the same value is used for both Min and Max:
-Diablo IV has run out of memory - #103 by DTMAce-1687
As for the error, you did get the common Prism lost (GPU) that I see a lot. But this can be caused by a number of things, including not enough swap space, which I indicated above. It can also be caused by the driver in some cases. This is one of the reasons we keep going back to 561.09 with nVidia cards.
I seem to be missing part of the file though you shared. Usually there is a section that denotes what hardware, CPU, GPU etc. Did you only share a portion of it?
Its best if you can share the full file, that way I can review the hardware to ensure I have the right information. 
I believe this is the full report: D4 crash full - Pastebin.com
Yep, that helps.
E 2024.11.03 22:34:45.734094 0 [Game] [17-34-45][streamline][error][tid:28204][1s:384ms:374us]sl.cpp:668[operator ()] Feature ‘kFeatureDLSS_G’ requires GPU hardware scheduling to be enabled in the OS
Yeah, you should be running the GPU scheduling for the system in your display settings under Windows:
2070 Super. 1440p Monitor. Running 566.30
Like the other one I just looked at, you too may want to go back to the 561.09 driver. Also set an FPS cap of 60 to start with, you can always go a bit higher. I wouldn’t try going above 100 though.
And in your case, you could also use a 16GB page file change. Look at this post on the other thread for the links and details:
-Diablo 4 crash to desktop - #4 by DTMAce-1687
Both your system and theirs are similar with cards and setup. Both are running the game on SATA based SSDs, both are using the 8GB 20xx series cards, both are running 32GB but not enough Swap file set. Both are using 1440p and dual monitors, both have headsets.
So both may benefit from the above changes. Questions just ask.
Val, yours is essentially the same build as the last two I looked at…
32GB, 2080 with 8GB, even have the same kind of SSD - Samsung SATA based SSD drive, Using 8GB or less for the swap file, running the 566.30 drivers…
My recommendations will be the same as above.
Drop down to the 561.09 driver
Setup a 16GB swap file
Refer to the previous post for links to the tools if you need them!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.