I guess some of us are trying to understand the sitution, which may help solve the issue with more data. It’s not like they tested the game on every possible nvme drives out there. I do understand they are a big company with a big budget but you can’t account for every single piece of hardware out there. But go ahead and refund, no one is holding you back.
My friend has the issue running intel optane 900p 480gb, if he runs CrystalDiskMark and benchmarks it when the game is loading it’s works fine.
I have a Samgung 970 Pro, no issues at all.
I’m using the Samsung NVMe Controller, he’s using the Standard Microsoft NVMe Controller.
Just a small FYI.
It seems that this fixes some people some of the time, and not consistently it appears.
Not only that, changing the region for logging in also seems to help the issue some of the time, not every time.
Lot of weird here. Just a heads up.
I agree. I will asked for a refund if the issue is not fixed after 1 week.
Switching game location from my shiny new NVME WDSN850X ssd to my ancient Crucial X500 SATA drive finally worked. No reinstall or anything, just copying the existing install files over and pointing the Bnet launcher to the new location.
Issue looks like this:
- can launch game and get through the queue fine
- when I hit the logging in diablo iv screen, on nvme it freezes (can hear intermittent background sound effects, but the spinning red circle stops spinning)
- on nvme it stays frozen for about three minutes, then shows the loading screen, then flashes to “Reconnecting to diablo” for a few seconds, then crashed to desktop.
On Non-nvme drive it just goes immediate pi from loading to character select.
1 Like
Corsair Force Series MP510 960GB
Decent speeds. Good brand.
About half the speed of the WD actually, so slower, yet still issues. Odd.
Mine is a Kingston Fury Renegade with speeds above both and is working.
This problem has no logic to it yet, that I can see. Frustrating.
Installing the game to my slower D drive, also fixed the issue for me.
I’m guessing that something about being on NVME makes the initial load take so long that the session connected to the server times out, and then the Reconnect step fails too. If at least the “reconnection to Diablo” step worked it wouldn’t be as bad since it’d still let people in (just slower on NVME, paradoxically).
Looking at the FenrisDebug.txt logs in the DiabloIV folder I see alot of
I 2023.06.02 16:01:42.207021 [Game] -----------------------------------------------------------------
I 2023.06.02 16:01:43.332004 [Game] No TACT path found for 'EncryptedNameDict-0xb429c2b91f7e3764.dat'
I 2023.06.02 16:01:43.332013 [Game] No TACT path found for 'EncryptedNameDict-0x76d2221076de3f86.dat'
I 2023.06.02 16:01:43.332017 [Game] No TACT path found for 'EncryptedNameDict-0x433bbc48059a3628.dat'
and WARN level logs for:
I 2023.06.02 16:01:37.652938 [Game] Computed solution to server puzzle | bits: 7 | solution: 131 | time_elapsed_us: 21
W 2023.06.02 16:01:37.709866 [Online.Systems.CPresence] Unhandled fenris game account presence field | presence_field_id: 11
W 2023.06.02 16:01:37.709977 [Online.Systems.CPresence] Unhandled fenris game account presence field | presence_field_id: 11
W 2023.06.02 16:01:37.710030 [Online.Systems.CPresence] Unhandled fenris game account presence field | presence_field_id: 11
W 2023.06.02 16:01:37.710057 [Online.Systems.CPresence] Unhandled fenris game account presence field | presence_field_id: 11
W 2023.06.02 16:01:37.710090 [Online.Systems.CPresence] Unhandled fenris game account presence field | presence_field_id: 11
I 2023.06.02 16:01:38.707120 [Game] ConnectionBase::Disconnect | connection_id: 1 | reason: 0 | connectiontype: 6
Then it realizes it’s disconnected, and tries to reconnect, but I guess it fails:
I 2023.06.02 16:05:15.387082 [Achievements] Loading static data
I 2023.06.02 16:05:15.392135 [WarpManager] Waiting for limbo warp...
I 2023.06.02 16:05:15.392143 [WarpManager] Warped into limbo
I 2023.06.02 16:05:15.410538 [WarpManager] Creating looping world
I 2023.06.02 16:05:15.412780 [WarpManager] Starting loop effect DCE_HellgateCamera_NoFade (1026142)
I 2023.06.02 16:05:15.417072 [Game] ConnectionBase::Disconnect | connection_id: 7 | reason: 0 | connectiontype: 2
I 2023.06.02 16:05:15.417088 [Online.Systems.CUserProxy] Deleting connection due to disconnect
I 2023.06.02 16:05:15.417116 [Online.Systems.CUserProxy] Attempting to find and connect to user proxy | client_user_id: 0
I 2023.06.02 16:05:15.417632 [Game] UIConnectionLost::ReconnectModalHandler::Update No input focus found for primary user. Attempting to find acceptable focus.
I 2023.06.02 16:05:15.420724 [Game] ---------------- UIModalNotificationManager::ShowModal 1: Reconnecting to Diablo IV
I 2023.06.02 16:05:15.666798 [Interface.BgsLow] I 16:05:15.666785 [BGS] |event=Disconnected|method=OnDisconnectComplete|address=prod.actual.battle.net|port=1119|status=1016 (C:\projects\fenris\shared\Contrib\bgs-sdk\6.1.0-pre-release1\src\low\core\connection_handler.cpp:245)
I 2023.06.02 16:05:15.666812 [BgsClient] BgsConnection: disconnected. | connection_index: 0 | connection_id: 1 | bgs_error_code: 1016
I 2023.06.02 16:05:15.666872 [Online.Systems.CAuthSession] OnDisconnectComplete | client_user_id: 0 | error_code: [symbol not found] (1016) | bgs_connection_id: 1 | silent_login: true
I 2023.06.02 16:05:15.666882 [Online.Systems.CAuthSession] OnDisconnectComplete - Silent Reconnect | client_user_id: 0 | error_code: [symbol not found] (1016) | bgs_connection_id: 1 | silent_login: true
I 2023.06.02 16:05:15.667010 [Online.Systems.CParty] OnFullyDisconnected | party_id: c3e9ff30-015e-11ee-8927-c1145bcf1811/us-central | client_user_id: 0
I 2023.06.02 16:05:15.667099 [Online.Systems.CAuthSession] StartSilentReconnect | client_user_id: 0 | ip: prod.actual.battle.net | port: 1119
I 2023.06.02 16:05:15.667558 [Game] bgs Connecting to prod.actual.battle.net:1119
W 2023.06.02 16:05:15.793255 [Interface.BgsLow] W 16:05:15.793241 [RPC] |event=rpc_connection_status_queue_not_empty|class=rpc::ConnectionManager|method=DestroyConnection|numPendingEvents=6 (C:\projects\fenris\shared\Contrib\bgs-sdk\6.1.0-pre-release1\src\low\rpc\rpc_connection_manager.cpp:149)
I 2023.06.02 16:05:17.416984 [Interface.BgsLow] I 16:05:17.416973 [BGS] |event=Connection metering enabled.|connection_id=2 (C:\projects\fenris\shared\Contrib\bgs-sdk\6.1.0-pre-release1\src\low\core\connection_handler.cpp:263)
I 2023.06.02 16:05:17.416995 [Interface.BgsLow] I 16:05:17.416992 [BGS] |event=Connection to Battle.net ready.|connection_id=2|address=prod.actual.battle.net|port=1119 (C:\projects\fenris\shared\Contrib\bgs-sdk\6.1.0-pre-release1\src\low\core\connection_handler.cpp:283)
I 2023.06.02 16:05:17.417000 [BgsClient] BgsConnection: connected. | connection_index: 0 | connection_id: 2
I 2023.06.02 16:05:17.417003 [Online.Systems.CAuthSession] StartSilentReconnect: Connect callback | client_user_id: 0 | bgs_error_code: 0 | bgs_connection_id: 2
I 2023.06.02 16:05:18.041676 [Online.Systems.CAuthSession] OnLogonCompleted | client_user_id: 0 | result: bgs.protocol.authentication.v2.client.LogonCompleteNotification { error_code: 0 record { account_id: 2096544 game_account { id: 689254027 title_id: 4613486 region: 100 } battle_tag: "alienangel#1427" geoip_country: "CA" session_key: "\025\256\021\244\343z\242\213,z|?\025\246&\343Wa|\33454=\201!\327HK\350\276\021\345\215\034F\3355H\014FN;@\261L\303\257\370f\2018\320\323\200\000\002O\'C\242\316\003H\230" employee_only_mode: false } }
I 2023.06.02 16:05:18.416686 [Online.Systems.CAuthSession] GetAccountState | client_user_id: 0 | bgs_error_code: 0 | bnet_account_id: bgs.protocol.account.v1.AccountId { id: 2096544 } | country: CAN
I 2023.06.02 16:05:19.041751 [Online.Systems.CAuthSession] OnCreateSession | client_user_id: 0 | id: bgs.protocol.session.v2.client.SessionId { account_id: 2096544 game_account { id: 689254027 title_id: 4613486 region: 100 } instance_id: "94C262EA645280BF-0000000000082575" } | bgs_error: 0
I 2023.06.02 16:05:19.292184 [WarpManager] Waiting for destination warp...
I 2023.06.02 16:05:19.418184 [Online.Systems.CUserProxy] Attempting to find and connect to user proxy | client_user_id: 0
I 2023.06.02 16:05:19.419225 [WarpManager] Portal completed
I 2023.06.02 16:05:19.420270 [Game] Can't find player to snap camera
W 2023.06.02 16:05:19.430766 [WarpManager] Disconnected from userproxy during loading
I 2023.06.02 16:05:19.545263 [Game] GameDisposeGames()
I 2023.06.02 16:05:19.545269 [Game] ENDING GAME
I don’t see a way to attach the logs, hopefully you can pull them remotely anyway.
Summary
This text will be hidden
same here , sad that i even preorder this . first and last time i ever preorder smth from this small indie company
This fixed my issue! Great idea for a workaround.
To those that need a little more info:
- Open Disk Management
- Click Action → Create VHD
- Pick a place to store it (I created a C:\VHD folder)
- I made it 150 GB in size, VHDX format with Dynamic expansion (means it will only take up the space that is used on your disk, not the full 150GB)
- Initialize the disk by right clicking on it, initialize
- Create a new volume using the full drive, name it whatever you want
- Copy and paste your DiabloIV folder there as mentioned above, then change the folder location in the BNet DiabloIV client settings
- ???
- Game works!
1 Like
Same issue here. Crashes on my gen 4 nvme. Older gen 3 nvme loads game perfectly every time.
This is insane. You didn’t test on … particularly fast NVMe drives? Now I need to buy a SLOW one in order to play the game? That’s not an option or at all realistic.
I think this is more coincidence than anything else.
Not everyone is having this problem, but one of the common factors was NVME drives.
Yet I have a very fast one, works fine.
And two laptops that have so far been fine.
And I see several friends playing, some of whom I know are on NVMEs.
So your response, while justified is not completely true. OF course it was tested.
I think this is more along the lines of some sort of bug, and it has to do with the login more than the hardware, just that for some reason some of these “fixes” are for now correcting it.
Though some fixes have been temporary for some players too.
So, take it all with a grain of salt at this point.
For another data point, dug out an old Samsung 970 Pro and appears to load up just fine. Was failing to start on the much faster 990 Pro. Of course tried all the normal troubleshooting steps first (reinstalling, drivers, rebooting, repairing, etc.), none of which had any effect.
I had this same problem both in launch and the server slam, I have a newer NVMe SSD and I had previously tried everything before finding this thread including reformatting my drive and reinstalling windows ahead of launch just to be sure nothing goes wrong. After seeing this and moving it from my NVMe SSD to one of my SATA SSD’s the crashes are gone entirely game works perfectly normally. Before there was a like 90% chance it would crash before getting past the log in and if I did get into the game it would crash eventually on a load screen.
Glad to have it solved but there is definitely something wrong with this game in regards to NVMe drives.
Not sure if this is mentioned, but enabling the Pagefile on said M2 SSD helps some ppl.
I’ve switched from Samsung 970 Evo+ 256GB to Kingston KC3000 2TB between Server Slam and Early release and I have this issue too. CrystalMark helps here too.
It isn’t just nvme ssds. I had this issue on a 3TB Seagate Baracuda model ST3000DM008. I reinstalled the game on my primary drive which is a 1TB Samsung 860 EVO and I am not experiencing the issue.
Exactly same scenario. Different drives in question but result and symptoms exactly the same and resultant fix the same.
I realized how little info i put:
started on an NVME 2TB Samsung Evo. It worked last night for multiple hours. SOMETHING changed from last night to this morning. When I tried to log on this morning, no go.
After messing around with firewall settings for an hour or more it suddenly worked so I blamed it on the firewall but after a lunch break it stopped working again. Came to this thread. Moved the game (just wholesale copied the directory) from the NVME drive to a 4TB SSD and repointed the bnet client and it logged in first time. Firewall settings had nothing to do with it.
edited again to add that crystaldiskmark fix (essentially trying to bog down the drive?) did not fix my issue. It was fixed, instantly, after spending the 5-8 minutes to copy the diablo 4 directory to a SSD.
I should point out, i’m still flabbergasted I played for several hours last night, no issues. So I made no changes on my side that caused this.