WoW Error 132 Problems running World of Warcraft
  1 / 2    
WoW frequently crashes on a newly built pc.

================
This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal Exception
Program: C:\Program Files\World of Warcraft\WoW.exe
Exception: 0xC0000096 (PRIV_INSTRUCTION) at 001B:023327B0
====================

The PRIV_INSTRUCTION sometimes also shows as ACCESS VIOLATION

System specs are:
AMD Athlon 64 X2 4400+
Asus A8N SLI Premium motherboard
2g (2x1024) Corsair TWINX2048 - 3200C2PT RAM
WD Raptop 74g SATA
ATI Radeon X1900XTX 512 video card

(SLI mobo was a brainfart. Had 7800 GTX in shopping cart, then saw rebate deal on x1900xtx. Didnt switch mobo to a crossfire board. Hope that doesn't matter since i am only running 1 PCIe x16 card!)

I've run memtest86 on the memory and didnt find any errors. I havent done any overclocking to the system. This is my first home-built PC.

Any suggestions on what to do next? Any help would be much appreciated!
WoW frequently crashes on a newly built pc.



================

This application has encountered a critical error:



ERROR #132 (0x85100084) Fatal Exception

Program: C:\Program Files\World of Warcraft\WoW.exe

Exception: 0xC0000096 (PRIV_INSTRUCTION) at 001B:023327B0

====================



The PRIV_INSTRUCTION sometimes also shows as ACCESS VIOLATION



System specs are:

AMD Athlon 64 X2 4400+

Asus A8N SLI Premium motherboard

2g (2x1024) Corsair TWINX2048 - 3200C2PT RAM

WD Raptop 74g SATA

ATI Radeon X1900XTX 512 video card



(SLI mobo was a brainfart. Had 7800 GTX in shopping cart, then saw rebate deal on x1900xtx. Didnt switch mobo to a crossfire board. Hope that doesn't matter since i am only running 1 PCIe x16 card!)



I've run memtest86 on the memory and didnt find any errors. I havent done any overclocking to the system. This is my first home-built PC.



Any suggestions on what to do next? Any help would be much appreciated!

#1
Posted 03/23/2006 03:29 AM   
I am in the exact same situation as you. I'm running a slightly less powerful comp as you but am still having the same problem. I can be playing for a good 20-30 minutes and just, BAM! ERROR #132. I've done everything the WoW site has said to do for troubleshooting and no luck. I'm currently playing Email tag with a Blizzard tech for further assistance, so if you haven't done so already I would suggest emailing them for help.
I am in the exact same situation as you. I'm running a slightly less powerful comp as you but am still having the same problem. I can be playing for a good 20-30 minutes and just, BAM! ERROR #132. I've done everything the WoW site has said to do for troubleshooting and no luck. I'm currently playing Email tag with a Blizzard tech for further assistance, so if you haven't done so already I would suggest emailing them for help.

#2
Posted 04/01/2006 03:24 AM   
I didn't edit because I wanted to bump this, but I fixed my error. On the WoW Tech Support message boards they have a thread about this error. One of the guys said that he simply changed his RAM voltage and it stopped the problem, I tried this and lowered my RAM voltage by .5. Oddly enough my computer will ONLY run WoW without the error with my RAM at a 2.55 Voltage setting. anything else and I still get the message. I'm not saying this will work for everybody but hey, I tried it and it did. Good Luck.
I didn't edit because I wanted to bump this, but I fixed my error. On the WoW Tech Support message boards they have a thread about this error. One of the guys said that he simply changed his RAM voltage and it stopped the problem, I tried this and lowered my RAM voltage by .5. Oddly enough my computer will ONLY run WoW without the error with my RAM at a 2.55 Voltage setting. anything else and I still get the message. I'm not saying this will work for everybody but hey, I tried it and it did. Good Luck.

#3
Posted 04/07/2006 02:00 PM   
i am in the same boat...error 132...just got new pc today..specs are
AMD Athlon 4000+
6600 256 nvidia
A8N-SLI Premium mobo
2 gigs ram

tried bringing down DDR voltage .5 from 3.00...didnt help...did that over and over until i hit 2.60...didnt help...thats the lowest it will let me go..any help or advice on how you did this, especially since we have same mobo...plz do so...i am not the most computer savy person but i can get the job done...just need a little guidance..

============================================================
==================
World of WarCraft (build 5195)

Exe: C:\Program Files\World of Warcraft\WoW.exe
Time: Apr 8, 2006 1:45:46.937 PM
User: Chris
Computer: CHRIS-3D44D2A6B
------------------------------------------------------------------------------

This application has encountered a critical error:

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

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


WoWBuild: 5195
------------------------------------------------------------------------------

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

EAX=00000004 EBX=0012FE18 ECX=6867694D EDX=00002EA6 ESI=06CDC008
EDI=00002EA6 EBP=0012FE04 ESP=0012FDEC EIP=00000004 FLG=00010202
CS =001B DS =0023 ES =0023 SS =0023 FS =003B GS =0000


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

Address Frame Logical addr Module

00000004 0012FE04 0000:00000000 C:\Program Files\World of Warcraft\WoW.exe
005232D5 0012FE30 0001:001222D5 C:\Program Files\World of Warcraft\WoW.exe
00523B71 0012FE58 0001:00122B71 C:\Program Files\World of Warcraft\WoW.exe
0059D403 0012FE98 0001:0019C403 C:\Program Files\World of Warcraft\WoW.exe
00412DA2 0012FF08 0001:00011DA2 C:\Program Files\World of Warcraft\WoW.exe
00412971 0012FF20 0001:00011971 C:\Program Files\World of Warcraft\WoW.exe
00403F10 0012FFC0 0001:00002F10 C:\Program Files\World of Warcraft\WoW.exe
7C816D4F 0012FFF0 0001:00015D4F C:\WINDOWS\system32\kernel32.dll
i am in the same boat...error 132...just got new pc today..specs are

AMD Athlon 4000+

6600 256 nvidia

A8N-SLI Premium mobo

2 gigs ram



tried bringing down DDR voltage .5 from 3.00...didnt help...did that over and over until i hit 2.60...didnt help...thats the lowest it will let me go..any help or advice on how you did this, especially since we have same mobo...plz do so...i am not the most computer savy person but i can get the job done...just need a little guidance..



============================================================

==================

World of WarCraft (build 5195)



Exe: C:\Program Files\World of Warcraft\WoW.exe

Time: Apr 8, 2006 1:45:46.937 PM

User: Chris

Computer: CHRIS-3D44D2A6B

------------------------------------------------------------------------------



This application has encountered a critical error:



ERROR #132 (0x85100084) Fatal Exception

Program: C:\Program Files\World of Warcraft\WoW.exe

Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:00000004



The instruction at "0x00000004" referenced memory at "0x00000004".

The memory could not be "read".





WoWBuild: 5195

------------------------------------------------------------------------------



----------------------------------------

x86 Registers

----------------------------------------



EAX=00000004 EBX=0012FE18 ECX=6867694D EDX=00002EA6 ESI=06CDC008

EDI=00002EA6 EBP=0012FE04 ESP=0012FDEC EIP=00000004 FLG=00010202

CS =001B DS =0023 ES =0023 SS =0023 FS =003B GS =0000





----------------------------------------

Stack Trace (Manual)

----------------------------------------



Address Frame Logical addr Module



00000004 0012FE04 0000:00000000 C:\Program Files\World of Warcraft\WoW.exe

005232D5 0012FE30 0001:001222D5 C:\Program Files\World of Warcraft\WoW.exe

00523B71 0012FE58 0001:00122B71 C:\Program Files\World of Warcraft\WoW.exe

0059D403 0012FE98 0001:0019C403 C:\Program Files\World of Warcraft\WoW.exe

00412DA2 0012FF08 0001:00011DA2 C:\Program Files\World of Warcraft\WoW.exe

00412971 0012FF20 0001:00011971 C:\Program Files\World of Warcraft\WoW.exe

00403F10 0012FFC0 0001:00002F10 C:\Program Files\World of Warcraft\WoW.exe

7C816D4F 0012FFF0 0001:00015D4F C:\WINDOWS\system32\kernel32.dll

#4
Posted 04/08/2006 06:08 AM   
[quote name='Grimie' date='Apr 8 2006, 08:08 AM']i am in the same boat...error 132...just got new pc today..specs are
AMD Athlon 4000+
6600 256 nvidia
A8N-SLI Premium mobo
2 gigs ram

tried bringing down DDR voltage .5 from 3.00...didnt help...did that over and over until i hit 2.60...didnt help...thats the lowest it will let me go..any help or advice on how you did this, especially since we have same mobo...plz do so...i am not the most computer savy person but i can get the job done...just need a little guidance..

============================================================
==================
World of WarCraft (build 5195)

Exe:      C:\Program Files\World of Warcraft\WoW.exe
Time:    Apr  8, 2006  1:45:46.937 PM
User:    Chris
Computer: CHRIS-3D44D2A6B
------------------------------------------------------------------------------

This application has encountered a critical error:

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

The instruction at "0x00000004" referenced memory at "0x00000004".
The memory could not be "read".
WoWBuild: 5195
------------------------------------------------------------------------------

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

EAX=00000004  EBX=0012FE18  ECX=6867694D  EDX=00002EA6  ESI=06CDC008
EDI=00002EA6  EBP=0012FE04  ESP=0012FDEC  EIP=00000004  FLG=00010202
CS =001B      DS =0023      ES =0023      SS =0023      FS =003B      GS =0000
----------------------------------------
    Stack Trace (Manual)
----------------------------------------

Address  Frame    Logical addr  Module

00000004 0012FE04 0000:00000000 C:\Program Files\World of Warcraft\WoW.exe
005232D5 0012FE30 0001:001222D5 C:\Program Files\World of Warcraft\WoW.exe
00523B71 0012FE58 0001:00122B71 C:\Program Files\World of Warcraft\WoW.exe
0059D403 0012FE98 0001:0019C403 C:\Program Files\World of Warcraft\WoW.exe
00412DA2 0012FF08 0001:00011DA2 C:\Program Files\World of Warcraft\WoW.exe
00412971 0012FF20 0001:00011971 C:\Program Files\World of Warcraft\WoW.exe
00403F10 0012FFC0 0001:00002F10 C:\Program Files\World of Warcraft\WoW.exe
7C816D4F 0012FFF0 0001:00015D4F C:\WINDOWS\system32\kernel32.dll
[right][post="82301"]<{POST_SNAPBACK}>[/post][/right][/quote]


whats the deal with ram latency? what does changing that value do to overall performance?
[quote name='Grimie' date='Apr 8 2006, 08:08 AM']i am in the same boat...error 132...just got new pc today..specs are

AMD Athlon 4000+

6600 256 nvidia

A8N-SLI Premium mobo

2 gigs ram



tried bringing down DDR voltage .5 from 3.00...didnt help...did that over and over until i hit 2.60...didnt help...thats the lowest it will let me go..any help or advice on how you did this, especially since we have same mobo...plz do so...i am not the most computer savy person but i can get the job done...just need a little guidance..



============================================================

==================

World of WarCraft (build 5195)



Exe:      C:\Program Files\World of Warcraft\WoW.exe

Time:    Apr  8, 2006  1:45:46.937 PM

User:    Chris

Computer: CHRIS-3D44D2A6B

------------------------------------------------------------------------------



This application has encountered a critical error:



ERROR #132 (0x85100084) Fatal Exception

Program: C:\Program Files\World of Warcraft\WoW.exe

Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:00000004



The instruction at "0x00000004" referenced memory at "0x00000004".

The memory could not be "read".

WoWBuild: 5195

------------------------------------------------------------------------------



----------------------------------------

    x86 Registers

----------------------------------------



EAX=00000004  EBX=0012FE18  ECX=6867694D  EDX=00002EA6  ESI=06CDC008

EDI=00002EA6  EBP=0012FE04  ESP=0012FDEC  EIP=00000004  FLG=00010202

CS =001B      DS =0023      ES =0023      SS =0023      FS =003B      GS =0000

----------------------------------------

    Stack Trace (Manual)

----------------------------------------



Address  Frame    Logical addr  Module



00000004 0012FE04 0000:00000000 C:\Program Files\World of Warcraft\WoW.exe

005232D5 0012FE30 0001:001222D5 C:\Program Files\World of Warcraft\WoW.exe

00523B71 0012FE58 0001:00122B71 C:\Program Files\World of Warcraft\WoW.exe

0059D403 0012FE98 0001:0019C403 C:\Program Files\World of Warcraft\WoW.exe

00412DA2 0012FF08 0001:00011DA2 C:\Program Files\World of Warcraft\WoW.exe

00412971 0012FF20 0001:00011971 C:\Program Files\World of Warcraft\WoW.exe

00403F10 0012FFC0 0001:00002F10 C:\Program Files\World of Warcraft\WoW.exe

7C816D4F 0012FFF0 0001:00015D4F C:\WINDOWS\system32\kernel32.dll

[post="82301"]<{POST_SNAPBACK}>[/post]






whats the deal with ram latency? what does changing that value do to overall performance?

#5
Posted 08/21/2006 01:42 AM   
[quote name='BugMeNot' date='Aug 20 2006, 05:42 PM']whats the deal with ram latency? what does changing that value do to overall performance?
[right][post="108441"]<{POST_SNAPBACK}>[/post][/right][/quote]


I have had this error for around 2 months now. I've tried everything twice!!

New vid card / memory... changing memory dimm slots.

Im not about to go out and buy a new mobo.

It only happens for me on thaddius encounter in naxxaramas. Other then that I can go days with out this error. At this point im desprate, it's very hard to understand how so many people have this error, and so many people have differnt fixes for it. H E L P M E
[quote name='BugMeNot' date='Aug 20 2006, 05:42 PM']whats the deal with ram latency? what does changing that value do to overall performance?

[post="108441"]<{POST_SNAPBACK}>[/post]






I have had this error for around 2 months now. I've tried everything twice!!



New vid card / memory... changing memory dimm slots.



Im not about to go out and buy a new mobo.



It only happens for me on thaddius encounter in naxxaramas. Other then that I can go days with out this error. At this point im desprate, it's very hard to understand how so many people have this error, and so many people have differnt fixes for it. H E L P M E

#6
Posted 09/15/2006 05:25 AM   
[quote name='^Kover7' date='Sep 14 2006, 09:25 PM']I have had this error for around 2 months now.  I've tried everything twice!!

New vid card / memory... changing memory dimm slots. 

Im not about to go out and buy a new mobo.

It only happens for me on thaddius encounter in naxxaramas.  Other then that I can go days with out this error.  At this point im desprate, it's very hard to understand how so many people have this error, and so many people have differnt fixes for it.  H E L P M E
[right][snapback]113992[/snapback][/right]
[/quote]


I have the same problem i had it for 3 weeks how do i fix it i done everything
[quote name='^Kover7' date='Sep 14 2006, 09:25 PM']I have had this error for around 2 months now.  I've tried everything twice!!



New vid card / memory... changing memory dimm slots. 



Im not about to go out and buy a new mobo.



It only happens for me on thaddius encounter in naxxaramas.  Other then that I can go days with out this error.  At this point im desprate, it's very hard to understand how so many people have this error, and so many people have differnt fixes for it.  H E L P M E

[snapback]113992[/snapback]








I have the same problem i had it for 3 weeks how do i fix it i done everything

#7
Posted 03/19/2007 09:25 PM   
[quote name='KillaJT' date='Mar 19 2007, 04:25 PM']I have the same problem i had it for 3 weeks how do i fix it i done everything
[right][snapback]173402[/snapback][/right]
[/quote]


I get the exact same problem only when I go into the BF instance in Outlands. No where else, no other instance does this to me. I can walk 10 to 15 steps into BF and then crash, and continual crash until I turn the char around to walk out.

I used to get this exact issue going into the BRS instances prior to Burning Crusades but after the upgrade I was able to go into those instances without issue.

I have run the repair kit, says files are fine, I have no known issues with my hardware and when not going into that instance I play without lag, or anything.


What can be done?
[quote name='KillaJT' date='Mar 19 2007, 04:25 PM']I have the same problem i had it for 3 weeks how do i fix it i done everything

[snapback]173402[/snapback]








I get the exact same problem only when I go into the BF instance in Outlands. No where else, no other instance does this to me. I can walk 10 to 15 steps into BF and then crash, and continual crash until I turn the char around to walk out.



I used to get this exact issue going into the BRS instances prior to Burning Crusades but after the upgrade I was able to go into those instances without issue.



I have run the repair kit, says files are fine, I have no known issues with my hardware and when not going into that instance I play without lag, or anything.





What can be done?

#8
Posted 04/11/2007 07:32 PM   
This happened to me about 1 week after I got the video card I'm using (6200 GeForce, but might work for you aswell). One of the ways I fixed this problem was changing the refresh rate of the video card (From 75hrz to 70hrz) ... dunno exactly how I did it but it worked! ^_^
This happened to me about 1 week after I got the video card I'm using (6200 GeForce, but might work for you aswell). One of the ways I fixed this problem was changing the refresh rate of the video card (From 75hrz to 70hrz) ... dunno exactly how I did it but it worked! ^_^

#9
Posted 04/15/2007 04:09 AM   
From reading this thread I have a pretty good idea of what everyone's problem is here. Its probably not a memory issue , or even a glitch. It has something to do with windows works if my hunch is correct on what is causing your problem.

If any of you have shared computers this will go a lot easier. If you or someone else installed World of Warcraft on a different username that has a password, and most importantly keeps its files private, you will have a difficult time doing much with that program on another username First Admin , Admin, or not. Especially running the program for the first time where it might require setup files from that original user's private data which held the setup info. Its also possible that you ran some sort of cleaner right after installation accidently deleting the ifiles to finish installation.

Now that is just general Windows information, but reformatting would also help this too with any big hardware change especially a video card or a motherboard. Dont get too stressed out if that doesnt work either just try to relax.

Computers can be the most stress causing devices in the world if you want them to be.

Be happy,
Silverbot

PS: Attach DX Diags just in case, so someone can look at that if your issue isn't fixed.
From reading this thread I have a pretty good idea of what everyone's problem is here. Its probably not a memory issue , or even a glitch. It has something to do with windows works if my hunch is correct on what is causing your problem.



If any of you have shared computers this will go a lot easier. If you or someone else installed World of Warcraft on a different username that has a password, and most importantly keeps its files private, you will have a difficult time doing much with that program on another username First Admin , Admin, or not. Especially running the program for the first time where it might require setup files from that original user's private data which held the setup info. Its also possible that you ran some sort of cleaner right after installation accidently deleting the ifiles to finish installation.



Now that is just general Windows information, but reformatting would also help this too with any big hardware change especially a video card or a motherboard. Dont get too stressed out if that doesnt work either just try to relax.



Computers can be the most stress causing devices in the world if you want them to be.



Be happy,

Silverbot



PS: Attach DX Diags just in case, so someone can look at that if your issue isn't fixed.

#10
Posted 04/15/2007 06:25 PM   
:) [quote name='^Kover7' date='Sep 14 2006, 09:25 PM']I have had this error for around 2 months now.  I've tried everything twice!!

New vid card / memory... changing memory dimm slots. 

Im not about to go out and buy a new mobo.

It only happens for me on thaddius encounter in naxxaramas.  Other then that I can go days with out this error.  At this point im desprate, it's very hard to understand how so many people have this error, and so many people have differnt fixes for it.  H E L P M E
[right][snapback]113992[/snapback][/right]
[/quote]
I replaced a videocard and memory and had the same problem. After i load the default settings in the bios everything worked fine for me.

try it out and let me know..

:)
:) [quote name='^Kover7' date='Sep 14 2006, 09:25 PM']I have had this error for around 2 months now.  I've tried everything twice!!



New vid card / memory... changing memory dimm slots. 



Im not about to go out and buy a new mobo.



It only happens for me on thaddius encounter in naxxaramas.  Other then that I can go days with out this error.  At this point im desprate, it's very hard to understand how so many people have this error, and so many people have differnt fixes for it.  H E L P M E

[snapback]113992[/snapback]




I replaced a videocard and memory and had the same problem. After i load the default settings in the bios everything worked fine for me.



try it out and let me know..



:)

#11
Posted 04/17/2007 03:37 PM   
[quote name='Rosaro' date='Apr 17 2007, 09:37 AM']:)
I replaced a videocard and memory and had the same problem. After i load the default settings in the bios everything worked fine for me.

try it out and let me know..

:)
[right][snapback]185866[/snapback][/right]
[/quote]

i'm not real good with computers, what bios did u set to default?
[quote name='Rosaro' date='Apr 17 2007, 09:37 AM']:)

I replaced a videocard and memory and had the same problem. After i load the default settings in the bios everything worked fine for me.



try it out and let me know..



:)

[snapback]185866[/snapback]






i'm not real good with computers, what bios did u set to default?

#12
Posted 04/24/2007 06:49 PM   
hey guys i got my problem fixed. If you have any new hardware in your computer that came with some type of software and you did not instal it, that might be your problem. Thats what i did and now WoW runs fine for me. Hope it helped. -.-
hey guys i got my problem fixed. If you have any new hardware in your computer that came with some type of software and you did not instal it, that might be your problem. Thats what i did and now WoW runs fine for me. Hope it helped. -.-

#13
Posted 03/12/2008 03:47 PM   
Ok, i do not know what server you guys are on, but if you are on any FREESERVER, there is a quick and simple fix to this problem. I am not sure if they work on retail wow, but this might help: /blarg.gif' class='bbc_emoticon' alt=':/' />

1. Delete ur cache folder! [My computer > Local Disk > Program Files > World of Warcraft > Cache] (this is for PC (!) , no idea for macs >.< )

2. Disable your addons! (im guessing you know how to do that if you use them, if you dont use them, dont worry about it.) for PC its [My computer > Local Disk > Program Files > World of Warcraft > Interface > AddOns] (the blizzard ones dont do anything )

3. Every once in a while delete your WTF folder in the WoW Folder (WTF stands for: WoW Temporary Folder, dont worry about it, you wil just have to reconfig ur bindings, and other settings) path for PCs: [My computer > Local Disk > Program Files > World of Warcraft > WTF]

4. If that doesnt work, well... ur kinda buggered i guess, but good luck, hope that helps, if almost ALWAYS works on free servers, retail figured out the problem i think. Again: Good Luck! /wave.gif' class='bbc_emoticon' alt=':wave:' />



[quote name='Cooter' date='Mar 22 2006, 07:29 PM']WoW frequently crashes on a newly built pc. 

================
This application has encountered a critical error:

ERROR #132 (0x85100084) Fatal Exception
Program: C:\Program Files\World of Warcraft\WoW.exe
Exception: 0xC0000096 (PRIV_INSTRUCTION) at 001B:023327B0
====================

The PRIV_INSTRUCTION sometimes also shows as ACCESS VIOLATION

System specs are:
AMD Athlon 64 X2 4400+
Asus A8N SLI Premium motherboard
2g (2x1024) Corsair TWINX2048 - 3200C2PT RAM
WD Raptop 74g SATA
ATI Radeon X1900XTX 512 video card

(SLI mobo was a brainfart.  Had 7800 GTX in shopping cart, then saw rebate deal on x1900xtx.  Didnt switch mobo to a crossfire board.  Hope that doesn't matter since i am only running 1 PCIe x16 card!)

I've run memtest86 on the memory and didnt find any errors.  I havent done any overclocking to the system.  This is my first home-built PC.

Any suggestions on what to do next?  Any help would be much appreciated!
[right][snapback]78643[/snapback][/right]
[/quote]
Ok, i do not know what server you guys are on, but if you are on any FREESERVER, there is a quick and simple fix to this problem. I am not sure if they work on retail wow, but this might help: /blarg.gif' class='bbc_emoticon' alt=':/' />



1. Delete ur cache folder! [My computer > Local Disk > Program Files > World of Warcraft > Cache] (this is for PC (!) , no idea for macs >.< )



2. Disable your addons! (im guessing you know how to do that if you use them, if you dont use them, dont worry about it.) for PC its [My computer > Local Disk > Program Files > World of Warcraft > Interface > AddOns] (the blizzard ones dont do anything )



3. Every once in a while delete your WTF folder in the WoW Folder (WTF stands for: WoW Temporary Folder, dont worry about it, you wil just have to reconfig ur bindings, and other settings) path for PCs: [My computer > Local Disk > Program Files > World of Warcraft > WTF]



4. If that doesnt work, well... ur kinda buggered i guess, but good luck, hope that helps, if almost ALWAYS works on free servers, retail figured out the problem i think. Again: Good Luck! /wave.gif' class='bbc_emoticon' alt=':wave:' />







[quote name='Cooter' date='Mar 22 2006, 07:29 PM']WoW frequently crashes on a newly built pc. 



================

This application has encountered a critical error:



ERROR #132 (0x85100084) Fatal Exception

Program: C:\Program Files\World of Warcraft\WoW.exe

Exception: 0xC0000096 (PRIV_INSTRUCTION) at 001B:023327B0

====================



The PRIV_INSTRUCTION sometimes also shows as ACCESS VIOLATION



System specs are:

AMD Athlon 64 X2 4400+

Asus A8N SLI Premium motherboard

2g (2x1024) Corsair TWINX2048 - 3200C2PT RAM

WD Raptop 74g SATA

ATI Radeon X1900XTX 512 video card



(SLI mobo was a brainfart.  Had 7800 GTX in shopping cart, then saw rebate deal on x1900xtx.  Didnt switch mobo to a crossfire board.  Hope that doesn't matter since i am only running 1 PCIe x16 card!)



I've run memtest86 on the memory and didnt find any errors.  I havent done any overclocking to the system.  This is my first home-built PC.



Any suggestions on what to do next?  Any help would be much appreciated!

[snapback]78643[/snapback]


#14
Posted 06/10/2008 01:24 AM   
[quote name='BSoD Victim' date='Jun 9 2008, 09:24 PM']Ok, i do not know what server you guys are on, but if you are on any FREESERVER, there is a quick and simple fix to this problem. I am not sure if they work on retail wow, but this might help: /blarg.gif' class='bbc_emoticon' alt=':/' />

1. Delete ur cache folder! [My computer > Local Disk > Program Files > World of Warcraft > Cache]  (this is for PC  (!) , no idea for macs  >.< )

2. Disable your addons! (im guessing you know how to do that if you use them, if you dont use them, dont worry  about it.) for PC its [My computer > Local Disk > Program Files > World of Warcraft > Interface > AddOns] (the blizzard ones dont do anything )

3. Every once in a while delete your WTF folder in the WoW Folder (WTF stands for: WoW Temporary Folder, dont worry about it, you wil just have to reconfig ur bindings, and other settings) path for PCs:  [My computer > Local Disk > Program Files > World of Warcraft > WTF]

4. If that doesnt work, well... ur kinda buggered i guess, but good luck, hope that helps, if almost ALWAYS works on free servers, retail figured out the problem i think. Again: Good Luck!  /wave.gif' class='bbc_emoticon' alt=':wave:' />
[right][snapback]391174[/snapback][/right]
[/quote]

That's called resetting your interface and it fixes like 90% of problems.
[quote name='BSoD Victim' date='Jun 9 2008, 09:24 PM']Ok, i do not know what server you guys are on, but if you are on any FREESERVER, there is a quick and simple fix to this problem. I am not sure if they work on retail wow, but this might help: /blarg.gif' class='bbc_emoticon' alt=':/' />



1. Delete ur cache folder! [My computer > Local Disk > Program Files > World of Warcraft > Cache]  (this is for PC  (!) , no idea for macs  >.< )



2. Disable your addons! (im guessing you know how to do that if you use them, if you dont use them, dont worry  about it.) for PC its [My computer > Local Disk > Program Files > World of Warcraft > Interface > AddOns] (the blizzard ones dont do anything )



3. Every once in a while delete your WTF folder in the WoW Folder (WTF stands for: WoW Temporary Folder, dont worry about it, you wil just have to reconfig ur bindings, and other settings) path for PCs:  [My computer > Local Disk > Program Files > World of Warcraft > WTF]



4. If that doesnt work, well... ur kinda buggered i guess, but good luck, hope that helps, if almost ALWAYS works on free servers, retail figured out the problem i think. Again: Good Luck!  /wave.gif' class='bbc_emoticon' alt=':wave:' />

[snapback]391174[/snapback]






That's called resetting your interface and it fixes like 90% of problems.

#15
Posted 06/10/2008 01:42 AM   
  1 / 2    
Scroll To Top