Forum > Miscellaneous

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

<< < (3/8) > >>

Garthog:
New WoW Error, occuring on "newly enabled" race/class combination. Happening since I did that TrinityCore update ( two years of update ).

WoW Errors occurs on character selection screen, when clicking one of those character.

Here's the error :

ERROR #132 (0x85100084) Fatal Exception
Program:   D:Projet MithrasDossiers WOWWorld of Warcraft MithrasWow.exe
Exception:   0xC0000005 (ACCESS_VIOLATION) at 0023:004E4191

[attachment=0:2t4mt494]Wow error.txt[/attachment:2t4mt494]

EDIT : Found the answer. Basically it's when you have a wrong CHAR_ENUM packet ( with wrong displayid ). It leads to wow errors and strange green items. ( I had an item with entry 0, it made the whole trinitycore server bugging >-< )

Ascathos:
The instruction at "0x007F69D1" referenced memory at "0x00000000".
The memory could not be "read".

Trying to call GtBarberCosts.dbc for an entry that does not exist.

Ascathos:
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007C59EA.
The instruction at "0x007C59EA" referenced memory at "0x1F312341".
The memory could not be read.


Occurance unknown for now.

Derass39:
What to do when wow error "0x007C59EA" ?

ERROR #132 (0x85100084) Fatal Exception
Program:   C:UsersValentinDocumentsJeuxWorld of Warcraft privewow.exe
Exception:   0xC0000005 (ACCESS_VIOLATION) at 0023:007C59EA

The instruction at "0x007C59EA" referenced memory at "0x1DE0A7AE".
The memory could not be "read".

Laduguer:
Hi guys! Not sure about this one. It appeared randomly after a session of building on Noggit and I can't seem to find any reasonable explanation:

ERROR #132 (0x85100084) Fatal Exception
Program:   I:WoWModdingClient335aTestwow.exe
Exception:   0xC0000005 (ACCESS_VIOLATION) at 0023:007A39D7

The instruction at "0x007A39D7" referenced memory at "0x43E2C70D".
The memory could not be "written".

EDIT: Possibly something to do with ADT corruption? But then I can't see any reason why that would have occured.

EDIT 2: Fixed it. It was an issue with massive .wmo duplication.

Navigation

[0] Message Index

[#] Next page

[*] Previous page