Topic
Crit Error 132
|
|
Edited by Púnzorz on 30/08/12 16:06 (BST)
I keep getting this Crit Errors, I Open up Wow all is fine, I can see everyone, Cast skills, Etc But i randomly get one of these 2 errors, but it didnt happen straight away, it was around 1 hour to 2 hours after i had downloaded the new patch and i have no idea why it is doing this.
http://pastebin.com/Pw145Gvc is the Error Log Things i've tried: All my Wow Clients + Launcher Are defaulted to open up as Administrator I've deleted my Cache folder Deleted my WTF folder Deleted My interface Folder Deleted my Battle.net folders Ive deleted my WoW.mFil File Followed the infomation on this article http://eu.battle.net/support/en/article/error-132 Ive Tried With and Without Addons, Happens either way Had my Heat on the Computer Monitored as the Blue Article Said, Was fine Defragged my HDD checked for my Out-dated Drivers, All up to date.. Clicked On Recomended Settings on the System File Ive Tried the Wow-32 client Does anyone know a REAL solution? |
|
|
?
|
|
I'm having the same problem as you...
|
|
|
any Blue gonna post?
|
|
nope!
|
|
|
Got same problem, 3 errors in 3 hours. One when been dpsing dummies, 2 in dragonsoul (1 out of combat 1 during warmaster fight)
This application has encountered a critical error: ERROR #132 (0x85100084) Fatal exception! Program: C:\Users\Public\Games\World of Warcraft\WoW-64.exe ProcessID: 1252 Exception: 0xC0000005 (ACCESS_VIOLATION) at 0033:000000013FE37DC4 The instruction at "0x000000013FE37DC4" referenced memory at "0x000000000000001C". The memory could not be "written". |
|
|
Had same probe, using the 32 bit cliënt solved the prob.
|
|
|
I got the same problem. I have tried to reinstall the game, tried 32 and 64 bit, Directx 9 and 11.
Without any addons, and never had the problem before the patch. |
|
|
Same problem here, but only on one of two identical laptops (probably not hardware-related?). Tried reinstalling the patch, but to no avail. Running the 64-bit clients.
|
|
Would be nice if someone from Blizz could look in to this.
|
|
had the same problem as i was in a raid on my rogue, completely inconvenient. patch isnt fully ready and needs to be looked in to. this is what we pay our money for, to be able to play a game that works. please fix this and at least can we get a blue post on here?
|
|
|
This |
|
SOLUTION FOR PEOPLE : >
Anyone still having this program i was getting error 132 all the time i went and changed my System settings on the logging screen (where u type your e mail and pass) go system and go Recomended settings and accept to all it fixed my error 132 hope it does for you cheers |
|
|
Didnt work for me, Tried over 13 diferent things now, that people have said, im still getting no luck :s tho the attempts to fixing it did prolong the Crit error so i cud get around 20-25 mins of play time, before i got it
|
|
|
Hi guys,
Please could you check if the issue is caused by the issue I have described at the following thread: - http://eu.battle.net/wow/en/forum/topic/5207843100 Basically, there is a proven bug that makes you crash if someone else logs in on an account that you have enabled using Recruit-A-Friend. If you can see this is the case for you, please post in that thread so we can get some visibility on the issue. |
|
|
Its the Same Code you shown in your thread, but it was happening when my RaF Wasn't Even logging in, he had got the 90% Big so went offline for around 2 hours, Yet i still got around 5-8 Crit Errors in that time.
|
|
OP: We can't help you without seeing the error log.
Everyone else: Start your thread, include the error log. Poupi: We need to see the entire error message to be able to help. |
|
|
How am i supost to post my error log? it exceeds the Maximam amount of Characters?
|
|
You could cut it in half and spread it over two posts, you could save it on an external website like http://pastebin.com/ and then link us to it, et cetera.
|
|
|
http://pastebin.com/Pw145Gvc is the Error Log
|
