Access Violation

Support Technical Support
1

Since Tuesday’s maintenance, the game has been frequently crashing (there are 41 crash logs at the moment) with an Access Violation message. The error happens often in raids, but is just as frequent when loading a character.
“Exception: ACCESS_VIOLATION - The instruction at “0x00007ff6f408e5cb” referenced memory at “0xffffffffffffffff”.
The memory could not be “read”.”

  • I’m using a laptop CPU that is not listed as affected by the Intel microcode bug
  • I have the latest Windows updates and NVidia drivers and have ensured there are no BIOS updates available.
  • I’ve tried deleting the Data\indices and Data\config folders
  • I’ve run dism /online /cleanup-image /restorehealth and sfc /scannow
  • I’ve run the scan and update option from the battle.net launcher.

EDIT to add - Just adding that my CPU is a Intel(R) Core™ i9-14900HX 2.20 GHz and my GPU is NVIDIA GeForce RTX 4070 Laptop GPU using driver version 576.80 from 6/17
DXDIAG: https://pastebin.com/dKNgKV1w
I ran the intel processor diagnostic tool it gave me a PASS result.

UPDATE: 8/8/2025 -
This is now 100% reproducible. I simply have to swap characters to cause the access violation.
I’ve tried:

  • switching to DX11
  • disabling optional gpu features and advanced work submit
  • setting render scale to exactly 100%
  • Windows 11 repair installation.
  • Most recent NVidia driver (7/31), Oldest available NVidia driver (3/15-ish)
  • I have no addons in the addons folder.
  • I’ve tried getting support from NVidia, but the crash doesn’t leave full dump files in crash logs, just Blizzard’s mini dump format and NVidia says there’s nothing they can do with those.

I’ve run the heaven benchmark with no issues and tested memory and ssd with ASUS diagnostics. I’m about to quit this game at this point.

UPDATE 8/12/2025 - Spent hours on Friday/Saturday reinstalling Windows. Had everything stable with no crashes for Saturday, Sunday, and Monday. Today, after the maintenance, back to having issues.

What else can I do? Is anyone else seeing this issue?

UPDATE 8/17/2025 - Followed instructions on Reddit to disable aggressive processor settings and I haven’t encountered the Access Violation since.

2

same ehre man and it is alot of them most i seen in a long time

3

141 is almost always a driver issue. Mainly GPU drivers. The last few NVidia drivers have not played nice with wow. You can try rolling your Nvidia drivers back to February 13th

Use DDU to remove the drivers on your rig. And install the older drivers. See if your issue is resolved?

1 Like
4

Thanks for your reply. I’m confused when you say: “141 is almost always a driver issue” - What do you mean by 141?

5

When you get an error that says the memory cannot be read and the memory location is all Fff that’s generally a driver it’s very rarely an actual memory issue

6

Used DDU in safe mode to remove the drivers yesterday and installed 572.47 (2/15). Still experiencing Access Violations when swapping characters after this morning’s maintenance.

Also updated to the July 1 drivers and still experienced Access Violations. This has only happened since the 6/24 update. At this point, my finger is pointed directly at Blizzard.

7

I been getting the same errors since Tuesday’s maintenance too. It’s really annoying, and I blame Timewalking, cause a similar issue happened during Burning Crusade week before.

I can play for a bit, but anytime there is a loading screen, usually I’ll get an error message and kicks me off the game.

8

Swapping from DX12 to DX11 resolved this for me.

9

Same problem with DX11. Access Violation when switching characters.

10

I’ve solved my access violation crash with /console cvar_default. Beware this resets your graphics, sound etc back to default but my game isn’t crashing now.

11

I just tried that. Unfortunately, it didn’t improve my situation. I’ve crashed about 15-20 times today. Sometimes it takes 4-5 attempts to load a character.
I’ve also gone into Armoury crate and lowered the voltage settings for PL2 to 160W (PL1 is 140W)

12

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.