Access Violation and TAC Fail

I keep getting constant crashes either with the game client or the battle.net launcher. As a returning player after almost a year you can potentially understand how frustrated this makes me after subscribing again.

For the launcher it will sometimes never load. To explain it just pulls the window up but doesn’t load any text, buttons, etc…just the spinning “loading” icon. I try to restart it, repair, reinstall it, close all instances using task manager etc…Still does it.

I also get a TAC error: “The CAS system was unable to initialize: tact instance creation failed. Error (16): container locked Tact instance creation failed. Error (16): container locked.” This as Chat GPT has stated tells me, is Windows potentially blocking access to files etc…Just know I went through all steps I was provided and still run into this occasionally including whitelisting all instances of WoW and Battle.net. No idea what to do with this because it constantly comes back up.

Last thing is the “ACCESS_VIOLATION - The instruction at “0x00007ff767304421” referenced memory at “0x0000000000000000”. The memory could not be “read”.” Or some variation of that. I have an asus rog strix Scar 18 2024 laptop with a 4080 in it and the Intel 14900HX in it. I have seen lots on how there is an issue with these CPUs and some recent wow updates since that is the only thing to crash and no other games do. Anyhow, I went through a massive amount of steps for this one and still get it. BIOS updated, VBS turned off, drivers updated, game reinstalled, game repaired, all old files and folders deleted before reinstalling, wiped my laptop entirely and started fresh, changed a million settings, turned off the new graphics options in the wow client, removed addons, removed interface wtf and cache folders, and probably a hundred other avenues. I’ve done a lot to try and make this work and all I’m left with is more frustration. I know part of it is on Windows and Intel for a chip that is unstable. (I even utilized the underclocking method using Intel Extreme Tuning Utility). But something has to be on Blizzard too with some update recently. Before I quit last time it worked perfectly fine. I come back with the same laptop and settings and whatever mix of windows updates and blizzard updates has made the game unplayable. I’m lucky to get 15 minutes in it let alone even logged into a character for more than 20 seconds. Areas, items, etc don’t seem to be triggering this that I can tell but I could be wrong. I’ve tried to check but most times it is when I’m not moving or doing anything or hovering/clicking anything. I dunno…

1 Like

Last time i had that issue i had out of date drivers

You should post this here. Might get some help.

1 Like

the computer i bought last year that i’m using now has a somewhat faulty type of chip in it that can become unstable but the devs of the chip made patches for it, BIOS patches. was a slight pain to buy a flash drive so I could flash the BIOS drivers but I assume my chip won’t degrade now. I don’t know if you have the same kind I have. It may be that your CPU is too damaged already if it’s the same as mine could have been and that you have to buy a new PC to play WoW, that would suck for you if so. I wish you luck.

1 Like

I was getting it too, I turned off “Advanced Work Submit” and it seemed to stop happening. Just did it yesterday tho.

I had this EXACT ISSUE recently. Battle.net swirling endlessly, and when I could get in the game it would crash with the access violation error. It was unplayable. I also tried everything to fix it and the issue persisted. The computer was under warranty so I sent it in and they had to replace the motherboard. WoW works like a charm now.

1 Like

Odds are was the cpu 13th gen intel failed

1 Like

I had this issue back in the spring and I ended up having to replace one of my RAM sticks and that fixed the issue

1 Like

i don’t know if this expac is more sensitive to out of date drivers, but I feel like I have had to update the blizz client, and all my graphics card and chip drivers more frequently in this expac to avoid these kinds of issues.

updating the blizz launcher seems to be more frequent now, too.

1 Like

Switching to direct x11 helps me with this issue. I do not know why.

Edit: specifically the access violation issue.

1 Like

Might be bad RAM.

1 Like