World of Warcraft - crash in game

Alex Woods wine-devel at
Thu Feb 24 16:22:48 CST 2005


World of Warcraft is working beautifully now apart from a crash that
occurs seemingly randomly.  The application is catching the crash, and
giving a message like this:

This application has encountered a critical error:

ERROR #132 (0x85100084)
Program:        C:\Program Files\World of Warcraft\WoW.exe
Exception:      0xC0000005 (ACCESS_VIOLATION) at 0023:557102CD

EAX=00000000  EBX=55BDFCA8  ECX=00000000  EDX=55BDFBB8  ESI=5E320308
EDI=00000000  EBP=55BDFC08  ESP=55BDFB9C  EIP=557102CD  FLG=00010212
CS =0023      DS =002B      ES =002B      SS =002B      FS =005B      GS=0063

I know this isn't really much use on it's own.  I've tried turning on
+relay logging, but it's proved futile - it seems to end up freezing up
my system before a crash occurs.  One thing that might be useful is that
the access violation always seems to be around the same small area of
memory each time, eg:

Exception:        0xC0000005 (ACCESS_VIOLATION) at 0023:557103CD
Exception:        0xC0000005 (ACCESS_VIOLATION) at 0023:5571025D

Over the course of 13 (unlucky for me ;)) crashes, these are the only 3
addresses it has given.  My question is what can I do to debug this?
+relay logging is probably infeasible, but I'd be happy to hack around
to get it to only log certain things - I'm not sure what I'd need to
log.  Also, the last time it crashed, I was lucky enough to have it
leave me in winedbg, which I've left open.  Is there anything worth my
while poking around with in there while I have the chance?

I guess I'll be running memtest on my machine too, but I'd like to do
what I can in winedbg first ;)



More information about the wine-devel mailing list