Recently, I’ve had two black screen incidents where my graphics would cut out. On both occasions, the drivers needed to be updated. I’m running with an NVIDIA 4060 RTX. The first black screen was to update the drivers from 542.16 to 542.42. The second was an update to 542.47.
I’ve since reverted back to 542.24 and, as an added precaution, reinstalled the game per NVIDIA customer service chat today. This has happened all within the time 2.8.0.99920 was deployed. Hopefully, the steps I have taken have resolved the issue, but I will post both here and with NVIDIA if the issue persists.
This has happened again with the 542.24 driver, so it is definitely since the 2.8.0 patch on max settings. Other drivers have the same issue with other games, so there is something in the in game settings that causes the drivers to kick out the error code. The event viewer insists that no info is available as to the cause, but…
Just to let you know: On Thursday, February 27, 2025 driver 572.60 was released.
I don’t understand that. I haven’t had any issues and I’m still using my computer, which just turned 9 years old this past January. And I’m still running Windows 10 Pro 64-bit with my NVIDIA GeForce GTX 1080 Ti.
Just to be clear: I was letting @DiabloVern know that I’m still on my older computer. My guess is they are on a newer machine than mine, but still with a few years on it. They are also using older versions of the NVIDIA drivers.
I’m not having any issues with my system. I just don’t understand why they haven’t tried the latest graphics driver.
Just ran a complete system scan and had a veritable river of corrupted system files. Yikes, the log file was 6 MB in size. That hopefully will alleviate some of the issues after the fix, which NVidia customer support told me to run. I did so after it crashed on the 566.36 drivers, so it had to be something else. The scan is done now, so a test drive with a Wiz is in order after I have dinner.
Update:
Found a possible issue in my d3debug.txt files. It hints at a rich presence failure for a missing presence, FMOD error and a max contacts reached issue. The presence failure references a place in the 2.8.0 build and file where the error is. The max contacts reached references a specific email and the FMOD error is a sound connection not ready. This is from the black screen event of two days ago.
This is the first time I’ve been able to see the error file immediately after a crash. For this most recent crash, both the FMOD error and the rich presence failure error are in the file, but not the max contacts error. I may need to update Fmodex to solve the FMOD error. As far as the rich presence error, here are the two points:
These are from the d3debug.txt file created 30 minutes ago. Any help would be appreciated.
This is a repeat of the issue in:
Will update Fmodex64.dll from 0.4.31.4 to 0.4.44.64. There are two things I can try before this update: Lowering the sound channel from 128 to 64 or turning off sound altogether (from the aforementioned thread). Or I can run the 32-bit client and see if that works. I want to exhaust all possibilities before doing this. I will mention the 0.4.31.4 file is very old and the bug may have been reintroduced with the latest patch. At least, it has on my system.
If a new patch is needed, both Fmodex dll files should be updated to their latest versions and the rich presence issue needs to be fixed. Games are constantly evolving and, even though this one is in maintenance mode, D3 should at least have the most current dll files to ensure a smooth play experience.
