I keep getting persistent access violation errors randomly while playing TBC Anniversary:
==============================================================================
Exception: ACCESS_VIOLATION - The instruction at “0x00007ff6506c62bf” referenced memory at “0x000000d300000000”.
The memory could not be “read”.
ProcessID: 508
ThreadID: 868
<Exception.IssueType> Exception
Crash
Exception.Summary:
ACCESS_VIOLATION - The instruction at “0x00007ff6506c62bf” referenced memory at “0x000000d300000000”.
The memory could not be “read”.
(DBG-OPTIONS DBG-ADDR<00007ff6506c62bf>(“WowClassic.exe”) ← DBG-ADDR<00007ff6506c50bb>(“WowClassic.exe”) ← DBG-ADDR<00007ff6506b7557>(“WowClassic.exe”) DBG-OPTIONS<>)
<:Exception.Summary>
Exception.Assertion:
DBG-ADDR<00007ff6506c62bf>(“WowClassic.exe”)
DBG-ADDR<00007ff6506c50bb>(“WowClassic.exe”)
DBG-ADDR<00007ff6506b7557>(“WowClassic.exe”)
DBG-ADDR<00007ff65300dc99>(“WowClassic.exe”)
DBG-ADDR<00007ff65300dd6d>(“WowClassic.exe”)
DBG-ADDR<00007ff6521c2779>(“WowClassic.exe”)
DBG-ADDR<00007ff6521c48e9>(“WowClassic.exe”)
DBG-ADDR<00007ff650a81b1d>(“WowClassic.exe”)
DBG-ADDR<00007ff651ace7c3>(“WowClassic.exe”)
DBG-ADDR<00007ff651ad116f>(“WowClassic.exe”)
DBG-ADDR<00007ff6505fc86e>(“WowClassic.exe”)
DBG-ADDR<00007ff6505fa148>(“WowClassic.exe”)
DBG-ADDR<00007ff650636f5a>(“WowClassic.exe”)
DBG-ADDR<00007ff6505f03fd>(“WowClassic.exe”)
DBG-ADDR<00007ff6505ef67e>(“WowClassic.exe”)
DBG-ADDR<00007ff6506b7779>(“WowClassic.exe”)
<:Exception.Assertion>
Exception.HashBlock:
DBG-OPTIONS
ERROR #132
DBG-ADDR<00007ff6506c62bf>(“WowClassic.exe”)
DBG-ADDR<00007ff6506c50bb>(“WowClassic.exe”)
DBG-ADDR<00007ff6506b7557>(“WowClassic.exe”)
DBG-ADDR<00007ff65300dc99>(“WowClassic.exe”)
DBG-ADDR<00007ff65300dd6d>(“WowClassic.exe”)
DBG-ADDR<00007ff6521c2779>(“WowClassic.exe”)
DBG-OPTIONS<>
<:Exception.HashBlock>
No
<Jira.JiraProjectId> 11103
<Jira.JiraProjectKey> CLASS
<Exception.ProjectId> 10
2.5.5.65895
<Exception.BuildNumber> 65895
<Exception.Branch> 2.5.5
<Exception.WowProject> BurningCrusadeClassic
World of Warcraft
Client
Retail
Type: WoW
WowClassic.exe
<Wow.Platform> X64
<Exception.Platform> Win 11 (x86 64-bit)
Free Disk Space: 152.63 GB
Exe Built: Feb 11 2026 13:45:44
0000003F 00001FFF 00000400
App Up Time: 0 days, 0 hours, 15 minutes, 19 seconds
System Up Time: 0 days, 12 hours, 57 minutes, 8 seconds
Current Frame: 126846
Current Time: 46628086
Current Tick: 15
0
1
Number of thread pool threads: 6/6/6 (High/Mid/Low)
Battle.net.exe
<Locale.Text> enUS
<Locale.Audio> enUS
Session Time(hh:mm:ss): 00:15:07
<SessionTime.Grouping> 00:15:00 - 00:29:59
Time in World(hh:mm:ss): 00:14:45
<TimeInWorld.Grouping> 00:00:00 - 00:14:59
Total Time in World(hh:mm:ss): 00:14:45
<TotalTimeInWorld.Grouping> 00:00:00 - 00:14:59
No
No
I have received this error with several addons loaded, all addons disabled, current drivers with a clean install, old drivers with a clean install, after scan and repair, running as admin, forcing DX11, using DX12, lowest graphics settings, max graphics settings, graphics compatibility boxes checked and unchecked, overclocking GPU, underclocking and undervolting GPU, both prior to and after updating BIOS and chipset drivers, as well as disabling any software that has overlays or hooks, like Discord and DisplayFusion.
I’ve even tried using Grok to read the crash files and determine a cause, which it was unable to pinpoint and gave me the following summary based on the logs I uploaded to it:
Consistent ACCESS_VIOLATION crash at offset 0x00007ff6506c62bf (instruction at WowClassic.exe+0x2362bf referencing invalid low pointer) with the exact same call stack:
00007ff6506c62bf → 00007ff6506c50bb → 00007ff6506b7557 → 00007ff65300dc99 etc.
Reproduces with zero addons (only BetterAddonList enabled) on the latest AMD driver (32.0.23017.1001, 2026-01-08) in both D3D11 and D3D12. Happens reliably after ~12–15 minutes in Outland zones (e.g. Shattrath).
CPU: AMD Ryzen 9 3900X 12-Core Processor (3.80 GHz)
Board: TUF GAMING X570-PLUS (WI-FI)
GPU: ASUS AMD Radeon RX 7900 XTX
RAM: Corsair Vengeance Pro 128GB - 4x 32GB DDR4 3200MHz
Posting because I’m out of ideas on how to fix this and it’s severely impacting my ability to play and enjoy TBC Anniversary.