More than 2 instances of Wow

[Friedpickles]

I've had error 132 before on two different machines, and it had two different causes. On one machine, it was heat related (and crappy motherboard related), something on my motherboard was heating up too much and I'd get a full crash and that error. The other one, more recently, was on my wife's computer. She had a stick of RAM go bad on her, and would consistently but randomly get this error.

So if there's two causes, there's probably more...ugh...

To rule out heat and overtaxing of things, try closing off all your WoW's, logging in one session and go into the options. Turn evvvvvvverything down to minimum. Like lowest graphics quality, no sound, no AA, low low low. Save that, quit the game fully to ensure the config.wtf is created with the new settings. Then try firing up two WoW's, logging both in, if all is well, try a third. Go baby steps.

If that works then perhaps it's just a load issue or heat or something, it probably is less likely to be bad memory at least. If it happens then too, perhaps running a memory checker is in order.

Thank you for the advice, I'm willing to bet it might be heat/mobo related but will run a memory checker at a later point. Worse case scenario newegg.com has plenty to sell me I guess :-)

[Psych]

Thank you for the advice, I'm willing to bet it might be heat/mobo related but will run a memory checker at a later point. Worse case scenario newegg.com has plenty to sell me I guess :-)

Sometimes you just need these little pushes to get on the upgrade bandwagon

[wowphreak]

Maybe yer comp is harboring lots of dust bunnies? clear em out :P

barring bad memory another thing that'll help is to disable as many system services as you can this will free up some cpu cycles.

another thing is to go start-controll panel- system and click advanced tab click on setting for performance and set it to "adjust for best performance" makes the gui look ugly but it'll help some.