-
What are the specs on your computer? Error# 132 is usually memory related. I am having the same problem at times and mine is a bad RAM stick somewhere.
Once you work through that problem, we can get the rest of the little things worked out. I went at least a month before I got everything working and it took alot of good people to help me get there. That is what is good about this site, we were all beginners and try to help others get up to speed.
-
If I exit the game with all of my toons at once (broadcast Escape, for example), I sometimes get that error.
It never occurs when they leave one at a time.
-
Spec:
HP Pavilion Elite e9280t PC
• Genuine Windows 7 Home Premium 64-bit
• Intel(R) Core(TM) i7-920 processor [2.66GHz, 1MB L2 + 8MB shared L3 cache]
• 8GB DDR3-1066MHz SDRAM [4 DIMMs]
• 1TB RAID 0 (2 x 500GB SATA HDDs) - performance
• 1GB ATI Radeon HD 4650 [DVI, HDMI, VGA]
• LightScribe 16X max. DVD+/-R/RW SuperMulti drive
• Integrated 10/100/1000 (Gigabit) Ethernet, No wireless LAN
• 15-in-1 memory card reader, 1 USB, 1394, audio
• No TV Tuner
• Creative Sound Blaster X-Fi Xtreme Audio
• No speakers
• HP multimedia keyboard and HP optical mouse
• Microsoft(R) Works 9.0
• Norton Internet Security(TM) 2010 - 15 month
• HP Home & Home Office Store in-box envelope
I just got this late Dec. 2009.
And YES, i purchased a pre-made because of the 2 yrs tech and warranty....Some will flame me, but that is okay! And yes, baby Jesus cried!
Doing a search for Error#132 on Google provides lot of other people with this, some the only way is to keep your computer cool. Reinstall and defrag does nothing. But I am curious, why only this affect the TeamShammy and not the Locky team, pally team, druid team and the priest? Only affect the shammy in WoW2 account!!!!
I uninstalled the video card driver, got the OEM driver from their site and reinstalled, and result is sometimes it works and sometimes it doesnt. What gives?
SaraiE
-
first of all, theres nothing wrong with buying premade.. were not all tech wizzards are we.
can i ask if you are using the isboxer way of creating virtual wtf files for each character?
before i started using isboxer i had lock ups and crashes like yours when i closed all the clients simultaniously and i'm pretty sure its because the os locks the file to the first client trying to write to the wtf and then falls over trying to save settings and wotnot to wtf whilst its already being written to .
I found that closing them separately, one at a time resolved the issue i was having.
Since i started using the wizard in isboxer i never had the problem as the wtf's are all seperate for each account.
just a thought..