Exception: ACCESS_VIOLATION

Support Technical Support
1

For the past month or two I’ve been getting an error that crashes my game. I’ve seen that this is a generic error and have done most of the troubleshooting suggestions: a reinstall, disabling out of date addons, multiple scan and repairs, etc.

Program: C:\Program Files (x86)\World of Warcraft_retail_\Wow.exe
Exception: ACCESS_VIOLATION - The Instruction at '0x00007ffea3bc1be8" referenced memory at '0xfffffffffffffffff".
The memory could not be “read”.
ProcessID: 24788
ThreadID: 4632

I’m not sure what information to include, but one of the pop up windows said to use this Report ID when communicating with Blizzard : 8E73BF06-4C94-4EA6-A346-4F093B890DD8. Also I’ve seen people include a pastebin link of their DxDiag so here’s mine: https://pastebin.com/9vQmFEwg

Any help would be appreciated.

2

Problem signature:
P1: ITERHPGen.exe

Problem signature:
P1: RaiderIO.exe

First, address those errors. Not sure what the first app is, but the second seems unnecessary if you have the addon.

Second, since you have an i9-13900K, you may be experiencing the CPU bug. Read more here:

3

Tried addressing the first error and I thought I located it with an unnecessary startup program so I uninstalled it, but kept raider io on. Got another error so I turned off raider io and got another error.

Program: C:\Program Files (x86)\World of Warcraft_retail_\Wow.exe
Exception: ACCESS_VIOLATION - The Instruction at '0x00007ff99b421be8" referenced memory at '0xfffffffffffffffff".
The memory could not be “read”.
ProcessID: 11720
ThreadID: 17532

Report ID: 3ECE3753-6CE4-496C-9B1A-BA56CD164031

Another DXDiag: https://pastebin.com/Ki9YJein

Update (11:05pm pst) Just received another error after uninstalling Raider io.

Report ID: ECD3CA8B-893E-47CC-A5BF-77028D6CCC66

Here’s the actual error: https://pastebin.com/w2ZDpaLb

4

Those error messages cannot be deciphered on the forum. They require a tool Blizzard uses and it’s only available through the ticket system. The same goes for the Error log.

I think you should look into the link I shared since the DxDiag is the same errors.