Access Violations Crashing

Hi, I have been having this crash pretty frequently the last few weeks, pretty regularly in Dornogal, I have seen past threads similar to this of posting a paste of dxdiag and someone smart seeing the issue, https://pastebin.com/VvBUvPms

Hoping someone can help me out here! Sorry if there is a running thread for these.

Unfortunately, access violations are quite tough to diagnose over a forum because the common diagnostics, like the DxDiag or MSInfo, don’t offer much insight on the cause.

One thing I recommend checking is the permissions on your World of Warcraft folder. After some Windows updates, I kept finding mine was set to Read Only for the whole directory, which can cause those errors.

1 Like

Hi, I am having the same crashing issues "“access violation” “memory”

I did just go to my WOW folder and it DOES say "read only(only applies to files in folder)

Should I uncheck this? Or are there specific ones I need to check/uncheck?

Uncheck the main folder in C:\Windows\Program Files for WoW and it will apply to everything inside it. You may need to wait a moment, as there are a lot of files.

I started getting Access Violation error when trying to start the game from Battlenet, but can start the game from wow folder.

“One thing I recommend checking is the permissions on your World of Warcraft folder. After some Windows updates, I kept finding mine was set to Read Only for the whole directory, which can cause those errors.” - this does not work, it goes back to read only right after you change it.

1 Like

Then your admin account on Windows may be corrupted or another app is controlling the directory. The settings don’t just flip back under normal circumstances.

Mine just keeps going back to read only. This is getting extremely frustrating

1 Like

I don’t know if the “read-only” even matters. I asked friends, and their folder is on read-only too, and their game loads from battlenet just fine. Meanwhile my game gives access violation error. I can start the game just fine from the wow folder though

I have spent hours trouble shooting now. None of it is working. I thought the “read only” thing worked but the crashes resumed again 5 minutes later. I really do not even know what to do at this time, apparently the only technical support they provide now is the online automatic directory which is not helping at all.

I think you and I are also having somewhat different issues, but a similar error message. I was told to try to reinstall wow, but I am too lazy to do that now since I can start it from the folder directly and play it fine. The ticket I sent in told me to go to the forums for answers lol

Yeah it is pretty crazy, they told me the same, that other players would probably help me.
When you say you’re launching it from the folder, are you just clicking the “World of Warcraft Launcher” in the folder? And should i like turn the bnet launcher thing off? TY much

I’m in this boat as well. I haven’t seen anything that fixes this issue. I have a ticket into Blizz, but they have not found a solution yet either.

Having the same issue including the read only flip back. So far however I have only gotten crashes in Dornugal while doing Thaum, but that is also the only time I am just standing in one spot for extended periods.

I’m getting the same thing since War Within started.

I could be in one spot for extended periods or doing some thing like flying to another part of the map or reading a map to go to my next location. It does not matter. I get the Access Violation Error that can’t read memory. I don’t know if the “read-only” even matters. I have even disabled addons. Issue still happened.

Processor: 13th Gen Intel(R) Core™ i9-13900K (32 CPUs), ~3.0GHz

Intel messed up their specs for PC manufacturers and may have caused physical harm to your CPU. Read more:

Problem signature:
P1: UplayWebCore.exe

System resource hog. Ubisoft is bloatware. Not the same game, but you can find the same comments about pretty much all titles: https://www.reddit.com/r/Rainbow6/comments/tk31rt/ubisoft_connect_web_core_using_too_much_cpu_fixed/