Strange Error

[TheDarkMandible]

I have been getting this strange error ever since I installed warcraft on my "new" computer. I have XP, at least 76GB of memory left and 1GB RAM. I have a feeling that It is something to do with the memory but I just cannot make sense of it.

I do have the latest patch. Can anyone tell me what's wrong and how to fix it.

 

[Kercyn]

Try reinstalling Warcraft, and see if it happens again.

 

[TheDarkMandible]

Try reinstalling Warcraft, and see if it happens again.

I've already tried that, I have reinstalled Warcraft III about 2 or 3 times now.

I'm wondering if that is why, because I have installed it so many times. I have previously installed the two Warcraft III's about double that amount before the error started appearing.

Also, It only happens about once every 3 months or so, It's not a big deal. It is just very annoying when I'm in the middle of a game on battle.net as it looks like I left and being a "leaver" is not a good reputation to have!

 

[M0rbid]

I have the same error on vista.
Yeah, it appears sometime, I thought of it might be caused by vista, it's quite disturbing, but actually it appears only sometimes so I can live with it, but reinstalling definetallely not help!

 

[TheDarkMandible]

At least I'm not the only one, even if we do have different operating systems.

 

[TheDivineBoss]

Did you try uninstalling the game and then remove all old (registry) files? (Not by hand, but with a program)(CCleaner is useful)

And another thing: Does this happen when you are in a (certain) map or try to start up the game (etc)?

Edit: It is possible that some maps can crash your game.

 

[M0rbid]

My personal experience is, that this error often comes up, when more complex things happen at the same time, graphics, but mainly triggers. For example in an Aos, when many triggered hero spells are casted at the same time I had such a crash, same with a different map....

 

[TheDarkMandible]

The latest crash was when I was playing that new "The Last Stand" Map by vengencekeal. It appears to have quite trigger heavy spells which could have caused the crash this time.

It is always ingame on custom maps. I have never had the crash on melee maps.

 

[M0rbid]

Yeah, same here, I#m not sure, maybe an expert knows, maybe this could be caused by JNGP?

 

[BlargHonk]

Ah yes, 0xC0000005, we meet again.

It's basically just the general Warcraft 3 error.


Now, right click the main Wc3 file in Program Files and uncheck the box that says Read-Only.

If that doesn't work try manually patching it, exe is here (ROC and TFT Patch): http://us.blizzard.com/support/article.xml?locale=en_US&articleId=21224

And if that doesn't work, download http://www.piriform.com/ccleaner and scan your registry.

 

[TheDarkMandible]

It seems to have stopped coming up for the moment. Thanks for all your help guys!

 

[Tleno]

http://eu.blizzard.com/support/arti...parentCategoryId&pageNumber=1&categoryId=3104
Well there is some kind of info in Blizzard tech support website if you're curious.