А также, кто знает англ, советую прочитать:
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 должна исчезнуть.
04.01.2023
589 Просмотры
решил поиграть в WoW Sirus вкл лаунчер не запускается так же как и NOLauncherStart и сам exe перекачал игру 3 раза тоже самое в код ошибке пишет это
This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal Exception
скачайте ЧИСТЫЙ клиент, без ничего лишнего и обновите его лаунчером
Addon Updater – программа для обновлений аддонов для игры World Of Warcraft.
Что умеет?
- Вы можете скачивать и удалять ненужные вам аддоны.
- В настройках программы можно включить автообновление.
- Запускать лаунчер игры.
- Удалять настройки аддонов.
- У каждого аддона есть описание.
захожу в игру чутка бегаю ,а потом вылетает из игры с этой ошибкой ..подскажите ,что делать?
Запустите лаунчер и выполните проверку файлов игры (кнопка в левом нижнем углу)
- Закройте лаунчер;
- Удалите папки лаунчера:
C:UsersИМЯПОЛЬЗОВАТЕЛЯAppDataLocalsirus-open-launcher-updater
C:UsersИМЯПОЛЬЗОВАТЕЛЯAppDataLocalProgramssirus-open-launcher
C:UsersИМЯПОЛЬЗОВАТЕЛЯAppDataRoamingSirus Launcher
Скачал установил, файлы которые нужно заменил, логин и пароль ввел, выбрал сервер и пишет: соединение установлено, потом через 20-30 секунд пишет: что соединение с сервером разорвано… перезапускал игру, перезагружал комп, всё так же…
Скачай полный клиент у них на сайте – и ничего не заменять – скачал и играешь.
Обычно ошибка Error #134 вызвана поврежденными или отсутствующими файлами. В некоторых случаях она возникает, если игра была установлена на диск с испорченными секторами на жестком диске или на компьютер с поврежденной/неподходящей оперативной памятью.
Способ первый: Запуск утилиты восстановления файлов игры Repair.exe.
Способ второй: Проверка оперативной памяти.
Проверка оперативной памяти вашего компьютера поможет обнаружить дефекты, которые могли вызвать ошибку. Для проверки оперативной памяти рекомендуется утилита Windows Memory Diagnostic, загрузить ее можно с сайта Microsoft
Способ третий: Обновление системных драйверов.
- Неисправности модулей памяти. Проверьте их программой «Memtest».
- Неисправности материнской платы. Замените ее или отнесите в сервис центр.
- Несовместимости планок между собой, материнской платой или видеокартой. На моем опыте были случаи, когда абсолютно рабочая видеокарта отказывалась работать с конкретной оперативной памятью, причем тоже рабочей. Это редкость, но все же
Как выясняется, одна из наиболее распространенных причин, которые могут вызвать этот код ошибки, — это то, что средство запуска игры (Battle.net) не имеет прав администратора. Если этот сценарий применим, вы сможете легко решить проблему, заставив запускать программу с правами администратора.
Загрузка…
Problem: World of Warcraft hang and the error message prompted showing Wow-64.exe application critical error due to access violation fatal exception. This error normally happens after Windows 10 update installed and caused unable to process temporary files or corrupted system files.
Solved: How do I fix Wow-64.exe Critical ERROR #132 (0x85100084) Fatal Exception ACCESS_VIOLATION?
The detail error message as below:
Wow-64
This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal Exception!
C: Porgram Files (x86 World of Warcraft Wow-64.exe
Exception: ACCESS_VIOLATION
The memory could not be “read”.
Press OK to terminate the application.
Follow below solution steps to resolve WoW access violation fatal exception error issue.
Content Summary
Solution 1: Delete the World of Warcraft Cache and Interface Folder
Solution 2: Execute World of Warcraft Scan and Repair Tool
Solution 3: Disable Antivirus
Solution 4: Update Graphics Card and Audio Drivers
Solution 5: Disable Xbox Game DVR
Solution 6: Disable Windows Game Bar
Solution 7: Disable Xbox Game Monitoring
Solution 8: Exclude the Game Executable from Data Execution Prevention (DEP)
Solution 9: Enable OpenGL Mode
Solution 10: Turn Off Windows Defender Firewall
Solution 11: Execute System File Checker (SFC)
Solution 12: Execute CHKDSK
Solution 13: Execute Windows Store App Troubleshooter
Solution 14: Execute Windows Memory Diagnostic
Solution 15: Uninstall and reinstall World of Warcraft
Reference
Solution 1: Delete the World of Warcraft Cache and Interface Folder
Step 1: Exit the game.
Step 2: Right-click on the game’s icon and choose Open file location option in the context menu.
Step 3: Locate the folder named Cache, Interface, and WTF.
Step 4: Delete both folders.
Step 5: The system will recreate those folders automatically when the game next launch.
Solution 2: Execute World of Warcraft Scan and Repair Tool
Step 1: Exit the game.
Step 2: Right-click on the game’s icon and choose Open file location option in the context menu.
Step 3: Locate the folder named WoW.exe or WoW-64.exe in 64-bits PCs.
Step 4: Double-click Battle.net launch app to open it.
Step 5: Go to the World of Warcraft panel and click on Options > Scan and Repair.
Scan and Repair option in War of Warcraft
Step 6: Click on Begin Scan. It will start to download the deleted cache and WoW.exe/WoW-64.exe.
Solution 3: Disable Antivirus
Many World of Warcraft players has fixed the Wow-64.exe application error by turning off antivirus protection because the antivirus software or services actively find and quarantine suspicious files and processes.
Step 1: Right-click on the antivirus icon on the taskbar and choose Disable.
Step 2: Start to the game again. If the game runs smoothly with no prompting the same error, then you can be certain that your antivirus program was the cause.
Step 3: Proceed to exclude the game from the virus scans by navigating to the Settings page and find the Exceptions setting.
Step 4: Click on Add and browse for the World of Warcraft executable file from its installation folder.
Remark: The locations of the settings for excluding applications vary in different antivirus software.
Solution 4: Update Graphics Card and Audio Drivers
Step 1: Press the Windows + “R keys to open the Run box.
Step 2: Type devmgmt.msc and click on the OK button.
Step 3: Expand the Display adapters.
Step 4: Right-click on your graphics card and choose the Update driver option from the context menu.
Step 5: Click on the Search automatically for the drivers or Search automatically for updated driver software option.
Click on the Search automatically for the drivers or Search automatically for updated driver software option.
Step 6: Windows will start to look for a newer version of the driver from the Internet. If available, you will be prompted about the same.
Step 7: If the newer version of the driver found, proceed with the installation.
Step 8: Restart your PC.
Step 9: Perform the same update driver process for Audio inputs and outputs and Sound, video, and game controllers.
Solution 5: Disable Xbox Game DVR
Step 1: Right-click on the Start button.
Step 2: Click on the gear icon located in the bottom left corner of the Window to open Settings.
Step 3: Click on Gaming.
Windows Gaming Settings
Step 4: Switch to Game DVR tab.
Step 5: Toggle off Record in the background while I’m playing a game and Record audio when I record a game from Background recording section.
Toggle off Record in the background while I’m playing a game and Record audio when I record a game from Background recording section.
Solution 6: Disable Windows Game Bar
Step 1: Right-click on the Start button.
Step 2: Click on the gear icon located in the bottom left corner of the Window to open Settings.
Step 3: Click on Gaming.
Windows Gaming Settings
Step 4: Switch to the Game bar tab.
Step 5: Toggle off Record game clips. Screenshots, and broadcast using Game Bar.
Toggle off Record game clips. Screenshots, and broadcast using Game Bar.
Solution 7: Disable Xbox Game Monitoring
Step 1: Press Windows key + R to open a Run box.
Step 2: Type regedit and press Enter to open up the Registry Editor. Click Yes to grant administrative privileges when prompted by the UAC (User Account Control).
Step 3: Navigate to the following location: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesxbgm
Step 4: Right-click on the Start REG_DWORD key at the right-side pane of the window, and click Modify.
Right-click on the Start REG_DWORD key at the right-side pane of the window, and click Modify.
Step 5: Type 4.
Modify Start DWORD (32-bit) Hexadecimal value to 4
Step 6: Click on the OK button.
Remark: If you want to enable back Xbox Game Monitoring again then repeat the steps, and change the value from 4 to 3.
Solution 8: Exclude the Game Executable from Data Execution Prevention (DEP)
Step 1: Open the Control Panel.
Step 2: Go to System and Security > System.
Step 3: Choose Advanced system settings option from the left column of the following window.
Advanced system settings
Step 4: Switch to the Advanced tab.
Step 5: Click on the Settings button under the Performance section.
Click on the Settings button under the Performance section.
Step 6: Switch to Data Execution Prevention tab.
Step 7: Check the radio button of Turn on DEP for all programs & services except those I select.
Check the radio button of Turn on DEP for all programs & services except those I select.
Step 8: Click the Add button.
Step 9: Browse to the WoW executable file location: C:Program Files (x86)World or WarcraftWow-64.exe
Step 10: Click on the Open button.
Solution 9: Enable OpenGL Mode
Step 1: Right-click on the World of Warcraft icon from the desktop screen and select Properties.
Step 2: Switch to the Shortcut tab.
Step 3: Add -OpenGL in the last of the existing path adjacent to Target:
C:Program FilesWorld of WarcraftLauncher.exe” -OpenGL
Step 4: Click on the Apply button and then the OK button.
Solution 10: Turn Off Windows Defender Firewall
Step 1: Press Windows + I key to open the Windows Settings.
Step 2: Choose Update & Security.
Step 3: Click on Windows Security from the left pane.
Step 4: Click on Firewall & network protection.
Firewall & network protection
Step 5: Click on Private network and toggle off Windows Defender Firewall section.
Toggle off Windows Defender Firewall for Private network and Public network
Step 6: Perform the same step for the Public network.
Solution 11: Execute System File Checker (SFC)
Run System File Checker (SFC) to replace potentially corrupted system files.
Step 1: Press Windows key once.
Step 2: Type cmd in the search box.
Step 3: Choose Run as administrator option to open an elevated command prompt. If you are prompted for an administrator password or for a confirmation, type the password, or select Allow.
Step 4: Type the following command below and press Enter for each line of command: sfc /scannow
Execute System File Checker (SFC) scan
Step 5: Wait until the message The operation completed successfully or Windows Resource Protection did not find any integrity violations show then close Command Prompt.
Step 6: Restart the computer.
Solution 12: Execute CHKDSK
Execute an Automatic CHKDSK scan with the ‘Scan for and attempt recovery of bad sectors’ option.
Step 1: Press Windows key once
Step 2: Type cmd in the search box.
Step 3: Choose Run as administrator to open an elevated command prompt. If the UAC prompts then click on Yes to proceed further.
Step 4: Type chkdsk /f and press Enter.
Solution 13: Execute Windows Store App Troubleshooter
Step 1: Press Windows + R to open up a Run dialogue box.
Step 2: Type control.exe /name Microsoft.Troubleshooting or ms-settings:troubleshoot, press Enter to open up the Troubleshooting tab in the Settings menu.
Step 3: go to Find and Fix other problems section > Windows Store Apps > Run the troubleshooter button.
Problem found in Windows Store Apps Troubleshooter
Step 4: Wait until the initial scan is complete, click Apply this fix button to apply the repair.
Step 5: Restart the computer.
Solution 14: Execute Windows Memory Diagnostic
Step 1: Press Windows key once
Step 2: Type cmd in the search box.
Step 3: Choose Run as administrator to open an elevated command prompt. If the UAC prompts then click on Yes to proceed further.
Step 4: Type mdsched and press Enter.
Step 5: Click on Restart now & check for problems to start the process.
Click on Restart now & check for problems to start the Windows Memory Diagnostic
Solution 15: Uninstall and reinstall World of Warcraft
Step 1: Press Window key to show the application list.
Step 2: Scroll down and locate World of Warcraft from the application list.
Step 3: Right-click on it and select Uninstall.
Step 4: Open Microsoft Store, type World of Warcraft in the Search Box, and then install on PC.
Reference
- Reddit > r/wow > Keep on getting “fatal error” crashes.
- Microsoft Community > ERROR #132 (0x85100084 Fatal exception! — 0x0007ff84ff8d431 referenced memory at 0x0000000000000018
- Microsoft Support > Get updates for apps and games in Microsoft Store
- Wow freakz error #132 fatal exception!
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………….
——————————————————————————
WAIT! READ ME FIRST: If you don’t read this all, okay. But, do me one favor, do you know if WoW WotLK 3.3.5a has any known conflicts with Windows 10’s 20H2 update? That is the only difference from a working machine I have and a non-working machine. Read on and see what’s up. Thanks!
I’m not normally a big forum user anymore, my stats will prove that but I have run out of resources so I bring my situation to you…
I recently bought a new ASUS laptop, it’s an all AMD machine, the G15 Advantage Edition. The laptop can run WoW and is currently running every other game I have installed on it — and everything else — without issue. However, here is the timeline:
— After updating the new machine with Windows Updates, driver updates, etc. The usual new computer stuff, I began downloading the games I wanted. I was able to download the BitTorrent of the 3.3.5a client from this site just fine and run it ONCE. It ran once, for 5 seconds and I logged back out.
— Days later when I went to open it again, I began seeing the below error every time.
— Since, I have downloaded the torrent repeatedly to no avail. I have got the 3.3.5a client from other sources as well, for no positive result. I have also done all of the standard Error 132 checks: Game DVR mode off, all Windows «Game» features are off, drivers are all updated, run as Admin, unchecked Read-Only, used Large Address Aware, cleaned my registry, made config changes, cleared my cache and all those sub folders, and more. I have literally done everything I have found to no result.No matter what I do, still the same results. I am asking for any and all help if you have it. This one is really something else.
The full error displayed:
The application has encountered a critical error:
ERROR #132 (0x85100084) Fatal Exception
Program: C:Program Files (x86)World of Warcraft WarmaneWow.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:008D2412
The instruction at «0x008D2412» referenced memory at «0x00000000»,
The memory could not be «read»,
Press OK to terminate the applicationAt first, the account on the new laptop was a Windows Live account. It has since been switched to a local Windows account and still, the issue is there. There are no mods or any advanced textures being run. This is just stock WoW WotLK 3.3.5a I am trying to run here.
What is more frustrating is that I had the Mac client working on my Macbook Pro, but removed it cause I got this laptop for gaming. My desktop has the client running just fine and has never has issue. I have replicated the setup with the new install off the torrent, I have even taken the install off the desktop and dropped it on the laptop to no change.
I have also referenced many of the posts I see referenced here on the forums about the error codes and such. I haven’t found an answer there and I saved LAA for last and still — it didn’t work. So, any tips on how you might beat this please let me know.