This is a read only copy without any forum functionality of the old Modcraft forum.
If there is anything that you would like to have removed, message me on Discord via Kaev#5208.
Big thanks to Alastor for making this copy!

Menu
Pages: [1] 2 3

Author Topic: ERROR #132 - An actual way to fix it. (Build 12340)  (Read 26507 times)

schlumpf

  • Administrator
  • Creator of Worlds
  • *****
  • Posts: 2967
    • View Profile
ERROR #132 - An actual way to fix it. (Build 12340)
« on: October 13, 2012, 12:37:00 pm »
« Last Edit: March 04, 2018, 11:01:03 pm by schlumpf »
Logged

Ayos

  • Registred Member
  • BLP Convertor
  • *****
  • Posts: 11
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #1 on: July 03, 2013, 02:18:32 pm »
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?
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

schlumpf

  • Administrator
  • Creator of Worlds
  • *****
  • Posts: 2967
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #2 on: July 03, 2013, 02:41:47 pm »
Quote from: "nightattack"
Yesterday it was "0x004057FB" read "0x00000004" but i think somehow i fixed that, but then this new error appaered instantly.
That was fixed by adding the map dbc entry.
Thanks for the backtrace. Please bump once to remind me investigating this at home.
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

schlumpf

  • Administrator
  • Creator of Worlds
  • *****
  • Posts: 2967
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #3 on: July 03, 2013, 08:17:27 pm »
Quote
0x007B4D61 read 0x00000071
Requires pretty deep investigation, not a trivial case. Raid now, may check later today or "soon" (aka never unless bumped).
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

Ayos

  • Registred Member
  • BLP Convertor
  • *****
  • Posts: 11
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #4 on: July 04, 2013, 07:17:18 pm »
I hope you can find some solution.. :) it's really annoying.
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

schlumpf

  • Administrator
  • Creator of Worlds
  • *****
  • Posts: 2967
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #5 on: July 04, 2013, 08:59:10 pm »
Seems to be related to WDT. Try redoing that. (At least, there is CBarrier code nearby.)
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

Ayos

  • Registred Member
  • BLP Convertor
  • *****
  • Posts: 11
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #6 on: July 13, 2013, 04:25:02 pm »
So, i recreated the whole map again with a different adt template from this site and still crashing, but this time from this:

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

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

I hope this is not related to the fact that i use a full 64x64 map... this size is necessary for my project.
Any idea?
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

schlumpf

  • Administrator
  • Creator of Worlds
  • *****
  • Posts: 2967
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #7 on: July 13, 2013, 04:55:39 pm »
That's pretty close to the old values, thus in the same function, thus most likely in the same filetype. Did you try creating the files step by step so that you see, when it starts crashing? (i.e. create the wdt + 1 adt first. See if it crashes. Expand the WDT, see if it crashes, ..)
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

MR. Farrare

  • Registred Member
  • Creator of Worlds
  • *****
  • Posts: 963
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #8 on: August 01, 2013, 09:50:36 pm »
when i get to the end of my map i get only at the end and up in my map is ok only  at the end maybe because my map is too big 64 64 and ye i used add water on the last off my map and i picked ocean plz help and no wmo there all deleted and if there maybe and wmo then its unseen wmo plz tell me how to find it and select it and delete it srry for my english im trying to get better
ERROR #132 (0x85100084) Fatal Exception
Program:   I:wow woltk repackseus wowWorld of Warcraft 3.3.5a (no install)wow.exe
Exception:   0xC0000005 (ACCESS_VIOLATION) at 0023:007B4D61

The instruction at "0x007B4D61" referenced memory at "0x00000071".
The memory could not be "read".
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

Ayos

  • Registred Member
  • BLP Convertor
  • *****
  • Posts: 11
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #9 on: August 04, 2013, 12:16:56 pm »
My problem was almost the same as yours. The client always crashed when i used my 64x64 map, but when i made a 63x63 version (still dont know why), the crashes disappaered. So just try to cut the outter lines of your map.
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

Garthog

  • Contributors
  • Polygonshifter
  • *****
  • Posts: 56
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #10 on: August 14, 2013, 08:17:33 pm »
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 >-< )
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

Ascathos

  • Moderators
  • Creator of Worlds
  • *****
  • Posts: 1129
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #11 on: September 15, 2013, 03:12:09 pm »
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.
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

Ascathos

  • Moderators
  • Creator of Worlds
  • *****
  • Posts: 1129
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #12 on: November 17, 2013, 02:19:09 pm »
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.
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

Derass39

  • Registred Member
  • MWCS Enthusiast
  • *****
  • Posts: 1
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #13 on: May 06, 2014, 01:02:06 pm »
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".
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

Laduguer

  • Registred Member
  • Wiki Incarnate
  • *****
  • Posts: 144
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #14 on: May 26, 2014, 03:01:21 pm »
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.
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged
Pages: [1] 2 3