А также, кто знает англ, советую прочитать:
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.
Часто во время запуска World of Warcraft возникают разнообразные ошибки. Сегодня поговорим об одной из них…
Сообщение this application has encountered a critical error обычно возникает в процессе игры. Данное сообщение предупреждает пользователя о возникновении системного сбоя. Данная ошибка всегда имеет различные цифры, которые идут после слова ERROR. Например, ERROR #121, где 121 — номер ошибки.
[adace-ad id=»5173″]
Коды ошибок могут быть следующими: 0, 121, 124, 131, 132, 134. Несмотря на разные коды причина всех ошибок, как правило, одна — это нехватка оперативной памяти для выполнения программы
Играть в World of Warcraft когда постоянно возникает критическая ошибка, естественно, невозможно.
Ошибка недостаточного объема оперативной памяти неслучайно возникает именно в играх — они кушают наибольшее количество ресурсов компьютера. Если сообщение This application has encountered a critical error появляется неоднократно нужно первым делом выйти из World of Warcraft и перезагрузить компьютер.
Идем в каталог с установленной игрой и находим папку WTF — её нужно будет полностью удалить. Переживать не стоит — дело в том, что даже после удаления данная папка снова создастся при следующем старте WOW. Удаление папки WTF — это мера, которая которая призвана очистить временные файлы
Временные и другие мусорные файлу могут накапливаться в каталоге с игрой, занимая большое количество места на диске. Если ошибка возникает не в World of Warcraft, а в какой-либо иной игре нужно в каталоге с ней отыскать папку временных файлов и очистить её.
После удаления папки WTF необходимо инсталлировать утилиту CCleaner. Запускаем её и очищаем реестр, а затем данные программ. Так же необходимо убедиться в том, что драйверы материнской платы, звуковой карты, видео и сетевой платы находятся в актуальном состоянии.
Операционная система также должна иметь последние обновления. Можно также установить диагностическое ПО, которое покажет все проблемы компьютера
После выполнения всех указанных выше действий ошибка this application has encountered a critical error должна исчезнуть.
Here’s the complete log for one of the errors:
==============================================================================
Warcraft III (build 6300)
Exe: c:program files (x86)warcraft iiiwar3.exe
Time: Jun 9, 2014 10:59:01.170 PM
User: Rienskje
Computer: HomeSweetHome-PC
——————————————————————————
This application has encountered a critical error:
FATAL ERROR!
Program: c:program files (x86)warcraft iiiwar3.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:70A9FC10
The instruction at ‘0x70A9FC10’ referenced memory at ‘0x70A9FC10’.
The memory could not be ‘read’.
——————————————————————————
—————————————-
x86 Registers
—————————————-
EAX=70A9FC10 EBX=0018F3F0 ECX=9E759524 EDX=04B7BBE4 ESI=0058CA98
EDI=0378CD60 EBP=0018F3B4 ESP=0018F2FC EIP=70A9FC10 FLG=00210246
CS =0023 DS =002B ES =002B SS =002B FS =0053 GS =002B
—————————————-
Stack Trace (Manual)
—————————————-
Address Frame Logical addr Module
70A9FC10 0018F3B4 0000:00000000 c:program files (x86)warcraft iiiwar3.exe
74092002 0018F45C 0001:00011002 C:WINDOWSSYSTEM32d3d8.dll
74092256 0018F4B4 0001:00011256 C:WINDOWSSYSTEM32d3d8.dll
740E2AAE 0018F5C0 0001:00061AAE C:WINDOWSSYSTEM32d3d8.dll
740E388E 0018F630 0001:0006288E C:WINDOWSSYSTEM32d3d8.dll
740E256C 0018F644 0001:0006156C C:WINDOWSSYSTEM32d3d8.dll
740DCEA3 0018F7B8 0001:0005BEA3 C:WINDOWSSYSTEM32d3d8.dll
740B2CCB 0018F814 0001:00031CCB C:WINDOWSSYSTEM32d3d8.dll
6F0D0559 0018F874 0001:000CF559 c:program files (x86)warcraft iiiGame.dll
6F0D045C 0018FCC8 0001:000CF45C c:program files (x86)warcraft iiiGame.dll
6F0D0845 0018FCE0 0001:000CF845 c:program files (x86)warcraft iiiGame.dll
6F0C8377 0018FD08 0001:000C7377 c:program files (x86)warcraft iiiGame.dll
6F0069E1 0018FD34 0001:000059E1 c:program files (x86)warcraft iiiGame.dll
6F0060BD 0018FE44 0001:000050BD c:program files (x86)warcraft iiiGame.dll
00401219 0018FEF0 0001:00000219 c:program files (x86)warcraft iiiwar3.exe
00401D68 0018FF8C 0001:00000D68 c:program files (x86)warcraft iiiwar3.exe
7713919F 0018FF98 0001:0000919F C:WINDOWSSYSTEM32KERNEL32.DLL
7752A8CB 0018FFDC 0001:000498CB C:WINDOWSSYSTEM32ntdll.dll
7752A8A1 0018FFEC 0001:000498A1 C:WINDOWSSYSTEM32ntdll.dll
—————————————-
Stack Trace (Using DBGHELP.DLL)
—————————————-
70A9FC10 <unknown module> <unknown symbol>+0 (0x036B6600,0x0018F380,0x0058CA98,0x0018F480)
740918E9 d3d8.dll DebugSetMute+15545 (0x00000000,0x00000000,0x00000000,0x00000000)
—————————————-
Loaded Modules
—————————————-
0x00400000 — 0x0046F000 c:program files (x86)warcraft iiiwar3.exe
0x0F000000 — 0x0F006000 C:Program Files (x86)NVIDIA CorporationCoProcManagerdetoured.dll
0x10000000 — 0x10101000 C:WINDOWSsystem32nvspcap.dll
0x15000000 — 0x15067000 c:program files (x86)warcraft iiiStorm.dll
0x21100000 — 0x2115F000 c:program files (x86)warcraft iiimss32.dll
0x60000000 — 0x6005D000 c:program files (x86)warcraft iiiijl15.dll
0x658C0000 — 0x658E5000 C:WINDOWSSYSTEM32cryptnet.dll
0x658F0000 — 0x6590E000 C:WINDOWSSYSTEM32gpapi.dll
0x6CC50000 — 0x6CC7B000 C:WINDOWSSYSTEM32NTASN1.dll
0x6CC80000 — 0x6CC9C000 C:WINDOWSSYSTEM32ncrypt.dll
0x6F000000 — 0x6F924000 c:program files (x86)warcraft iiiGame.dll
0x72970000 — 0x72978000 C:WINDOWSSYSTEM32WSOCK32.dll
0x735A0000 — 0x7385E000 C:WINDOWSSYSTEM32nvapi.dll
0x73860000 — 0x73933000 C:WINDOWSSYSTEM32nvumdshim.dll
0x73AF0000 — 0x73BD7000 C:WINDOWSSYSTEM32DDRAW.dll
0x73BE0000 — 0x73BFF000 C:WINDOWSSYSTEM32DEVOBJ.dll
0x73C30000 — 0x73C50000 C:Program Files (x86)NVIDIA CorporationCoProcManagernvdxgiwrap.dll
0x73C50000 — 0x73D24000 C:WINDOWSSYSTEM32OPENGL32.dll
0x73D30000 — 0x73DC9000 C:WINDOWSsystem32apphelp.dll
0x73F30000 — 0x74078000 C:WINDOWSSYSTEM32dbghelp.dll
0x74080000 — 0x7417F000 C:WINDOWSSYSTEM32d3d8.dll
0x74180000 — 0x7433D000 C:WINDOWSSYSTEM32WININET.dll
0x74470000 — 0x74689000 C:WINDOWSSYSTEM32iertutil.dll
0x74690000 — 0x746BC000 C:Program Files (x86)NVIDIA CorporationCoProcManagernvd3d9wrap.dll
0x74760000 — 0x74779000 C:WINDOWSSYSTEM32USERENV.dll
0x74780000 — 0x747AC000 C:WINDOWSsystem32nvinit.dll
0x747B0000 — 0x747D0000 C:WINDOWSSYSTEM32WINMMBASE.dll
0x747D0000 — 0x747F0000 C:WINDOWSSYSTEM32WINMM.dll
0x747F0000 — 0x7480D000 C:WINDOWSSYSTEM32bcrypt.dll
0x74810000 — 0x7483F000 C:WINDOWSsystem32rsaenh.dll
0x74840000 — 0x74858000 C:WINDOWSSYSTEM32CRYPTSP.dll
0x74870000 — 0x74877000 C:WINDOWSSYSTEM32d3d8thk.dll
0x74880000 — 0x74887000 C:WINDOWSSYSTEM32DCIMAN32.dll
0x74890000 — 0x748B4000 C:WINDOWSSYSTEM32GLU32.dll
0x748C0000 — 0x748D8000 C:WINDOWSSYSTEM32dwmapi.dll
0x748E0000 — 0x749BB000 C:WINDOWSsystem32uxtheme.dll
0x749C0000 — 0x749C9000 C:WINDOWSSYSTEM32kernel.appcore.dll
0x74A40000 — 0x74A65000 C:WINDOWSSYSTEM32ntmarta.dll
0x74AD0000 — 0x74AD8000 C:WINDOWSSYSTEM32VERSION.dll
0x74AE0000 — 0x74AEE000 C:WINDOWSSYSTEM32profapi.dll
0x74AF0000 — 0x74B66000 C:WINDOWSSYSTEM32SHCORE.DLL
0x74B70000 — 0x74B78000 C:WINDOWSSYSTEM32WINNSI.DLL
0x74B80000 — 0x74B9E000 C:WINDOWSSYSTEM32IPHLPAPI.DLL
0x74EA0000 — 0x74EF3000 C:WINDOWSSYSTEM32bcryptPrimitives.dll
0x74F00000 — 0x74F09000 C:WINDOWSSYSTEM32CRYPTBASE.dll
0x74F10000 — 0x74F2D000 C:WINDOWSSYSTEM32SspiCli.dll
0x74F30000 — 0x74FB6000 C:WINDOWSSYSTEM32comdlg32.dll
0x74FC0000 — 0x750CC000 C:WINDOWSSYSTEM32ole32.dll
0x750D0000 — 0x7510A000 C:WINDOWSSYSTEM32cfgmgr32.dll
0x75110000 — 0x75188000 C:WINDOWSSYSTEM32ADVAPI32.dll
0x75190000 — 0x751C8000 C:WINDOWSSYSTEM32WINTRUST.dll
0x751D0000 — 0x7521D000 C:WINDOWSSYSTEM32WS2_32.dll
0x75220000 — 0x7536E000 C:WINDOWSSYSTEM32combase.dll
0x75370000 — 0x75395000 C:WINDOWSSYSTEM32IMM32.dll
0x754F0000 — 0x754FE000 C:WINDOWSSYSTEM32MSASN1.dll
0x75520000 — 0x755DE000 C:WINDOWSSYSTEM32MSVCRT.dll
0x75660000 — 0x75667000 C:WINDOWSSYSTEM32NSI.dll
0x75670000 — 0x756F7000 C:WINDOWSSYSTEM32OLEAUT32.dll
0x75700000 — 0x75808000 C:WINDOWSSYSTEM32GDI32.dll
0x75810000 — 0x758DF000 C:WINDOWSSYSTEM32KERNELBASE.dll
0x75900000 — 0x76AAD000 C:WINDOWSSYSTEM32SHELL32.dll
0x76AB0000 — 0x76BA7000 C:WINDOWSSYSTEM32MSCTF.dll
0x76BB0000 — 0x76BF1000 C:WINDOWSSYSTEM32SHLWAPI.dll
0x76C00000 — 0x76C86000 C:WINDOWSWinSxSx86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.16384_none_7c55c866aa0c3ff0COMCTL32.dll
0x76C90000 — 0x76DDF000 C:WINDOWSSYSTEM32USER32.dll
0x76E50000 — 0x76F01000 C:WINDOWSSYSTEM32RPCRT4.dll
0x76F10000 — 0x76F4E000 C:WINDOWSSYSTEM32sechost.dll
0x76F50000 — 0x770CF000 C:WINDOWSSYSTEM32CRYPT32.dll
0x770D0000 — 0x7711B000 C:WINDOWSSYSTEM32WLDAP32.dll
0x77120000 — 0x77260000 C:WINDOWSSYSTEM32KERNEL32.DLL
0x77260000 — 0x7740D000 C:WINDOWSSYSTEM32SETUPAPI.dll
0x774E0000 — 0x77648000 C:WINDOWSSYSTEM32ntdll.dll
—————————————-
Memory Dump
—————————————-
Code: 16 bytes starting at (EIP = 70A9FC10)
70A9FC10: <can’t read from this address>
Stack: 1024 bytes starting at (ESP = 0018F2FC)
* = addr ** *
0018F2F0: 00 00 00 00 00 00 00 00 D8 67 6D 9E E9 18 09 74 ………gm….t
0018F300: 00 66 6B 03 80 F3 18 00 98 CA 58 00 80 F4 18 00 .fk…….X…..
0018F310: 60 CD 78 03 80 A5 6B 03 98 CA 58 00 D0 BB B7 04 `.x…k…X…..
0018F320: 00 00 00 00 00 00 00 00 00 10 00 00 04 00 00 00 …………….
0018F330: 80 17 00 80 C2 0F 00 40 00 00 00 00 00 00 00 00 …….@……..
0018F340: 50 01 00 00 00 00 00 00 01 00 00 00 80 17 00 80 P……………
0018F350: C2 0F 00 40 01 00 00 00 D0 BB B7 04 00 00 00 00 …@…………
0018F360: 00 00 00 00 00 00 00 00 00 00 00 00 80 A5 6B 03 …………..k.
0018F370: 50 01 00 00 40 22 00 80 5C 00 00 00 15 1A 09 74 P…@»……..t
0018F380: 01 00 00 00 D0 BB B7 04 40 22 00 80 00 00 00 00 ……..@»……
0018F390: 00 00 00 00 60 CD 78 03 01 00 00 00 03 00 00 00 ….`.x………
0018F3A0: 00 00 00 00 98 CA 58 00 00 00 00 00 00 00 00 00 ……X………
0018F3B0: 00 00 00 00 5C F4 18 00 02 20 09 74 F0 F3 18 00 …….. .t….
0018F3C0: 00 00 00 00 01 00 00 00 B0 F4 18 00 08 F5 18 00 …………….
0018F3D0: D8 F4 18 00 BF FD FF FF 90 06 00 00 1A 04 00 00 …………….
0018F3E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …………….
0018F3F0: 16 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 …………….
0018F400: D8 F3 18 00 01 00 00 00 00 00 00 00 00 00 00 00 …………….
0018F410: 00 00 00 00 00 00 00 00 00 00 00 00 60 CD 78 03 …………`.x.
0018F420: 00 98 00 08 01 00 00 00 00 00 00 00 1C 00 00 00 …………….
0018F430: 00 00 00 00 80 AA 6B 00 01 00 00 00 F8 F3 18 00 ……k………
0018F440: 01 00 00 00 00 00 00 00 C0 17 00 80 00 00 00 00 …………….
0018F450: C2 0F 00 40 5E 35 BB 9F 50 6F D2 04 B4 F4 18 00 …@^5..Po……
0018F460: 56 22 09 74 01 00 00 00 05 40 00 80 E0 57 6B 03 V».t…..@…Wk.
0018F470: 00 00 00 86 00 00 00 00 98 CA 58 00 C1 01 00 00 ……….X…..
0018F480: 98 CA 58 00 28 F5 18 00 01 00 00 00 01 00 00 00 ..X.(………..
0018F490: 00 00 00 86 04 00 00 00 16 00 00 00 00 00 00 00 …………….
0018F4A0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 …………….
0018F4B0: 4E 29 0E 74 C0 F5 18 00 AE 2A 0E 74 D8 F4 18 00 N).t…..*.t….
0018F4C0: 14 58 6B 03 40 F8 18 00 E0 57 6B 03 00 00 00 00 .Xk.@….Wk…..
0018F4D0: 02 00 00 00 00 00 00 00 98 CA 58 00 28 F5 18 00 ……….X.(…
0018F4E0: 02 00 00 00 01 00 00 00 00 00 00 86 04 00 00 00 …………….
0018F4F0: 16 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …………….
0018F500: 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 …………….
0018F510: 00 00 00 00 16 00 00 00 00 00 00 00 01 00 00 00 …………….
0018F520: 00 00 00 00 05 40 00 80 90 06 00 00 1A 04 00 00 …..@……….
0018F530: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …………….
0018F540: 60 CD 78 03 90 06 00 00 1A 04 00 00 00 00 00 00 `.x………….
0018F550: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …………….
0018F560: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …………….
0018F570: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …………….
0018F580: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …………….
0018F590: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …………….
0018F5A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …………….
0018F5B0: 00 00 00 00 80 0F 00 00 00 00 00 00 C2 34 BB 9F ………….4..
0018F5C0: 30 F6 18 00 8E 38 0E 74 90 06 00 00 1A 04 00 00 0….8.t……..
0018F5D0: 16 00 00 00 01 00 00 00 2C 7E 02 00 00 00 00 00 ……..,~……
0018F5E0: 01 00 00 00 01 00 00 00 40 F8 18 00 00 01 00 00 ……..@…….
0018F5F0: 80 35 6B 03 08 F6 18 00 E0 57 6B 03 C0 C0 76 03 .5k……Wk…v.
0018F600: 3B 00 00 00 40 F8 18 00 01 00 00 00 01 00 00 00 ;…@………..
0018F610: 98 CA 58 00 90 06 00 00 1A 04 00 00 16 00 00 00 ..X………….
0018F620: 3C 00 00 00 00 00 00 00 00 00 00 00 32 37 BB 9F <………..27..
0018F630: 44 F6 18 00 6C 25 0E 74 40 F8 18 00 00 00 00 00 D…l%.t@…….
0018F640: 64 11 11 75 B8 F7 18 00 A3 CE 0D 74 40 F8 18 00 d..u…….t@…
0018F650: 8C F6 18 00 00 00 00 00 BA 36 BB 9F 80 35 6B 03 ………6…5k.
0018F660: 01 00 00 00 42 00 00 00 08 00 14 00 38 00 00 00 ….B…….8…
0018F670: 50 37 6B 03 01 00 01 00 D0 7F 59 00 04 00 00 00 P7k…….Y…..
0018F680: 40 F8 18 00 A0 EC 56 00 00 00 00 00 00 00 00 00 @…..V………
0018F690: 63 3A 5C 70 72 6F 67 72 61 6D 20 66 69 6C 65 73 c:program files
0018F6A0: 20 28 78 38 36 29 5C 77 61 72 63 72 61 66 74 20 (x86)warcraft
0018F6B0: 69 69 69 5C 77 61 72 33 2E 65 78 65 00 01 02 00 iiiwar3.exe….
0018F6C0: 1F 00 00 00 00 00 00 00 98 0A 02 00 00 00 00 00 …………….
0018F6D0: 5C F7 18 00 EB 08 52 77 38 00 00 00 08 00 14 00 …..Rw8…….
0018F6E0: 00 00 00 00 00 00 00 00 40 00 00 00 48 12 00 00 ……..@…H…
0018F6F0: F8 05 78 03 02 00 00 00 08 00 00 00 00 00 00 00 ..x………….
——————————————————————————
-
Home
-
Forums
-
The Site
-
Technical Support
‘This application has encountered a critical error:’….UGH!
-
Thread starter
EmeraldDark -
Start date
Oct 21, 2006
-
#1
EmeraldDark
Guest
This application has encountered a critical error:
FATAL ERROR!
Program c:program fileswarcraft iiiwar3.exe
Exception: 0xC0000005 (ACCES_VIOLATION) at 001B:01053F7D
The instruction at '0x01053F7D' referenced memory at '0x02142460'.
The memory could not be 'read'.
Press OK to terminate the application.This is ticking me off. Does anyone know how i can fix this?
-
#2
1. ignore it and hope it wont happen too often
2. use the opengl mode. to do this run wc3 with -opengl parameter. however this had a couple of side-effects — for example the textures usually mess up when i minimize the game.
-
#3
EmeraldDark
Guest
happens to me often as well…two solutions:
1. ignore it and hope it wont happen too often
2. use the opengl mode. to do this run wc3 with -opengl parameter. however this had a couple of side-effects — for example the textures usually mess up when i minimize the game.
The sad thing is i tried ignoring it.
and now everytime i open the game it happens.
Ill try out your idea. See if it works.
EDIT : worked longer than normal.but still crashed.
-
#4
-
#5
EmeraldDark
Guest
Are you doing anything specific when the game crashes and gives you this error message?
Nope, it just happens
This is really starting to piss me off. I havnt played a full game for about 1 year now without it crashing!!!
List of things i have tried
-reducing the game quality
-Turning off the sound in the game
-Adding different Parameters to the end of its extenstion
-Changed my sound quality in dxdiag
-Change my video quality in dxdiag
-Turned off external Chip Use
-Changing the movie folder name
-Taking the movie folder out of the war directery
I really dont know what the hell to do. Ive searched sites and everything. Nothing is working.
-
#6
-
#7
-
#8
Sry to bring this thread back because i dont want to start a new thread on the same problem.
My Story:
a few mths ago, my WC3 was running perfectly. But then my PC USB drive had a short circuit and we had to change the motherboard. So everything was lost and i install WC3 again. But when i play a campaign or standard game for only a few minutes, ths same Fatal Error pop up. It annoys me as well.
Quote>SFilip happens to me often as well…two solutions:
1. ignore it and hope it wont happen too often
2. use the opengl mode. to do this run wc3 with -opengl parameter. however this had a couple of side-effects — for example the textures usually mess up when i minimize the game.
Of course the 1st solution didnt work.
Could you explain the 2nd solution a bit more. Im sry but i dont quite understand what it means.
Thks in advance
-
#9
Shadowics
Guest
Explaination of his 2nd solution:
There are basically 2 different ways for a game to draw graphics on your computer screen, Direct3D and OpenGL. Most games and computers support both, and depending on your system, one may work better than the other. To tell Warcraft 3 to try using OpenGL instead, right-click on the shortcut you use to run Warcraft 3, select properties, find the Target: line in that dialog and add -opengl to the end. It should look like: «C:Warcraft IIIWAR3.EXE» -opengl
Then try running Warcraft 3.
-
#10
Damn it wasnt like this b4 i change my motherboard
Anyway does any of u know what does the error mean?
-
#11
Shadowics
Guest
The only real information we can get, without disassembling warcraft 3, is that it tried to access a location in memeory that either didn’t didn’t exist, or that it didn’t have permission to read. This really doesn’t tell us a lot, basically the equivalent of a segmentation fault if you’re familiar with C. It’s mostly likely a result of some minor issue in the graphics drawing engine, which is why different settings (most notably, opengl) and/or different hardware will affect when/if you crash.
It’s also possible that is a result of a problem with your RAM, but that’s unlikely.
-
#12
War3 (and most other Blizzard Games) are highly intensive Memory applications and problems with your memory show up big time. It is definitely worth looking into.
-
#13
Shadowics
Guest
Quite a bit of modern RAM can correct it’s own errors, and I personally have 10 year old sticks that still work perfectly (except they only hold 64 MB). Really, the only reason to suspect RAM is if you had just installed some new RAM and think you might have gotten one with a manufacturing error. It’s really far more likely that there’s an error on your hard drive that corrupted part of warcraft 3, before it even got to the RAM.
-
#14
It could most definitely be a Ram problem. Try some new Ram in that computer, make sure it is matched Ram, the same speed and the same kind. If you just added memory take the new memory out or take the old memory out but try to run with only one stick.War3 (and most other Blizzard Games) are highly intensive Memory applications and problems with your memory show up big time. It is definitely worth looking into.
Thks, i believe its my RAM problem. The error only occurs when i play Warcraft for a short period of time. It doesnt happen when i played other simplier game.
But I would like to know more about RAM. I know it is a place where u store data temporarily. If the PC is off, the data is lost.
So when u save yr data, they are stored into yr C drive or thumbdrive or whatever storage devices. Then my question is what happened to the data in the RAM? Are they emptyed since the data is saved?
Hmm… is any body gonna answer my above questions? I just want to ensure the source of the problem because the error is still occurring.
-
#15
When the power is on, it will store information… but when it is shut off all the memory is lost (there is no way to actually know what is stored in memory when the computer is turned back on.)
Hard drives actually ‘write’ into the physical disc when they store information. This is why hard drives have a limited life span, because they ruin physically.
-
#16
So when u save yr data, they are stored into yr C drive or thumbdrive or whatever storage devices. Then my question is what happened to the data in the RAM? Are they emptyed since the data is saved?(Assuming the PC is still on)New question
I would like to clarify this:
When i am playing Warcraft, what is the RAM doing?Thks in advance
-
#17
g1real
Guest
— When starting the game.
— When starting a map.
— When finishing a map.
That’s what I know for sure, it’s used in some other things too I think. Like:
— When battle.net starts
In map situations it basically loads all files of that map into your RAM, also including the models of all units, all buildings, the sounds, the music, the imported stuff and all. Most of the standard loading happens at the start of warcraft. But some of them happen at map load =P, but that’s just a few eh…
-
#18
-
#19
Question 1:
What is the situation here?
Question 2:
have you guys ever encounter the Blue Screen? Where it say Begin dumping of physical memory: xxx before?
THks in advance
-
#20
monte928
Guest
hi, i join this board just to help you but i see its been awile.
i had the exact same problem.
to fix it i did this.
1. delete the warcraft3 shortcut.
2. go to your warcraft3 folder and find war3.exe
3. make a shortcut to it and put it on your desktop.
it took care of the memory error for me.
hope it works.
forgot to mention..run your game directly thru the war3.exe shortcut.
-
Home
-
Forums
-
The Site
-
Technical Support
-
#1
Erm, I’m not really sure if this is the correct area to post this thread, but I’ll try asking it here.
Well, it seems that I’ve been having this problem for 5 days already, I’ve tried asking in the Blizzard Forums, Hive Chat and some other areas, but to not much avail.
However, some progress have still been made, before I’ve done anything, this was the error my Antivirus found that made Warcraft III unable to be run:
C:Program FilesWarcraft IIIBNUpdate.exe — Corrupted Executable File
C:Program FilesWarcraft IIIgame.dll — Corrupted Executable File
C:Program FilesWarcraft IIIStorm.dll — Corrupted Executable File
C:Program FilesWarcraft IIIwar3.exe — Corrupted Executable File
C:Program FilesWarcraft IIIworldedit.exe — Corrupted Executable File
Then, I tried to download and replace the corrupted files (Some .dlls and such) with those that I’ve found from Google, I’m not too sure if they’re from trusted sites, but here are the errors I’ve gotten after that:
1. When I tried running war.exe, it gives me the error «The ordinal 590 could not be located in the dynamic link library Storm.dll»
2. When I tried running worldedit.exe, it gives me the error «The ordinal 293 could not be located in the dynamic link library Storm.dll»
Right after that, I tried to replace those ‘failed’ .dll files with the ones that my friend uses on his thumbdrive (He doesn’t own a copy of Warcraft III) that works for him.
Well, I managed to see the screen go black (A sign that the game’s going to start) and a Warcraft III: Reign Of Chaos (I’m not sure why it isn’t The Frozen Throne) icon showing on the desktop bar, however, it quickly closed with a fatal error. Here’s the fatal error I’ve gotten from it:
This application has encountered a critical error:
FATAL ERROR!
C:Program FilesWarcraft IIIwar3.exe
Exception:0xC0000005 (ACESS_VIOLATION) at 001B:15033C10The instruction at ‘0x15033C10’ referenced memory at ‘0x0000002F’.
The memory could not be ‘read’.Press OK to terminate the application.
I really hope somebody would be willing to help me solve this problem, thank you so much.
-
#2
try reinstalling your wc3…
-
#3
Oh, I forgot to mention in the earlier post, sorry.
But uhm, I seem to have misplaced my CD, and my CD-Key went along with it — Lost.
I hope there’s some way somebody could help me out, I’m really sorry for the trouble…
-
#4
If you registered your copy with Battle.net you could redownload… ^_^
else, you need someone to give you those…
btw, its a nice AV you got there, this is the first time I’ve seen an AV being able to troubleshoot…
-
#5
Hehe… I’m quite happy though, I just found my lost disc (It was lost for about 5 years already) and I’ll let you know if it works.
-
#6
This could point towards a failing hard drive. If the drive becomes unreliabe, more and more read errors would occur which can ultimatle lead to a file being marked as curropted (as it was read incorrectly despite error checking).
I advise running a disk check (the one that comes with Windows OSs) just to make sure. It could even be something stupid like damaged sectors.
-
#7
This could point towards a failing hard drive. If the drive becomes unreliabe, more and more read errors would occur which can ultimatle lead to a file being marked as curropted (as it was read incorrectly despite error checking).
I advise running a disk check (the one that comes with Windows OSs) just to make sure. It could even be something stupid like damaged sectors.
Every computer related issue can be chalked up as a failed hard disk, eh? Seriously, every thread you post the same thing.
I’m willing to bet reinstalling the game will fix it.
-
#8
Yeh it might, but why would those files suddenly become «curropt» in the first place?
-
#9
Well, my brother took out my computer for cleaning, and when he placed it back, I found several corrupted files with the antivirus.
Anyways, it’s fixed now, thank you so much everyone for helping me for this week, I owe you one!
Hehe, you can close it now
-
#10
Yeh it might, but why would those files suddenly become «curropt» in the first place?
I don’t pretend to know, but I would only think it might be a hard drive issue if a) it sounded like one b) nothing else worked.