I’ve been experiencing persistent crashes for about a week now (after not experienceing any through pre release and post launch). I’m sure blizzard tech support is overwhelmed which is why replies to my ticket are taking so long, so I tried to get chatgpt 4 to help analyze the error report in hopes that it would be something i could fix. It walked me through installing and using windbg and this was its reply when i gave it the exception analysis of the dmp file
The information provided in the dump indicates that the application Diablo IV crashed due to an “Access violation” error. An access violation error, represented by the exception code c0000005, generally means that a program tried to access memory that it should not have. In this case, it was trying to read from a memory address that it didn’t have permissions to (ffffffffffffffff). This is also denoted by the key-value pair “AV.Fault: Read”.
The cause of the problem seems to be a function within Diablo IV, referred to in the stack trace as Diablo_IV!AK::ReadBytesSkip::Count+0x1d6cd. The “STACK_TEXT” section shows the order of function calls leading up to the crash, which can help determine where the problem originated.
If you’re a user, there’s not much you can do to fix the problem other than:
- Ensure your system meets the minimum requirements for running Diablo IV.
- Update Diablo IV to the latest version.
- Update your system drivers, especially the graphics driver.
- If you’re overclocking your PC, try running at the default clock speed.
- Reinstall the game.
- Reach out to Blizzard support with this information.
If you’re a developer or you have the source code, you can use this stack trace to help locate the problematic code in the application that’s causing the crash. However, this would be in the realm of advanced debugging and would require deep knowledge of the software’s inner workings.