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 26500 times)

ruffo91

  • Registred Member
  • GM Isle Explorer
  • *****
  • Posts: 17
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #15 on: July 21, 2014, 11:46:27 pm »
ERROR #132 (0x85100084) Fatal Exception
Program:   C:UsersRubenDesktopWoW SaronWowejecutable.exe
Exception:   0xC0000005 (ACCESS_VIOLATION) at 001B:004DFEDD

The instruction at "0x004DFEDD" referenced memory at "0xBE860A92".
The memory could not be "written".

This error appears when I am in the character creation screen, I used a converted version of Pandaren model and Worgen, when Im in a different race like Felorc for example and I select the Pandaren race the crash appear but if I enter in Character creation screen and the Pandaren race is default selected no problem appears.
« 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 #16 on: July 22, 2014, 10:16:36 am »
Quote from: "ruffo91"
ERROR #132 (0x85100084) Fatal Exception
Program:   C:UsersRubenDesktopWoW SaronWowejecutable.exe
Exception:   0xC0000005 (ACCESS_VIOLATION) at 001B:004DFEDD

The instruction at "0x004DFEDD" referenced memory at "0xBE860A92".
The memory could not be "written".

This error appears when I am in the character creation screen, I used a converted version of Pandaren model and Worgen, when Im in a different race like Felorc for example and I select the Pandaren race the crash appear but if I enter in Character creation screen and the Pandaren race is default selected no problem appears.

Races are hard coded. Selecting death knights will also crash most likely. Only reusing existing races will correctly work. Also, do not change internal names for them. Same for classes. Every non-existing race/class is a potential crash.
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

ruffo91

  • Registred Member
  • GM Isle Explorer
  • *****
  • Posts: 17
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #17 on: July 22, 2014, 11:01:19 am »
Okay, thanks for your reply Im trying to fix it cause just 2 races crash me the client and I have 24, I think that the problem is in CharacterSections.dbc or in the model so not totally sure. If I'll fix it I'll tell you how. Thank you.
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

Mjollna

  • Contributors
  • Model Change Addict
  • *****
  • Posts: 254
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #18 on: July 24, 2014, 04:40:06 pm »
Hi everyone, long time no see :)

I don't know if that can help someone in the future, but I've solved a #132 labeled 0x85100084.

I had created a custom m2, and when launching the game with that model it crashed. I realized I had forgotten to add a dummy "stand" anim in the mdl before converting from mdlvis to m2.

After that, no more error. It might be very specific, but maybe someone will face this case again some day.
« 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 #19 on: July 24, 2014, 07:18:56 pm »
Quote from: "Mjollna"
Hi everyone, long time no see :)

I don't know if that can help someone in the future, but I've solved a #132 labeled 0x85100084.

I had created a custom m2, and when launching the game with that model it crashed. I realized I had forgotten to add a dummy "stand" anim in the mdl before converting from mdlvis to m2.

After that, no more error. It might be very specific, but maybe someone will face this case again some day.
thank you you blossom gorgues princess!!!! just kidding thank you for this info Mjollna :D
and its really nice to see you back legend
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

andrejmega

  • Registred Member
  • GM Isle Explorer
  • *****
  • Posts: 24
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #20 on: July 30, 2014, 11:25:10 am »
This application has encountered a critical error:

Error #132 (0x85100084) Fatal Exception
Program: D:Program Files (x86)WoW 3.3.5Wow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION_ at 0023:007D6B51

The instruction at "0x007D6B51" referenced memory at "0x6CCE528B".
The memory could not be "read".

Press OK to terminate the application.


-----------------------------------

Using Noggit 1.2.
The ADT didn't had water, I used the CMD program CopyWater and I replaced the original ADTs, which didn't crash when launched, with the "fixed" ones. When I applied them to the WoW data folder I instantly crashed.

Why I replied is because this number: 0x007D6B51; I couldn't find in the guide, so I ask you. How can I fix it? Should I leave it without water? or is there another way to fix it?
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

kirito-kun

  • Registred Member
  • BLP Convertor
  • *****
  • Posts: 10
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #21 on: August 10, 2014, 05:41:54 pm »
Hey guys,

I made a new Map with Noggit. After trying to go to it ingame the Error #132 appears.
I don't know whats wrong. It says wow.exe does have an problem or something like that.

The .exe is cracked with "wow_unsig(12340)". So what could be the problem?

I'll upload a screenshot of the error-window and the textfile of the error-log below.

Thanks for your time and help :)
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

Amaroth

  • Contributors
  • Creator of Worlds
  • *****
  • Posts: 1219
    • View Profile
    • Amaroth's Tools
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #22 on: September 05, 2014, 02:08:17 pm »
Adding new error here and its solution:

0x0082C7C9 - error caused by NPC DisplayID if it uses CreatureDisplayInfoExtra.dbc and its CreatureDisplayInfoExtra.Texture (21st column, or 20th if zero-based) is set to "" (empty string). Solution - enter texture name (even wrong and thus not working name will make NPC with such displayID/player with such morph stop causing this WoW Error).
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged
English YT tutorial channel. Check it out if you preffer videos over walls of text.:
https://www.youtube.com/AmarothEng

Want to support me for my releases and/or tutorials? You can send donation via Paypal to:
jantoms@seznam.cz

Amaroth

  • Contributors
  • Creator of Worlds
  • *****
  • Posts: 1219
    • View Profile
    • Amaroth's Tools
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #23 on: December 21, 2014, 12:13:35 pm »
0x0072DA70 - unknown CreatureModelData.ID for NPC displayID, meaning client could not find model ID in #2 column of CreatureDisplayInfo.dbc. Check your CreatureDisplayInfo.dbc, there will be somewhere link to not existing model ID from CreatureModelData.dbc.
« Last Edit: January 03, 2017, 01:13:22 am by Admin »
Logged
English YT tutorial channel. Check it out if you preffer videos over walls of text.:
https://www.youtube.com/AmarothEng

Want to support me for my releases and/or tutorials? You can send donation via Paypal to:
jantoms@seznam.cz

Ascathos

  • Moderators
  • Creator of Worlds
  • *****
  • Posts: 1129
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #24 on: May 04, 2015, 06:37:40 am »
0x004E0A9B read 0x0000001C

Cause unknown for now. Investigating the changes I did.
« 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 #25 on: May 28, 2015, 03:08:32 pm »
The instruction at "0x005CE0C8" referenced memory at "0x00000010"
Upon entering character -> Skills on a newly created race (raceid 22)
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

Gurluas

  • Contributors
  • Creator of Worlds
  • *****
  • Posts: 344
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #26 on: June 02, 2015, 02:00:23 am »
Is there any way to remove that hardcoded limit?

We have been messing with the client before after all.
« 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 #27 on: June 02, 2015, 03:03:53 pm »
Same error occurs with raceid 13. SkillLine* is done properly and completely.
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged

Supora

  • Registred Member
  • Wiki Incarnate
  • *****
  • Posts: 143
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #28 on: July 26, 2015, 07:21:54 pm »
Code: [Select]
ERROR #132 (0x85100084) Fatal Exception
Program: E:GamesWorld of WarcraftWorld of Warcraft 3.3.5Wow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007C81ED

The instruction at "0x007C81ED" referenced memory at "0x00000017".
The memory could not be "read". Get this error when set flags of wmo group to 2001(Has MOBN and MOBR chunk. + Indoors.) when group file has a MCCV chunk. If I set flags to 2005(Has MOBN and MOBR chunk. +Has MCCV chunk.  + Indoors.) then it was fine(no error). If I set flags back to 2001 and delete MCCV chunk then I get this error:
Code: [Select]
ERROR #132 (0x85100084) Fatal Exception
Program: E:GamesWorld of WarcraftWorld of Warcraft 3.3.5Wow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007C81ED

The instruction at "0x007C81ED" referenced memory at "0x00000027".
The memory could not be "read". So it seems that indoor parts can't be rendered and get this error if:
1)indoor batches in MOGP chunk is more then 0
2)This indoor part doesn't have MCCV chunk and flag for it.
So to solve this problen you need to have flag "Has MCCV" and MCCV chunk in this indoor part.
« 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 #29 on: October 15, 2015, 01:55:31 pm »
I fix the error by replacing my wow 3.3.5a with a new one and here is my tip always have backups
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
Logged
Pages: 1 [2] 3