Yea this is on blizzards end it has nothing to do with anyone’s computer.
1 Like
I had to underclock my AMD Ryzen 7 3800xt 8 core.
Default clock is 4GHz, but the default bios settings allow them to be over clocked automagicly to 4.4Ghz and sometimes even more.
Limiting all core clock to 3.9GHz stopped the lesser quality cores from overheating.
I didn’t change voltage or anything except the core clocks and locked them so none could exceed 3.9GHz.
note: some CPUs will have cores that just don’t perform as well as others on the same die. These are “binned” for the cheaper version of the high end CPUs.
You win the silicon lottery when you get one that has all cores that perform at the same level.
2 Likes
That was why some of the first advice to hep you use the CPU’s … Was to turn off cores one at a time until you found the bad core. Then test without that core in use.
You can temp turn off in task manager or turn them off in the device manager.
Then all the rage was to not over clock by the current…
But the AMD chips have the same issues as well… Still a over clock issue, but fix is different.
Thanks for share… Good luck.
1 Like
Yes, this problem, not sure we should even call it that, has been around for years if not decades.
CPUs are expensive to make so none of the manufacturers trash any waffers unless they are forced to.
most just test to see what frequency they can get reliably out of them and disable the core that don’t work.
Thats how we get things like the CPU I use.
Out of the 16 cores 5GHz it was designed for, only 8 worked properly enough to pass QC so 8 were disabled and we get a discounted 8 core version that runs at a lower freq 
1 Like
9/24/24 and the access_voilation crashes have gotten significantly worse.
And again…when WoW is the ONLY game that causes this issue, it’s not a cpu problem, it’s a Blizzard problem.
Edit: Just overloaded a herb, spawned a Twisted Lasher, immediately got an Access_Voilation crash. Quickly logged back in and I was dead. Thanks Blizzard!
1 Like
Hmm, I was having these on 1 of my 2 PC’s of which both are i9-14900KF’s but it stopped a few weeks ago. I was assuming a patch came along that made things better (as I didn’t change anything else). So while I was having this issue (like 3-4 times a day) it just miraculously went away on sometime around the 11th of this month (last crash was on 9/11, boy that just sounds wrong)… So yeah, that sucks if it’s still happening to you.
I couldn’t effectively raid due to the constant crashing last night. Desperately hoping they’ll roll back to whatever fix they’d implemented a few weeks ago - the issue completely vanished when that was in place, only to return worse than ever before as of the most recent updates.
1 Like
I keep getting this error in Dawnbreaker m+ dungeon. I cannot complete the dungeon cuz I just keep crashing. I’m on an AMD Ryzen 7 7800X3D
==============================================================================
Exception: ACCESS_VIOLATION - The instruction at “0x00007ff7244578b7” referenced memory at “0xffffffffffffffff”.
The memory could not be “read”.
ProcessID: 7784
ThreadID: 15392
still no help with 11.0 bug introduced by Blizz. Trying to [awn it off to Intel and Nvidia is BS. Does not happen with any other of my games or apps. So blizz you own 0832B142-9AC8-4DF6-B7B3-2A2F970F65A9 error and making this game almost unplayable- but definitely unenjoyable
2 Likes
How is Intel taking responsibility for a CPU issue “pawning it off”? Wild logic.
Maybe because people without Intel CPU’s are having the same problem?
But this thread is about Intel CPUs, as mentioned in the original post. And their problem was solved by underclocking their cores.
O.o, that’s not a fix, that’s neutering your CPU for a single games bug.
2 Likes
You’re missing a ton of context while expressing opinions on the situation. Intel messed up with their specs, and has taken responsibility for doing so. The overclocked Intel CPUs may have experienced irreparable harm, so downclocking or replacing are the only options.
1 Like
I have the CPU in question, and have been following the issues with it since February (every bios update, changes to the power prior to fixes, etc.). Now, as I keep repeating and others keep saying as well. I have zero issues with no other apps, games, etc. Just WoW, and it only started with the 11.0 pre-patch (I played DF for months and months with zero issues). And it’s come and gone from patch to patch as they make changes. So again, if I was having issues with other games, other apps, I could understand what you’re saying, but when the ONLY app I have issues with is WoW, it’s pretty clear that the issue isn’t my CPU.
It’s not our PCs! I have a brand new one that I bought two months ago, worked with WoW right out of the box, no issues, and then as of a week ago out of nowhere I’m getting these crashes! It’s stupid, pretty much right when reset day happened, you telling us Intel or some other update that wasn’t from Blizzard is now killing our PCs?? I think not, it is something in the coding that they released that is affecting quite a few of us and we want help to fix it so we can play the game!
1 Like
For anyone that hasn’t tried so far, roll your Nvidia drivers wayyyyy back. I went back to April of this year and I have not had an access violation for about 24 hours now…
I am not calling this fixed, but it seems to be better at least. I don’t know where the drivers actually become a problem, but i did roll back a few versions at first and it didn’t solve it.
You could have just said you don’t want to do the troubleshooting everyone else did because you don’t believe it. All we can do is offer the information Intel provided about this issue.
I’m referencing the post Intel made where they took responsibility for an issue they created. The CPUs were being pushed too hard, and over time, degrade due to those out-of-bounds settings that they can’t handle.
2 Likes
I’m literally telling you over and over that I’ve done extensive troubleshooting of my two PC’s. They pass every benchmark, every burn-in test, every stress test, everything I can throw at it with flying colors, EXCEPT wow. WoW crashes constantly (and it’s weird, it’ll crash 4 times in one day, and than go for a week without crashing). This NEVER happened until the 11.0 pre-patch. Prior to that I had zero issues.
And to clarify, the moment some test I run (and I’m talking running these for 24+ hours), I’ll start adjusting CPU settings. But at the moment, the only application I have on my PC that crashes is WoW. You can paint the picture however you want, but considering the extensive amount of testing I’ve done, all roads lead back to one single app.
Part of this sentence is missing I guess, because you said you did testing but you won’t adjust CPU settings.
Whatever the case for you, the OP has an i9-14900KF. Intel recommended doing ONE thing to fix crashes, they did it, and now they aren’t crashing. No one is requiring you to do anything, only recommending you do what the manufacturer of the chip also recommends. If you don’t want to, don’t. Chances are, the crashes will continue.
We’re way off track now and these replies are pinging the OP for no reason. The original purpose of the thread is solved, so I consider this thread complete and will not be doing further troubleshooting here. Good luck with your issue.
1 Like