Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WARDEN crash the game client! #188

Open
SOWRON opened this issue Jun 19, 2012 · 1 comment
Open

WARDEN crash the game client! #188

SOWRON opened this issue Jun 19, 2012 · 1 comment

Comments

@SOWRON
Copy link

SOWRON commented Jun 19, 2012

When enabled in the config option Warden.Enabled = 1, after 10 seconds after a successful authentication the client is a client crash. Tested on 3 different game client 4.0.6a on operating systems Windows XP (x86), Seven (x64). The server was compiled under Windows Seven (x64), Debian6 (x64).

WoW Error(small part):
World of WarCraft: Retail Build (build 13623)
Exe: D:\Games\World of Warcraft\WoW 4.0.6a\START.exe
Time: Jun 19, 2012 9:55:27.907 PM
User: *****
Computer: *****
This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal Exception
Program: D:\Games\World of Warcraft\WoW 4.0.6a\START.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:0137654A
The instruction at "0x0137654A" referenced memory at "0x00000045".
The memory could not be "read".

@w5860363
Copy link

w5860363 commented Jul 8, 2012

Warden.Enabled = 1?The default configuration files without this option

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants