Error 132

[Maxgirth]

Wouldn`t it be a great idea if blizzard incorperated a server to deal with this problem, that was actually available.
Normal scenario,get invited or start group, make way to instance, about to start, 132 spam.
Relog, place in queue 366..240..130..82...15.... 132 spam, grrrrrrrrrr.
Finally log on and all the guys you were in SM with are now level 60, and don`t need you anymore.
From the many forums i`ve visited, i`ve tried all the basic solutions to no avail, I have re-installed game..swapped ram..don`t wear blue sox on a monday...never suck diesel from a tractor..nor put jam on a magnet.
What`s really needed is the server to be up and running that deals with each individual error,not to much to ask for from a paying customer, is it?
A major problem that needs addressing.
Rant over.

 

[Evoknox]

http://forums-en.wow-europe.com/thread.aspx?fn=wow-tech-support-en&t=64570&p=1&tmp=1#post64570

It appears to be bad memory, test it with the link provided in the blizzard post. If it is bad memory, it's obviously not Blizzards fault

Always check the blizz tech forums when you get the same error over and over again, 90% chance there's a blue post of it there.

 

[Maxgirth]

http://forums-en.wow-europe.com/thread.aspx?fn=wow-tech-support-en&t=64570&p=1&tmp=1#post64570

It appears to be bad memory, test it with the link provided in the blizzard post. If it is bad memory, it's obviously not Blizzards fault

Always check the blizz tech forums when you get the same error over and over again, 90% chance there's a blue post of it there.

Iirc the memory test thing is for error 131,I looked at severall posts on the tech support forums, many solutions for many different 132 errors.
But (fingers crossed) since last patch, 132`s seem a distant memory.
Now shall I gamble on d/l TS and another UI again.

 

[Garax]

I read through that as i was getting random 132 errors. I followed the advice to disable the triple buffering option within the graphics options and i haven't had the error since. Hope this helps you with this fuckin annoyin error!

 

[Maxgirth]

I read through that as i was getting random 132 errors. I followed the advice to disable the triple buffering option within the graphics options and i haven't had the error since. Hope this helps you with this fuckin annoyin error!

Last night was fooking terrible, i`m not a very techy type person,so i`ve copied the error ( it`s imprinted into my memory now ), and if you or any other peeps reading this could help, i`d be eternally grateful.

This application has encountered a critical error:

ERROR #132 (0x85100084)
Program: E:\World of Warcraft\WoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:00080101

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


WoWBuild: 4375

Thanks in advance.

 

[enigma]

I get that exact error aswell. Doesn't happen every day, but when it happens it doesn't happen only once. I've tried everything written in any blue post about this issue on both the eu and us forums and nothing changed. Started exactly after the 1.3.1 patch came.

 

[Cylian]

#132 is a problem with your gfx-card memory. Think it's the memory getting too hot, since if I just open the case and aim a fan at the gfx card it doesn't happen at all.