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

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

Valkryst

  • Moderators
  • Model Change Addict
  • *****
  • Posts: 224
    • View Profile
    • http://valkryst.com/blog/
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #30 on: December 14, 2015, 11:38:05 pm »
I guess this is the thread that you wanted the error posted in?

Getting 0x007C8DA0 read 0x5182FF42.
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
MY BLOG IS NOW HERE.

Смердокрыл

  • Registred Member
  • Creator of Worlds
  • *****
  • Posts: 445
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #31 on: March 03, 2016, 03:18:17 am »
Hey, guys!
Could somebody help me with the following errors?

Code: [Select]
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".


Code: [Select]
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".
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
or no.
At least I tried.

schlumpf

  • Administrator
  • Creator of Worlds
  • *****
  • Posts: 2967
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #32 on: March 03, 2016, 09:27:57 am »
Quote from: "Смердокрыл"
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.
« Last Edit: January 01, 1970, 01:00:00 am by Admin »

Смердокрыл

  • Registred Member
  • Creator of Worlds
  • *****
  • Posts: 445
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #33 on: March 03, 2016, 12:41:42 pm »
Quote from: "schlumpf"
Quote from: "Смердокрыл"
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
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
or no.
At least I tried.

Смердокрыл

  • Registred Member
  • Creator of Worlds
  • *****
  • Posts: 445
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #34 on: March 03, 2016, 12:59:52 pm »
I manipulated the files a bit, and now I'm getting
Code: [Select]
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".
« Last Edit: January 01, 1970, 01:00:00 am by Admin »
or no.
At least I tried.

Смердокрыл

  • Registred Member
  • Creator of Worlds
  • *****
  • Posts: 445
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #35 on: June 24, 2017, 09:12:08 am »
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?
« Last Edit: June 24, 2017, 09:24:22 am by Смердокрыл »
or no.
At least I tried.

Amaroth

  • Contributors
  • Creator of Worlds
  • *****
  • Posts: 1219
    • View Profile
    • Amaroth's Tools
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #36 on: June 24, 2017, 10:28:19 am »
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:
Code: [Select]
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.
« Last Edit: June 24, 2017, 11:56:37 am by Amaroth »
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

Senix

  • Registred Member
  • BLP Convertor
  • *****
  • Posts: 7
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #37 on: January 15, 2018, 11:02:23 am »
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".

schlumpf

  • Administrator
  • Creator of Worlds
  • *****
  • Posts: 2967
    • View Profile
Re: ERROR #132 - An actual way to fix it. (Build 12340)
« Reply #38 on: January 15, 2018, 11:13:30 pm »
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.