ERROR #132 ACCESS_VIOLATION causing game crashes over and over, leaving the game entirely unplayable

Hi there. I am new to WotLK as of this year. I have had a great time thus far playing with a friend who is from the old original days on WoW, but I am about at my wits end here trying to get the game to be playable again. I am ready to give up on the game as I dont have the time to dedicate to troubleshooting it more than I invested today.

I will start by saying, I had never experienced a single game crash or had any issues with playing until this recent content drop. Over the last few days, I noticed highly populated areas being less “smooth, or responsive” and taking longer to load in than before. No big deal.

Then i get what I notice to be some occasional skips that are short lived… also no big deal… until the screen seems to freeze for atleast 3 seconds, and then gameplay resumes… meanwhile video on my monitor was frozen for all of those 3 seconds while my group is still playing and getting wiped. I am a level 80 disc priest for heals in my group, I cant have 3 seconds of not seeing whats going on, someone could die in that period, or worst… we all die and cause entire wipes. This has been my gaming experience progression since the new content drop… that is UNTIL LAST NIGHT.

Starting 10/15/2023 I started getting game crashes. The screen will freeze mid action and I can see character model frozen. (I could be running around, jumping, standing still, fishing, casting a spell, you name it and it doesn’t matter) but I can still hear the audio from things around me such as if a fish got hooked, then the screen blacks out and I will either get to resume gameplay 5 or so seconds later, or the game will then crash and give me an ERROR#132 message stating: The instruction at ‘0x00007ff83fefdb15’ referenced memory at ‘0xffffffffffffffff’. The memory could not be “read”. It may be worthwhile to note, I have noticed that my discord will consistently crash when the freeze occurs. EVERY TIME.

Now… after running into this issue, I uninstalled the game, deleted Bnet, reinstall Bnet, reinstalled the game, and hoped it would be better… What do I experience? THE SAME EXACT CRASHING AND ERROR MESSAGES.

Now… I decided to wipe my computer, reinstall windows 10, reinstall drivers, the whole 9 yards… Reinstall bnet, get WotLK again, and STILL THE SAME ERROR MESSAGES.

The game has become completely unplayable for me since this new content drop as I crash within 10 minutes of running around in game.
I can simply recreate the game crash just by walking around dalaran spamming nameplates off and on for 5 or less minutes and the game crashes. I can just sit there in Dalaran and the game crashes. These are not things that should lead to a client crash.

I have spent upwards of 8 hours today working to troubleshoot this and get the game playable before an ICC 10M that my group had planned for tonight that I am now barred out of participating in. I would love to get some help with this, as I am not the wisest for finding solutions or going through and checking logs to really see what the issue is and get to the bottom of this.

AGAIN… to recap… I ENTIRELY REINSTALLED WINDOWS AND REINSTALLED ALL MY DRIVERS AND UPDATED EVERYTHING, STILL SAME ISSUE OCCURING. I EVEN TRIED THE DIRECTX11 v 12 AND STILL GET CRASHES.

If anyone can help, it’d be greatly appreciated, otherwise I will be giving the game up at this point as it simply wont run on my PC without crashing.

Can you post the complete error to pastebin.com and post the link please

1 Like

Are you looking for the entire error prompt wording? It would be as follows. IDK how to copy paste it rn since all I have is screenshots available, so I am typing it out according to the many screenshots I took.

"This application has encountered an critical error:

ERROR #132 (0x85100084) Fatal exception!

Program: C:\Program Files (x86)\World of Warcraft_classic_\WowClassic.exe
ProcessID: 20032
ThreadID: 20792
Exception: ACCESS_VIOLATION

The instruction at ‘0x00007ff83fefdb15’ referenced memory at ‘0xffffffffffffffff’. The memory could not be “read”.

Press OK to terminate the application.

I will figure out pastebin, but please do clarify what youre looking for please. This is how the message reads out when the error pops up. I did manage to find an error folder that appeared to have some form of crash logs though. Idk if thats something youd want to see.

There should be more to the error

1 Like

Yes that would be great. Just the latest one

1 Like

That is the entire error message that comes up. Then when I close that, there is another window for me to send the info to blizzard and reopen the application.

============================================================================== - Pastebin.com

Link to pastebin for the latest crash log

It looks like your graphics drivers are crashing. Install the new drivers did you download them from AMD if not you’re going to want to get the latest versions of your drivers from AMD also do you have a hardware monitoring program she can check the temperature of your graphics card

1 Like

Yes I installed direct from AMD website, none of that was the issue. I am not sure the entire solution to the issue, or what the genuine and true root of the problem was… but its fixed, I have no issues anymore.

For the record, I ended up wiping and reinstalling windows a total of 3 times, each time redownloading and installing any windows updates, then slowly working on and hand picking the graphics drivers from 4 updates back and bumping it up one at a time to see if a particular update was good. On the 3rd wipe and reinstall of windows, I performed a BIOS update and proceeded to download and install drivers etc, and things have been working smoothly ever since!!

I received an update about a new graphics driver version available… but did not grab it as I have not had any issues to date so far since doing what I last did, and dont want to fix what isnt broken anymore.

According to the program I was running, temps were sub 60 every time a crash occurred. As far as I know and believe, temp was not the issue, especially since its never been an issue for my set up.
What was unique about the 3rd and last attempt to wipe and install windows, was my efforts to go through and perform a BIOS update on my mobo. This was the only thing different that I did from the first 2 attempts, and so far, smooth sailing!! No more graphics driver timeout crashes or anything of the sort!!

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