Error #134 Error #134 is usually caused by a corrupted file. However, we have also seen this error message being caused by hard drive issues such as bad sectors or due to bad/mismatched RAM. To address this issue, try each of the solutions below.
Step 1 - Remove and Repair In the example above, the file expansion3-speech-enUS.MPQ appears to be the source of the corruption. Find and delete this file. These files can generally be found in your World of Warcraft\Data or World of Warcraft\Data\enUS directory. Note: Do not delete the entire enUS folder, doing so may require you to reinstall the game. Once the file has been deleted, run the Repair Utility found in your World of Warcraft directory. Running the Repair Utility will check your game files and replace them if they are found to be corrupt. If you do not have the most current version of the Repair Utility installed, you can download it from us directly. Once the repair is finished, try playing again. Step 2 - Check for RAM Errors Doing a scan of the computer's physical memory can help you identify memory (RAM) problems which could cause this issue. We are tentatively recommending users try memory scan utilities such as the Windows Memory Diagnostic, available directly from Microsoft. We recommend the extended test suite, which takes the longest time to run but is the most thorough test suite available with this tool. Please ensure that you follow the directions properly when using the tool. If any errors are found while it runs it could indicate that a physical error exists with your memory (RAM) and you will want to contact your system manufacturer or the RAM manufacturer for assistance in replacing it. Windows Vista includes its own RAM diagnostic tool, please see our Windows Vista Memory Diagnostic Tool article for instructions. Step 3 - Update Motherboard/Video Drivers Make sure you have all the latest Motherboard/Video drivers. Motherboard/Video drivers will be available on your system manufacturer's site. It is important that you follow all precautions given by your manufacturer when updating drivers or firmware. If you have any concerns about this step, please contact your system manufacturer for assistance. Links to web sites can be found on the Hardware Manufacturers page. You also want to make sure you have all the available updates from Microsoft. Step 4 - Uninstall, Scandisk and Defrag, Reinstall, and Patch Before following these steps, users should uninstall World of Warcraft by going to: Start -> Programs -> World of Warcraft -> Uninstall World of Warcraft Once the uninstallation is complete, go into your hard drive, into the folder called "Program Files," and then delete the entire "World of Warcraft" folder. Now you're set to run a thorough scandisk and defrag of your hard drive(s). You will probably find it helpful to disable your screen saver and power management features before you scandisk or defrag. Sometimes Windows will restart the defragmentation and/or scandisk if your screen saver or power management kicks in. You may find a full set of instructions on how to run a ScanDisk and Defrag. Once you are done with the Scandisk and Defrag, please reinstall World of Warcraft normally. After the game is installed, log-in to the game to automatically download the latest patch. I was going through my WoW Folder and this is what I did to fix it, it pissed me off at first, but here it is.
Go to the place where your WoW Folder is and Right Click > Properties. After that, try to find Read-Only, and uncheck it. -__________- It works, promise.
Error #132 Error #132 is a problem which is caused by your computer being unable to correctly read & save the “temporary files” that your game requires to run. We’ve found that many WOW games which have been played once are showing this error, because your PC cannot handle the temporary files which it requires to run. This means that if you are seeing the 132 error, you need to basically repair any of the problems that are leading the issue to show – a process that can be done by using the steps outlined on this page. What Causes World Of Warcraft 132 Errors? The errors you’re seeing are caused by your computer not being able to correctly process the “temporary files” that the WOW game requires to run. You need to realize that all versions of WOW will use a series of “Temporary Files” to help the game run. These files will store everything from battle data to your profile information, and are highly important for the smooth operation of the game. In order to ensure that this error does not show, you need to make sure that any offending files / settings are fixed, and that your PC can run WOW properly. How To Fix The 132 World Of Warcraft Error Step 1 - Clean Out The Temporary Files Of World Of Warcraft The temporary files of World Of Warcraft are where your game keeps the information it uses to run, and is highly important. It will be the case that there’ll be some problem / error that will be preventing WOW from reading the temporary files, meaning that you should delete them by using the steps here: - Click onto “My Computer“ - Browse to “C:/Program Files/WarCraft” (or where you installed the game) - Locate the “Interface” folder and rename is to “InterfaceBackup” (you may or may not have this folder) - Locate the “Cache” & “WTF” folders, and rename them These folders will be recreated with default values the next time you run the game. Please note that if you haven’t successfully gotten into the game yet, these folders may not exist. If that is the case, please move on to the next step. Step 2 - Update Your Video Drivers It’s recommended that you repair any of the video drivers that your computer will have. Most of the time, World Of Warcraft will be so advanced that the current video drivers that you will have on your PC will be unable to correctly process – making it recommended that you update the video drivers of your system. To do this, you should click onto either ATI or NVidia and download the latest drivers that your computer will use to run. Step 3 - Re-Install The World Of Warcraft Program In order to fix the problem you’re seeing, you should look to re-install the World Of Warcraft program. This can be done by clicking onto “Start > Control Panel > Add / Remove Programs” and removing the WOW application from, your PC. This will remove the program from your PC, and then allow you to re-install the application onto your system from the installation CD. This will refresh any of the programs that your game will use to run – allowing your computer to run much smoother as a result. Step 4 - Clean Out The Registry - Download a Registry Cleaner and run it. This is highly recommended to help your computer run as smoothly as possible. The “registry” is a large database which stores all the important settings that your computer will use to run. Although the registry is a highly important part of the Windows system, which is used to store all the important settings that your software & games require to run. World of Warcraft keeps a large number of important settings inside the registry, which stores everything from your keyboard layout to your player profile settings. In order to make sure the 132 error does not show again, its’ recommended that you use a registry cleaner to fix any of the problems that your system may have inside by downloading & running a registry cleaner tool. Error #0
Error #0 is a basic error and can be caused by anything. In most cases it is reffering to being unable to connect to the server because it's being blocked by a firewall or anti-virus software. While in other cases it temporary just lost track of the connection and thus doesnt know what to do. Possible sollution: - Check your connection if warcraft is being blocked. - Ignore the error and restart the game. note: Mostly after error 0 the real error appears when restarting. - Check your pc if it works propperly - Delete cache / WTF folder. A real sollution to error #0 isnt there .. cause it isnt a real error of the game. ERROR #0 (0x85100000) Assertion Failure" is caused by entering email address instead of account name on login screen.
All credit to somezombie for original post.