memory error while loading my map to test/play?

About halfway through the loading process of my map, WC3 shuts down and I get an error message.

This application has encountered a critical error:

FATAR ERROR!

Program: c:\program files\warcraft iii\War3.exe
Exception: 0xC0000005 (ACESS_VIOLATION) at 001B:6F2DFEB2

The instruction at'0x6F2DFEB2' referenced memory at '0x0000000C'.
The memory could not be 'read'.

Press OK to teminate the application.

This only started when I tried adding variables to my unit creation triggers..I've tried disabling them but that don't work. Anyone got an idea as to why my map can't load? Only happens with this one.

If possible, instead of having things go off during Map Init, have them start 1 second of game time. I kept breaking my map by glomming in stuff to the 1 Map Initialization trigger -- just have them happen 1 second into the map; nobody will ever notice.

Oddly, anything to do with day/night cycle borks up maps on Init. I'm sure that's not the only one.

Experience tells me that 95% of the time, it's because of a trigger. Just find a pattern and find out what trigger is doing it. Then find out why, and fix it. It happens in the beginning, right? Well, some "Map Initialization" triggers can actually go off just before the map finishes loading, so check those. Furthermore, it could be an imported file that you're using incorrectly. It's going to take some dedication to look for and find out what it is, so, good luck! :D

Thanks for the suggestions..

I've tried taking off all map initialization triggers, didn't work.

I've tried disabling any new triggers I added (mostly variables, dont suppose setting those would cause this?) from after I last tested the map when it worked, didn't work.

It'll try removing all triggers that I've added since it worked last..see if that does anything :\

Were you ignoring my final suggestion, or what? I'm telling you, it could possibly be an imported file that is incompatible with WC3. Don't forget to see if that's it.

Sorry, meant to reply to that also but wanted to test your other suggestions ;x

I haven't imported anything at all.

Edit: Deleted all triggers to try and start it with nothing going on, but still got the same error.

Hopefully, you have those triggers backed up somewhere -- disabling works just fine, FFR.

Ok. No imported files, no commands during initiation. Um... is your computer having problems with warcraft generally (i.e., is this not the first time you've crashed out)? My old Athlon, in its death throes, kept vomiting every time I made it run WCIII -- finally had to get a new motherboard.
If it's a general compatability problem, it may not be entirely WC's fault -- but there's a simple test for that. Would you mind uploading your map? If none of us can get it to open, then we can at least try to figure out what's causing the trouble.

I'm having the same problem.... my editor doesn't USUALLY churn out the errors like this.... though lately, it's been giving me a bit of trouble.... Does anyone have any ideas aside from getting a new computer?

Just in case, Eriond, check out this:
http://www.nocrash.com/ncbbs/msgs/3357.shtml - Warcraft crashes aren't terribly uncommon. Give these items a try.

And, straight from Bliz: http://www.blizzard.com/support/?id=awr0649p

But it's only this one map. All other maps work fine... the fixes are all suggested when it's for everything

WC3 is giving me no problems at all other than this map, triggers don't seem to be causing it unless I somehow made one invisible and forgot about it :\

Not only does it crash while opening, but it even crashed me while hanging around in the load screen - got a "sound file is corrupt" error with the music.

Lemme take a look at it in the editor.

This is the first time I've messed with variables, so I don't expect anything to work perfectly:P Course I can't fix anything until I find why it won't load heh ;x

I don't see why sound might make it crash.. but at this point about anything could be it I guess.

Talis, I wiped out ALL of the triggers and variables, so no, they're not the problem. And I think the sound error was just a fluke. I'm curious if this isn't a building problem -- did you set any units to buildings or vice versa?

Here's my map. Dunno why my leader wanted me to make it, he jus did... it's still under construction... Can you take a look at it? It was working fine earlier today... What went wrong?