View Full Version : WoW Error #132
SpliT71
01-05-05, 03:02 PM
I don't know if any of you have this problem but i just recieved it. I just bought another 512 stick of the same ram i have. Well not but 10mins into WoW it crashed. I cannot figure out why. I ran mem test and i got errors on both sticks, GOOD and supposedly BAD stick, im confused. Any insight is appriciated.
Robrules18
01-05-05, 03:55 PM
try it again with only one stick and see how thats works, if it works then its probably the ram if it doesnt then something got changed when you installed the ram, (i dont know enough about ram to help you with that aspect) but Crashes in WoW sometimes are WoW's fault I crash randomnly because of their unstable servers (which BTW are killing an awesome game). Also using UI mods like Cosmos, CTmod or Gypsie can cause crashes. Delete any UI mods you have and see if that helps. Other than that I dunno, but if it happened on Tuesday its a good bet it may have been the server (Every Tuesday since launch servers have gone down or bugged out).
Flashfx2
01-05-05, 07:17 PM
Well if you ran memtest and got errors on both sticks it is probably the memory that is causing the error. Are you running them at stock speed?
SpliT71
01-05-05, 08:28 PM
Yep stock speeds and everything. I just installed the ram and viola, started crashing. Now people on the WoW boards have found it's an overheating problem. They have increased the speed of the fan and lowered temps and haven't gotten the error, so it may be a heat issue, especially since i have an XPC.
Well let me add my two cents to the mix, I originally installed and ran WoW on an;
- Iwill KK266-R
- 1GB of SDRam
- 1400 T-Bird
- gForce 4 Ti4200 128MB
It ran fine up until Blizz released the 1.2.1 patch, then I started getting a crash everytime the game would boot up, RHM and I sat down and we tried everything. Found the HD wouldn't bench at all so we put another IDE controller in, that didn't fix it. We completely re-installed windows with SP1a, DX9.0C the latest nVidia's and the up to date Via 4-in-1's. Now let me tell you this confuses the hell out of me because this rig has run everything from UT to BF1942 and been a solid rig for years, even ran the HL2 demo. So then we tore it apart and took the board out of my wifes old rig, a Gigabyte something or other, didn't pay much attention to the actual model of it and built this;
- Gigabyte via board of some sort
- 512 DDR SDRam
- 1400 T-Bird
- gForce FX 5200 128MB
We did all of the above on a fresh install, got up to the 1.2.1 patch and it crashed again, now, this being the third day straight of playing about trying to get all this to work I was getting a bit frustrated. I mean the crashes literally were blue screening XP. After alot of investigation my wife came across a post at Blizzard where a guy found by installing the latest nVidia's his rig would just blue screen and reboot. We decided to give it a shot as it's been a real pain not having a rig to play on equates to everyone else playing WoW and me twiddling my thumbs :(
Went back into the nVidia archives and found these:
Windows XP/2000 (http://www.nvidia.com/object/winxp_2k_61.77.html)
Version: 61.77
Release Date: July 27, 2004
Figured what the hell, loaded them up and I'll be, it worked. Moral of the story if you have a nVidia and tried the latest drivers, try rolling them back a step and it just might clear up your issues, I may try the latest nVidia beta's and see if those will work but for now I am content just being able to play the game I've become slightly addicted to. :D
J :cool: Just my two cents
» BETA Drivers (http://www.nzone.com/object/nzone_downloads_winxp_2k_67.02.html)
» Version: 67.02
Just in case you want to try the beta drivers, I think I may give them a shot personally.
J :cool:
trueplaya4ever8
01-06-05, 09:54 PM
Man these errors are starting to **** me off, i cant even play.... error 132...... i have uninstalled and reinstalled and it just errors. i am done messing with it for tonite.
madcow235
01-06-05, 10:06 PM
I switched it from my 80gb to 120gb drive and voila no problems
SpliT71
01-07-05, 09:33 AM
I actually uninstalled the defragged, then reinstalled. I haven't had errors since. No updated or rollbacked drivers. And heat wasn't an issue.
» BETA Drivers (http://www.nzone.com/object/nzone_downloads_winxp_2k_67.02.html)
» Version: 67.02
Just in case you want to try the beta drivers, I think I may give them a shot personally.
J :cool:
***Update*** Just tried the 67.02's and no joy, BSOD and reboot, back the 61.77's for me, hopefully nVidia or Blizzard can get this fixed :(
J :cool:
trueplaya4ever8
01-07-05, 07:56 PM
U kno whats cool, I just Reinstalled WOW, then patched it, and went to play ...... BLUE SCREEN.... dont kno what the problem is, havent had this before. Until i got cosmos, then since i got my gig of ram its gotten worse. anyone have any ideas?
YellowDart
01-12-05, 05:49 PM
That sucks. I'm starting to get 132 errors too... I'm thinking it's an issue w/ the Cosmos UI. I didn't start getting these errors until I started using it.
I've also been getting strange lock ups. In mid-gameplay, WoW will freeze, the screen will go black, and when it comes back, I get this weird checkerboard graphic corruption. Haven't found a fix for it yet. I tried setting my CPU back to stock, and that didn't fix things. Now, I've got my 9800 pro dialed back to its stock settings. It hasn't done it again... but we'll see. I'll give it another stressful run again tonight to see what's up w/ it.
WoW is very stressful on any system, I had to turn it down to 800x600 to compete with the lag. Additionally make sure you are running the Cosmos.exe before you load into WoW everytime and you should notice there's not errors. They update cosmos fairly regularly.
J :cool:
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.