Author Topic: Critical error (Read 1343 times)

Leodred · « **on:** September 16, 2007, 01:19:29 PM »

Wondered if anyone would be able to help me with a problem, after reinstalling WoW and WoW:TBC I click 'Play World of warcraft' and then this error pops up:

==============================================================================
World of WarCraft (build 6080)

Exe: C:\Program Files\World of Warcraft\WoW.exe
Time: Sep 16, 2007 2:15:14.656 PM
User: Ted
Computer: COLE
------------------------------------------------------------------------------

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:0067BF05

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

WoWBuild: 6080

Not sure what's happening, but I can't continue with the patches, anyone know what could be wrong?

Jaxc · « **Reply #1 on:** September 16, 2007, 01:22:35 PM »

try to restart you comp

Leodred · « **Reply #2 on:** September 16, 2007, 01:36:16 PM »

no luck

Daemonetta · « **Reply #3 on:** September 16, 2007, 01:41:37 PM »

have you tried googling the error?
http://www.google.co.uk/search?q=ERROR+%23...art=10&sa=N

seems to be a common error, using an Nvidia card by any chance?

If you need more help we really need to see your computer specs as well? i.e processer, os, mem installed, video card etc.

Although from the google i would say clean install of your video drivers is the first step.

Jaxc · « **Reply #4 on:** September 16, 2007, 01:48:28 PM »

start menu>run>dxdiag>save the info and post here

that should provide the info daemonetta needs

Leodred · « **Reply #5 on:** September 16, 2007, 01:59:43 PM »

Edit: no need to have all that posted anymore

Leodred · « **Reply #6 on:** September 16, 2007, 03:13:09 PM »

Update: Just used system restore, so starting over.

Jaxc · « **Reply #7 on:** September 16, 2007, 03:18:29 PM »

btw, you tryed to repair wow? just if you havnt

Splishy · « **Reply #8 on:** September 16, 2007, 04:13:49 PM »

You want to hit Windows Update, and keep hitting it until you have no updatyes left. At least part of your issue is that you're using the default display driver

Daemonetta · « **Reply #9 on:** September 16, 2007, 04:17:47 PM »

copied from blizzard tech site----WORKING SOLUTION

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

For those that are affected by this Error 132 (unsupported and supported cards both), you can get around that error by setting your texture quality to 'high'. To do this, go to your World of Warcraft folder and open the WTF folder. Open the config.wtf file in Wordpad, then look for this line:

SET baseMip "1"

If that exists, change it to a "0". If that doesn't exist, copy and paste this line to the bottom of the file:

SET baseMip "0"

Save the file and try the game. A low quality texture fix will come in a future patch.

A fix to this is coming in a future patch.

NOTE: If you reopen the "config.wtf" file after making changes, you may not actually see all the lines you added, but this is normal. It does not necessarily mean the game has not saved them in its own data files.

Update

S3 people and others with a related Error 132 crash - you may want to install the latest motherboard chipset drivers as well as the video card drivers. Development and the QA teams will be trying to reproduce the bug on the S3 UniChrome since it seems to happen most often there and seems to be related enough to other non-related cards. If it can be reproduced, they can work on a solution. They will be using the latest available drivers so you'll want those too to be on the same page.

If you need help finding the chipset drivers, check this - http://www.playtool.com/pages/chipse...s/chipset.html

S3 Drivers - http://www.s3graphics.com/en/index****p
nVidia Drivers - http://www.nvidia.com/
AMD/ATI Drivers - http://ati.amd.com/

Leodred · « **Reply #10 on:** September 16, 2007, 06:25:27 PM »

Well after using system restore, I made sure that firewall and virus protectors were up, then I had some problems with connection (nothing to do with firewall), by the time I got back on it was a little late, so I'm not going to bother installing wow again untill I come back next saturday.

Leodred · « **Reply #11 on:** September 23, 2007, 10:22:37 AM »

Okay I started reinstalling WoW again and the error popped up again, Splishy you said I needed to use windows update, exactly how do I do that?

Leodred · « **Reply #12 on:** September 23, 2007, 10:59:20 AM »

Done Repair wow, no change, still getting the error

Splishy · « **Reply #13 on:** September 23, 2007, 11:46:45 AM »

goto www.windowsupdate.com. Scan and install any and all available updates. Then once that's done click start>run and type cmd then press enter. From the black box that pops up type chkdsk c: /r and press enter - it will say that the volume is locked and ask if you want to do this on next reboot. elect yes, then reboot.

This will check your hard drive for problems, and fix them if it can. Dependent on the size of the drive it may take quite some time (read hours)

Leodred · « **Reply #14 on:** September 23, 2007, 03:39:25 PM »

hmm well I have automatic updates switched on, and I did the scan anyway, but still no luck.

TomTheWizard · « **Reply #15 on:** September 23, 2007, 03:40:57 PM »

Hmm, just a guess, could this be a RAM issue? (Ram is memory (I.T. Crowd))

Leodred · « **Reply #16 on:** September 23, 2007, 04:20:49 PM »

I checked the error with the technical forums and some info about it came up:

Quote

Memory Could Not Be Read/Written

This 132 error is the most common, and unfortunately the most vague.

Q u o t e:

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

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

Note: The above example may be different to the error you are getting.

The explanation for this is that an error occurred while accessing data that caused the software (World of Warcraft) to be unable to continue functioning correctly. While the most common cause can indeed be system memory (RAM) related, it certainly does not imply that all occurrences of this issue are.

I checked the error with the technical forums and some info about it came up:

Memory Could Not Be Read/Written

This 132 error is the most common, and unfortunately the most vague.

Q u o t e:

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

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

Note: The above example may be different to the error you are getting.

The explanation for this is that an error occurred while accessing data that caused the software (World of Warcraft) to be unable to continue functioning correctly. While the most common cause can indeed be system memory (RAM) related, it certainly does not imply that all occurrences of this issue are.
Quote

Splishy · « **Reply #17 on:** September 23, 2007, 04:42:08 PM »

did chkdsk /r throw any errors? If not your next port of call is Memtest86++ - download the .iso, boot from it and leave it running overnight (or for a good few hours anyways) and this will tell you if your RAM is borked.

Leodred · « **Reply #18 on:** September 23, 2007, 05:08:33 PM »

Okay well I'll try that next time I'm up my grandparents, getting a little late and I won't be around to find out if this Memtest hasdiscovered anything or not.

Splishy · « **Reply #19 on:** September 23, 2007, 05:10:21 PM »

NP, as I said, it needs a good long run (8 hours is a good number) to fully test the RAM. If it throws errors quickly you know you have an issue though!

http://www.memtest.org/download/1.70/memtest86+-1.70.iso.zip for the zipped ISO btw

News:

Author Topic: Critical error (Read 1343 times)