UPDATE 2.0.5A - ISSUE STILL HAPPENS
At least for me this issue used to occur without the black screen, but with the latest Patch Black Screen with GUI still showing when I teleport to a crowded location, it doesn’t come back it just hangs like this. Sometimes I can exit to character select, and sometimes it just crashes but the report in the Fenris log shows up the same in either case.
I wish I had a way to share my logs, like dxdiag, sysinfo, nettrace, GPU logs, driver latency, etc.
Everyone I noticed something, that I want everyone to test out for me. If you are still here that means you are still having the problem. Basically, I can tell if I have crashed even before the network disconnect notification, if I tab out during the teleport loading screen and I experience lag in other apps like my browser.
Diablo 4 is on a different M.2. Drive than my Windows installation + Web Browsers but interestingly, if I use a web browser at the start of a normal teleport the browser behaves as expected and I can tab back into the game and find my character at the desired destination, however if I do the same action at the beginning of warp that is going to crash, I notice the browser and any other foreground apps hang
I managed to play for about 8 hours in Nahantu without having a problem. Normally I disconnect the majority of warps, so I thought it was solved but a friend also playing on PC later joined my group and the warping disconnects started happening again, even after the person left my group. While playing strictly in Nahantu, I don’t encounter the issue as often, but I assume this is because the areas have similar textures. When I did crash in Nahantu, I was warping from the jungle area of Kurast Bazaar to the eastern desert-like region of Nahantu.
UPDATE (PRE 2.0.4):
Testing a crossplay theory… when crossplay is disabled for both my wife and I use Windows PC’s and when crossplay is disabled on both our accounts we can’t invite each other?!? So we are testing a theory here that somehow my account/key is getting misidentified by the servers as a non-PC account.
-
It STILL happens after the expansion pack.
-
It isn’t the brand of RAM (I tried different brands)
-
It isn’t the amount of RAM amount (I am using 64GB of RAM and an enormous pagefile on a mostly empty 2TB SSD.)
-
It isn’t crossplay (happens when crossplay is enabled or disabled)
-
It isn’t HDD/SSD (I am using an M.2) - It might have to do with NVMe chipset conflicts though
-
It isn’t your graphics card (I tried AMD and Nvidia)
-
It isn’t your processor because people with all sorts of different ones are having the same issue
-
It isn’t your BIOS (people are having the problem on ASUS and MSI boards at least
-
It isn’t your router or network (I have multiple computers on this network that don’t have the issue)
-
It isn’t your network card because it happens when I am connected via WiFi with Ethernet disabled and the other way around, and I purchased newer cards, the error persists.
-
It’s not likely a software conflict because I reformatted my drives and reinstalled Windows and Diablo 4 so it’s not an install issue or a system issue (probably).
-
I am currently running Windows 11 Insider Preview in an attempt to fix the issue with the latest drivers, but others have reported experiencing this issue on Windows 10 and Windows 11 release builds.
-
It is doubtful that it is related to a USB hub UNLESS your USB hub driver happens to be causing latency and your install location happens to be on an external drive! (guess)
-
The bug happens still happens using Microsoft DirectX11 and DirectX12
-
I have disabled unnecessary services, and unplugged all devices except the mouse and keyboard and the issue persists.
-
I suspect it has to do with NVMe port latency via storport.sys because the more data that has to be rapidly stored on your computer upon warping the more likely you are to crash. Larger areas = more players in an area = more people inventories to load, warping from one area with unique textures to another with completely different textures seems to bring it on, higher resolution textures vs. lower res textures, being in a group.
A great point was raised; those of us having this issue are getting Fenris Debug logs that appear in our Diablo IV folder. Those logs show that we begin the warp, transfer zones, enter the world, warp into the destination, start the outro_effect and the SERVER suddenly issues notice to the client.
I am betting ONLY Blizzard could solve this because ONLY Blizzard knows what hardware/software checks and data loads occur upon warping. I am pretty confident they do some serverside checks, maybe even some TTL/ping (to make sure there isn’t a “glitch in the matrix”, no extra long pause between data bits) to ensure you are not running software that could inject malicious code to prevent duping, item hacks, you name it. I CAN tell you that doing things like having party voice chat, and multiple party members appears to increase the odds of this happening.
We could sit here guessing until someone finds the “secret cow level” but the truth is, until we have a Blizzard programmer speaking to us, we are not likely to get anywhere.
Here is what you could all do to help: Post your latest Fenris debugs (located in the Diablo IV folder, search for “sHandleDisconnect” and copy and paste the logs 5-10 lines BEFORE and AFTER that “sHandleDisconnect”. Someone could correct me here too, because perhaps there is more useful information elsewhere in the log?
My latest example:
I 2024.10.13 03:48:11.145930 25695 | [Game] Adjusting world Sanctuary_Eastern_Continent (69068) subzone from EGD_MSWK_World_01 (1815144) to Frac_Kyovashad (445430) |
---|---|
I 2024.10.13 03:48:24.247302 25695 | [Game] Client entered world |
I 2024.10.13 03:48:24.506160 25695 | [WarpManager] Warped into destination |
I 2024.10.13 03:48:25.103592 25695 | [WarpManager] Starting outro effect default_warp_effect_outro (239915) |
I 2024.10.13 03:48:25.406642 25696 | [Game] Client: sHandleDisconnect |
I 2024.10.13 03:48:25.507295 25696 | [Game] [Prism] 5552: Purged 104 entries from the render and compute pipeline caches in 1.493ms |
I 2024.10.13 03:48:25.512706 25696 | [Game] Disposing UI for World |
I 2024.10.13 03:48:25.649421 25696 | [Game] Client Disposed world 1048578. |
I 2024.10.13 03:48:25.662432 25696 | [Game] UICommon::OnGameDisconnected msg=The game connection has been lost: your client has been disconnected from the server. |
I 2024.10.13 03:48:25.662458 25696 | [WarpManager] Warp canceled |