ERROR #132

Account or connection issues

ERROR #132

by darkfoxx » Sun Jun 28, 2015 9:10 pm

I am getting an error with wow that crashes and says:


==============================================================================
World of WarCraft (build 5875)

Exe: D:\WoW_1.12.1_enGB_Ready\WoW.exe
Time: Jun 28, 2015 5:05:59.978 PM
User: "Removed for security"
Computer: "Removed for security"
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal Exception
Program: D:\WoW_1.12.1_enGB_Ready\WoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:006C7712

The instruction at "0x006C7712" referenced memory at "0xCA40D826".
The memory could not be "read".


WoWBuild: 5875
------------------------------------------------------------------------------

----------------------------------------
x86 Registers
----------------------------------------

EAX=00000031 EBX=2077E008 ECX=00000000 EDX=651C651F ESI=65247307
EDI=0018F980 EBP=0018F988 ESP=0018F968 EIP=006C7712 FLG=00210246
CS =0023 DS =002B ES =002B SS =002B FS =0053 GS =002B
darkfoxx
Grunt
Grunt
 

Re: ERROR #132

by Bufallo » Sun Jun 28, 2015 9:14 pm

Same here, anyone is having the same issue ?
Bufallo
Tester
 

Re: ERROR #132

by Gentnovic » Sun Jun 28, 2015 9:25 pm

Same error here and many people ingame complaining about the exact same error. I am instantly getting this error message, when I enter the world with one of my chars.
Gentnovic
Tester
 

Re: ERROR #132

by matw1990 » Sun Jun 28, 2015 9:29 pm

Im having the same problem everytime i log in, tried re installing. worked for a minute, then had another error
matw1990
Tester
 

Re: ERROR #132

by shadowanker » Sun Jun 28, 2015 9:38 pm

I was just online and almost everyone was getting this simultaneously. Everyone thought they had solutions at first but the error kept coming back. This is a server issue and needs to be fixed ASAP. The game is currently broken.
shadowanker
Grunt
Grunt
 

Re: ERROR #132

by shadowanker » Sun Jun 28, 2015 10:15 pm

Whatever it was, I think it's fixed now. Will report back if it happens again.
shadowanker
Grunt
Grunt
 


Return to Support