IPB

Welcome Guest ( Log In | Register )

> WoW Errors: Common fixes!
Brink
post Aug 2 2009, 05:37 PM
Post #1


Advanced Member
***

Group: Members
Posts: 173
Joined: 1-August 09
From: FFA Arena
Member No.: 1,022



1. Introduction

The first step when facing any error or crash is to close down WoW and remove the WTF, WDB and Interface folders from the World of Warcraft game directory. These folders contain temporary data and frequently altered files that may have become corrupted. This will also remove any custom UI's that may contribute to the problem as well.

You can move these folders to the desktop or another directory if you wish to retain the data, however for now please start WoW without those folders present. Also do not use any third party programs to start WoW; often some custom UI's will place a shortcut for you to start WoW from, please use the (Launcher.exe) in the World of Warcraft directory.

# The information below is a compilation of various crashes and errors that users may experience while playing World of Warcraft. The examples used may not be identical to an error that may be experienced, but if the information looks similar, the steps listed may apply. Keep in mind that even though your error message may match closely to what is listed below, the actual cause and ultimate resolution may be quite different from what is contained here.


1. Introduction
2. Error 121
3. Error 124
4. Error 131
5. Error 132
6. Error 134


2. Error 121

If you've gotten an error 121 recently, please check your message to see if it matches the underlined part:

World of WarCraft (build 6080)

This application has encountered a critical error:

ERROR #121 (0x85100079) Version Mismatch
Program: C:\Users\Public\Games\World of Warcraft\WoW.exe

DBFilesClient\Startup_Strings.dbc has wrong number of columns (found 19, expected 11)



If it does, it means that you've downgraded from a major 3.0 patch back to 2.0 using the Burning Crusade install disc or a very old download. This happens most often if you install World of Warcraft using the InstallWoW.exe file and then installing an old Burning Crusade on top of that. To fix this, uninstall the game and use InstallWoW.exe to start the installation, but pick Burning Crusade from the dropdown menu instead of World of Warcraft.


If it does not match the bold part, this errors root cause is extensive corruption in the World of Warcraft files. The corruption is usually caused by one of two things; missing important data files or mixed patches installed. A system restore will sometimes trigger this error by mixing the patch files in the program. I.E. some files have been reverted back to a previous version while some files are patched to the most recent version.


Example of the Error 121 message:


ERROR #121 (0x85100079) Version Mismatch
Program: C:\Program Files\World of Warcraft\WoW.exe

DBFilesClient\VideoHardware.dbc has wrong number of columns (found 19, expected 22)





The first approach to resolving this error should always be the repair tool. The repair tool is located in the World of Warcraft folder called repair.exe.


3. Error 124

The "Error #124 - Memory Invalid Block" error message has been known to be caused by memory related hardware such as your hard drive, RAM, and/or motherboard. Please follow all the steps below as they may help resolve or identify the error you are experiencing.

# Checking the hard drive

This error may be caused by the hard drive itself rather than the files stored there. Please follow these steps as to perform general maintenance for the hard drive. The first step is to perform a scandisk of the hard drive to look for errors on the hard drive itself that may result in data becoming corrupt.

ScanDisk
(Windows 98/Me)
1. Click on the Start button and go to Run
2. Type in scandisk and click the OK button
3. Follow the prompts and select Thorough scandisk and let it run
4. This will tell you if there are any problems on the hard disk.

(Windows 2000/XP)
1. Open My Computer, and select the local disk you want to check
2. On the File menu, click Properties
3. Click the Tools tab
4. Under Error-checking, click Check Now
5. Under Check disk options, select the Scan for and attempt recovery of bad sectors check box and the automatically fix file system errors box
6. Select yes to schedule after restart if a dialog box comes up prompting you to do so
7. Restart your computer

# Memory diagnostic

This error can also signify faulty memory. The situations can vary, from improper configuration of RAM setting on the motherboard, mismatched RAM modules, faulty or failing RAM, etc. Please utilize Microsofts memory tester http://oca.microsoft.com/en/windiag.asp to test for any instability in the memory.

Be certain to run the tool using the extended test suite by pressing T while the Windows Memory Diagnostic is running. In addition allow the memory testing tool to thoroughly test the RAM over a period of 2 hours.

# Motherboard drivers

Make sure you have all the latest Motherboard drivers. Motherboard drivers will be available on your motherboard or system manufacturer's site. It is important that you follow all precautions given by your motherboard manufacturer when updating drivers or firmware. If you have any concerns about this step, please contact your motherboard or system manufacturer for assistance.

4. Error 131

The "Error 131" error message is usually caused by corrupt game files.

The first approach to resolving this error should always be the repair tool. The repair tool is located in the World of Warcraft folder called repair.exe.
The second step, as the repair tool will sometimes advise, is to reinstall World of Warcraft. Before reinstalling, be sure to uninstall WoW first by using the provided short-cut placed in WoWs Start Menu folder or by using the Add/Remove Programs tool in the Control Panel.


5. Error 132

The Error 132 is a vague error message that is reported when something went wrong that was unexpected and not previously documented. This error can exist due to the actual code being faulty or system instability. This was the first type of error that was created when WoW was made. The other types of errors in this thread were once Error 132s before they were isolated and separated as to their individual causes.

It is important to separate an Error 132 that happens before recent patches against those that happen after.

As an example please note this particular Error 132 that can occur before WoW is patched:


ERROR #132 (0x85100084)
Program: C:\Program Files\World of Warcraft\WoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:00604D73

The instruction at "0x00604D73" referenced memory at "0x00000054".
The memory could not be "read"."




After recent patches this error will appear as:


World of Warcraft was unable to start up 3D acceleration




Through research and troubleshooting the error reports that contain this code "0x00000054" means that there are issues using DirectX and/or the video card/drivers.

6. Error 134

There are several varieties of Error 134 that can be received however there are two primary types that are seen most often. The two most common types will be discussed here, one is caused by corruption in the World of Warcraft game files and the other is caused by a firewall or security feature restricting WoWs internet access.

Example of a corruption in WoWs game files:


ERROR #134 (0x8510086) Fatal Condition
Program: C:\Program Files\World of Warcraft\WoW.exe

Failed to open archive model.MPQ; The system cannot find the file specified.



The above type of Error 134 may vary on the actual file that is missing or damaged, this one is on the model.MPQ file. This error is commonly corrected by running the repair tool located in the World of Warcraft folder called repair.exe.

Example of a firewall or security feature restricting WoWs internet access:


ERROR #134 (0x85100086) Fatal Condition
Program: C:\Program Files\World of Warcraft\WoW.exe

Unable to establish a connection to socket: The attempt to connect was forcefully rejected.



Many firewall and security applications will recognize the game as a new program after it has been patched and therefore must be reconfigured. The easiest method of doing this would be by entering your security software/firewall settings and remove any previous settings you had for the game. After you have removed these settings start up WoW. When you re-launch the game, your security program should prompt you to allow the game access to the internet or not, select yes in this case.


Hopes this helps, Thanks.

- Brink


--------------------
Vote

Setup Guide

IRC Webchat

Dizzle [Main Character]
Go to the top of the page
 
+Quote Post
 
Start new topic
Replies
Deject3d
post Aug 2 2009, 07:22 PM
Post #2


Advanced Member
***

Group: Members
Posts: 496
Joined: 15-June 09
Member No.: 229



http://forums.worldofwarcraft.com/thread.h...21039&sid=1

thanks?
Go to the top of the page
 
+Quote Post

Posts in this topic
- Brink   WoW Errors: Common fixes!   Aug 2 2009, 05:37 PM
- - Deject3d   http://forums.worldofwarcraft.com/thread.h...21039...   Aug 2 2009, 07:22 PM
|- - Alucard   QUOTE (Deject3d @ Aug 2 2009, 08:22 PM) h...   Aug 2 2009, 10:22 PM
- - Brink   Indeed   Aug 2 2009, 07:23 PM
- - Bitza   Brink really reminds me of http://www.youtube.com/...   Aug 3 2009, 10:57 AM


Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



Lo-Fi Version Time is now: 29th March 2024 - 01:09 PM