Modcraft - The community dedicated to quality WoW modding!
Wrath of the Lich King Modding => Miscellaneous => Topic started by: schlumpf on October 13, 2012, 12:37:00 pm
-
See https://wowdev.wiki/Client_Error_Analysis.
-
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?
-
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.
-
0x007B4D61 read 0x00000071
Requires pretty deep investigation, not a trivial case. Raid now, may check later today or "soon" (aka never unless bumped).
-
I hope you can find some solution.. :) it's really annoying.
-
Seems to be related to WDT. Try redoing that. (At least, there is CBarrier code nearby.)
-
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?
-
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, ..)
-
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".
-
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.
-
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 >-< )
-
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.
-
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.
-
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".
-
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.
-
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.
-
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.
-
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.
-
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.
-
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
-
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?
-
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 :)
-
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).
-
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.
-
0x004E0A9B read 0x0000001C
Cause unknown for now. Investigating the changes I did.
-
The instruction at "0x005CE0C8" referenced memory at "0x00000010"
Upon entering character -> Skills on a newly created race (raceid 22)
-
Is there any way to remove that hardcoded limit?
We have been messing with the client before after all.
-
Same error occurs with raceid 13. SkillLine* is done properly and completely.
-
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:
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.
-
I fix the error by replacing my wow 3.3.5a with a new one and here is my tip always have backups
-
I guess this is the thread that you wanted the error posted in?
Getting 0x007C8DA0 read 0x5182FF42.
-
Hey, guys!
Could somebody help me with the following errors?
ERROR #132 (0x85100084) Fatal exception!
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:00C26EC9
The instruction at "0x00C26EC9" referenced memory at "0x13291000".
The memory could not be "read".
ERROR #132 (0x85100084) Fatal exception!
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:012A6EC9
The instruction at "0x012A6EC9" referenced memory at "0x12DB2000".
The memory could not be "read".
-
Hey, guys!
Could somebody help me with the following errors?
Finding these is not exactly trivial, so knowing at least roughly what you did to trigger them would help a lot.
-
Hey, guys!
Could somebody help me with the following errors?
Finding these is not exactly trivial, so knowing at least roughly what you did to trigger them would help a lot.
Well, I copied the wandering isle map to my Cata server and when I'm in that place (on the picture) and I turn left, the game crashes.
[attachment=0:17go60z3]wanderingislecrash.JPG[/attachment:17go60z3]
Most likely, it's some wmo/m2, but if I try to find out by trial and error, it's gonna take ages.
And interesting detail is that I've done exactly the same process before, and I had no crashes at all
-
I manipulated the files a bit, and now I'm getting
ERROR #132 (0x85100084) Fatal exception!
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:00F16EC9
The instruction at "0x00F16EC9" referenced memory at "0x153AE000".
The memory could not be "read".
-
Creating a spell which persists on a character even when he's dead/logged out seems to be causing crashes on logging in for me. It also occurs whenever I close wow.exe (either forcefully or by clicking "Exit game").
The error is always same:
The instruction at "0x77e8cecf" referenced memory at "0x00000014". The memory could not be "read".
Could someone help?
-
Auhm guys... I would really, really recommend to keep this thread free of discussions, theories, questions and spams. Those should, in my opinion, go to separated threads, while this should be only list of things we have found and about which we know well, wtf is happening. Otherwise can this topic become just help spam topic, and thats where the rest of forum comes in. I think that this thread should literally be just something like a database of error codes and solutions to them - which mens an addition to FAQ, not an actual Q&A.
I am no mod ofc, so this is just my opinion, and recommendation to those, who actual mods are, as otherwise can this topic become just hard to search through. Which means that if you agree with me, feel free to edit this post of mine of course.
Found a new kind of error I didn't know about until now:
This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal Exception
Program: D:\Hry\World of Warcraft 3.3.5a\Wow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:007EBF50
The instruction at "0x007EBF50" referenced memory at "0x00000000".
The memory could not be "read".Error comes from Light.dbc, light settings, which were attempted to be loaded, have refference to non-existing LightParams.dbc.ID. Check Light.dbc settings (incorrectly often called skyboxes) in your vicinity (using LightMapper) and make sure that all of them have correct IDs in last 8 of their fields. Information about tools and DBCs included can be found on my channel.
-
i get this error on my map...
ERROR #132 (0x85100084) Fatal Exception
Program: D:\WoW\3.3.5aNoggit\CustomWoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:0087307D
The instruction at "0x0087307D" referenced memory at "0x00000120".
The memory could not be "read".
-
i get this error on my map...
ERROR #132 (0x85100084) Fatal Exception
Program: D:\WoW\3.3.5aNoggit\CustomWoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:0087307D
The instruction at "0x0087307D" referenced memory at "0x00000120".
The memory could not be "read".
Please provide a log file. Also, you are even in the filename using "CustomWoW.exe". You should probably provide that as well. Otherwise, nobody can answer your question, by definition.