OKay -- if you're getting a "cannot access memory" error from Vista and WoW is not producing an error log, then you're looking at a much larger problem which is not related to any of your mods... either its a huge WoW bug which is causing a memory address violation (like a nil memory pointer) or you have a physical memory error in your computer -- bad memory chip, a paging fault, cache file problems, etc. One way or the other, the symptoms you described here are those of a computer problem and not a Mod or WoW problem.
Originally Posted by Alarra
Thanks for clarifying the issue. The reason I say "memory leak" is that is what my system is telling me when i crash. it's a "cannot access memory" error and sends it to microsoft. The problem is this, it's not showing up as a game crash in my vista control panel for fixes to errors so I dont know the exact problem. if I could go into the error reports and see why WoW is crashing I could get a better handle on it. Like I said in my last post though, I'm going to disable the stat addon that switched omen/recount on combat and see if that is the problem.
|