Infamous Error 132

[irishllama]

I tried posting on the official forums, but alas no fix was given to me. I'm still randomly getting error 132, and sometimes Error 131 (File corruption).
I've tried the blizzard repair, and it found corrupted files and download/fixed them. Still the 132's are pretty frequent, and sometimes WoW just hard freezes and I have to manually turn my computer off.

I'm running the following specs:
X2 3800
7800GT
1.5gb Ballistix Ram (Crucial)
Sound Blaster Live! 24 bit
W.D 250gb SATA
Asus a8n sli-premium.
Neo Power PSU.

I know it can't be heat related issues, as I have a antec 900, all the fans are always on High.

If anyone can fix this, or attempt to make the errors more sparse, Please do!

[Kalos]

How did you achieve a total of 1.5 gig of ram? What stick configuration do you use?

[irishllama]

How did you achieve a total of 1.5 gig of ram? What stick configuration do you use?

3 sticks of 512mb.

Yeah.. I know it isn't favored to do this, but I ended up getting a deal on an extra stick.

[Kalos]

Is the extra stick exactly the same as the other two, in terms of speed, source, capacity, and manufacturer? The timings must be identical. Try running Memtest (Google&download) to see if your configuration is stable or not, for at least twelve hours or one full cycle, though some errors don't become noticed until the third cycle of testing in my experience.

I must admit, the primary cause of error 132 is a bad selection of addressed memory, one of the memory caches must be of poor quality or otherwise inferior in order to create a bad patch. When WoW writes something to this memory, it simply isn't recorded and held properly, when WoW then needs that file, relying on it, and tit isn't there properly to be read; there is a crash with Error 132 given as the coded cause. Something in your computer's hardware stinks and can't be reliable.

[irishllama]

Is the extra stick exactly the same as the other two, in terms of speed, source, capacity, and manufacturer? The timings must be identical. Try running Memtest (Google&download) to see if your configuration is stable or not, for at least twelve hours or one full cycle, though some errors don't become noticed until the third cycle of testing in my experience.

I must admit, the primary cause of error 132 is a bad selection of addressed memory, one of the memory caches must be of poor quality or otherwise inferior in order to create a bad patch. When WoW writes something to this memory, it simply isn't recorded and held properly, when WoW then needs that file, relying on it, and tit isn't there properly to be read; there is a crash with Error 132 given as the coded cause. Something in your computer's hardware stinks and can't be reliable.

I ran Memtest a while back, before I started playing WoW, but I'll try it again when I get home. Yes the memory is all the same, same timings, manufacturer, same everything.

[Kalos]

Ok, make sure Memtest has plenty of time to run, I've had incidents where bad sectors have escaped detection first time round, but doing more than one full sweep mysteriously found bad sectors which previously had gone undocumented. I have left it running on some PCs where memory related issues have been happening for over 24 hours just to rule out false negatives.