Quote Originally Posted by Friedpickles View Post
ERROR #132 (0x85100084) Fatal Exception
Program: C:\Program Files\World of Warcraft\WoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:007D03C8

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

----
Yea i have the trials set up so now i feel like im on a deadline or something lol. I have the RAF setup I just cant login more than 2 toons at the same time. I can for example get all 5 logged into their character screens but more than 2 instances of the actual worldserver up and running and it crashes.

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.