Error #132

Support Technical Support
1

Yesterday I had three error #132 crashes. This my computer did not completely freeze but I had to restart WoW in order to play. Here is a copy of the message.

World of Warcraft: Retail Build (build 32638)

Exe: C:\Program Files (x86)\World of Warcraft_retail_\Wow.exe
Command: “C:\Program Files (x86)\World of Warcraft_retail_\Wow.exe” -launcherlogin -uid wow
Time: Nov 24, 2019 8:36:27.773 PM
User: cbarr
Computer: DESKTOP-QDK5NQA

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program: C:\Program Files (x86)\World of Warcraft_retail_\Wow.exe
ProcessID: 9256
Exception: ACCESS_VIOLATION

The instruction at “0x00007ff69c485ed0” referenced memory at “0x00000000000000e9”.
The memory could not be “read”.

<Exception.IssueType> Exception
Crash
Exception.Summary:
ACCESS_VIOLATION
(DBG-OPTIONS DBG-ADDR<00007ff69c485ed0>(“Wow.exe”) <- DBG-ADDR<00007ff69c48b8c0>(“Wow.exe”) <- DBG-ADDR<00007ff69c48b51b>(“Wow.exe”) DBG-OPTIONS<>)
The instruction at “0x00007ff69c485ed0” referenced memory at “0x00000000000000e9”.
The memory could not be “read”.

2

I have am AMD 5700 XT with updated drivers and an MSI z390 gaming edge ac with current bios as well.

3

This is so frustrating. I just got another error #132 and I have no idea what is causing it.

4

It’s still no end in sight. I believe the culprit is my video card but I’m not sure. Blue, please check the logs. If it is the video card I need to replace it asap. It’s frustrating not being able to play WoW without worrying about crashes.

5

Hey, Veneno!

The crashes are all over the place. It is some sort of system instability issue, for sure. Have you been experiencing driver crashes or Windows Bluescreen crashes?

Please collect a DXDIAG and post it here using the Preformatted Text button in the posting options. Just make sure the full DXDIAG contents are between the Preformatted Text tags.

6

Ive been having the same issue the past week.

8

A post was split to a new topic: Dlog - Error 132