This damn #132 error

[Gray]

I know i am definatly not the only one to be suffering from this error message, its becoming quite a pain in the arse indeed.

The errors only started happening when the new patch was released about 2 weeks ago. Basically i could be anywhere in the game, flying, walking, on zepplin anywhere and it would just end up crashing the system.

I have checked the World of Warcraft forums on Blizzard, which state they are aware of the problem. There is hundreds of pages quite literally and i dont fancy sifting through all of them to attempt to see if it is sorted.

They say it relates to a memory problem somewhere, now, a few weeks ago, yes i would have said "yep! i completely agree".

The reason for this is simply that for about 6 months, the memory i had (Kingston KVR400X64C3A/512 -- running Dual Channel --- 1gb) has to my mind been causing unbearable system problems, blue screens (PFN_LIST_CORRUPT and more).

I thought enough was enough and purchased some new memory, in a hope that it would counteract the problem of getting the error #132 in WoW as well as the Blue screens.

I took out one bank of the Kingston memory while i waited for my new memory (Corsair 1GB DDR XMS3200XL Platinum TwinX) to arrive. I had to whack everything in game on low settings because the lag in places like Ogrimmar was not good. This did not help though as i was lagging like a bitch - BUT i found that while i only had one bank in (512mb) there was no crashes.

New memory comes, everything is hunky dorey, put everything back up on the settings, no lag. Excellent. Few hours into it *bang* error hits again, #132.

Before anyone says it - Yes, i have formatted, and yes, i even tried a different hard drive with new operating system to see if it would fix it. It has not. The options for this seem to be few and far between.

I have been told it might be the Windows Paging File, or something to that effect, or the Virtual Memory... I was wondering if anyone knew if this sorted them out? And if so - How is it done in Windows?


Windows XP SP2
BFG Geforce 6800GT
Soundblaster Audigy 2
1gb DDR Memory (Corsair) running Dual Channel
Abit NF7-S v2
AMD 3200+

 

[Vae]

I had the same problem and had to sift those forums. In the end it seems it was the motherboard drivers for my Asus A7N8X which were at fault. An update to the error 132 problem. So you might have to sift through the forums, specifically the Blue posts.

One thing to consider - Have you tried the memory in different slots on your motherboard?

 

[Gray]

Do you know which inparticular drivers that you had to update for it? This is an NForce2 motherboard, and it has everything like Firewire, LAN, Sound etc - But its all disabled...

Will have to check Nvidia later for any new updates

 

[Gray]

I went into the BIOS and lowered my FSB down again... The problem (Well..) is solved for the mean time, i did play for about 3 hours on the trot without a hitch.

I dont see though why it is necessary to have to go to lengths at lowering the FSB of the system...

Its not the memory at fault, ive tried 2 different brands and thats fine, it seems to be pointing in the direction of the actual Motherboard though... Well, what i'll do before making it that soundly, is install the PSU i have which is still wrapped up, see whether enough juice is actually getting to the system or not.

Another quicky - I checked the WoW forums, and made a post, its under the Technical forum, under "#132 error message" i think... That thread is over 16 pages long, but i can only view around 13 pages. It wont let me view higher than that.

Anyone got any clues how to fix?

 

[enigma]

I'm getting it aswell, allthough after I lowered the refreshrate in game to 60hz it happens very rarely.

I've done as you, tried everything from formats, hd changes, ram changes, bios, gfx settings, changed powersupply, os changes, chipset drivers, agp drivers, usb drivers, no case, fan blowing into case, switched places on various pci cards, severely underclocked my system to lag hell(sometimes it works, sometimes not), deleted interface /wdb/wtf/interface folders, I've even switched filesystems from ntfs to fat etc..

Started to crash instantly after the 1.3.1 patch for me.

 

[Zill]

I've been getting the same error messages too. It's damn annoying and seem to occur at the most inopportune moments. I've missed two MC raids last week as a result because of locking up and error messages, as well as a few other raids in BRS. But there's no way am I messing around with my BIOS settings to correct a problem not of my doing. I might try lowering my refresh rate.

As I understand from reading the Tech forums, this whole nonsense started ever since the patch update to correct a bug issue with Mac users . So the rest of us have to suffer as a result.

 

[Garax]

I found that putting my CPU back to stock speed solved the problem of #132 since the latest patch. However i hadn't had that problem since back when WoW was open beta in the US. When WoW went closed beta in the UK the problem had magically vanished and was able to overclock my CPU backup with no issues.

 

[Spankya]

I never bother overclocking processors anymore, seems to cause more hassle than its worth and things like these can occur. So thats definately one to look at Gray if you have overclocked it. I dont really see the point of overclocking the main CPU for gaming anyways, as most games just need lots of memory and a decent graphics card. CPU isnt that important unless you have some old machine with a 1GHz processor or something.

And Garax ya tart, how ya doing mate? Long time no speak!! And you Gray! Where r u playing nowdays?