Forum > Miscellaneous

ERROR #132 - An actual way to fix it. (Build 12340)

(1/8) > >>

schlumpf:
See https://wowdev.wiki/Client_Error_Analysis.

Ayos:
Hi! I just started a project a few days ago with a concept that requires a full sized map. Everything worked fine with a small testmap before, but when i started a new full-sized map, it even crashes my wow client and noggit at totally random spots.
Here is the crash report:

This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal Exception
Program:   D:JátékokTauri WoWWow.exe
Exception:   0xC0000005 (ACCESS_VIOLATION) at 0023:007B4D61

The instruction at "0x007B4D61" referenced memory at "0x00000071".
The memory could not be "read".

Yesterday it was "0x004057FB" read "0x00000004" but i think somehow i fixed that, but then this new error appaered instantly.
Any idea?

schlumpf:

--- Quote from: "nightattack" ---Yesterday it was "0x004057FB" read "0x00000004" but i think somehow i fixed that, but then this new error appaered instantly.
--- End quote ---
That was fixed by adding the map dbc entry.
Thanks for the backtrace. Please bump once to remind me investigating this at home.

schlumpf:

--- Quote ---0x007B4D61 read 0x00000071
--- End quote ---
Requires pretty deep investigation, not a trivial case. Raid now, may check later today or "soon" (aka never unless bumped).

Ayos:
I hope you can find some solution.. :) it's really annoying.

Navigation

[0] Message Index

[#] Next page