Lately when using (and only when using) Arelog do I get the "Wow Crash #132". I've looked into it and usually they say that it is a random crash that may be due to bad ram or something. But why has it never happened and only happens with Arelog? Any ideas? PS the Error occurs right as wow is launched
i posted this on the arelog thread several times, no love ie no answers.......i can understand your desperation!