Error 138 wow - Исправление ошибок и поиск оптимальных решений проблем

#1 — Nov. 10, 2017, 7:37 p.m.

I keep getting a fatal exception every time I play

usually about 3-4 minutes in

This application has encountered a critical error:

ERROR #138 (0x8510008a) Fatal exception!

Program: D:World of WarcraftWow-64.exe
ProcessID: 9384
Exception: 0xC000001D (ILLEGAL_INSTRUCTION) at 00007ff6219adea2

tried with minimal startup,
no addons
updated gfx drivers

#3 — Nov. 11, 2017, 11:43 a.m.

Heya,

Please go through the steps outlined here. Make sure to go through the Advanced Steps as well, and see if that helps out.
______________________________________________________
Have a few seconds to spare? Let me know how I’m doing!
https://www.surveymonkey.com/r/Nenyasqi

#7 — Nov. 15, 2017, 11:03 a.m.

Heya,

It sounds like you have gone through a lot of troubleshooting already at this stage, so let’s dive right into the system files.

Please go through the steps listed here, and create both the MSInfo and DxDiag files. Post them on a page like Pastebin.com or through OneDrive once you have the files ready, and post the links here so we can have a look.
______________________________________________________
Have a few seconds to spare? Let me know how I’m doing!
https://www.surveymonkey.com/r/Nenyasqi

#9 — Nov. 15, 2017, 5:32 p.m.

Thank you for the heads up, happy to hear you sorted out the issue.
______________________________________________________
Have a few seconds to spare? Let me know how I’m doing!
https://www.surveymonkey.com/r/Nenyasqi

#13 — Nov. 30, 2017, 3:19 p.m.

Hey Omgkillkenny,

If this is happening on your account only at the moment (you mentioned testing this on your account, on nother computer), than please contact the support directly for further assistance. They will be able to test things out further, something that we unfortunately cannot do here.
______________________________________________________
Have a few seconds to spare? Let me know how I’m doing!
https://www.surveymonkey.com/r/Nenyasqi

#15 — Nov. 30, 2017, 3:59 p.m.

You can view the Minimum and Recommended System Requirements here.
______________________________________________________
Have a few seconds to spare? Let me know how I’m doing!
https://www.surveymonkey.com/r/Nenyasqi

#21 — Dec. 1, 2017, 2:19 p.m.

Hello again Omgkillkenny,

I don’t know how the system requirements are decided, that is not something that we have any say in ourselves. I would still like to have a look and see if we can figure out what caused this problem, but would still need the files I requested previously.
______________________________________________________
Have a few seconds to spare? Let me know how I’m doing!
https://www.surveymonkey.com/r/Nenyasqi

#25 — Dec. 3, 2017, 11:13 a.m.

Heya,

Please disable IOBit, and re-install World of Warcraft afterwards to test again. Please install it on a different drive if you can.
______________________________________________________
Have a few seconds to spare? Let me know how I’m doing!
https://www.surveymonkey.com/r/Nenyasqi

#31 — Dec. 4, 2017, 12:41 p.m.

Sad to hear this is still happening. There’s only a couple of things I spotted in your MSInfo that -might- help.. I could see your Secondary Logon isn’t set up right, and that you’ve still got Adobe updater in your startup programs, disable that and close it, see if that helps?

#33 — Dec. 4, 2017, 6:55 p.m.

Hello Omgkillkenny!

Can you please try and repair your OS? Some of the errors in your log indicate that there could be some issues with your system itself.

1) Run System File Checker
2) Run Memory Diagnostic

Radathryl
–––––––––
Feedback? Fill out this Survey.

#37 — Dec. 5, 2017, 12:48 p.m.

Ok for some reason I’m seeing more stuff on your startup programs, namely an extension for Chrome and Chrome itself, which wasn’t on your MSInfo from the 3rd.. very odd.
Can you please ensure you go through closing background programsand stop all services apart from the Microsoft ones?

It also looks like your graphics drivers somehow reverted to an earlier version. Please can you update them.

#40 — Dec. 5, 2017, 3:53 p.m.

Hello Omgkillkenny,

It is just an observation and small thing that stands out in your system configuration: Can you please reduce your USB-Devices to regular Keyboard (preferably PS/2, if available) and mouse only and test for a while?

Radathryl
–––––––––
Feedback? Fill out this Survey.

#42 — Dec. 6, 2017, 5:43 p.m.

Thank you for that Omgkillkenny. It’s good to have the different diagnostics between steps, as it helps us compare things.

The one thing that stands out now, is that your chipset drivers seem to be using the default and not the updated AMD drivers. I would suggest downloading the latest version of those and retesting once more afterwards.

If that still does not help out, I can only suggest to contact a local authorized computer technician to look into this further.
______________________________________________________
Have a few seconds to spare? Let me know how I’m doing!
https://www.surveymonkey.com/r/Nenyasqi

#44 — Dec. 7, 2017, 11:22 a.m.

Hey Shenglong,

Please do post your logs so we can have a look. Just as a reminder, go through the steps listed here, and create both the MSInfo and DxDiag files. Post them on a page like Pastebin.com or through OneDrive once you have the files ready, and post the links here.
______________________________________________________
Have a few seconds to spare? Let me know how I’m doing!
https://www.surveymonkey.com/r/Nenyasqi

Источник

MMO-Champion
»
Forum
»
World of Warcraft
»
General Discussions

anyone geting Error#138 (085100086) Fatal Condition Beta/WoW-64/.Exe process ID 5752

2014-07-18, 10:51 AM

#1

Stood in the Fire

anyone geting Error#138 (085100086) Fatal Condition Beta/WoW-64/.Exe process ID 5752

My toons just traped at hearting too my base so it showing me your guys no where to be found.. when i try to click on him to go in to wow u get Error#138 (085100086) Fatal Condition Beta/WoW-64/.Exe process ID 5752 client.cpp 5006 Bad Zone ID-1.

Any help would be great if someone knows how to fix that part be great thank ya for helping
2014-07-18, 03:29 PM

#2

Mechagnome

Error 138?
Sounds like Francis needs to make a Youtube video about this.

In all seriousness, Fatal Condition means a corrupt file on your end. You’ll need to reinstall the client I thinks.
Try deleting Cache, Data, and WTF folders first and see what happens.
2014-07-20, 03:20 PM

#3

Keyboard Turner

I have the same problem only when i click to log in on my hunter 94lvl i got black screen and this error:
Error#134 (085100086) Fatal Condition Beta/WoW-64/.Exe process ID 1320 client.cpp 5006 Bad Zone ID-1.
When i log on other toons there is no error only on this one.

Did u wheel fix that and how teelll me i wanna start con lvl my hunter?

Thanks.
2014-07-20, 03:42 PM

#4

Keyboard Turner

There is a blue post about this error from one of the QA’s — us.battle.net/wow/en/forum/topic/13482148180#13
2014-07-20, 04:00 PM

#5

Brewmaster

I think you mean #134 not #138

and yes as posted at post #4 it’s on the radar :

Regarding the Bad Zone ID -1 error :

* It is on Blizzard bug radar to fix
* For some unknown reason the game thinks you’re in an invalid zone map [eg EK map 0 , Kalimdor map 1]
* Crash is because the game is reporting you in Map -1 …. which should be impossible
* They’ll try to rescue toons but for now use other toons
* Minusworld analogy was used.

http://us.battle.net/wow/en/forum/to…8180?page=1#13
2014-07-20, 09:48 PM

#6

Stood in the Fire

Originally Posted by wheelmandan

My toons just traped at hearting too my base so it showing me your guys no where to be found.. when i try to click on him to go in to wow u get Error#138 (085100086) Fatal Condition Beta/WoW-64/.Exe process ID 5752 client.cpp 5006 Bad Zone ID-1.

Any help would be great if someone knows how to fix that part be great thank ya for helping

yes i can’t get my toon back he lost for ever in heartstoneing home i’ll never see him sad face.— — — Updated — — —

yea i have that

— — — Updated — — —

thank ya for the help yes its a sad day i’ve lost wheelhammer the true wheelhammer he’s lost in space….. he could’t make it out of the star gate.
2014-07-20, 09:53 PM

#7

The Lightbringer

Originally Posted by NickCageFanatic

In all seriousness, Fatal Condition means a corrupt file on your end. You’ll need to reinstall the client I thinks.
Try deleting Cache, Data, and WTF folders first and see what happens.

Not necessarily, like Blu posted thinks you’re on a world that simply doesn’t exist and because of that the client crashes. Had the same issue on premade 90 Monk but simply deleted it since I noticed the character copy at character selection and used my live one.

3DS Friend Code: 1891-2236-0134
2014-07-21, 06:14 AM

#8

Brewmaster

Originally Posted by Dedweight

Not necessarily, like Blu posted thinks you’re on a world that simply doesn’t exist and because of that the client crashes. Had the same issue on premade 90 Monk but simply deleted it since I noticed the character copy at character selection and used my live one.

Actually Nick’s sort of 1/2 correct there.

The #134 error can occur because of corrupt data. It can also be caused by bugs. The information contained in the error report needs to be carefully looked at before looking into a solution.

At the time of Nick’s post he may not of seen that post from Zorbix on the US forums. Zorbix made that post on the Saturday morning. So it may of been lost in the flood of ZOMG WAI MA BETA NO GO posts that they would of had on the forums on Saturday morning.

EDIT : Actually checking timestamps looks like NickCageFanatic had posted before the post from Zorbix existed.
2014-07-22, 11:22 PM

#9

Keyboard Turner

They fixed,now try to log.
2014-07-23, 08:55 AM

#10

Brewmaster

Sort of.

They put in a band aid fix of moving affected toons to their hearthstone locations.

The root cause has yet to be find and you can still be trapped by it.
2014-07-24, 09:34 AM

#11

Brewmaster

Another set of updates :

http://us.battle.net/wow/en/forum/to…180?page=8#160

Originally Posted by Blizzard Entertainment

Unfortunately in this case, none of those options will result in a faster resolution. We don’t have the ability to fix individual players, as our Customer Support team doesn’t have access to the same tools on beta realms that they have for live, retail realms. With that being the case, knowing which specific characters are affected doesn’t allows us to resolve it any quicker.

We’re able to see all the client crash reports you send in when attempting to log onto one of the affected characters, which should give us enough insight into the issue for now.

http://us.battle.net/wow/en/forum/to…180?page=9#175

Originally Posted by Blizzard Entertainment

A bulk move would be what we did before, and there’s a likely chance we’ll have to do it again. Don’t have exact timetables for that but we’re monitoring the incoming crash reports closely.

In other news, our next build *might* have a fix for this issue — no promises, but we’re making progress.

http://us.battle.net/wow/en/forum/to…80?page=10#184

Originally Posted by Blizzard Entertainment

Okay so we did some magic; pushed some code changes and did another temp fix to move broken characters back to your bind point.

If you’re still broken, let me know what you’re seeing.

MMO-Champion
»
Forum
»
World of Warcraft
»
General Discussions

anyone geting Error#138 (085100086) Fatal Condition Beta/WoW-64/.Exe process ID 5752

Posting Permissions

You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
[VIDEO] code is On
HTML code is Off

Источник

Обновлено: 08.02.2023

Код 138 представляет собой ошибку соединения, которая появляется на экране при попытке входа в игру. Если вы являетесь одним из пользователей, которые в прошлом сталкивались с ошибкой Valorant error code 138. И если вы не смогли решить проблему, то мы поможем вам понять, как можете фиксить ее самостоятельно.

Исправление ошибка 138 в Valorant

1. Удалить Riot Vanguard

2. Конфигурация Bcdedit

Если вышеописанный шаг не решит проблему, попробуйте это решение.

Теперь в командной строке необходимо ввести следующие коды:

bcdedit.exe /set nx OptIn

bcdedit.exe /set testigning off

bcdedit.exe /set nointegritychecks off

Затем вам нужно перезагрузить систему, и код ошибки, скорее всего, исчезнет. Однако, если проблема все равно сохранится, вы можете попробовать выполнить следующий шаг.

3. Изменить совместимость с Windows

4. Изменения в Приоритете процесса VGC

Если ошибка Valorant 138 продолжает поражать систему, вы можете попробовать этот метод.

Stood in the Fire Join Date Feb 2010 Posts 436

Any help would be great if someone knows how to fix that part be great thank ya for helping

Mechagnome Join Date Aug 2012 Location USA!! Posts 676

Error 138?
Sounds like Francis needs to make a Youtube video about this.

In all seriousness, Fatal Condition means a corrupt file on your end. You’ll need to reinstall the client I thinks.
Try deleting Cache, Data, and WTF folders first and see what happens.

Keyboard Turner Join Date Aug 2013 Posts 6

Did u wheel fix that and how teelll me i wanna start con lvl my hunter?

Keyboard Turner Join Date Nov 2013 Posts 7

Brewmaster Join Date Dec 2007 Posts 1,313

Regarding the Bad Zone ID -1 error :

* It is on Blizzard bug radar to fix
* For some unknown reason the game thinks you’re in an invalid zone map [eg EK map 0 , Kalimdor map 1]
* Crash is because the game is reporting you in Map -1 . which should be impossible
* They’ll try to rescue toons but for now use other toons
* Minusworld analogy was used.

Stood in the Fire Join Date Feb 2010 Posts 436
Originally Posted by wheelmandan

Any help would be great if someone knows how to fix that part be great thank ya for helping

yes i can’t get my toon back he lost for ever in heartstoneing home i’ll never see him sad face.

yea i have that

thank ya for the help yes its a sad day i’ve lost wheelhammer the true wheelhammer he’s lost in space. he could’t make it out of the star gate.

The Lightbringer Join Date Mar 2009 Posts 3,613
Originally Posted by NickCageFanatic
In all seriousness, Fatal Condition means a corrupt file on your end. You’ll need to reinstall the client I thinks.
Try deleting Cache, Data, and WTF folders first and see what happens.
Not necessarily, like Blu posted thinks you’re on a world that simply doesn’t exist and because of that the client crashes. Had the same issue on premade 90 Monk but simply deleted it since I noticed the character copy at character selection and used my live one.

Brewmaster Join Date Dec 2007 Posts 1,313
Originally Posted by Dedweight
Not necessarily, like Blu posted thinks you’re on a world that simply doesn’t exist and because of that the client crashes. Had the same issue on premade 90 Monk but simply deleted it since I noticed the character copy at character selection and used my live one.

Actually Nick’s sort of 1/2 correct there.

At the time of Nick’s post he may not of seen that post from Zorbix on the US forums. Zorbix made that post on the Saturday morning. So it may of been lost in the flood of ZOMG WAI MA BETA NO GO posts that they would of had on the forums on Saturday morning.

EDIT : Actually checking timestamps looks like NickCageFanatic had posted before the post from Zorbix existed.

I have been checking year old forums all day today and will continue to do so until the problem is fixed, or until I have run out of all possible options to fix this. (Unfortunately, I ran out fast as my problem appears to be unique to my situation.)

Any external help would be greatly, greatly appreciated. I will do whatever it takes in my power to be able to play pre-patch, even if it means dual-booting into the operating system mess of privacy called windows ten. I have a Ryzen 5 2600, and an RX 570 w/ eight gigs of ram.

решил поиграть в WoW Sirus вкл лаунчер не запускается так же как и NOLauncherStart и сам exe перекачал игру 3 раза тоже самое в код ошибке пишет это

This application has encountered a critical error:

The instruction at «0x00000000» referenced memory at «0x00000000».
The memory could not be «written».

Читайте также:

Fable как убрать шрамы

Supermicro bmc driver ошибка

Как поменять пол оператора warframe

Far cry 5 как включить вид от 3 лица

Xcom 2 как включить русский язык

Источник

How do I fix WoW errors?-Windows error #132

WoW error,How do I fix WoW errors?,Why do I get WoW error?,How do I fix WOW51900319?,What does WoW code WOW51900319 mean?,WoW error 132 memory could not be read, WOW error 133,WoW error 138,WoW error 132 0x851,WoW error 51900319,WoW error 132 reddit,0x85100084,WoW classic tbc error 132,WoW error 132 fatal exception reddit,Warmane Wow error,Windows error #132

In this guide, you will find all the helpful insights necessary to repair this WoW Error #132., & 134

Ways to repair a WoW Error #132 and #134

There square measure some ways within which you’ll fix this drawback. each resolution during this guide is an efficient methodology to fixing this drawback.

Try all the solutions in serial order to induce the most effective results.

Solution 1: putting in the most recent Patch

The game developers keep it up cathartic new patch files to update your current gameplay expertise and fix errors within.

Sometimes, not change these patch files will cause errors like #132.& #134

Therefore, check the official game application, Battle.net, to visualize if there square measure any unfinished patch updates. Follow the straightforward steps below to put in the most recent game patch files.

☑️Launch the Blizzard Battle.net application on your pc

☑️On the left facet of the applying, find and click on on the planet of Warcraft icon

☑️Now click on the choices button settled right below the title

☑️Click on Patch Notes to visualize if there square measure any unfinished updates

☑️If there square measure, simply click on the patch file to put in it on your pc

☑️After change, attempt launching the sport once more

If this solves the matter, the game can run without any issues. However, if your game is up thus far and you’re still facing the error message, then attempt succeeding resolution.

Solution 2: Run Repair Tool to repair the difficulty

The Blizzard Battle.net application comes with a repair tool that may fix the corrupted and broken game files on your pc.

Therefore, exploitation this repair tool may fix the WoW gameplay error.

Follow the straightforward steps below to run the Battle.net repair tool:

☑️Launch the Blizzard Battle.net application on your Windows ten pc

☑️On the left panel of the applying, find and click on on the planet of Warcraft icon

☑️Now click on the choices button settled right below the title

☑️Click on the Scan and Repair possibility from the drop-down

Finally, click on Begin Scan so follow the on-screen directions to with success scan and repair the sport files

The process might take a short time, therefore hold back and expect it to finish. once the method ends, attempt launching the sport once more.

This should fix the Error #132, & #134however if the error still shows up, attempt succeeding resolution.

Solution 3: Run System File Checker

The annoying game error may be the results of corrupted and broken system files on your pc.

To run Windows System File Checker, follow the directions below:

☑️Go to the search bar close to the beginning menu

☑️In the dialogue box, kind command, so whereas holding Ctrl + Shift, press Enter to launch the prompt with administrator access

☑️Now, within the prompt, kind sfc/scannow so press Enter

☑️Wait for the method to finish; this might take your time

☑️Once the method completes, shut the prompt and every one different open applications so restart your pc

Once the pc starts once more, attempt launching World of Warcraft once more. If the matter is solved , then the sport can run with none interruptions.

However, if the matter still exists or if you are looking for an alternate methodology, then follow succeeding resolution.

Solution 4: Reset the program (user interface)

This resolution is usually recommended by Blizzard recreation itself.

Follow the straightforward directions below to try and do so:

☑️If the sport application is running or is within the background, then check that to properly shut and exit it

☑️If you’re exploitation any add-on managers, like Curse, Pawn, WIM, etc., then check that to uninstall them 1st

☑️Now launch the Blizzard Battle.net application on your pc

☑️On the left panel of the applying, find and click on on the World of Warcraft icon

☑️Click on the choices button settled right below the title

☑️Click on Show in mortal from the pop-up list to open the folder wherever all of your Battle.net games square measure put in

☑️Double-click on the planet of Warcraft folder to open it

☑️In the folder, find the folders named Cache, Interface, and WTF

☑️Right-click on these folders one by one and rename them to Cache Old, Interface Old, and WTF Old severally

☑️Now run the sport and therefore the game can recreate these folders

If the error is mounted, then the sport can run swimmingly, however all of your program changes are gone.

Conclusion: WoW Error #132 & 134

It is not a significant issue, however has to be mounted so as for the sport to be ready to be compete once more.

Sometimes, simply restarting the computer and game will fix this error.

In different cases, you’ll use the Blizzard Battle.net repair tool to scan and repair the corrupted and broken game files among your pc.

However, if the error message is shown thanks to faults in system files, then exploitation the Windows System File Checker to repair these faults may fix the matter.

As a final resort, if nothing is functioning for you, then resetting the program of the planet of Warcraft game ought to for certain solve the matter once and for all.

Источник

ILLYRIA

Обама за международное право… Проститутки за девственность…

Игрок
80 Cообщений
07-Апрель 12

Отправлено 04 Март 2013 — 09:03

При игре в вов с завидным постоянством вылетает така ошибка ERROR #132(ox85100084) Fatal Exception блал бла бла
Дрова менял, кэш чистил, аддоны отрубал.Прошу умных дядинек и тётинек помочь в сложившейся ситуации. Жду РЕАЛЬНО хороших советов а не каках от местных выскочек)

Наверх

Начать играть на Isengard?

Присоединяйтесь к нашему сообществу!

Играйте на самом работоспособном и стабильном русскоязычном WoW сервере без доната игровых ценностей!

Spiritson

Эбусь в глаза.

Игрок
264 Cообщений
07-Июль 10

Отправлено 04 Март 2013 — 09:12

Наверх

kingd

Игрок
6 Cообщений
31-Январь 12

Отправлено 04 Март 2013 — 09:18

Ошибка ERROR #132 (0x85100084) Fatal Exception может быть вызвана множеством причин, для ее исправления попробуйте следующее:

1. Удаление всех временных файлов в папке Interface
Откройте папку с установленным WOW, по умолчанию C:Program FilesWorld ofWarcraft . Удалить или переименовать папку Interface, затем удалить все файлы в папках Cache и WTF. Файлы в данных папках будут автоматически созданы при повторном запуске игры.
2. Обновить драйвера
Обновить драйвера видео, материнской, звуковой и сетевой платы.
3. Сделать тест оперативной памяти
Запустить тест оперативной памяти от Microsoft ( Windows Memory Diagnostic ). Если при сканировании обнаружатся ошибки, заменить неисправные устройства или свяжитесь с производителем.
4. Запуск игры в режиме OpenGL, без звука в оконном режиме
Откройте папку с установленным WOW, в папке WTF есть файл Config.wtf. Измените в нем следующее
OpenGL: SET gxAPI «OpenGL»
SET Sound_EnableAllSound «0»
SET gxWindow «1»
Если при включении режима OpenGL, ошибка ERROR #132 (0x85100084) Fatal Exception пропала, то видимо это связано с вашей видео картой.
Если ошибка исчезла после отключения звука, то попробуйте сделать следующие пункты на этой странице
Если игра запустилась в оконном режиме, скорее всего игре не хватает ресурсов компьютера.
Попробуйте закрыть в диспетчере задач не нужные в данный момент программы.
5. Перегрев ПК.
Обратите внимание на температуру процессора, чипсета, видео карты.
6. Отключите звуковую плату

после прочтение выше приведенного текста лучше открыть гуг и посмотреть самаму о своей ошибке!!!!!!!!!!!!!!!!!!!!! :rtfm:

Наверх

Vivi Ornitier

Марина

Игрок
4 001 Cообщений
18-Январь 11

Отправлено 04 Март 2013 — 09:58

Цифробот нифиговую ссылку дал мне
http://lmgtfy.com/?q…#132(ox85100084)+Fatal+Exception

При игре в вов с завидным постоянством вылетает така ошибка ERROR #132(ox85100084) Fatal Exception блал бла бла
Дрова менял, кэш чистил, аддоны отрубал.Прошу умных дядинек и тётинек помочь в сложившейся ситуации. Жду РЕАЛЬНО хороших советов а не каках от местных выскочек)

Наверх

tumbablo

Игрок
98 Cообщений
14-Апрель 12

Отправлено 04 Март 2013 — 10:13

у меня в Одно время тоже эта ошибка вылетала,Удалил папки WTF и Chache

Наверх

kal

Игрок
31 Cообщений
25-Август 10

Отправлено 04 Март 2013 — 10:39

клиент переустанови, мне лично всегда помогало

Наверх

De Vett

Игрок
509 Cообщений
09-Июль 10

Отправлено 04 Март 2013 — 10:59

Я когда поставил все настройки по максимуму (включая дирек 10, или 11), тоже такая фигня была. Удаление тех папок не помогло, я решил убавить настройки (графики), и всё стало ок. Возможно, у клиента проблемы с дх 10/11.
И, да, клиент катовский.
Это относится к 4.3.4. С какой версией у тебя проблемы — ты не указал.

Наверх

InMoonWeTrust

Игрок
397 Cообщений
24-Июль 10

Отправлено 04 Март 2013 — 11:59

132 — насколько я помню ошибка MPQ файлов ? поправьте ,если ошибаюсь. Помогает переустановка 100%

Наверх

thomerthu

Игрок
17 Cообщений
01-Май 09

Отправлено 04 Март 2013 — 12:54

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

http://img197.imageshack.us/img197/7761/1353885947a6.png

Наверх

bydogs

Всё ещё нет.

Игрок
1 120 Cообщений
16-Апрель 09

Отправлено 04 Март 2013 — 12:55

А кап авойданса спасет?

… и случится нечто чудовищное. Чебурашки захватят детский сад. (с)

Буква «ч» залипает на клавиатуре, давлю, как могу!

Наверх

thomerthu

Игрок
17 Cообщений
01-Май 09

Отправлено 04 Март 2013 — 13:03

от болезней авойданс не спасает, к сожалению. а без точного диагноза вам и доктор ничего не скажет.

http://img197.imageshack.us/img197/7761/1353885947a6.png

Наверх

ILLYRIA

Обама за международное право… Проститутки за девственность…

Игрок
80 Cообщений
07-Апрель 12

Отправлено 04 Март 2013 — 16:19

Цифробот нифиговую ссылку дал мне
http://lmgtfy.com/?q…#132(ox85100084)+Fatal+Exception

блоо а вот и одна из выскочек) молорик выделся и в этой теме, хлопаю в ладоши. эмм ты зарубки часом на столе не ставишь?

а так всем спс, сегодня вечером примусь штурмовать данную проблему

Я когда поставил все настройки по максимуму (включая дирек 10, или 11), тоже такая фигня была. Удаление тех папок не помогло, я решил убавить настройки (графики), и всё стало ок. Возможно, у клиента проблемы с дх 10/11.
И, да, клиент катовский.
Это относится к 4.3.4. С какой версией у тебя проблемы — ты не указал.

3.3.5 скачал тут же на изи с прошлой проблем небыло

Наверх

Spiritson

Эбусь в глаза.

Игрок
264 Cообщений
07-Июль 10

Отправлено 04 Март 2013 — 20:35

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

внезапно, из за единичной траблы надо вливать фиксы на серв? no way

Наверх

LCT

Launcelot из Братства Стали

Игрок
1 173 Cообщений
23-Февраль 13

Отправлено 04 Март 2013 — 22:03

А кап авойданса спасет?

:rofl:

а реально привыкаешь, у нас если рейд то рейд: «ты иди на…, у тебя дпс как у хлебушка, а ты вообще му…» © Неизвестный паладин

Ваш последний голос 24 Март 2013 — 05:04, вы не голосовали за сервер уже более суток.

Наверх

ILLYRIA

Обама за международное право… Проститутки за девственность…

Игрок
80 Cообщений
07-Апрель 12

Отправлено 04 Март 2013 — 22:15

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

старый клиент воткнул всё ок стало

Наверх

LCT

Launcelot из Братства Стали

Игрок
1 173 Cообщений
23-Февраль 13

Отправлено 04 Март 2013 — 22:20

старый клиент воткнул всё ок стало

Ты зря с ним споришь, сейчас тебе на 3-ёх страницах напишут, что на самом деле у тебя всё не ок и ты не прав.

Ваш последний голос 24 Март 2013 — 05:04, вы не голосовали за сервер уже более суток.

Наверх

ILLYRIA

Обама за международное право… Проститутки за девственность…

Игрок
80 Cообщений
07-Апрель 12

Отправлено 04 Март 2013 — 22:23

не так то он прав на офах такое встречается частенько

в гугле много слез нашел типов от туда про эту же ошибку

Наверх

0x0590A03

Игрок
6 597 Cообщений
22-Июль 10

Отправлено 04 Март 2013 — 22:42

не так то он прав на офах такое встречается частенько

в гугле много слез нашел типов от туда про эту же ошибку

А теперь посмотри сколько играет людей на офе и сколько это примерно сотых процента из всех.

Наверх

Crash Override

Игрок
43 Cообщений
04-Июнь 11

Отправлено 04 Март 2013 — 22:53

для начала, чтоб дрова не трогать, обнови DirectX. Потом отпишись

Наверх

0x0590A03

Игрок
6 597 Cообщений
22-Июль 10

Отправлено 04 Март 2013 — 22:54

Слушать алкоголика, себе дороже.

Наверх

Источник

anyone geting Error#138 (085100086) Fatal Condition Beta/WoW-64/.Exe process ID 5752

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://www.mmo-champion.com/images/buttons/collapse_40b.png" alt /> Posting Permissions

Исправление ошибка 138 в Valorant

1. Удалить Riot Vanguard

2. Конфигурация Bcdedit

3. Изменить совместимость с Windows

4. Изменения в Приоритете процесса VGC

How do I fix WoW errors?-Windows error #132

Ways to repair a WoW Error #132 and #134

Conclusion: WoW Error #132 & 134

Posting Permissions