Error 132 and random crashes

Hello, I tried to search on the forum but didn't find much, if the question has already been asked and replied, please delete this topic, thanks!

As title says, I get error 132 random, specially in arena, causing me the loss obviously. When I afk in the city or I run around waiting for the que I never crash or something. I started to think that maybe it was Sound Alerter that gets too much data and overloads the game, also because in some arenas it is completly mute for no reason (maybe combat log bugged idk), in other arenas it works perfectly. It's not a stable addon, at least for me, but I honestly don't know if this could really cause a crash.
Other times, this specially in PvE, instead of error 132, I get all frozen with WoW window stuck not responding, and I have to force Alt F4 and relog as fast as possible. Some times when I relog, I find myself in Elwyn Forest human starter zone for no reason, don't know why.
I read everywhere about crashes and particulary error 132, but this error kinda means nothing and everything at the same time. I mean it can be my computer old, my graphic card too hot, but it can be also the game itself, maybe some addon..there is no specific information when error 132 occours, about what caused it, if it's a software or a hardware problem (afaik)..So I'm lost. I'm not using any patches or model edits, or MoP client, and i have just gladius, soundalerter, grid, cooldowns. I mean my UI is pretty basic and it's not overloaded with tons of addons. The heaviest addon I have is Grid which is 2MB around.

Anyone have some suggestion to reduce these crashes? I wouln't care much, but they happen always in the worst moments.

Thanks.