-
Newbie
[Ascent] Error #132
Hi, all! I downloaded and installed Ascent with NCDB, and got it running all by myself :batman: All was running like grease on axles until I updated my DB and Core two nights ago, using 2458 and 677. All of a sudden, I got error 132 at the end of the loading screen each time I'd try to log in to a character, upon which point, WoW crashes. Error details follow:
"This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal Exception
Program: E:\Program Files\World of Warcraft\WoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:0041B436
The instruction at "0x0041B436" referenced memory at "0x00000054".
The memory could not be read."
Before you suggest renaming WDB and Interface, know that I've already tried it to no avail. I checked my config files, but the problem wasn't there. Finally, I downgraded my Core, then my DB. Nothing works.
Any suggestions?
-
-
Omega
Re: [Ascent] Error #132
Made a new character & tried?
(Just to note #132 can be caused by many things, even official's tech support can't pinpoint it sometimes)
-
Newbie
Re: [Ascent] Error #132
I tried it, but no success. What next?
-
Omega
Re: [Ascent] Error #132
If that worked & this doesn't then try going back to the previous rev you were using
-
Newbie
Re: [Ascent] Error #132
I've tried that. I'm at a loss.
-
You don't know me.
-
Elite Member
Re: [Ascent] Error #132

Originally Posted by
Paco44
It's a database problem.
I agree, I've had the a problem similar to this.
Just download a fresh new revision and database and go with a clean install, make sure you have the right DBCs and maps...whatnot, so on and so forth
**EDIT** Also if you have custom items, vendors, or anything. Use a clean install(possibly use a new character) and try it, if it works only AFTER it works start adding in the customs until it stops working, keep checking yourself so if it's one of your customs causing a problem you'll know which one. ALSO...
go to your wow directory... C:\Program Files\World of Warcaft (whatever it is) and go to your Cache Folder and follow the folder WDB to enUS(or your language) and you'll see about 9 or 10 files in there. Called Creaturecache, itemcache, and so on. Delete all those cache files something stored may be causing the client crash.