Like some other players, I’m also experiencing these once in a while. Been happening since Season 6. Never had this issue prior.
Fenris Log here.
I 2025.01.21 23:23:00.139874 0 [Game] DirectStorage: Enabled
You have a WD (Western Digital Black without heatsink) SSD here. Its possible that your SSD and this game using Direct Storage may not get along. It is also possible there is a firmware update for the drive. You may want to visit WD here to check for this:
https://support-en.sandisk.com/app/products/product-detailweb/p/1534
You can obtain the software to check the drive here:
https://wddashboarddownloads.wdc.com/wdDashboard/DashboardSetup.exe
What is weird to me is this that I see on some AMD based GPU system builds:
E 2025.01.21 23:23:02.938648 0 [Game] [18-23-02][streamline][error][tid:6008][1s:003ms:920us]sl.cpp:668[operator ()] Feature ‘kFeatureDLSS_G’ requires GPU hardware scheduling to be enabled in the OS
Now. Your card doesn’t use DLSS, so I’m hoping it isn’t being enabled, even though the game is looking for it. That said, you really should be running GPU scheduling for your card.
You can turn that on following these steps:
Windows 11:
GPU scheduling is enabled in your Windows settings under the Settings → System → Display → Graphics → Change default graphic settings.
You are getting a lot of these errors in the log as you play:
E 2025.01.22 00:57:00.389722 745093 [Game] The user 0 appears to have a bad pack container id 7fffffffffffffff E 2025.01.22 00:57:00.438732 745100 [Game] The user 0 appears to have a bad pack container id 7fffffffffffffff E 2025.01.22 00:57:01.056514 745188 [Game] The user 0 appears to have a bad pack container id 7fffffffffffffff E 2025.01.22 00:57:01.322758 745226 [Game] The user 0 appears to have a bad pack container id 7fffffffffffffff E 2025.01.22 00:57:01.357618 745231 [Game] The user 0 appears to have a bad pack container id 7fffffffffffffff I 2025.01.22 00:57:24.812023 748529 [Game] Application Deactivated. Active: 0 Minimized: 0 I 2025.01.22 00:57:28.291099 749025 [Game] Application Activated. E 2025.01.22 00:57:32.484792 749607 [Game] The user 0 appears to have a bad pack container id 7fffffffffffffff E 2025.01.22 00:57:32.853382 749657 [Game] The user 0 appears to have a bad pack container id 7fffffffffffffff E 2025.01.22 00:57:33.150159 749697 [Game] The user 0 appears to have a bad pack container id 7fffffffffffffff E 2025.01.22 00:57:33.538423 749752 [Game] The user 0 appears to have a bad pack container id 7fffffffffffffff E 2025.01.22 00:57:33.587380 749759 [Game] The user 0 appears to have a bad pack container id 7fffffffffffffff
I would explore the first thing I suggested, check the firmware of the drive and possibly disable Direct Storage if updating the firmware doesn’t solve it.
You can disable it using this command line option in the launcher settings:
To access the settings you do the following:
- From the Battlenet App game page for Diablo IV, click the Gear Cog to the right of the play button.
- In the menu that appears, click on Game settings.
- On the next page, you should have an option for Additional command line arguments. Click the check box to enable.
This command disables Direct Storage for this game:
-disableds
But only use that if checking for an SSD firmware update doesn’t help. And make sure if that drive has any critical or important data on it, that you back it up prior to the firmware update using the WD software.
1 Like
Thanks for the reply. Going through it and checking things one by one.
- Checked my WD drive’s firmware via the WD dashboard software; it’s already at the latest (111110WD) unfortunately.
- I don’t see “Change default graphic settings” in Graphics, and no mention of GPU scheduling. However, my 6800 XT should be able to support it, according to Google, and my drivers are up to date. Not sure if it’s on AMD’s side or Microsoft’s side that the option doesn’t show up for me.
- I don’t have Resolution Scaling enabled in-game; it’s set to off, and the drop-down doesn’t even have DLSS as an option, so I’m really confused why the game is looking for it.
- Alright, I added that command line argument. Will be testing tomorrow and see if that fixes it.
I wonder if moving my Diablo 4 installation from my WD Black NVME to my Samsung NVME would fix the issue.
I might also look into using that GPU driver cleaner and try to remove any traces of Nvidia on my PC (if any exist) to see if that stops the game from looking for DLSS.
What version of 11 are you running? You need to be on 22H2 or newer.
Possibly. I have also suggested for a couple others that they could setup a swap file. Your system looked to have some space there, but it might not hurt. You could set it for 16 or 24GB. Here is a link to the instructions for that:
1 Like
I’m currently on Windows 11 24H2 (Build 26100.2894). I think it may be an issue with AMD’s drivers possibly. Using the latest one, though - 24.12.1.
Interesting. I don’t have a ton of experience with the AMD cards in recent years, but may need to try to remove and reinstall the driver, or go back a version?
1 Like
Yeah that’d be my next step if the issue happens again. For now, though, I did:
- added command line arg to disable Direct Storage
- changed my pagefile from 5GB to 16GB
- used DDU in safe mode to remove any traces of Nvidia
- ran DISM and SFC just to make sure my Windows OS has no issues
Gonna see if the issue happens today. If it does, I’ll resinstall my AMD driver and try moving D4 to my Samsung NVME.
EDIT:
Just happened again today after playing for maybe 30-40 minutes? I was in the middle of an area, opened the map, and wanted to teleport to a waypoint to continue doing a headhunt somewhere else.
I can confirm that DirectStorage was disabled for Diablo 4:
I 2025.01.22 13:16:38.240990 0 [Game] DirectStorage: Disabled
It’s also still trying to look for Nvidia stuff:
E 2025.01.22 13:16:40.236154 0 [Game] [08-16-40][streamline][error][tid:5152][0s:001ms:151us]file.h:94[open] File 'C:\ProgramData/NVIDIA/NGX/models/nvngx_config.txt' does not exist
E 2025.01.22 13:16:40.236172 0 [Game] [08-16-40][streamline][error][tid:5152][0s:001ms:171us]ota.cpp:255[readServerManifest] Failed to open manifest file at: C:\ProgramData/NVIDIA/NGX/models/nvngx_config.txt
...
E 2025.01.22 13:16:40.693860 0 [Game] pmAftermathError::LogResult: Unsupported driver version - requires at least an NVIDIA R495 display driver. - Error : Invalid, SystemCode : 0x00000000 (S_OK)
E 2025.01.22 13:16:41.310548 0 [Game] pmAftermathError::LogResult: Aftermath Error 0xbad00005 - Error : Invalid, SystemCode : 0x00000000 (S_OK)
...
E 2025.01.22 13:16:41.330400 0 [Game] [08-16-41][streamline][error][tid:5152][1s:095ms:395us]sl.cpp:668[operator ()] Feature 'kFeatureDLSS_G' requires GPU hardware scheduling to be enabled in the OS
And then I see a bunch of these everywhere:
E 2025.01.22 13:20:01.530317 28186 [Game] [DataBinding] ERROR: DataStoreImpl::DeleteTemplateIfUnused Failed to delete template data from the DataStore! ErrorCode: BindingResult::kCouldNotFindData
E 2025.01.22 13:20:01.530447 28186 [Game] [DataBinding] ERROR: DataStoreImpl::DeleteTemplateIfUnused Failed to delete template data from the DataStore! ErrorCode: BindingResult::kCouldNotFindData
E 2025.01.22 13:20:01.530476 28186 [Game] [DataBinding] ERROR: DataStoreImpl::DeleteTemplateIfUnused Failed to delete template data from the DataStore! ErrorCode: BindingResult::kCouldNotFindData
E 2025.01.22 13:20:01.530497 28186 [Game] [DataBinding] ERROR: DataStoreImpl::DeleteTemplateIfUnused Failed to delete template data from the DataStore! ErrorCode: BindingResult::kCouldNotFindData
E 2025.01.22 13:20:01.530525 28186 [Game] [DataBinding] ERROR: DataStoreImpl::DeleteTemplateIfUnused Failed to delete template data from the DataStore! ErrorCode: BindingResult::kCouldNotFindData
And these:
E 2025.01.22 13:23:37.112381 61129 [Game] [DataBinding] ERROR: Binding Failed, BindingResult::kInvalidPath. DataStore: SeasonsDataStore, Target:
E 2025.01.22 13:23:37.112406 61129 [Game] [DataBinding] ERROR: Binding Failed, BindingResult::kInvalidPath. DataStore: SeasonsDataStore, Target:
E 2025.01.22 13:23:37.112426 61129 [Game] [DataBinding] ERROR: Binding Failed, BindingResult::kInvalidPath. DataStore: SeasonsDataStore, Target:
E 2025.01.22 13:23:37.112444 61129 [Game] [DataBinding] ERROR: Binding Failed, BindingResult::kInvalidPath. DataStore: SeasonsDataStore, Target:
E 2025.01.22 13:23:37.112467 61129 [Game] [DataBinding] ERROR: Binding Failed, BindingResult::kInvalidPath. DataStore: SeasonsDataStore, Target:
So I’m at a bit of a loss. I think I can try to uninstall D4 and reinstall it on my main Samsung NVME (or move the installation if that’s a thing, I’ll check).
I’m also not entirely sure if reinstalling my AMD driver will help if the game keeps looking for DLSS and Nvidia stuff, even though my Resolution Scaling is disabled in-game, and so is raytracing.
No idea what else to try beyond that. All I know is that this started only when I got the DLC around Season 6, but maybe something else happened around that time, I’m not entirely sure.
EDIT 2:
I think I MAY have potentially fixed it? Don’t quote me on it yet, still playing and testing, but here’s something I tried:
Go to C:\Users\<YourUsername>\Documents\Diablo IV\LocalPrefs.txt and edit it with the following change:
Change DLSS "2" to DLSS "0".
Only make this change if you’re on an AMD system like me.
EDIT 3:
Bah, nevermind, it happened again. 
im having the same issue, ive seen hundreds of threads about amd users trying to portal and ending in black screen with some parts of hud up. nothing ive tried has fixed it. gonna email support again but it looks like all they wanna say is its a connection issue. bought the expansion to play this season and it only started then. level 60 paragon 121 and its happened probably over 100 times. so multiple times per hour lol
1 Like
This happens about half the time when I portal back to town. I don’t have the expansion and this has happened for months. Exact same happens to me and sometimes the game kicks me out of the game and I have to start a new game.
Can’t see myself getting the expansion until blizzard fixes this.
Same issue here with same errors than you. Repaired game, fixed virtual memory, cleaned cache…nothing works EXCEPT play at minimum quality (for now it seems stable…).
The best and funny error on my fenris log is related to nvidia…but I’m have an AMD GPU lol
EDIT: crash again at minimum quality…this is frustrating.
See, that’s the thing I don’t get. I don’t understand why it’s continuously looking for DLSS and Nvidia files when we’re using AMD GPUs. That HAS to be an issue on Blizzard’s side.
1 Like
Same. Logging into Diablo IV hangs … Music stops for 30s-1min then starts again. Wait another 3-5 minutes then “Reconnecting to Diablo” pops up in upper left and game closes.
This is getting annoying.
I opened a ticket with Blizzard Support and told them to please forward all of this to someone on their team who can look into why the game stopped recognizing AMD systems for some reason. Hopefully they release a fix soon.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.