If Blizz was a Gnome, I'd punt it! (Error #132)

[Limb0]

Last night, crash, Error #132. I figured, hey I'm in Dalaran, it's late, it's a sign to get some sleep.

4:30am
..I wake up, coffee, walk the pooch, log on in Dal. crash, Error #132 -rinse, repeat until I manage to port to Ironforge.
..seems safe, so I head to the ah -probably all the Dalaran problems I've been hearing finally got to me.
..talk to Auctioneer, UI blanks out, crash, Error #132 -hmm maybe auctioneer or my ui addons
..disable all addons, log in, Error #132 -log onto Tech Support Forums
..I read TECHNICAL ISSUES: Error and Crash Info
"8. Error 132

The Error 132 is a vague error message that is reported when something went wrong that was unexpected and not previously documented. This error can exist due to the actual code being faulty or system instability. This was the first type of error that was created when WoW was made. The other types of errors in this thread were once Error 132s before they were isolated and separated as to their individual causes."

..hmm well I followed another link there and went through the paces
-I removed all temp files (buh bye wtf), nope #132
-Updated my NVidia card, nope #132
-Ran the Memory Diagnostic, nope #132
-Tried running in OpenGL, nope #132

..removed Interface folder, nope #132



4 hours later and still no progress, I am ready to punt a gnome

[yssaril]

have you tried running the repair file in your wow directory? it will scan your game files and make sure they are nor corrupt

[Limb0]

Originally Posted by yssaril have you tried running the repair file in your wow directory? it will scan your game files and make sure they are nor corrupt

I hadn't tried this, since yesterday I did a complete fresh install from scratch..

I'm going to try again with no cache, no addons and no wtf, then will try the error checker.

[qaarh]

Unfortunately, error 132 can also mean you have faulty memory sticks.. Or an unstable graphics card (check heat levels).. or your CPU overheating..

I'd recommend switching the computer off for a few hours, then running a memtest86/ over night to see if you run into any errors.

It might work. I had similar problems and haven't had them very often since I replaced my faulty memory sticks..

Hope this helps!

[Dainton]

Grab Defraggler (or something similar) and defragment your WoW folder. Any time my game crashes I do this and it works fine afterwards.
It's worth a shot.

[Limb0]

Right on thank you all for the tips (just reading a few now)..

Heat? I am aware of its possibility but it's really np.

Mem sticks? hmmm I've never had mem problems before 3.2, usually I run around 50-67mb with full Auctioneer Suite, Lightheaded, UI elements, Tooltip, etc all running together. My pc was new in February and I've updated all the drivers. I'm gonna look into this..

Memtest? I previously ran the Memory Diagnostic from my PC which Blizz suggested and nothing came up..

Defrag? Definitely a great idea.. I regularly defrag with Auslogics-Disk-Defrag which a nerdier friend recommended to me from cnet.. works great, looks great, is great? yeah, it is..


So, I wanted to post that Blizz punted me instead, but I've been able to get back in game and begin to configure a few key addons (hope I can stay logged in)

[Limb0]

well, I found the group of culprits after redoing my UI from the ground up ..eesh, lesson learned (nerdrage sequence deactivated)

[Petrah]

And the culprits where..... ?

[Cralor]

Originally Posted by Silenia And the culprits where..... ?

Exactly what I was going to say. s/where/were

[Syxx]

Originally Posted by Silenia And the culprits where..... ?

Yeah fill us in! You can't do this kinda stuff on a forum man, it's just wrong! Information, we want information.

[Limb0]

..just taking a break from ToC

well Goingprice w/ Goingprice Allakhazam either h8s me or is conflicting with one of my addons.. seems I cannot disable some of the modules, and when i try to, Error #132.

I stripped down my addons significantly, so don't know if this was the only one causing the errors.