I feel your frustration, wizard
Gotta love young males and their dimwitted and halfassed 'write-you-off' kinda remarks. It's something I get alot from ignorant children who think they know everything and instead of trying to be helpful, they either ignore you or leave some dimwitted comment like the two above have left.
I think what you're dealing with is the same thing I have concluded; bad RAM. Whether it was bad from the beginning, or just went bad, it's most likely the culprit. I've spent just this weekend having the last I could stand from my wow crashing all the time to Error 132s, just like you've been experiencing. I have no where else to go except that it might be my memory going into the ****ter. Fortunately, they are either tell-tale signs now of what is to come later, or just when wow is accessing that area of memory addresses, it can't access them.....so you get a crash. Unlike HDD sectors, where you can mark them bad and avoid them, you can't on your sticks of RAM. Either go through a time period of downtime while they are replaced via warrantee, or go buy new RAM. I would suggest buying a top name brand, with the highest timing you're willing to afford. Unfortunately, it's going to be a money spent now, or money you'll spend later. Crucial and Samsung are good brands to go with, and I wouldn't stray far from there.
In fact, I'm going to go buy some new RAM this weekend, because I don't like to wait for the warrantee. Besides, it's money well spent. I haven't had to replace my RAM since I crafted my machine almost 5 years ago. Pentium 4, 2.4GHz Prescott on a P800E Asus board. It's been an awesome machine, and I'll probably hang on to it for a good few years to come.