Ошибка wow 123

World of Warcraft Forums

Loading

World of Warcraft Forums

Loading

WoW Crashing to desktop with ERROR #123 and ERROR #132

Hello everyone, I have been having an issue with WoW encountering fatal errors that crash to the desktop. The error is:

ERROR #132 (0x85100084) Fatal exception!The instruction at “0x00007ff6a355a0d7” referenced memory at “0x000000000010024c”.The memory could not be “read”.

This error has occurred every day since I started to play WoW again on the Shadowlands launch… sort of.

When I went poking in the WoW Error log folder, I found back in February 2020 that my game crashed with:

ERROR #123 (0x8510007b) This memory block has been corrupted by an out-of-bounds memory write.

Memory corrupted – delete -1

I took a break from WoW around this time, and forgot this happened. At the time maybe I assumed it was a one-time thing, or perhaps it just coincided with when I took my break. I have not gotten ERROR #123 since I started playing again, but ERROR #132 keeps showing up.

I have been lurking on the WoW tech support forums for the past couple weeks, as well as searching through old ERROR #132 posts other players have made within the past year or so. I have tried a handful of the solutions recommended. To list so far:

  1. Uninstall Addons: I completely removed any addons from the WoW folder, and then I renamed my Interface, Cache, and WTF folders to -Old.

  2. Turn off all game overlays: I have made sure that Discord, Nvidia, Windows Game Bar, and Overwolf overlays are all turned off. I cannot find any other programs on my system that use an overlay. This solution was suggested multiple times by Blue’s in the tech support forum.

  3. Switch from DirectX12 to DirectX11, turn off MSAA: These were various suggestions I came across in my search, and they didn’t help.

  4. Fresh install of WoW

  5. Run SFC Scan and DISM many times, a pass of memtest86, multiple tests with the Windows Memory Diagnostic tool, and a CHKDSK: Some hardware testing that did not turn up any errors or anomalies. Every test I’ve run so far has found nothing wrong. I have also tried reseating the RAM in my computer.

  6. Reinstall my graphics driver, and attempting to uninstall Nahimic audio drivers: People have mentioned audio .dll from Nahimic could potentially be causing issues or crashes. I have tried to uninstall Nahimic, but it appears that while I can uninstall the Nahimic App, my MOBO itself has Nahimic built into its whole audio package. So I can’t really get rid of it, as far as I know.

None of these solved the problem, and my game still crashes with ERROR #132. There doesn’t seem to be a pattern as to when the crash occurs; I’ve had it happen while doing a variety of in-game events, and it has happened from any time within 10 minutes of playing the game, to up to 4 hours.

Finally, I would like to note that no other game, at least from what I can remember, on my system has crashed. It seems like WoW is the only one with this issue (or maybe the only one that runs into a computer-issue that other games have somehow avoided).

I’ve copied the error logs into pastebin if anyone wants to have a look at them:

https://pastebin.com/J4p24m4M (First crash ever, and the only crash that is ERROR #123)

https://pastebin.com/6cYZJ9Be (Crash with ERROR #132, addons are installed here)

https://pastebin.com/uvhVeecV (ERROR #132 with NO ADDONS INSTALLED)

ANY suggestions as to what I might be able to do further would be greatly appreciated.

Приветствуем вас на форуме проекта WoW Circle. Если вы читаете это, значит не зарегистрировались у нас. Для того, чтобы получить доступ к расширенным возможностям нашего форума нажмите сюда и пройди регистрацию, которая не займет у вас много времени. После регистрации будут доступны новые, более расширенные, возможности.

Ошибка #132

Ошибка 132 — общая ошибка, которая может быть вызвана:

  • Наличием устаревших обновлений
  • Поврежденными файлами игры
  • Несовместимостью драйверов
  • Неполадками в работе жесткого диска

Как с ней бороться:

I. Сперва нужно сбросить настройки интерфейса

II. Выполнить проверку диска и его дефрагментацию

III. Выполнить сканирование компьютера с помощью антивируса

IV. Обновить драйвера (3 и 4 пункт темы)

V. Переустановить игру с помощью торрента или лаунчера

  • Для Windows XP

Перед деинсталяцией игры рекомендуется удалить файлы из данной темы и загрузить их заново с помощью лаунчера:

  1. Закрыть лаунчер в трее
    1543507850528.png
  2. Удалить упомянутые по ссылке выше файлы
  3. Запустить лаунчер с правами администратора

Если ни один из способов выше не помог, значит ошибка в содержится в конкретном файле клиента игры, которые мы не затрагивали, или их совокупности. Для этого нужно полностью удалить игру и загрузить её заново.

Понравилась статья? Поделить с друзьями:

Не пропустите эти материалы по теме:

  • Яндекс еда ошибка привязки карты
  • Ошибка wot systemerror text
  • Ошибка wot game resource path does not exist
  • Ошибка wot application has stopped working
  • Ошибка wot 8007

  • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии