Warcraft 3 frozen throne fatal error the memory could not be read - Исправление ошибок и поиск оптимальных решений проблем

А также, кто знает англ, советую прочитать:

HELLWOLF’S GUIDE TO FIXING FATAL ERRORS — AN ADDON TO N_’s INFORMATION

Greetings Forum Surfers and newcomers. If N_’s guide doesn’t help you with the problem (Trust me, it won’t). My LONG guide of solutions should be able to fix your solutions. This will work with generally any 0x8E (Unhandled Exception) or 0xC4 error. How I know these will work? I have written this guide thru experience since my first computer suffered like this. I fixed it with a new PSU and DRAM Voltage, now it crashes from triggers . However, I have no assurance whatsoever that your problem will get worse, you decided to do this so do the advanced issues at your own risk .

-Bad Drivers
Update your video card when new drivers come out. Go to your manufacturer’s website to download the latest. For ATI, its Catalyst. For nVidia it’s Forceware. Just remember you need a 32 bit version of Windows XP or Vista or 2000 to operate these drivers properly. There are no real 64 Bit ones yet, and your drivers will fail to install on a 64 bit machine.

-Insufficient or Ineffective RAM
Get more RAM, make sure its of the right frequency so it doesnt lead to incompatibility. Eg. If you can support DDR 400, then get them both at DDR400 and have the same voltage. You will need to look at the sticker that comes on the RAM and break down the format to extract this information.

If you think it’s a certian stick of RAM and you have more than 1, take out one, and run Warcraft III. Then repeat for your other RAM. If one stick is causing the crash, then replace it with one that works. If it’s 1, then you will need to replace it. The best way to detect this problem is checking your crash logs and looking for the memory address that crashed. You can also install and run MemTest86 to find out which addresses aren’t complying and which ones are.

-Motherboard Conflicts
This is one nasty mother ****er. You would need to either update your current drivers. Or even go as far as Flashing a new BIOS (requires reinstall and hopes that it doesnt crash in reinstallation). Or even to disect your computer and install a new motherboard (4-5 hrs. you dont want to do). This is a rare occurance, I have never seen a Motherboard conflict, unless you did something stupid like drop a magnet on it or broke a piece of it.

-PSU not strong enough (STRONG POSSIBILITY)
This is the most common problem that is often overlooked. It happened to me when I owned a JGE 300W PSU before I got it replaced. It wasn’t passing enough volts through the 12V Line (15A). Open your case, and look at your PSU label for the 12V line(not colour, the AMPS). If the number is below 20-22A, then you need to get it replaced. Its not sending a powerful enough current through the motherboard to power everything! For watts, aim towards 450+ to your PSU. However, brand will determine how AWESOME it is. Get a well known name brand (Antec for example), otherwise the PSU could fry or explode if the parts are cheap or defective (we can’t have that). Plus, some brands don’t have good warranties, so you cannot get a proper replacement should anything happen to it.

-Your running 3D sound with a card that doesnt support it (makes a different error message)
This will make a different error message. Saying that the mp3 was failed to initialize. Users running a RealTek Audio chipset will have to turn off 3d sound to avoid this problem. If your sound card/chipset supports it, then you are safe and can turn it on. I recommend Sound Blaster Audigy or X-Fi to operate 3D Sound.

-You have anti-aliasing on (wc3 hates this feature, water.blp doesnt load right)
This was a bad issue back when ATI Catalyst was around 4.5-4.8. Anti-aliasing was always on and Warcraft III is a real prick when dealing with Anti-aliasing, mostly because the water models wouldnt be able to work properly. Find a way to turn it off, or install 4.10+ (anti-aliasing wasnt on default in those versions).

-You’re running openGL (remove -opengl tag) from Properties
If you right click on your shortcut and select Properties, you’ll find where your shortcut is running to. Look at the end of it, for the -openGL tag. This shouldn’t be here. We live in a world of Direct3D now. The only purpose OpenGL servers is probably playing Unreal Tournament 1999 and Doom II, since these games actually looked better in OpenGL than Direct3D. Other games may not take OpenGL kindly.

-Virus (STRONG)
You could have a virus that is plaguing your system. You can run an anti-virus scan or reformat your hard disk. Reformating clears everything (requiring Windows reinstall) but you will have nuked the viruses. Use Norton (if you want a virus within itself) or AVG (it’s free), Proxomitron or Spybot to keep these threats neutralized.

-Too Many programs running at once (STRONG)
Control Alt Delete > Close off any programs that you don’t want running. To free up physical memory so your RAM doesn’t overload and close Warcraft III. The only situation this is a problem is with programs that conflict with each other or if you blew your Virtual Memory cache (The portion of the Hard Drive that writes page files should you inflate your RAM).

-Models could be rendered incorrectly (updates and fixes, custom models)
Not really a common problem, was in DOTA!!! Some custom models may have not been done incorrectly and the game will crash. Not much you can do, update your game and use models that work properly for best effects.

-DRAM Voltage TOO LOW!!
Another problem, it requires you to tamper with your BIOS settings. Load up the BIOS the way would do it. Then find the option called DRAM Voltage (should be in Power Management). Set it to the maximum value. If your BIOS warns you about it being unsafe, just do it anyways. Be sure your PSU can take the heat.

-AGP Aperture Size
The value of this must be half of what your video card is (Eg. if its 256MB, then set Aperture to 128MB, and so on). If you use the full value, your card will stop working properly! By default, the Aperture of the card is usually set to Auto, which adjusts based on the card installed.

-Fast Writes and XAGP
My old Windows XP machine usually had this at 4x and Fast Writes on. If your computer can support it, go 8x and Fast Writes. However, your motherboard needs to have the feature. BIOS has an option called AGP Fast Writes within it, it must be enabled to work properly. Check your motherboard specs to make sure you know what the limits are.

-Overheating
If parts get too hot, they will stop functioning properly. Use better fans or cooling systems to operate these parts and keep them cooled. It can also help to open your case to regulate hot air. Just make sure you keep the open side away from your feet, your dog or whatever. I recommend you only open the case when you want to install new parts.

-Internal Engine issues:
This happens to me in The last Sylvannas mission and the older versions of DOTA. It could preform an operation that the system really hates. Wait until future versions of the map come, it could solve the problem about whats happening. For me, this also happens sometimes when I cast Storm, Earth and Fire in Melee or when I transition a hero unit to something like a bear or a storm crow (hero > unit or unit > hero by skill, not trigger). As patches go on, some of these bugs are corrected.

-CD Cracks (for you warez boys out there )
You most likely have a CD key or an illegal burned copy that needs libraries or certain files that would appreciate it if you had the real version. Do us all a favor and buy the REAL expansion, reinstall Wc3, and that should fix your problem.

If you decide to reinstall Wc3, keep your maps you want to keep in a seperate folder so you can copy them to the map folder later. The only reason you may want to reinstall is if you reformat your Hard Drive.

If you need any further questions, PM me or contact me on MSN. If you do so in a inpolite way, have had the problem only occur once or rarely; I will NOT! answer you back, I may even block you. I want to help, but I am a busy person sometimes and I don’t appreciate getting **** yous or assholes when I want to explain how to fix your motherboard problems.

Источник

Содержание

FATAL ERROR! Как боротся?
fatal error
[Solved] What can anyone tell me about this crash error?
Kakerate
Kakerate
ZiBitheWand3r3r
ZiBitheWand3r3r
Resources
Kakerate
Kakerate
PublishedShadow
PublishedShadow
Resources

FATAL ERROR! Как боротся?

у меня когда играю в доту вылетает ошибка(может в начале. конце когда угодно):
war3
This application has encountered a critical error:

Program E:GAMESwarcraftIIIwar3.exe
Exception: 0xc0000005(ACCESS_VIOLATION)at 001B:6F4CBDBB5
Thi instruction at ‘0x6F4CBDB5’ referenced at ‘OxXE8873AC’
This memory could not be ‘read’.

Press OK to terminate the application

Умоляю помогите.
Я с етим оч долго мучаюсь.

А также, кто знает англ, советую прочитать:

HELLWOLF’S GUIDE TO FIXING FATAL ERRORS — AN ADDON TO N_’s INFORMATION

-Models could be rendered incorrectly (updates and fixes, custom models)
Not really a common problem, was in DOTA. Some custom models may have not been done incorrectly and the game will crash. Not much you can do, update your game and use models that work properly for best effects.

Источник

fatal error

This application has encountered a critical error:

Program: c:gamezwarcraft iiiwar3.exe
Exception: 0xC0000005 (ACCES_VIOLATION) at 001B:6F001120

The instruction at ‘0x6F001120’ referenced memory at ‘0xD329E6A4’
The memory could not be read.

Вот такая ошибка вылетает при запуске варика. Пробовал качать разные версии варика, разные патчи. Пробовал менять местами память оперативную. Проверял на вирусы. Удалил свой антивирус нод32. Менял дрова на видюху. Ошибка продалжает вылетать.
Подскажите плз что ещё может быть не так?

Nod32 хороший антивирус,зря так на него.
Варкрафт в принципе довольно дырявая игра — фаталы в ней не редкость (у меня довольно часто при выходе случается)

Смысл ошибки в следующем: команда по некоему адресу ссылается на неположенное место, так как тот участок памяти не может быть прочитан.
Скорее всего (раз ставил всякие разные версии вара и все это продолжалось) проблема в винде. Попробуй переустановить систему (Windows довольно капризная система, тем более если качает обновления с инета — ибо неизвестно что майкрософтовцы подсовывают и, следовательно, непонятно к чему приведет)

Kvel92
типо микрософт не шарит ничево в винде а я реал-про программер))
если бы ты хоть что-то знал, то не говорил бы всякой ерунды, приведу пример для лолок:
в какой-то (уже не помню) версии виндоус была зашита программа-шпион, очевидно, вставленная специально и хз с каким умыслом. И в следующий раз, перед тем как что-то писать, подумай нужен ли этот бред здесь.
и если ты действительно ничего так и не понял, то поясню эти слова: ибо неизвестно что майкрософтовцы подсовывают — это означает, что майкрософтовцы (девелоперы, если угодно) создают различного рода обновления для своей операционной системы, при этом обновления, как правило, касаются безопасности системы, тогда логичным является то, что вместо защиты, может быть создана некая программа-шпион.

DES-SHARKER
может быть у него windows 3.1 =O

Источник

[Solved] What can anyone tell me about this crash error?

Kakerate

The translation for this is: an instruction tried to reference memory at a very low memory address (in this case: ‘0x0000000C’). Your OS denied Warcraft III access to this memory address (as it has no rights to access memory outside of it’s environment), throwing the exception.

In most cases, this tells you that you tried to access a variable that hasn’t been properly initialized. Possible causes for this is a double-free of a variable or a plain and simple coding error, trying to read a variable that doesn’t exist.

Which seems like the case with mine as well ‘0x0000001C’

How do I go about finding exactly what caused this?

ZiBitheWand3r3r

Resources

Kakerate

In all the crashes, this is the error:
«The instruction at ‘0x6F430C91’ referenced memory at ‘0x0000001C’.»

So how can I find out whats running that crashing it?

I checked out that link, but afaik it’s not any of the listed reasons.

edit: a couple times when the map crashed, it was immediately after a Neutral Passive hero killed a Neutral Hostile Unit. No clue what could cause that. Some other times it just seemed to crash from attacks by the Neutral Passive hero.

PublishedShadow

Resources

Were you playing the map alone or with other people?

To better help we need to know what exactly was happening at the time of the crash. In a multiplayer map, what was EVERYONE doing at the time of the crash? A crash report won’t really narrow it down. With that being said, I’ve seen several instances when a unit was selected it caused a crash. This could be for several reasons, but a big one you should check is:

12 — Custom icon files need to be prepared in a proper way, or WC3 will crash when trying to load them (which may be map init, or may be the selection of a tavern selling units with custom icons, etc.) Sadly, the default settings for Button Manager produce Mac-incompatible icons; read here for compatible settings.

Источник

Code:

Memory cannot be 'read' ;
==============================================================================
Warcraft III (build 6401)

Exe:      c:program files (x86)warcraft 3war3.exe
Time:     Jan  5, 2016  5:41:19.253 PM
User:     Paul
Computer: PAUL-PC
------------------------------------------------------------------------------

This application has encountered a critical error:

FATAL ERROR!

Program:	c:program files (x86)warcraft 3war3.exe
Exception:	0xC0000005 (ACCESS_VIOLATION) at 0023:6F430C91

The instruction at '0x6F430C91' referenced memory at '0x0000001C'.
The memory could not be 'read'.


War3Build: 1.26.0.6401
Played MapsTesttest.w3x
Player  0 Player 1          	Race Human	StartLoc  0
Player  1 Player 2          	Race Human	StartLoc  1
Player  2 Player 3          	Race Human	StartLoc  2
Player  3 Player 4          	Race Human	StartLoc  3
Player  4 Player 5          	Race Human	StartLoc  4
Player  5 Player 6          	Race Human	StartLoc  5
Player  6 WorldEdit         	Race Human	StartLoc  3
Player  7 Player 8          	Race Human	StartLoc  7
Player  8 Player 9          	Race Human	StartLoc  8
Player  9 Player 10         	Race Human	StartLoc  9
Player 10 Player 11         	Race Human	StartLoc 10
Player 11 Player 12         	Race Human	StartLoc 11
------------------------------------------------------------------------------

----------------------------------------
    x86 Registers
----------------------------------------

EAX=0C4327B4  EBX=0C4327B4  ECX=0C4327B4  EDX=00000000  ESI=0000000C
EDI=0018F0C4  EBP=0000000C  ESP=0018F048  EIP=6F430C91  FLG=00210206
CS =0023      DS =002B      ES =002B      SS =002B      FS =0053      GS =002B


----------------------------------------
    Stack Trace (Manual)
----------------------------------------

Address  Frame    Logical addr  Module

6F430C91 0000000C 0001:0042FC91 c:program files (x86)warcraft 3Game.dll

----------------------------------------
    Stack Trace (Using DBGHELP.DLL)
----------------------------------------

6F430C91 Game.dll     GameMain+4355137 (0x0000000C,0x00000000,0x6F9473BE,0x6F45D1B8)


----------------------------------------
    Loaded Modules
----------------------------------------

0x00400000 - 0x0047D000  c:program files (x86)warcraft 3war3.exe
0x15000000 - 0x15061000  c:program files (x86)warcraft 3Storm.dll
0x21100000 - 0x2115F000  c:program files (x86)warcraft 3mss32.dll
0x22600000 - 0x22616000  c:program files (x86)warcraft 3redistmilesMssfast.m3d
0x22700000 - 0x22717000  c:program files (x86)warcraft 3redistmilesMssdolby.m3d
0x22C00000 - 0x22C18000  c:program files (x86)warcraft 3redistmilesMsseax2.m3d
0x24600000 - 0x24611000  c:program files (x86)warcraft 3redistmilesReverb3.flt
0x26F00000 - 0x26F2A000  c:program files (x86)warcraft 3redistmilesMp3dec.asi
0x5C430000 - 0x5C705000  C:Windowssystem32nvapi.dll
0x60000000 - 0x6005D000  c:program files (x86)warcraft 3ijl15.dll
0x63320000 - 0x6345A000  C:Program Files (x86)NVIDIA Corporation3D VisionnvSCPAPI.dll
0x63700000 - 0x644CE000  C:Windowssystem32nvd3dum.dll
0x651E0000 - 0x652E5000  C:Windowssystem32d3d8.dll
0x66EF0000 - 0x66F15000  C:Windowssystem32powrprof.dll
0x66FE0000 - 0x66FE7000  C:Windowssystem32avrt.dll
0x670B0000 - 0x67122000  C:Windowssystem32DSOUND.DLL
0x67130000 - 0x671CB000  C:WindowsWinSxSx86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fcMSVCR80.dll
0x67460000 - 0x67555000  C:WindowsSystem32PROPSYS.dll
0x67560000 - 0x67599000  C:WindowsSystem32MMDevApi.dll
0x675A0000 - 0x675D6000  C:Windowssystem32AUDIOSES.DLL
0x6A6D0000 - 0x6A7B7000  C:Windowssystem32DDRAW.dll
0x6A7C0000 - 0x6A888000  C:Windowssystem32OPENGL32.dll
0x6F000000 - 0x6FBB5000  c:program files (x86)warcraft 3Game.dll
0x6FD30000 - 0x6FD6B000  C:Windowssystem32rsaenh.dll
0x6FD70000 - 0x6FD87000  C:Windowssystem32CRYPTSP.dll
0x71810000 - 0x71816000  C:Windowssystem32DCIMAN32.dll
0x71870000 - 0x7188C000  C:Windowssystem32cryptnet.dll
0x71890000 - 0x718CD000  C:WindowsSysWOW64bcryptprimitives.dll
0x718D0000 - 0x718F2000  C:Windowssystem32GLU32.dll
0x719E0000 - 0x71ACB000  C:Windowssystem32dbghelp.dll
0x71AD0000 - 0x71B50000  C:Windowssystem32uxtheme.dll
0x71B50000 - 0x71B82000  C:Windowssystem32WINMM.dll
0x71B90000 - 0x71BA3000  C:Windowssystem32dwmapi.dll
0x71BB0000 - 0x71BB6000  C:Windowssystem32d3d8thk.dll
0x71E70000 - 0x71E77000  C:Windowssystem32WSOCK32.dll
0x72260000 - 0x72277000  C:Windowssystem32bcrypt.dll
0x72650000 - 0x72666000  C:Windowssystem32GPAPI.dll
0x727D0000 - 0x727D6000  C:Windowssystem32SensApi.dll
0x727E0000 - 0x72819000  C:Windowssystem32ncrypt.dll
0x72820000 - 0x728A4000  C:WindowsWinSxSx86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18837_none_ec86b8d6858ec0bcCOMCTL32.dll
0x72A30000 - 0x72A6C000  C:Windowssystem32mswsock.dll
0x75270000 - 0x75291000  C:Windowssystem32ntmarta.dll
0x75300000 - 0x75309000  C:Windowssystem32VERSION.dll
0x753D0000 - 0x753DC000  C:Windowssyswow64CRYPTBASE.dll
0x753E0000 - 0x75440000  C:Windowssyswow64SspiCli.dll
0x75440000 - 0x754D0000  C:Windowssyswow64GDI32.dll
0x754D0000 - 0x754D3000  C:Windowssyswow64api-ms-win-downlevel-normaliz-l1-1-0.dll
0x754E0000 - 0x75581000  C:Windowssyswow64ADVAPI32.dll
0x75590000 - 0x755BF000  C:Windowssyswow64WINTRUST.dll
0x755C0000 - 0x75605000  C:Windowssyswow64WLDAP32.dll
0x75610000 - 0x75670000  C:Windowssyswow64IMM32.dll
0x75670000 - 0x756FF000  C:Windowssyswow64OLEAUT32.dll
0x75760000 - 0x75992000  C:Windowssyswow64iertutil.dll
0x759A0000 - 0x75A3D000  C:Windowssyswow64USP10.dll
0x75A40000 - 0x75C33000  C:Windowssyswow64WININET.dll
0x75C40000 - 0x75C46000  C:Windowssyswow64NSI.dll
0x75DA0000 - 0x75DA4000  C:Windowssyswow64api-ms-win-downlevel-shlwapi-l1-1-0.dll
0x75DC0000 - 0x75E6C000  C:Windowssyswow64msvcrt.dll
0x75E70000 - 0x75F60000  C:Windowssyswow64RPCRT4.dll
0x75F60000 - 0x75FA7000  C:Windowssyswow64KERNELBASE.dll
0x75FB0000 - 0x75FB3000  C:Windowssyswow64normaliz.DLL
0x75FC0000 - 0x760D0000  C:Windowssyswow64kernel32.dll
0x76100000 - 0x76105000  C:Windowssyswow64PSAPI.DLL
0x76110000 - 0x762AD000  C:Windowssyswow64SETUPAPI.dll
0x762B0000 - 0x762BA000  C:Windowssyswow64LPK.dll
0x762C0000 - 0x762D9000  C:WindowsSysWOW64sechost.dll
0x762E0000 - 0x76315000  C:Windowssyswow64WS2_32.dll
0x76320000 - 0x76377000  C:Windowssyswow64SHLWAPI.dll
0x76380000 - 0x76403000  C:Windowssyswow64CLBCatQ.DLL
0x764A0000 - 0x764A5000  C:Windowssyswow64api-ms-win-downlevel-advapi32-l1-1-0.dll
0x764B0000 - 0x765B0000  C:Windowssyswow64USER32.dll
0x765B0000 - 0x765B4000  C:Windowssyswow64api-ms-win-downlevel-user32-l1-1-0.dll
0x765C0000 - 0x765D7000  C:Windowssyswow64USERENV.dll
0x765E0000 - 0x765F2000  C:Windowssyswow64DEVOBJ.dll
0x76600000 - 0x7724B000  C:Windowssyswow64SHELL32.dll
0x77250000 - 0x773AC000  C:Windowssyswow64ole32.dll
0x773B0000 - 0x7742B000  C:Windowssyswow64comdlg32.dll
0x77430000 - 0x7743C000  C:Windowssyswow64MSASN1.dll
0x77440000 - 0x77444000  C:Windowssyswow64api-ms-win-downlevel-version-l1-1-0.dll
0x77450000 - 0x77571000  C:Windowssyswow64CRYPT32.dll
0x77580000 - 0x775A7000  C:Windowssyswow64CFGMGR32.dll
0x775B0000 - 0x7767C000  C:Windowssyswow64MSCTF.dll
0x77A50000 - 0x77A5B000  C:Windowssyswow64profapi.dll
0x77A80000 - 0x77C00000  C:WindowsSysWOW64ntdll.dll


----------------------------------------
    Memory Dump
----------------------------------------

Code: 16 bytes starting at (EIP = 6F430C91)

6F430C91: 8B 75 10 8B  4D 0C 8B D6  E8 92 ED C0  FF 85 C0 0F  .u..M...........


Stack: 1024 bytes starting at (ESP = 0018F048)

* = addr                            **                                *       
0018F040: 00 00 00 00  75 91 45 6F  0C 00 00 00  1C F1 18 00  ....u.Eo........
0018F050: FF FF FF FF  58 BB 3B 6F  0C 00 00 00  00 00 00 00  ....X.;o........
0018F060: BE 73 94 6F  B8 D1 45 6F  11 00 00 00  A4 D1 45 6F  .s.o..Eo......Eo
0018F070: 11 00 00 00  9C D1 45 6F  A0 35 6D 0F  88 00 17 03  ......Eo.5m.....
0018F080: 08 00 00 00  B8 D1 45 6F  09 00 10 00  DC 1F 10 00  ......Eo........
0018F090: B8 82 6D 0F  DC 1F 10 00  D6 B7 45 6F  88 00 17 03  ..m.......Eo....
0018F0A0: D0 F0 18 00  93 A0 45 6F  6A 0A 4B E8  00 00 00 00  ......Eoj.K.....
0018F0B0: D0 F0 18 00  F8 F0 18 00  28 E6 82 6F  00 00 00 00  ........(..o....
0018F0C0: 11 00 00 00  A0 02 AE 0E  E0 35 6D 0F  6D BB 46 86  .........5m.m.F.
0018F0D0: 0C 00 00 00  E0 35 6D 0F  97 3C 03 15  20 D2 6D 0F  .....5m..<.. .m.
0018F0E0: E0 35 6D 0F  FF FF FF 7F  A0 00 F0 06  D0 90 9E 06  .5m.............
0018F0F0: F4 CD 44 6F  20 D2 6D 0F  E0 35 6D 0F  04 00 00 00  ..Do .m..5m.....
0018F100: C0 F0 18 00  94 90 9E 06  50 01 AE 0E  04 00 00 00  ........P.......
0018F110: 01 00 00 00  30 BB 3B 6F  DA 0B 4B E8  04 00 00 00  ....0.;o..K.....
0018F120: AE EF 45 6F  A0 35 6D 0F  EA 0B 4B E8  00 00 00 00  ..Eo.5m...K.....
0018F130: 88 00 17 03  00 00 00 00  AC 00 17 03  00 00 76 0E  ..............v.
0018F140: 00 04 00 00  00 00 00 00  00 00 00 00  26 00 00 00  ............&...
0018F150: 00 00 00 00  00 00 00 00  00 00 00 00  48 5D 02 15  ............H]..
0018F160: 00 04 00 00  E2 5D 02 15  80 00 76 0E  D6 B7 45 6F  .....]....v...Eo
0018F170: 88 00 17 03  A4 F1 18 00  93 A0 45 6F  46 0B 4B E8  ..........EoF.K.
0018F180: 00 00 00 00  A4 F1 18 00  CC F1 18 00  28 E6 82 6F  ............(..o
0018F190: 00 00 00 00  32 E8 45 6F  5A 0B 4B E8  00 00 00 00  ....2.EoZ.K.....
0018F1A0: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0018F1B0: 00 00 00 00  01 00 00 00  01 00 00 00  32 A9 02 00  ............2...
0018F1C0: 00 00 00 00  F0 F2 18 00  A8 E8 82 6F  FF FF FF FF  ...........o....
0018F1D0: 03 FC 45 6F  70 A4 6E 10  7C F2 18 00  E0 93 04 00  ..Eop.n.|.......
0018F1E0: 00 00 00 00  73 00 00 00  88 00 17 03  CC 00 78 0C  ....s.........x.
0018F1F0: C0 00 78 0C  D4 B6 44 6F  70 A4 6E 10  00 00 00 00  ..x...Dop.n.....
0018F200: 7C F2 18 00  E0 93 04 00  00 00 00 00  00 00 00 00  |...............
0018F210: 7C F2 18 00  64 FF 91 23  96 83 3A 6F  00 00 00 00  |...d..#..:o....
0018F220: 7C F2 18 00  E0 93 04 00  00 00 00 00  00 00 00 00  |...............
0018F230: 00 00 00 00  5C 12 79 0C  00 00 00 00  74 0C 7D 0C  .....y.....t.}.
0018F240: C4 A8 3B 6F  73 00 00 00  7C F2 18 00  64 FF 91 23  ..;os...|...d..#
0018F250: 00 00 00 00  00 00 00 00  14 FF 91 23  55 58 44 6F  ...........#UXDo
0018F260: 7C F2 18 00  64 FF 91 23  00 00 00 00  00 00 00 00  |...d..#........
0018F270: 14 FF 91 23  64 FF 91 23  14 FF 91 23  00 00 00 00  ...#d..#...#....
0018F280: F6 73 44 6F  64 FF 91 23  00 00 00 00  14 FF 91 23  .sDod..#.......#
0018F290: 14 FF 91 23  08 49 06 1F  38 FF 91 23  00 00 00 00  ...#.I..8..#....
0018F2A0: 08 49 06 1F  38 FF 91 23  14 FF 91 23  8F 00 6E DC  .I..8..#...#..n.
0018F2B0: 33 50 44 6F  72 50 44 6F  00 00 00 00  14 FF 91 23  3PDorPDo.......#
0018F2C0: 38 FF 91 23  08 49 06 1F  82 7F 44 6F  16 08 4B E8  8..#.I....Do..K.
0018F2D0: FF FF FF FF  38 32 FD 1C  44 35 8C 23  88 00 B2 06  ....82..D5.#....
0018F2E0: FC 31 FD 1C  44 35 8C 23  88 00 B2 06  14 FF 91 23  .1..D5.#.......#
0018F2F0: 50 F3 18 00  51 DE 82 6F  FF FF FF FF  64 82 44 6F  P...Q..o....d.Do
0018F300: 38 32 FD 1C  C3 CD 02 E3  00 00 00 00  D6 09 4B E8  82............K.
0018F310: FC 31 FD 1C  FC 31 FD 1C  9C 00 82 0C  14 FF 91 23  .1...1.........#
0018F320: 78 65 74 2B  6C 67 61 2B  78 65 74 2B  00 00 00 00  xet+lga+xet+....
0018F330: 9C E2 3C 0C  0C 72 AB 6F  00 00 00 00  00 00 00 00  ..<..r.o........
0018F340: 00 00 00 00  00 00 00 00  FF FF FF FF  FF FF FF FF  ................
0018F350: BC F3 18 00  A8 DE 82 6F  00 00 00 00  CB 82 44 6F  .......o......Do
0018F360: 00 00 00 00  B4 27 43 0C  36 84 44 6F  94 CE 57 20  .....'C.6.Do..W 
0018F370: 94 CE 57 20  3C 86 CD 19  2C F6 34 20  FD A6 62 6F  ..W <...,.4 ..bo
0018F380: 90 00 15 03  4E 09 4B E8  9C 00 82 0C  44 35 8C 23  ....N.K.....D5.#
0018F390: 90 00 15 03  44 35 8C 23  00 00 00 00  02 00 00 00  ....D5.#........
0018F3A0: 2C F6 34 20  AC F3 18 00  94 CE 57 20  94 CE 57 20  ,.4 ......W ..W 
0018F3B0: 28 F4 18 00  00 00 00 00  E0 01 00 00  50 F4 18 00  (...........P...
0018F3C0: 88 0A 84 6F  00 00 00 00  D0 A7 62 6F  14 02 08 00  ...o......bo....
0018F3D0: 90 00 15 03  9C 00 82 0C  84 FE 94 6F  A1 9A 62 6F  ...........o..bo
0018F3E0: 14 02 08 00  90 00 15 03  EC 7F 43 0C  FD 71 43 6F  ..........C..qCo
0018F3F0: 90 00 15 03  1C 2E DE 09  84 CE 57 20  84 CE 57 20  ..........W ..W 
0018F400: 54 0C CD 19  B4 27 43 0C  01 00 00 00  B4 44 0D 21  T....'C......D.!
0018F410: FD A6 62 6F  90 00 15 03  DA 0E 4B E8  B4 27 43 0C  ..bo......K..'C.
0018F420: EC 7F 43 0C  9C 00 82 0C  EC 7F 43 0C  00 00 00 00  ..C.......C.....
0018F430: 14 00 00 00  1C 2E DE 09  84 C8 56 20  44 1D 7F 1C  ..........V D...
0018F440: 44 1D 7F 1C  BF 18 47 6F  00 00 00 00  6C F4 18 00  D.....Go....l...


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

On a different THW post about this, Zwiebelchen said,

The translation for this is: an instruction tried to reference memory at a very low memory address (in this case: ‘0x0000000C’). Your OS denied Warcraft III access to this memory address (as it has no rights to access memory outside of it’s environment), throwing the exception.

In most cases, this tells you that you tried to access a variable that hasn’t been properly initialized. Possible causes for this is a double-free of a variable or a plain and simple coding error, trying to read a variable that doesn’t exist.

Which seems like the case with mine as well ‘0x0000001C’

How do I go about finding exactly what caused this?

Last edited by a moderator: Jan 6, 2016

check metamorphosis based (and similar) spells
and this

In all the crashes, this is the error:
«The instruction at ‘0x6F430C91’ referenced memory at ‘0x0000001C’.»

So how can I find out whats running that crashing it?

I checked out that link, but afaik it’s not any of the listed reasons.

Last edited: Jan 6, 2016

Were you playing the map alone or with other people?

edit: a couple times when the map crashed, it was immediately after a Neutral Passive hero killed a Neutral Hostile Unit. No clue what could cause that. Some other times it just seemed to crash from attacks by the Neutral Passive hero.

That makes me wonder about the attack type, and if there is an orb effect. Is there an ability involved? Try to duplicate the crash by controlling the suspected unit or creating a test trigger forcing the neutral unit attacking to debug.

It was caused by a trigger that ran when Neutral Hostile units were killed. I fed a parameter for a player number that was the killing unit’s number +1, instead of -1.

After finding that mistake I was able to fix it. I was basically feeding a player number too high into a function making it crash. rip. Thanks though. ^^

Источник