WoW Crashing Error #132

[alcattle]

Anyone else been getting this? Since last update last week, WoW has been crashing. Sometimes only one toon, never same one, but now even solo. I tried restarted, running virus scans, no add-ons, no launcher, deleted the WTF and interface folders. Still happening. Put a post on WoW Tech support, not much help yet. gggrrrrrrr :cursing:

[Jafula]

Are you deleting your cache folders as well?

[alcattle]

no, I deleted WTF, WDB and interface. I will also try the Cache file now

[alcattle]

still crashed, solo and tri-box.

[Svpernova09]

#132 is a generic "oh shit something went wrong /crash" error. You need to read through the rest of the error and see what caused it. Saying you got a #132 is like telling a mechanic your car won't start.

[Oswyn]

What Svper said. When I had this error, I ran the game repair and it fixed it all up good.

[d0z3rr]

Sounds like one of the mpq file is messed up. Try the game repair like Oswyn said, it can take a long time to run, so set it and forget it.

[Basilikos]

When I was getting #132 a long time back, it was actually due to the RAM not getting enough voltage. The issue is determining what is causing your particular error #132.

[blast3r]

Check your free hard drive space. That can cause errors as well.

[Ualaa]

I've had 132's in the past.

The repair tool has always fixed them.
I periodically still get 132's, which now say something about memory (bunch of numbers) could not be read at (bunch of numbers).
It's very infrequent, repair tool doesn't fix it.
But its one crash every 20-25 hours of play time.
Wouldn't mind a fix, but not a major deal either.