World of Warcraft®

Hi all,

After a bit of tearing my hair out regarding intermittent Error #132 crashes I've finally come across a tested and confirmed reason for this crash.

This diagnosis only concerns: -

• ERROR #132 (0x85100084)
• Crashes that happen intermittently (not regularly on log-in)
• Crashes that in the error logs show a referenced memory at "0x000000000000001C"

As strange as it might sound, I have confirmed (and so have others on the US forum) that this crash occurs when another account that you enabled via Refer-A-Friend logs in.

I have tested this several times with my RaF buddy and it is now proven.

This bug is actually one of the craziest I have ever seen in my seven years plus with this game and I couldn't quite believe it until we tested.

Hopefully this will allow other people to stop wasting their time trying to diagnose the issue and wait for a patch release by Blizzard (A blue confirmation that this bug has been logged would be nice too!)

Well this cant be because I do not have a RAF and I get this same problem as do everyone else that gets this problem. So it has nothing to do with RAF but just purely blizzard that has to fix the new patch problems.

I get same error again while paying nothing is wrong untill I want to do a raid or dungeon.

Hi Zeozordon,

I think you must have a different problem then, as the issue I have described above is 100% confirmed.

Error #132 has a number of different causes, but please look at the section in your crash report that says Instruction at "0x0000000140297DC4" referenced memory at "0x000000000000001C" to see if it is the same issue.

I have now confirmed this issue with several more players, both in the EU and US.

OK. I do get the exact same 001c error. And like you was trying many options. At the same time my girlfriend was logging in and out behind me (due to graphical issues on the game on the laptop).

So, this explains everything.

Just tried it and indeed it did cause the crash as she came to character select screen.

Come on Blizz. Sort it aaaat!

Thanks for the heads up :)

Its the Same Code, but it was happening when my RaF Wasn't Even logging in, he had got the 90% Big so went offline for around 2 hours, Yet i still got around 5-8 Crit Errors in that time.

Are you sure that you don't have any other RaF that you have forgotten about?

And when you say the same code, do you mean the Error #132?

RAF issues without any doubts.

Thanks for the comment Doom, however I don't really want this thread to turn into people pasting their error logs because the diagnosis part has been completed. We just want to make sure that Blizzard have seen this problem, know how to recreate it and have put it in their bug backlog.

I'd rather people used this thread to test out if this is what is causing there problem, and then post to confirm, so we can see how many people are affected and what priority the fix should take.

As we all know the #132 errors can mean a million and one different things, and threads often turn into chaos when people start filling them up with logs. I've removed the memory address from the first post as I agree that is confusing.

Sorry my mistake, just saw that it is a diffrent instruction. how could I have know that programmers would give an same error code for multiple errors....best of luck on your problem hope ours also get sorted out soon or MoP wont see me.

Oh wow, I did notice a couple of my crashes coincided with my boyfriend logging in, but then other times he logged in and all was fine so I thought it was just bad timing... I only RAF'd one of his accounts (and my other account was not linked to either of his), so it's making sense. Will have to test this some more, but at first glance it seems to add up, especially since I'm not crashing now he's at work. Well done whoever figured that one out!

Just completed some further tests with my RaF buddy and the crash happened 20 out of 20 times and has not happened once outside of these log in scenarios.

As a side note, my RaF buddy is in Romania and I am in the UK, so there cannot be any relations to local network settings or firewalls.

30/08/2012 13:35Posted by Ursari

Just completed some further tests with my RaF buddy and the crash happened 20 out of 20 times and has not happened once outside of these log in scenarios.

One thing I noticed is that sometimes it does it as soon as she gets on the character select screen. Other times it's after I see the real ID toast (I thought I was going to survive it when I saw that). But it does always happen.

So, now whenever she needs to relog. She lets me know. So I can exit so my addons save their data at least.

Annoying, but better than losing my accounting from AHage.

I can confirm I'm having the exact same problem, my RaF logged into the character selection screen and it made me have this error. It's happened 100% of the time we have tried this out.

This is my error log: http://pastebin.com/TFqHEewD

Without the error log we cannot assist in this case. Please can you post the full log, that'll help us look into this.

In the nicest possible way I can say this.

You've been given clear steps to replicate the issue. You don't need a full log. You can create accounts with the RaF links as described. Then you're able to create the issue yourself. So can your developers who can do this with debuggers attached to the processes and actually see exactly what's going on.

My point being this clear method of reproducing the issue is actually BETTER than a full error log.

30/08/2012 14:13Posted by Lurdlespor

Andrai, we are testing this issue but so far have been unable to reproduce it.

That's fine. I understand, but you have several accounts mentioned in this thread (and the US one) that you can look at for clues.

I'll try and give all the info about my account that may help.

1: Our accounts were linked on 4th December 2011 (and so the actual link has expired for the purposes of benefits).

2: We're both Real ID friends (other friends logging in doesn't cause a problem)

3: We're in the same guild (but I have other friends also in the same guild on Real ID that haven't caused the crash).

4: We're on the same network (but me logging in doesn't disconnect her, and other people in my house don't disconnect me and vice-versa etc).

EDIT:

5: May be pertinent. I have upgraded to MoP (The referrer). Her account (the referred) has not been upgraded yet. Not sure whether that matters. I may upgrade her account later and see.

Also, if you'd like access to the accounts in question (or devs do) please feel free to contact me via email to discuss it. I'd be happy to help.

EDIT: http://pastebin.com/xaMKf4a9 error dump I just reproduced. I removed wtf/cache/interface folders. Just to remove that from your concerns.

30/08/2012 14:13Posted by Lurdlespor

Can you also test in DirectX 9 mode as well? Just to test the cause.

Aha on this subject I can say I've had it happen in X64 client, DX11 and DX9, and X86 client I think also on both DX9/DX11.

I thought the X86 option fixed it last night. But it just coincided with my girlfriend getting bored of the problems causing her client to close (I suspect graphics) and shutdown for the night. Hence I got no more crashes.