Question:
I have encountered an error when i start up my warcraft 3 TFT application.?
3vilMTV
2008-08-31 19:24:42 UTC
I've just switched to the original copy of warcraft 3.
but after reinstalling, i can't even start up the application.
Even after updates, crack or whatever i could think up of.
It would just show the black screen for 2 or 3 secs and then crash.
*Previously it was perfectly ok, so its not related to hardware.

Hope this helps:

==============================================================================
Warcraft III (build 6328)

Exe: E:\Warcraft III The Frozen Throne\War3.exe
Time: Sep 1, 2008 10:14:57.562 AM
User: Disneyxy
Computer: DRAGON
------------------------------------------------------------------------------

This application has encountered a critical error:

FATAL ERROR!

Program: E:\Warcraft III The Frozen Throne\War3.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:6F51C758

The instruction at '0x6F51C758' referenced memory at '0x00000000'.
The memory could not be 'read'.

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

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

EAX=00000000 EBX=00000000 ECX=00000000 EDX=0012FA8C ESI=00000000
EDI=00230144 EBP=00000000 ESP=0012FA7C EIP=6F51C758 FLG=00210246
CS =001B DS =0023 ES =0023 SS =0023 FS =003B GS =0000


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

Address Frame Logical addr Module

6F51C758 00000000 0001:0051B758 E:\Warcraft III The Frozen Throne\Game.dll

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

6F51C758 Game.dll +0 (0x00000000,0x00000000,0x00000000,0x00000000)


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

0x00340000 - 0x00349000 Normaliz.dll
0x00400000 - 0x0047D000 War3.exe
0x0FFD0000 - 0x0FFF8000 rsaenh.dll
0x10000000 - 0x10005000 avgrsstx.dll
0x15000000 - 0x15061000 Storm.dll
0x20000000 - 0x202C5000 xpsp2res.dll
0x21100000 - 0x2115F000 mss32.dll
0x4D4F0000 - 0x4D548000 WINHTTP.dll
0x59A60000 - 0x59B01000 dbghelp.dll
0x5AD70000 - 0x5ADA8000 uxtheme.dll
0x5B860000 - 0x5B8B4000 netapi32.dll
0x5D090000 - 0x5D12A000 COMCTL32.dll
0x5ED00000 - 0x5EDCC000 OPENGL32.dll
0x60000000 - 0x6005D000 ijl15.dll
0x629C0000 - 0x629C9000 LPK.DLL
0x68B20000 - 0x68B40000 GLU32.dll
0x6F000000 - 0x6FBA0000 Game.dll
0x71AA0000 - 0x71AA8000 WS2HELP.dll
0x71AB0000 - 0x71AC7000 WS2_32.dll
0x71AD0000 - 0x71AD9000 WSOCK32.dll
0x71BF0000 - 0x71C03000 SAMLIB.dll
0x722B0000 - 0x722B5000 SensApi.dll
0x73760000 - 0x737A9000 DDRAW.dll
0x73BC0000 - 0x73BC6000 DCIMAN32.dll
0x74720000 - 0x7476B000 MSCTF.dll
0x74810000 - 0x7497D000 quartz.dll
0x74D90000 - 0x74DFB000 USP10.dll
0x755C0000 - 0x755EE000 msctfime.ime
0x75E60000 - 0x75E73000 cryptnet.dll
0x76390000 - 0x763AD000 IMM32.dll
0x763B0000 - 0x763F9000 comdlg32.dll
0x769C0000 - 0x76A73000 userenv.dll
0x76B40000 - 0x76B6D000 WINMM.dll
0x76C30000 - 0x76C5E000 WINTRUST.dll
0x76C90000 - 0x76CB8000 IMAGEHLP.dll
0x76F60000 - 0x76F8C000 WLDAP32.dll
0x76FD0000 - 0x7704F000 CLBCATQ.DLL
0x77050000 - 0x77115000 COMRes.dll
0x77120000 - 0x771AB000 OLEAUT32.dll
0x773D0000 - 0x774D3000 comctl32.dll
0x774E0000 - 0x7761D000 ole32.dll
0x77690000 - 0x776B1000 NTMARTA.DLL
0x77A80000 - 0x77B14000 CRYPT32.dll
0x77B20000 - 0x77B32000 MSASN1.dll
0x77C00000 - 0x77C08000 VERSION.dll
0x77C10000 - 0x77C68000 msvcrt.dll
0x77DD0000 - 0x77E6B000 ADVAPI32.dll
0x77E70000 - 0x77F02000 RPCRT4.dll
0x77F10000 - 0x77F57000 GDI32.dll
0x77F60000 - 0x77FD6000 SHLWAPI.dll
0x77FE0000 - 0x77FF1000 Secur32.dll
0x78000000 - 0x78045000 iertutil.dll
0x78050000 - 0x78120000 WININET.dll
0x78130000 - 0x781CB000 MSVCR80.dll
0x7C800000 - 0x7C8F5000 kernel32.dll
0x7C900000 - 0x7C9B0000 ntdll.dll
0x7C9C0000 - 0x7D1D6000 SHELL32.dll
0x7E410000 - 0x7E4A0000 USER32.dll


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

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

6F51C758: 8B 08 68 08 B3 97 6F 50 8B 01 FF D0 3B C6 7D 14 ..h...oP....;.}.


Stack: 1024 bytes starting at (ESP = 0012FA7C)

* = addr ** *
0012FA70: 00 00 00 00 48 DE 12 00 00 00 00 00 8C FA 12 00 ....H...........
0012FA80: 50 C8 51 6F 14 FB 12 00 00 00 00 00 59 D5 41 7E P.Qo........Y.A~
0012FA90: 00 00 00 00 44 01 23 00 00 02 00 00 FB C9 51 6F ....D.#.......Qo
0012FAA0: 44 01 23 00 50 FB 12 00 96 F8 41 7E 40 04 67 00 D.#.P.....A~@.g.
0012FAB0: 00 00 00 00 00 00 00 00 02 E0 42 7E 00 FB 12 00 ..........B~....
0012FAC0: 14 0F 73 74 4D 01 01 00 00 00 00 00 01 00 00 00 ..stM...........
0012FAD0: 19 0F 73 74 00 00 00 00 00 E0 FD 7F 02 E0 42 7E .
Three answers:
Ninja_Jesus
2008-08-31 20:15:03 UTC
This is most probably because you are using a crack.



Do a clean reinstall and then install the latest update. The latest update removes the need for the CD in the drive when playing, so you won't need to use a crack.



Download the latest Warcraft 3 update here:

http://us.blizzard.com/support/article.xml?articleId=21220
2014-08-24 21:30:41 UTC
Hi,

You can download Warcraft III The Frozen Throne for free here: http://bitly.com/1uSFZwd



Amongst the novelties of this patch you can find some new maps for playing in the multiplayer mode, map changes, and fixes that could ruin the game experience.

I love it!
mccaskey
2016-12-15 02:23:26 UTC
i'm getting this mistake each and every so often besides. based once you get it and so on it particularly is alot of issues. What has got here approximately is that warcraft has lost the rights to a area of memory and it particularly is not stable. abode windows does not like classes gaining access to memory it particularly is not meant to. If it occurs whenever you do something in a custom map. it particularly is the map makers fault. If it occurs randomly it particularly is blizzards fault. not alot you're able to do besides customary cleansing of your laptop definite it particularly is noted as a memory leak. occurs with the terrific of classes. particularly you have counsel that factor to aspects of ram so if the pointer is deleted and the information isn't released you have a memory leak considering that memory remains owned yet unusable. the possibilities of it failing improve with length of a interest


ⓘ
This content was originally posted on Y! Answers, a Q&A website that shut down in 2021.
Loading...