User:Resa1983/Diagnosing ERROR 132 in Windows

This page contains information on how to diagnose your ERROR 132 log. Please be sure to scan through each section.

Note: If you run a Dell XPS 630i, this guide can't help you due to a hardware issue with this system's entire manufacturing line.

Fake MSN Messenger / Keylogger
If you see the following at the beginning of your crash log: The instruction at "0x0000022D" referenced memory at "0x00000001". then you have a keylogger. Please run Malwarebytes.

Atlasloot
If you see the following at the beginning of your crash log: The instruction at "0xxxxxxxxx" referenced memory at "0x00000008". then Atlasloot is crashing you. Please update it as they've now resolved this issue.

Cache issues
This issue pops up if your copy of wow incorrectly closes. This is shown when your error section looks like this: Program: C:\Users\Public\Games\World of Warcraft\WoW.exe File: .\DBCache.cpp This is a quick & simple fix. Navigate to  (or whatever path it shows in your error log), go to the   folder, and delete that folder.

Clues in Loaded Addons Section
You can skip this section if the loaded addons section looks like this: Current Addon: (null) Current Addon function: UNKNOWN Current Addon object: (null)

If any of those 3 lines show anything but the above, then the addon named is the cause of your crashing. Update it, or remove it.

This is an example of an XPerl crash: Current Addon: XPerl_RaidFrames Current Addon function: XPerl_Raid_Grp2UnitButton3nameFrame:SetBackdrop Current Addon object: (null)

Clues in the GxInfo section
GxApi: OpenGL This shows Wow's running in OpenGL mode, which is not recommended for Windows users (other than testing purposes) as it can cause wow to crash. Run wow without the -opengl tag

Clues in Stack Trace
To diagnose the stack trace, you'll want to look at usually the first 2-3 lines only. If the top 2 lines of your Stack Trace look like the lines below, then skip to the Loaded Modules Section. 007F3E6B 001AFCB0 0001:003F2E6B D:\World of Warcraft\WoW.exe 007F41D9 001AFCD8 0001:003F31D9 D:\World of Warcraft\WoW.exe

DirectX crash
This is an example of a DirectX crash: 4FE625B6 0019F9DC 0001:000915B6 C:\WINDOWS\system32\d3d9.dll 0063AD36 0019FA18 0001:00239D36 C:\World of Warcraft\WoW.exe or 75FA11D8 001BF454 0001:000011D8 C:\Windows\syswow64\kernel32.dll 712BE36E 001BF47C 0001:0010D36E C:\Windows\system32\d3d9.dll This one's iffy. The cause can either be outdated DirectX, or outdated graphics card drivers.
 * ATI's website
 * Nvidia's website

Graphics card drivers crashing
This is an example of Nvidia graphics card drivers crashing: 6F39690B 0019FA9C 0001:0039590B C:\Windows\system32\nvd3dum.dll 6F271599 0019FAD0 0001:00270599 C:\Windows\system32\nvd3dum.dll

This is an example of ATI graphics card drivers crashing: 69C760E1 001FFBC0 0001:000150E1 C:\Windows\system32\atiumdag.dll 69C67ACA 001FFD44 0001:00006ACA C:\Windows\system32\atiumdag.dll

This generally occurs when the graphics drivers are outdated. To fix this obtain new graphics drivers.
 * ATI's website
 * Nvidia's website
 * Intel's website

Intel drivers crashing
This is an example of Intel graphics card drivers crashing: 6F514E25 001FF704 0001:00003E25 C:\Windows\system32\igdumd32.dll 6F52BF1F 2C18FEC0 0001:0001AF1F C:\Windows\system32\igdumd32.dll

Update the graphics card driver. If it doesn't work, you'll have to set fixedfunction.

Malware/Keyloggers
One sign of malware is the in the first few lines of the stack trace. 10071E39 001AF6F8 0000:00000000   0042011C 001AF758 0001:0001F11C C:\World of Warcraft\WoW.exe Essentially, its trying to hide, but still keylog your machine. Most Antiviruses won't bother picking up game-related keyloggers, so anti-malware programs are essential to getting rid of this. Run malwarebytes.

Clues in the Memory Dump
If you don't see any words other than  in the dump, skip to the last section.

Cache
To figure out if you have a cache error or not, just search the dump for the word.

0019D200: 4A 00 00 00 43 3A 5C 55 73 65 72 73 5C 74 68 65 J...C:\Users\\AppData\L 0019D220: 6F 63 61 6C 5C 42 6C 69 7A 7A 61 72 64 20 45 6E ocal\Blizzard En 0019D230: 74 65 72 74 61 69 6E 6D 65 6E 74 5C 42 61 74 74 tertainment\Batt 0019D240: 6C 65 2E 6E 65 74 5C 43 61 63 68 65 5C 00 00 00 le.net\Cache\...

This represents a cache corruption. This means the last time you played wow, wow closed incorrectly, and it corrupted the folder. To fix this issue, delete the cache folder. The good thing with this type of error, it'll tell you EXACTLY which Cache folder it is (Wow uses at least 2 due to battle.net). The address of the folder needed to be deleted can be found in the memory dump. In the above case, its where is the username on the OS.

Cache errors can also look like:

001FF8D0: D4 F8 1F 00 43 61 63 68 65 5C 57 44 42 5C 65 6E ....Cache\WDB\en 001FF8E0: 55 53 00 00 00 00 00 00 00 00 00 00 00 00 00 00 US..............

In this case, we go up to the 3 lines where it states the error #: ERROR #132 (0x85100084) Fatal Exception Program: C:\Users\Public\Games\World of Warcraft\WoW.exe

And it'll tell us where the Cache folder is:

DBG
0019FCD0: 44 42 47 3A 41 63 65 45 76 65 6E 74 32 30 46 72 DBG:AceEvent20Fr 0019FCE0: 61 6D 65 00 B8 3B BF 08 60 30 C4 12 01 00 00 00 ame..;..`0......

DBG: represents an addon is causing the wow crash. What follows DBG is usually the addon name, or something connected to the addon. In this case, its something Ace2/Ace3 related which is causing the crash. Unfortunately this doesn't help much as there are many addons which use the Ace2/Ace3 Library.

What we recommend in these circumstances, is first updating your addons. If after updating all addons, you still get this same crash, then you'll want to disable ALL Ace-related addons & the library, and then re-enable them one by one until you crash again. AddonControlPanel is great for this.

Sound driver errors
Sound driver errors will always mention the driver. Either by the input (Microphone) default driver, or the output default driver. They'll usually always say, and you can look for   or   in the dump to diagnose this as the cause of the crash.

Issues with sound drivers can look like this: 0019FA60: 4D 69 63 72 6F 70 68 6F 6E 65 20 28 52 65 61 6C Microphone (Real 0019FA70: 74 65 6B 20 48 69 67 68 20 44 65 66 69 6E 69 74 tek High Definit 0019FA80: 69 6F 6E 20 41 75 64 69 6F 29 00 00 00 00 00 00 ion Audio)......

Or this: 001EFA90: 00 00 00 00 53 74 65 72 65 6F 20 4D 69 78 20 28 ....Stereo Mix ( 001EFAA0: 56 49 41 20 48 69 67 68 20 44 65 66 69 6E 69 74 VIA High Definit 001EFAB0: 69 6F 6E 20 41 75 64 69 6F 29 00 00 00 00 00 00 ion Audio)......

To fix these errors, you need to update your sound drivers. If after updating to the latest version of your sound driver, you still receive this sound-related crash, chances are your soundcard/OS is no longer being supported. As such if you want to play, you'll have to disable all sound.


 * Realtek's website
 * VIA's website
 * Creative/Soundblaster's website

Clues in the Hardware Section
The last section of the error logs is usually the hardware section. For some ERROR 132s, it doesn't appear as its not necessary to diagnose the problem.

Vista without Service Pack 2
If running Vista, and you don't have Service Pack 2 installed, wow can randomly crash due to an error in Vista. Your hardware section will look like this: Os Version: 6.0 Os Service Pack: 0.0 Service Pack 2 is required for wow. To fix this issue, install Service Pack 2.

Antivirus

 * Avast
 * Housecall Online Scanner

Anti-Malware

 * Malwarebytes
 * ComboFix