dslreports logo
Search similar:


uniqs
139358

bendejo
Bendejo
join:2003-02-12
Plano, TX

bendejo

Member

WoW Crashes with Error #132

I have been having stability problems with World of Warcraft. Sometimes the game will close with an Error #132 while other times the system will reboot itself.

I received this error even after updating my bios, video, sound, motherboard drivers, and completely uninstalling the game, running scandisk and defreg, and reinstalling the game. I receive the error on all my characters at various times in the game, but always when I'm doing an action such as attacking, talking to an NPC, checking the quest log, resurrecting, etc.

I have an Athlon XP 3000+, 1GB of PC3200, Radeon 9800Pro 128MB, 80GB Maxtor HD, Windows XP Home SP2.

Any advice? The WoW tech support forums have been of little help. An error log is pasted below.

==============================================================================
World of WarCraft: Assertions Enabled Build (build
4222)

Exe: E:\Program Files\World of Warcraft\WoW.exe
Time: Feb 27, 2005 3:19:04.281 PM
User: Bender
Computer: Bender
------------------------------------------------------------------------------

This application has encountered a critical error:

ERROR #132 (0x85100084)
Program: E:\Program Files\World of Warcraft\WoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at
001B:007177E7

The instruction at "0x007177E7" referenced memory at "0x994A4C8C".
The memory could not be "read".

WoWBuild: 4222
------------------------------------------------------------------------------

----------------------------------------
x86 Registers
----------------------------------------

EAX=19C15C54 EBX=20000003 ECX=194A4C80 EDX=00000002 ESI=0000E3DD
EDI=00000003 EBP=0012F828 ESP=0012F814 EIP=007177E7
FLG=00210246
CS =001B DS =0023 ES =0023 SS =0023
FS =003B GS =0000

----------------------------------------
Stack Trace (Manual)
----------------------------------------

Address Frame Logical addr Module

007177E7 0012F828 0001:003167E7 E:\Program Files\World of
Warcraft\WoW.exe 0071885A 0012F9E8 0001:0031785A E:\Program Files\World of
Warcraft\WoW.exe 0071798E 0012FA60 0001:0031698E E:\Program Files\World of
Warcraft\WoW.exe
00716564 0012FA80 0001:00315564 E:\Program Files\World of
Warcraft\WoW.exe
006064B6 0012FAA4 0001:002054B6 E:\Program Files\World of
Warcraft\WoW.exe
0060D262 0012FAC0 0001:0020C262 E:\Program Files\World of
Warcraft\WoW.exe
0060D0B5 0012FAF8 0001:0020C0B5 E:\Program Files\World of
Warcraft\WoW.exe 00605D3F 0012FB74 0001:00204D3F E:\Program Files\World of
Warcraft\WoW.exe 0048D46F 0012FB90 0001:0008C46F E:\Program Files\World of
Warcraft\WoW.exe 0048D3CF 0012FBAC 0001:0008C3CF E:\Program Files\World of
Warcraft\WoW.exe 006871FC 0012FC58 0001:002861FC E:\Program Files\World
of Warcraft\WoW.exe 0068403B 0012FC80 0001:0028303B E:\Program
Files\World of Warcraft\WoW.exe 0067BB9F 0012FCA4 0001:0027AB9F E:\Program
Files\World of Warcraft\WoW.exe 0048ED2A 0012FD30 0001:0008DD2A E:\Program
Files\World of Warcraft\WoW.exe
00756DF1 0012FD54 0001:00355DF1 E:\Program Files\World of
Warcraft\WoW.exe
0074B7C8 0012FD84 0001:0034A7C8 E:\Program Files\World of
Warcraft\WoW.exe 0074A03C 0012FD90 0001:0034903C E:\Program Files\World of
Warcraft\WoW.exe 004433CE 0012FE58 0001:000423CE E:\Program Files\World of
Warcraft\WoW.exe
0041CBD6 0012FE94 0001:0001BBD6 E:\Program Files\World of
Warcraft\WoW.exe 0041887A 0012FF0C 0001:0001787A E:\Program Files\World of
Warcraft\WoW.exe
00418001 0012FF20 0001:00017001 E:\Program Files\World of
Warcraft\WoW.exe 0040422B 0012FFC0 0001:0000322B E:\Program Files\World of
Warcraft\WoW.exe 7C816D4F 0012FFF0 0001:00015D4F
E:\WINDOWS\system32\kernel32.dll

----------------------------------------
Stack Trace (Using DBGHELP.DLL)
----------------------------------------

007177E7 WoW.exe +0
(0x0000E3DD,0x0000000C,0x19472CE4,0x19C15C54)
0071885A WoW.exe +0
(0x10930E90,0x00000054,0x19472CA0,0x00000200)
0071798E WoW.exe +0
(0x0012FAB4,0x1DB0C268,0x0F370008,0x00000000)
00716564 WoW.exe +0
(0x0012FAB4,0x00000012,0x03952088,0x0F370008)
006064B6 WoW.exe +0
(0x0012FAB4,0x1DB0C268,0x00000000,0x00CA6EC8)
0060D262 WoW.exe +0
(0x0012FAF0,0x03952088,0x1DB0C268,0x0F370008)
0060D0B5 WoW.exe +0
(0x0F370008,0x0F370008,0x00000000,0x1DB0C268)
00605D3F WoW.exe +0
(0x0F370008,0x1DB0C268,0x0F370008,0x00000002)
0048D46F WoW.exe +0
(0x00000000,0x00000002,0x1D5EDA20,0x1D5EDA20)
0048D3CF WoW.exe +0
(0x000656DE,0xF0007000,0x00000000,0x00000000)
006871FC WoW.exe +0
(0x0F370008,0x0F370008,0x10BA7FA8,0x00000000)
0068403B WoW.exe +0
(0x00490402,0x00000000,0x00000000,0x00000000)
0067BB9F WoW.exe +0
(0x00000000,0x3F800000,0x00000000,0x00000000)
0048ED2A WoW.exe +0
(0x10C26FD4,0x0FB29C08,0x0FB29C14,0x0FB29C14)
00756DF1 WoW.exe +0
(0x0A8C3D08,0x0D3CC008,0x10D4FD88,0x00000000)
0074B7C8 WoW.exe +0
(0x10D4FDA0,0x0012FE58,0x004433CE,0x10D4FDA0)
0074A03C WoW.exe +0
(0x10D4FDA0,0x3C8B4396,0x0012FE6C,0x0A8C3C88)
004433CE WoW.exe +0
(0x00000001,0x0A8C3808,0x00000000,0x0A8C3C88)
0041CBD6 WoW.exe +0
(0x00000000,0x00000001,0x0A8C3808,0x00000000)
0041887A WoW.exe +0
(0x00000015,0x00402442,0x00000001,0x0012FFC0)
00418001 WoW.exe +0
(0x0040B1A4,0x00400000,0x00000000,0x001423AD)
0040422B WoW.exe +0
(0x80000001,0x00B7E0C4,0x7FFDE000,0x8054B038)
7C816D4F kernel32.dll RegisterWaitForInputIdle+73
(0x00401000,0x00000000,0x78746341,0x00000020)

----------------------------------------
Loaded Modules
----------------------------------------

0x00320000 - 0x003AF000 E:\Program Files\World of Warcraft\fmod.dll
0x00400000 - 0x00B33000 E:\Program Files\World of Warcraft\WoW.exe
0x10000000 - 0x10069000 E:\Program Files\World of Warcraft\DivxDecoder.dll
0x11C70000 - 0x11D41000 E:\Program Files\World of Warcraft\dbghelp.dll
0x4FDD0000 - 0x4FF76000 E:\WINDOWS\system32\d3d9.dll 0x5B860000 -
0x5B8B4000 E:\WINDOWS\system32\NETAPI32.dll 0x5D090000 - 0x5D127000
E:\WINDOWS\system32\COMCTL32.dll 0x5ED00000 - 0x5EDCC000
E:\WINDOWS\system32\OPENGL32.dll 0x629C0000 - 0x629C9000 E:\WINDOWS\system32\LPK.DLL
0x662B0000 - 0x66308000 E:\WINDOWS\system32\hnetcfg.dll 0x68B20000 -
0x68B40000 E:\WINDOWS\system32\GLU32.dll 0x6D990000 - 0x6D996000
E:\WINDOWS\system32\d3d8thk.dll 0x71A50000 - 0x71A8F000
E:\WINDOWS\system32\mswsock.dll 0x71A90000 - 0x71A98000 E:\WINDOWS\System32\wshtcpip.dll 0x71AA0000
- 0x71AA8000 E:\WINDOWS\system32\WS2HELP.dll 0x71AB0000 - 0x71AC7000
E:\WINDOWS\system32\WS2_32.dll 0x71AD0000 - 0x71AD9000
E:\WINDOWS\system32\WSOCK32.dll 0x722B0000 - 0x722B5000 E:\WINDOWS\system32\sensapi.dll
0x72D10000 - 0x72D18000 E:\WINDOWS\system32\msacm32.drv 0x72D20000 -
0x72D29000 E:\WINDOWS\system32\wdmaud.drv 0x73760000 - 0x737A9000
E:\WINDOWS\system32\DDRAW.dll 0x73BC0000 - 0x73BC6000
E:\WINDOWS\system32\DCIMAN32.dll 0x73EE0000 - 0x73EE4000 E:\WINDOWS\system32\KsUser.dll
0x73F10000 - 0x73F6C000 E:\WINDOWS\system32\dsound.dll 0x74D90000 - 0x74DFB000
E:\WINDOWS\system32\USP10.dll 0x755C0000 - 0x755EE000
E:\WINDOWS\system32\msctfime.ime 0x76390000 - 0x763AD000 E:\WINDOWS\system32\IMM32.dll
0x769C0000 - 0x76A73000 E:\WINDOWS\system32\USERENV.dll 0x76B40000 -
0x76B6D000 E:\WINDOWS\system32\WINMM.dll 0x76C30000 - 0x76C5E000
E:\WINDOWS\system32\WINTRUST.dll 0x76C90000 - 0x76CB8000
E:\WINDOWS\system32\IMAGEHLP.dll 0x76E80000 - 0x76E8E000 E:\WINDOWS\system32\rtutils.dll
0x76E90000 - 0x76EA2000 E:\WINDOWS\system32\rasman.dll 0x76EB0000 -
0x76EDF000 E:\WINDOWS\system32\TAPI32.dll 0x76EE0000 - 0x76F1C000
E:\WINDOWS\system32\RASAPI32.DLL 0x76F20000 - 0x76F47000
E:\WINDOWS\system32\DNSAPI.dll 0x76F60000 - 0x76F8C000 E:\WINDOWS\system32\WLDAP32.dll
0x76FB0000 - 0x76FB8000 E:\WINDOWS\System32\winrnr.dll 0x76FC0000 - 0x76FC6000
E:\WINDOWS\system32\rasadhlp.dll 0x77120000 - 0x771AC000
E:\WINDOWS\system32\OLEAUT32.dll 0x771B0000 - 0x77256000
E:\WINDOWS\system32\WININET.dll 0x77260000 - 0x772FE000 E:\WINDOWS\system32\urlmon.dll 0x773D0000 -
0x774D2000
E:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_ a84f1ff9\comctl32.dll
0x774E0000 - 0x7761D000 E:\WINDOWS\system32\ole32.dll 0x77A80000 -
0x77B14000 E:\WINDOWS\system32\CRYPT32.dll 0x77B20000 - 0x77B32000
E:\WINDOWS\system32\MSASN1.dll 0x77BD0000 - 0x77BD7000
E:\WINDOWS\system32\midimap.dll 0x77BE0000 - 0x77BF5000 E:\WINDOWS\system32\MSACM32.dll
0x77C00000 - 0x77C08000 E:\WINDOWS\system32\VERSION.dll 0x77C10000 -
0x77C68000 E:\WINDOWS\system32\MSVCRT.dll 0x77D40000 - 0x77DD0000
E:\WINDOWS\system32\USER32.dll 0x77DD0000 - 0x77E6B000
E:\WINDOWS\system32\ADVAPI32.dll 0x77E70000 - 0x77F01000 E:\WINDOWS\system32\RPCRT4.dll 0x77F10000 -
0x77F56000 E:\WINDOWS\system32\GDI32.dll 0x77F60000 - 0x77FD6000
E:\WINDOWS\system32\SHLWAPI.dll 0x77FE0000 - 0x77FF1000
E:\WINDOWS\system32\Secur32.dll 0x7C800000 - 0x7C8F4000 E:\WINDOWS\system32\kernel32.dll
0x7C900000 - 0x7C9B0000 E:\WINDOWS\system32\ntdll.dll 0x7C9C0000 -
0x7D1D4000 E:\WINDOWS\system32\SHELL32.dll

----------------------------------------
Memory Dump
----------------------------------------

Code: 16 bytes starting at (EIP = 007177E7)

007177E7: 8B 04 99 89 45 0C 8B C6 2B 45 0C 3D F4 01 00 00
....E...+E.=....

Stack: 1024 bytes starting at (ESP = 0012F814)

* = addr **
*
0012F810: 00 00 00 00 08 58 4C 0F 54 5C C1 19 EC 5B
C1 19 .....XL.T\...[..
0012F820: 00 00 00 00 00 00 80 3F E8 F9 12 00 5A 88
71 00 .......?....Z.q.
0012F830: DD E3 00 00 0C 00 00 00 E4 2C 47 19 54 5C
C1 19 .........,G.T\..
0012F840: 03 00 00 00 08 58 4C 0F 08 58 4C 0F D8 CB
53 BF .....XL..XL...S.
0012F850: 51 EE FB BD 1E 4F 0C BF 00 00 00 00 B5 CC 0F 3F
Q....O.........?
0012F860: 74 87 39 BE B8 A7 4E BF 00 00 00 00 DF 2C 6D 31
t.9...N......,m1
0012F870: BC F8 12 00 57 77 79 00 8C 41 2B 3F 48 48 3E 3F
....Wwy..A+?HH>?
0012F880: 00 00 00 00 00 00 00 00 48 48 3E BF 8C 41 2B 3F
........HH>..A+?
0012F890: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
0012F8A0: 00 00 80 3F 00 00 00 00 1C B3 9E C5 40 3D FE C4
...?........@=..
0012F8B0: 15 FC 46 C2 00 00 80 3F B4 E8 92 10 4C F9
12 00 ..F....?....L...
0012F8C0: 7A 8D 79 00 B4 E8 92 10 D4 90 B1 1D 8C 41 2B 3F
z.y..........A+?
0012F8D0: 48 48 3E 3F 00 00 00 00 00 00 00 00 48 48 3E BF
HH>?........HH>.
0012F8E0: 8C 41 2B 3F 00 00 00 00 00 00 00 00 00 00 00 00
.A+?............
0012F8F0: 00 00 00 00 00 00 80 3F 00 00 00 00 1C B3 9E C5
.......?........
0012F900: 4C F9 12 00 0A C6 7B 3F C4 CA 33 BD B2 C4
33 BE L.....{?..3...3.
0012F910: 00 00 00 00 32 D9 58 3D 00 5B 7F 3F 58 44
41 3D ....2.X=.[.?XDA=
0012F920: 00 00 00 00 E4 31 31 3E 24 25 64 BD 0E BC 7B 3F
.....11>$%d...{?
0012F930: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
0012F940: 00 00 80 3F B3 38 17 C2 3A D9 C3 C1 EA 9A 10 C2
...?.8..:.......
0012F950: 00 00 00 00 D0 FA 12 00 7E 3D 71 00 00 FB
12 00 ........~=q.....
0012F960: 08 E8 92 10 D4 90 B1 1D D4 90 B1 1D 8B 41 2B 3F
.............A+?
0012F970: 47 48 3E 3F EB 5E 7D BE 11 47 59 BE D2 04
72 BF GH>?.^}..GY...r.
0012F980: 00 00 00 00 2B 0A 78 3F 8E F2 5D BD 72 38
77 BE ....+.x?..].r8w.
0012F990: 00 00 00 00 E0 2C 6D 31 2F C9 79 3F 2A 40 60 BE
.....,m1/.y?*@`.
0012F9A0: 00 00 00 00 3F FE 16 C2 B6 90 CE C1 73 7C 0E C2
....?.......s|..
0012F9B0: 00 00 80 3F 40 0E 0F BE 3E FE B9 3F E9 61 C0 3F
...?@...>..?.a.?
0012F9C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00
................
0012F9D0: 00 00 00 00 10 00 47 19 00 00 00 00 28 5C
C1 19 ......G.....(\..
0012F9E0: 00 00 00 80 00 00 00 80 60 FA 12 00 8E 79
71 00 ........`....yq.
0012F9F0: 90 0E 93 10 54 00 00 00 A0 2C 47 19 00 02 00 00
....T....,G.....
0012FA00: 08 58 4C 0F 10 00 47 19 00 00 00 00 00 00 00 00
.XL...G.........
0012FA10: 00 00 00 00 00 00 80 3F 00 00 00 00 1C B3 9E C5
.......?........
0012FA20: 40 3D FE C4 15 FC 46 C2 00 00 80 3F 8B 41 2B 3F
@=....F....?.A+?
0012FA30: 47 48 3E 3F 00 00 00 80 00 00 00 00 47 48 3E BF
GH>?........GH>.
0012FA40: 8B 41 2B 3F 00 00 00 00 00 00 80 3F 00 00 80 3F
.A+?.......?...?
0012FA50: 00 00 80 3F 00 00 00 00 00 00 00 00 00 00 00 00
...?............
0012FA60: 80 FA 12 00 64 65 71 00 B4 FA 12 00 68 C2 B0 1D
....deq.....h...
0012FA70: 08 00 37 0F 00 00 00 00 D5 46 03 C0 2E 64
71 00 ..7......F...dq.
0012FA80: A4 FA 12 00 B6 64 60 00 B4 FA 12 00 12 00 00 00
.....d`.........
0012FA90: 88 20 95 03 08 00 37 0F 11 0E F0 3F 15 07 3F 40 .
....7....?..?@
0012FAA0: 01 00 00 00 C0 FA 12 00 62 D2 60 00 B4 FA
12 00 ........b.`.....
0012FAB0: 68 C2 B0 1D 00 00 00 00 C8 6E CA 00 C8 6E CA 00
h........n...n..
0012FAC0: F8 FA 12 00 B5 D0 60 00 F0 FA 12 00 88 20
95 03 ......`...... ..
0012FAD0: 68 C2 B0 1D 08 00 37 0F 88 20 95 03 00 00 00 00 h.....7..
......
0012FAE0: 7F 0E 7F 02 F4 FA 12 00 68 90 42 00 3F 14
52 0E ........h.B.?.R.
0012FAF0: 00 00 00 00 00 00 00 00 74 FB 12 00 3F 5D 60 00
........t...?]`.
0012FB00: 08 00 37 0F 08 00 37 0F 00 00 00 00 68 C2 B0 1D
..7...7.....h...
0012FB10: 00 00 00 00 00 00 80 3F 00 00 00 00 00 00 00 00
.......?........
0012FB20: 00 00 80 3F 74 FB 12 00 5D 64 60 00 96 43 8B 3C
...?t...]d`..C.
0012FB30: 00 00 00 00 50 FB 12 00 08 32 8F 17 08 00
37 0F ....P....2....7.
0012FB40: DE 56 06 00 00 70 00 F0 30 F2 3C 0D 68 FB
12 00 .V...p..0..h...
0012FB50: 73 5C 60 00 02 00 00 00 68 C2 B0 1D 20 04
41 00 s\`.....h... .A.
0012FB60: DE 56 06 00 68 C2 B0 1D 90 FB 12 00 62 D4
48 00 .V..h.......b.H.
0012FB70: 58 72 00 00 90 FB 12 00 6F D4 48 00 08 00
37 0F Xr......o.H...7.
0012FB80: 68 C2 B0 1D 08 00 37 0F 02 00 00 00 08 00
37 0F h.....7.......7.
0012FB90: AC FB 12 00 CF D3 48 00 00 00 00 00 02 00 00 00
......H.........
0012FBA0: 20 DA 5E 1D 20 DA 5E 1D 30 EA AA 00 58 FC
12 00 .^. .^.0...X...
0012FBB0: FC 71 68 00 DE 56 06 00 00 70 00 F0 00 00 00 00
.qh..V...p......
0012FBC0: 00 00 00 00 E8 BE B1 00 A8 7F BA 10 D4 00 0E BF
................
0012FBD0: 40 01 55 3F 00 00 00 00 40 01 55 BF D4 00 0E BF
@.U?....@.U.....
0012FBE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 3F
...............?
0012FBF0: D3 00 0E BF 3F 01 55 3F 00 00 00 00 00 00 00 00
....?.U?........
0012FC00: 3F 01 55 BF D3 00 0E BF 00 00 00 00 00 00 00 00
?.U.............
0012FC10: 00 00 00 00 00 00 00 00 FF FF 7F 3F 00 00 00 00
...........?....
bendejo

bendejo

Member

Response from WoW Tech Support when I sent a second error message:

While we are investigating the "Error 132" error message, please try a few more common solutions that have helped other customers:

1. If you have an Interface folder, rename it or delete it completely, then remove all the files in your WDB and WTF folders. They 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.

2. Try running the game in openGL mode:

- Click Start
- Highlight Programs
- Highlight World of Warcraft without clicking on it.
- Right click on the World of Warcraft icon
- Click Properties
- In the Target field add -opengl after the quotation mark
Example: "C:\Program Files\World of Warcraft\WoW.exe" -opengl
- Click OK
- Try the game now with the icon you just modified.

You can also try running the game in a window by adding
-windowed
to the line as explained above. You can also put both options on at the
same time, just make sure there is a space between them.

3. A program running on your machine could be causing issues. Please
try closing all background applications as explained on our support site:
»www.blizzard.com/support ··· agi0558p

4. Check your hard disk for errors by following the instructions on our
ScanDisk/Defrag page:
»www.blizzard.com/support ··· mgi0559p

Also, note that some customers have reported that hard drives larger
than 127 gigabytes in size can have issues if you do not have the latest
Windows Updates from Microsoft:
»windowsupdate.microsoft.com/

We recommend that you read all the documentation that came with your hard drive of system. Many manufacturers have special instructions necessary for proper use of 48-bit Large Block Addressing on hard drives larger than 127 gigabytes.

5. World of Warcraft attempts to use your hardware to it fullest. If you overclock your hardware in any way, even if other applications on your computer are stable, it may cause problems with World of Warcraft. Please set all your components to their factory default speeds while playing World of Warcraft.

6. Doing a scan of the computer's physical memory can help you identify 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:
»oca.microsoft.com/en/windiag.asp

We recommend the extended test suite, which takes the longest time to run but is the most thorough test suite available with this tool.

7. If your system is becoming too hot, it may cause the game to freeze or crash. You can test this by removing the side of your case from the computer for troubleshooting purposes. If the issues go away, then we suggest adding a fan to your system to help distribute heat in the case.

8. Try disabling the sound card, by following these steps:
- Right click on My Computer and select properties.
- (Windows 2000 only) Click on the Hardware tab.
- Click on Device manager.
- Expand the Sound, video, and game controllers branch.
- Select the sound card and click the Properties button.
- Disable the device from the active profile.
- Click OK
- Reboot your computer and start the game again.

9. Remove all custom User Interface (UI) mods from your game installation. To do this, go into your World of Warcraft folder and delete the folder called "Interface."
bendejo

bendejo

Member

My responses to his suggestions, if anyone could comment I would appreciate it:

1. I have done this already before, it didn't seem to help.

2. What exactly is openGL mode?

3. All background programs are closed or disabled.

4. Did a scandisk/defrag when I uninstalled the game. I have 80GB HD.

5. No overclocking on my machine at all.

6. I will try this diagnostic tonight. Anyone get good results from other tools?

7. I have a large heat sink fan on my CPU and one 80mm case fan on the rear of the tower in addition to the fan for the power supply. I have a ATX mid-tower case. The CPU runs between 52 and 58 degrees.

8. Haven't tried this yet.

9. I have done this already before, it didn't seem to help.
bendejo

bendejo

Member

I haven't seen a crash in about 2 weeks. The "fix" or last thing I tried to change since the last crash was:

Moved Memory DIMM 2 from DIMM Slot 2 to DIMM Slot 3

This enabled dual channel memory mode on my motherboard and also required uninstalling and re-seating my DIMM's. So my theory is that either my memory was having communication problems in single channel mode or my DIMM's possibly weren't seated well to begin with.

Since I didn't have any problems with the memory in other games or with the Windows Memory diagnositc, I'm thinking its the dual channel mode that was the fix.

AuraReturn
Premium Member
join:2003-08-18
USA

1 edit

AuraReturn to bendejo

Premium Member

to bendejo
1394 views and 3 replies. Is this a record?

Sorry, make that 4.:D

Rdax
Premium Member
join:2001-05-18
El Dorado, AR

Rdax

Premium Member

That just shows how popular WOW is.
yitsan
join:2005-03-26
Netherlands

yitsan

Member

WoW keeps crashing with this error for me after the last update from Blizzard... Does anyone recognize this problem?
thirdeyeopen7
join:2005-03-27

thirdeyeopen7 to bendejo

Member

to bendejo
I tryed opengl mode, and now i crash every 40-45 minutes instead of every 5-10! Thanks!

MikeBland
@tallah01.fl.comcast.

MikeBland to bendejo

Anon

to bendejo
Well I am glad I am not the only one having this problem. I noticed that it started happening after the last update. Prior to the update my game was running perfectly. Anyone else notice this? When it started, I uninstalled the game, defragged my system, ran a scan disc (no errors found) and reinstalled the game. Now it is worse then ever and crashes every 5 minutes. Is there a solution?

Neoptolemos
@dsl.hccnet.nl

Neoptolemos to bendejo

Anon

to bendejo
It has to do with the new update, they already fixed a few errors so part of the community can go back online, this is one of the very few errors that still isn't fixed though. Sometimes playing on another server fixes it, but that sucks.

Hey, it's Blizzard, duh.

MaRsHlL
@rivernet.com.au

MaRsHlL to MikeBland

Anon

to MikeBland
i have been getting same errors as you and have tried all you have as well my pc spec are more than yours and still i get errors too...

for me wow started great no crash maybe 1 or 2, but update after update is has gotten worse... i get them in same spots u mentioned and now it has even made some other game on my pc start to do same thing..

have you traied a format and re install i am trying this after backup and apparenty page errors may be cause but a build of of crap in pc..

ill let yas know

bendejo
Bendejo
join:2003-02-12
Plano, TX

bendejo

Member

I forgot to mention that somewhere along the line I played in openGL mode and it continued to crash, but also had lots of lag and artifacts in the video. The only item I never tried was playing with the audio card disabled.

I didn't start getting the errors until the previous patch (not last weeks) and stopped getting the errors before this current patch.

Again the last thing I implemented was dual channel mode on my RAM. I have since added back in all my uiMods and replaced the cover on my case (removed to lower system/cpu temps) without a crash.

Take note in your error logs that there are several types of error message that are label Error #132. Mine happened to specifcally reference the memory.

Demonphlegm
@tpgi.com.au

Demonphlegm to bendejo

Anon

to bendejo
I have had this problem as long as the game has been available - I even upgraded to a brand new computer too (January). I have done every type of diagnostic known to mankind (or so it seems) on every part of my computer. I've defraged, reinstalled, reformated, updated, even underclocked for more stability, cleaned, run the game in open GL, windowed (and both at once) and done every single thing Blizzard told me to do and nothing. The ONLY way I can play longer than 5 mins is by ONLY USING 1 STICK OF MEMORY, and even then it still does it, just a little less often.
oh, by the way My set up is this:
Athlon 3200+ socket 939 w/hyperthreading
80 gig SATA
MSI Geforce 6800GT
Sound blaster Audigy LS
1gig (2 x 512) Corsair TWINX latency: 2-2-2-5 - so it aint mismatched memory. I have swaped the memory in to every combination possible on my board dual and single channel with the same result.
all on an Abit Uguru - so I know that my temperatures aren't bad (eg. cpu runs @ 29 - 32 degrees)
In a thermaltake Tsunami Dream case.
NOT A SINGLE OTHER GAME I HAVE EVER PLAYED ON THIS MACHINE DOES THIS ERROR - ONLY WOW.
Only a bad tradesman blames his tools.
Blizzard needs to fix the current problems of the game rather than just making up new servers for more money, as their current level of customer support......well you go figure.

longstreet
join:2004-11-14
Plano, TX

4 edits

longstreet

Member

I think the error has to do with user mods . . . if you remove all of your add ons, remove WoW, reinstall a fresh copy, then update and play without any add ons (cosmos ui etc) I think it might alleviate the problem.

You might need to do more than just remove the directory, try using add/remove programs to do it.

I would also revert to all previous driver versions or bios versions you've had in the past, as sometimes new updates actually create more problems if the update isn't designed properly during development.

First thing would be flashing the MB bios back to the earlier version.

If all else fails, format, reinstall windows, windows update, then install wow and see if it runs. I would ignore getting any driver updates from windows update, just get the direct x stuff, .NET, etc.

It looks like the game tryed to read from a specific memory location but that location was protected for whatever reason. This could be reasonably fixed by blizz by telling the game to copy the information to another location and then read it.

Looks like Blizzard/Your hardware manufacturer should add a few more of these :

try
{
**do thing causing crash**
}

catch
{
**copy information to another memory location**
**try and read it**
}

Blame the patch designers from WoW, or whoever wrote the new driver version for your hardware. It could also be a sign that one of your memory chips is going bad.
longstreet

2 edits

longstreet

Member

I found a link for a fixed Exe for this crash :

Here it is :

»ftp://ftp.uunet.co.za/pub/inco ··· /wow.exe

I found this at another web forum off google, I don't know if it works or the content of the Exe, so try at your own risk. I would assume you should backup your regular exe, and then rename it to .bak then place this in the game directory. If it doesn't work then just delete it, and rename the regular exe.

I don't know what version this works with.

Good luck.

Rdax
Premium Member
join:2001-05-18
El Dorado, AR

Rdax to bendejo

Premium Member

to bendejo
Lose the UI's and you will be ok. Game has most of what you need now.

bendejo
Bendejo
join:2003-02-12
Plano, TX

bendejo

Member

A restatement of one of my earlier posts, I uninstalled and deleted the game folders and reinstalled the game with no UI mods and it didn't help with the error.

When I switched the memory to dual channel mode (moving from DIMM slot 2 to DIMM slot 3 on my Giga-byte GA-7N400V Pro2 Mobo) I was able to play the game without crashes or Error 132's. I slowly added back in UImods and am now playing with Gypsymod, Selfcast, MapNotes, MapNotesGathering, and EasyMail. I have been crash free for at least three weeks while playing long hours.

It seems that my solution will not work for everyone, but it is something to look at that is not suggested by the WoW tech support if you are getting the error.
thirdeyeopen7
join:2005-03-27

thirdeyeopen7 to longstreet

Member

to longstreet
I used this exe file and couldn't even open the game without crashing immediatly, i wouldnt recomend this link to anyone.

Robrat41
@cable.ubr03.blac.blu

Robrat41 to bendejo

Anon

to bendejo
Tried all this and now I cant even re-install. it hangs usually when loading terrain.mpq from disk 1 but on the odd occasion it gets past (once I've removed all references to WOW from the registry) it then hangs loading a file with the same name from disk 2. "Screams in frustration".
By the way every thing was perfectly okay until the 1.3.0 update. :-P
deadalus9
join:2005-04-02

deadalus9 to bendejo

Member

to bendejo
hello to u all
my problem is a bit different
as soon as i enter the world o got the #132 error note and the game crush.

at first it worked and the crushes been happening every ~5 minutes or so.
then i reinstalled and after that i werent able to play anymore

i closed all my background programs, i tried both openGL and window mode.
before my second installation i done deffrag and scandisk.

the only thing that helped a little is the hacked EXE file which found by longstreet:
"I found a link for a fixed Exe for this crash :

Here it is :

ยป»ftp://ftp.uunet.co.za/pub/inco ··· wow.exe"
the game does work and i enter to the world but i cant do anything all but me is frozen and i cant cast spell ETC...
(as if my client doesnt get any information from server)

i have client 1.2.4
my comp':
P4 3.0 GHZ
512 duel DDR ram
80G HD
Nvidia Geforce PCX 5300
intel 915G motherboard
cabel connection via usb (not network adapter card)
all hardware is non overclocked

and my error log:This application has encountered a critical error:

ERROR #132 (0x85100084)
Program: C:\Program Files\World of Warcraft\WoW.exe
File: C:\build\buildWoW\ENGINE\Source\Services\Texture.cpp
Line: 1935

textureptr

WoWBuild: 4222

and:
This application has encountered a critical error:

ERROR #132 (0x85100084)
Program: C:\Program Files\World of Warcraft\WoW.exe
File: C:\build\buildWoW\WoW\Source\ObjectMgrClient\ObjectMgrClient.cpp
Line: 1182

Failed to update object data. Object (0x0000000000859644) unknown to client!

WoWBuild: 4222

and i have also probelem with error #0
:This application has encountered a critical error:

ERROR #0 (0x85100000)
Program: C:\Program Files\World of Warcraft\WoW.exe
File: C:\build\buildWoW\WoW\Source\Net\NetClient\NetClient.cpp
Line: 332
Expr: "id NUM_MSG_TYPES", id = 55655 (0x0000D967)

WoWBuild: 4222
____________________________________________________
so what should i do install again?
i've noticed that the major problem is with the files Texture.cpp, ObjectMgrClient.cpp and NetClient.cpp.
i have searched for those and found out these files isnt on my computer!
if anyone who have a stable & working WoW can send my those file i will be great full

bendejo
Bendejo
join:2003-02-12
Plano, TX

bendejo

Member

My WoW install has been stable **knocks on wood** and I don't have any of those three .cpp files on my computer.

wowuser
@shawcable.net

wowuser to deadalus9

Anon

to deadalus9
That last post shows that you aren't patched properly...

Read wow's forums and you would've got that answer there... Build is 429x somewher around there... your number is low...

As for downloading that .exe up there... whoever did it, I'd run a virus/trojan scan on your system... never run programs you don't know. Especially when it's not even from a trusted source.

MRManZ1691
@comcast.net

MRManZ1691

Anon

so is there a fiz because i am getting it every 20 min or so and i eep getting artifacts n the screen as well. This is really bothering me.

World of WarCraft: Assertions Enabled Build (build 4297)

Exe: C:\Program Files\World of Warcraft\WoW.exe
Time: Apr 3, 2005 10:13:40.359 PM
User: Andrew
Computer: MADDDOGG
------------------------------------------------------------------------------

This application has encountered a critical error:

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

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

WoWBuild: 4297
deadalus9
join:2005-04-02

deadalus9 to bendejo

Member

to bendejo
btw i forgot to ask
are u playing in the official servers or this problem only happen if u play privet servers?

bendejo
Bendejo
join:2003-02-12
Plano, TX

bendejo to MRManZ1691

Member

to MRManZ1691
said by MRManZ1691:

so is there a fix because i am getting it every 20 min or so and i keep getting artifacts n the screen as well. This is really bothering me.
In my personal experience and research on this error, I have discovered no "fix" for this issue. There are many suggested "fixes" by Blizzard which I recommend you try them all. They are listed in the 2nd post on this topic.

My "fix" was not one that was recommended by Blizzard, which was enabling dual channel mode for my memory on my motherboard.

The "fix" for you may be something else yet. Let us know how it goes.

suckafreec
@rr.com

suckafreec

Anon

hey,

im at my friends house and he wanted me to overclock his 9200 so i downloaded ATI Tool (i use it at home, no problems, same videocard too) and i bumped it up a lil bit and as soon as you enter the acutal game, after it loads "westfall" or wherever your at it crashes, like deadalus' problem "hello to u all
my problem is a bit different
as soon as i enter the world o got the #132 error note and the game crush.
" same thing here.. we tried setting the clock back to default (still wont work) then we uninstalled the program (still wont work) what should we do next??

thanks
Margolis
Premium Member
join:2003-11-24
Saint Louis, MO

1 edit

Margolis to deadalus9

Premium Member

to deadalus9
said by deadalus9:

btw i forgot to ask
are u playing in the official servers or this problem only happen if u play privet servers?
well it can't be the official servers since you can't even log on without the game being patched to the latest. Also the game automatically updates if you aren't patched. Something is very fishy

Blackwort
@sequoa01.nm.comcast.

Blackwort to Demonphlegm

Anon

to Demonphlegm
I found a solution that seems to have worked for me. I believe that this is a hardware error and deals primarily with your motherboard and the memory (this is just a guess based on lots and lots of trial and error). Therefore, the actual solution may be a little different for each set of hardware.

In my case, I was using an ASUS A7N8X mb with two 256MB sticks of Kingston Value Ram in dual channel mode. I was able to stabilize WOW by (1) slowing down the FSB frequency to 333 (instead of 400) and later by (2) replacing the Kingston Value Ram sticks with two Corsair TwinX memory sticks (and resetting the FSB to 400).

I ran two separate memory diagnostic programs overnight to test the Kingston memory (at 400) and they passed both time without a problem. Therefore I'm tempted to believe that the problem stems from one of those "compatibility" issues.

I admit I am no computer expert and I have no idea what would cause a seemingly good stick of memory to not work because of the manufacturer.

Although I doubt my solution will work for everyone, I believe that you will probably find your solution by focusing on the memory and motherboard.

BTW: I ran all my trial an error test with a minimum amount of extra hardware and software. At the time I had only installed Windows XP SP1, DirectX9c, NForce drivers for my MB, ATI Radeon drivers and World of Warcraft. The only card plugged into the MB was the video card and I had disabled the onboard sound. I also used the onboard Lan.

air taran
@lsanca1.dsl-verizon.

air taran to Demonphlegm

Anon

to Demonphlegm
same shit with my computer and now im getting really pissed off....BLizzard really needs to friggin solve this or repl er sumthin cuz this is bullshit
Margolis
Premium Member
join:2003-11-24
Saint Louis, MO

Margolis

Premium Member

said by air taran:

same shit with my computer and now im getting really pissed off....BLizzard really needs to friggin solve this or repl er sumthin cuz this is bullshit
or just fix your computer.