Critical (#132) but only under certain ingame conditions

[Subseven]

Hi, i don't know what's suddenly going on - my client recently crashes with a critical error ONLY when I'm in a raid group while standing near the portal stone to the emerald nightmare. If I am alone there or in a normal group, the game continues as normal and I have no problems. After a relog (while part of a raid group) it takes about 5-15 seconds, until the client crashes again.
That has happened to me 6-7 times and just momets ago. So I waited in the off until the group had removed me from the raid, logged in again and there was no crash. If I didn't have to go into the EN for my campaign progress, I wouldn't care

I hope u can help me ... here's the crash report:



This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal exception!

Program: C:\Users\xyz\Desktop\Freakz\wow-64.exe
ProcessID: 7568
Exception: ACCESS_VIOLATION

The instruction at "0x0000000140794013" referenced memory at "0x00000000000003e0".
The memory could not be "read".


Thx!

[Sarah]

Hello Subseven,

It usually happens when the Raid UI for the group you're in gets corrupted (A member either doesn't show at all, or shows up twice), the client doesn't know what to do with that and crashes because of it.

The solution is to unstuck on the website and tick the "Remove from party" box to get out of the broken group.

This can happen to any raid group in any location, I'd say it's just bad luck that it happened on EN repeatedly.


Best regards
Sarah

All PMs must be written in English. Bug reports in PMs will be ignored - use the Bug Report section on the forum.

[Subseven]

Mh, well, that also explains why almost all raid members were offline last time, when I logged in again immediately after a crash - so I was probably not the only one.

Then I'll just keep trying. Thanks for the reply, I think the thread can be closed.