Suddenly wow wont run? Critical error

[Nobody]

Hey guys used to play fine until now but this morning suddenly whenever i try to run wow nos i get a critical error and wow crashes any got any ideas??

[Nobody]

im getting error 132 ! i tried deleting wow completely and downloading it again and i still get the same error ! can someone help?? it seems to have happened out of nowhere yesterday i was playing fine !

[Uzephi]

Can you print screen the error and post it here?

To do this, press the print screen button on your keyboard and then go into a photo editing program like paint and paste the image and save it as a jpg file and in the "full editor" you can attach an image less than 250kb.

[Nobody]

http://imageshack.com/a/img661/8205/1m8ij1.png

this is the error

[Uzephi]

Access violation usually is admin privileges error. Can you right click wow.exe and run as administrator and see if you get the error again?

[Diametra]

ya, after that ^

try this: Right click on wow.exe. Select> troubleshoot compatibility. Select> try recommended settings. Select> start the Program.

[Uzephi]

Let us know if adding admin privileges fixes your issue. If you are not on an admin account on your PC, try installing on another partition than C. I personally have a separate partition for games (Partitioned and named A drive).

[Nobody]

i run wow as administrator and still didnt work :/ i also tried the troubleshoot compatibility -> recommended settings and i still get the same error... its really weird this thing out of the blue

[schaka]

Don't use any addons at all, make sure WTF and WDB are both deleted when starting the game as admin.
Tbh, if it's a genuine #132, not one thrown by corrupt addons or something similarly stupid, that's most likely caused by broken RAM or a broken hard drive.

I used to have the same issue with WoW randomly erroring until I got new RAM. Sometimes after an error, I couldn't log back in without having that specific character moved by a GM. Then other times, I could never get on GM Island (private servers) without erroring.

So yeah, do a memcheck.

[Uzephi]

That is odd the error is stating a memory block could not be read. Usually admin privileges would fix this issue. Below is the read/write permissions the folder should have. To get to the permissions screen, right click the folder and go to properties and select the tab security. Admin accounts should have full control. You could edit so users have full control as well.

Edit: as posted above: If permissions are set right, a memory block could be corrupt. Below is a link with instructions on how to do a memcheck with windows 7

http://windows.microsoft.com/en-us/wind ... r-computer

Untitled-1.jpg (228 KiB) Viewed 4400 times