Hi I’m getting random Access Violation crashes, like once maybe twice a day with no rhyme or reason to them. I have an i9 9900kf is it’s unrelated to the problems people with 13th and 14th gen intel CPUs have been having. I just don’t want this to happen in dungeons or something, what can I do to figure out what is causing it to happen?
2 Likes
Maybe try going into a dungeon or raid that you have done several years ago not current and see if it causes a crash just to test.
It seems completely random as to when/where the crashes happen. Had it happen in the new raid, old world, out questing, etc. it’s just super infrequent and I’m unable to figure out what exactly is the trigger.
Access violations are not exclusive to CPUs. They can also be caused by insufficient permissions on a directory, poorly made or outdated addons, lack of RAM due to use or faulty modules, corrupt drive space, lack of drive space for pagefile use, etc. For all these reasons, they’re difficult to diagnose.
Edit: Sometimes the Windows Event Viewer has more info about stuff happening around the same time.
2 Likes
I don’t have too many addons, just the usual suspects (details, dbm, raiderio etc). I have enough RAM (32gb and not even close to all used). 750gb free on my drive and health check on the RAM and drive came back OK.
The only things I see in the event viewer that happened very close to when this happened are the following error:
The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout.
And the following warning:
Certificate for local system with Thumbprint 1a dd 3a 5d 39 34 0e 74 b2 a4 3b 10 31 64 e6 7a 86 72 8a 99 is about to expire or already expired.
1 Like
I’m also having Access Violation crashes, just started in the last couple of days. Will post more info in a moment.
Did you try turning off the gamebar? It’s a common problem with Blizzard games for it to cause crashes. The irony of that statement does not escape me.
It’s off in settings, I remember reading about it being the cause of issues in the past. Not sure why it’s trying to do stuff still and getting errors when it’s off.
Edit: I had it turned off in settings but I’m going to try uninstalling it and see if that does anything. Using the following command in powershell in case it does work and someone comes across this in the future:
Get-AppxPackage Microsoft.XboxGamingOverlay | Remove-AppxPackage
Edit2: This did not work.
2 Likes
I’ve been dealing with these crashes for so long now, too. It only happens to WoW, no other game, and we all know WoW isn’t the prettiest compared to what’s out now. So frustrating. Happens to me about 3 to 8 times a day!
I’m never buying Intel top tier anything ever again. I promise you that.
This, on top of Pacifist Rig randomly disconnecting me mid fight in a delve!
I just tried the PowerShell thing you’re talking about. I hope for some luck already. Geez.
Oh, the only way I know how to stop the crashes is to go into Bios and disable the top two turbo features. But it does affect performance, and WoW isn’t the only game I play. So it’s unreasonable to ask for me to go into Bios 10+ times a week.
Somebody in another forums said:
“I have the same problem, using AMD cpu and gpu. Usually error occurs when interacting with an NPC.
Turning off ‘Read Only’ attribute on WoW folder in Windows Explorer fixes the issue for me. However after every update it comes back, after every patch or hotfix I need to do it again”
I just tried it. Restarting the computer. See you in 5 mins when it crashes again! lol
The PowerShell thing did not work for me and infact I had a blue screen from the crash after I deleted GameBar (doubt the bsod had to do with that but it didn’t work for the crashes). I just put my RAM down to 2333mHz instead of the 3600 it’s rated for and I haven’t gotten any crashes since then. Might be worth looking into disabling XMP/putting RAM back down to default clock values.
2 Likes
I just tried the read-only thing, PowerShell, Intel’s tuning app, and disabled one of my cores. So now, if it works, I won’t know what did it (but I doubt it will work).
I’ve gotten BSOD a few times, too, but I haven’t seen it in over a week.
Can’t even do any group content as tank or healer (my mains) without fear of “crashing/DC’ing.”
Your RAM was overclocked and unstable was the solution.
1 Like
I hope so. So far so good, just weird that it’s only unstable in WoW - not other games or anything. And it was sold as 3600 RAM so idk why it’d be unstable at 3600.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.