World of Warcraft constantly crashing - UPDATE

[DVad3r]

My world of warcraft crashes constantly. Sometimes it takes a few min sometimes longer. The error it crashes to is error # 132. My setup is a 3800 X2 dual core, 1 gig ram, 7800 GTX, and 2 250 gig seagate SATA hard drivers.

Apperently from scoping around WoW forums there are SERIOUS issues with the game and dual core chips. I have not been able to find anything on the matter. If you can help me solve this problem ill paypal you 10 bucks.

Thanks.


UPDATE !!!!

After almost a week of madness troubleshooting, I think the problem might be solved.

Faulty memory, the corsair pc 4400 seems to be defective. Tried my friends memory in my system and it runs perfect, put mine in his and his crashes.

Funny how that is though since I ran numerous mem tests and everything was dandy.

I am going to play all night tonight with his memory and see if I get any crashes, for now the performance has been sweet and everything stable.

Good thing corsair has lifetime warranty, now just dishing out 4 bills for a 2 gig XTC ram set from OCZ is gonna make me kinda depressed, thx everyone all for trying to help.

 

[Noema]

Did this begin with 1.9?

I suggest you try playing without addons, specially the outdated ones. Many addons are poorly coded and can be very bloated. I used to have over 30 UI mods and the like and the game barely ran anymore, and it crashed a lot. Now I play only with CT_Raidassist and performance is loads better.

Also, move or rename your WDB and WTF folders, as well as your interface folder (they can be found in the WoW directory). This is because they tend to get corrupted. You'll have to reload your settings but that usually fixes it.

EDIT: WoW is also very picky with RAM...if one of your sticks is even slightly defective, WoW won't run well, even if other games do run without hitch. Have you tried Memtest to check your RAM?

 

[Malladine]

132 is still around?

That's a bad one, sorry.

I'm guessing you've fully reinstalled already? All the latest drivers of everything?

 

[Cheetah8799]

Originally posted by: DVad3r
My world of warcraft crashes constantly. Sometimes it takes a few min sometimes longer. The error it crashes to is error # 132.

Try the official Blizzard forums.

http://forums.worldofwarcraft.com/threa...-support&t=308254&p=1&tmp=1#post308254

 

[Noema]

Originally posted by: Malladine
132 is still around?

That's a bad one, sorry.

I'm guessing you've fully reinstalled already? All the latest drivers of everything?

The thing is 132 is the general 'something went wrong and the application will now close' error message...so it's hard to know what happened and exactly what went wrong that caused it. I used to get it when using Teamspeak until I updated my motherboard drivers.

You probably read it already but here is Blizzard's official error 132 thread.

 

[DVad3r]

I have read the 132 support thread, the only thing I have not tried is the memtest. I have 1 gig 2x512 of corsair TCCD pc 4400 ram. Like noema said it is a very general error and can be a number of things.

Prior to 1.9 the game crashed once in a while...it was still playable though sometimes not crashing for hours, and sometimes never. I had cosmos and uninstalled it after having numerous problems with it in 1.9. I also deleted my interface folders, WTF and WDB.

As for drivers yes I have the latest everything, bios, vid, sound, network, chipset. 1.9 definetely gave me waaay more crashes, so I don't understand what changed. I have been on the WoW forums and made several posts, and no response from blizzard guys yet.

I am going to try memtest in a sec, and see what happens.

Just for the record, my system is overclocked but is stable in prime95 and my other games run fine. I also have the microsoft dual core hotfix installed and enabled. 10x221 2210 mhz 1.375 volt, 2.8 v ram, 2.5 4 4 8 timings, 4 HTT, 1 T command.

 

[Malladine]

This and the crashing after quest hand ins are errors that have been around for many months now. Blizzard needs to step up and fvckin fix their problems.

 

[cKGunslinger]

Originally posted by: Malladine
This and the crashing after quest hand ins are errors that have been around for many months now. Blizzard needs to step up and fvckin fix their problems.

The quest turn-in crashing was major, but seems to have been fixed (I haven't heard of any complaints in a while.) The "132" error still, to me, seems to be related to hardware memory interface and timing setups, and has little, or, more likely, nothing to do with the software.

It very simliar to Unreal Tournament's low tolerance for over-clocked systems. I had a rock-solid stable system that happened to be overclocked, and as such, it randomly crapped-out of UT. I tried everything to correct it, but the only thing that actually worked was turning back down the memory and FSB timings on my hardware. Everything else I had worked flawlessly with my OC'd system, but that one game, and it was the same for many, many other people I talked with online.

It's hard to blame the SW for something that can be corrected by defaulting the HW back to spec limits. We software developers aren't miracle workers, we can only make things work for how things should be, not how they might be.

 

[DVad3r]

I just ran the microsoft mem test. Went through 2 passes, no errors.
I also tried downclocking my system to stock speed and still get the crashes, so obviously it is not the overclock. My memory timings are stock for the memory I have, 2.5 4 4 8 is not aggressive at all. There are other timings in the bios options but I have no clue what those do and I did not touch them.

I should also mention that my motherboard is an Asus SLI Premium. Anything else I can try?

 

[Malladine]

Originally posted by: cKGunslinger

Originally posted by: Malladine
This and the crashing after quest hand ins are errors that have been around for many months now. Blizzard needs to step up and fvckin fix their problems.

The quest turn-in crashing was major, but seems to have been fixed (I haven't heard of any complaints in a while.) The "132" error still, to me, seems to be related to hardware memory interface and timing setups, and has little, or, more likely, nothing to do with the software.

It very simliar to Unreal Tournament's low tolerance for over-clocked systems. I had a rock-solid stable system that happened to be overclocked, and as such, it randomly crapped-out of UT. I tried everything to correct it, but the only thing that actually worked was turning back down the memory and FSB timings on my hardware. Everything else I had worked flawlessly with my OC'd system, but that one game, and it was the same for many, many other people I talked with online.

It's hard to blame the SW for something that can be corrected by defaulting the HW back to spec limits. We software developers aren't miracle workers, we can only make things work for how things should be, not how they might be.

I was getting 132 errors on a perfectly stock rig. All drivers up to date.

 

[DVad3r]

While Gunslinger has a point, this does not apply to WoW. There are mass amounts of people that have similar problems on normal stock systems of variety. Blizzard has clearly admitted to issues with WoW and dual core chips, and seems to ignore everyone else that has problems with "normal" systems.

 

[cKGunslinger]

Originally posted by: Malladine
I was getting 132 errors on a perfectly stock rig. All drivers up to date.

Interesting, is it an Asus MB as well?

 

[Malladine]

At the time I was getting the errors I think I was using a gigabyte board.

My best lead on the reason for 132 is overheating...the gigabyte board ended up dying due to bust capacitors.

 

[cKGunslinger]

Originally posted by: DVad3r
While Gunslinger has a point, this does not apply to WoW. There are mass amounts of people that have similar problems on normal stock systems of variety. Blizzard has clearly admitted to issues with WoW and dual core chips, and seems to ignore everyone else that has problems with "normal" systems.

As a system developer, I'll offer this. If you have a product that satisfies 95%+ of your customer base, there is a very limited amount of resources (time, effort, money) a profitable company is willing to invest in trying to appease that unsatisfied 5%.

I know that sucks, but that's the way it is. Of course, you never come right out and tell them that you're abandoned them, you simply offer up some low-hanging fruit fixes, then promise that you are still researching.

I mean, you all saw Fight Club and remember Norton's little speech about and car manufacturers' reasons for recall vs lawsuits/settlements. It may sound callous, but that's the way most all businesses are run. I'm sure Blizzard has run the numbers on cancelled accounts + bad will and negative publicity due to queues, system instability, crashes, etc and compared them against the the costs of extensive software analysis, debugging, retesting, etc and have foundit to be an unworthwhile attempt.

Like they say, 1 billion Red Chinese can't be wrong. :laugh:


That said, I know I'd be royally pissed, if say, after a new patch, my system is irrevocably unplayable.

 

[Fingolfin269]

I used to get error 132. I had my computer overclocked and supposedly stable as it ran everything else without a hitch but WoW just wouldn't work without that error popping up.

I set everything back to stock speeds and it works just fine. And since I'm addicted and that game is all I play now I don't care about having my system OC'd.

 

[CKent]

What's your power supply?

 

[DVad3r]

Originally posted by: cKGunslinger

Originally posted by: DVad3r
While Gunslinger has a point, this does not apply to WoW. There are mass amounts of people that have similar problems on normal stock systems of variety. Blizzard has clearly admitted to issues with WoW and dual core chips, and seems to ignore everyone else that has problems with "normal" systems.

As a system developer, I'll offer this. If you have a product that satisfies 95%+ of your customer base, there is a very limited amount of resources (time, effort, money) a profitable company is willing to invest in trying to appease that unsatisfied 5%.

I know that sucks, but that's the way it is. Of course, you never come right out and tell them that you're abandoned them, you simply offer up some low-hanging fruit fixes, then promise that you are still researching.

I mean, you all saw Fight Club and remember Norton's little speech about and car manufacturers' reasons for recall vs lawsuits/settlements. It may sound callous, but that's the way most all businesses are run. I'm sure Blizzard has run the numbers on cancelled accounts + bad will and negative publicity due to queues, system instability, crashes, etc and compared them against the the costs of extensive software analysis, debugging, retesting, etc and have foundit to be an unworthwhile attempt.

Like they say, 1 billion Red Chinese can't be wrong. :laugh:


That said, I know I'd be royally pissed, if say, after a new patch, my system is irrevocably unplayable.

Yep that's 100 % true. I already felt and knew that they don't care about my problem, they were not even replying to the threads we posted on the blizzard forum. I am going to suck it up, complain 24/7, and play the game because cancelling an account to a game I am addicted to won't change anything. I am just hoping for a fix to the solution that someone knows about it could work.

 

[DVad3r]

Originally posted by: RBachman
What's your power supply?

OCZ Modstream 520

 

[zzzz]

Have you tried playing a shaman?

 

[cKGunslinger]

Originally posted by: zzzz
Have you tried playing a shaman?

:thumbsup: :laugh:

 

[DVad3r]

Originally posted by: zzzz
Have you tried playing a shaman?

Haha naa Im a hunter.

 

[phantom404]

I would try RAm. I had the same problem unti i switched memory modules and never seen the 132 again. I ran memtest and all pasted but for somereason wow was crashing and this fixed it for me

Also on a note, I do have a dual core processor and havnt had any issues

 

[DVad3r]

^

 

[skace]

I'd say roughly 80% of all issues people have with gaming rigs these days are due to heat and power consumption. Yea, I know I pulled that number right out of my ass but its true. It has happened to me, it has happened to almost everyone I know.

I can tell you right now that your system is very close to mine specwise. I have a 3800 X2, 2GB of ram, 7800 GT, 1 74GB WD Raptor. But mine isn't overclocked and it runs WoW perfectly fine. I've also put a lot of time into keeping it cool and bought a very good Enermax PS.

The only thing I can say is that before I even tested WoW on my dualcore rig I had installed the AMD x2 driver as well as the microsoft hotfix for dualcore. I've also installed the 82.12 nvidia forceware beta driver because it is supposed to have improved dualcore performance.

 

[hooflung]

3800 X2 w/ 6800NU ( unlocked and Oclocked ) w. 2gig DDR400

no problems here in 1.9 but I don't use any interface mods