I’m getting contant ACCESS_VIOLATION - The instruction at “0x00007ff7d6f0fbf8” referenced memory at “0xffffffffffffffff” when playing the beta. Works fine in Retail and/or other games. No addons. I’ve tried updating BIOS even.
This is the crash report located at C:\Program Files (x86)\World of Warcraft_beta_\Errors
Running the report by an AI agent:
Core Issue
ACCESS_VIOLATION (Memory Read Error) - The game tried to read from an invalid memory address 0xffffffffffffffff (all F’s = -1, a null/invalid pointer).
Key Details
What happened:
-
When: ~12 minutes into gameplay after attacking a training dummy
-
Where: Contender’s Gate, Dornogal
-
Character: Night Elf Rogue (Outlaw spec) on Halduron realm
-
Activity: Combat with “Cleave Training Dummy”
Technical indicators:
-
Clean beta build (64339) from Nov 7, 2025
-
No addons loaded (
<Addons.HasAny.Loaded> No) -
Zero Lua errors
-
System stable (20 min uptime, good hardware - RTX 3080, 32GB RAM)
-
Using D3D12 renderer with NVIDIA drivers
Likely Cause
The crash stack trace shows the exception originated deep in WoW’s rendering or combat calculation code. Given you were:
-
Attacking a training dummy with AoE abilities (Cleave dummy)
-
Playing Outlaw Rogue with various combat effects active
-
Had spell clutter/density settings at moderate levels
This appears to be a beta bug in combat spell effect handling - possibly a race condition where the game tried to access a spell effect or combat log object that was already deallocated or not properly initialized.
What You Can Do
-
Report this to Blizzard via their beta bug report system
-
Try reproducing: Does it crash consistently with the same rotation on training dummies?
-
Consider lowering spell density settings temporarily (
spellClutter,particleDensity)
This is a legitimate bug in the beta client, not something wrong with your system. Your hardware and drivers look fine.